Next step – Run interfaces

After doing ship confirm, the shipping line status changes to ‘Shipped’ and next step shows ‘Run Interfaces’

There are many reasons for an delivery line to get stuck like this, the common reason is when an user does ‘Ship confirm’ there is ‘Defer Interface’ checkbox which should be ‘Unchecked’ so that concurrent request ‘Interface trip stop SRS’ is run automatically after ship confirm is done.

If user has checked ‘Defer Interface’ checkbox, then ‘Interface trip stop SRS’ will not run, and should be run manually by user.Run ‘Interface trip stop SRS’ concurrent and ensure that it is completed successfully then run ‘Workflow background process’ concurrent.

If ‘Interface trip stop SRS’ concurrent completes with warnings or in error, Set the following profile options and once again run the concurrent and refer the log file to find the reason behind the problem.

OM: Debug level – Set to 5

WSH: Debug Enabled – Set to Yes

INV: Debug Trace – Set to Yes

WSH: Debug level – Set to Statement

INV: Debug Level – Set to 11

After getting the log file reset the profile option back to original value.

Even after ‘Interface trip stop SRS’ concurrent is run with ‘Defer Interface’ checkbox in ‘Unchecked’ status, if the next step is not changed to ‘not applicable’ then try running the following concurrent’s in the same order.

1. Interface trip stop SRS
2. Order management interface
3. Inventory interface
4. Workflow background process.

Navigation to run the concurrent’s – Order management – Shipping – Interfaces - Run

Even after performing these activities, if the issue is not resolved then, in ‘Transaction open interface’ form query the Item in the particular organization, you can find the problematic delivery with the reason for it.

Analyze the reason and do necessary corrections.

Navigation: Inventory – Transactions – Transaction open Interface.

---X---