2lis Data Sources Enhancement Site

Technical Paper: Strategic Enhancement of 2LIS Data Sources in SAP BW/4HANA 1. Introduction In SAP ERP Central Component (ECC) and SAP S/4HANA, Logistics Information Systems (2LIS) extractors are the backbone for operational reporting in Supply Chain Management (SCM). These extractors (e.g., 2LIS_03_BF for Goods Movements, 2LIS_11_VAITM for Sales Orders) capture delta data from application tables (MSEG, VBAK, LIKP) into SAP BW or BW/4HANA. However, standard extractors often lack specific custom fields, derived calculations, or filters required by modern analytics. Data Source Enhancement is the disciplined process of extending these extractors without breaking SAP standard objects or delta mechanisms. 2. Why Enhance 2LIS Data Sources? Common business drivers include:

Adding Custom Fields: Include Z-fields from custom tables or appended structures (e.g., a "Sales Channel Priority" in the sales order header). Deriving Calculated Fields: Compute net weight from volume density, or calculate aging buckets at extraction time. Filtering Unnecessary Data: Exclude order types ‘ZTEST’ or cancelled goods movements to reduce ETL load. Improving Performance: Push complex joins or calculations to the source system (push-down optimization).

3. Core Technical Architecture of 2LIS Extractors Before enhancement, understand the three-layer architecture:

Data Source (RSA5/RSO2): Definition in the source system (SAP ERP). Contains extract structures, fields, and ODS settings. Extract Structure (SE11): Typically named MC* (e.g., MC03BF0 for goods movements). This is a SAP-delivered structure you can append. Function Module (FM): EXIT_SAPLRSAP_001 (Customer exit for DataSource enhancement) or RSU5_* update rules. Data Transfer Process (DTP) & PSA: Where enhanced data lands in BW. 2lis data sources enhancement

4. Step-by-Step Enhancement Procedure Phase 1: Append Custom Fields to the Extract Structure

Transaction SE11 → Enter the extract structure (e.g., MC11VA0H for sales order header). Click Append Structure → Create ZMC11VA0H . Add your custom fields (e.g., ZZ_REGION_GROUP , ZZ_PRIORITY ). Activate the append structure.

⚠️ Do not modify SAP original structures directly; always use appends. Technical Paper: Strategic Enhancement of 2LIS Data Sources

Phase 2: Extend the DataSource in Transaction RSA5

Transaction RSA5 → Locate the DataSource (e.g., 2LIS_11_VAHDR ). Click Edit → Go to Extract Structures . Your new appended fields will appear with status "Field not filled yet". Mark them as Extraction-Relevant .

Phase 3: Implement Customer Exit (BADI or CMOD) 2LIS extractors use a generic enhancement: RSAP0001 (Customer Exit for DataSource). Why Enhance 2LIS Data Sources

Method: Transaction CMOD → Project ZBW_EXIT → Component EXIT_SAPLRSAP_001 .

Inside the DATA_EXIT subroutine, you populate your custom fields: FORM data_exit CHANGING c_data TYPE table. DATA: wa_data TYPE ANY. " Inline declaration recommended FIELD-SYMBOLS: <fs_ext> TYPE any. LOOP AT c_data ASSIGNING <fs_ext>. " Assign custom field values ASSIGN COMPONENT 'ZZ_REGION_GROUP' OF STRUCTURE <fs_ext> TO FIELD-SYMBOL(<fv_region>). IF <fv_region> IS ASSIGNED. " Example: Derive region group from country CASE <fs_ext>-land1. " Standard field WHEN 'US'. <fv_region> = 'NA'. WHEN 'DE'. <fv_region> = 'EU'. ENDCASE. ENDIF. ENDLOOP. ENDFORM.

Shopping cart