Hey ezijderveld,
Because of the nature of our business and how Oracle had been flip flopping with how these function worked we ended up using a company # specific modifcation to get around all the garbage.
Hope this helps!
Functions - B4000350, B4000351
See below for our communications with Oracle.
Problem Description: Provide a detailed statement of the issue, include when it started, error number/ID, and message.:
When using DMAAI 4122 and performing inventory transactions, the business unit on the GL post using the MCUS from the F0006 instead of the MCU if the MCUS is popluated. Is there a way to ignore the MCUS.
Provide the steps to reproduce your issue.:
1. Create Business Unit with MCUS populated
2. Ensure DMAAI 4122 transaction type set-up properly and has the business unit field blank.
3. Create Inventory transaction and post.
Provide the environment (e.g., test, development, or production) where the issue occurs.:
ALL
Describe any workaround you are using to avoid this issue.:
Created batch version to re-allocate costs to MCU instead of MCUS.
Program ID/Object:
P4112,3,4
Application Release:
8.11 SP1
Tools Release:
8.96
Can you easily recover from, bypass or work around the problem?:
No
Does your system or application continue normally after the problem occurs?:
Yes
Are the standard features of the system or application still available; is the loss of service minor?:
Yes
Oracle Support - January 9, 2009 2:07:04 PM GMT-07:00 [Notes]
Is this the first time this has happened or does this always happen? If this is the first time, what has changed in your environments?
Can you send me screen shots of your 4122 AAI setup and your Business Unit setup?
Oracle Support - January 9, 2009 3:18:53 PM GMT-07:00 [Notes]
Hi Mike -
I found SAR 4778119 that states that the system is working as designed. Here is the disposition of that SAR:
Rules used in assigning business unit during distribution
AAI retrieval (B4000350) are as follows:
.
1. Use BU that is in AAI table.
2. If BU in AAI table is blank, than use project number
(MCUS) from business unit master table (F0006).
3. If project number is also blank, then use branch/plant
passed into the BSFN.
. Project number in business unit master
designates parent business unit of a business unit. For
example, if B/P M30 has project number 5100, then all M30's
transactions will be logged to B/P 5100 instead of M30. This
feature enables parent child relationship between multiple
projects (i.e 5100 <- M30 ) during JEs.
( <- M20 )
Therefore, expecting child BU to be used for PO transactions
when child BU has a associated project number is incorrect.
If this is not a desired result, then removing project
number from P0006 will resolve the issue.
SAR 7480238 states the same, the system is functioning as designed.
Thanks you.
