Emergency: Affecting 100 people,Acct cant enter into the SAP &Cant select the BR Acct table as key

[frezhang]

The Brazilian National Public Cloud System has activated the local Brazilian chart of accounts. As a Brazilian group company, the Chinese entity must map its group-level accounts to the system to align with the local Brazilian accounts (maintaining two sets of accounts: one for the group and one for Brazil). 1. When configuring the chart of accounts, the Brazilian company's operational accounts are automatically assigned the YCOA standard. The YCBR Brazilian chart of accounts serves as an alternative chart of accounts (the system should designate which accounts belong under the group-level chart and which under the local Brazilian chart).

[MOHAMMED_BASER · Accepted solution]

Hi @frezhang ,
Please start by checking OBY6 company code parameters — that’s the most common reason why the BR chart of accounts cannot be selected. Following action must be taken to fix the issue.

Check Company Code Settings (OBY6), Ensure the Brazilian company code has, Chart of Accounts: YCOA and Alternative Chart of Accounts: YCBR

Verify Chart of Accounts Definition (OB13), Confirm YCOA and YCBR are both defined and ensure YCBR is flagged as alternative.

Map Accounts (FS00 / FS02):
For each operational account in YCOA, assign the corresponding YCBR account in the Alternative Account Number field.

Authorization Check, Run SU53 for affected users to see missing authorizations. Ensure roles allow access to BR account table.

System Sync, If this is in the Brazilian National Public Cloud, confirm that the integration layer is active and synchronized.

Establish a mapping table between YCOA ↔ YCBR for all accounts.
Automate assignment during account creation.
Train users to maintain both sets of accounts consistently.
Document the configuration in SAP Solution Manager for audit compliance.

[erickgoulardt · Accepted solution]

Hello Baser, I hope it's all right. I am accepting the response offered to our customers, which is the root cause of the problem described. Thank you for contributing to our community. 🙂 Best Regards, Erick Goulardt SAP Support