Enterprise Structure

Overview

SAP Best Practices

Enterprise Structure
Baseline Package
Operating Concern 1000

This data is created in BB 101

Controlling Area 1000

Company Code 1000

Credit Control Area 1000

Personal Area 1000

Personal Area 1100

Purchasing Org. 1000

Sales Org. (Domestic) 1000

Sales Org. (Export) 1100

Pers. Subarea Pers. Subarea Pers. Subarea Pers. Subarea 1010 1020 1110 1120

Purchasing Group 100,101,102,103

Purchasing Group 110,111,112,113

Distr. Ch 10

Distr. Ch 20

Distr. Ch 30

Distr. Ch 10

Distr. Ch 20

Distr. Ch 30

Plant (Production) 1000

Plant (Distribution Center) 1100

Div Div 10 20

Div 10

Div 20

Div 10

Div 20

Div 10

Div 20

Div 10

Div 20

Div 10

Div 20

Shipping Point 1000

Shipping Point 100R

Shipping Point 1100

Shipping Point 110R

SLoc Shop Floor 1020

SLoc Shipping 1030

SLoc Shipping 1040

SLoc Stores 1050

SLoc Returns 1060

SLoc Shipping 1130

SLoc Shipping 1140

SLoc Returns 1160

Lean WM 110

Lean WM 120

Enterprise Structure - Accounting

Overview for FI/CO/HCM

Personnel Area 1000 Personnel Subarea 1010 Personnel Subarea 1020 Personnel Area 1100 Personnel Subarea 1110 Personnel Subarea 1120

Client Operating Concern 1000 Controlling Area 1000

Credit Control Area 1000

Company Code 1000

Red: Default values for variable parameters

Enterprise Structure Logistics

Overview for SD/MM
Red: Default values for variable parameters
Division 10 Division 20

Company Code 1000

Production Plant 1000

Sales Organization 1000 Controlling Area 1000 Purchasing Groups 100 101 102 103 Purchasing Groups 110 111 112 113 Distribution Plant 1100

Purchasing Organization 1000

Client

Enterprise Structure Sales

Sales Area
Red: Default values for variable parameters
Division 10 Division 20

Company Code 1000

Production Plant 1000

Sales Organization 1000 Controlling Area 1000 Distribution Plant 1100

Purchasing Organization 1000

Client

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.