Distribution - JDE1 (MOSC)

MOSC Banner

SR 3-8764484171 BackOrder release locks Order - PrintPick slip fails to Print on subsystem

edited Apr 4, 2014 12:00PM in Distribution - JDE1 (MOSC) 1 commentAnswered

We enabled Back Ordering for some of our branch plants. Back order release program (R42118) has been configured to use Print Pick slips (R42520) in Subsystem. There are some instances where Print Pick slip fails. Approximately 10% of the orders fail to print Pickslips.

.

Our detailed analysis proved that, the logical flow is causing the Order reservation, which fails Print Pick slip subsequently.

.

Technical  Details:

Below is the sequence of functions in the technical flow:

  1. Do Object reservation on Order [F00095]
  2. Release back orders
  3. Add subsystem record
  4. Release Object reservation on Order [Delete F00095]

In a typical scenario, this flow is working pretty well. But there are very frequent instances, where Print Pick Slip is failing to run. We analyzed the log / Call stack, & noticed that Print Pick slip is picking the subsystem request sometimes before Object reservation is removed. Which means that print pick flow is run before someone unlocked the order, so which obviously is failing.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center