PRC:PO: Import Purchase Orders: Charge Account Segment Values Entered In Import Template Are Being Ignored/Replaced By Charge Account From Transaction Account Definition (TAD)
(Doc ID 2887809.1)
Last updated on AUGUST 05, 2022
Applies to:
Oracle Fusion Purchasing Cloud Service - Version 11.13.22.04.0 and laterOracle Fusion Purchasing - Version 11.12.1.0.0 and later
Information in this document applies to any platform.
Symptoms
Import Purchase Order
ACTUAL BEHAVIOR
---------------
Import Purchase Order
Template is created with
Line Type = Goods
Destination Type = Expense
Project fields populated
Charge Account Segment Values populated
Segment values entered via Import Purchase Order (FBDI) are not being used. Instead the system is retrieving the Charge Account Combination from Transaction Account Definition (TAD).
EXPECTED BEHAVIOR
-----------------------
System to keep segment values entered viaImport Purchase Order (FBDI).
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Populate Import Template as follows
header
action = original
lines
Line Type = Goods
line locations
Destination Type = Expense
distributions
Charge Account Segments populated
Project fields populated
2. Run Load Interface Files for Import
3. Run Import Purchase Orders
4. Review Process Log, purchase order is created with success.
5. Review Purchase Order
Segment values are not retrieved, instead
Charge Account Combination from TAD is retrieved.
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 |