CONFIGURATION WORKBENCHLegal entity, posting control, and reporting proof

R2R 404 · COMPANY CODE

Company Code Configuration Workbench

Use the Company Code as the legal accounting boundary. Configure only after its ownership, currencies, fiscal calendar, operational assignments, and reporting obligations are understood.

LEGAL ENTITY

Define the Company Code in OBY6

Maintain the legal entity name, address, country, language, local currency, and fundamental Company Code settings.

SPRO / IMG path

Enterprise Structure → Definition → Financial Accounting → Define, copy, delete, check Company Code.

Transactions and apps

OX02 / OBY6Define the Company Code and maintain global parameters

OB13Maintain the operating chart of accounts

Decide and maintain

Confirm the legal entity, country, statutory currency, chart of accounts, and permitted accounting principles.
Record the accountable Finance owner and the scope of local tax, reporting, and localization requirements.
Keep the legal boundary distinct from operational branches, departments, plants, and profit centers.

EXPECTED PROOFThe Company Code has one credible legal identity and can accept only the intended accounting context.

FAILURE CHECK

Country, currency, statutory owner, or chart of accounts must be repaired manually after the first controlled posting.

OBY6 FIELD MAP

Read global data by control purpose

The exact fields available depend on release, localization, and activated scope. Use the field groups to ask the right design question before treating any setting as universal.

Identity and localization

Company Code, country, local currency, language, address, and VAT registration identify the legal accounting context and its local obligations.

Accounting foundation

Operating and alternative charts of accounts, fiscal-year variant, and productive status establish the accounting structure and permitted lifecycle state.

Processing control

Field-status and posting-period variants, exchange-rate tolerance, workflow, and fiscal-year proposal settings shape how a posting can be entered and when it is permitted.

Conditional features

Credit control, Funds Management, Asset Accounting, tax reporting, and other switches must be assessed against the approved solution design rather than activated as defaults.

ENTERPRISE STRUCTURE

Attach operational organizations

Plants, purchasing organizations, sales organizations, and controlling assignments must operate beneath a coherent legal accounting boundary.

Design the assignments

Assign each Plant to the Company Code that owns the resulting inventory and operational postings.
Connect Purchasing and Sales organizations only where their commercial activity is legally and financially intended to post.
Validate controlling-area compatibility before assigning cost and profit responsibility.

EXPECTED PROOFA purchase, production, and sales example derive the intended Company Code without cross-entity repair.

FAILURE CHECK

An operational document derives the wrong entity, currency, or controlling context.

POSTING CONTROL

Set fiscal and posting-period control

Fiscal year, posting-period variant, ledger settings, and account controls decide when and how the legal entity may record a business event.

Key settings

Financial Accounting → Financial Accounting Global Settings → Ledgers → Fiscal Year and Posting Periods.

Transactions

OB29 / OB37Maintain and assign fiscal-year variants

OB52Open and close posting periods

FINSC_LEDGERMaintain ledger and currency settings

Prove fiscal periods

Assign a fiscal-year variant that matches the statutory calendar and any approved year shift.
Assign and protect the posting-period variant; distinguish controlled operational period opening from design transport.
Test a valid period, a closed period, and an adjustment-period scenario with the intended account type and authorization.

EXPECTED PROOFA valid journal posts to the intended ledger and period; a closed or unauthorized period is rejected with an explainable message.

FAILURE CHECK

Period access is opened too broadly, ledger currency is unexpected, or a source document posts outside the intended legal period.

STATUTORY REPORTING

Produce statutory accounts

Company Code reporting brings journals, local currency, fiscal calendar, tax, closing evidence, and financial-statement structure together for the legal entity.

Define the reporting proof

Agree the financial-statement version, ledgers, currencies, reporting principles, and close ownership.
Trace material balances from source documents through the Universal Journal into the statutory statement lines.
Reconcile subledgers, inventory, assets, tax, and open items before approving the period.

EXPECTED PROOFStatement balances reconcile to the journal and the legal entity can explain its local currency, period, and accounting basis.

FAILURE CHECK

Financial statements require unexplained manual journals or cannot be reconciled to source and ledger evidence.

MANAGEMENT AND SEGMENT REPORTING

Report by business segment

Profit Center is an internal reporting and PCA balance-sheet dimension beneath the Company Code; it is not a replacement legal entity.

Preserve the distinction

Define the Profit Center hierarchy and mapping to reportable management or IFRS business segments.
Test derivation through sales, material, plant, production, cost, and service activity into the Universal Journal.
Reconcile profit-and-loss and balance-sheet dimensions by Profit Center back to the Company Code statutory total.

EXPECTED PROOFPCA reporting explains profit, assets, receivables, payables, and inventory by business segment while reconciling to the legal entity.

FAILURE CHECK

Segment reporting is treated as a separate legal ledger or financial dimensions are missing from the intended postings.

CONTINUE THE PATHTrace the full accounting configuration spine

Use the R2R workbench for ledger, journal, source-integration, reconciliation, and close controls.

Open R2R configuration