Mapping Set based on purchasing category and project synthetic value (project parent value)
Summary:
Our customer uses Oracle Purchasing to manage their procurement process.
Regarding the derivation of the account segment from the charge account combination, it is being derived based on the respective item purchasing category and the project (analytical value from the COA) chosen by the user.
Since it can be a large rule, considering the combination of all categories and projects, then it was asked about the possibility to change the TAB setup to derive the account based on the purchasing category and project synthetic value. Thus, instead of using project analytical value, use the respective project synthetic value defined in the General Ledger module.
Tagged:
0