Distribution - JDE1 (MOSC)

MOSC Banner

Could you please advise the root cause of the Invalid Commit that persist even after inventory relie

edited Aug 25, 2019 5:02AM in Distribution - JDE1 (MOSC) 1 commentAnswered

Could you please advise the root cause of the Invalid (False) Commit that persist in F41021.HCOM even after inventory relieved during sales order processing in JDE 9.1.

Why run R42995 repost report to correct them. Why cant the system itself avoid such occurrences without the need of R42995.

1. What causes the mismatch between F4211 and F41021. i.e. why there are instances where the F41021 has false hard committed quantities (HCOM.F41021) even though there are no valid corresponding data in F4211.

2. Also, is R42995 the very & only mechanism to refresh the sales commitments between F41021 and F4211.

3. Is it related to database connections/failure that causes the invalid commit for given item in F41021 even after the sales order is processed.

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

E1 Distribution Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center