Mapping Set for Item Does not Default Defined PO Charge Account
Last updated on JANUARY 31, 2017
Applies to:Oracle Fusion Purchasing - Version 220.127.116.11.0 and later
Oracle Fusion Purchasing Cloud Service - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
When trying to set up default PO Charge Accounts for expense items following <Document 1403960.1> the PO Charge Account is not defaulting any defined values from the mapping set besides the default one.
The issue can be reproduced at will with the following steps:
1. Set up a Mapping Set by item.
2. Use the same item when creating a PO.
3. See that the wrong PO Charge Account is being defaulted.
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