Global Settings represent the system-wide rules, parameters, and variants that govern how financial transactions are processed, recorded, and controlled across all assigned company codes. Their importance cannot be overstated, as they ensure consistency in financial data, compliance with accounting principles, and the automation of core accounting operations. Mistakes in these foundational settings can have far-reaching consequences, often requiring significant effort to correct once transactional data is live. Therefore, meticulous attention to detail during this phase is non-negotiable.

2.1 Fiscal Year and Posting Period Variants

2.1.1 Maintaining the Fiscal Year Variant

The Fiscal Year Variant defines a company’s financial year, specifying its posting periods and any special periods used for year-end closing activities. A company’s fiscal year can either align with the calendar year (January-December) or be defined differently (e.g., April-March).

Creation is handled via the SPRO path: SPRO → Financial Accounting → Financial Accounting Global Setting → Fiscal Years → Maintain Fiscal year variant

Key configuration options include:

• Year-Dependency: This checkbox is selected if the start and end dates of the fiscal year change from one year to the next.
• Calendar Year: This checkbox is selected if the fiscal year aligns with the standard calendar year.
• Number of Posting Periods: The total number of regular accounting periods (typically 12).
• Number of Special Periods: The number of additional periods used for closing adjustments (up to 4).

2.1.2 Defining and Managing Posting Period Variants

The Posting Period Variant is a powerful control mechanism that determines which accounting periods are open for posting transactions. Its primary function is to prevent erroneous entries in closed accounting periods, thereby protecting the integrity of financial data.

1. Define Variant: First, a unique 4-digit variant code and a descriptive name are created using the SPRO menu path: SPRO → Financial Accounting → Financial Accounting Global Setting → Document → Posting Periods → Define Variant for open Posting Periods
2. Open and Close Periods: Next, the periods are managed using the “Open and Close Posting Periods” transaction. This is where the specific rules are defined. The table below illustrates the structure for this configuration and explains the purpose of each column.

• Var.: The 4-digit variant code being configured.
• Account Type: Specifies the type of account the rule applies to. Key types include A (Assets), D (Customers), K (Vendors), M (Materials), S (General Ledger), and + (Valid for all account types).
• From Per.1 / To Period: Defines the range of regular posting periods that are open.
• Year: The fiscal year for which the period range is valid.
• Authorization Group: Can be used to restrict posting in certain periods to a specific group of users.

2.2 Field Status Configuration

2.2.1 Defining the Field Status Variant

A Field Status Variant is a collection of Field Status Groups. It acts as a container for rules that control which fields are Suppressed, Required, Optional, or Display Only during financial document entry.

Best Practice: As a non-negotiable best practice, you must create your Field Status Variant by copying the standard SAP 0001 variant. Never create one from scratch. This is a critical best practice because it ensures that all 41 standard field status groups are available as a baseline, preventing issues with standard transactions that expect these groups to exist.

2.2.2 Understanding Field Status Groups

The link between document entry and the G/L account is the Field Status Group. The Field Status Variant is assigned to the Company Code, the Field Status Group is assigned to the G/L Master Record, and together they dictate the data entry screen for any transaction posting to that specific G/L account. This provides granular control over data entry, ensuring that relevant information is captured while irrelevant fields are hidden.

• Suppress: The field is completely hidden from the user on the transaction screen.
• Optional: The field is visible, but data entry is not mandatory.
• Require: The field is visible, and the user must enter a value before the document can be saved.
• Display: The field is visible but greyed out; the user cannot enter or change the data.

2.3 Document Control Configuration

2.3.1 Defining Document Types

The Document Type is a key that classifies business transactions and controls how they are processed. Its purpose is multifaceted: it distinguishes between different transactions (e.g., a customer invoice vs. a vendor payment), assigns a specific number range to the document, and defines which account types are permitted for posting within that document. In practice, this means the Document Type acts as a primary control key for financial postings, ensuring auditability by segregating transactions and enforcing correct number sequencing.

Common Document Type Keys include:

2.3.2 Defining Document Number Ranges

Each Document Type must be assigned a Document Number Range. This ensures that every financial document created in SAP has a unique identifier. Number ranges can be either internal, where the system assigns the next available number sequentially, or external, where the user manually enters a number.

Using Transaction Code FBN1, a new number range interval is created by specifying the following:

• Number Range code: A two-digit code that links to the Document Type.
• Year: The fiscal year for which the number range is valid.
• From Number / To Number: The start and end numbers of the range.
• Ext checkbox: This is selected if the number range is for external assignment.

2.3.3 Defining Posting Keys

The Posting Key is a two-digit code that provides critical control over document line items. It determines three key attributes: the account type the line item can be posted to, whether the posting is a debit or a credit, and the field status of the line item screen.

The following table provides examples of standard Posting Keys:

With the global settings for document control and financial periods established, the next logical step is to configure the core of the financial system: the General Ledger.