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)
MVKE (Text at distribution chain level: Sales text)

Data category

Master data

Number assignment

External only
Note: Internal number assignment is possible by calling the BAPI BAPI_MATERIAL_GETINTNUMBERRET (single and generic articles) or BAPI_MATERIAL_GETVARNUMBERS (variants).

SAP field for number in legacy system

MARA-BISMT

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

Reports for displaying and analyzing the data transferred

None

Deletion program for mass data

Possible only by discontinuation

Change options for mass data:

-         Change program available?

-         Mass maintenance tool applicable?

Mass maintenance tool can be used.

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)
PSAPSTABI (Index)

IMG activities influencing data transfer

-         Make Global Settings (Transaction OMT0)

-         Maintain Field Selection for Data Screens (Transaction OMS9)

-         Define Attributes of Material Types (Transaction OMS2)

-         General Control, Retail Master Data (to define general reference sites) (Transaction WSS1)

-         Distribution Chain Control (to define distribution-chain-specific reference stores)

Time of transfer

Article master records can be transferred to the SAP system at any time.

Dependencies regarding other data

Before article master records are transferred to the SAP system, the following basic data should already exist:

-         Company codes

-         Sites

-         Other organizational levels for which article master data is to be transferred

-         Material types

-         Units of measure

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

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?

-         Parameter ExtensionIn/ExtensionOut?

-         User exits or BAdIs available?

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.