Information Sheet on Transferring Article Master Data (Retail)
Transfer article master data for retail by Application Link Enabling (ALE). Although the data transfer workbench can be used, it may slow down the process considerably. For more information, see the SAP library documentation LO SAP Retail
Articles: Transfer and Distribution of Master Data.A. Object Profile
Object Name and Identification
Name of application object |
Article master |
Name of business object (BOR object) |
BUS1001001 |
Data transfer workbench object and subobject number |
None |
Change document for object supported? |
MAT_FULL |
Long texts for object |
MATERIAL (Texts at client level: Basic data text, inspection text, purchase order text) |
Data category |
Master data |
Number assignment |
External only |
SAP field for number in legacy system |
MARA-BISMT |
Transactions
Create |
MM41 |
Change |
MM42 |
Display |
MM43 |
Flag for deletion (article discontinuation) |
WSE1 (at client level) and WSE4 (at site level) |
Cancel deletion flags |
WSE8 |
Archive |
MM71 |
Other Programs
Reports for displaying and analyzing the data transferred |
None |
Deletion program for mass data |
Possible only by discontinuation |
Change options for mass data:
|
Mass maintenance tool can be used. |
Tables/Databases
Relevant tables |
MARA, MAW1, MAKT, MARC, MARD, MBEW, MLGN, MLGT, MVKE, WLK2, MLAN, MARM, MPOP, MPGD, MEAN, MAMT, MLEA, MVER, MAPR, PROP, PROW, STXH, STXL |
Logical databases |
None |
Tablespace |
PSAPSTABD (Data) |
Customizing
IMG activities influencing data transfer |
|
Time and Sequence
Time of transfer |
Article master records can be transferred to the R/3 System at any time. |
Dependencies regarding other data |
Before article master records are transferred to the R/3 System, the following basic data should already exist:
|
SAP Notes
44410 |
Implementing customer-specific fields (primarily relevant to the material master for industry but also relevant in part to the article master for retail) |
127905 |
Composite note with tips on improving the runtime |
141242 |
Composite note with tips on improving the runtime in data transfer |
B. BAPI Information
Required authorization? |
Same as for dialog maintenance |
Business object method |
CLONE |
Message type |
ARTMAS |
IDoc type |
ARTMAS03 |
Workflow for error handling |
Yes |
Which attributes are covered? Are all necessary parameters included? If not, which ones are not included? |
All attributes maintainable in dialog mode All pure article master data exists as parameters. Additional article data (such as purchasing info records, listing conditions, prices, and layout modules) cannot be processed. |
Are the created objects rendered in a message within the standard parameter RETURN?* |
No. The application log number is returned in the parameter RETURN. |
Test run flag* |
No |
Mass update possible? Is the buffer concept implemented? |
No No |
Is the BAPI extensible?
|
Yes, but only for the main parameters. No. A separate extension parameter exists for each extensible main parameter. User exit for transferring data for customer-defined fields (Enhancement MGV00003) |
Program for generating test data |
Yes |
Special notes for parallel runs |
None |
Special notes and constraints |
See LO SAP Retail Articles: Transfer and Distribution of Master Data. |
* See BAPI Development for Mass Data Transfer.