Notes on Specific Master Data

Distributable Master Data Objects

Change Master Record

The distribution of a change number using the message type ECMMAS contains the following information:

The distributed change number is newly created in the target system if it does not already exist here. It is not yet possible to delete a change number in the target system nor to distribute it using a change pointer.

Article master

Only the article master data without external objects is transferred. External objects must be transferred separately (see below).

The following IDoc types are important for distributing article master data:

Vendor master

When distributing vendor master data, reminder data is posted in the inbound processing only to the default dunning area.

Classification

For the message type CLFMAS the dependencies of other message types, such as MATMAS and CREMAS must be maintained in different filter groups.

Customer Master

Addresses of contacts are not distributed.

Long texts are not included in the change document system.

Cost Accounting

When cost centers are distributed, the field CV_OTYPE for the joint venture object type is not distributed with them.

Material Master

The material type for a material (field MTART) is only read by the receiving system when you create a material and not when you change one. It is therefore possible for a single material to have different material types in different systems. It also means, however, that changes to the material type of a material cannot be distributed.

The production version segment (E1MKALM) is only used in outbound processing in Release 3.0. You cannot import the corresponding information into an R/3 System. This information can, however, be processed by non-SAP systems.

G/L accounts

The EXTERNAL ACCOUNTING INFORMATION field in the company code segment is only taken into account when new G/L accounts are created. Changes to this field are not posted. For security purposes, you have to do this manually.

Bills of Material

Bills of material (BOM) are distributed with all items and, if applicable, local object dependencies which are valid on the key date.

The distribution of bills of material does not include:

If you send bills of material directly, the user receives a list of all bills of material selected by the system which can be manually edited afterwards. Because only simple BOMs can be distributed, the user cannot select relevant alternative and variant BOMs, plant assignments and material variants for distribution.

You can overwrite the selection date displayed on the selection screen in the detail list. You can also replace it with a change number. For maintenance in the target system, you can also give a valid-from date or a change number (engineering change management). If you do not change it, the valid-from date or change number is copied from the sending system.

Here are the message variants for message type BOMMAT:

The BOM header data remains unchanged. It creates the BOM in the target system if it is not already there. This is the default if you do not select a message variant.

If the BOM already exists in the target system the IDoc is not posted.

You should however only use this function with the utmost caution, since the deletion of the BOM also deletes references from other applications (such as routing and production orders).

Changes to simple material BOMs or BOM items can also be distributed via SMD Tool. This way you can identify items in the target system using the fields, item category, item number, sort string and object. The object field is dependent on item category material, document data and class data.

Purchasing Info Records

Customs tariff preference data is not distributed when purchasing info records are distributed.

The order price history is not distributed.

The relevant vendors and materials must be distributed first.

The number ranges for purchasing info records need to be agreed system-wide in advance.

When a purchasing info record is posted, its conditions are not changed. However, the NETPR (net price) and EFFPR (effective price) fields are updated. In other words, the values are copied from the central system.

If the PLANT filter object is used in modeling the distribution of purchasing info records, the plant field must contain the value SPACE when you are working with purchasing info records which deal with more than one plant.

If the MATERIAL or MATERIAL LISTING filter objects are used in modeling the distribution of info records, the MATERIAL field must contain the value SPACE when you are working with purchasing info records for non-stock materials.

The SUPPLIER LISTING field cannot be used in the distribution of purchasing info records. Only material listings are permitted as filter objects in the distribution of purchasing info records.

Conditions for info records are passed on via the general conditions distribution and not via the info record IDoc.

Source List

The appropriate suppliers, materials and, if applicable, contracts, must be distributed in advance.

Distribution of source list records which refer to a scheduling agreement is not supported, since scheduling agreements cannot be distributed using ALE. If you do need to distribute such source list records, you need to arrange for the scheduling agreements to be distributed somehow to the appropriate systems.

If you use the ‘Purchasing organization ‘ filter object in modeling the distribution of source lists, the supplier field must contain a space if you are working with source lists which span more than one purchasing organization.

If you use the SUPPLIER filter object in modeling the distribution of source lists, the supplier field must contain a space if you are working with source list records which are supplier-independent.

The SUPPLIER LISTING filter object cannot be used in the distribution of source lists. Only material listings are permissible as filter objects.

Conditions

Fields which are reduced are set to initial in the receiver system. If you reduce whole segments, these are deleted in the target system.

Conditions with use E (= bonus, conditions for later calculation) can only be distributed manually and not using the change document system.

Human Resources

Info types are distributed with all of their fields.

Entries in T77TR lock objects in the target system against import.

In insert mode (complete distribution) the objects are transported completely.

In update mode (change pointers) the transported data is completely replaced in the target system.

Object types and info types can be restricted further using filters. You can define a filter for the object which you actually need. For example, you should not transport object types X*.

Distributable PA Object Types and PA Info Types

To distribute PA object types and PA info types, various filter types must be defined for the message type HRMDS_A in the distribution model. Each filter type must be assigned to its own filter group.

The only PA object type that can be distributed is PERSON. To distribute the PA object type PERSON, a filter object of type OTYPE with value P must be assigned to the message type HRMDS_A.

To distribute the PA info types, a filter object of type ITYPE with the value of the info type number must be assigned to the message type HRMDS_A for each info type.

The following PA info types can be distributed:

Info type number

Info type long text

0000

Tasks

0001

Organizational assignment

0002

Personnel details

0003

Payroll status

0006

Address

0009

Bank details

0017

Travel privileges

0105

Communication

0900

Sales data

PA info types for important application cases are in the target system.

Distributable PD Object Types and PA Info Types

All PD object types can be distributed.

PD info types are numbered from 1000-1099. All info types from the Organizational Management and Planning can be distributed, except for activity groups and workflow.

Constraints

For HR data there is only one central HR R/3 System, in which all HR components are integrated. PA and PD data must cannot be changed in the receiver system. This can be effected by using profiles which allow only read-only access.

Data in the receiver system is created under the same plan variant as in the sending system.

If you want to create further PA and PD objects directly in the receiver system, you must take care that the number ranges are different from those in the sending system.

The integrated HR/logistics work center must be maintained in the logistics system. If this integrated work center is being used, the HR work center is automatically locked against import.

Tasks are not distributed, although the links (1001) to tasks can be distributed.

Local PD links in the target system are retained in update mode.

If an object without active change pointers is deleted, it must also be deleted manually in the target system.

PA data is saved in the target system without authorization or dialog checks.

PD data is saved in the target system without dialog checks.

Texts for PA info types are not distributed.

When you distribute PA info types you must ensure that at least info types 000, 0001, 0002 and 0003 are distributed. Info type 0003 is only distributed via change pointers if it is changed in combination with one of the other supported PA info types.

Profit Center

Statistical key figures are not distributed.

Master data can only be maintained in the local system of the controlling area.