!--a11y-->
Consistency Check for Organizational
Plan 
The report BBP_CHECK_CONSISTENCY (that can also be called up via transaction BBP_ATTR_CHECK) checks the consistency of the organizational plan. It also checks whether the attributes for companies, purchasing organizations, purchasing groups, and users are defined correctly for the individual applications.
·
The organizational
plan has been defined.
(See: Creating
the Organizational Plan)
·
The user attributes
have been defined on the organizational unit and position level.
(See: Defining
User Attributes in the Organizational Plan)
You can use this report to carry out two types of check:
· Consistency
If this field is selected, the system checks the consistency of the obligatory attributes of organizational units, that are defined as company, purchasing organization, or purchasing group. In addition, the system checks the consistency of the users in these and subordinate organizational units. In this way, the system checks whether the user has a business partner, whether this business partner has an address, and whether the user has been added correctly to the organizational plan.
· User Attributes for the Application
If this field
is selected, the report checks whether the user attributes for the selected
application are defined correctly. The report checks whether the user can
execute the relevant application with the existing attribute settings.
You can select an application to be checked (for example shopping cart,
invoice, purchase order) using a dropdown box or you can check
all
applications at
once.
Restrict Scope of the Check
You can restrict
the scope of the check via the dropdown box in the screen area Selection by choosing either company,
department, or user.
If you select one of the three categories, you can enter a relevant search
term or key in the field assigned to the dropdown box. There is an F4 search
help available if you are selecting via a search term. If you know the key
(the object ID or description of the organizational unit or the user name in
organizational management [PPOMA_BBP]) you can enter this directly in the entry
field.
¡ Company
To restrict
the check to a certain company, enter the key of the company to be checked or
use the input help to find the companies.
All subordinate organizational units that are defined as enterprise,
purchasing organization, or purchasing group are checked, as well as all
subordinate users.
¡ Department
To restrict
the check to a certain department, enter the key of the department to be
checked or use the input help to find the department.
All subordinate organizational units that are defined as enterprise,
purchasing organization, or purchasing group are checked, as well as all
subordinate users.
¡ User Name
To restrict the check to a certain user, enter the relevant user name or use the input help to find the user.
Maximum Number of Hits
To further restrict the scope of the check, you can specify a maximum number of hits. This number comprises both organizational units and users. This number comprises both organizational units and users.
You can correct the displayed fields in the organizational plan. Red error messages have to be corrected, and yellow error messages are just warnings.
See the path in IMG: SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Change Organizational Plan