Troubleshooting-stuck Pickrelease And Shippingtrans 1h118

Document Display

https://.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


3.3. Activity instance ship_line is not a notified activity 3.4. No delivery detail found 3.5. Inventory Interface could not process some of the lines in the batch as they are in error status 3.6. Interface Trip Stop Fails With Error in Routine WSH_INTERFACE.PROCESS_DETAILS, Oracle Error - 1 -Defined Exception 3.7. Your Change Invalidates the Customer Item Number on the Line 3.9. Interface Trip Stop Completes Successfully But Delivery Detail Status Update Is Delayed 3.10. ITS Error: No Serial Records Found For Transaction_Temp_Id 3.11. ITS Error: No Open Period Found for Date Entered 3.12 ITS errors not resolved by the above suggestions 4. ERRORS WITH SHIPPING REPORTS 4.1 Error at Ship Confirm: "The document category has no valid sequence" 5. SHIPPING EXCEPTIONS 6. WORKFLOW CONSIDERATIONS 7. DATA ISSUES 9. RESOURCES 9.1. Diagnostics 9.2. INV/SHIP Profiles for Data Analysis 9.3. Demos/White Papers/Troubleshooting Notes 10 Training References

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


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

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 Ask the customer for screen shots of the On-Hand Availability form. This form will show sufficient on hand quantity, but the fields 'Available to Reserve and /or Available to Transact will not show sufficient quantity. Following is an example:

3 of 30

5/31/13 4:40 PM

Document Display

4 of 30


5/31/13 4:40 PM

Document Display


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 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 , 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


1. As the inventory , please navigate to setup->organizations->subinventories 2. Search the primary subinventory in which your items exist 3. Open this subinventory. 4. In the field picking order, enter a value of 1. This will be the subinventory which pick release will be examined first to see if sufficient quantity exists, when you do not specify a subinventory on the pick release form. 5. Repeat these steps for each of the subinventories which will have all of the items that will be picked on your sales orders. You may assign all of these subinventories to the same priority (1), or to different priorities if you want to implement a prioritization requirement. 6. Test this setup by entering a new order having items which exist in different inventories. Note that all items must exist in one of the subinventories you modified in steps 2-5. Reference: Note 299889.1 "WSHFRREL: How to specify the Order in which the system will pick release from the Subinventories if none is specified in the release sales order form."

2.1.3 No default stage subinventory A stage subinventory is always required. Solution: 1. Order Management super . 2. Navigate to Change Organization, and select the organization for which you are defining the staging subinventory. 3. Navigate to shipping->setup->shipping parameters 4. Go to the Pick Release tab 5. Select a default Stage Subinventory in the field Staging1. The default staging subinventory must not be the same as the subinventory from which the items will be picked. 6. If locator controlled items are being shipped, the Staging subinventory must be defined as having locator control.

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.


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

2.1.5. No open period exists for pick release In addition to the inadequate supply error, the Pick release log file shows these errors: [] Inv_Pick_Release_PVT.Process_Line: inv detailing failed [] Inv_Pick_Release_PVT.Process_Line: No open period found for date entered Solution: Use either options A, B, or C A. Open the inventory ing period for the period in which the order is scheduled to ship. 1. As the Inventory , navigate to ing Close Cycle->Inventory ing Periods 2. Select the period to be opened. Its current status should be Future 3. Click on the change status button. 4. A small dialog box asks if you want to open this period. Click on Yes. B. Change the requested date on the order to a date within an open period 1. As the Order Management super , navigate to the Sales Orders form 2. Go to the Line Items/Shipping tab. 3. For each order line, change the requested date to a date which is in an open inventory period. 4. If the scheduled ship date does not automatically change to a date within the open period, then also change the scheduled ship date. Note that the scheduled ship date may be driven by defaulting rules (navigate to Order Management->setup->rules->defaulting) C. 1. 2. 3. 4. 5. 6.

7 of 30

Transact the move order in the open period. As the Order Management super , navigate to the Pick Release form. Pick Release the order. Specify Auto Allocate as NO, so that move orders will not be automatically transacted. Switch to the Inventory Navigate to Move Orders->Transact Move Orders, and find the move order for this order. Allocate the move order Click on the View/Update allocations button

5/31/13 4:40 PM

Document Display


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.6. Improper set-up of the Sales Order Key Flexfield in Inventory In addition to the inadequate supply error, the following error also occurs in the pick release log file: No Mtl_Sales_Order ID found for oe header Solution: 1. As the Order Management super , navigate to Setup>>Financials>>Flexfield>>Key>>Segments 2. Ensure that the Sales Order Key flexfield segments --Order Number, Order Type and Order Source are mapped to Segments 1 , 2 and 3 as follows: Segment1-Order Number Segment2-Order Type Segment3-Order Source 3. Also ensure that the profile option OM: Source Code is set to 'ORDER ENTRY' Reference: Note.398385.1 11i WSH Pick Release backorders sales order lines

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 no unintended ship set defaulting is occurring. A. Remove the line with insufficient quantity from the ship set 1. As the Order Management , 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


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.8. An invalid subinventory was specified on the sales order line The Order entry operator explicitly specified a subinventory on the sales order line (line items/shipping tab), and that subinventory is either invalid or does not have sufficient quantity.. Since there was no available quantity in that subinventory, pick release backordered the delivery line. When a subinventory is specified on the order line, pick release considers only that subinventory and does not look for other subinventories where sufficient quantity is available Solution: Remove or correct the subinventory specified explicitly on the sales order line. 1. Order Management super 2. Navigate to the Sales orders form, and find the sales order in question. 3. Go to the Line Items/Shipping tab. 4. On this tab, the subinventory field is normally hidden. If you do not see this field, use the Folder->show field option at the top of the Applications window to display it. 5. Null out any value within this field.

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


1. In the Pick Release form, go to the Inventory tab. 2. that no subinventory is specified in the pick from subinventory field.

2.1.10. There may be an issue in Inventory Allocations To diagnose the possiblity that this is true, do the following: 1. 2. 3. 4. 5. 6. 7. 8.

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 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 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 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


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 ed 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 Details", there is a button to the files associated with this diagnostics test. Click on it. 3. Zip file WSHPKLN.ZIP will be ed. 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 ree file. There are two ree 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:

Analysis of Batch vs Transaction data ERROR - Batch specified To Schedule Date = 08-AUG-09 23:59:59 which is less than the transaction Schedule Date = 10-AUG-09 20:40:21 ACTION - Please ensure To Schedule Date specified for Pick Release >= transaction schedule date B. FOR RELEASE 12.0.2 AND HIGHER, this test is available in the Diagnostics Pack. Please see Note 463641.1 "Oracle Shipping Delivery Based Details Not Selected For Pick Release Details Transaction Data Test" for complete instructions on how to run this test from the Oracle Diagnostic Tools responsibility. Following is a summary of steps to run this test with the Diagnostics Pack, taken from Note 463641.1: 1. As the Order Management Super , 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. 2. When pick release completes, open the Pick Selection List Generation log file, and note the batch number for the request. 3. Switch responsibility to "Oracle Diagnostics Tool" (see Note 358831.1 for details) 4. Select application "Oracle Shipping Delivery Based" from the "Application" list of values

11 of 30

5/31/13 4:40 PM

Document Display


5. Click the "Advanced" tab 6. Scroll down to group "Pick Release" 7. Select test name "Details Not Selected For Pick Release Details" 8. Input Parameters (* required) Order Header Id Line Id Delivery Detail Id Batch Name (This is the patch number you noted in step 2) C. If the Diagnostics tests from either step A or step B cannot be performed you can diagnose the issue as follows: 1. Re-run pick release for the problematic order with debug options turned on. Please see <> for details 2. In the pick release logfile search for the line which begins with "Dynamic SQL..." 3. The lines immediately following represent the SQL query which is used to select lines eligible for picking. Example: Dynamic SQL: ( SELECT DISTINCT WDD.SOURCE_LINE_ID, WDD.SOURCE_HEADER_ID, .... FROM WSH_DELIVERY_DETAILS WDD, WSH_DELIVERY_ASSIGNMENTS WDA, .... WHERE WDE1.DELIVERY_ID = WDA.DELIVERY_ID {more where clauses}

4. After the SQL statement, look for lines like this: No line fetched release_table.COUNT ==> 0 5. You can copy this query into your SR, reformat it to show where the WHERE clause begins, and then compare every non- clause to the HTMomse report to find mutually exclusive conditions. You can also compare all of the pick release criteria in the screenshots of the 3 tabs of the Pick Release form to the WHERE clauses from the dynamic SQL statement. If there are other fields in the WHERE clause which are not shown in either the HTMomse report or the Pick Release form, then you can query for all of the data in a specific table. For example, if there are fields in wsh_delivery_details that are not visible, use the following query: select * from wsh_delivery_details where delivery_detail_id =

12 of 30

5/31/13 4:40 PM

Document Display


HTMomse Report You can run the HTMomse11i or HTMomse12 report by doing the following: 1. 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 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 the report to this SR.

FREQUENT CAUSES:

2.2.1. Subinventory specified as Release Criteria In the "Release Orders for Picking" form, Inventory tab: there are two different fields for subinventory. 1. Under Release Criteria. If a subinventory is specified here, no order line will be considered for picking unless that subinventory has been explicitly specified on the sale order line, line items/shipping tab. . Orders lines which have a NULL value in the subinventory field will not be picked. The subinventory field is not normally visible in the line items section of the Sales Orders form; it must be displayed by using folder->show field. Most s will not see a subinventory field on the line items/shipping tab, and will not select a subinventory; thus, specifying a subinventory under release criteria will exclude most order lines from consideration for pick release. 2. Under Pick From region at the bottom. If a subinventory is specified here, but not under release criteria, then there will be no eligibility for picking exclusion based on subinventory. Pick release will look only in this subinventory; if sufficient quantity is not found here, pick release will not consider any other subinventory and will report insufficient quantity. Reference: Note 305708.1 WSHFRREL: Unable To Pick Release From Release Sales Orders Form after 11.5.10

13 of 30

5/31/13 4:40 PM

Document Display


2.2.2. Specified date ranges exclude the order being picked Cause: 1. An order was specified which has a future scheduled ship date or request date. 2. The Scheduled Ship or Request TO dates defaulted to today's date when the release sales orders for picking form was opened. 3. did not null out these dates. Solution: When attempting to pick release orders with future scheduled ship dates, insure that the "TO" schedule ship date in the pick release form is either nulled out, or contains a date future to the scheduled ship dates on the orders to be picked.

2.2.3. Delivery detail has already been assigned to a delivery 1. Run the pick release diagnostic as discussed above under troubleshooting tips sections A and B 2. The output will show that the delivery detail has been assigned to a delivery, and "include assigned lines" was not checked. Solution: This issue is resolved by checking the check box "Include Assigned Lines" on the shipping tab of the Pick Release form.

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 ed 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 , 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.


Navigate to Shipping->Setup->Picking->Define Release Rules Form Query the Pick Release Rule in the Define Release Rules form. Remove the warehouse value Enter the same value again. (Which takes latest ship from location value associated to that warehouse). Save the record.

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 11.5.10

If you log a Service Request with Oracle for your pick release issue, please 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)

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. Solution: Run the script loc_col.sql to check for trailing spaces within any of the item description. This script can be ed from the following site: http://www-apps.us.oracle.com/pqe/wsh/wsh_generic_scripts.html#GS-13 If the script returns any trailing spaces, please patch 4488261. This patch contains the script wshtrail.sql, which can be run to remove the trailing spaces from these records. See <> for more information.

15 of 30

5/31/13 4:40 PM

Document Display


3.2 Interface Trip Stop problems Most of the Interface Trip Stop problems will require a datafix from Development. The following are some of the scenario that can appear for OM Interface issues. The scenario also includes the query which needs to be run where the output will need to be included in the datafix bug.

Symptoms of problems with Interface Trip Stop include the following: 1. In the View-> Requests form, you see that the request Interface Trip Stop completed with Error or Warning. 2. In the Shipping Transactions form, after you ship confirm a delivery, you see that the status of the delivery details you thought you ship confirmed is 'Shipped' and the next step is 'Run Interfaces'. If you see this or any of the following 3 symptoms, check view->requests and that the Interface Trip Stop request completed with error. 3. After you ship confirm an order, you query the Inventory Material Workbench and find that inventory balances have not been adjusted for the quantity that was shipped. 4. In the Sales Orders form, after you ship confirm a delivery, you observe that the order line status remains at 'SHIPPED' and does not change to something like 'Awaiting Invoicing' or 'Closed' When entering a new SR for ANY issue with Interface Trip Stop, please the following documents: A. Interface Trip Stop debug log file: 1. On your production instance, please set the following profile options at the level. chosen must be the same who will perform all remaining steps in this action plan. OM: Debug level=5 INV:Debug level=10 INV: Debug trace = yes WSH: Debug Enabled = Yes WSH: Debug Level = Statement 2. Navigate to Shipping >Interfaces-> run 2.1 Select Interface Trip Stop - SRS 2.2 In the parameters screen, set Debug Level = 1 2.3 Input parameters to select the problematic delivery or trip stop 3. Submit the Request 4. View->Requests; wait for the Interface Trip Stop programs to complete 5. When complete, the request log file to your new SR. 6. If more than one delivery or trip stop is stuck in Interface Trip Stop, please repeat steps 2-5 for all such trip stops or deliveries 7. to set the 4 profiles from step 1 back to their original values. Otherwise, you may experience significant performance degradation.

16 of 30

5/31/13 4:40 PM

Document Display


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.

Diagnostic apps check report As the OM super , navigate to reports,requests->run request Select the Request Diagnostics: Apps Check Select the following product parameters Order Management Shipping Execution Inventory Warehouse Management 4. the request output file to this SR. D. The query from item "a)" below, unless one of the subsequent queries is more pertinent to your issue.

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


and ol.line_id = wdd.source_line_id and wdd.source_code = 'OE' and wdd.released_status = 'C' and (wdd.oe_interfaced_flag in ('N','P') or wdd.inv_interfaced_flag in ('N','P')) and wdd.source_line_id = ol.line_id and trunc(wdd.creation_date) > sysdate -365

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


where wdd.source_code = 'OE' and wdd.released_status = 'C' and (wdd.oe_interfaced_flag in ('N','P') or wdd.inv_interfaced_flag in ('N','P')) and wdd.delivery_detail_id = wda.delivery_detail_id and trunc(wdd.creation_date) > sysdate -365 and wda.delivery_id = wnd.delivery_id and wnd.delivery_id = wdl.delivery_id and wdl.pick_up_stop_id = wts.stop_id and nvl(wts.pending_interface_flag,'X') <> 'Y' order by 1;

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 and provide the documentation requested in the previous note box

3.3. Activity instance ship_line is not a notified activity Interface Trip Stop fails due to incorrect status in the Ship_Line Workflow activity. This is usually due to some exception in the Workflow, or the Workflow was forced and progressed beyond Ship_Line activity and may have closed.

19 of 30

5/31/13 4:40 PM

Document Display


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 , 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/'.),

then check the following: 1. As the Inventory , Navigate to navigate to setup->organizations->subinventories 2. Find the Staging subinventory, and open it. 3. In the Parameters region, check the checkbox labeled "Allow Reservation" (In 12.x releases, you may find that 'allow reservation' is checked by default and is not updatable) Reference: Note 185804.1 Interface Trip Stop Ends With A Warning Message and OM Interface Does Not Complete

3.4. No delivery detail found See the following in the ITS debug log file: No of record fetch ==> 0 l_bulk_batch_size ==> is NULL l_def_inv_online ==> No Delivery Detail Found No Delivery Detail Found ==> is NULL

20 of 30

5/31/13 4:40 PM

Document Display


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 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 and 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 -Defined Exception

21 of 30

5/31/13 4:40 PM

Document Display


See the following error in the ITS log file: msg_buffer ==> Error in Routine WSH_INTERFACE.PROCESS_DETAILS, Oracle Error - 1 -Defined Exception This issue has been fixed in the file WSHDDINB.pls in version 115.272.11510.4. To resolve the issue, and apply patch 5703373. Reference: Note 839264.1 "Interface Trip Stop Erroring With Error Routine WSH_INTERFACE.PROCESS_DETAILS, Oracle Error - 1 -Defined Exception"

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 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 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. that the Activate checkbox is checked for this item. Next, click on Cross References and 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


3.10. ITS Error: No Serial Records Found For Transaction_Temp_Id Caused by changing an item from serial-controlled to not-serial-controlled after pick release. At the time of pick release, a transaction_temp_id was populated in wsh_delivery-details. Therefore the system expects serial numbers. Solution: Log a Datafix bug to null-out the transaction_temp_id

3.11. ITS Error: No Open Period Found for Date Entered Interface trip stop program is failing during the Inventory Interface. The following error appears in the HTMomse report, in the MTL_TRANSACTIONS_INTERFACE section: Error : No open period found for date entered in MTL_TRANSACTIONS_INTERFACE. This issue will most frequently occur when the goods are physically shipped late in one month, for example, on March 25 2010. However, due to issues with the order or just not having personnel available to update e-Business suite, it is not noticed until early the following month, for example on April 10, that the order was never ship confirmed. The March period was closed on April 1st.

Solution: 1. As the Inventory , navigate to Transactions->Transactions Open Interface 2. Search for the erred record 3. Update the transaction date to a date with the current ing period 4. As the Order Management , 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.

3.12 ITS errors not resolved by the above suggestions For all issue with Interface Trip Stop which cannot be resolved using any of the above suggestions, please enter a new SR with Shipping Execution . Please attach the following documents to your new SR: 1. Diagnostic Apps Check report, for Order Management, Shipping Execution, and Inventory 2. Interface Trip Stop debug log file. Please see <> for debug log file instructions. 3. HTMomse report for the problematic order. Please see <> to obtain the HTMomse script. If you do not know the order number affected by Interface Trip Stop issues, you can find the order from the delivery_id or trip_stop_id using one of the following queries:

23 of 30

5/31/13 4:40 PM

Document Display


select oh.header_id, oh.order_number, wda.delivery_id, wdd.delivery_detail_id from wsh_new_deliveries wnd, wsh_delivery_assignments wda, wsh_delivery_details wdd, 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 and wnd.delivery_id = &delivery_id select oh.header_id, oh.order_number, wda.delivery_id, wdd.delivery_detail_id, wts.stop_id, wts.trip_id from wsh_new_deliveries wnd, wsh_delivery_assignments wda, wsh_delivery_details wdd, oe_order_headers_all oh, wsh_trip_stops wts, wsh_delivery_legs wdl where wdl.pick_up_stop_id = wts.stop_id and wdl.delivery_id=wnd.delivery_id and wnd.delivery_id=wda.delivery_id and wda.delivery_detail_id = wdd. delivery_detail_id and wdd.source_header_id = oh.header_id and wts.stop_id = &pickup_stop_id

4. ERRORS WITH SHIPPING REPORTS

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


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 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.

3. Query using the flashlight. 3.1 Search for the Application = Shipping Execution 3.2 Pick the Name of the Document Category you are using 3.3 Ensure that there is a valid document category defined for the document which is not being printed. 3.4. Make a note of the value for the field Code. This will need to match the value of the category_code in step 3.6 3.5. Navigate to shipping->setup->documents->assign sequence 3.6. In the sequence assignment form, if there already is a sequence assignment for the category you confirmed in step 3.3: 3.6.1 Select that sequence assignment 3.6.2 From the top menu bar, navigate to help->diagnostics->examine 3.6.3 In the Examine window, select ASSIGNMENTS as the value for BLOCK, and CATEGORY_CODE as the value for FIELD 3.6.4 The value returned should be the same as the value noted in step 4. If not, proceed to step 7 3.7. If there are any sequence assignments with invalid category_code (from step 6.4), end-date those assignments 3.8. Enter a new sequence assignment. Select the same category as you reviewed in step 3 and 4.9. Retest your issue. In the case where the value returned in step 6.4 IS the same as the value for category_code in the document categories form, please log a new SR with Oracle

25 of 30

5/31/13 4:40 PM

Document Display


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


In View Exceptions form look out for Exception Behavior and Status

Queries to show exception definitions /* query to find exception_behavior 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_BEHAVIOR' AND (lookup_type LIKE 'EXCEPTION_BEHAVIOR') AND (view_application_id = 665)

27 of 30

5/31/13 4:40 PM

Document Display


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 (cogs_11i.sql)

28 of 30

5/31/13 4:40 PM

Document Display


Detailed ITS Debugging Interface Trip Stop debug file (OM/WSH/INV debug) Environment information and file versions Level 12 trace file generated for this request Bde_ITSall.sql

9.2. INV/SHIP Profiles for Data Analysis Note 290432.1 - How to Create a Debug File in Shipping Execution Note 148651.1 - How to get Debug Information for Inv. Mat. Transactions

9.3. Demos/White Papers/Troubleshooting Notes Note Note Note Note

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


-

OMCHECK.SQL Oracle Order Management Diagnostic Tool How to Create a Debug File in Shipping Execution Sales Orders will not Pick - No open period found for date entered WSHFRREL: How to specify the Order in which the system will pick release from the Subinventories if none is specified in the release sales order

-

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 -Defined Exception Interface Trip Stop Ends With A Warning Message and OM Interface Does Not Complete Debugging Cost of Goods Sold (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

Troubleshooting-stuck Pickrelease And Shippingtrans 1h118

Overview 3e4r5l

More details w3441

Related Documents 3m3m1z

Troubleshooting-stuck Pickrelease And Shippingtrans 1h118

Lysosomes And Peroxisomes And Glyoxysomes 4u1e12

House And Lords And Rashi 1n1ou

Spun And Filament Yarns And 52243u

Hazards And Gmp And Ssop.ppt 4a5j60

Ecuk And City And Guilds 71205y

More Documents from "CG" 4v1p2p

Troubleshooting-stuck Pickrelease And Shippingtrans 1h118

Top Body Challenge Free 6v4i2w

2016 - Bttax z2a3j

Tb_ch01 5c475t

Vfjhbfjdbvdf Bb B B Vbn Bnv V V V Vbvv Bv V Bv Bv Bv V Vbvb Bv Vb Vb V V Bv V V Vv Vvv V V V Vbv Hghvbb Vb Bvvb Bv Vb Vb Vb Bvvb Bv Bvv V Bvvb Bv Bv Bvvb V V V Bv Vv V Vb Bvv Bv Bv Bv Bv V Vb Vb V Vbv Bv Vbv Vbvb 6jj5q

6l6m1j