Procure to Pay Cycle Query

PROCURE TO PAY QUERY WITHOUT RECEIPTS

SELECT DISTINCT reqh.segment1 req_num, reqh.authorization_status req_status,

                poh.segment1 po_num, pol.line_num,

                poh.authorization_status po_status, i.invoice_num,

                i.invoice_amount, i.amount_paid, i.vendor_id, v.vendor_name,

                c.check_number, h.gl_transfer_flag, h.period_name

           FROM ap_invoices_all i,

                ap_invoice_distributions_all invd,

                po_headers_all poh,

                po_lines_all pol,

                po_distributions_all pod,

                po_vendors v,

                po_requisition_headers_all reqh,

                po_requisition_lines_all reql,

                po_req_distributions_all reqd,

                ap_invoice_payments_all p,

                ap_checks_all c,

                ap_ae_headers_all h,

                ap_ae_lines_all l

          WHERE 1 = 1

            AND i.vendor_id = v.vendor_id

            AND c.check_id = p.check_id

            AND p.invoice_id = i.invoice_id

            AND poh.po_header_id = pol.po_header_id

            AND reqh.requisition_header_id = reql.requisition_header_id

            AND reqd.requisition_line_id = reql.requisition_line_id

            AND pod.req_distribution_id = reqd.distribution_id

            AND pod.po_header_id = poh.po_header_id

            AND pod.po_distribution_id = invd.po_distribution_id

            AND invd.invoice_id = i.invoice_id

            AND h.ae_header_id = l.ae_header_id

            AND l.source_table = 'AP_INVOICES'

            AND l.source_id =i.invoice_id

            --AND poh.segment1 = :PO_NUMBER

            --AND reqh.segment1 = :req_number

            --AND i.invoice_num = :INVOICE NUMBER

PROCURE TO PAY CYCLE QUERY WITH RECEIPTS

SELECT DISTINCT reqh.segment1 req_num, reqh.authorization_status req_status,

                poh.segment1 po_num, pol.line_num,

                poh.authorization_status po_status, rcvh.receipt_num,

                rcv.inspection_status_code, i.invoice_num, i.invoice_amount,

                i.amount_paid, i.vendor_id, v.vendor_name, c.check_number,

                h.gl_transfer_flag, h.period_name

           FROM ap_invoices_all i,

                ap_invoice_distributions_all invd,

                po_headers_all poh,

                po_lines_all pol,

                po_distributions_all pod,

                po_vendors v,

                po_requisition_headers_all reqh,

                po_requisition_lines_all reql,

                po_req_distributions_all reqd,

                rcv_transactions rcv,

                rcv_shipment_headers rcvh,

                rcv_shipment_lines rcvl,

                ap_invoice_payments_all p,

                ap_checks_all c,

                ap_ae_headers_all h,

                ap_ae_lines_all l

          WHERE 1 = 1

            AND i.vendor_id = v.vendor_id

            AND c.check_id = p.check_id

            AND p.invoice_id = i.invoice_id

            AND poh.po_header_id = pol.po_header_id

            AND reqh.requisition_header_id = reql.requisition_header_id

            AND reqd.requisition_line_id = reql.requisition_line_id

            AND pod.req_distribution_id = reqd.distribution_id

            AND pod.po_header_id =poh.po_header_id

            AND POH.PO_HEADER_ID = RCV.PO_HEADER_ID

            AND rcvh.shipment_header_id = rcv.shipment_header_id(+)

            AND pod.po_distribution_id = invd.po_distribution_id

            AND invd.invoice_id = i.invoice_id

            AND h.ae_header_id = l.ae_header_id

            AND l.source_table = 'AP_INVOICES'

            AND l.source_id = i.invoice_id

            --AND poh.segment1 = :PO_NUMBER

            --AND reqh.segment1 = :req_number

Read more »

HZ tables in Oracle Receivables

This article describes few important HZ tables in AR and their relationships with each other.

HZ_PARTIES:

The HZ_PARTIES table stores basic information about parties that can be shared with any relationship that the party might establish with another party. The primary key for this table is PARTY_ID.

Few Important Columns are

  1. PARTY_ID: Party identifier
  2. PARTY_NUMBER: Unique identification number for this party
  3. PARTY_NAME: Name of the party
  4..PARTY_TYPE: The party type can only be Person, Organization, Group or Relationship.

HZ_PARTY_SITES:

The HZ_PARTY_SITES table links a party (HZ_PARTIES) and a location (HZ_LOCATIONS) and stores location-specific party information. One party can optionally have one or more party sites. One location can optionally be used by one or more parties. The primary key for this table is PARTY_SITE_ID.

Few Important Columns are

  1. PARTY_SITE_ID: Party site identifier.
  2. PARTY_ID: Identifier for the party. Foreign key to the HZ_PARTIES table.
  3. LOCATION_ID: Identifier for the party site. Foreign key to the HZ_LOCATIONS table.
  4. PARTY_SITE_NUMBER: Party site number.
  5. PARTY_SITE_NAME: User-defined name for the site.
  6. ADDRESSEE: Addressee information.

HZ_LOCATIONS:

The HZ_LOCATIONS table stores information about a delivery or postal address such as building number, street address, postal code, and directions to a location. This table provides physical location information about parties (organizations and people) and customer accounts. The primary key for this table is LOCATION_ID.

Few Important Columns are

  1. LOCATION_ID: Unique identifier for this location
  2. COUNTRY: Country code from the TERRITORY_CODE column in the         FND_TERRITORY table
  3. ADDRESS1: First line for address
  4. ADDRESS2: Second line for address
  5. ADDRESS3: Third line for address
  6. ADDRESS4: Fourth line for address
  7. CITY: City
  8. POSTAL_CODE: Postal Code
  9. STATE: State
10. ADDRESS_KEY: Derived key that facilitates fuzzy searches

HZ_CUST_ACCOUNTS:

The HZ_CUST_ACCOUNTS table stores information about customer accounts , or business relationships that the deploying company establishes with a party of type Organization or Person. This table focuses on business relationships and how transactions are conducted in the relationship. Since a party can have multiple customer accounts, this table might contain several records for a single party. For example, an individual person can establish a personal account, family account, and a professional account for a consulting practice. The primary key for this table is CUST_ACCOUNT_ID.

Few Important Columns are

  1. CUST_ACCOUNT_ID: Customer account identifier
  2. PARTY_ID: A foreign key to the HZ_PARTY table.
  3. ACCOUNT_NUMBER: Account Number
  4. CUSTOMER_TYPE: Receivables lookup code for the CUSTOMER_TYPE attribute. I for internal customers, R for revenue generating external customers.
  6. CUSTOMER_CLASS_CODE: Customer class identifier

HZ_CUST_ACCT_SITES_ALL:

The HZ_CUST_ACCT_SITES_ALL table stores all customer account sites across all operating units. Customer account sites are addresses, for customer accounts, where the deploying company does business with its customers. One customer account can have multiple customer account sites, and customer account sites for one customer account can belong to multiple operating units. The primary key for this table is CUST_ACCT_SITE_ID.

Few Important Columns are

  1. CUST_ACCT_SITE_ID: Customer site identifier
  2. CUST_ACCOUNT_ID: Identifier for a customer account. Foreign key to the HZ_CUST_ACCOUNTS table
  3. PARTY_SITE_ID: Identifier for a party site. Foreign key to the HZ_PARTY_SITES table
  4. BILL_TO_FLAG: Indicates if this is a Bill-To site.
  5. SHIP_TO_FLAG: Indicates if this is a Ship-To site.
  6. MARKET_FLAG: Indicates if this is a Marketing site.

HZ_CUST_SITE_USES_ALL:

The HZ_CUST_SITE_USES_ALL table stores business purposes assigned to customer account sites, for example Bill-To, Ship-To, and Statements. Each customer account site can have one or more purposes. This table is a child of the HZ_CUST_ACCT_SITES_ALL table, with the foreign
key CUST_ACCT_SITE_ID. The HZ_CUST_SITE_USES_ALL table also stores operating unit identifier, though the HZ_CUST_ACCT_SITES_ALL table itself stores the operating unit for customer account sites. The primary key for this table is SITE_USE_ID.

Few Important Columns are

  1. SITE_USE_ID: Site use identifier
  2. CUST_ACCT_SITE_ID: Identifier for the customer account site. Foreign key to the HZ_CUST_ACCT_SITES_ALL table
  3. SITE_USE_CODE: Business purpose assigned to customer site account, such as Bill-To, Market, and Statements.
  4. PRIMARY_FLAG: Indicates if this site is the primary site for this customer account. Y for the primary customer account site. N for other customer account sites.

HZ_CUSTOMER_PROFILES:

The HZ_CUSTOMER_PROFILES table stores information about the credit characteristics of a single customer account or a customer account site or a party. A profile class defined in the
HZ_CUSTOMER_PROFILE_CLASSES table can be used to provide default values for the attributes in this table. The primary key for this table is CUST_ACCOUNT_PROFILE_ID.

Few Important Columns are

  1. CUST_ACCOUNT_PROFILE_ID: Unique identifier of this customer profile
  2. CUST_ACCOUNT_ID: Identifier for the Customer Account. Foreign key to the HZ_CUST_ACCOUNTS table.
  3. STATUS: Indicates whether the profile is active or inactive

HZ_CUST_PROFILE_CLASSES:

The HZ_CUST_PROFILE_CLASSES table stores information about the credit characteristics that are common across a group of customer accounts. The characteristics specified in this table can be used as default characteristics for similar customer accounts. The primary key for this table is PROFILE_CLASS_ID.

HZ_PARTY_RELATIONSHIPS:

The HZ_PARTY_RELATIONSHIPS table stores information about relationships between parties.

Read more »

Oracle Purchasing Module Step by Step in R12

 All the Purchasing related activity information will be declared in Purchasing

            

Procure 2 Pay Cycle:

RequisitionàRFQàQuotationà

Quotation AnalysisàPurchasingàReceivingàInvoice à PaymentàReconciliation

PO-Integration: PO is integrated by GL, AP, I Supplier, Procurement, and Project Accounting 

PO Responsibility

            Step1: Define PO Responsibility

                        Nav: System administratoràSecurityàResponsibilityàDefine

            Step2: Assign PO options to the PO Responsibility

                        Nav: System administratoràProfileàsystem

            Step3: Assign PO Responsibility to User

                        Nav: System administratoràsecurityàuseràdefine

Note: PO is including some of i.e. Options, Supplier, Item, Expenses, and Purchasing.

Options: Options nothing but a Controlling future at the operating unit level.

           

            They are Three Types of Option i.e.

 1. Financial Option

                         2. Purchasing Option

                         3. Receiving Option

1.    Financial Option: These options will be shared by Purchasing, Account table,Internet expenses application 

 Nav: JADE POàSetupàOrganizationàFinancial Option

2.    Purchasing Options: It will be shared by the Purchasing applications

      Nav: JADE POàSetupàOrganizationàPurchasing Option

            3.  Receiving Options: This option will be shared by Inventory, Purchasing and Order

                                           Management

               Nav: JADE POàSetupàOrganizationàReceiving Option

Employee:

            It is used to position of the organization i.e. CEOàDMàPMàPO Clerk.

Step1: Define a Job

           

Nav: JADE HRàWork structureàJobàDescriptionàNew (A)

Step2: Create Employees

           

             Nav: JADE HRàPeopleàEnter and maintain

Step3: Assign Job to be Employee

           

            Nav: JADE HRàPeopleàEnter and maintain

           

            3.1: Assign PO Clerk Jobs to the Employee1

            3.2:  Assign PO Manager to the Employee 2

Step4: Assign Manager to the Clerk

           

                        Nav: JADE HRàPeopleàEnter and maintain

Step5: Create User and assign Employees to the User

           

                        Nav: System administratoràSecurityàUseràDefine

            5.1 PO Clerk User Name

            5.2 PO Manager (new)

Supplier:

Definition: Either Person or Organization who is Supplying Good or Services is called a

                   Supplier.

           

            They are two levels of data in Supplier i.e.

1. Supplier header (Head Office): This Information is Global Specific

2. Supplier Site (Branch Office): This Information is Operating Unit Specific 

Step1: Create a Supplier

            Nav: JADE poàSupplier BaseàSupplier

           

            Step1.1 Create Supplier

           

                        After Organization (Tab), Address Book (T), Contact (T), Business Classification (T), Product and Services (T), Purchasing (T), Receiving (T).

ITEM:

Definition: Item will be defined in either Inventory or Purchasing Application so it is used Inventory Key Flexfield to define the Item, these are seven key flexfield in the inventory applications

Item Category Structure:

Family:           Electricals

Classifiers: Lap tops    Led TVs

Step1: Create Item Category Structure

           

Nav: JADE InvàSetupàFlexfieldsàkeyàSegment

Application: Inventory                   Flexfield Title: Item Category

Add New:       JADE ITEM go to Segment

1. Family        family             Segment1        item categories

2. Class           Class               Segment2        Item Class Category

                       

             (√) Enable Freeze Flexfield DefinitionàCompile (2 times)

Item Category Values

Step1.1: Define Values

            Nav: JADE-InvàSetupàFlexfieldà KeyàValues

                       

Application: Inventory

                        Title:    Item Category

                        Structure: JADE ITEM

                        Segment: Family         goes to find

Add new Values

JADE Electricals           JADE Electricals           JADE Electricals

JADE Furniture             JADE Furniture             JADE Furniture

                       

                                    SAVE

Step 1.2 Class Values

                       

                        Same Navigation

Nav: Go toàviewàfindàsegmentàClassàindependent valueàJADE ElectricalsàFind

Add new values

Laptop             Laptop             Laptop

LED TV          LED TV          LED TV

           

                                    SAVEàExit

Category Codes: Category codes are used to categories the Item

            Step1: Define Category Codes

                       

            Nav: JADE-INVàSetupàItemàCategoryàCategory CodesàNew

JADE ITEM      JADE ELEC LAPTOP             JADE ELEC LAPTOP

JADE ITEM      JADE ELEC LEDTV               JADE ELEC LEDTV  

Category Set: It is used to group the values categories

           

            Step1: Define Category Set

            Nav: JADE INVàSetupàItemsàCategoriesàCategory setsàOrganization (Win)àJADE SOFTWARE ORGàOK

            Category Set (Window)

            Name: JADE Category set

            F Structure: JADE ITEM

            Default Category: JADE ELEC LAPTOP

            (√) Allow Multiple Item Category

            Category

JADE ELEC LED TV

           

            SAVEàClose

Create Item

        Step1: Define Item

                       

                        Nav: JADE INVàItemsàMaster Item

Go to Main (T): Primary: Each

Go to Inventory (T): Enable Inventory Item

Go to Purchasing (T): Enable Purchasing and 01.001.5050.000

Go to Order Management (T): Enable Customer Ordered

Go to Invoice: Enable Invoice and Sales A/C: 01.001.5110.000

                       

                                                SAVE

Note: place curser on ITEM (LAP TOP)àgo to TOOLSàCategoriesàCategory Assignment (Win)

Category set               Control Level             Category

JADE Category set        Master                         JADE ELEC LAPTOP

                        SAVEàCloseàClose

Open PO Periods

Nav: JADE POàSetupàFinancialàAccountingàControl Purchasing Periods

Document Types: It will determine the futures of various Purchasing

                                                Documents.

            Step1: Define Document Type

                                   

                        Nav: JADE POàSetupàPurchasingàDocument Types

Approval Groups: This are used to define the authorized limit for various Job

            Step1: Define Approval Limits

                        Nav: JADE POàSetupàApprovalà Approval Groups

Operating Unit: JADE Software

Name: PO CLERK

Object                                     Type                                        Low value                   High value

Document Type          include                        500000           

Account Range           Include                        500000            01.001.1000.000       Z.ZZ.ZZZZ.ZZ

                         

Nav: JADE POàSetupàApprovalà Approval Groups

Operating Unit: JADE Software

Name: PO MANAGER

Object                                     Type                                        Low value                   High value

Document Type          include                        500000           

Account Range           Include                        500000            01.001.1000.000       Z.ZZ.ZZZZ.ZZ

Approval Assignments:  It is used to Assign Approval goods to the Jobs

            Nav: JADE POàSetupàApprovalàApproval Assignments

            Step1: PO CLERK

           

                        Operating Unit: JADE Software

                        Job:      JADE POCLERK

Note: Add the EIGHT Approval Assignments

Nav: JADE POàSetupàApprovalàApproval Assignments

            Step2 PO MANAGER

           

                        Operating Unit: JADE Software

                        Job:      JADE POMANAGER

Note: Add the EIGHT Approval Assignments

Buyer: A person who is buying goods or services behalf of organization is

                              called a buyer

Define a Buyer i.e. emp1 as buyer

           

                        Nav: JADE POàSetupàPersonalàbuyer

Add BuyeràSave

Define a Buyer i.e. emp2 as buyer

           

                        Nav: JADE POàSetupàPersonalàbuyer

Add BuyeràSave

1.   Requisition: When there is goods are services requirement in Organization

                                             Service is in employee

            These Requisitions contain three levels of information i.e. 1.header 2. Lines

 3. Distribution

           

                        For Example                Serial No:                   Supplier

                                                              

105                                              Sony pvt ltd àHeader

Lap Top                10*10000=100000àLine

                                                                                                                          Distribution

                                                                                                                       

            They two types of Requisition 1. Internal Requisition

                                                             2. Purchase Requisition 

           

1.            Internal Requisition: Internal Requisition will be created by Employee and send to the where house to adjust items internally

2.            Purchase Requisition: It will be created by Employee and send to the Purchasing department to accrue goods from external sources.

Step1: Create Purchase Requisition

           

Nav: JADE POàRequisition

            Operating Unit: JADE Software

            Type: Purchase Requisition

A.    Go to Lines (T) [ check Source, Details, Currency,)

B.     Go to distribution àAccount(T)àenter Amount and AccountàSaveàClose

C.     Come to Requisition(Win)àApproveàEnable Submit for Approval, PrintàOk

Step2: Query the Purchase Requisition to check the Approval status

                        Nav: JADE POàRequisitionàRequisition Summary

           

                        Operating Unit: JADE Software

                        Requisition Num: 1

                                                Find

                        Requisition Summary (Win)

            Number          Description     Approval Status        Create Document

                  1                  Test               Approved                         ------------

2. RFQ (Request For Quotation): RFQ will be created by Buyer only and send to the various Suppliers to obtain Quotation.

            They are three types of Standard RFQ’s

1.      Catalog RFQ

2.      Standard RFQ

3.      Bid RFQ

RFQ will be created in two ways i.e. 1. Manual, 2. Auto Create

Manual RFQ Create

A.            Catalog RFQ: These will be created by regular purpose so these are contains three levels of data i.e. 1. Header 2. Lines 3. Price breaks

Step1: Create Catalog RFQ

                  Nav: JADE POàRFQ QuotationàRFQ

      Operating Unit: JADE Software           Type: Catalog RFQ

      Description: testing                             Close Date:

Come to Item (T)

Num          Type    Item     UOM               Total Payment

  1              goods  Laptop each                   35000

Go to Terms

      Testing and Condition

Price Breaks (T)

Num          UOM

More (T)

     

      Num    Match Approval                      Tolerance                     Exception                   

      1          2Way                                       10                                Warning

     

                                          CloseàSave

                              Go to SuppliersàRFQ Supplier 1

Seq            Supplier           Site

1                Sony                Sony hyd

                                         

                                                      Close

Come to RFQ (Win)

                 

                              Status: Active

                                         

Close the Application

Step2: Print RFQ

            Nav: viewàRequestàSubmit a new requestàselect single requestàok

                        Name: Print RFQ Report (Land Scope)

                                   

                                    Operating Unit: JADE Software

                                                Parameters: all

                                                            From 1 to 1àok

View àRequestàfindàenter

                                                  

Standard RFQ: It is used for items which are buying very occasionally they are three levels of information in Standard RFQ

1.      header

2.      line

3.      Price breaks

     Bid RFQ: It is used to for High value item which are having special shipping details

                        Example: Machinery (Rice Machine) 

                  Three levels of information in Bid RFQ

1        Header

2        Line

3        Shipment

Auto Create RFQ:

            Nav: JADE POàPurchase OrderàAuto create

Quotation: Quotation are received from supplier and entered in the Oracle

                                           PO it contains all items segment details.

                        They are Three Types of Quotations i.e.

1.      Catalog  Quotation

2.      Standard Quotation

3.      Bid Quotation

Quotation Created by Two Ways i.e.

 1. Manual

 2. Auto Create

1.            Manual Creation: This manual used to Catalog Quotation

Step1: Create Catalog Quotation

           

Nav: JADE POàRFQ and QuotationsàQuotations

Operating Unit: JADE Software           Type Catalog

Supplier: Sony                                     Site: Sony Hyd

Go to Item (T)

More (T) àgo for àPrice breaksà More (T)

                                                                        Status: Active

                                                                       

                                                                         Approve

Note: Quotations are created by only Buyers.

  

Purchase Orders: It’s a legal document which will be created by

                    Organization and send to the Supplier to buy goods or services

They are Four Types of Purchase Order i.e.

1.      Standard Purchase Order

2.      Plan Purchase Order

3.      Blanket Purchase Agreement

4.       Contract Purchase Agreement

These are four level of information in purchase order

1.            Header

2.            Lines

3.            Shipment

4.            Distribution

Purchase Order can be create in two ways: 1. Manual 2. Auto create

1.            Manual Creation:

A.            Standard Purchase Order: it’s a legal document to buy goods of service by supplier it will be created when we know the term and conditions goods or services, price, Quantity, Delivery, Schedule, and accounting distribution and also it is one time purchase order.

1. Create Standard Purchase Order

                        Nav: JADE POàPurchase OrderàPurchase Order

Operating Unit: JADE Software                       Type: Standard Purchase Order

Supplier: Sony pvt ltd                                     Site: Sony hyd

Come Lines (T)

Come to Price Breaks (T)  go to shipments(T), go to More (T), Status (T) , Place curser on shipment go to Receiving Controlàgo to distributionàsave

Distribution àcome to More (T), go to ApproveàOK.

2. Plan Purchase Order: It is long time agreement so its agreement between the Org and Supplier to buy goods or services it will be created when we know the terms and conditions goods or services, price, quantity, and distribution, schedule, so later we will create schedule release with the reference of plan purchase order and send to the supplier to obtain goods or services.

3. Blanket Purchase Agreement: it’s Agreement between Org and Supplier to buy goods or services it will be created when we know the terms and condition goods or services and price later blanket retain will be created with reference of blanket purchase agreement and send to the supplier to obtain good or services

4. Contract Purchasing Agreement: it’s long term agreement release a Org and Supplier it will be created when we know the terms and condition later standard purchase order will be created with reference of contract purchase agreement and send to the supplier to obtain goods or services

Receiving: Entering Delivery Information in the system is called a Receiving

                  

                        They are three types of receiving methods

1.      Direct method

2.      Standard Receipt

3.      Inspection

Note: always receiving will be done at inventory Organization

Open Inventory Periods:

                       

                        Nav: JADE INVàA/c ing Close CycleàInventory A/c ing PeriodsàJADE SoftwareàInventory A/c (Win) àchange month status i.e. open

Sub inventory:

           

                        Step1: Define Sub inventory

                                   

                                    Nav: JADE INVàsetupàOrganizationàSub inventoryàSub inventory summary (Win) àOpenàSub Inventory

Name: JADE Sub Inv                            Description: JADE sub inventory

Accounting (T):

                                    01.001.7515.000

                                    01.001.5370.000

                                    01.001.1410.000

                                    01.001.1410.000

            Resource         01.001.1481.000                     Save

On Hand Availability:

           

                        Nav: JADE InvàOn Hand AvailabilityàOn Hand QuantityàQuery Material (W) àFindàMaterial Work Bench

Direct Delivery: it is receipt routing goods will be direct delivery to final destination    

Step1: Create Purchase Order with Receipt Routing Direct Delivery

            Nav: JADE POàPurchase OrderàPurchase Orderà Purchase Order (W)

            PO Receipt: 1àgoes to Shipment, come to receiving controls àenable Receipt Routing is Direct DeliveryàOK

                        Go to Status (T)

Num    status   ordered                        received                       excel                bill

  1                       10                                   0                               0                     0

Close àClose

Step2: Receive the goods

                        Nav: JADE POàReceivingàReceiptsàJADE SoftwareàOK

Step3: Check the receiving transaction status in the remaining transaction summery window

            Nav: JADE POàReceiving àReceiving Transaction Summary

Step4: Check the received Quantity in the purchase order

            Nav: JADE POàPo orderàpo order

Step5: Check the material on hand availability

            Nav: JADE invàon hand availabilityàon hand quantity

Standard receipt: Under this receipt routing first goods will be received at one place and send to the final destination

            Step1: Create the purchase order with receipt routing standard receipt

                        Nav: JADE POàPurchase orderàPO Order

            Step2: Received the goods at one place

                        Nav: JADE POàReceiving à Receipts àJADE software orgàok

Step3: Check the receiving transaction status in the receiving transaction summary window

            Nav: JADE POàReceivingàreceiving transaction summary

Step4: Delivery goods the final destination

            Nav: JADE POàReceivingà receiving transaction

Step5: Check the receiving transaction status in the receiving transaction summary window

            Nav: JADE POàReceivingàreceiving transaction window

Inspection: Under this method first goods will be received at one place then inception came then inspection people inspection then goods after that the final destination.

            Step1: set a QA Inspection people option name at responsibility level

                        Nav: System administratorà SystemàPeople

            Step2: Create the purchase order with receipt routing standard receipt

                        Nav: JADE POàPurchase orderàPO Order

            Step3: Received the goods at one place

                        Nav: JADE POàReceiving à Receipts àJADE software orgàok

Step4: Check the receiving transaction status in the receiving transaction summary window

            Nav: JADE POàReceiving à Receipts àJADE software orgàok

Step5: Inspects the goods

            Nav: JADE POàReceivingàreceiving transaction

Step6: Check the receiving transaction status in the receiving transaction summary window

            Nav: JADE POàReceivingàreceiving transaction summary

Step7: Delivery the goods to the final destination

            Nav: JADE POàReceivingàReceiving Transaction

Step8: Check the receiving transaction status in the receiving transaction summary window

            Nav: JADE POàReceiving à Receiving Transaction summary

Returns: It is used to record the returns goods information

            Step1: Check the material on hand availability

                        Nav: JADE invàon hand availabilityàon hand quantityà JADE soft org

            Step2: Return the goods to supplier

                        Nav: JADE POàReceiving àReturnsàJADE Soft org

            Step3: check the on hand availability

                        Nav: JADE invàon hand availabilityàon hand quantityà JADE soft org  

Read more »