SAP Error – G/L Account 39912000 Not Extended to Company Code ZR01
Account 39912000 is currently not extended to company code ZR01, which prevents posting and may cause critical financial reporting errors. You must extend the account to ZR01 in the chart of accounts to resolve this. For details on handling similar issues, refer to this Error Message ‘G/L account is not defined for company code’ discussion.
Key Takeaways:
- G/L account 39912000 is typically used in SAP IS-Retail for posting differences during goods movements, such as price variances between purchase orders and goods receipts; when this account is not extended to company code ZR01, postings related to inventory or invoice verification fail with an error.
- To identify which G/L accounts need extending when setting up a new company code, review the chart of accounts assigned to the company code and cross-check with accounts used in active business processes like inventory valuation, accounts payable, and cost of goods sold; transaction code S_ALR_87012326 (G/L Account Balances) or FBL3N reports from similar company codes can help pinpoint frequently used accounts.
- Extend G/L account 39912000 to company code ZR01 using transaction FS00: open the account master data, enter the chart of accounts key and account number, switch to the “Create/bank/interest” tab, input the new company code ZR01, fill in required fields like account currency, tax category, and reconciliation account assignment, then save to complete the extension.
Factors Influencing G/L Account 39912000 Usage
Account 39912000 is reserved exclusively for IS-Retail goods movements in SAP systems, ensuring accurate financial tracking during inventory transfers. Usage depends on proper extension to relevant company codes like ZR01. Incorrect configuration disrupts postings. Assume that failure to extend the account will halt retail-specific processes.
Role in retail inventory management
You rely on account 39912000 to record valuation changes during retail inventory movements. It ensures financial accuracy when goods shift between storage locations or stores. Without it, inventory valuations in IS-Retail environments become inconsistent and unreliable.
Impact on automated goods movement postings
Automated postings fail when account 39912000 isn’t extended to company code ZR01. The system cannot complete goods movement documents, triggering SAP error messages. Assume that missing account extension halts transaction processing in retail operations.
When account 39912000 is not extended to company code ZR01, every automated goods issue, receipt, or transfer in IS-Retail stops at the posting stage. The system requires this account to value inventory flows in real time, and without it, background jobs and batch processes generate errors instead of entries. You’ll see failed IDocs, blocked deliveries, and unposted transfer orders-directly impacting daily retail operations and month-end closing.
Tips for Identifying G/L Accounts Requiring Extension
- Review the Chart of Accounts at the client level to confirm which G/L accounts are active
- Identify mandatory accounts required for company code ZR01 initialization
- Use transaction code FS00 to check if an account like 39912000 is extended
Recognizing common pitfalls early can save significant troubleshooting time. For guidance, refer to this community discussion: Solved: G/L account does not exist in company code.
Reviewing Chart of Accounts at the client level
You must examine the Chart of Accounts configuration in the client to determine which G/L accounts are defined globally. This step reveals accounts that may not yet be extended to company code ZR01, preventing errors during posting.
Determining mandatory accounts for new company code initialization
Your setup requires specific mandatory accounts to be extended before transactions can run in company code ZR01. These include reconciliation accounts, tax accounts, and retained earnings entries tied to legal reporting.
Every new company code depends on predefined mandatory accounts such as the retained earnings account, profit and loss statement carriers, and balance sheet integrations. Without extending these to company code ZR01, financial statements will fail to generate and month-end closing processes will halt. Recognizing these dependencies early ensures a functional ledger structure from day one.
How-to Procedure for Extending Accounts via FS00
The FS00 transaction allows you to extend a G/L account like 39912000 to a new company code such as ZR01 by guiding you through master data replication. You’ll input the account number and assign it to the target company code, ensuring accurate financial reporting across entities.
Accessing the G/L account master record centrally
You begin by entering transaction FS00 in the SAP command field to access the global G/L account master record. This central view lets you manage chart of accounts data and initiate the extension to any company code, including ZR01, from a single interface.
Inputting the target company code ZR01
Type ZR01 in the company code field after opening account 39912000 in FS00. SAP will prompt you to create the account for this company code if it doesn’t exist. This step is important to enable posting activities in ZR01.
When you enter ZR01 as the company code for account 39912000, SAP checks whether the account is already active in that organizational unit. If not, the system triggers a creation workflow, pulling default settings from the chart of accounts while allowing you to customize company-specific entries. Failure to complete this step blocks financial postings in ZR01.
Maintaining company code specific data and saving
After assigning ZR01, you enter required company-level details like currency, tax settings, and field status. Once all mandatory fields are filled, click Save to activate account 39912000 in ZR01. This action enables live transactions in the new company code.
Company code-specific data for ZR01 includes local currency (usually EUR), tax jurisdiction code, and account currency settings, which must align with legal reporting requirements. Field status groups control which fields appear during posting, so correct configuration ensures data integrity. After verification, save the record using a valid authorization key-without this, the extension remains incomplete and the account cannot be used for posting in ZR01.
Final Words
On the whole, you must extend G/L Account 39912000 to Company Code ZR01 to meet the requirements for accurate goods movement postings. Without this extension, financial integration fails, leading to posting errors and misaligned ledger entries. You are responsible for ensuring the account is properly configured in the new company code environment.
FAQ
Q: What is G/L Account 39912000 used for in SAP IS-Retail goods movements?
A: G/L Account 39912000 is typically configured as a stock adjustment account in SAP IS-Retail environments. It records the value impact when goods are received, transferred, or returned between stores or warehouses. During goods movements like GR (Goods Receipt) or STO (Stock Transfer Order), if inventory values change due to price differences or valuation mismatches, this account captures the offsetting entry. It ensures accurate financial representation of stock in transit or revaluation scenarios. Without proper extension of this account to a company code, such as ZR01, the system blocks postings and raises an error.
Q: Why does the error “G/L Account 39912000 Not Extended to Company Code ZR01” occur?
A: This error appears when a financial transaction attempts to post to G/L Account 39912000 within company code ZR01, but the account master data has not been extended to that specific company code. In SAP, a G/L account must be individually activated for each company code where it will be used. If the account exists in the chart of accounts but lacks company code-level settings-like currency, tax details, or field status-SAP prevents any document posting. This commonly happens after creating a new company code or when integrating retail modules that rely on predefined accounts not yet extended.
Q: How can I identify which G/L accounts need to be extended to a new company code like ZR01?
A: To find required G/L accounts, start by reviewing the chart of accounts assigned to the company code. Use transaction code OB62 to see which accounts are already extended. For missing accounts, check integration points such as MM (Materials Management) or IS-Retail configurations where automatic account determination is defined. Transaction code OBYC helps identify G/L accounts used in automatic postings for inventory, invoice verification, or retail-specific processes. Run a simulation of key operations-like goods receipt or stock transfer-in a test environment to trigger missing account errors and compile a list. Cross-reference with standard retail account schemas to ensure all necessary accounts are extended before go-live.
Q: What is the step-by-step procedure to extend G/L Account 39912000 to company code ZR01 using FS00?
A: Open transaction FS00 in SAP. Enter the account number 39912000 and the chart of accounts key (e.g., INT or your custom chart). Click on “Create/bank/interest” or press Enter to open the account master data. If the account exists at chart level but not in ZR01, select the “Create” option for company code ZR01. Fill in mandatory fields: account currency (usually the company code currency), tax category (if applicable), and field status group. Set reconciliation account flags if needed. Save the entry. The system will confirm the account is now active for company code ZR01. Test by posting a sample goods movement to verify the error no longer appears.
Q: Can I automate the extension of multiple G/L accounts to a new company code?
A: Yes, you can use transaction FS00 with the “Mass Change” function to extend multiple accounts at once. Enter the range of G/L accounts used in IS-Retail, select the target company code ZR01, and apply standard templates for currency, tax settings, and field status. Another method is using SAP’s LSMW (Legacy System Migration Workbench) or direct input via batch input sessions for large-scale rollouts. Ensure consistency by validating entries against the account determination setup in OBYC and the retail financial configuration. Always test in a development system first and verify postings after extension.