SAP Error – G/L Account 13600000 Not Extended to Company Code ZR01

It’s a common SAP posting issue when you encounter the error “G/L Account 13600000 Not Extended to Company Code ZR01” during a goods receipt. This means the account isn’t activated for your company code, blocking transaction completion. The GR/IR clearing account may trigger a separate but related extension error even in the same MIGO session. Failure to extend required accounts can halt financial postings. Use transaction FS00 to verify and extend the account to ZR01, and always check related accounts in advance to prevent repeated errors.

Key Takeaways:

• The error “G/L Account 13600000 Not Extended to Company Code ZR01” means the general ledger account exists in the chart of accounts but is not activated for use in company code ZR01. This prevents posting transactions in modules like MM during goods receipt, even if the account is otherwise valid.
• GR/IR (Goods Received/Invoice Received) clearing accounts often trigger this error separately from other G/L accounts during the same MIGO session because they are posted in a distinct accounting step-typically after the inventory account. The system evaluates extension for each account individually, so missing extension on the GR/IR account appears as a second, independent error.
• To resolve, use transaction FS00 to extend G/L account 13600000 to company code ZR01 by entering the company code-specific data like account currency and reconciliation settings. Before posting, check if other key clearing or inventory accounts used in the process-especially those tied to valuation-are also extended to prevent cascading errors.

The Broken Session

When you encounter the Error Message ‘G/L account is not defined for company code’ during a MIGO transaction, it may seem like a repeat of the earlier issue-but this time it’s the GR/IR clearing account failing. This error appears separately because SAP validates accounts at different stages of the posting process. Even if you fixed account 13600000, the system halts again when it reaches the GR/IR account, which also must be extended to company code ZR01. Use transaction FS00 to extend it-and check all related clearing and offsetting accounts now to prevent repeated interruptions.

The FS00 Repair

When you encounter the GR/IR clearing account extension requirement, it appears separately from the initial G/L account error-even during the same MIGO session-because SAP validates company code extensions individually per account. You must use FS00 to extend G/L Account 13600000 to company code ZR01, ensuring all necessary ledgers and fiscal variants are correctly assigned. Failure to check related accounts like GR/IR beforehand may trigger repeated errors, so review the complete posting template or document flow to preemptively extend all involved accounts in one pass. This prevents serial interruptions and maintains processing momentum.

The Preventive Look

Every time you encounter the “G/L Account 13600000 Not Extended to Company Code ZR01” error during a MIGO session, recognize that the GR/IR clearing account may trigger a separate but related issue even if you’ve resolved the initial G/L account problem. This happens because SAP validates each account independently during document posting. To prevent repeated errors, use transaction FS00 to extend all necessary G/L accounts, including GR/IR, to the relevant company code upfront. Check your valuation classes and movement types to anticipate which accounts will be hit, so you’re not fixing them one by one. Learn more about handling the G/L account not extended to Company Code issue from real user experiences.

To wrap up

On the whole, you encounter the SAP error “G/L Account 13600000 Not Extended to Company Code ZR01” because the account lacks configuration in that specific company code, often surfacing during transactions like MIGO. The GR/IR clearing account may appear separately due to distinct account determination rules. You must extend the account via FS00 and verify all relevant company codes are included. Review your account determination in OBYC and ensure all required G/L accounts are pre-extended to avoid repeated errors. For detailed guidance, refer to 3576723 – Issue when extending G/L Account to Multiple ….

FAQ

Q: Why does the error ‘G/L Account 13600000 Not Extended to Company Code ZR01’ occur during MIGO?

A: This error appears when the system tries to post a transaction involving General Ledger account 13600000, but that account has not been activated or configured for use in company code ZR01. In SAP, every G/L account must be explicitly extended to each company code where it will be used. If the account exists in the chart of accounts but is missing in the company code view, the system blocks the posting to prevent inconsistent financial data. This commonly happens after new company codes are created or when accounts are added without full rollout across all relevant company codes.

Q: Why does the GR/IR clearing account show a similar extension error even though it wasn’t mentioned in the first error message?

A: The GR/IR (Goods Receipt/Invoice Receipt) clearing account is used automatically during MIGO when posting goods receipts for purchase orders with invoice verification enabled. Even if the first error involves a different G/L account, the system processes multiple accounts in sequence during the same transaction. Once the initial G/L account issue is resolved, the system proceeds and then encounters the next missing configuration – the GR/IR account not being extended to company code ZR01. These errors appear separately because SAP validates each account at the point it is accessed in the posting logic, not all at once.

Q: How do I fix the missing G/L account extension using FS00?

A: Use transaction code FS00 to open the G/L account master data maintenance screen. Enter the account number (e.g., 13600000) and the chart of accounts key. Click on the “Create/bank/interest” tab, then switch to the company code tab and enter ZR01. If the account is not extended, you will need to create the company code segment by filling in required fields such as account currency, tax settings, and reconciliation account flag if applicable. Save the entry to complete the extension. Repeat this process for the GR/IR clearing account if it is also missing.

Q: What should I check to avoid encountering more G/L account extension errors one after another?

A: Review the complete list of G/L accounts used in the transaction by checking the posting document’s expected line items, such as inventory accounts, input tax, GR/IR, and vendor clearing accounts. Use transaction S_ALR_87012179 (G/L Account Balances) filtered by company code ZR01 to see which accounts already exist in that company code. Cross-reference with the chart of accounts (FBL3N with no company code filter) to identify gaps. Also, verify the OBYC settings for automatic posting configurations, as these define which accounts are triggered during MIGO. Ensure all accounts referenced in OBYC are extended to ZR01.

Q: Can I extend multiple G/L accounts to company code ZR01 in bulk instead of one by one?

A: Yes, you can use transaction FBD1 to create G/L account master records in bulk for a company code. Enter the chart of accounts and company code ZR01, then input a list of accounts that need to be extended. You can also use LSMW or custom ABAP programs for larger-scale extensions, especially during system rollouts or new company code setups. Before using bulk methods, validate the account data (currency, reconciliation flags, tax settings) to ensure consistency. Always test in a development environment first to avoid incorrect configurations in production.