Account (A-Segment)

CL_USMDZ7_RS_ACCOUNT
1

10
Validation Checkpoints for Entity
Entity
Account Type X
Once an account has been activated, the account type must not be changed.

Account Group
The Account Group is mandatory. Its value has to be defined for the current chart of X
accounts. A new or changed account group has to be valid for the current account ID.
The account group defines the interval for the account IDs. The current account ID has
to part of this interval.

P&L Account Type X

The P&L account type is mandatory for P&L accounts. The chosen value has to be valid.

Group Account
If the current chart of accounts uses a group chart of accounts, the Group Account is X
mandatory. The chosen value has to be valid. The current account and the group
account have to have the same account type. The Group Account must not be defined
as "Statistical Indicator".

Statistical Group Account

The chosen Group Account has to be a valid value. The current account and group X
account have to have the same account type. The group account has to be defined as
"Statistical Indicator".

Account ID
The account can only be created using the current ID, if there is no secondary cost X
element having the same ID. Cost elements using the same ID have to be primary cost
elements.
Functional Area
Balance Sheet Accounts must not have a functional area. Primary cost elements of the X
account have to use the same (inherit) functional area.

Hierarchy Assignment
Check Parent.
FRS Item is the only valid parent (see below for exceptions)
Special Items 'Financial Statement Notes', 'Not Assigned', 'P+L Result', 'Net Result: Loss'
and 'Net Result: Profit' cannot be used as parent.
Check Number of Assignments in Hierarchy X
Common FRS Items allow one or two assignments of the account in the complete
hierarchy.
Contra FRS Item requires exactly two assignments of the account in the complete
hierarchy (current item and its contra item).
All siblings are accounts having the same account type.
Hierarchy Attributes 'Credit relevant' and 'Debit relevant' are mandatory.
An account assigned to a common FRS Item has to set both. This is either done in the
single assignment, or with opposite values in the implicit 'contra' assignment.
An account assigned to two contra FRS Items has to set opposite values. All siblings
below a contra FRS item have to use the same value (e.g. credit only or debit only).
Account Name
The Account Name has to be defined in the default language of the current chart of X
accounts.
New Account X
The New Account must not be a self-reference.
Checkpoints for Entity Changed in
Change Request Edition Release
X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X MDG 8.0

X X MDG 7.0

X - -
Account in Company Code
CL_USMDZ7_RS_ACCCCDET
1

10

11

12

13

14

15

16
17

18

19

20

21

22
Validation Checkpoints for Entity
Entity
Currency
Show a warning in case of changes. X
Only Balances in Local Currency
Show a warning in case of changes. The indicator should not be set if the actual
currency of the company code differs from the default in customizing. The usage of X
local currency is only allowed for balance sheet accounts.

Reconciliation Account for Account Type

Show a warning in case of changes. Reconciliation accounts must not use balances in X
local currency. Reconciliation accounts must not be P&L accounts.

Post Automatically Only

Show a warning in case of changes. Automatically Posting is not allowed for X
reconciliation accounts.
Open Item Management
Show a warning in case of changes. Open Item Management is not valid for X
reconciliation accounts or P&L accounts.
Valuation Group X
Show a warning in case of changes.
Authorization Group X
Show a warning in case of changes.
Field Status Group
Show a warning in case of changes. The field status group is mandatory. Its value has X
to be valid for the current company code.

Alternative Account Number

Validation is needed if a country chart of accounts is maintained for the current
company code in customizing (T001-TKOP2) and if the value of the alternative account X
number has changed.
Performed checks are:
The alternative account has tp exist in the country chart of accounts. The account
types of the current account and the alternative account must be the same. The
alternative account must not be referenced yet by a different account.
Line Item Display
Line Item Display is not valid for reconciliation accounts. If Open Item Management is X
defined, the line item display indicator has to be set.
Tax Category
Check tax category vs. reconciliation accounts. The tax category has to be valid for the X
current company code.

Exchange Rate Difference Key X

The Exchange Rate Difference Key has to be valid for the current chart of accounts.
Company Code X
The company code has to be valid for the current chart of accounts.
Parent Account: Account Group
Execute required field checks according to the field status as defined for the current X
account group.
Parent Account: Block for Creation X
If the A-Segment is blocked for creation, new B-Segments cannot be created.
Inflation Key X
The Inflation key has to be valid for the current company code.
Sort Key
A sort key is mandatory if the line item display indicator is set. A sort key must not be X
set if the line item display indicator is not set.
The sort key has to be valid for the current company code.
Planning Level X
The selected value of the UI has to be in the list of allowed values.
Tolerance Group. X
The tolerance group has to be valid for the current company code.
Accounting Clerk X
The Accounting Clerk has to be valid for the current company code.
Commitment Item X
The commitment item has to exist and has to be valid.

Reconciliation Account Ready for Input X

The indicator can only be set for customer and vendor related reconciliation accounts.
Checkpoints for Entity Changed in
Change Request Edition Release
X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X -

X X -
X X -

X X -

X X -

X X MDG 8.0

X X MDG 8.0

X X MDG 8.0
Company Validation Checkpoints for Entity
CL_USMDZ7_RS_COMPANY Entity Change Request
Check Required Fields
The company defines the following fields as
mandatory:
• TXTLG – Name 1
• STREET – Street
• POST_COD1 – Postal Code
1 • CITY1 – City X X
• COUNTRY – Country
Fields City and Street must not contain more
than 30 characters.

Company Address
Validate the postal code (zip code) against its
country since the Company entity does not
provide all address data for a complete
2 check. The check is the same as executed in X X
SAP ERP customizing maintenance for
companies.
ints for Entity Changed in
Edition Release

X -

- -
Financial Reporting
Structure
CL_USMDZ7_RS_FRS

10

11

12

13
Validation Checkpoints for Entity
Entity
Assignment of Functional Areas permitted
Deselecting the indicator is not allowed if any FRS Item of the current financial reporting
structure hierarchy contains already an assignment of functional areas. X

Special Items
1. All Special Items should be defined. X
2. A single FRS Items can only be assigned once as special item.
Special Items in Hierarchy
1. Item 'Not Assigned' must not have any children at all.
2. Item 'P+L Result' must not have any children at all.
3. Item 'Net Result: Loss' must not have any children at all. X
4. Item 'Net Result: Profit' must not have any children at all.

Group Account Number

If the indicator is set, all assigned accounts in the hierarchy must have a reference to a X
group account.
Assignment of FRS Items in the Hierarchy
It is required that all FRS Items are part of the corresponding hierarchy. X
Financial Reporting Structure ID
It is not allowed to use a FRS ID twice. X
Financial Reporting Structure Name
With MDG 7.0, the FRS Name is a mandatory field. X
Balance Sheet Accounts in Hierarchy
List all balance sheet accounts that have not been added to the FRS hierarchy as errors. -

Profit and Loss Accounts in Hierarchy

The validation is executed only if assignments of functional areas are not allowed. If so, -
check if existing P&L Accounts have been assigned to the current hierarchy.

Functional Areas in Hierarchy

The validation is executed only if functional areas are allowed in the current hierarchy. If -
so, list all unassigned functional areas as errors.
P&L Accounts assigned to Special Item Assets in Hierarchy
It is not allowed to assign P&L Accounts below the special item 'Asset'. -
P&L Accounts assigned to Special Item Liabilities & Equity in Hierarchy
It is not allowed to assign P&L Accounts below the special item 'Liabilities & Equity'. -
Balance Sheet Accounts not assigned to Special Items Assets or Liabilities & Equity' in
Hierarchy -
Balance Sheet accounts should be assigned at least once.
Checkpoints for Entity Changed in
Change Request Edition Release

X X -

X X -

X X -

X X -

X X -

X - -

X - MDG 7.0

- X -

- X -

- X -

- X -

- X -

- X -
FRS Item
CL_USMDZ7_RS_FRSI
1

5
6
Validation

FRS Item ID
The FRS Item ID must not be the same as the related FRS ID.
Contra Item
1. The contra item must not be a self-reference to the current FRS item.
2. Execute the hierarchy specific checks for the contra item (CHECK_FRSICONTR).
a) The contra item has to be a bi-directional assignment. If item ABC references to contra item XYZ, item XYZ has to reference t
item ABC, too.
b) The direct children of the FRS item and its contra items must be accounts.
c) The direct children of the FRS item and its contra item must be absolutely identical (same accounts).
d) Identical accounts require that the 'Credit relevant' and 'Debit Relevant' indicators are set to opposite values. A single contra
item is either 'Credit' or 'Debit' only.

Hierarchy Assignment (Single Object Maintenance)

1. Valid parents of a FRS Item are FRS and FRSI entities. Assignment below accounts or functional areas is forbidden.
a) Special Items 'Not Assigned', 'P+L Result', 'Net Result: Loss' and 'Net Result: Profit' cannot be used as parent. The actual
definition of an FRS Item as special item is not checked. This is part of the FRS validations.
b) FRS Items allow only a single assignment in the complete hierarchy.
2. All siblings are FRS Items.

FRS Item Name

The name (long text) is mandatory.
FRSI Text Items (SUT 4)
The texts must not contain a $ sign.
Complete Hierarchy
1. Interval check for the assignment of account and / or functional area ranges. Intervals must not overlap. A single object mus
not be assigned within an interval and individually at the same time (except accounts assigned to contra items).
2. Direct children of the FRS root node must be FRS Items. Other entity types must not be assigned directly to the root.
3. For new or changed FRS Items, the following checks are executed:
a) Direct children must have the same entity type.
b) Children of type functional area require that the FRS root allows the assignment of functional areas in general.
c) Children of type account require that the hierarchy attributes 'Credit relevant' and 'Debit relevant' are set. Accounts assigned
to contra items execute additional checks:
i. The contra item has to be a bi-directional assignment. If item ABC references to contra item XYZ, item XYZ has to reference to
item ABC, too.
ii. The direct children of the FRS item and its contra items must be accounts.
iii. The direct children of the FRS item and its contra item must be absolutely identical (same account IDs).
iv. Identical accounts require that the 'Credit relevant' and 'Debit Relevant' indicators are set to opposite values.
e). All children of type account shall have the same account type.
f). A single FRS item has to appear only once in the hierarchy.
4. For deleted or removed FRS Items, the contra item checks (see details of item 3.3.) are executed.
5. New or changed accounts or functional areas must always be assigned as leafs. They must not have any other children.
6. New or changed accounts must be validated w.r.t. contra items (see details of item 3.3).
7. Any change for a single child assigned to a FRS Item requires the complete check of the parent FRS Item including all of its
direct children (see details of item 3).
8. The special FRS Items as defined by the FRS root require more specific validations:
a) All special FRS items must be part of the hierarchy.
b) Item 'Financial Statement Notes' must not have any accounts or functional areas as direct children. It's valid to assign other
FRS items.
c) Item 'Not Assigned' must not have any children at all.
d) Item 'P+L Result' must not have any children at all.
e) Item 'Net Result: Loss' must not have any children at all.
f) Item 'Net Result: Profit' must not have any children at all.
 Checkpoints for Entity Checkpoints for Hierarchy Changed in
Entity Change Request Edition Entity Change Request Edition Release
X X X - - - -

X X X - - - -

X X X - - - MDG 8.0

X X - - - - MDG 7.0

X X - - - - -
- - - X X X -
Cost Center
CL_USMDZ7_RS_CCTR

10

11
Validation

Cost Center ID
1. The ID is mandatory.
2. The ID must not contain a star (*) and / or comma (,)
Logical System
If ALE replication via logical systems is active for the current controlling area, the logical system must have the same
value as defined in customizing. Otherwise the field has to be empty.
Business Area
1. The current company code can define the business area as a mandatory field.
2. The change of an existing business area is only valid for a new fiscal year.
Functional Area
The current company code can define the functional area as a mandatory input field.
Currency
1. The controlling area can define the usage of the company code's currency as mandatory.
2. The change of an existing currency is only valid for a new fiscal year.
Company Code
1. The current controlling area defines a list of company codes in customizing that are valid for the controlling area.
The current company code must be part of this list.
2. The change of an existing company code is only valid for a new fiscal year.

Profit Center
1. If profit center accounting is active, the field should be filled.
2. Active data should only be changed if a new accounting period starts.
3. The Profit Center itself must be active (postable) for the current cost center's company code.
4. The validity of the Profit Center and the current Cost Center has to match.

Address
Execute the standard checks of the business address service.
Tax Jurisdiction Code
1. Existence Check: the tax jurisdiction code must exist either in SAP customizing or in external providers.
2. Company Code Validation: if the tax jurisdiction code is determined from SAP customizing, it must be valid for the
assigned company code of the cost center.
3. Validation vs. external providers: if the tax jurisdiction code is determined by external providers, the same are
used for checking.

Short Texts / Name

The short text / name is mandatory.
Hierarchy Assignment
Checks for single entity processing are only executed in MDG 8.0 and newer!
1. The cost center should be assigned to the standard hierarchy.
2. The cost center must not be assigned within a range in the standard hierarchy. Ranges are only allowed for
additional hierarchies.
3. The cost center must not be assigned multiple times in a single hierarchy.
 Checkpoints for Entity Changed in
Entity Change Request Edition Release

X X X -

X X X -

X X X -

X X X -

X X X -

X X X -

X X X -

X X X
MDG 7.0

X X X MDG 7.0

X X -

X X X

MDG 8.0
Cost Center Group
CL_USMDZ7_RS_CCTRG

3
Validation Checkpoints f
Entity
Cost Center Group ID
1. The cost center group ID (name) must fulfill the required format as defined for the current system. X
2. The cost center group ID (name) must differ from hierarchy names.
Hierarchy Assignment (Single Object Maintenance)
1. The cost center group must not be assigned multiple times in a single hierarchy. X
Complete Hierarchy
1. Cost Centers must not have children.
2. Each Cost Center should be assigned to the standard hierarchy.
3. Each Cost Center Group node should appear only once in the hierarchy. -
4. Each Cost Center should appear only once in the standard hierarchy.
5. Ranges of cost centers are forbidden in the standard hierarchy.
Checkpoints for Entity Checkpoints for Hierarchy Changed in
Change Request Edition Entity Change Request Edition Release

X X - - - -

X X - - - MDG 8.0

- - X X X MDG 8.0
Cost Center Group
Hierarchy
CL_USMDZ7_RS_CCTRH

1
Validation Checkpoints f
Entity
Cost Center Group Hierarchy ID
1. The cost center group hierarchy ID must not be longer than 10 characters. X
2. The cost center group hierarchy ID must differe from existing cost center group IDs.
Checkpoints for Entity Changed in
Change Request Edition Release

X - MDG 7.0
Cost Element
CL_USMDZ7_RS_CELEM
1

6
Validation

Record Quantity Indicator

If the indicator is set, the Cost Element's Unit of Measure is mandatory.
Unit of Measurement
1. The UoM must have an ISO Code.
2. The change of an existing UoM should not change the dimension.
Cost Element Category
The category defines the actual classification (primary or secondary) of the cost element. Each classification requires
specific checks:
1. Primary Cost Elements need an existing account.
2. Primary Cost Elements using the category 90 must be related to a balance sheet account. The account must be an
asset reconciliation account.
3. Primary Cost Elements using any other category must be related to Profit & Loss Accounts
4. Secondary Cost Elements can only be created with an ID that is not used by accounts.

Hierarchy Assignment
Checks for single entity processing are only executed in MDG 8.0 and newer!
1. The cost Element must not be assigned multiple times in a single hierarchy.
Currency
1. The controlling area can define the usage of the company code's currency as mandatory.
2. The change of an existing currency is only valid for a new fiscal year.
Short Text (Name)
The cost element name (short text) is mandatory.
 Checkpoints for Entity Changed in
Entity Change Request Edition Release
X X X -

X X X -

X X X -

X X X -

X X X -

X X - -
Cost Element Group
CL_USMDZ7_RS_CCTRG

3
Validation

Cost Element Group ID

1. The cost Element group ID (name) must fulfill the required format as defined for the current system.
2. The cost Element group ID (name) must differ from hierarchy names.

Hierarchy Assignment (Single Object Maintenance)

1. The cost Element group must not be assigned multiple times in a single hierarchy.
Complete Hierarchy
1. Cost Elements must not have children.
2. Ranges of cost Elements are forbidden in the standard hierarchy.
 Checkpoints for Entity Checkpoints for Hierarchy Changed in
Entity Change Request Edition Entity Change Request Edition Release

X X X - - - -

X X X - - - MDG 8.0

- - - X X X MDG 8.0
Cost Element Group
Hierarchy
CL_USMDZ7_RS_CELEMH

1
Validation Checkpoints f
Entity
Cost Element Group Hierarchy ID
1. The cost element group hierarchy ID must not be longer than 10 characters. X
2. The cost element group hierarchy ID must differe from existing cost element group IDs.
Checkpoints for Entity Changed in
Change Request Edition Release

X - MDG 7.0
Profit Center
CL_USMDZ7_RS_PCTR
1

10

11
Validation

Profit Center ID
The profit center ID must not be a hash-tag (#) or contain any comma (,) or star (*).
Existence Check for Company Codes of Controlling Area
The chosen controlling area must have at least one company code assigned.
Logical System
The current controlling area defines whether a logical system has to be assigned or not. Check the system
customizing vs. the current value.
Assignment to Company Codes
1. If the indicator 'Postable in all Company Codes' is set, there have to be company codes assigned to the profit
center.
2. With MDG 7.0: if the indicator 'Postable in all Company Codes' is set, additionally all assigned company codes
must have their specific 'Postable' indicator set to true.
3. If the indicator 'Postable in all Company Codes' is not set, at least one of the assigned company codes must not
have set the specific 'Postable' indicator.
4. If the 'Postable' indicator for a specific company code that is assigned to a profit center is removed, a cross check
vs. cost centers is required. Cost centers use profit centers as a cross reference. This relation requires that the profit
center is postable in the company code used by the cost center (e.g. if the cost center uses company code 0001, the
profit center must be assigned to company code 0001 and the specific 'Postable' indicator has to be set).

Segment
The usage of the segment is defined by the system's customizing.
1. Inactive usage: there must not be any value for the segment attribute of the profit center.
2. Active usage: if related split method is active, too, and split fields are defined, the segment should contain a value.
3. The change of an already active value is forbidden.

Blocking Indicator
The blocking indicator must not be set for the SAP dummy profit center.
Address
Execute the standard checks of the business address service.
Tax Jurisdiction Code
1. Existence Check: the tax jurisdiction code must exist either in SAP customizing or in external providers.
2. Company Code Validation: if the tax jurisdiction code is determined from SAP customizing, it must be valid for the
assigned company code of the profit.
3. Validation vs. external providers: if the tax jurisdiction code is determined by external providers, the same are
used for checking.

Short Texts / Name

The short text / name is mandatory.
Hierarchy Assignment
Checks for single entity processing are only executed in MDG 8.0 and newer!
1. The profit center should be assigned to the standard hierarchy.
2. The profit center must not be assigned within a range in the standard hierarchy. Ranges are only allowed for
additional hierarchies.
3. The profit center must not be assigned multiple times in a single hierarchy.

Assignments to Company Codes (special consistency check)

In the lifetime of an edition, it is possible that the company code assignment of controlling areas is changed. The
release of an edition needs to validate, if all of its profit centers still have valid company codes assigned.
 Checkpoints for Entity Changed in
Entity Change Request Edition Release
X X X -

X X X -

X X X -

X X X -

X X X -

X X X -

X X X MDG 7.0

X X X MDG 7.0

X X - MDG 7.0

X X X MDG 8.0

- - X
MDG 8.0
Profit Center Group
CL_USMDZ7_RS_PCTRG

3
Validation Checkpoints f
Entity
Profit Center Group ID
1. The Profit center group ID (name) must fulfill the required format as defined for the current system. X
2. The Profit center group ID (name) must differ from hierarchy names.
Hierarchy Assignment (Single Object Maintenance)
1. The Profit center group must not be assigned multiple times in a single hierarchy. X
Complete Hierarchy
1. Profit Centers must not have children.
2. Each Profit Center should be assigned to the standard hierarchy.
3. Each Profit Center Group node should appear only once in the hierarchy. -
4. Each Profit Center should appear only once in the standard hierarchy.
5. Ranges of Profit centers are forbidden in the standard hierarchy.
Checkpoints for Entity Checkpoints for Hierarchy Changed in
Change Request Edition Entity Change Request Edition Release

X X - - - -

X X - - - MDG 8.0

- - X X X MDG 8.0
Profit Center Group
Hierarchy
CL_USMDZ7_RS_PCTRH

1
Validation Checkpoints f
Entity
Profit Center Group Hierarchy ID
1. The profit center group hierarchy ID must not be longer than 10 characters. X
2. The profit center group hierarchy ID must differe from existing profit center group IDs.
Checkpoints for Entity Changed in
Change Request Edition Release

X - MDG 7.0