A Techno-functional Perspective

1. Oracle SCM A Techno-functional Perspective

2. Agenda Requisitions Requisitions Open Interfaces Request for Quotation Quotation Blanket Purchase Agreement Release Blanket Purchase Agreement Standard Purchase Orders Purchasing Open Interfaces Purchasing Public APIs Entering Receipts Entering Receiving Transactions Buyers and Approval Limit Supplier Item Catalog

3. • Oracle Product Lifecycle Management . Oracle Advanced product Catalog • Telesales • Trade Management • Incentive Compensation • Order Capture • Partners Online • Depot Repair • Field Service • Install Base • Service Contracts • Service Fulfillment Manager • Spares Management Supply Chain Management Processes Overview Develop Service & Maintain Market • Advanced Supply Chain Planning • Global Order Promising • • Release Management • • Shipping Execution • • Inventory Management • WMS • • Transportation Execution Fulfill Plan Oracle Supply Chain Management Solutions Manufacture Sell & Manage Orders • Cost Management • Configure to Order • Process Manufacturing • Project Manufacturing • Quality • Work in Process Procure • Order management Advanced Pricing • Configurator • iStore • Purchasing • iProcurement

4. A request for quotation (RFQ) is sent to a supplier to request pricing and other information for an item. A quotation is the supplier’s response to that RFQ. Identify requisitions that require supplier quotations and automatically create a RFQ Or create manually and send it thru’ Fax or iSupplier portal. Oracle Solutions for Procure to Pay Cycle Create requisition to procure goods and service with supplier information, delivery instructions, multiple accounting distributions, and notes to buyers, approvers, and receivers. Oracle Purchasing Oracle Purchasing Oracle iProcurement Record supplier quotations from a catalog, telephone conversation, or response from your RFQ. You can also receive quotations electronically and import as Quotations (catalog). Review, analyze, evaluate and approve supplier quotations. Oracle INV Oracle Purchasing Oracle WMS Transfer and deliver goods using the Receiving Transactions window. If you want to perform an inspection transaction, you can open the Inspections window to specify accepted and rejected quantities. Oracle Mobile Supply Chain Application Oracle INV Oracle Purchasing Oracle WMS Create standard purchase order, BPA and blanket releases. Inform your suppliers of your shipment schedule requirements. Record supplier acceptances of your purchase order’s terms and conditions. Provide a quantity and price for each item you are ordering. Alternatively, you should also be able to create your purchase order simply by providing an amount if you are ordering a service that you cannot break down by price and quantity Enter goods and service receipt information against the PO using routing controls viz: Direct delivery, standard receipt or standard receipt with inspection.

5. Oracle Solutions for Procure to Pay Cycle Oracle Purchasing Oracle iProcurement Oracle Purchasing Create Requisition Oracle INV Oracle Purchasing Oracle WMS Oracle Mobile Supply Chain Application Oracle INV Oracle Purchasing

6. Requisition

7. Enter Requisition type, which can be Purchase Requisition or Internal Requisition. The Preparer defaults to ur employee name. Enter a line Type , the default for this field is from the Purchasing Options window. Line types are handled in three classes: amount–based, quantity–based, and outside processing. Enter the Quantity you want to request for the item. You can use the Catalog button to get price breaks for different quantities from catalog quotations or blanket purchase agreements. Enter the Destination Type: Expense – The goods are delivered to the requestor at an expense location. The destination subinventory is not applicable. Inventory – The goods are received into inventory upon delivery. Shop Floor – The goods are delivered to an outside processing operation defined by Work in Process. Enter the name of the Requestor. The default is the requisition preparer. Enter the Organization, delivery location, Subinventory. Enter the Source type. Inventory or the Supplier source type. For the Supplier source type, enter the suggested Supplier, Supplier Site, Contact, and Phone. For the Inventory source type, enter the Organization and Subinventory. Enter the unit Price for the item. If you create a requisition line for an amount based line type, Purchasing sets the price to 1, and you cannot change it. Enter the Need By date-time for the requested items. This is required only for planned items. It should be greater than or equal to the requisition creation date. Save and Approve the document. The status will be changed to approved. Query the requisition and view its details.

9. Requisitions Open Interfaces

10. Insert a single row into PO_REQUISITIONS_INTERFACE_ALL and PO_REQ_ DIST_INTERFACE_ALL table for each requisition line that you import. Then launch Requisition Import program. The Requisition Import program operates in three phases. In the first phase, the program validates your data and derives or defaults additional information. The program generates an error message for every validation that fails and creates a row in the PO_INTERFACE_ERRORS table. In the second phase, the program groups and numbers the validated requisition lines. If you specify a value in the REQ_NUMBER_SEGMENT1 column of the PO_REQUISITIONS_INTERFACE_ALL table, all lines with the same value for this column are grouped together under a requisition header. If you provide a value in the GROUP_CODE column, all lines with the same value in this column are grouped together under a requisition header. In the third phase, the program deletes all the successfully processed rows in the interface tables, and creates a report which lists the number of interface records that were successfully imported and the number that were not imported. Launch the Requisition Import Exceptions Report to view detailed errors. Required Data for PO_REQUISITIONS_INTERFACE_ALL: INTERFACE_SOURCE_CODE to identify the source of your imported requisitions DESTINATION_TYPE_CODE AUTHORIZATION_STATUS PREPARER_ID or PREPARER_NAME QUANTITY CHARGE_ACCOUNT_ID DESTINATION_ORGANIZATION_ID DELIVER_TO_LOCATION_ID DELIVER_TO_REQUESTOR_ID Required columns for PO_REQ_DIST_INTERFACE_ALL: CHARGE_ACCOUNT_ID or charge account segment values DISTRIBUTION_NUMBER DESTINATION_ORGANIZATION_ID DESTINATION_TYPE_CODE INTERFACE_SOURCE_CODE

11. Oracle Solutions for Procure to Pay Cycle Oracle Purchasing Oracle Purchasing Oracle iProcurement Create RFQ (Optional) Oracle INV Oracle Purchasing Oracle WMS Oracle Mobile Supply Chain Application Oracle INV Oracle Purchasing

12. Request for Quotation

13. A request for quotation (RFQ) is sent to a supplier to request pricing and other information for an item. A quotation is the supplier’s response to that RFQ. You send an RFQ to a supplier by fax, making a phone call, or using Oracle iSupplier Portal. A supplier can send a quotation, whether or not in response to an RFQ, is through the Purchasing Documents Open Interface. If you don’t receive quotations electronically from your supplier, you can create the quotation manually using the Quotations window, or copy the quotation from an RFQ. You can create RFQs directly from requisitions using Autocreate Documents window. You need to enter the RFQ type. Then click on create and review the RFQ.

14. RFQ type can be a Catalog: Used for high–volume items or items for which your supplier sends you information regularly. A Catalog quotation or RFQ also includes price breaks at different quantity levels. • Standard: Used for items you’ll need only once or not very often, but not necessarily for a specific, fixed quantity, location, and date. • Bid: Used for a specific, fixed quantity, location, and date. Eg. for a large or expensive equipment or for an item that incurs transportation or other special costs The status of RFQ initially is ‘In Process’. It can be ‘Active’ – Choose this status when the RFQ is complete and you are ready to send it to your suppliers. Only Active RFQs are printed. Printed – The status assigned to the RFQ when you have printed at least one copy of it. You must change the status to Active if you want to reprint the RFQ. Closed – Choose this status to close the RFQ when all suppliers have responded or when you no longer want responses. When you close an RFQ, Purchasing deletes all follow up notifications associated with it. Enter ship-to, bill-to locations and Due Date & Close Date for your suppliers to reply. Enter the Reply/Receive Via code for the method you want the supplier to use to send the quotation viz: mail, telephone, or FAX. All other line level information are copied from the Requisition. Enter an optional Target Price for the RFQ line for negotiation purposes.

15. Enter the suppliers to which this RFQ will be sent. You can also delete suppliers from the RFQ until you have printed the RFQ for them. ‘Include In Next RFQ Printing’ check box is checked when you add a supplier. After you print the RFQ for a supplier, Purchasing deselects this field. If you want to reprint the RFQ for a supplier, you must use this window to select the field again. Select the Add From List button in the RFQ Suppliers window to open the Supplier Lists modal window. Select any supplier list for which you want to copy all suppliers to the RFQ. Enter the Payment terms, Freight terms, Carrier, FOB for the RFQ. Navigate to the RFQ Price Breaks window for Quotation Class of Catalog. Enter the Quantity and unit Price for the RFQ price break line. Leave this field blank if you want the supplier to provide a price independent of the price you want You might want to provide price discounts to indicate to the supplier the prices you would like to receive.

16. Oracle Solutions for Procure to Pay Cycle Oracle Purchasing Oracle iProcurement Oracle Purchasing Oracle INV Oracle Purchasing Oracle WMS Create Quotation (Optional) Oracle Mobile Supply Chain Application Oracle INV Oracle Purchasing

17. Quotation

18. You can Copy quotations directly from RFQs, using Tools->Copy Document. You can also manually create a quotation and reference to the RFQ against which , you are creating this. Enter a unique number for the quotation. In the Type field, enter Standard quotation. You can also manually provide an RFQ number against which , you are creating this. Enter a supplier name and site name. Purchasing uses the default terms, conditions, and currency information for this supplier site in the Quotation Terms and Currency windows. Enter a supplier Contact, Ship–To and Bill–To locations for the quotation. Enter the Supplier Quote number. The Status can be ‘In Process’ – The initial status when you create the quotation. Active – Choose this status when the quotation is complete and you are ready to approve it. Only Active quotations can be approved. Closed – When you enter a quotation, you provide an expiration date for it. Purchasing sends you a notification when the quotation approaches expiration using the warning delay you provided in the quotation header. You can manually close the quotation to acknowledge the notification. Select Approval Required to indicate that approval is required to purchase goods based on this quotation. The Response Date is the date you actually received the quotation. Enter the beginning and ending Effective Dates for the quotation. Purchasing displays your name as the Buyer. You can forward the quotation to another buyer by choosing the name of this buyer from the list of values. The buyer you enter receives all notifications regarding this quotation.

19. Use the Analyze Quotations window to review and approve general or specific quotation information for an item. You need to approve quotation shipments if you want requestors or buyers to be able to reference the shipments on purchase orders or requisitions. Purchasing lets you approve quotation shipments for specific purposes so that you can control the use of your sourcing information. Enter the approval Type which can be ‘All Orders’ ie. all types of purchase orders and Requisitions or ‘ Purchase Agreements’ or ‘Requisitions’ or ‘Standard Purchase Orders’ Enter an active approval reason & name of the Approver

20. Oracle Solutions for Procure to Pay Cycle Oracle Purchasing Oracle iProcurement Oracle Purchasing Oracle INV Oracle Purchasing Oracle WMS Oracle Mobile Supply Chain Application Oracle Purchasing Oracle INV Create Purchase Order

21. Blanket Purchase Agreement

22. Query the Quotation document you want to copy, then choose Copy Document from the Tools menu. Enter the To document type as BPA. Other valid doc types are listed here ...

23. Choose the purchase order Type: Standard Purchase Order, Planned Purchase Order, Blanket Purchase Agreement, Contract Purchase Agreement. For blanket and contract purchase agreements only, enter the total Amount Agreed. This is the amount you have agreed to spend with the supplier. For blanket or contract purchase agreements, check the Global box to indicate that this is a global agreement that can be assigned to other operating units. This checkbox cannot be deselected once you have saved the document. For standard and planned purchase orders and blanket purchase agreements, enter line information for the header. Released – For blanket and contract purchase agreements, Purchasing displays the current total amount Released. The amount released is 0.00 until you create releases against the blanket purchase agreement or reference the contract on a standard purchase order. P–Card – Purchasing displays a procurement card number if the purchase order was created from an iProcurement requisition that used a corporate credit card for the purchase. Only the last four digits are displayed. Procurement cards can be used for items with a Destination Type of Expense, for documents that do not contain a Project number, and for standard purchase orders or releases only. Enter the unit Price for the item. The default price is the list price for the item. In Price reference tab, Enter the latest Market Price for the item. List price is defaulted from Item set up. For planned purchase orders and blanket purchase agreements, check Allow Price Override to indicate that the release price can be greater than the price on the purchase agreement line. If you allow a price override, the release price cannot exceed the Price Limit specified on the line. If you do not allow a price override, Purchasing displays on the release this price from the purchase agreement and prevents you from updating it.

24. Enter the Payment terms, Freight terms, Carrier, FOB for the Purchasing document. If ‘Pay on’ is ‘Receipt’ then it will automatically generate an invoice for this purchase order on receipt. The supplier site should be set up as a Payment on Receipt site in the Supplier Sites window. Select Confirming Order to indicate that the purchase order is a confirming order. A confirming order is an order that you are submitting formally to confirm a verbal order already placed with the supplier. For confirming orders, Purchasing prints the following on the purchase order header: This is a confirming order. Do not duplicate. Select Firm to indicate that the purchase order is firm. Firm your purchase order when you want to indicate to Master Scheduling/MRP or your manufacturing application that it should not reschedule this purchase order shipment. Select Supply Agreement if you want Oracle Supplier Scheduling to communicate releases against this blanket purchase agreement to suppliers. Supplier Scheduling can communicate releases against a blanket purchase agreement only when this option is selected. For planned purchase orders, blanket purchase agreements, and contract purchase agreements, enter the Amount Limit (for the total of all releases) and the Minimum Release Amount that can be released against this purchase order. For blanket and contract purchase agreements, the Amount Limit must be equal to or greater than the Amount Agreed. Enter Effective from and to dates to limit the agreement controls by time. For blanket purchase agreements, enter a Price Update Tolerance only if you are importing price/sales catalog information through the Purchasing Documents Open Interface. The Price Update Tolerance specifies the maximum percentage increase allowed to an item’s price on this blanket purchase agreement when your supplier sends updated price/sales catalog information through the Purchasing Documents Open Interface.

25. Release Blanket Purchase Agreement

26. Query the BPA and press new release. A new blanket release is generated for the BPA. Blanket release 1 for BPA 4515 is created with other header defaults from the BPA. In shipment tab specify the quantity, organization and ship to location, date you want your supplier to deliver the items on a purchase order line, and country of origin for the items. The Country of Origin displayed here defaults from the Approved Supplier List, if it is defined there. If not, it defaults from the supplier site in the Supplier Sites window. Taxable is selected if a tax code is associated with the item. The tax code defaults from the following sources, in the following order: • The Purchase Order Preferences window. If you have specified a preferred tax code in this window, Purchasing defaults this tax code onto the purchase order shipment. • The Tax Defaults region in the Purchasing Options window. If you have specified a tax defaulting hierarchy in this window, Purchasing searches for and defaults the tax code based on that tax defaulting hierarchy. View the status of the document line viz: how many are ordered, received and billed.

27. The destination type determines the final destination of the purchased items. Choose Expense – The goods are delivered to the requestor at an expense location. The destination subinventory is not applicable. Inventory – The goods are received into inventory upon delivery. You can choose this option only if the item is stock enabled in the ship–to organization. Shop Floor – The goods are delivered to an outside processing operation defined by Work in Process. You can choose this option only for outside processing items. Enter the Requestor and Deliver To location for this distribution. If the destination type is Inventory, you can also enter the Subinventory. Enter the Quantity (Amount, if using Oracle Services Procurement) of the purchase order shipment that you want to charge to the Accounting Flexfield. The terms are defaulted from the BPA terms defined before.

28. Standard Purchase Orders

29. Create a Standard Purchase Order using autocreate window. The information appears here as it appears for a blanket release document.

30. Approve the document..

32. Lookup type code can be standard, blanket, quotation, RFQ or contract

33. Purchasing Open Interfaces

34. You can import standard purchase orders, blanket purchase agreements or catalog quotations. Replace or Update Blanket purchase agreements and quotations. Standard purchase orders can only be imported as new documents. You can update your item master and, for blanket purchase agreements and quotations, apply sourcing rules and release generation methods to the imported item. The PO_HEADERS_INTERFACE, PO_LINES_INTERFACE, and PO_ DISTRIBUTIONS_INTERFACE tables are loaded manually Sample columns in Headers_interface table: PROCESS_CODE: Set it to PENDING. After processing it shows as ACCEPTED, REJECTED or NOTIFIED. ACTION: ORIGINAL, REPLACE or UPDATE. • ORIGINAL: Original is one in which all information is new in your system. • REPLACE: Replaces already-created blanket purchase agreements or catalog quotations with new documents containing the new information. First, it looks for documents that have same document type (DOCUMENT_TYPE_CODE), supplier (VENDOR_ID) and supplier document number (VENDOR_DOC_ NUM) with the existing supplier document number (VENDOR_ORDER _NUM) as the replacement document • UPDATE: Updates Unit Price, Item Description, UOM, Price Breaks, Expiration Date DOCUMENT_TYPE_CODE: STANDARD, BLANKET or QUOTATION VENDOR_NAME VENDOR_SITE_CODE Launch the Purchasing Documents Open Interface program Launch Purge Purchasing Documents Open Interface Processed Data program to purge PO interface data. This program removes data that has been accepted or rejected, not data that is still pending. Launch Purchasing Interface Errors Report to view errors. If you want to purge data from the Purchasing Interface Errors table, set the Purge Data field to Yes

35. Purchasing Public APIs

36. The Change Purchase Orders APIs provides the following public procedures: • record_acceptance - Record the acceptance or rejection of a purchase order by a supplier. • update_po - Update a standard purchase order or release changes of quantity, price, and promise date. The API will return a numeric zero if the update was successful and a numeric one if some error was encountered. When an error is encountered the APIs will update the PO_INTERFACE_ERRORS table with the detailed error messages. You can view transactions that failed validation by running the Purchasing Interface Errors Report. declare result number := null; begin -- Do not forget to commit after the result returns 0 and rollback if result returns 1. -- This needs to change as per your application. fnd_global.apps_initialize(1318, 50578, 201); result := PO_CHANGE_API1_S.record_acceptance( 1261, --po num null, -- release num 0, -- revision num ’NEW’, -- action null, -- action date 588, -- employee_id 'N', -- accepted flag 'On Schedule', -- acceptance lookup code 'All valid', -- note 'APITEST', --- interfacetype null, -- transaction_id '1.0'); -- api version result := PO_CHANGE_API1_S.update_po( 1263, -- po num 1, -- release num 1,-- revision 1,-- line num 1, -- shipment num 5,-- qty null, -- price null, -- date ’Y’, -- launch approvals null, -- update source ’APITEST’, -- interface type null, -- txn id ’1.0’); -- version dbms_output.put_line(’result:’||result); EXCEPTION WHEN OTHERS THEN raise; end

37. The PO_Document_Control_PUB.control_document () PL/SQL procedure provides the ability to cancel Purchasing documents directly through an API. DECLARE l_return_status VARCHAR2(1); BEGIN fnd_global.apps_initialize(user_id, resp_id, resp_application_id); --call the Cancel API PO_Document_Control_PUB.control_document ( 1.0, -- p_api_version FND_API.G_TRUE, -- p_init_msg_list FND_API.G_TRUE, -- p_commit l_return_status,-- x_return_status ’PO’, -- p_doc_type ’STANDARD’, -- p_doc_subtype null, -- p_doc_id ’PO123, -- p_doc_num null, -- p_release_id null, -- p_release_num null, -- p_doc_line_id null, -- p_doc_line_num null, -- p_doc_line_loc_id null, -- p_doc_shipment_num ’CANCEL’, -- p_action SYSDATE, -- p_action_date null, -- p_cancel_reason ’N’, -- p_cancel_reqs_flag null, -- p_print_flag null ); -- p_note_to_vendor -- Get any messages returned by the Cancel API FOR i IN 1..FND_MSG_PUB.count_msg LOOP DBMS_OUTPUT.put_line(FND_MSG_PUB.Get(p_msg_index => i, p_encoded => ’F’)); END LOOP; END;

38. Oracle Solutions for Procure to Pay Cycle Oracle Purchasing Oracle iProcurement Oracle Purchasing Oracle INV Oracle Purchasing Oracle WMS Oracle Mobile Supply Chain Application Oracle INV Oracle Purchasing Receive

39. Entering Receipts

40. Receipt routing is defined in Receiving options window and at supplier site level. In the purchase document, the receiving controls window defaults the value , which can be overridden. As per this value the receiving transactions will be done. The various options are Direct Delivery, Standard Receipt, or Inspection Required. For receiving against the PO 4515 release 1, we shall use standard receipt ie. We need to first enter receipt info and then deliver using the receiving transactions.

41. Enter Receipt date, Shipment number, Shipped Date, Packing Slip number, Waybill number, Freight Carrier, Bill of Lading, number of Containers, Received By person, Supplier or Customer ie. for supplier–sourced shipments, this is the supplier & for inventory–sourced shipments, this is the organization. If the field says Customer, this is the customer returning an item. Select the line you want to receive. If you specify blind receiving at the system option level, Purchasing neither performs over–receipt checking nor displays a Quantity To Receive. Enter the Destination Type: Receiving, Expense, Inventory, or Shop Floor. This determines the final destination of the received items. Enter the receiving Location., Requestor. For the Inventory destination type, enter the Subinventory, stock Locator. (when the item and/or the subinventory have locator control enabled) & Country of Origin. Now Receiving transaction processor runs and may take a sec until this receipt is available for receiving.

42. Oracle Solutions for Procure to Pay Cycle Oracle Purchasing Oracle iProcurement Oracle Purchasing Oracle Purchasing Oracle WMS Inspect & Deliver Oracle Mobile Supply Chain Application Oracle Purchasing Oracle INV

43. Entering Receiving Transactions

44. In the Transactions tabbed region, you can view Destination Type, Item number, Revision number, Item Description, Location, Person, Subinventory, and stock Locator. • In the Details tabbed region, you can view Packing Slip number, Supplier Lot number, Reason code, Hazard class, and UN Number. • In the Order Information tabbed region, you can view Oder Type, Order number, Release number, Line number, Shipment number, Supplier or Customer, Quantity Ordered, UOM, and Due Date. • In the Outside Services tabbed region, you can view Job/Schedule, Line, Operation Sequence, and Department. In the Quantity field, enter the positive or negative correction quantity for the current line. For controlled items, you can select the Lot & Serial button to navigate to the Lot Number and Serial Number windows. Select the line for which you want to enter a receiving transaction. If a material shortage exists for the item, a message appears. Displaying shortage messages for certain items is a setup option. From the message, you can view details of where in your organization the demand exists for the item. You can then make the item available with a high priority. Enter the transaction Quantity, Destination Type, Location, Subinventory, stock Locator.

45. Again until Receiving transaction processor runs and completes the delivery action, You can see it in transaction status summary UI as status pending. After it is completed u can’t see this record here. Now check all the transactions in Receiving Transactions summary UI.

46. View the PO release to check the received quantity is reflected or not..

48. Receiving Open Interface

49. Receiving Open Interface is used for processing receipt data & ASNs. TRANSACTION_TYPE: This column indicates the transaction purpose code. It accepts values of ’SHIP’ for a standard shipment (an ASN or ASBN) or ’RECEIVE’ for a standard receipt. TRANSACTION_DATE PROCESSING_STATUS_CODE PROCESSING_MODE_CODE: This column defines how the Receiving Open Interface is to be called. It accepts a value of ’BATCH’ only. You initiate one of these values when you submit the Receiving Transaction Processor program through the Submit Request window. TRANSACTION_STATUS_CODE: This column indicates the status of the transaction record. The Receiving Open Interface provides a value of ’ERROR’ or ’COMPLETED’. QUANTITY: This column indicates the shipment quantity. The value in this column must be a positive number. Load the receipt data into the RCV_HEADERS_INTERFACE and RCV_ TRANSACTIONS_INTERFACE tables. Launch Receiving Open Interface program. The pre-processor selects unprocessed rows in the RCV_HEADERS_ INTERFACE table with a PROCESSING_STATUS_CODE of ’PENDING’ and a VALIDATION_FLAG of ’Y’. Receiving Transaction Processor performs these steps : Populates the RCV_SHIPMENT_HEADERS & RCV_SHIPMENT_LINES. Populates the RCV_TRANSACTIONS table for each row in the RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES table if the column AUTO_TRANSACT_CODE in the RCV_TRANSACTIONS_INTERFACE table contains a value of ’RECEIVE’ or ’DELIVER’. Updates supply for accepted line items in the tables MTL_SUPPLY and RCV_SUPPLY. Calls the Oracle Inventory module for processing ’DELIVER’ transactions. Calls the Oracle General Ledger module for processing financial transactions, such as receipt-based accruals. Updates the corresponding purchase orders with the final received and delivered quantities. Launch Receiving Interface Errors report and for ASBNs, the Purchasing Interface Errors Report to view error details. The Receiving Open Interface does not support:: Serial numbering Separate receive and deliver transactions Corrections Returns Movement statistics Dynamic locators Receiving against Internal Orders Receiving against Inter-Organization transfers Receiving against Drop Ship Orders Receiving against RMAs Required for RCV_HEADERS_INTERFACE table: HEADER_INTERFACE_ID: Purchasing provides a unique-sequence generator to generate a unique identifier for this column. GROUP_ID: Purchasing provides a group identifier for a set of transactions that should be processed together. PROCESSING_STATUS_CODE: This columns indicates the status of each row in the RCV_HEADERS_INTERFACE table. The Receiving Open Interface selects a row for processing only when the value in this column is ’PENDING’. RECEIPT_SOURCE_CODE: This column indicates the source of the shipment. It tells the Receiving Open Interface whether the shipment is from an external supplier or an internal organization. Currently, this column can accept a value only of ’VENDOR’. TRANSACTION_TYPE: This column indicates the transaction purpose code for the shipment header. This column accepts a value of ’NEW’ or ’CANCEL’. VENDOR_NAME VALIDATION_FLAG: This column indicates whether to validate a row before processing it. AUTO_TRANSACT_CODE: Perform a standard receipt (’RECEIVE’) or direct receipt (’DELIVER’) SHIPMENT_NUM: This column indicates the shipment number from the supplier Required for RCV_TRANSACTIONS_INTERFACE: INTERFACE_TRANSACTION_ID: Purchasing provides a unique-sequence generator to generate a unique identifier for the receiving transaction line. GROUP_ID:

50. Buyers and Approval Limit