E1: 41: How to Update an Incorrectly Entered G/L Class Code at the Item Branch Plant Level
(Doc ID 2719456.1)
Last updated on OCTOBER 13, 2020
Applies to:JD Edwards EnterpriseOne Inventory Management - Version 9.2 and later
Information in this document applies to any platform.
A new item was set up in item master and item branch and incorrectly classified with the wrong G/L Class Code. Then R41826 - Item Branch Duplication was run to update all branches with the incorrect G/L Class Code in both the item master (F4101) and the item branch (F4102).
The user subsequently changed the G/L Class Code on the item master, but not the item branch record which is the driver for the accounting used.
Transactions have since been completed in some, but not all branches.
What is the impact of changing the G/L Class Code in the two following scenarios:
1. Change G/L Class code in item branch plant for all branches?
a. What are the potential integrity issues of making the change after transactions have been posted?
b. Can this be completed once transactions have been done?
c. How does Oracle recommend this change be made with the least amount of impact and integrity risk?
2. Change G/L Class Code in item branch plant for only those branches that had transactions
a. What are the potential integrity issues of having different G/L class codes depending on the branch plant?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document