How to Diagnose Issues Related to the Drop Shipment Process and the

Interface Between Order Management and Purchasing ? (Doc ID To

Bottom
566616.1)
Modifie Typ
d: 31-Jul-2013 e: TROUBLESHOOTING

In this Document
Purpose
Troubleshooting Steps
TEST CASE
DOCUMENTATION
SETUP
1- Inventory Setup
2- OM Setup
3- PO Setup
DIAGNOSTICS
PROCESSING OVERVIEW
USED ACTIVITIES
THE DATAFLOW OF DROP SHIPMENT ORDERS:

Drop Ship Flow - USED TABLES

TRACING
FAQ
How to resubmit the errored Drop Ship Sales Order Lines after fixing the errors?.
HOW TO link from SO to PO in a drop ship?
References

APPLIES TO:
Oracle Purchasing - Version 11.5.10 to 12.1 [Release 11.5 to 12.1]
Oracle Order Management - Version 11.5.10.0 to 12.1 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
EXECUTABLE:POCIRM - Requisition Import
EXECUTABLE:CTODSREQ - AutoCreate DropShip Requisitions

PURPOSE
This document is intended to help understand what is the Drop Shipment Process and how to
investigate and analyze issues encountered when using the Drop Shipment functionality.
TROUBLESHOOTING STEPS
INTRODUCTION
Oracle Order Entry and Oracle Purchasing integrate to provide drop shipments. Drop shipments
are orders for items that your supplier ships directly to the customer either because you don't
stock or currently have the items in inventory, or because it's more cost-effective for the supplier
to ship the item to the customer directly.
Drop shipments are created as sales orders in Order Entry. The Purchase Release concurrent
program in Order Entry creates rows in the Requisition Import tables in Purchasing. Then
Purchasing's Requisition Import process creates the requisitions. Drop shipments are marked
with the Source Type of External in Order Entry and Supplier in Purchasing.
When the drop shipment has been sent to the customer, the supplier can confirm the shipment
through a phone call, an invoice, or an Electronic Data Interchange (EDI) document, such as an
Advance Shipment Notice (ASN).
When you receive confirmation of a drop shipment, enter the shipment as a receipt, even though
you have not received the item physically (because your customer has received it directly). If
your supplier sends only an invoice, you need to enter a passive receipt. This creates inbound and
outbound material transactions in your system for accounting purposes.
Drop shipment is the process by which an organization takes orders from their customer and gets
it fulfilled by a 3rd party. The selling organization places a purchase order to the 3rd party
(supplier) who ships the ordered products to the end customer directly.

There are three Dropshipments types:

Full Dropshipment - Seller sends Full Qty .
Partial Dropshipment - Only a Part Qty is Shipped, PO is Created to against the Remaining Qty.
Normal Dropshipment - From Inventory it sends the Goods (External Source) .

Following are the benefits of using drop shipping :

No inventory is required.
Reduced order fulfillment processing costs.
Reduced flow times.
Elimination of losses on non-sellable goods.
Elimination of packing and shipping costs.
Reduced inventory space requirements.
Reduced shipping time to your customer.
Enables you to offer a variety of products to your customers
When processing drop shipments for orders, you can: Optionally receive and electronically
process Advanced Shipping Notices (ASN).
Automatically perform logical receipts upon notification of shipment.
Perform Drop Ship for both make and buy items, and automatically default the source type of
External for order lines which need to be drop shipped.

TEST CASE
It is very important to understand as much about a problem as possible, in order to effectively
assist in diagnosing the cause and solution. Hence the following information should be validated
to help confirm the extent and background to the issue and demonstration of how the problem is
encountered.
Does the problem occur while creating the Sales Order? (Is the source type at the line level
defined as external? )
Does the problem occur while running the Workflow Background Processor after booking the
SO (The workflow is unable to pick up the sales order line and insert a requisition into the
PO_REQUISITIONS_INTERFACE_ALL )?
Does the problem occur while running the Requisition Import (requisitions inserted into the
interface tables can not be created)?.
Does the problem occur due to customcode, custom triggers..?
If sourcing is a problem, Is the sourcing happening when manually create a requisition for the
Item?
Does the problem occur while using the autocreate functionality to create the PO's?
Does the problem occur due to 'PO Create Document' workflow ?
Does the problem occur while creating the receipt?
Does the problem occur while running the Invoicing workflow activity?
Is the Problem for only one created SO? or for all ?
Is the Problem specific for only one employee or for all?
Is the problem specific for only one item or for all?
The following presentation will help to understand the steps you have to follow to complete
dropshipment cycle.

DOCUMENTATION
-Oracle Purchasing Users Guide. Purchase Orders (Ch4) . Drop Shipments (11i, R12 )
-Oracle Order Management Users Guide. Order Processing (ch3). Drop Shipment Processing
(11i, R12)
MetaLink:
Document 393688.1 : How To Cancel a Drop Ship Order Line
Document 272154.1 : FAQ: Sales Order Processing within Inventory / Drop Ship Transactions
Hungup In Transaction Open Interface
Document 829165.1 : How is drop_ship_flag implemented in release 11.5.10
Document 286996.1 : How to Automatically Generate Receipts for Drop Shipments with
Advanced Shipment Notices (ASN's)
Document 133464.1 : HTMOMSE Sales Order Diagnostic Script The purpose of this script is to
collect information related to a sales order, its shipment lines and workflow status
Document 463673.1 : R12.0.[3-4] : Oracle Order Management Sales Order Setup Test This test
gives a comprehensive analysis of transaction data for a sales order in Order Managementt
Document 463574.1 : R12.0.[3-4] : Inventory Transaction Diagnostic Scripts Transaction Data
Test This test case provides the details of the material transactions depending on the user selected
parameters
Document 463602.1 : R12.0.[3-4] : Inventory Item Data Collection Setup Test This test case
provides the item information for a particular item
Document 463636.1 : R12.0.[3-4] : Inventory Purchase Orders Data Collection Test This
diagnostic test provides details of a Purchase Order and transactions done against the purchase
order
See Also
Drop Shipments (Order Entry/Shipping)
Drop-Ship Order Flow (Order Entry/Shipping)
Drop-Ship Return Flow
Purchase Release (Order Entry/Shipping)
Advanced Shipment Notices (ASNs)
Entering Receipt Header Information
Entering Receipt Lines

SETUP
You need to associate drop shipments with a receiving location. (See: Associating Ship-to and
Receiving Locations).
Drop shipments support a Destination Type of Expense or Inventory only.
You can handle returns of drop shipments using standard Order Entry/Shipping or Purchasing
functionality. There are different ways you may want to handle returns depending on whether the
customer returned the item to you or directly to the supplier.
Note: You should not drop-ship internal sales orders.
You have to consider the following setup:
1- Inventory Setup
Inventory Setup : (Define and Maintain The Item)
The drop ship inventory organization, item and subinventory must be setup prior to creating any
drop ship orders. All drop ship subinventory must have the Reservable box checked.
Below are list of the required item attributes for a drop ship item. All of these attributes MUST
be enabled unless otherwise specified.
Inventory Attributes: Inventory Item , Stockable, Transactable, Reservable
Purchasing Attributes: Purchased, Purchaseable
Costing Attributes: Costing Enabled this should only be checked for items that are cost
enabled, Inventory Asset Value this should only be checked for asset items (non-expense
items)
Receiving Attributes: Receipt Routing set to Direct this is not required, but preferred since it
makes receiving process one step versus two or three
Order Management Attributes: Customer Ordered, Customer Orders Enabled, OE Transactable
As a Troubleshooting tips on creating a drop ship item and subinventory:
Make sure the subinventory is Reservable.If the subinventory is not Reservable, the sales order
issue transaction will not be created in MTL_TRANSACTIONS_INTERFACE.
Make sure the item has the above mentioned item attributes in the drop ship organization. If the
above item attributes are not set, problems will arise in various places during the drop ship
transaction process.
2- OM Setup
Make sure the sales order line Source Type is External. If the source type is not External,
workflow will not distinguish the line as being a drop shipment and will not insert any data into
the purchasing modules requisitions interface.
For customer, enter internal ship to location.
Customer must have a valid ship-to and bill-to locations.
Make sure that either the schedule ship date or request date is populated.If both of these are null,
the requisition will not be imported into the purchasing modules requisitions interface.
Make sure there are no holds against the line. If there is a hold, the hold must be removed and
then the order can be progressed or the line must be manually purchased release.
Verify in HR, that the employee has an active status and has not been terminated.
For more details..
Note 99888.1: Drop Shipments Setup
Note:99886.1 : Drop Shipments FAQ
Note:99889.1 : Drop Shipments - Troubleshooting
3- PO Setup
Make sure the Import Source parameter list of values contains ORDER ENTRY.
If ORDER ENTRY appears in the Import Source parameter list of values, then it means that the
Workflow Background Processor successfully inserted a requisition into
PO_REQUISITIONS_INTERFACE_ALL. If ORDER ENTRY is not visible in the Import
Source parameter list of values, then no rows were inserted into the table. Review the setup
under Order Management.
User should be setup as a valid PO Buyer.
Make sure the Group By parameter is actually set the user wants the requisitions grouped.
Hence as Points for Implementation Considerations:
Order line attribute: Source Type (need to be external). You can be defaulted from item or order
type
Menu -> Responsibility Order Entry Super User/setup/Orders/Types
Setup an order type using the cycle defined in the previous step (a),an order number source, a
valid standard value rule set.
Item attributes (OM and Purchasing). You need to do the setup for these attributes:
Purchased (PO) Enabled
Purchasable (PO) Enabled
Transactable (INV) Enabled
Stockable (INV) Optional
Reservable (INV) Optional
Inventory Item (INV) Optional
Customer Ordered (OE) Enabled
Customer Orders Enabled (OE) Enabled
Internal Ordered (OE) Disabled
Internal Orders Enabled (OE) Disabled
Shippable (OE) Optional
OE Transactable (OE) Enabled
Setup requisition import parameters
You can also use grouping by Vendor
You can also set the multiple distributions set to No
ASL and/or Sourcing rule relationship need to be setup for Automatic PO creation
Oracle recommends using a logical organization for drop shipment. Exclude this organization for
planning purposes. It can be worked around using non nettable Dropship subinventory

DIAGNOSTICS
1.1- Run the Dropship Order Activity Diagnostic Test to collect data related to a Dropship Order
at various stages of the Dropship process and can be used proactively to solve/prevent issues
related to the dropship process also contain the error and warning messages, followed by
suggested actions, identify possible problem areas.
For11i : Note:224391.1 : Oracle Purchasing Dropship Order Activity Test.
For R12 : Note:463567.1: Dropship Order Activity Diagnostic Test.

1.2-Verify that an order is booked and does not have hold so that the "Purchase Release" program
can pick order lines and create records in the PO_REQUISITIONS_INTERFACE_ALL table.
You can check if the hold is applied on an order or its order line by looking at the "Holds" tab on
"Additional Order Information" screen. Make sure that order line source type is External" on the
"Shipping" tab of order line.
You can also run the following query to know if the order line is eligible for Purchase Release"
SELECT orha.order_number,
orla.line_number,
orla.source_type_code,
d.name hold_name,
d.type_code hold_type,
ho.released_flag,
r.release_reason_code,
orla.drop_ship_flag,
orla.booked_flag,
orla.open_flag,
orla.cancelled_flag
FROM oe_order_headers_all orha,
oe_order_lines_all orla,
oe_order_holds_all ho,
oe_hold_sources_all s,
oe_hold_definitions d,
oe_hold_releases r
WHERE orha.order_number = <order number>
AND orha.header_id = orla.header_id
AND orla.header_id = ho.header_id (+)
AND orla.line_id = ho.line_id(+)
AND ho.hold_source_id = s.hold_source_id (+)
AND s.hold_id = d.hold_id (+)
AND s.hold_release_id = r.hold_release_id(+) ;

2.1- Run the Requisition Import Activity Diagnostic Test (POReqImport115.sql) to validates and
diagnose the issues related to PO Requisition Import, test may display the error and warning
messages, followed by suggested actions, identify possible problem areas.
For 11i: Note 221938.1: Purchasing (PO) Requisition Import (POReqImport115.sql).
For R12: Note 463565.1: Requisition Import Activity Diagnostic Test.

2.2-Following query may be used to find the status of requisition interface record:
The first column DROP_SHIP_SOURCE_ID is the INTERFACE_SOURCE_LINE_ID column
in the PO_REQUISITIONS_INTERFACE_ALL table. Use this query after running the
"Requisition Import" program as it shows the requisition ids as well as purchase order line and
shipment ids once the purchase order is created out of the requisition.
SELECT s.drop_ship_source_id,
 orha.order_number,
orla.line_number||'.'||orla.shipment_number line_number,
orla.ordered_item,
t.name line_type,
orla.line_category_code,
orla.source_type_code,
orla.booked_flag,
orla.flow_status_code,
s.requisition_header_id,
s.requisition_line_id,
s.po_header_id,
s.po_line_id,
s.line_location_id,
s.po_release_id
FROM oe_drop_ship_sources s,
oe_order_lines_all orla,
oe_order_headers_all orha,
oe_transaction_types_tl t
WHERE s.line_id(+) = orla.line_id
AND orla.header_id = orha.header_id
AND orla.line_type_id = t.transaction_type_id
AND orha.order_number = <Order Number>
AND orla.line_number||'.'||orla.shipment_number = <Line Number>

2.3- Following SQL may be used to retrieve the stuck requisitions after running the Requisition
Import process
Select INTERFACE_TRANSACTION_ID, ERROR_MESSAGE, COLUMN_NAME
From PO_INTERFACE_ERRORS
Where INTERFACE_TYPE= 'REQIMPORT';
The ERROR_MESSAGE will contain the a self explanatory message explaining the cause and
the action that should be taken like following error:
"Item is missing, invalid, or not internally orderable for the purchasing organization.
Cause The item is missing, invalid or not internal-order enabled for the purchasing organization.
This is required for a source type of 'INVENTORY'
Action Enter a valid, internal-order-enabled item for the purchasing organization."
3.After running the "Requisition Import" program,it will generate the requisition for the order
line if the DROP_SHIP_SOURCE_ID has some value. You may use this value to view the
record in the PO_REQUISITIONS_INTERFACE_ALL table:
Following query shows status of the requisition interface record if it has been run before. If the
query has no value for "REQUEST_ID" column, hence the "Requisition Import" program has
not been run.
SELECT r.transaction_id,
r.process_flag,
r.request_id,
r.interface_source_code,
r.source_type_code,
r.destination_type_code,
r.quantity,
r.authorization_status,
i.segment1||'.'||i.segment2 item_no,
i.description,
c.segment1||'.'||c.segment2||'.'||c.segment3||'.'||c.segment4||'.'||c.segment5 charge
_account
-- add/remove segment fileds based on accounting structure.
FROM po_requisitions_interface_all r,
mtl_system_items i,
gl_code_combinations c
WHERE r.interface_source_line_id = <Drop Ship Source Id>
AND r.item_id = i.inventory_item_id
AND r.charge_account_id = c.code_combination_id
AND r.destination_organization_id = i.organization_id;
After running the "Requisition Import" program, the requisition number and its status are shown
on the "Drop Ship" tab of "Additional Line Information" form. Once a purchase order is created,
check the purchase order number and its status on the "Drop Ship" tab. also click the
"Purchasing" button on the "Drop Ship" tab to view the purchase order information.

3- Run the Purchasing (PO) Check Employee Setup to check the setup of an employee attached
to a username (the employee who is running the process must be a valid employee).
For 11i: Note 224590.1 : Purchasing (PO) Check Employee Setup .
For R12: Note 463556.1 : Employee Setup Diagnostic Test.

4- From the purchasing responsibility submit the concurrent program. 'Diagnostics: Apps Check'
as following :
4.1 Navigation: Reports/Run
4.2 Submit a Single Request
4.3 Name: Diagnostics: Apps Check
4.4 Parameters: Application 1: Oracle Purchasing , Application 2:Order Entry (you can add more
parameters like (Advanced Supply Chain Planning ,..)
4.5 Submit the request then check the output. The output will let you know the files version you
have, also will enable to detect if there any invalid objects , custom code, custom triggers and
other information. (All invalid objects that may affect the functionality have to be validated, also
all of the custom code or triggers that may affect the functionality must be disabled).

5-Run the HTMomse11i.sql script as in Note 133464.1: "HTMOMSE Sales Order Diagnostic
Script", it will help to collect information related to the sales order, its shipment lines and the
workflow status.

PROCESSING OVERVIEW
USED ACTIVITIES
These are the following activity takes place when you have drop shipment
-Supplier (Warehouse Item, Ship order, Shipment notification) .
-Order Entry (Enter customer, Enter order, Demand order (optional), Cancel order (optional),
Close order).
-Purchasing (Create and send Purchase Order , Enter shipment notification in system ).
-Receivables (Create invoice , Collection of payment , Receipt ).
THE DATAFLOW OF DROP SHIPMENT ORDERS:
Order Entry: Create a Sales Order with a source type of external (at the line level) and a
receiving organization . Here the activity is entering process in oe_order_headers_all
(flow_status_code as entered), oe_order_lines_all .
Sales Order Booking : Book the Sales Order, The order will be booked as DROP SHIP,

Run the Workflow Background Processor that will passes information about eligible drop-ship
order lines to Oracle Purchasing. It will pick up the sales order line and insert a requisition into
the PO_REQUISITIONS_INTERFACE_ALL table .

After Purchase Release has completed successfully, run Requisition Import in Oracle Purchasing
to generate purchase requisitions for the processed order lines. The Requisition Import program
reads the table po_requisitions_interface_all, validates your data, derives or defaults additional
information and writes an error message for every validation that fails into the
po_interface_errors table.The validated data is then inserted into the requisition base tables
po_requisition_headers_all, po_requisition_lines_all, po_requisition_distributions_all. (For that
stuck requisitions it can be retrieved using the following SQL.
SQL>select * from PO_INTERFACE_ERRORS where interface_type= 'REQIMPORT';) . To
run the Requisition Import, navigate as following (Purchasing responsibility=>Request=>Submit
a new request=>Single request =>Requisition import ). Define the import Source as ORDER
ENTRY and way you want requisition to be grouped from the group by, and whether you want to
approve the requisition after importing

After the requisition has been imported, the requisition number can be found (to Find the
Requisition Number/ Po Number from the Sales Order, navigate to Shipping > Actions >
Additional Line Info > Drop Ship to get the requisition / Purchase Order Number).
Then use autocreate PO functionality to create purchase orders.

Perform receipts against these purchase orders. . The inventory organization where the drop ship
receipt should be created is the same as the warehouse for the drop ship line as well as the same
inventory organization listed for the PO line shipment. Ideally, drop ship receipts will have the
same quantity as the quantity listed on the sales order line. When you receive shipment
confirmation, enter a receipt in Oracle Purchasing. For accounting purposes, you must perform
the receipt. This will create the inbound and outbound material transactions in the application.
The receipt transaction will change the Purchase Release orders cycle action to Confirmed.
The Material Transaction and Material Distribution forms will show the receipt and sales order
transactions. The inventory issue to the sales order is performed internally in the application. The
user is not required to manually issue the item to the Sales Order. The application deliverers the
item to the inventorys subinventory using the applications standard functionality. The item is
issued to the sales order by inserting a row into the MTL_TRANSACTIONS_INTERFACE
table. The Material Transaction Interface Manager will then process the row. If the item has not
been issued out of the inventory subinventory, then check the Material Transaction Interface
form.
After the receipt is recorded, run the Receivables Interface and AutoInvoice programs to generate
an invoice to your customer.

After the goods are successfully received, invoices for vendors are created in accounts payables
as in normal purchase orders. (Enter a receipt against PO in receiving subinventory and run
workflow background process). After the receipt is recorded, Invoicing workflow activity
transfers shipped item information including quantities, selling prices, payment terms, and
transaction dates to Oracle Receivables, which processes invoices and accounts for revenue.
Additionally, process credit memos and credits on accounts created from returns can be created
using this process. There are some limitations when attempting to do a Return and Re-Receive.
Utilize Note 563373.1 for further details on these limitations.

Invoices are generated for customers In account receivables. Upon completion of the Invoicing
workflow activity, submit AutoInvoice from Oracle Receivables to import invoice and credit data
into Oracle Receivables, we can use the Concurrent request Pay On Receipt AutoInvoice as
another example of interface between purchasing and Payables to Execute AutoInvoice then run
Auto Invoice Master Program hence if we checked the SO line status it should be closed.

oe_order_lines_all (flow_status_code shipped, open_flag N)

oe_order_lines_all (flow_status_code closed, open_flag N)

Drop Ship Flow - USED TABLES

The following tables contain data related to drop ship orders.
Table Description
PO_LINE_LOCATIONS_ALL Stores document shipment sched
quotations, and RFQs
PO_LINES_ALL Stores purchase document lines
quotations, and RFQs
PO_HEADERS_ALL Stores document headers for pur
and RFQs
PO_DISTRIBUTIONS_ALL Stores purchase order distributio
PO_REQUISITION_HEADERS_ALL Stores requisition headers
PO_REQUISITION_LINES_ALL Stores requisition lines
PO_REQ_DISTRIBUTIONS_ALL This table stores requisition distr
PO_REQUISITIONS_INTERFACE_ALL This is the Requisition Import in
OE_ORDER_LINES_ALL Stores information for all order l
RCV_SHIPMENT_LINES Stores receiving shipment line in
OE_DROP_SHIP_SOURCES Stores relationships between ord
associated oracle purchasing req
Oracle purchasing purchase orde
Drop Ship Flow Related Files

File Command to obtain the file version

OEXOERD.fmb: Order Entry Form
wfengs.pls: Work Flow Engine package spec
wfengb.pls: Work Flow Engine package body
pocirm.oc: Wrapper for ReqImport Concurrent Program
pocis.opc: Functions to validate Req Import Lines
POXBWVRP.fmb: Autocreate Purchase Order
POXPOEPO.fmb: Approve Purchase Order
RCVRCERC.fmb: Purchase Receiving Form
rcvoltm.oc: Transaction manager wrapper for rvtbmctrl()
rvctp.oc: Concurrent program wrapper for rvtmain()
inctcm.ppc: Inventory transaction manager
BaseTransaction.java
QtyManager.java
TrxProcessor.java
TRACING
You may get the Concurrent trace, Form trace or the code Debug Log to figure out the error more
clearly
-The Concurrent trace:
You can enable the sql trace for the concurrent request program that is not passing the data prope
rly to help identifying and figure out the error as following:
strings a $AU_TOP/forms/US/OEXOEORD
strings a $FND_TOP/patch/115/sql/wfengs.p
strings a $FND_TOP/patch/115/sql/wfengb.p
strings a $PO_TOP/lib/pocirm.o | grep i $H
strings a $PO_TOP/lib/pocis.o | grep i $He
strings a $AU_TOP/forms/US/POXBWVRP
strings a $AU_TOP/forms/US/POXPOPOE.
strings a $AU_TOP/forms/US/RCVRCERC.
strings a $PO_TOP/lib/rcvoltm.o | grep i $
strings a $PO_TOP/lib/rvctp.o | grep i $He
Strings a $INV_TOP/lib/inctcm.o | grep i $
execute
fnd_aolj_util.getClassVersionfromDB('oracle.
execute
fnd_aolj_util.getClassVersionfromDB('oracle.
execute
fnd_aolj_util.getClassVersionfromDB('oracle.

1-Use the System Administrator responsibility Nav: Concurrent / Program / Define.

2-Query the process with the short name (REQIMPORT is the Short Name of 'Requisition Impor
t' program, POXPOIV is the Short Name of 'Pay On Receipt AutoInvoice', .. ).
3-Check the box enable trace
4-Then launch the report / program.
5- To retrieve the trace:
5.a. Retrieve the request_id of the program ((M) Views=>Requests=>(B) Find)
5.b. Execute the following sql SELECT oracle_process_id FROM fnd_concurrent_requests WH
ERE request_id = &request_id;
5.c. The trace file should have the name orannnnn.trc where nnnnn is the oracle_process_id retur
ned by the previous SQL
6-You can analyze and provide to support:
- the trace generated (Raw and Tkprofed files)
- the log and output files.
-The Form trace:
Through out your navigation among the application modules you may get a trace file, if the issue
is reproducible you can enable the trace before the failure of the functionality.
To enable the SQL trace navigate to (M) Help > Diagnostics > Trace > Trace with
Binds and Waits, it is the same path to disable the trace, in between you will find a populated
message informing you of the location of the trace file.
Do not run several requisition import simultaneously while retrieving the trace.
-The code Debug Log (FND LOG)
You may need to get the code debug log to analyze the issue further. Here are the detailed steps
to get the fnd log.
1. Run the query:
select max(log_sequence) from fnd_log_messages;
Note this log_seq.

2. Set the following profiles at the user level:

FND: Debug Log Enabled = YES
FND: Debug Log Filename = NULL
FND: Debug Log Level = STATEMENT
FND: Debug Log Module = %

3. Then try to reproduce the issue. Once the issue is reproduced, upload the
output of the following sql in xls format into Metalink.

4. Run the following sql:

Select * from fnd_log_messages
where log_sequence > &log_seq_noted_above
order by log_sequence
5.You can check the message text filed to check if there any error, you can upload the data [fnd
Log Messages] from the above SQL in an xls file to support.

FAQ
How to resubmit the errored Drop Ship Sales Order Lines after fixing the errors?.
If I ran "Req Import" for the second time then it is not considering the old lines (from
apps.po_requisitions_interface_all) which are errored out in the previous runs.

You need to delete those errored records first then you need to run again "Requisition Import"
process to resubmit the lines.
Please review Document 224025.1 to find details which will help you to delete your records
from the Interface Tables.
Q. How is the PO_INTERFACE_ERRORS table purged and does this data have any
dependencies?
A: Oracle Purchasing provides the Requisition Import Exceptions Report, which can be used to
diagnose records in Error in the PO_REQUISITIONS_INTERFACE_ALL table. It also has an
option to purge the Error records in PO_REQUISITIONS_INTERFACE_ALL and the
corresponding Error message in the PO_INTERFACE_ERRORS table: - Responsibility:
Purchasing Super User
- Navigation: Reports/Run, then select Requisition Import Exceptions Report

There is a parameter titled 'Delete Exceptions'. If you select 'Yes', then records in the
PO_REQUISITIONS_INTERFACE_ALL table with a status ERROR' and the corresponding
records in the PO_INTERFACE_ERRORS table will be deleted. You can also restrict the deleted
records by selecting the Batch_id and the Interface Source code. The dependency is between
PO_REQUISITIONS_INTERFACE_ALL (transaction_id) and PO_INTERFACE_ERRORS
(interface_transaction_id)
Document 415756.1 says that "There is a an Enhancement Request 3977875 already opened
requesting A Form To View, Correct And Resubmit Failed Rows From REQIMPORT Process."
HOW TO link from SO to PO in a drop ship?
The link between a Sales Order and a Purchase Order is shown in the following query;
SELECT po_req_number, revision_num, release_num, line_num, vendor_name,status,
buyer_name, creation_date, supplier_item, ordered_uom,quantity, currency_code, unit_price,
location_code, schedule_date,received_uom, quantity_received
FROM oe_drop_ship_links_v
WHERE (line_id = &sales_order_line_ID) -- This is a sales order line ID
/
or alternatively,
CURSOR c_get_buyer_ds (cp_header_id IN NUMBER,cp_line_id IN NUMBER) IS
SELECT poh.segment1 po_number,prh.segment1 req_number,ppf.full_name buyer
FROM oe_drop_ship_sources odss,po_headers poh,po_requisition_headers prh,per_people_f
ppf
WHERE 1=1
AND odss.po_header_id = poh.po_header_id(+)
AND odss.requisition_header_id = prh.requisition_header_id(+)
AND poh.agent_id = ppf.person_id
AND odss.line_id = cp_line_id
AND odss.header_id = cp_header_id
/
The functional link for drop ship links can be found via Order Management >> Order Organiser
Document 286996.1 : How to Automatically Generate Receipts for Drop Shipments with
Advanced Shipment Notices (ASN's)
Document 563373.1 : Return To Supplier Transaction Cannot Be Performed Again For A
Dropship Document 110258.1: OM-DROP: Drop Ship FAQ
Document 99886.1: OM-DROP: Drop Shipments - FAQ
Document 225434.1 : FAQ: Drop Ship Purchase Orders