Last updated on MAY 19, 2017
Applies to:JD Edwards EnterpriseOne Product Data Management - Version XE and later
JD Edwards EnterpriseOne Requirements Planning - Version XE and later
Information in this document applies to any platform.
Information Center: Overview of JD Edwards EnterpriseOne Product Data Management > Information Center: Troubleshooting JD Edwards EnterpriseOne Product Data Management > Document 828438.1 and Information Center: Overview of JD Edwards EnterpriseOne Requirements Planning > Information Center: Troubleshooting JD Edwards EnterpriseOne Requirements Planning> Document 828438.1
The Low Level Code (LLX) is different in one Branch Plant from another Branch Plant record for the same item. LLX should be the same in every Branch Plant for any specific item.
Corrupted LLX values may have no effect or may cause unexpected results. The following is one example of an error caused by LLX being different between the Supply and Demand Branch Plants:
The LLX values were reviewed and found to be different between two branch when Multi-plant MRP (R3483) was generating OP messages when OT messages were expected for a small percentage of the total items processed in a Net-Change mode run. The items that were in error were independent demand items which had been used as components in the past so their LLX was not = 0 and they had different LLX in the supply branch from the demand branch.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms