Account Rule Within Purchasing TAD Is Not Deriving Segment Value Based On Project
Last updated on OCTOBER 10, 2016
Applies to:Oracle Fusion Self Service Procurement Cloud Service - Version 188.8.131.52.0 and later
Oracle Fusion Self Service Procurement - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Other Issues
Account Rule Within Purchasing TAD Is not Deriving Segment Value based on Project
Requirement is to update the purchasing transaction account rules to derive the project name within the projects segment of the requisition charge account
E.g. When requisition is charged against Project 'ABC' then the project segment in the COA shows value 'XYZ'
1. Created a mapping set to bring this value back
2. Assigned this to an account rule
3. Add to the TAD
4. Create requisition
5. Find that projects segment is not deriving the value in charge account.
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