Seeded Project Segment Value Set Limitation for Project Transaction
Hi Team ,
I have a business requirment to use Project as a Segment in COA Structure. Reviwed Oracle has provided a value set ORA_PJF_PROJECT_NUMBER_COA as a solution.
Observed some limitations/restrictions,when try to Implement this seeded valueset . Table based value set , will not be eligible for hierarchy creation, segment value security and cross validation rules. But,these are common features used by businesses on their COA segment values.
Can you please advise in best solution for project Segment derivation for below scenarios.
- The Project should automatically added to the Value Set of the Project Segment. so that when ever the transactions are accounted the Project segment is derived automatically for the project.
0