Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Why do we have to create SLA Rules for Secondary Ledger

in General Ledger & Intercompany 3 comments

Summary:

Why do we have to create SLA Rules for Secondary Ledger

Content (required):

We have a Primary and a Secondary Ledger, which is configured to transfer data at Sub Ledger level. The difference between the two ledgers is that we have a different COA in Primary and in Secondary.

We have created few SLA rules in AP, in AR and in TAX sub modules to ensure we have the correct BSV during the accounting of the transaction and to avoid any unwanted IC entries. This is all working as expected. No issues or problems. But when the accounting entries are created in the Secondary, it does not create the identical accounting but includes erroneous BSV and all unwanted IC entries. Why is that please? Why cannot Secondary ledger inherit the same accounting string that is being sent by Primary? This is resolved as soon as we implement identical SLA

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!