The standard variant K4 is based on a calendar year (Jan-Dec). Since the client’s fiscal year starts in February, a custom variant (like Z1) must be created where the first posting period (e.g., 001) corresponds to February. This correctly maps the 12 periods to the client’s unique fiscal calendar.

Even with correct master data and configuration, depreciation cannot post to a period that is closed. Transaction OAAQ or the corresponding app must be used to open the depreciation posting period for the current month before executing the depreciation run (AFAB). This is a critical step in the periodic closing process.

Transaction KKBC_KO (or its Fiori equivalent, ‘Analyze Production Variances’) is specifically designed to analyze the variances of production orders and process orders. It breaks down the total variance into categories like input price, resource usage, and output price variances, and can display them by cost component, providing the detailed insight needed.

In parallel accounting, ledgers are assigned to a company code. When a posting is made, the system automatically replicates the posting to all active ledgers assigned to that company code, ensuring consistency. The accounting principles (e.g., IFRS, local GAAP) are managed through different valuation approaches or parallel accounts within this framework, not by separate manual postings.

A cost center master record has a ‘Lock for Posting’ indicator. If this is set during a certain validity period (even if the cost center is technically active), the system will prevent any new postings to it. This is a frequent cause of issues and is checked in the cost center master data (transaction KS02).

Node types are crucial in FSV configuration. They define the source of data for each row. Key types include ‘I’ for items (directly from G/L account balances), ‘M’ for manual entry, ‘T’ for text, and ‘C’ for calculation rows (to add or subtract other rows). This determines the arithmetic and logic behind the final financial statement figures.

The three-way match is key. The obligation (commitment) becomes a liability only upon invoice verification. Invoice receipt (MIRO) performs the critical accounting entry: Debit the GR/IR clearing account (which was credited at goods receipt) and Credit the vendor liability account. This settles the GR/IR interim account and formally records the payable.

A primary historical challenge was reconciling the total costs and revenues in Finance (FI) with the cost accounting details in Controlling (CO). Since every relevant posting now writes a single line item to ACDOCA with all accounting and controlling dimensions (like cost center, order, profit center), the data is inherently reconciled. This significantly speeds up the closing process.

Assessment is a cost allocation method in CO that uses a fixed percentage or equivalence number (like square meters, headcount) to distribute primary costs from one or more sender cost centers to multiple receiver cost centers (or other objects). It is executed periodically via a cycle (transaction KSU5) and is ideal for allocating shared service costs like rent, utilities, or IT.

The standard variant K4 is based on a calendar year (Jan-Dec). Since the client’s fiscal year starts in February, a custom variant (like Z1) must be created where the first posting period (e.g., 001) corresponds to February. This correctly maps the 12 periods to the client’s unique fiscal calendar.0