|
Home
| |
Master data than can be distributed in V3.1H
Notes on Specific Master Data
The material type for a material (field MTART) is only read by the receiver 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. Importing the corresponding information into an R/3 System is not supported. This
information can, however, be processed by the non-SAP system.
When distributing vendor master data, reminder data is posted in the input processing
only to the default dunning area.
Addresses of contacts are not distributed.
Long texts are not included in the change document system.
The 'Run account externally' 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
safety you therefore need to adjust the field manually.
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:
 | long texts for headers, alternatives and items |
| sub-items |
| global object dependencies, which must exist in the target system |
| BOM history. In other words, only the status of the BOM on the key date is distributed. |
| the BOM item objects, for example materials, documents and classes. These objects must
be distributed separately from, and before, the BOM. |
| if applicable, the change number. The change number must exist in the system! |
On sending, 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:
| CNG (change): changes the BOM items.
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. |
| CRE (create): creates the BOM.
If the BOM already exists in the target system the IDoc is not posted. |
| DEL (delete): deletes the BOM.
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.
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.
| For purchasing info records for stock materials, the number of the purchasing info
record is taken from the central system on posting, so long as the purchasing info record
for the material and the appropriate supplier does not already exist in the receiver
system. If this is the case, the existing purchasing info record is updated. |
| For purchasing info records for non-stock materials, the purchasing info record number
is always taken from the central system. If a purchasing info record with the same number
already exists, the system checks whether it has the same supplier and material group as
the info record from the central system. |
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.
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.
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.
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 pointer) the transported data is completely replaced in the target
system.
Distributed object types:
| PA Object types
 | P Person |
|
| PD Object types
| All PD object types are distributed |
|
Distributed info types:
| PA Info types
| 0000 Measures |
| 0001 Org. assignment |
| 0002 Personal data |
| 0003 Payroll status |
| 0006 Addresses |
| 0009 Bank details |
| 0017 Travel privileges |
| 0105 Communication |
| 0900 Sales data |
|
| PD-Info types: 10**
| All info types from organization management and planning may be distributed with the
exception of activity groups and Workflow. |
|
Info types are distributed with all of their fields.
Object types and info types can be further limited using filters. You can define a filter
for the object which you actually need. For example, you should not transport object types
X*.
Further restrictions:
There is a single central HR system for HR data in which all components are
incorporated. 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 an active change pointer 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.
Example:
Personnel number to check existence:
Object type: P, Info types: 0000, 0001, 0002, 0003.
Personnel number to generate vendors in FI:
Object type: P, Info types: 0000, 0001, 0002, 0003, 0006, 0009, 0017.
Personnel number for sales orders (maintained in HR!).
Object type: P, Info types: 0000, 0001, 0002, 0003, 0006, 0105, 0900.
Statistical key figures are not distributed.
Master data can only be maintained in the home system of the controlling area.
|
