My Oracle Support Banner

Account Rule Within Purchasing TAD Is Not Deriving Segment Value Based On Project (Doc ID 2184833.1)

Last updated on FEBRUARY 04, 2019

Applies to:

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

Symptoms

On : 11.1.11.1.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'
 

STEPS
-----------------------
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.

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
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.