Activate Document Splitting

SAP Best Practices Baseline Package (China)

SAP Best Practices

Scenario Overview 1
Purpose and Benefits
Purpose

The online split is provided with the new General Ledger Accounting. Documents are enhanced with additional account assignment objects, or additional postings are done which split the original postings into lines referring to the account assignment objects. Account assignment objects can be defined according to selected dimensions. In SAP Best Practices the dimensions are profit centers and segments.

Benefits

The postings are done in real time (online). It is possible to draw up complete financial statements for the selected dimensions at any time (segment reporting).

Scenario Overview 2
SAP Applications Required

SAP ECC 6.0 EhP3

Company roles involved in process flow

Finance Manager General Ledger Accountant

Key process flows covered

Find or create a document whose G / L Account with Different Segments Check and display assignment profit center and segment

Scenario Overview 3
Detailed Process Description
Activate Document Splitting
The online split is a feature in the new general ledger accounting which does not lead to own processes or separate scenarios. SAP Best Practices provides an example how to check the segment and profit center assignment in general ledger documents.

Key Points to activate online split Install other building blocks which require the online split (e.g. Baseline: Cost of Sales Accounting scenario and Segment Reporting scenario).

The online split is provided with the new General Ledger Accounting. The online split is based on segments. The online split must be activated before the start of postings in the client. Postings done before can cause subsequent online split errors (see also note 891144).

Process Flow Diagram

Activate Document Splitting
G / L Account Document with Different Segments

Event

Reporting

Finance Manager / General Ledger Accountant

Check and display assignment profit center and segment

Legend
Symbol Description Usage Comments
Role band contains tasks common to that role.

Symbol

Description

Usage Comments

<Function>

Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role. The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario. External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.

Diagram Connection

To next / From last Diagram: Leads to the next / previous page of the Diagram

Flow chart continues on the next / previous page

Hardcopy / Document

Hardcopy / Document: Identifies a printed document, report, or form

External to SAP

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. Flow line (dashed): Line indicates flow to infrequentlyused or conditional tasks in a scenario. Line can also lead to documents involved in the process flow. Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario

Connects two tasks in a scenario process or a non-step event

Financial Actuals: Indicates a financial posting document

Financial Actuals

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Business Activity / Event

Does not correspond to a task step in the document

Budget Planning: Indicates a budget planning document

Budget Planning

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario

Corresponds to a task step in the document

Manual Process: Covers a task that is manually done

Unit Process

Manual Proces s
Process Reference: If the scenario references another scenario in total, put the scenario number and name here. Corresponds to a task step in the document

Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow. Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines

Process Reference

SubProcess Reference

Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here

Corresponds to a task step in the document

Existing Version / Data

Existing Version / Data: This block covers data that feeds in from an external process

Proces s Decisio n

Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond.

Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution

System Pass/F ail Decisio n

System Pass / Fail Decision: This block covers an automatic decision made by the software

Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.