Hierarchy
⤷ AP-MD-BF-SYN (Application Component) Master Data Synchronization
⤷ MDS_IMG (Package) Master Data Synchronization: IMG Structure
IMG Activity
ID | MSI_REQUIREMENTS_01 | Preparatory Steps for Material-Service Integration |
Transaction Code | S_PCO_36000329 | (empty) |
Created on | 20050519 | |
Customizing Attributes | MSI_REQUIREMENTS_01 | Preparatory Steps for Material-Service Integration |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | MSI_REQUIREMENTS_01 |
Customizing of Required Entry Fields in the Material Master Record
The material master record makes it possible for you to demand that a required entry be made within a view for fields. In the context of master data synchronization between the product and the material master, you have two possibilities:
- You do not define any new fields as required entry fields in the views Basic Data 1 and Basic Data 2 (Processing Status K) or Purchasing (Processing Status E).
- If you do define new fields as required entry fields in these views, you must implement the Business Add-In Enhancements for Material Master to Product Mapping and define fixed values for mapping there for these fields.
The service master record makes it possible for you to demand that a required entry be made within a view for fields. In the context of master data synchronization between the product and the service master, you have two possibilities:
- You do not define any new fields as required entry fields in the views of the service master.
- If you do define new fields as required entry fields in these views, you must implement the Business Add-In Enhancements for Service Master to Product Mapping and define fixed values for mapping there for these fields.
Activities
- BAdI: Enhancements for Material Master to Product Mapping
- BAdI: Enhancements for Service Master to Product Mapping
Harmonizing Number Ranges for Material Master/Service Master and Product
When a material master or a product (product type material) is created in the context of master data synchronization, then the system creates the corresponding target object with the identical identifier.
This system behavior has the following effects on number range assignment:
- In the case of internal number assignment for the product and the material, the number range intervals of both objects may not overlap. Both number range intervals are independent of each other, and could be updated differently.
- In the case of external number assignment for the product and the material, the number range intervals of both objects may not overlap either. If the number ranges do overlap, you must take organizational steps to ensure that identical identifiers are assigned.
When a service master or a product (product type service) is created in the context of master data synchronization, then the system creates the corresponding target object with the identical identifier.
This system behavior has the following effects on number range assignment:
- In the case of internal number assignment for the product and the service master, the number range intervals of both objects may not overlap. Both number range intervals are independent of each other, and could be updated differently.
- In the case of external number assignment for the product and the service master, the number range intervals of both objects may not overlap either. If the number ranges do overlap, you must take organizational steps to ensure that identical identifiers are assigned.
Activities
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | MSI_REQUIREMENTS_01 | 0 | PAB0000028 | Master Data Synchronization |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20050519 |
SAP Release Created in | 600 |