Using value sets with table validation for segments of the Accounting Key Flexfield
Content
We have a CoA segment to capture the project number from Project Costing transactions. Whilst it is usually not considered best practice to have a project segment in the CoA we are inheriting this from legacy ERP. In parallel, we're implementing the project number as a supporting reference in SLA (with balance tracking) for future use, but for now we have to migrate the project segment to the CoA as removing it will be too impactful.
As projects are defined in Project Foundation, we want to use a value set for the Accounting KFF segment that has table validation. This will remove the extra effort in creating a project value in an independent value set every time a new project is created.
3