Can't Get Accounts As Expected When Using AR Invoice Global Attribute As A Mapping Set Source.

(Doc ID 2249822.1)

Last updated on AUGUST 02, 2017

Applies to:

Oracle Fusion Receivables Cloud Service - Version and later
Information in this document applies to any platform.


Can't get accounts as expected when using AR invoice global attribute as a mapping set source.

Since the invoice receivable account can only be derived from the invoice header, and I can find the available mapping set source in SLA configuration is the transaction global attribute, so I want to use this source for test. The step is as below:

1. Open the transaction global attribute 4 as a DFF to store legal entity information.
2. Create an invoice and in the global attribute field,  LE.
3. Create a mapping set, use transaction global attribute 4 as input source.
4. Create an account rule.
5. Assign the account rule to the journal entry rule set.
6. Use the journal entry rule set in the accounting method.
7. Account draft to the invoice and view the account.

The expected result is both the debit and credit accounts in the invoice display 2216 as company code. But actually they still show the default value 2000 which was configured in the transaction type.

Account should be derived based on SLA customized setup.


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