Articles: Customer-Specific Fields in ALE (SAP Library

Articles: Customer-Specific Fields in ALE

Use

In Customizing for the Article Master, you can configure the article master to include table fields of your own. You do this in the section Configuring the Article Master. The data contained in the customer-specific fields can also be distributed by Application Link Enabling (ALE).

Prerequisites

If you want to use ALE to distribute customer-specific data, you must do the following:

Activate SAP Enhancement MGV00003

For more information, see the SAP library documentation BC Changing the SAP Standard.

Define the necessary source code for the following user exits contained in SAP Enhancement MGV00003:

EXIT_SAPLMV01_003
EXIT_SAPL1001_003

For more information, see the documentation for SAP Enhancement MGV00003 and for the user exits. You can base your source code on the sample source code referred to in the user exit documentation.

Features

When article master data is distributed by ALE, the customer-specific data is read in outbound processing and transferred to the assigned IDoc segment via user exit EXIT_SAPLMV01_003. In inbound processing, the customer-specific data is taken from the corresponding IDoc segment and posted in the target system via user exit EXIT_SAPL1001_003.

For the following article master tables, you can distribute customer-specific fields without including new segments in the IDoc:

MARA (client-specific article data)
MARC (site-specific article data)
MARD (storage-location-specific article data)
MBEW (valuation data)
MVKE (sales data)
WLK2 (POS data)
MLGN (warehouse-specific article data)
MLGT (storage-type-specific article data)

If you want to extend and distribute other article master data tables, you must include new segments in the IDoc. For more information on extending business application programming interface (BAPI) methods, see the SAP library documentation BC BAPI Programming.