My Oracle Support Banner

E1: 31A: When AAI BU Exist In Different Company R31802A Writes IM KCO Wrong Company (Doc ID 2511305.1)

Last updated on JULY 16, 2021

Applies to:

JD Edwards EnterpriseOne Shop Floor Control - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

When a setup exist where the AAI Tables 3120, 3110, and 3130 are setup with a Branch Plant / Business Unit that exist in a different Company than the Branch Plant / Business Unit in the Work Order Charge To Cc field, and the P3111 Item Part List issuing Branch Plant / Business Unit field. The R31802A writes the F0911 IM Journal Entry where Field DOC CO (KCO) is populated with the incorrect company, while the IC DOC CO (KCO)field is populated with the correct company.  This causes an integrity issue for the IM JE’s when running the R41543 Item Ledger/Account Integrity because the Cardex DOC CO (KCO) was written to the company based on the P3111 / F3111 issuing Branch Plant / Business Unit, while the F0911 DOC CO (KCO) for the IM was written based on the Branch Plant / Business Unit entered in the AAI’s.

Steps To Duplicate:

  1. Create a Parent Item and Component in the Item Master and Item Branch M30 G/L Class Code IN30. i.e. Parent 2719 and Component 2719C.
  2. Create P4105 records for the Parent item and component Sales /INV 07 Purchase 08.  Give the component 08 Purchase Cost of $2.00
  3. Create a P3002 BOM for the Parent item 2719 with the Component 2719C on the BOM Qty 1
  4. Run the R30812 Cost Simulation and R30835 Frozen Cost update to Freeze standard cost for both items.
  5. Go to menu G09411 / P0006 Review and Revise Business Units and confirm that i.e. BU M30 exist in Company 200 and BU DSBLK exist in Company 00001.
  6. Go to menu G09411 / P0901 Review and Revise Accounts and make sure the following accounts exist for M30 and DSBLK. i.e. DSBLK.1710, DSBLK.1411, and M30.1710, M30.1411   
  7. Go to DMAAI’s and setup 3120, 3110, and 3130 AAI’s with the account strings.  i.e.

3120 AAI = Company 200, GL Class IN30, Order Type WO, Cost Type A1, Branch Plant DSBLK, Object 1710.

 

3110 AAI = Company 200, Doc Type IM, GL Class IN30, Order Type WO, Cost Type A1, Branch Plant DSBLK, Object 1411

 

3110 AAI = Company 200, Doc Type IM, GL Class IN30, Order Type WO, Cost Type A1, Branch Plant DSBLK, Object 1411

 

3130 AAI = Company 200, Doc Type IC, GL Class IN30, Order Type WO, Cost Type A1, Branch Plant DSBLK, Object 1411

  1. Go to menu G3111 / P48013 Work Order Entry and enter a WO for i.e. Qty 10, Branch Plant M30 and Charge To Cc M30.  Attach Part list and ensure the components issue from Branch Plant is also M30
  2. Now do P31113 issues and issue component to work order, P31114 completion and Complete the work order.
  3. Go to Menu G3116 / R31802A Manufacturing Accounting Data Select on the Work Order and run in Final mode. Check PDF to ensure IC and IM Journal entries were created without error and used correct accounts for IM and IC beginning with BU DSBLK as expected. Notice Company on PDF is 200, and Make Note of Batch Number.
  4. Databrowse the F0911 for the Batch number and notice the Following:

IC Company for field DOC CO (KCO) = 200 for 3130 debit and 3120 credit AAI’s

IM Company for field DOC CO (KCO) = 00001 for 3120 debit and 3110 credit AAI’s ( This is incorrect and will cause integrity issues between the F0911 and Cardex when R41543 is run)

 

Also Note:

IC Company for field CO (CO) = 00001 for 3130 debit and 3120 credit AAI’s which is field / company used when posting to F0902

 

IM Company for filed CO (CO) = 00001 for 3120 debit and 3110 credit AAI’s which is field / company used when posting to F0902

 

The CO (CO) company is correct for both the IC and IM and will post without error to the F0902 when R09801 is.

 

Note: This can be duplicate in E1 9.1 and 9.2

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.