Ansicht
Dokumentation

RFM_CONV_CONFIG_MAT_TO_ARTICLE - Configurable Material to Article Conversion Report

RFM_CONV_CONFIG_MAT_TO_ARTICLE - Configurable Material to Article Conversion Report

BAL Application Log Documentation   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You use this report to convert master data (configurable material and material variants only) to retail specific article master data (variants of configurable article and configurable article with category single article). This report adds the missing data when converting material to article.

Integration

Prerequisites

Before executing the program, make sure you have carried out the following actions in Customizing:

  • Table T130S (General Control Indicators in Master Data Maintenance)

You have maintained the following field in Customizing for Material Master in the IMG activity Make Global Settings:

  • Standard country (retail) (T130S-LAND1): Enter your default country accordingly. While extending material master data table MARA (field TAKLV: Tax classification of the material), field T103S-LAND1 is used to determine the default tax classification of the material based on the given default country.

  • Table TWPA (General Parameters for Retail Control)

You have maintained the following fields in Customizing for Basic Data Retail in the IMG activity General Control, Retail Master Data:

  • Retail industry sector (TWPA-MBRSH): recommended value is “1” (Retail).

  • Reference plant for DCs (TWPA-VLGVZ): it is mandatory to use one of the given distribution centers as a reference DC for the article master data creation.

  • Reference plant for stores (TWPA-VLGFI): it is recommended to useone of the given stores as a global reference store for the article master data creation (as an alternative you can use distribution chain specific reference stores).

  • Work without listing conditions (TWPA-LIKON): If you plan to work with listing conditions make sure that the flag is not set.

  • Table TVKOV (Org. Unit: Distribution Channels for Each Sales Organization)

You have maintained the following fields in Customizing for Basic Data Retail in the IMG activity Distribution Chain Control:

  • Distribution chain category (TVKOV-VLTYP): Enter the category of the given distribution chain according to the usage (“SPACE” = Distribution chain for wholesale trade, “1” = Distribution chain for stores, “2” = Distribution chain for distribution centers).

  • Field VLTYP is required for maintaining table MAW1.

  • Reference Store (TVKOV-VLGFI): In case you want to use distribution chain specific reference stores instead of or in addition to the global reference store, enter the suitable store.

Also make sure you have carried out following actions in general:

  • Plants associated with the material must be converted into a Retail distribution center or store before running the conversion. Use transaction WB02 (Change plant) to convert a plant into a distribution center or store.
  • Assign a material group in transaction MM02 (Change Material) to each material which needs to be converted into an article. Make sure the material group has been converted into a Retail merchandise category. Use transaction WG21 (Create material group) to create a new merchandise category or apply transaction WG22 (Change material groups) to an existing material group to convert them into a merchandise category.

Note: It is recommended to create reference articles for the used merchandise categories. Based on the reference article missing values for mandatory fields can be merged into the converted article master data.

Use the button Goto Reference Material in transaction WG22(Change material groups) to create a reference article for this merchandise category. For the reference article, you must need to maintain at least the views Basic Data and Logistics DC for the reference DC. If you have a general reference store, maintain also the Logistics Store view.

Read Configurable Material and Material Variants

If you enter a material variant or a configurable material in the selection criteria, its configurable material and all other material variants of this configurable material are also considered for migration.

For example, let’s consider the following scenario:

50138 – Configurable material

50139 – Material variant of configurable material 50138 (plant Specific) at plant F051

50140 - Material variant of configurable material 50138 (plant Specific) at Plant FDC1

50141 – Material variant of configurable material 50138 (cross- plant)

50142 – Material variant of configurable material 50138 (cross- plant)

If you specify material variant 50139, all materials (configurable material and material variants) are considered for migration.

If you specify a configurable material 50138, all materials (configurable material and material variants) are considered for migration.

Note:

  • Cross Plant Material Variant, assignment to a configurable material is defined in the basic data of the material master.
  • Plant Specific Material Variant, assignment to a configurable material is defined in the MRP 3 view of the material master.

Criteria for conversion of a configurable material and its material variants into an article

You must ensure that the

  • materials are not yet articles (MAW1 record does not exist, MARA-ATTYP = SPACE)
  • materials are not without a material group assignment (MARA-MATKL <> SPACE)
  • materials are not flagged for deletion (MARA-LVORM = SPACE)
  • materials are not segmentation relevant (MARA-SGT_REL = SPACE)
  • material category is not standard material (MARA-ATTYP <> SPACE)

Note: You can copy the fields which are mandatory for the article master data from a reference article if those are available.

This conversion program extends the master data segments for all processed materials and the following tables are updated:

  • MARA - Here the existing record is updated with relevant fields:
Field   Description   Reference Field
ATTYP   Article category   “00” = Single article
MBRSH   Industry sector   TWPA-MBRSH
LAEDA   Date of last change   SY-DATUM
AENAM   Name of person who changed object   SY-UNAME
PRDHA   Product hierarchy   MVKE-PRODH
PMATA   Pricing reference material   MVKE-PMATN
TAKLV   Tax classification of the material   MLAN-TAXM1 of the default   country (T130S-LAND1) or based on reference article
BWSCL   Source of supply   Initialize
DATAB   Valid from date   MARA-ERSDA
LIQDT   Valid to date   Maximal date (31.12.9999)
TRAGR   Transportation group   Based on reference article

Note: the MVKE reference data is determined based on the first distribution chain maintained for the material.

  • MAW1 (retail Specific) - Here a new record is inserted into the table with relevant fields:
Field   Description   Reference Field
WPSTA   Maintenance status   Based on the given data of the material
LDVFL   From listing period - store   SY-DATUM
LDBFL   To listing period - store   Maximal date (31.12.9999)
LDVZL   From listing period - DCs   SY-DATUM
LDBZL   To listing period - DCs   Maximal date (31.12.9999)
VDVFL   Date from which sold in the store   SY-DATUM
VDBFL   Date to which sold in the store   Maximal date (31.12.9999)
VDVZL   Date from which sold in the distribution center   SY-DATUM
VDBZL   Date to which sold in the distribution center   Maximal date (31.12.9999)
WMAAB   ABC indicator   MARC-MAABC
WEKGR   Purchasing group   MARC-EKGRP
WHERL   Country of origin   MARC-HERKL
WHERR   Region of origin   MARC-HERKR
WLADG   Loading group   MARC-LADGR
WVRKM   Sales unit   MVKE-VRKME
WAUSM   Unit of issue   MARC-AUSME (for distribution centers)
WLADG   Loading group   MARC-LADGR or based on reference article
WBKLA   Valuation class   MBEW-BKLAS or based on reference article
WBWSP   Valuation margin   MBEW-BWSPA

Note:

  • The MVKE reference data is determined based on the first store distribution chain maintained for the material.

  • The MARC reference data is determined based on the reference sites maintained for the material. System checks for the data in this order: Reference DC ->global reference store -> distribution chain specific store -> first non-reference site.

  • The MBEW reference data is maintained based on the reference sites maintained for the material. System checks for the data in this order reference DC -> global reference store -> distribution chain specific store -> first non-reference site.

  • MVKE - Here the existing records are updated with relevant fields:
Field   Description   Reference Field
LDVFL   From listing period - store   SY-DATUM
LDBFL   To Listing Period - store   Maximal date (31.12.9999)
LDVZL   From listing period - DCs   SY-DATUM
LDBZL   To Listing Period - DCs   Maximal date (31.12.9999)
VDVFL   Date from which sold in the store   SY-DATUM
VDBFL   Date to which sold in the store   Maximal date (31.12.9999)
VDVZL   Date from which sold in the distribution center   SY-DATUM
VDBZL   Date to which sold in the distribution center   Maximal date (31.12.9999)

Features

Selection

Standard Variants

Output

Activities

Executing the program:

  • On selection of Block Material checkbox, relevant tables are locked during the execution of the report. You can avoid locking of the table if you are sure that no other transactions are running in parallel which try to change the selected materials.
  • On selection of List Material checkbox, listing conditions are created in the table WLK1.
  • On selection of Test Mode checkbox, report runs in simulation mode (Default behavior).
  • No. of Materials per process indicates subset of materials processed before updating the database and which get locked together. By default, 5000 materials can be processed in a process.
The report reads all material variants and configurable materials based on the selection criteria. If a material variant does not have the prerequisite information, it is not considered for migration.
The configurable material and all other material variants of this configurable material are also ignored during migration. The report locks the configurable articles and the associated material variants and is updated in the same process to the database.
Please check the example section below.

Based on the defined reference sites, the system compares the logistical data (MARC, MPOP, MPGD, MFHM, MBEW, MARD) of a non-reference site with the data of the related reference site. In case of deviations on field level, a deviation pointer is inserted into table MABW (Management of Differently Maintained Material Data in Retail) later.

You can run the program either in online or background mode. If all the materials are processed at the first time when you run the program in test mode, we recommend that you run it in the background due to the extended runtime and since a very large number of records may be changed or inserted.

If you want to process all the potential materials in the system, you do not need to enter all materials on the initial screen. The convertible materials will be determined based on the above-mentioned prerequisites.

Once processed, you will be able to see the results in the application log. Use transaction SLG1 (Application Log: Display Logs) with Object = MATU and External ID = MAT2ART_CONV/Transaction code = MAT2ART_CONV.

During execution changes are performed on the following tables:

Table   Description   Database Operation
MARA   General Material Data   Update
MAW1   Material Master: Default Fields and Special Retail Fields   Insert
MVKE   Sales Data for Material   Update
WLK1   Listing Conditions SAP Retail Assortments   Insert
WLK2   Article Master Data SAP Retail/Part POS Control Data   Insert
MABW   Management of Differently Maintained Material Data in Retail   Insert

Example

The following example shows how the report locks and updates the configurable articles and its material variants based on the number of materials per process.

Let’s consider 3 configurable materials C1, C2and C3. ,,

C1has 3 material variants, C2has 2 material variants and C3has 5 material variants.

Let’s assume

S1: collection of configurable material C1and its material variants

S2: collection of configurable material C2and its material variants

S3: collection of configurable material C3and its material variants

Configurable Material   Material Variant     Total Materials
C1     S1   4
C1   C1V1   S1
C1   C1V2   S1
C1   C1V3   S1
C2     S2   3
C2   C2V1   S2
C2   C2V2   S2
C3     S3   6
C3   C3V1   S3
C3   C3V2   S3
C3   C3V3   S3
C3   C3V4   S3
C3   C3V5   S3

The total number of materials to be migrated = 4+3+6 = 13 materials.

Depending on the number of materials per process, the report locks and updates the material data as follows:

  • Number of materials per process = 15 or 14 or 13
The total number of materials to be migrated is less than the number of materials per process (15). Therefore, all 13 materials are locked and updated in a single process.

  • Number of materials per process = 12 or 11 or 10 or 9 or 8 or 7
The total number of materials to be migrated is greater than the number of materials per process (12).
Therefore, all materials related to configurable material C1and C2are locked and updated in one process. Materials related to configurable material C3are locked and updated in another process.

  • Number of materials per process = 6

The total number of materials to be migrated is greater than the number of materials per process (6).
  • All materials related to configurable material C1are locked and updated in one process.

  • All materials related to configurable material C2are locked and updated in another process.

  • All materials related to configurable material C3are locked and updated in different process.

  • Number of materials per process = 5 or 4
The total number of materials to be migrated is greater than the number of materials per process (5).
  • All materials related to configurable material C1are locked and updated in one process.

  • All materials related to configurable material C2are locked and updated in another process.

  • For the configurable material C3, the report internally increases the number of materials per process to 6. All materials related to this configurable material are then locked and updated in another process.

  • Number of materials per process = 3

The total number of materials to be migrated is greater than the number of materials per process (3).

  • The number of materials per process is 3 which is less than the number of materials related to configurable material C1(4). Therefore, the report internally increases the number of materials per process to 4. All materials related to configurable material C1are then locked and updated in one process.

  • The number of materials per process is 3 which is equal to the number of materials related to configurable material C2(3). Therefore, all materials related to configurable material C2are locked and updated in another process.

  • The number of materials per process is 3 which is less than number of materials related to configurable material C3(6). Therefore, the report internally increases the number of materials per process to 6. All materials related to configurable material C3are then locked and updated in another process.

  • Number of materials per process = 2 or 1
The total number of materials to be migrated is greater than the number of materials per process (2).
  • The number of materials per process is 2 which is less than the number of materials related to configurable material C1(4). Therefore, the report internally increases the number of materials per process to 4. All materials related to configurable material C1are then locked and updated in one process.

  • The number of materials per process is 2 which is less than the number of materials related to configurable material C2(3). Therefore, the report internally increases the number of materials per process to 3. All materials related to configurable material C2are then locked and updated in another process.

  • The number of materials per process is 2 which is less than number of materials related to configurable material C3(6). Therefore, the report internally increases the number of materials per process to 6. All materials related to configurable material C3are then locked and updated in another process.






CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 37259 Date: 20240520 Time: 122615     sap01-206 ( 294 ms )
Number of Materials Per Process   Process 1   Process 2   Process 3
15   S1, S2, S3
14   S1, S2, S3
13   S1, S2, S3
12   S1, S2   S3
11   S1, S2   S3
10   S1, S2   S3
9   S1, S2   S3
8   S1, S2   S3
7   S1, S2   S3
6   S1   S2   S3
5   S1   S2   S3
4   S1   S2   S3
3   S1   S2   S3
2   S1   S2   S3
1   S1   S2   S3