Distribution - JDE1 (MOSC)

MOSC Banner

P4205 updated F4111 but failed to update F4211

edited Aug 4, 2017 5:01AM in Distribution - JDE1 (MOSC) 2 commentsAnswered

User performed P4205, which wrote a record to F4111, but did not update F41021 nor F4211.  We SQL F4211 with actual ship date, added appropriate location and lot, ran through sales update hoping it would grab the F4111 record and update with invoice #, gl date, etc, but instead it wrote a new record to F4111.  What is best option to fix so that we don't have duplicate hits to F4111?  Thinking we may need to delete the original F4111 record since there is no F41021.

Not sure of root cause for the failure to update all tables related to original P4205 - session may have been dropped midstream, or failed to commit due to asynch.  Have not been able to duplicate.

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