Selecting Finance Settings, Building the Organizational Structure, and Configuring the Standard Order Type

Next, select the Fiscal Year Variant and Group Currency, which are applied to the entire system and cannot be changed after saving.

The Fiscal Year Variant (FYV) defines the relationship between the calendar year and the fiscal year. This selection defines how the system determines the posting period to assign when posting a journal entry. In accounting, you can have a fiscal year with a maximum of 16 posting periods, including special periods. The same FYV applies to your entire system with all its ledgers and company codes.

The Group Currency is the global currency that is applied to the entire system. A group currency allows you to compare amounts from different company codes in their respective currencies against one, overarching currency.

You can define the currency for each company code and ledger in the Product-Specific Configuration phase with the configuration activity, Define Currency Settings for Ledgers and Company Codes.

Learn how to specify the primary finance settings in this tutorial:

The Organizational Structure app identifies the required organizational entities in the Units to Create area. SAP Central Business Configuration determines the number of required entities based on the activated scope and selected countries or regions. The system also validates that all mandatory relationships between entities are defined. For example, every distribution chain must be assigned to at least one plant.

A dedicated Fit-to-Standard workshop should be conducted to define the customer's organizational structure. It is recommended that the partner's lead configuration expert facilitates this workshop, as they perform most system setup tasks in SAP Central Business Configuration, including the creation of the organizational structure.

The organizational structure uses the following relationship types:

• Tree relation: A country-specific parent-child relationship (1:n).

  Example: Mapping a Plant to a Legal Entity.

• Additional relation: A relationship between an organizational unit in a country-specific tree and another unit in the same tree or a global unit.

  These relationships have an n:n cardinality, meaning an organizational unit can be linked to one or several other units.

Local entities are assigned to specific countries and represent the highest level of the organizational structure.

The Company serves as the root node and can have one legal entity as a child node.

Under legal entities, you can add the following units:

• Sales Organization (for Sales & Distribution)
• Plant (for site logistics)

Global entities can be assigned to organizational structures across multiple countries.

For example, a Shipping Point can be assigned to several Plants located in different countries.

You can create the following global entity types:

• Distribution Channel
• Division
• Purchasing Organization
• Sales Office
• Shipping Point
• Shipping Point for Raw Materials
• Standard Shipping Point

The Organizational Structure app provides different views to create and adapt your structure:

• Graphic view: This view provides visual guidance by displaying available child entities with the label Create [org entity]. Clicking an entity opens a details screen. This view is ideal for users new to SAP Central Business Configuration, as it guides you through the setup process.
• Simplified mode: A streamlined version of the Graphic view. It shows the visual hierarchy but hides the creation buttons to maximize screen space. This is useful when managing multiple structures for different countries.
• Table view: Displays all organizational entities in a list format. This view is often the most efficient way to manage complex structures spanning many countries.

After maintaining the organizational structure, select Confirm in the top-right corner to finalize the entities and complete the activity.

Follow this tutorial to learn how to build an organizational structure:

There’s a growing need to manage configuration content easily without having to deal with underlying complexity. Configuration templates are specifically designed to mask the complex semantics, enabling you to create configuration content through intuitive, user-friendly interfaces.

For sales document types, you can use a configuration template to configure the standard order type. By copying configuration values from a standard order type, you can quickly create a custom sales order type.

This feature can be used to create similar order types in SAP Central Business Configuration and deploy them to SAP S/4HANA Cloud Public Edition for productive use and further configuration.

Adding an extra layer of flexibility to the creation process, the order type is initially saved as a draft when you create it. This means you can still delete it and start over if needed. Once you’re confident everything is correct, you simply confirm the order type and continue.

Configuring the standard order type allows you to create and deploy variants of customer-specific sales order types with low customizing and maintenance efforts. It helps you streamline the sales document type process with tailor-made sales order types.

Furthermore, it enables the Internal Sales Representative role to streamline operations by using a dedicated subset of preconfigured business process capabilities. Overall, this feature accelerates the configuration and implementation process.

Learn how to configure the standard order type in this tutorial:

After creating all required organizational entities and confirming them, you can complete the activity to deploy the scope and organizational structure.

Learn how to complete the scope and organizational structure activity in this tutorial:

If you need to activate an additional country/region or business process, you can use the Edit button located in the top right corner of completed activities.

SAP Central Business Configuration is used both during initial implementation and after go-live to maintain systems through future releases. This flexibility allows you to navigate backward and forward through project activities as requirements evolve.

For instance, after a new release, a customer might decide to activate additional business processes. They can log into SAP Central Business Configuration, open the relevant activity, and select Edit to return the workspace to the Scope phase.

After selecting the new processes for the desired countries/regions, they must proceed through the subsequent activities to re-confirm the settings. This ensures that background technical consistency checks verify all dependencies for the new processes are met.

A new business process may require a new organizational entity. If you attempt to complete the Deploy Scope and Organizational Structure activity without adding the required entity, the system will prompt you to add it before proceeding.

Additionally, in the Product-Specific Configuration phase, new configuration values may appear that require data entry for the processes to function correctly.

Learn how to use the Edit button in this tutorial: