<Insert Picture Here>

Trouble Shooting Stuck Shipping Transactions.

Presented by Binh Nguyen and Ed Barker

Introduction

 GOALS
 Understand Pick Release process.
 Understand Interface Trip Stops process.
 Understand where and why shipping transactions get
stuck.
 Determine the category of problem.
 Diagnose corrupt Workflows.
 Diagnose corrupt data in Shipping.
 Diagnose other Shipping Exceptions
Introduction

SCOPE
 Discuss various Order Management (OM), Shipping (WSH),
Work Flow (WF), and Inventory (INV) tables and the
movement of data through the sales order flow.
 Give an understanding of what is a stuck Shipping transaction
and how to troubleshoot such issues.
 Does not cover Inventory transaction troubleshooting
techniques but mentions relevant notes.
 Not a detailed analysis of HTMomse11i, but does cover some
sections.
Topics

Basic Shipping – Inventory Data Flow

 Key tables involved
Stuck Shipping Transactions
 Categories of issues.
Troubleshooting
 What to look for.
 Shipping – Inventory Data Flow

• How data passes from OM to WSH to INV

 Shipping – Inventory Data Flow

 Booking process
– Scheduling derives the ship date
– WSH_DELIVERY_DETAILS are created (provided it is a
shippable item and flow, eg. not RMA or Drop Ship)
 Pick Release process
– WSH_NEW_DELIVERIES are created (provided Autocreate
delivery is used)
– Move order (MO) created in
MTL_TXN_REQUEST_HEADERS
– MO lines created in MTL_TXN_REQUEST_LINES
– MO lines are allocated and transacted (based on Pick options
Auto Allocate and Auto Pick Confirm)
 Shipping – Inventory Data Flow

 Ship Confirm process

– Interface Trip Stops may be immediate or deferred.
– WSH_TRIPS and WSH_TRIP_STOPS are created.
– OM interface occurs
 Triggers Advanced Pricing
 Calculates freight charges
 Progresses Workflow
– INV interface occurs
 Populates MTL_TRANSACTIONS_INTERFACE
 Fires Cost Of Goods Sold (COGS) account generation
 Triggers INV transaction manager to:
– Perform sales order issue and decrement on-hand
– Relieve reservations
 Shipping Transactions

• Understanding the Shipping processes

 Shipping Transactions – Pick Release

 Pick Release
– After Move Order (MO) creation the delivery is created
– Depends on Autocreate delivery option in the PR rule or form
– Lines are grouped on delivery based on grouping criteria in
Shipping Parameters
– Look for a record created in WSH_NEW_DELIVERIES
 Shipping Transactions – Pick Release

 Pick Release
– Next the MO lines are processed
– If Auto-allocate = N -- manual allocation needed
– If Auto-allocate = Y -- Auto-detail (allocation) takes place
 Material staging suggestions are created
 Released_status = S (Released to Warehouse)
– If Auto-pickconfirm = Y -- MO is transacted
 Material moved to Staging sub and reservations created
 Released_status = Y (Staged/Pick confirmed)
– If Auto-pickconfirm = N -- manually transact the MO

– Following slides show how to Transact a Move Order, and

ship confirm process.
 Shipping Transactions – Interface Trip Stop (ITS)

 Interface Trip Stops

• Triggered automatically during Ship Confirm if Defer Interface
option is unchecked.
• Can be submitted manually (Shipping > Interfaces > Run)
 Shipping Transactions - ITS

 First phase of ITS is the OM Interface

• Progresses the SHIP_LINE workflow from Notified to
Complete
• Updates the order line with shipped quantities
• Splits the order line if necessary
• WSH_Delivery_Details flag updated
 oe_interfaced_flag = Y
 Shipping Transactions - ITS

 Second phase of ITS is the Inventory Interface

• Inserts a record into material_transactions_interface (MTI)
• Generates Cost Of Goods Sold (COGS) account transaction
• WSH_Delivery_Details flag updated
 inv_interfaced_flag = Y
 Shipping Transactions - ITS

 COGS Account Generated

• Code Combination ID (CCID) derived (this is the COGS
account used for financial accounting purposes)
• Populated in MTI as distribution_account_id
 Shipping Transactions - ITS

 Record inserted in MTL_Transactions_Interface

• WSH_Delivery_Details flag updated
 inv_interfaced_flag = Y
 Shipping Transactions - ITS

 Inventory transaction manager is invoked

 Record should be cleared out of MTI (else look for
errors)
 Shipping Transactions - ITS

 Verify completion status of all phases of ITS.

• Reservations relieved
• Order line WF progressed
• Inventory on-hand decremented
.
DEMONSTRATION OF PICK RELEASE AND SHIP CONFIRM
PROCESS
Pick Release with Auto Allocate NO
Auto Pick Confirm is NO
 Shipping Transactions Form
Delivery Detail is “Released to Warehouse”
 Scroll Right
Note the Move Order Number
Switch Responsibility to Inventory
Navigate to Transact Move Orders
Find the Move Order
Move Order has been Allocated
Click on View/Update Allocations
Make any adjustments, for example, change locator or lot
Click on Transact
 Switch back to OM Super User
Find the order in Shipping Transactions form
See delivery details status is now “Staged/Pick Confirmed”
Ship confirm with Defer Interface
Now line status is Shipped, next step Run Interfaces
 Run Interfaces
Select Interface Trip Stop
Enter Delivery ID or Trip Stop ID
Submit the Request
 After Interface Trip Stop Completes
The Delivery Detail is Interfaced
Workflow Will Continue to Fulfillment and Invoicing
 Stuck Shipping Transactions

Workflow status prevents OM Interface completing.

 Retry WF Activities in Error function
 Note. 420748.1 – WF Retry Concurrent Program

Corrupt Shipping data prevents OM Interface or INV

Interface completing.
 Several known data issues: http://www-
apps.us.oracle.com/pqe/wsh/wsh_generic_scripts.html
Data inserted into MTI but errors.
 Note. 262979.1 - Unprocessed Shipping Transactions
Troubleshooting Guide
Valid business rule exceptions.
 Stuck Shipping Transactions - Data

 Important flags
– WSH_TRIP_STOPS - pending_interface_flag
• if set to Y will continue to be processed by ITS
– WSH_DELIVERY_DETAILS - released_status_flag
Y = Staged
R = Ready to Release
S = Released to Warehouse
B = Backordered
P = Pending Inventory Interface
C = Shipped
N = Not Ready to Release
D = Cancelled
X = Not Applicable
 Stuck Shipping Transactions - Data

 Important flags
– WSH_DELIVERY_DETAILS – oe_interfaced_flag
Y = OM interface complete and WF updated
N = OM interface not complete
– WSH_DELIVERY_DETAILS – inv_interfaced_flag
Y = Data was inserted into Material_Transaction_Interface
P = Pending means MTI insert was attempted
N = INV interface not attempted

The status of these flags can be seen on the Shipping

Transactions form (STF) as seen below:
Stuck Shipping Transactions - Data
 Stuck Shipping Transactions – Data
Queries to find other orders with same issue
Stuck Shipping Transactions – Data

These queries are safe to give to customers.

No updates! Log a data fix bug.
 Debugging Shipping Transactions
Debugging WSH transactions
 Note.290432.1 – How to Create a Debug File in Shipping
Execution (might want to show what to look for to see if customer set the debug options properly.
Customer might say he set inv debug to 10, but how do we know that he/she did?)

Debugging COGS issues

 Note.159998.1 - Debugging Cost of Goods Sold Account
(cogs_11i.sql)
 NOTE: COGS issues are transferred to 497/accounting/cogs
Detailed ITS Debugging
 Bde_ITSall.sql
• Interface Trip Stop debug file (OM/WSH/INV debug)
• Environment information and file versions
• Level 12 trace file generated for this request
Generic Data Scripts
 Note. 404568.1 -- Generic Scripts To Identify Data Corruption
In Shipping Execution (Internally published)
 Debugging Shipping Transactions

Always collect the following

 Note.133464.1 – HTMomse (11i or 12) SO Diagnostic
 Sales order tables
 WF tables
 WSH tables
 INV tables
 Note.276207.1 - Diagnostics : Apps Check
 Profile options
 Recent patches
 Object versions
 Triggers
 Indexes
QUESTIONS
ANSWERS