Master Data 

Definition

This substructure shows the structure of master data in the SAP System. It is organized according to enterprise area. General master records, for example, Material Master, Work Center, Customer/Vendor Master Record are located below the enterprise-specific master data items in the tree structure.

Use

The customer input templates for the structure items in the Master Data substructure allow you to document and analyze the main areas of importance for your enterprise in this area. The information you enter here is essential for drawing up your Business Blueprint. The customer input template for the substructure Master Data is made up of the following sections:

CI template sections for Master data

Content

  1. Requirements/expectations

Construct a bulleted list of requirements and expectations for this structure item. This list should be specific to the customer and reflect their input. Critical points should be clearly visible.

  1. General description

Describe in as much detail as possible how this structure item will be used in the customer’s enterprise. The most important business processes should be described in detail in this section.

  1. Naming/numbering conventions

Describe the naming and numbering conventions the customer uses in this structure item.

  1. Organizational structure

Address issues agreed in the workshop on the organizational structure of the SAP System. For example:

  • Are additional steps required for a particular process because of master data requirements?
  • Are there any growth issues that could affect business and should be addressed here?
  1. Changes to enterprise structure

Describe the effect of this structure item on the customer’s enterprise structure. For example:

  • Will the customer and vendor master records be controlled and maintained in a central or a distributed database?
  • Will there be an impact on head count?
  1. Description of improvements

Describe improvements in the area of Master Data which will result from implementation of the SAP System. Be sure to include any impact on Business Drivers.

  1. Description of functional deficits

Detail any real or perceived gaps in functionality that have become evident through the business process review sessions. Enter "None apparent" if the customer’s requirements seem to have been fulfilled.

  1. Approach to tackling functional deficits

Address any functional deficits, for example, in short-term solutions, user exits or ABAP. Look for the best high-level solution. If no solution is evident, the impact on the customer and the project must be clear, so that the team can decide how best to proceed. Enter "None apparent" if the customer’s requirements seem to have been fulfilled.

  1. Notes on further improvements

Describe future or potential improvements, as well as issues to be clarified in a future SAP release or project phase. Any issues raised in the process review that are outside the current project scope should be recorded here.

  1. System configuration/Customizing

Describe issues of importance to the customer in relation to system configuration. Details are not required, but be sure to address any issues addressed during the review.

  1. Authorization and user roles

Describe how the customer will manage security in this area. Don't cover the creation of authorizations in too much detail. Sensitize the team to the system functions and get the process owners to think about access to the system and its data.

  1. Project-specific information

Enter any project-specific information, which has not been covered in the sections above.

 

You can find information on how to fill out the template under Working with customer input templates.