Internal Sales Order Setup

http://oracleapplicationsfunctional.blogspot.in/2011/08/mandatory-setups-for-internal-sales.htmlInternal Sales Order Setup Flow

Setup Instructions For Internal Sales Orders Across Operating Units [ID 403786.1]________________________________________ Modified 03-NOV-2011 Type HOWTO Status PUBLISHED In this DocumentGoalSolutionReferences________________________________________Applies to:Oracle Purchasing - Version: 11.5.10.2 to 12.0.6 - Release: 11.5 to 12Oracle Order Management - Version: 11.5.6 to 12.0.6 [Release: 11.5 to 12.0]Information in this document applies to any platform.GoalWhat are the mandatory setups for creating internal sales order between operating units?SolutionSetup for creating Internal Sales orders between Operating units

There should be two Operating Unit one is Destination Organization and the other is Source Organization

1) choose responsibility: Human ResourcesPeople> Enter and MaintainEnter Last Name, First Name, Typeclick Assignment:(both Job and Position are Key flex fields)

2) choose responsibility: System AdministratorSecurity > User > Define

3) choose responsibility: Purchasing, Destination OrganizationSetup > Personnel > Buyer > defineIt is required for creating requisition and purchase order in PO.

4) Setup > Purchasing > Document Typechoose internal Requisitionmake sure 'Owner Can Approve' checked.

5) Setup > Approvals > Approval GroupsName = Executivemake sure Document Total and Account Range are defined.

6) Setup > Approvals > Approval Assignmentchoose Position (from step 1)define Document Type = Approve Internal Requisitionsand Approval Group = Executive

7) Setup > Organizations > locationdefine new location (destination location) for Internal requisition use.NameInventory organization = destination organizationShip to location = the same name as location namecheck Ship-to site and Internal Site and Receiving Site

8) Items > Master Itemsa) define Master Itemmake sure ItemPurchased = YesPurchasable = YesStock able = YesInternal Order Enabled = YesInventory item = Yes.List price = Enter the list price

b) click Special > Organization AssignmentMake sure Item assign to destination organization, source organization/warehouse

c) Setups > Inventory > CostsSet inventory cost for that item

d) Setups > Inventory > Cost UpdateRun the "update standard cost" concurrent program

9) choose resp:Order Management, Source organizationSetup > Document > DefineName = InternalApplication = Oracle Order ManagementType = automaticInitial Value =

10) Pricing > Lists > Price ListsPrice List = Corporation

11) Setup > Transaction Type > DefineOrder Type =Transaction Type Code = ORDEROrder Category = OrderOrder Work flow = Order Flow - GenericPrice List =click Assign Line FlowsOrder Type =Line type =Item Type = Standard ItemLine Flow - Generic

12) Setup > Document > AssignApplication = Oracle Order ManagementCategory = InternalSets of Books =Method =Sequence =Need to define customer location associations for both source and destination operating units

13) Choose responsibility: Order Management, Destination organization > Customer > Standardmake sure the internal customer for each destination organization connected with destinationlocation.query on Customer =choose Address .. - destination operating unit customer site address..choose Ship-to...Internal zonelocation :Organization :destination inventory organization(OE requires both a ship-to and an invoice-to for each order, even though internal order linesare not invoiced., you can make the ship-to address both a ship-to and bill-to business purposeand set the Primary flag to Yes.)

14) Choose responsibility: Order Management, Source organization > Customer > Standardmake sure the internal customer for each source organization connected with destinationlocation.query on Customer =choose Address .. - source operating unit customer site address..choose Ship-to...Internal zonelocation :Organization : source inventory organization(OE requires both a ship-to and an invoice-to for each order, even though internal order linesare not invoiced., you can make the ship-to address both a ship-to and bill-to business purposeand set the Primary flag to Yes.)

Setups - OM Customer Association - click details provide the internal organization name

15) choose responsibility: Inventory, Destination organization > On-Hand,Available > On-hand quantitychoose Item = and Sub inventory =make sure there is quantity available in source organization

16) Setup > Organizations > Shipping Networkchoose ... add the following:From = source organization, TO = Destination organization and From = Destination organization,TO = source organizationTran fer Type = In transitFOB = Receipt,Receiving Routing = StandardInternal Order Required = 'Y'.

17) choose responsibility: Purchasing, Source organizationSetup > Organizations > Purchasing Optionschoose Internal Requisition zonedefine Order type = Internal1 and Order Source = Internal

18) choose responsibility: Purchasing, Destination organizationRequisitions > Requisitionscreate an Internal RequisitionItem#=Qty=Destination Type =Organization =Location =Source =Organization =Need By date = created a requisition #approve the requisition.go to Requisition Summary and query out this requisition, make sure it has been approved.

19) choose responsibility: Purchasing, Destination organizationReport > run > run Create Internal Sales Orders

20) choose responsibility: Order Entry, Source organizationOrders, Returns > Import Orders > Order Import Request submit the report.ReferencesNOTE:744481.1 - Internal Sales Order Cycle In Order ManagementRelated

2.

3. A Drop Shipment occurs when a customer order is sourced from and delivered by a supplier.Order Management sends information to the Purchasing Application to create that PO, and then when that PO is received (to indicate shipment from the supplier to your customer), the order line is automatically updated to indicate that it was fulfilled.In this process, the company running Order Management is modeled as the company to whom the end customer places the original order.Drop Shipment - SetupYou need to make sure these are attribute setup Correctly: Item AttributesPurchased :EnabledPurchasable :EnabledTransactable :EnabledStockable :OptionalReservable :OptionalInventory Item :OptionalCustomer Ordered : EnabledCustomer Order Enabled :EnabledInternal Ordered :DisabledOE Transactable :EnabledShippable :Optional And ,your do set up for Order Source Type as ExternalDrop Shipment Your Setup checklist Ensure you have created your Order Management Transaction Types and linked your Transaction Types to order and line workflows that support drop shipments. Ensure the Oracle Workflow Background Engine is running. Ensure all Drop ship locations you will use to perform drop shipments have the Ship To Site and Receiving Site defined. Ensure you have defined the Internal Ship To Locations for your drop shipment customers (Oracle Receivables Standard Customer window, Business Purpose Details Tab). Ensure your standard items have an associated List Price defined within your PO Inventory organization (Oracle Payables Financial Options window, Supplier-Purchasing Tab).Drop Shipment - Process Steps Create a Sales Order with line where the line source is External Book and Schedule the Sales Order Run Requisition Import Process Now the line status will be in Awaiting Receipt Login to the Receiving Organization (Purchasing) who has been setup as an Approver Run Requisition Import Create Purchase Order from the Requisition Approve the PO Receive the full quantity Run Auto Invoice Verify Invoice in Sales OrderCheck the detailshere.Things not to forget in a DropShipment Release 11i/12 does not support Drop Shipment across operating units. Blanket PO's will not used with Drop Shipment , the reason the PO must be created when OM notifies PO that a Drop Ship order has been created. You can't cancelled Drop Shipments once Oracle Purchasing obtains the receipt. Standard Items can be used for Drop Shipment. In 11i, PTO's and ATO's cannot be drop shipped

4. Order Management Drop Shipment, Functional Setup and flow

E-commerce site like ebay, ubid.com and amazon.com which are very common place in advance countries like USA, UK & Singapore where people can sell or buy there product. Have you ever think ,what is similar situation in real world , when the the word drop shipment comes to your mind. a business situation when the retailer or trader has no stock himself, instead giving customer details directly to the seller, and then saler than fills the order and send it to customer directly.How its soundsIn other words,Drop Shipment is a process where the customer places a purchase order on a company and this company instructs its supplier to directly ship the items to the customer.A Drop Shipment occurs when a customer order is sourced from and delivered by a supplier.Order Management sends information to the Purchasing Application to create that PO, and then when that PO is received (to indicate shipment from the supplier to your customer), the order line is automatically updated to indicate that it was fulfilled. In this process, the company running Order Management is modeled as the company to whom the end customer places the original order.We need to make sure these are attribute setup Correctly:Item AttributesPurchased : EnabledPurchasable : EnabledTransactable : EnabledStockable : OptionalReservable : OptionalInventory Item : OptionalCustomer Ordered : EnabledCustomer Order Enabled : EnabledInternal Ordered : DisabledOE Transactable : EnabledShippable : OptionalAnd We do set up for Order Source Type as External.Drop Shipment Setup checklistEnsure you have created your Order Management Transaction Types and linked your Transaction Types to order and line workflows that support drop shipments.Ensure the Oracle Workflow Background Engine is running.Ensure all Drop ship locations you will use to perform drop shipments have the Ship To Site and Receiving Site defined.Ensure you have defined the Internal Ship To Locations for your drop shipment customers (Oracle Receivables Standard Customer window, Business Purpose Details Tab).Ensure your standard items have an associated List Price defined within your PO Inventory organization (Oracle Payables Financial Options window, Supplier-Purchasing Tab).Drop Shipment Process StepsCreate a Sales Order with line where the line source is ExternalBook and Schedule the Sales OrderRun Requisition Import ProcessNow the line status will be in Awaiting ReceiptLogin to the Receiving Organization (Purchasing) who has been setup as an ApproverRun Requisition ImportCreate Purchase Order from the RequisitionApprove the POReceive the full quantityRun Auto InvoiceVerify Invoice in Sales OrderCheck the details here .

Things not to forget in a Drop Shipment

Release 11i/12 does not support Drop Shipment across operating units.Blanket POs will not used with Drop Shipment , the reason the PO must be created when OM notifies PO that a Drop Ship order has been created.You cant cancelled Drop Shipments once Oracle Purchasing obtains the receipt.Standard Items can be used for Drop Shipment.In 11i, PTOs and ATOs cannot be drop shipped

Difference between Internal and External Drop-Ship

In Oracle Context External Drop-Shipping means your Oracle Order Management uses purchase orders to outside suppliers that are automatically generated from sales orders for goods supplied directly from the supplier. The external supplier ships the goods directly to the 3rd Party customer and confirms the shipment through the use of an Advanced Shipment Notice(ASN). Note:Oracle uses this ASN to record a receiving transaction into inventory followed by an immediate logical shipping transaction. From these transactions, conveyance of title takes place and the customer can be invoiced and the suppliers invoice can be processed. where as Internal context Drop-Shipping functions in a similar fashion. The key difference is that no inventory transactions take place on the books of the selling operating unit; transfer of ownership of the goods from shipper to seller to customer with the only physical movement of the goods being out of the shipping organization.

Parallel Pick ReleaseParallel pick release enables multiple pick release processes to run simultaneously as child processes through the Pick Release SRS Parameters window and Release Sales Orders window through the concurrent mode. Parallel pick release is available when pick releasing from the Tools menu on the Shipping Transactions form through the concurrent mode.Parallel pick release enables you to set a default number of child processes by defining the profile option:WSH: Number of Pick Release Child Processes.Ship sets and ship models are processed first during pick release. They are included as part of the child processes.Parallel pick release can be run from the Shipping Transactions form Tools menu. It cannot, however, be executed from the Shipping Transactions form action Launch Pick Release. Parallel pick release does not run when Pick Release is executed Online.

Oracle e-business INTERNAL SALES ORDERS : CREATION TO RECEIPT CYCLEOverviewThis article outlines the functionality and flow of information from Purchasing to Order Management to Shipping and Inventory during the life cycle from an Internal Requisition creation until the Internal Order is received into the destination organization.The process of receiving against Internal Sales Orders involves the following steps:

1.Create an Internally Orderable Item2.Setup Shipping Network3.Create an Internal Requisition4.Run Create Internal Orders concurrent program5.Run Order Import concurrent program6.Pick Release7.Ship Confirm8.Interface Trip Stop9.Receive/Deliver the Shipment for the Internal Order10.Recommended Patch List11.Important Queries/Scripts for Internal Orders

1.0 Create an Internally Orderable ItemNavigate to: Inventory/Items/Master Items.Create an Item.Under Inventory alternative region, check the boxes for Inventory Item, Stockable, Transactable.Under Purchasing alternative region, check the boxes for Purchased, Purchasable.Under Order Management alternative region, check the boxes for Internal Ordered, Internal Orders Enabled, OE Transactable and Shippable.

Enable the item in Source and Destination Organization.

Setup Shipping NetworkThis information describes the relationships and accounting information that exists between a From (Source) Organization and a To (Destination) Organization.Navigate to: Inventory/Setup/Organizations/Shipping NetworkSpecify the From and To Organization.If you specify the Transfer Type as Intransit, then you need to explicitly receive using the Enter Receipts screen. It would be a Standard Receipt.If you specify the Transfer Type as Direct, then goods will get directly shipped into inventory. It would be a Direct Delivery.Make sure to check the Internal Order Required checkbox. ReceiptRouting can be Standard or Direct.

Create an Internal RequisitionNavigate to: Purchasing/Requisitions/Requisitions.Create an Internal Requisition using the item from Step 1.0Specify the quantity.Specify the Source and Destination Organizations. Source is on the right and Destination on the left in the overflow region.Save and Approve the Requisition.

Major Tables ImpactedMajor Columns

po_requisition_headers_allSEGMENT1, REQUISITION_HEADER_ID,TRANSFERRED_TO_OE_FLAG,ORG_ID, AUTHORIZATION_STATUS, CANCEL_FLAG, CLOSED_CODE

po_requisition_lines_allREQUISITION_LINE_ID, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY, SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY, DELIVER_TO_LOCATION_ID, ORG_ID, CANCEL_FLAG, CLOSED_CODE, QUANTITY,QUANTITY_CANCELLED, QUANTITY_DELIVERED, QUANTITY_RECEIVED

TRANSFERRED_TO_OE_FLAG = 'N'AUTHORIZATION_STATUS = 'APPROVED'CANCEL_FLAG 'Y'CLOSED_CODE 'FINALLY CLOSED'

Record is created in MTL_SUPPLY with SUPPLY_TYPE_CODE = 'REQ'.

Run Create Internal Orders concurrent programRun theCreate Internal Ordersconcurrent program. The Create Internal Orders process loads the OM open interface tables using the Order Type you define in the Purchasing Options window.Run the foll. queries to confirm if the interface record got created:SQL1> Select count(*) From oe_headers_iface_all Where orig_sys_document_ref = ;

SQL2> Select count(*) From oe_lines_iface_all Where orig_sys_document_ref = ;


oe_headers_iface_allORDER_NUMBER, HEADER_ID, ORDER_TYPE, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, BOOKED_FLAG, CANCELLED_FLAG, CLOSED_FLAG, STATUS_FLAG,ORIG_SYS_DOCUMENT_REF,DELIVER_TO_ORG_ID, ORG_ID

oe_lines_iface_allLINE_ID, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, SHIPMENT_NUMBER, SHIPPED_QUANTITY, CLOSED_FLAG, DELIVER_TO_ORG_ID, ORG_ID,ORIG_SYS_DOCUMENT_REF

BOOKED_FLAG = 'N'5.0 Run Order ImportNavigate to: Order Management/Orders, Returns/Import Orders.

Run theOrder Importconcurrent program. Order Import creates Internal Sales Orders from the records in the interface tables and determines the order cycle and defaults values based on the order type. Note down the Order Number.

Run the foll. Sql to get the Order Number:SQL1> Select order_number From oe_order_headers_all Where orig_sys_document_ref = ;

Check TRANSFERRED_TO_OE_FLAG = 'Y' in po_requisition_headers_all.


oe_order_headers_allORDER_NUMBER, HEADER_ID, ORDER_TYPE_ID, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, OPEN_FLAG, BOOKED_FLAG, CANCELLED_FLAG, FLOW_STATUS_CODE, DELIVER_TO_ORG_ID,ORIG_SYS_DOCUMENT_REF,ORG_ID

oe_order_lines_allLINE_ID, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, SHIPMENT_NUMBER, SHIPPED_QUANTITY, OPEN_FLAG, BOOKED_FLAG, CANCELLED_FLAG, DELIVER_TO_ORG_ID,ORIG_SYS_DOCUMENT_REF,FLOW_STATUS_CODE,SHIPPING_INTERFACED_FLAG,ORG_ID

BOOKED_FLAG = 'Y'FLOW_STATUS_CODE = 'BOOKED'SHIPPING_INTERFACED_FLAG = 'N'

Running Create Internal Orders and Order Import concurrent programs has no affect on MTL_SUPPLY.

By default theCreate Internal Ordersprocess populates the oe_actions_iface_all table with anOPERATION_CODEof 'BOOK_ORDER', causing the Order to be Booked by theOrder Importprocess. So there is no need to Book the Order. If for whatever reason a hold gets placed on the Order at Booking, then after removing the hold the user would have to peform the actionsProgress Orderto move it to "Awaiting Shipping".6.0 Pick ReleasePick Releasefinds and releases eligible delivery lines that meet the release criteria, and creates move orders. You can pick release by order, trip, stop, container, delivery, warehouse, customer, schedule, or requested dates, shipment priority or combinations of the above criteria. The default release criteria is set up in Shipping Parameters, but you can override the default criteria in the Release Sales Order window at pick release.


wsh_delivery_detailsOE_INTERFACED_FLAG, INV_INTERFACED_FLAG, ORGANIZATION_ID, RELEASED_STATUS, SHIP_FROM_LOCATION_ID, SHIP_TO_LOCATION_ID, SHIPPED_QUANTITY, DELIVERY_DETAIL_ID

Your Order should be Pick Release Eligible.RELEASED_STATUS: 'R' Ready to Release

ORGANIZATION_ID is the Source Organization_id

Navigate to: Order Management/Shipping/Release Sales Orders/ Release Sales Orders

Enter Order Number and complete your entries in the Release Sales Order for Picking window or select a Based On Rule to automatically default the remaining criteria.UnderShippingtab region, make sureAutocreate DeliveryisYes. It will automatically create theDelivery.UnderInventorytab region, make sureAuto Pick ConfirmisYes. It will make the lineStaged/Pick Confirmedafter Pick Release is done successfully.Choose theConcurrentorOnlinebutton.Pick release is launched and pick releases the deliveries and delivery lines for the trip.Save your work.

Your Order should now be Ship Confirm Eligible.RELEASED_STATUS: 'Y' Staged/Pick ConfirmedShip ConfirmShip Confirmis the process of recording that items have shipped. When you Ship Confirm a delivery, Shipping Execution confirms that the delivery lines associated with the delivery have shipped.

Your Order should be Ship Confirm Eligible.RELEASED_STATUS: 'Y' Staged/Pick ConfirmedNavigate to: Order Management/Shipping/TransactionsNavigate to theQuery Managerwindow, and find the Delivery. TheDeliverydisplays in theShipping Transactionswindow. Delivery is a not null column. If Delivery is null, you need to perform the actionAuto-create Deliveries. Delivery is passed asShipment Numberto INV and PO.UnderDeliveryalternative region, selectShip Confirmfrom the Actions menu to display theConfirm Deliverywindow. In theShip Optionsregion, selectShip Allto ship confirm the entire quantity regardless of what was entered in the Shipped Quantity field. In theAuto-create Trip Optionsregion, select the ship method and the actual departure date. The simplest way to ship confirm one or more deliveries is to enable the Set Delivery in-Transit and Close Trip fields.

Set Delivery In-transit:Creates a trip and stops for the delivery. Closes first stop of the delivery, but leaves second stop open. Sets status of delivery to In-transit and initiates Order Management (OM) and Inventory interfaces.Close Trip:Creates a trip and stops for the delivery. Closes trip, all stops, and the delivery.

If you uncheck theDefer Interfacebox and run Ship Confirm, the Inventory Interface is run automatically, and the Order Line status is updated. A request is submitted to runInterface Trip Stopwith modeAllfor the trip stop.If you check theDefer Interfacebox and run Ship Confirm, you need to run theInterface Trip Stop-SRSconcurrent request to update the Inventory and the Order Line status. When the Defer Interface box is checked, a request is not automatically submitted to interface the trip stops.

Choose the Go button to ship confirm and save your work.

Your Order should now be Ship Confirm, Confirmed and Inventory Interface, Interfaced.RELEASED_STATUS: 'C' Ship Confirmed


wsh_delivery_detailsOE_INTERFACED_FLAG, INV_INTERFACED_FLAG, ORGANIZATION_ID, RELEASED_STATUS, SHIP_FROM_LOCATION_ID, SHIP_TO_LOCATION_ID, SHIPPED_QUANTITY, DELIVERY_DETAIL_ID

INV_INTERFACED_FLAG = 'N' Not Interfaced 'Y' Record in MTL_MATERIAL_TRANSACTIONS 'P' Error Condition

OE_INTERFACED_FLAG = 'N' Not Interfaced 'Y' Record in OE_ORDER_LINES_ALL

If theInterface Trip Stopconcurrent request is run, record is created in MTL_SUPPLY with SUPPLY_TYPE_CODE = 'SHIPMENT'.

Ship Confirm inserts records into MTL_TRANSACTIONS_INTERFACE.

Interface Trip Stop

Navigate to: Order Management/Shipping/Interfaces/RunRun the request: Interface Trip Stop SRS.Mode: All All Interfaces Inventory Interface to Inventory OM and DSNO Interface to Order Management and Submit DSNOInventory Interface- SRSis run to update inventory with the ship confirmation information. Inventory balances are decremented and reservations relieved. This program always spawns theOrder Management Interface - SRSprogram. It is very important in the process flow that the Inventory Interface complete before the Order Management Interface to ensure the integrity of the reservation information.

Inventory Interfacepicks records from MTI (MTL_TRANSACTIONS_INTERFACE) and inserts them into MMTT (MTL_MATERIAL_TRANSACTIONS_TEMP). The Inventory Manager then inserts rows into RTI (RCV_TRANSACTIONS_INTERFACE) and calls the Receiving Transaction Processor.

If transfer type isDirect, the Receiving Transaction Processor inserts a record into MMTT and calls the inventory function inltpu() which inserts records into MMT (MTL_MATERIAL_TRANSACTIONS) and MOQ (MTL_ONHAND_QUANTITIES) and completes the delivery of the item into Inventory. The Receiving Transaction Processor also inserts records into RSH (RCV_SHIPMENT_HEADERS), RSL (RCV_SHIPMENT_LINES) and RT (RCV_TRANSACTIONS). It also updates theQUANTITY_RECEIVED and QUANTITY_DELIVERED on PO_REQUISITION_LINES_ALL.Records get deleted from MTL_SUPPLY on delivery into Inventory.


MTL_MATERIAL_TRANSACTIONS_TEMPTRANSACTION_HEADER_ID, TRANSACTION_TEMP_ID, ORGANIZATION_ID, OWNING_ORGANIZATION_ID, SOURCE_CODE, PARENT_LINE_ID, PARENT_TRANSACTION_TEMP_ID, PRIMARY_QUANTITY, RCV_TRANSACTION_ID, SHIPMENT_NUMBER, SHIPPED_QUANTITY, TRANSACTION_QUANTITY, SHIP_TO_LOCATION, REQUISITION_DISTRIBUTION_ID, REQUISITION_LINE_ID

MTL_MATERIAL_TRANSACTIONSORGANIZATION_ID, OWNING_ORGANIZATION_ID, SOURCE_CODE, SOURCE_LINE_ID, PRIMARY_QUANTITY, RCV_TRANSACTION_ID,SHIP_TO_LOCATION_ID, SHIPMENT_NUMBER, TRANSACTION_ID, TRANSACTION_TEMP_ID, TRANSACTION_QUANTITY, TRANSACTION_DATE

MTL_ONHAND_QUANTITIESDATE_RECEIVED, ORGANIZATION_ID, SUBINVENTORY_CODE, TRANSACTION_QUANTITY, UPDATE_TRANSACTION_ID

RCV_SHIPMENT_HEADERSRECEIPT_NUM, SHIPMENT_HEADER_ID, SHIPMENT_NUM,SHIPPED_DATE, RECEIPT_SOURCE_CODE, SHIP_TO_LOCATION_ID,SHIP_TO_ORG_ID, ORGANIZATION_ID

RCV_SHIPMENT_LINESFROM_ORGANIZATION_ID, TO_ORGANIZATION_ID, TO_SUBINVENTORY, SHIP_TO_LOCATION_ID, QUANTITY_RECEIVED, QUANTITY_SHIPPED, SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, REQ_DISTRIBUTION_ID, REQUISITION_LINE_ID, OE_ORDER_HEADER_ID, OE_ORDER_LINE_ID, DELIVER_TO_LOCATION_ID, DESTINATION_TYPE_CODE

RCV_TRANSACTIONSORGANIZATION_ID, SUBINVENTORY, SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, QUANTITY, TRANSACTION_DATE, TRANSACTION_ID, TRANSACTION_TYPE, REQ_DISTRIBUTION_ID, REQUISITION_LINE_ID, OE_ORDER_HEADER_ID, OE_ORDER_LINE_ID, DELIVER_TO_LOCATION_ID, DESTINATION_TYPE_CODE

PO_REQUISITION_LINES_ALLREQUISITION_LINE_ID, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY, SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY, DELIVER_TO_LOCATION_ID, ORG_ID, CANCEL_FLAG, CLOSED_CODE, QUANTITY,QUANTITY_CANCELLED, QUANTITY_DELIVERED, QUANTITY_RECEIVED

If transfer type isIntransit, the Receiving Transaction Processor just creates the shipment by inserting records into RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES. Then you need to explicitly receive from the Enter Receipts screen. Record is also created in MTL_SUPPLY with SUPPLY_TYPE_CODE = 'SHIPMENT'.Order Management Interfaceis run to update Order Management with the ship confirmation information. Order line shipped quantities will be updated..Receive/Deliver the Shipment for the Internal OrderNavigate to: Purchasing/Receiving/Enter Receipts.Query against the Requisition Number or the Shipment Number (Delivery Number on the Shipping Transactions window) and do the Receive/Deliver Transactions.


rcv_shipment_headersRECEIPT_NUM, SHIPMENT_HEADER_ID, SHIPMENT_NUM,SHIPPED_DATE, RECEIPT_SOURCE_CODE, SHIP_TO_LOCATION_ID,SHIP_TO_ORG_ID, ORGANIZATION_ID

rcv_shipment_linesFROM_ORGANIZATION_ID, TO_ORGANIZATION_ID, TO_SUBINVENTORY, SHIP_TO_LOCATION_ID, SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID,QUANTITY_RECEIVED, QUANTITY_SHIPPED, REQ_DISTRIBUTION_ID, REQUISITION_LINE_ID, OE_ORDER_HEADER_ID, OE_ORDER_LINE_ID, DELIVER_TO_LOCATION_ID, DESTINATION_TYPE_CODE

rcv_transactionsORGANIZATION_ID, SUBINVENTORY, SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, QUANTITY, TRANSACTION_DATE, TRANSACTION_ID, TRANSACTION_TYPE, REQ_DISTRIBUTION_ID, REQUISITION_LINE_ID,OE_ORDER_HEADER_ID, OE_ORDER_LINE_ID, DELIVER_TO_LOCATION_ID, DESTINATION_TYPE_CODE

Record is created in MTL_SUPPLY with SUPPLY_TYPE_CODE = 'RECEIVING' on performing a Receive transaction. But records get deleted from MTL_SUPPLY on delivery into Inventory.

Documents

Internal Sales Order Setup