For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Our company has made an acquisition. We have setup new company code (balancing segment). We have setup new company, new legal entity, new natural accounts, new cost centers, code combinations so we can upload account balances, activity each month of the sub and report consolidated financials.
We upload journal balances (Trial Balance) each month of the acquired subsidiary, which we can do with the above setups.
However if we want to prevent users from this subsidiary company code to create any transactions in PO, AP, AR, Cash, Fixed Assets, Expenses, Project sub ledger inadvertently. How do we prevent these? We want to retain ability to enter/upload journal in GL only but do not want to allow posting in GL from any sub ledgers.
Is there any creative and simpler way to setup sub ledger accounting rules to accomplish the above?
Comment
hi,these subsidiaries Shouldn't setup submodules.
Simultaneously ,enabling bsv value set security can prevent this situation
regards
Be the first to rate this
|
Sign in to rate this
I will look into BSV value set security. Sub Modules are already set. It's just that except GL, there should no other seeded source of transactions from other sub ledgers such as PO, AP, AR, Cash, Fixed Assets, Expenses, Project sub ledger inadvertently use the company code setup for this subsidiary.
Be the first to rate this
|
Sign in to rate this