Move Orders Form (INVTOMAI) Showing Unexpected Balancing Segment Values For Destination Account (Doc ID 1681057.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Inventory Management - Version 12.1.3 and later
Oracle Cost Management - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On release 12.1.3:

When creating Requisition move orders through the Move Orders form (INVTOMAI) with Transaction Type as Move Order Issue, the form does not filter Accounts based on the Legal Entity.
For the balancing segment, the user is able to select a value that is not defined as Balancing Segment Value in Accounting Setups General Ledger page.

The problem does not occur in the Organization Parameters form. (INVSDOIO) where it works as intended.

-- Expectation
While transacting in Inventory Management application, users should not be allowed to enter accounts with other balancing segment value than the one(s) set in Accounting Setups page.

-- Steps
The issue can be replicated at will per the below steps:
1. Go to General Ledger Super User: (N) Setup > Financials > Accounting Setup Manager > Accounting Setups
Query on your ledger
In Legal Entities region, see a Balancing Segment Value is associated to the legal entity associated to your ledger
2. Go to Inventory: (N) Move Orders : Move Orders
Create a move order with Transaction Type as Move Order Issue
Open the list of values for field Destination Account in the header block
In the Accounting Flexfield window, open the list of values for the balancing segment
See all values show up whereas you would expect to see only the above value
3. Go to Inventory: (N) Setup : Organizations : Organization Parameters
Go to Inter-Org Information tabbed region and open the list of values for Transfer Credit account (for instance)
See the list of values for the balancing segment is just showing the value of step 1 as expected

-- Business impact
Due to this issue, incorrect accounts get stamped on Move Order Issue transactions (and other) and a data fixes like the one <Document:781480.1> need to be applied.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms