Académique Documents
Professionnel Documents
Culture Documents
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
FAQ: Troubleshooting Stuck Pick Release and Shipping Transactions [ID 863761.1]
Modified: Apr 1, 2013
Type: TROUBLESHOOTING
Status: PUBLISHED
Priority: 2
In this Document
Purpose
Troubleshooting Steps
1. OVERVIEW
2. PICK RELEASE ISSUES
2.1. Pick Release Completes With Insufficient Available Quantity error
2.1.1. Sufficient on-hand quantity exists, but there is no quantity to reserve or transact
2.1.2 No subinventory picking order is defined, and no subinventory is specified on the order lines or on the Pick Release form, inventory tab, pick from
subinventory field
2.1.3 No default stage subinventory
2.1.4. Item is Locator Controlled, no locator specified during pick release, and no default locator exists
2.1.5. No open period exists for pick release
2.1.6. Improper set-up of the Sales Order Key Flexfield in Inventory
2.1.7. Partial shipment did not occur, because order line or lines are in a ship set
2.1.8. An invalid subinventory was specified on the sales order line
2.1.9. In the Pick Release form, a subinventory was defined in the Pick From subinventory field
2.1.10. There may be an issue in Inventory Allocations
2.2. Pick Release "Succeeds" but no order lines are pick released
2.2.1. Subinventory specified as Release Criteria
2.2.2. Specified date ranges exclude the order being picked
2.2.3. Delivery detail has already been assigned to a delivery
2.2.4. Pick Release using a Pick Release rule picks nothing, same criteria specified without the pick release rule succeeds
3. SHIP CONFIRM ISSUES
3.1 Ship Confirm errors with 'The action cannot be performed because the selected records could not be locked. ' This may also happen when attempting to
auto-create a delivery for a delivery detail.
3.2 Interface Trip Stop problems
1 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
Applies to:
Oracle Shipping Execution - Version 11.5.10.0 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
Pick Release, Ship Confirm, Interface Trip Stops, Shipping Transactions Form
Purpose
2 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
To provide assistance and guidance in the resolution of some common Shipping transactions like Pick Release and Interface Trip Stops.
Troubleshooting Steps
1. OVERVIEW
The purpose of this note is to provide some guidelines to troubleshooting stuck Shipping transactions. Logically data flows from the Sales Order object in Order
Management to the Shipping tables, like Deliveries and Delivery Details, then to the Inventory tables where the transactions are recorded, like Move Orders and
Material Transactions. This note will help determine where the process failed and how to troubleshoot the issues from a Shipping perspective.
This is a living document. If there are other issues you encounter which prevent progression of pick release or shipping activities, please add a
comment to this note and describe what situation needs to be addressed. If another note assisted solution of the issue, please include the
other note number in your comment. All suggestions are welcome and will be considered for inclusion in this note.
For troubleshooting stuck transactions from an Inventory perspective please see the following:
Note.837777.1 - FAQ: Troubleshooting Cross-Product Issues Between Shipping and Inventory
3 of 30
5/31/13 4:40 PM
Document Display
4 of 30
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
Solution:
This issue may occur if open reservations still exists for order lines which have been closed or canceled. To resolve this issue, run the Reservation cleanup scripts.
Reference: Note 372170.1 Script I2471362.Sql For Version 11.5.10.2
Run the standard cleanup scripts in the following order:
1. Run script $INV_TOP/sql/INCDPG.sql
2. Check for script i2471362.sql
strings -a $INV_TOP/patch/115/sql/i2471362.sql | grep -i '$Header'
If No such file or directory or version not 115.1
Download from Metalink patch 3170660 and Apply Patch 3170660,
3. Run i2471362.sql script manually
4. Run script $INV_TOP/sql/INCDPG.sql (2nd time)
5. Run Script $MRP_TOP/sql/mrppgupd.sql
6. If Move Orders need Purging, run Move Order Purge which is now a concurrent program. Navigate to INV-> Reports->ALL Move Order Purge
2.1.2 No subinventory picking order is defined, and no subinventory is specified on the order lines or on the Pick Release form, inventory tab,
pick from subinventory field
Solution:
Use either options A, B or C.
A: Specify a subinventory in the "Pick From" region of the Release Orders for Picking form, inventory tab.
If this is done, pick release will always pick from that subinventory. However, if the specified subinventory does not have sufficient quantity, pick release will not
consider any other subinventory for picking.
B: Define a defaulting rule for subinventory.
1. As the Order Management super user, navigate to setup->rules->defaulting.
2. Search for application Order Management and entity Order Line
3. Find the attribute Subinventory
4. Define rules to automatically default a subinventory to orders. (See the Order Management Implementation Guide for more details.)
C: Define subinventory picking order. In the absence of any defaults in shipping parameters and any subinventory specifications on the order or pick release form, pick
release will look first at the subinventories which have priority 1. If no available quantity is found in any of these subinventories, then pick release will look next at all
subinventories having priority 2. Process will continue until all subinventories which have a priority defined have been examined for sufficient on-hand quantity.
5 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
2.1.4. Item is Locator Controlled, no locator specified during pick release, and no default locator exists
If this cause applies, the following additional error messages will appear in Pick Release Debug Log file.
1. [DD-MON-YY HH:MI] Inv_Pick_Release_PVT.Process_Line: Failed to generate allocations. Cannot suggest a destination locator because there is no default
destination locator for this item.
2. INV#INV_NO_DEFAULT_LOC#
Solution:
Set up a default locator for the item in the Inventory Item transaction defaults as follows:
6 of 30
5/31/13 4:40 PM
Document Display
1.
2.
3.
4.
5.
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
Navigate to Inventory -> Setup -> Transactions -> Item Transaction Defaults
Click new, click the Locator tab, click New again
Enter your item,
Enter a type of Move Order Receipts
Enter the Subinventory and the Locator you want to use as the default
Reference Notes
Note 433379.1 WSHFRREL - Pick Releasing Backordering Order Line-Default Locator Not Set
Note.149926.1 Pick Release is Failing for Locator Controlled Items
7 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
7. In the form which follows, reset the date on the move order to a date in an open period.
NOTE: If the order was initially scheduled to ship during a period which is now closed, only options B and C are available. Once a period has been closed, it cannot be
re-opened.
Reference: Note.298432.1 Some Sales Orders Will Not Pick Release
2.1.7. Partial shipment did not occur, because order line or lines are in a ship set
When a single order line is on a ship set and enforce ship sets is specified., the entire quantity must be shipped. System will not split this order line, and will not create
a backorder for the amount of the shortage.
When multiple lines are on the same ship set; if one line has insufficient quantity, none of the other lines will be pick released either. In this case, the pick release
logfile and/or shipping exceptions report will show error message "Item 1234 is on a ship set, and item 2345 on the same ship set has insufficient quantity"
Solution:
Use either options A or B. Use option C to verify no unintended ship set defaulting is occurring.
A. Remove the line with insufficient quantity from the ship set
1. As the Order Management user, navigate to the Sales Orders form.
2. Find the order you are attempting to pick release
3. Go to the Line Items/Shipping Tab.
4. Remove any value in the field ship set
8 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
B. Uncheck the 'Enforce Ship Set' parameter in the Shipping Parameters screen
1. Navigate to shipping->setup->shipping parameters
2. Go to the Pick Release tab
3. Uncheck the box labeled Enforce Ship Sets and Ship Models
C. Review Order Management defaulting rules for entity 'Order Header', attribute 'Line Set'.
1. Navigate to setup->rules->defaulting
2. Select application Order Management, and Entity Order header
3. Find attribute Line Set
4. Click on the Defaulting Rules button
5. Review the Default Sourcing Rules to understand when lines may be defaulted to either a ship set or an arrival set.. Remove any of these sourcing rules which are
not appropriate for your business.
Reference: Note.388183.1 Order lines in Ship Sets Not Picking during Pick Release
2.1.9. In the Pick Release form, a subinventory was defined in the Pick From subinventory field
If insufficient quantity exists in that subinventory, pick release will not consider available quantity in any other subinventory.
Solution:
Do not specify a pick from subinventory:
9 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
Pick release the order with 'Auto Pick Confirm' = NO. This will require transacting a move order in inventory
Pick release will be successful, no 'Insufficient quantity error' will arise. If you still see an Insufficient quantity error, you can rule out this cause.
Find the order in the Shipping Transactions form. The delivery detail will be in status 'Released to Warehouse'. If you see a move order number here, copy it
Switch to the Inventory user
Navigate to Move Order->Transact move order
Find the move order either by entering the move order number noted in step 3, or by searching for the related sales order.
Select resulting move order record, and click on either the Alloocate or View/Update Allocations button.
If an error results when you do this, or if both buttons are disabled (grayed-out), there is an Inventory issue. Please log a new Serivce Request with the
Inventory Support group.
2.2. Pick Release "Succeeds" but no order lines are pick released
Symptoms:
1. This issue usually (but not always) occurs when a single order is being pick released.
2. The pick release debug log file shows message Pick Release completed Successfully
3. Query the order in the Shipping Transactions form, find that the delivery detail lines that should have been pick released are still in status Ready to Release"
Cause:
The user has specified criteria in the "Release Orders for Picking form which are mutually exclusive. A few examples include:
1. Subinventory specified as release criteria, and the order lines do not have a subinventory specified.
2. A specific sales order is entered, and the scheduled ship date or request date ranges are outside the dates specified in the order. For example, order 12345 was
entered and booked with scheduled ship date of Nov 1, 2009; and when pick releasing this order, a scheduled ship date range of Oct 1 2009 through October 31 2009
was specified.
3. Shipping warehouse specified on the Pick Release form is not the same as the shipping warehouse specified on the order.
10 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
Troubleshooting:
A. For release 11.5.10.x, Run the WSHPickLine115.sql
Refer to Note 151808.1 "Oracle Shipping Pick List Selection Activity Test " This note contains diagnostic scripts which can be downloaded and used to identify why
certain delivery details were not selected for pick release. Do the following:
1. In MetaLink, find Note 151808.1 "Oracle Shipping Pick List Selection Activity Test"
2. Under the section "Standalone Download Details", there is a button to download the files associated with this diagnostics test. Click on it.
3. Zip file WSHPKLN.ZIP will be downloaded. Extract all of these files from this zip file to an appropriate directory your PC. All files should be extracted to the
SAME directory
4. Review the readme file. There are two readme files, one formatted as HTML, the other a plain text file, both have the same information.
5. Pick release any order which should be ready to be pick released, using the pick release criteria used when the order failed to release. If the issue arises when a
pick release rule is used, be sure to specify that pick release rule. Submit Pick Release as a concurrent request.
6. When pick release completes, open the Pick Selection List Generation log file, and note the batch number for the request.
7. From a SQL*Plus session:
Execute the script WSHPickLine115.sql.
8. Enter values for all prompts; except that you do not need to enter value for HEADER_ID or LINE_ID as these are optional
9. The script will create an output file named WSHPickLine115__diag.html.(release 11.5.10).
Review error messages in this file. Following is a sample error message:
11 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
12 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
HTMomse Report
You can run the HTMomse11i or HTMomse12 report by doing the following:
1. Download the correct HTMomse script from <> "HTMOMSE Sales Order Diagnostic Script". Oracle Development has recently made some critical enhancements
and modifications to this script, so please download the script from Note 133464.1 even if you have done so in the past.
2. Execute the script from a SQL*Plus session. Please do not use an SQL tool such as Toad or SQL Developer; as unpredictable results may occur
3. When prompted for order number, please enter the order number of the problematic order.
4. When prompted for line_id, please hit the enter key without making any entry. This will cause the report to show all order lines.
5. When prompted for the sections you want shown in the report, please enter 'Y' for the following:
Workflow
Inventory
Purchasing
Receivables
6. When prompted for validations, please enter 'Y'; UNLESS this is a very large order. If the order is very large or the HTMomse script runs for a very long time,
enter 'N' to not perform validations. The report will run faster if validations are not performed.
7. The SQL script will give you the full path for the HTMomse report output. Please upload the report to this SR.
FREQUENT CAUSES:
13 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
2.2.4. Pick Release using a Pick Release rule picks nothing, same criteria specified without the pick release rule succeeds
A pick release rule is used for pick release. Pick release log file reports success, but no orders were picked. However, the same pick release performed from the
Release orders for Picking without using the pick release rule picks all expected order lines.
Cause: An incorrect (old) ship from location value is associated to the warehouse in the Pick Release Rule. The HTMomse report, wsh_delivery_details section, will
show a ship_from_location_id which does not match the ship_from_location_id passed to pick release (as seen in the Pick Release Criteria section of the Pick Release
Debug file).
Enhancement Request 7276387: UPDATE PICK RELEASE RULES WHEN SHIPPING LOCATION IS UPDATED FOR A WAREHOUSE has been entered, requesting that
pick release rule location ids are automatically updated when a warehouse shipping location is updated. If you are affected by this issue, please log a new SR
with Support, requesting that you be added to ER 7276387 as a customer affected by this issue.
Solution:
14 of 30
5/31/13 4:40 PM
Document Display
1.
2.
3.
4.
5.
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
Reference: Note 421998.1 Pick Release Fails When Using Pick Release Rule
A patch which may need to be applied, if patch release levels are not current:
Patch 4113837, SUBINVENTORY FIELD IN WSHFRREL GETTING DEFAULTED FROM PICK FROM, to upgrade file WSHPRREL.pld to version 115.100.11510.4 or higher.
This patch prevents automatic defaulting of the Release Criteria Subinventory field from the Pick From subinventory field. If file WSHPRREL.pld is lower version
115.100.11510.4, this automatic defaulting will occur and will very likely prevent any order lines from being considered for Pick Release.
Reference: Note 305708.1 WSHFRREL: Unable To Pick Release From Release Sales Orders Form after Upgrade to 11.5.10
If you log a Service Request with Oracle Support for your pick release issue, please upload the following files to your SR:
1. HTMomse report for the problematic order (see <>)
2. Pick Release debug log file (see <>)
3. Output file from WSHPickLine115.sql or WSHPickLine12.sql (if pick release succeeds but does not pick any lines)
15 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
16 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
You can reference Note 290432.1 "How to Create a Debug File in Shipping Execution" for additional information related to creating log files for any shipping
execution function.
B. HTMomse report. Please see previous note box describing this report.
C.
1.
2.
3.
Here are a few scenarios you may see with respect to issues in Interface Trip stop, and a query which can be used to find all affected orders.
a) Order line is closed. The delivery dtila is shipped, but is not interfaced to either Order Management and/or Inventory.
select wdd.source_header_number "Order Number",
ol.flow_status_code,
wdd.source_line_id,
wdd.delivery_detail_id,
wnd.delivery_id,
wdd.released_status,
wdd.oe_interfaced_flag,
wdd.inv_interfaced_flag,
wdd.creation_date
from wsh_new_deliveries wnd,
wsh_delivery_assignments wda,
wsh_delivery_details wdd,
oe_order_lines_all ol,
oe_order_headers_all oh
where wnd.delivery_id=wda.delivery_id
and wda.delivery_detail_id = wdd. delivery_detail_id
and wdd.source_header_id = oh.header_id
17 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
b) Model components are interfaced to OM but the Model line is failing OM interface.
select wdd.source_header_number, wdd.source_line_id, wdd.delivery_detail_id
from wsh_delivery_details wdd,oe_order_lines_all ol
where wdd.source_code = 'OE'
and wdd.released_status = 'C'
and trunc(wdd.creation_date) > sysdate-365
and wdd.source_line_id = wdd.top_model_line_id
and wdd.oe_interfaced_flag in ('N','P')
and wdd.source_line_id = ol.line_id
and ol.open_flag = 'N'
and not exists (select 'x'
from wsh_delivery_details wdd1
where wdd.top_model_line_id = wdd1.top_model_line_id
and wdd1.source_code = 'OE'
and wdd1.released_status <> 'D'
and wdd1.oe_interfaced_flag = 'Y'
and wdd1.released_status = 'C'
and wdd1.source_line_id <> wdd.top_model_line_id)
order by 1;
If you are running release 11.5.9, please apply to reseolve this issue
c) Trip Stop/delivery do not show up in ITS LOV but some of the details are not OM/INV interfaced.
select distinct wdd.source_header_number, wts.stop_id, wts.trip_id
from wsh_delivery_details wdd,wsh_delivery_assignments wda,wsh_new_deliveries wnd, wsh_delivery_legs wdl,wsh_trip_stops wts
18 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
d) Interface trip Stops program errors out with "for this transaction row the serial records are missing".
select wdd.source_header_number , wdd.delivery_detail_id, wdd.shipped_quantity,
wdd.transaction_temp_id, msi.serial_number_control_code
from wsh_delivery_details wdd, mtl_system_items msi
where wdd.released_status = 'C'
and wdd.source_code = 'OE'
and wdd.oe_interfaced_flag = 'Y'
and wdd.inv_interfaced_flag in ('N','P')
and wdd.inventory_item_id = msi.inventory_item_id
and wdd.organization_id = msi.organization_id
and wdd.transaction_temp_id is null
and exists (
select 'x'
from wsh_serial_numbers wsn
where wsn.delivery_detail_id = wdd.delivery_detail_id );
The following are a few of the errors you might see in an Interface Trip Stop debug log file. If any of these errors are observed and you cannot
resolve the issue using these notes, please log a new SR with Shipping Execution Support and provide the documentation requested in the
previous note box
19 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
Workflow should NEVER be forced. Forcing workflow ALWAYS results in data corruption
Solution: Run the Retry Workflow Activities in Error concurrent request.
Reference: Note.452832.1 Interface Trip Stop Errors w/ORA-20002 Activity Instance 'Ship_line' Is Not A Notified Activity For Item 'Oeol/xxxxxx':
IMPORTANT: If issue still exists, log a new SR with Shipping Execution product support, and include all of the documentation requested in section 3.2 above.
3.3.1 As per note 185804.1, this may also be caused because the staging subinventory is not reservable. If the following errors occur in the
Interface Trip Stop log file:
FND_AS_UNEXPECTED_ERROR (PKG_NAME=OE_Delayed_Requests_PVT)
(PROCEDURE_NAME=Process_Request_Pvt) (ERROR_TEXT=ORA-20002: 3133: Activity
instance 'SHIP_LINE' is not a notified activity for item 'OEOL/'.),
20 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
First, review the HTMomse report. You should see a stuck record in MTL_TRANSACTIONS_INTERFACE, which should have a more useful error message. If not, then
check for the Activity Instance ship_line error in the debug log file. If not, check that all debug profiles were set. The following profile options need to be set in order
to obtain a detailed log file.
OM: Debug Level - 5
INV: Debug Level - 10
WSH: Debug Enabled - Yes
WSH: Debug Level - Statement
On the Interface Trip Stop parameter, ensure that the Debug Level is set to '1'.
Note: if the 'No delivery detail' message occurs in the ITS log file and there are stuck transactions in mtl_transactions_interface with no error messages, doing
the following may resolve your issue:
1. As the Inventory user on your PRODUCTION instance, navigate to the Transactions Open Interface
2. Find transactions associated with the problematic sales order. (Do NOT search for any specific status)
3. Select all of these transactions, then click inside the Submit box. Save your changes
4. Re-run Interface Trip Stop for the affected delivery or trip stop, after setting the debug profiles as specified in <5. If Interface trip stop still completes with
error, create a new SR with Oracle Support and upload the following files to the new SR:
5.1 HTMomse reports for all of the problematic orders (See <
5.2 The Interface Trip Stop debug log file
5.3 A diagnostic apps check report for productions: Order Management, Shipping Execution, and Inventory Management.
3.5. Inventory Interface could not process some of the lines in the batch as they are in error status
Please query the lines using the Inventory Interface UI to correct the errors.
(preceding messages identify a batch id, but there is no clue as to what delivery details, deliveries, trip stops, or whatever, may be failing).
Need resolution: Need to go into pending transactions form or transaction open interface in Inventory, and resubmit records for processing. If these records don't
process, need a datafix from Inventory.
3.6. Interface Trip Stop Fails With Error in Routine WSH_INTERFACE.PROCESS_DETAILS, Oracle Error - 1 User-Defined Exception
21 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
3.7. Your Change Invalidates the Customer Item Number on the Line
Because the Customer Cross Reference Item was not active, this causes the Interface Trip Stop program to complete with the following error messages:
"Error msg: Your change invalidates the Customer Item Number on the Line.
Process Order failed for order header_id"
Solution:
Perform the following steps to verify whether the Customer Item is active.
From the HTMomse11i.sql output, look for the line that did not get processed by the Order Management Interface and Inventory Interface programs. Note the item
that's assigned to the line.
From the Inventory Super User responsibility, navigate to Items->Customer Items->Customer Items. Query the item that's assigned to the problematic line that's
found on the HTMomse11i.sql output. Verify that the Activate checkbox is checked for this item.
Next, click on Cross References and verify that the Activate checkbox is checked for the cross referenced item as well. After activating the item and the cross
referenced item, resubmit the Interface Trip Stop program which should then complete successfully.
Reference: Note 343201.1 "Your change invalidates the Customer Item Number on the Line".
3.9. Interface Trip Stop Completes Successfully But Delivery Detail Status Update Is Delayed
Delivery Detail status takes up to 2 hours before it is updated to Y after ITS completes.
Reason: "WSH: Defer Inventory Process Online" was set to Y (yes). This means that the inventory transaction manager will perform the interface to Inventory
whenever that background process runs.
Set this profile to N (no) if the INV Interfaced flag should be updated immediately upon completion of ITS.
Reference: Note 334052.1 "Interface Trip Stop Completes Successfully But Delivery Detail Status Update Is Delayed"
22 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
Solution:
1. As the Inventory User, navigate to Transactions->Transactions Open Interface
2. Search for the erred record
3. Update the transaction date to a date with the current accounting period
4. As the Order Management user, ship confirm the order with interfaces not deferred; or, ship confirm the order with interfaces deferred and then run Interface Trip
Stop for the associated delivery or trip stop.
23 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
These errors frequently appear as warnings when deliveries are ship confirmed. None of these errors actually prevent ship confirm or have any impact on
24 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
subsequent processes such as Interface Trip Stop. However, the documents in the ship confirm document set will not be printed.
4.1 Error at Ship Confirm: "The document category has no valid sequence"
When attempting to ship confirm deliveries, the following error occurs in the ship confirmation screen. "The document category has no valid sequence assigned."
Solution:
To implement the solution, please execute the following steps:
1. Responsibility: Order Management super user
2. Navigate to setup->documents->categories
Note: if you used the navigation path shipping->setup->documents->document categories, the Code (category_code) will not be displayed.
25 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
5. SHIPPING EXCEPTIONS
Shipping exceptions are valid business rule violations.
Some may prevent further processing of the delivery or detail until some manual action is taken.
May be seeded or custom created.
Look out for exception status and severity.
Customers must determine how to handle exceptions as these are business decisions.
Viewing Exceptions
If Shipping Transactions form shows Exception box checked then go to: Tools > Resolve Exceptions
26 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
In View Exceptions form look out for Exception Behavior and Status
27 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
AND (security_group_id = 0)
ORDER BY lookup_code;
/* query to find exception_status lookup values */
SELECT lookup_code, meaning, description, enabled_flag
FROM fnd_lookup_values_vl
WHERE (NVL ('', territory_code) = territory_code
OR territory_code IS NULL)
AND lookup_type = 'EXCEPTION_STATUS'
AND (lookup_type LIKE 'EXCEPTION_STATUS')
AND (view_application_id = 665)
AND (security_group_id = 0)
ORDER BY lookup_code;
6. WORKFLOW CONSIDERATIONS
7. DATA ISSUES
9. RESOURCES
9.1. Diagnostics
Sales Order Diagnostic:
Note 133464.1 - HTMOMSE Sales Order Diagnostic Script
Item Data Collection:
Note 223702.1 - Inventory Item Setup Data Collection Tool
Note 398723.1 - Oracle Inventory Item Data Collection Data Collection Test
Diagnostic Apps Check:
Note 156860.1 - OMCHECK.SQL Oracle Order Management Diagnostic Tool
Note 276207.1 - Diagnostics : Apps Check
Debugging COGS issues
Note.159998.1 - Debugging Cost of Goods Sold Account (cogs_11i.sql)
28 of 30
5/31/13 4:40 PM
Document Display
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
418492.1
262979.1
430528.1
420748.1
How to Process Standard Sales Orders in Order Management for Application Release 11.5.10
Unprocessed Shipping Transactions Troubleshooting Techniques
How To Use the HTMomse11i Output To Resolve Pending Sales and Move Order Transactions
Retry Activities in Error Concurrent Request to resolve OM Workflow errors.
10 Training
Understanding basic shipping to inventory workflows from pick release to ship confirm to interfaces.
Troubleshooting Stuck Shipping Transactions
Click here for Shipping Training Presentation:
References
NOTE:148651.1 - INV DEBUG: How to get Debug Information for Inventory Material Transactions
NOTE:452832.1 - Interface Trip Stop Error: ORA-20002: Activity Instance 'Ship_line' Is Not A Notified Activity For Item 'OEOL/xxxxxx'
NOTE:463641.1 - R12.0.[3-4] : Oracle Shipping Delivery Based Details Not Selected For Pick Release Details Transaction Data Test
NOTE:837777.1 - FAQ: Troubleshooting Cross-Product Issues Between Shipping and Inventory
NOTE:262979.1 - Unprocessed Shipping Transactions Troubleshooting Techniques
NOTE:276207.1 - Diagnostics : Apps Check Video
NOTE:133464.1 - HTMOMSE Sales Order Diagnostic Script
NOTE:149926.1 - Pick Release is Failing for Locator Controlled Items
NOTE:151808.1 - Oracle Shipping Pick List Selection Activity Test
29 of 30
5/31/13 4:40 PM
Document Display
NOTE:156860.1
NOTE:290432.1
NOTE:298432.1
NOTE:299889.1
form.
NOTE:305708.1
NOTE:334052.1
NOTE:343201.1
NOTE:358831.1
NOTE:372170.1
NOTE:388183.1
NOTE:398385.1
NOTE:839264.1
NOTE:185804.1
NOTE:159998.1
NOTE:223702.1
NOTE:398723.1
NOTE:418492.1
NOTE:420748.1
NOTE:421998.1
NOTE:430528.1
NOTE:433379.1
30 of 30
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=3ur...
WSHFRREL: Unable To Pick Release From Release Sales Orders Form -Picks from STF
Interface Trip Stop Completes Successfully But Delivery Detail Status Update Is Delayed
Interface Trip Stop Error 'Your change invalidates the Customer Item Number on the Line'
E-Business Suite Diagnostics Setup Instructions
ARCHIVED: Standard Cleanup Scripts for INVDVDSD - SUPPLY/DEMAND in 11.5.10.2, 12.0 and 12.1
Order lines in Ship Sets Not Picking during Pick Release
Pick Release Backorders Sales Order Lines, Error in Log File "No Mtl_Sales_Order ID found for oe header"
Interface Trip Stop Errors With Error In Routine WSH_INTERFACE.PROCESS_DETAILS, Oracle Error - 1 User-Defined Exception
Interface Trip Stop Ends With A Warning Message and OM Interface Does Not Complete
Debugging Cost of Goods Sold Account (cogs_11i.sql)
Inventory Item Setup Data Collection Tool 11i
11i : Oracle Inventory Item Data Collection Data Collection Test
How To Process Standard Sales Order in Order Management for Application Release 11.5.10
Retry Activities in Error Concurrent Request to resolve OM Workflow errors.
Pick Release Fails When Using Pick Release Rule
How To Use the HTMomse11i Output To Resolve Pending Sales and Move Order Transactions
WSHFRREL - Pick Releasing Backordering Order Line-Default Locator Not Set
5/31/13 4:40 PM