ARTICLE 1
Interface Trip Stop Functionality
There are typically four interface program get triggered at the
time of ship confirm. They are
·
Interface Trip stop
·
Packing Slip Report
·
Bill of Lading
·
Invoice
Interface Trip Stop is one of the main interface programs which can be triggered
at the time of ship confirm or later as Interface Trip stop - SRS concurrent request.
Interface trip stop has two parts
·
Order Management Interface (First part)
·
Inventory Interface (Second part)
Order Management Interface part update the order management tables
like OE_ORDER_LINES_All (Update Shipped_Quantity, Shipping_Quantity, Actual_Shipment_Date)
and also WSH_DELIVERY_DETAILS (make Released_status, OE_INTERFACED_FLAG = ‘Y’)
table.
The Inv_Interfaced_Flag remains = X (Pending) or N which will
changes to Y after execution of second part
The second part i.e. Inventory Interface will be triggered only if
the value of OE_INTERFACED_FLAG = ‘Y’ otherwise second part will not be
triggered. Even if you try to run this from SRS, these lines will not be picked
for processing.
Inventory Interface part move data from MTL_TRANSACTIONS_INTERFACE
to MTL_MATERIAL_TRANACTIONS and MTL_MATERIAL_TRANSACTIONS is updated with Sales
Order Issue transaction. Also data is deleted from MTL_DEMAND, MTL_RESERVATIONS
and WSH_NEW_DELIVERIES. Item quantity reduced from MTL_ONHAND_QUANTITIES
and
MTL_TRANSACTION_ACCOUNTS is updated with accounting information.
ARTICLE 2
Interface Trip Stop – SRS
Program
The Interface Trip Stop
(ITS) will be triggered at the time of Ship Confirm if the check box ‘Defer
Interface’ is not checked. ITS can also be
executed from concurrent request.
Interface Trip Stop does
the following things,
- · Updating the Order Management Data (OE_ORDER_LINES_ALL)
- · Triggering the Inventory Interface (to update the Inventory tables)
ITS updates the following
fields on OE_ORDER_LINES_ALL table:
- · Shipped_Quantity
- · Shipping_Quantity
- · Actual_Shipment_Date
Inventory Interface will be
triggered only if the first part, that means related to OM has successfully
completed and flag OE_INTERFACED_FLAG = ‘Y’ on WSH_DELIVERY_DETAILS.
If value of this flag is
N/P then Inventory Interface will never be triggered. And even if you try to
submit the Inventory Interface - SRS, delivery detail with OE_INTERFACED_FLAG =’N’ will never be picked up.
OE_INTERFACED_FLAG = Y -- signifies ITS has
interfaced shipping data to OM
INV_INTERFACED_FLAG = Y -- signifies ITS has
interfaced shipping data to INV
As mentioned earlier if the
‘Defer Interface’ checkbox is
checked then Interface trip stop concurrent will not be triggered
automatically, we should run it manually.
Navigation:
Oracle Order Management
> Shipping > Interfaces > Run
1.It process the data related to Order Management.
2.It Process data related to Inventory.(and we have separate CP for this too ?Inventory Interface?).
In First part it make update on oe_order_lines_all table as well as wsh-delivery_details and once this part executed successfully only then SECOND phase of ITS has triggered. If FIRST part error out for some reason then 2nd part will not be triggered, and even if you try to submit ?Inventory Interface?, it will not pick up you data. Reason ? it will validate and check if oe_interfaced_flag in wsh_delivery_details table is Y or not. If it is N or X ?inventory Interface? will not pick that record for processing.
I have observed that in most of time user submit the interface trip stop while doing the ship confirm, but there are considerable cases when customer preferred to run this as a scheduled process without specifying the delivery# or Trip #, because their volume of order processing is very high and they want to run this process during some particular time of the day.
Please make a note that unless this process execute, workflow for Order line is remain at SHIP_LINE Notified and will not progress to Fulfill and finally Invoicing .So while deciding when to trigger this program you have to make sure that when you want to Invoice customer.
One piece of advice that I will give here is, Never try to stop execution of this program, unless you have a very valid reason. Any halt in ITS will result in piling of data in SHIP_LINE notified workflow status and once you start executing again after a stop it will take a deep dive in terms of your performance.
ISSUE : (INTERFACE TRIP STOP COMPLETING WITH WARNING STATUS) Unable to Generate Excise Invoice against Delivery ID No: 4992318
DIAGNOSIS METHOD:
ARTICLE 3
Interface Trip
Stop - Interface Trip stop plays very critical part in Oracle Order management
application.
It is concurrent program that you can triggered from Interface > Submit Request . Interface Trip Stop.
Or you can also trigger this concurrent program at the time of ship confirm by uncheck the ?Defer Interface? checkbox. By Default this check box is uncheck only.
Interface trip stop has 2 parts
It is concurrent program that you can triggered from Interface > Submit Request . Interface Trip Stop.
Or you can also trigger this concurrent program at the time of ship confirm by uncheck the ?Defer Interface? checkbox. By Default this check box is uncheck only.
Interface trip stop has 2 parts
1.It process the data related to Order Management.
2.It Process data related to Inventory.(and we have separate CP for this too ?Inventory Interface?).
In First part it make update on oe_order_lines_all table as well as wsh-delivery_details and once this part executed successfully only then SECOND phase of ITS has triggered. If FIRST part error out for some reason then 2nd part will not be triggered, and even if you try to submit ?Inventory Interface?, it will not pick up you data. Reason ? it will validate and check if oe_interfaced_flag in wsh_delivery_details table is Y or not. If it is N or X ?inventory Interface? will not pick that record for processing.
I have observed that in most of time user submit the interface trip stop while doing the ship confirm, but there are considerable cases when customer preferred to run this as a scheduled process without specifying the delivery# or Trip #, because their volume of order processing is very high and they want to run this process during some particular time of the day.
Please make a note that unless this process execute, workflow for Order line is remain at SHIP_LINE Notified and will not progress to Fulfill and finally Invoicing .So while deciding when to trigger this program you have to make sure that when you want to Invoice customer.
One piece of advice that I will give here is, Never try to stop execution of this program, unless you have a very valid reason. Any halt in ITS will result in piling of data in SHIP_LINE notified workflow status and once you start executing again after a stop it will take a deep dive in terms of your performance.
REAL EXAMPLE IN MY EXPERIENCE
ISSUE : (INTERFACE TRIP STOP COMPLETING WITH WARNING STATUS) Unable to Generate Excise Invoice against Delivery ID No: 4992318
DIAGNOSIS METHOD:
1) Please generate the ITS debug logfile as
follows:
a) Set the following profile options, at User level
except
WSH: Debug Log Directory - This profile option may be set at the Site level to any valid directory path.
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
WSH: Debug Log Directory - This profile option may be set at the Site level to any valid directory path.
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not
need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
All profiles should be set to User level except
WSH: Debug Log Directory - This profile option may be set at the Site level to any valid directory path.
b )Go to Shipping Interfaces
Interface Trip Stop
Enter the delivery number
Set the Debug Level parameter to '1' (Debugging ON).
c) Submit the job.
d) Provide the Interface Trip Stop log file (View > Requests > Find > click on View Log... for the appropriate file).
2) Please do the following to upload an HTMomse report for your problematic order.
Download the correct HTMomse script from note 133464.1 "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.
. 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
. When prompted for order number, please enter order number
. When prompted for line_id, please hit the enter key without making any entry. This will cause the report to show all order lines.
. When prompted for the sections you want shown in the report, please enter 'Y' for all of the parameters
. 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.
. The SQL script will give you the full path for the HTMomse report output.
Please upload the report to this SR.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
All profiles should be set to User level except
WSH: Debug Log Directory - This profile option may be set at the Site level to any valid directory path.
b )Go to Shipping Interfaces
Interface Trip Stop
Enter the delivery number
Set the Debug Level parameter to '1' (Debugging ON).
c) Submit the job.
d) Provide the Interface Trip Stop log file (View > Requests > Find > click on View Log... for the appropriate file).
2) Please do the following to upload an HTMomse report for your problematic order.
Download the correct HTMomse script from note 133464.1 "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.
. 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
. When prompted for order number, please enter order number
. When prompted for line_id, please hit the enter key without making any entry. This will cause the report to show all order lines.
. When prompted for the sections you want shown in the report, please enter 'Y' for all of the parameters
. 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.
. The SQL script will give you the full path for the HTMomse report output.
Please upload the report to this SR.
ROOT CAUSE:
THE OE_INTERFACE_FLAG SHOWING 'P' INSTEAD OF 'Y'
RESOLVED STEPS:
WHAT ORACLE RECOMMENDED?
THE OE_INTERFACE_FLAG SHOWING 'P' INSTEAD OF 'Y'
Actions
=======
1. Run the below DML-statement.
UPDATE wsh_delivery_details
SET set oe_interfaced_flag = 'Y',
last_update_date = sysdate,
last_updated_by = 636021
WHERE delivery_detail_id in ( 5073499, 5073502)
/
2. Issue COMMIT if only 2 rows updated, else ROLLBACK.
3. Then run the "Order Management Interface - SRS" for Trip Stop -> 2302845-XXX TRADING:XXX TRADING LOCATION-14\02\2015
4. Ensure it completes, then please upload fresh HTMomse12 script of Order Number = 121221545.
=======
1. Run the below DML-statement.
UPDATE wsh_delivery_details
SET set oe_interfaced_flag = 'Y',
last_update_date = sysdate,
last_updated_by = 636021
WHERE delivery_detail_id in ( 5073499, 5073502)
/
2. Issue COMMIT if only 2 rows updated, else ROLLBACK.
3. Then run the "Order Management Interface - SRS" for Trip Stop -> 2302845-XXX TRADING:XXX TRADING LOCATION-14\02\2015
4. Ensure it completes, then please upload fresh HTMomse12 script of Order Number = 121221545.
WHAT ORACLE RECOMMENDED?