Trade BW Logistic Extraction

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.
com
2008 SAP AG 1
Tr ade BW Logi st i c Ex t rac t i on
Applies to:
This document applies to SAP ERP EhP4 and SAP BW BI_CONT 704.
Summary
This document contains a detailed description about the main logistical extractions on a retail point of view.
Each extractor/DataSource is described on a very detailed level, means field information, used process keys
and retail specifics are mentioned. Additional you can find general informations about how overall handling
and setup of a logistic extraction process, for example stock initialization, reconstruction, necessary
customizing is described in detail.
Author(s):
Company: SAP
Created on: 12 J une 2009
Author Bio
Michael Prokopi is a senior developer in Trading Industries and has been working for SAP since 2001. His
main topics of expertise are Trade BW content.
Trade BW Logistic Extraction
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
2008 SAP AG 2
Table of Contents
Applies to:.....................................................................................................................................................1
Summary......................................................................................................................................................1
Author Bio.....................................................................................................................................................1
Table of Contents..........................................................................................................................................2
Preliminary Remarks.....................................................................................................................................3
Process Description......................................................................................................................................3
ERP Extractor Development..........................................................................................................................4
Customizing..............................................................................................................................................4
Selecting an Industry ) ..........................................................................................................................................4
Process /Transaction Keys....................................................................................................................................5
Determining the Process key.................................................................................................................................8
DataSources for Logistic Data...................................................................................................................9
Purchasing data (scheduled line)......................................................................................................................... 10
Sales & Distribution............................................................................................................................................. 15
Inventory Management........................................................................................................................................ 29
Revaluation at Retail (Retail only)........................................................................................................................ 37
General Information about usage of Business Content................................................................................40
Logistic Extract Structures.......................................................................................................................40
Basic Structure................................................................................................................................................... 40
Customizing Cockpit........................................................................................................................................... 40
Log for Logistic Extract Structures (Tx LBWF)...................................................................................................... 41
Overview about the Process of Reconstruction.................................................................................................... 41
Data Initialization in BW...........................................................................................................................42
Master Data........................................................................................................................................................ 42
Transaction Data (Without Stocks) ...................................................................................................................... 43
Stocks Initialization to SAP BW........................................................................................................................... 43
SAP BW General Remarks for Retail.......................................................................................................48
Tables, Transactions...................................................................................................................................51
Related Content..........................................................................................................................................53
Copyright....................................................................................................................................................54
2008 SAP AG 3
Preli minary Remarks
This document is intended to give a general overview about the movement data extractors on a retail
perspective. The focus is to describe which movement data is normally used in the retail area.
Process Description
The first requirement for modeling Logistics processes in SAP BW as key figures or key performance
indicators (KPIs) was the development of comprehensive extractors for the transaction data (movement
data). This development covers Purchasing, Inventory Management and Sales & Distribution as well as
retail-specific applications retail price revaluation.
Due to continuous operational processes in the source system (SAP ERP), documents that supply data for
evaluations in a data warehouse are constantly being created.
The DataSources described in this document deliver the document data at the detailed level means
documents number, document line item and document date.
Figure 1: General overview about logistic extractors
The following graphic shows the data from the LIS communication structures being used as an interface to
the application. The data is pulled based on extract structures for Logistics to the central Delta Management
(Delta Queue). If we are talking about a reconstruction of data the data will be written into setup tables witch
can be used starting point for a Full data extraction to SAP BW.
2008 SAP AG 4
Figure 2: Detailed view to logistic extractors mentioned in this document
This document describes the development in SAP ERP (OLTP) as well as industry-specific aspects of
Business Content Development for SAP BW.
ERP Extractor Development
The following section describes the extractor development that was carried out in the operative SAP ERP.
The Plug-In development comprises Customizing, transaction data and master data extraction. These are
described in the following sections.
Customizing
Selecting an Industry )
In the BW Customizing for the OLTP System, the correct industry (none, Retail or CP) must be selected to
ensure that the extraction of the transaction data functions correctly (see Figure 3).
2008 SAP AG 5
Figure 3 Selection of the Industry with transaction MCB_
It is not possible to use a combination of industries (Retail AND CP, for example). You must select an
industry for each OLTP System/client. If "none" is selected, updating to the relevant transfer information
structure does not take place.
Remark: It is possible that other IBUs (such as Oil & Gas) may use the Retail/CP extractors in future
releases, and may therefore be included in industry Customizing.
Process /Transaction Keys
The extractors are basically structures that collect information from the documents of the corresponding
Logistics application (Purchasing, Inventory Management or Sales and Distribution, for example) and
transfer it to SAP BW.
The individual applications produce a large number of key figures that must be transferred to SAP BW using
these extractors. By using the "process/transaction key", SAP document information is analyzed in advance
so that key figures for particular processes can be used more easily by customers.
This means that the lines that are to be transferred contain only transfer quantity or transfer value fields.
The actual key figure is hidden behind a process key. This means that generic key figures (transfer quantity
and transfer values) are used, which then acquire a more precise significance in combination with the
process key. The following table shows several lines that are to be transferred, with their various transaction
keys (Purchasing, for example):
2008 SAP AG 6
Transacti on
key
Quantity (in BU,
for example)
Transfer val ue 1
(Purchase price,
for example)
Transfer val ue 2
(Sales price, for
example)*
(Characteri sti cs:
materi al/arti cle,
for example)
Further
characteri sti cs
001 10 PC 30 USD 35 USD CHOCOLATE ...
007 20 CAR 240 USD 270 USD SHIRT ...
002 5 CAR 15 USD 18 USD PANTS ...
... .... .... ... ... ...
Comment: *Sales price exists in Purchasing for Retail only
The first line would mean:
Process key: 001 ->purchase order with external vendor, material/article CHOCOLATE, Quantity 10 pieces
at a purchase price of 30 USD for particular characteristics.
The data is transferred line by line as it appears in the document, which means that for each document item
(in Purchasing for each schedule line number), a record is transferred so that the document hierarchy
(header, item, schedule line) is "flattened".
The process /transaction keys are defined using the Customizing transaction MCB0. The same setting can
be also found in the SAP BW extraction customizing SBIW under Settings for Application-Specific
DataSources (PI) + Logistics + Settings for IBU Retail / CP + Transaction Key Maintenance for SAP BW.
2008 SAP AG 7
Figure 4 - Maintaining the Process/ Transaction Keys
This transaction is based on Customizing table TMCLVBW, text table TMCLVBWT.
As the process keys must generally be dissolved into specific (general ->specific, e.g. Quantity ->Goods
receipt quantity) key figures when queries are created during updating. A thorough knowledge of the process
keys is essential for customer-specific transformations to DataTargets or for creating customer specific
queries.
Example for a routine logic: Update routine for the "Purchase order quantity /external vendor" key figure in
the InfoCube (pseudo-code):
IF COMM_STRUCTURE-PROCESSKEY =`001`.
RESULT =COMM_STRUCTURE-TRANS_AMOUNT.
ELSE.
CLEAR RESULT. Do not update key figure
ENDIF.
2008 SAP AG 8
Process keys are always assigned to their Logistics applications (Example: 02 =Purchasing) and application
component (industry or CORE component). As most of the keys are industry-independent, these are
assigned to the relevant core component (such as MM, SD).
Remark: MM/SD process keys may be broken down into further process keys due to industry requirements.
Example:
Industry independent (Core) Industry dependent
Application MM IS-R
Transaction Key 010/110 - Receipt/issue from
warehouse transfer
002/102 - Goods receipt/issue DC
003/103 - Merchandise clearing receipt/issue
If, therefore, Retail has been selected as the industry, the 010 or 110 keys never appear in the Purchasing
extractor. Instead, the 002/003 or 102/103 keys show that this key has been broken down. Based on the
values and quantities from the DataSource, 010 =002 +003 or 110 =102 +103.
As process keys are supplied interactively in the corresponding LIS function modules, it is possible to use
customer-specific process keys (customer name space 500-999).These keys can be supplied via the
associated customer exit in the Logistics application.
Determining the Process key
To ensure that the process keys are determined using the method described above, a function group with
function modules that enhance the LIS communication structures accordingly was created during extractor
development.
The communication structures have been extended to include the fields necessary for updating DataSources
for specific purposes, for example purchasing document item MCEKPO: MCEKPOBWAP (append structure).
If it is not clear how the process keys were created, a code inspection (debugging) should be performed.
Technical Information:
Development class: MCBW
Function group: MCRS
Function modules:
Function module Descripti on
LOG_CHECK_ENRICHMENT Check enhancement for industry
LOG_CHECK_PROCESSKEY Checks whether a process key exists
LOG_CONTENT_BILLING Enhancement billing
LOG_CONTENT_DELIVERY Enhancement delivery
LOG_CONTENT_ORDER Enhancement sales order
2008 SAP AG 9
LOG_CONTENT_PURCHASING Enhancement purchasing for SAP BW
LOG_CONTENT_PURCHPRICE_REVAL Enhancement cost price revaluation
LOG_CONTENT_SALESPRICE_REVAL Enhancement revaluation at retail
LOG_CONTENT_STOCKS_MSEG Enhancement inventory management
Your choice of transaction key is only active if transaction MCB_ has been used to select an industry!
DataSources for Logisti c Data
In the following chapter the most relevant data sources to run a retail business are named and described in
detail.
Application Area DataSource BW application component
Purchasing 2LIS_02_SCL MM
Material movements 2LIS_03_BF MM_IC
Stock Revaluation 2LIS_03_UM MM_IC
Stock initialization 2LIS_03_BX SD
SD sales order 2LIS_11_VAITM SD
SD delivery 2LIS_12_VCITM SD
SD billing document 2LIS_13_VDITM SD
SD settlement 2LIS_11_V_ITM SD
Retail Revaluation 2LIS_40_REVAL IS-R-IO
The InfoSource 2LIS_40_REVAL was developed especially for SAP Retail, and it belongs to BW application
component IS-R-IO. The other new DataSource do not only belong to the Retail application, and are
therefore assigned to other BW application components:
2008 SAP AG 10
Purchasing data (scheduled line)
2LIS_02_SCL Purchasing Scheduled Line
The Data Source provides purchasing data at document schedule line level.
Relevant Communication Structures (Updating):
- MCEKKO (Purchasing document header)
- MCEKKO (Purchasing document items
- MCEKET (Purchasing document schedule lines)
Relevant extract structure
- MC02M_0SCL with substructures
Characteristics
InfoObject Field i n Transfer
Structure
Descripti on
0MATL_GROUP MATKL Material group
0SCHED_LINE ETENR Schedule line number
0VENDOR LIFNR Vendor number
0SCL_DELDAT EINDT Planned delivery date of document schedule line
0INV_PARTY PREST Invoicing party
0BWAPPLNM BWAPPLNM Application component
0DOC_CAT BSTYP Purchasing document category
0DOC_ITEM EBELP BW: document item number
0DOC_NUM EBELN BW: document number
0DOCTYPE BSART Purchasing document category
0MATERIAL MATNR Material number
0INV_PTY LIFRE Different invoicing party
0SUP_PLANT PLIWK Supplying plant to which partner roles have been
assigned
0SCHED_TIME UZEIT Schedule line time
0ENTRY_DATE SYDAT Date on which the purchasing document was entered
0SUPPL_VEND LLIEF Supplying vendor
0MPN_MATNR EMATN Manufacturer part
0ORD_ADDR PBEST Ordering address
0PARTNER PLIEF Vendor to whom partner roles have been assigned
0SUPPLIER PWLIF Goods supplier
0STGR_LOC LGORT Storage location
2008 SAP AG 11
0STORNO ROCANCEL Cancellation/reversal indicator
0RT_PROMO AKTNR Promotion
0PUR_REASON BSGRU Reason for ordering
0ITM_CAT PSTYP Item category in purchasing document
0PUR_GROUP EKGRP Purchasing group
0PLANT WERKS Plant
0BATCH CHARG Batch number
0PROCESSKEY BWVORG BW: process key
0PURCH_ORG EKORG Purchasing organization
0SUPP_PLANT RESWK Supplying plant
Time Characteristics
Structure
Descripti on
0SCHED_DATE SCL_BEDAT Schedule line date
0DOC_DATE BEDAT Document date
0STAT_DATE SLFDT Statistics date
0PSTNG_DATE BUDAT Posting date in document
0FISCVARNT PERIV Fiscal year variant
Units
InfoObject Field in Transfer Structure
Description
0BASE_UOM LMEIN Base unit of measure
0LOC_CURRCY HWAER Local currency
0PO_UNIT MEINS Purchase order unit of measure
0ORDER_CURR WAERS PO currency
Key Figures
Structure
Descripti on Rocancel?
0NO_RMDRS MAHNZ Number of reminders/expediters X
0ORDER_VAL BWEFFWR Effective order value X
0NO_SCL NOSCL Counter for scheduling agreement schedule lines X
0CPDEOGPVOC DBWGEO Delta PO/GR PP excl. tax X
0CPPVLC BWGEO BW: purchase value in local currency X
0CPPVOC BWGEOO BW: purchase value in order currency X
2008 SAP AG 12
0CPQUAOU BWMNG BW: quantity in order unit X
0CPSTLC BWGVP BW: SalesWmS in local currency X
0CPSVLC BWGVO BW: sales value in local currency X
0SUBTOT_OC1 BWKZWI1 Subtotal 1 X
0NUMERATOR UMREN Numerator for conversion of sales unit into SKU.
0PUR_GROVAL BWBRTWR Gross order value in order currency X
0EXCHG_RATE WKURS Currency exchange rate for price determination and
statistics
0DENOMINTR UMREZ Denominator for conversion of sales unit into SKU.
0CPDEOGQUOU DBWMNG Delta PO/GR order quantity X
Column ROCANCEL shows the relevant key figure during extraction, multiplied by -1 if the 0STORNO (=
ROCANCEL) field has been marked X. This occurs when, for example, a document item is changed. If this
is the case, the system extracts the unchanged old data before changes are made with ROCANCEL =X and
the new data after the change with ROCANCEL is extracted. This means that the data record containing the
old data with negative values then cancels out the original data.
Measuring vendor quantity reliability or showing open order stock correctly is done by including the delta
fields (quantity, value) in the transfer information structure and updating them to the appropriate InfoCubes.
Deltas occur when the goods receipt quantity entered is greater (negative delta) or smaller (positive delta)
than the quantity ordered. Deleting purchase orders also creates deltas.
The application component becomes more important if customers from mixed industries use Industry 1 (CP,
for example) in an R/3 System, and Industry 2 (Retail, for example) in a different R/3 System. In cases such
as this where a SAP BW System is supplied by both systems, the process key may no longer be
unambiguous.
Specific Retail enhancements
InfoObject Field i n Transfer Structure Descripti on
- ITEM_CAT EA Retail BW Extr. Enhancement: Item Type
- REC_TYPE EA Retail BW Extr. Enhancement: Data Record Type
- ATTYP Material Category (lot, display, set)
- VLFKZ Plant category (Distribution center or store)
All these 4 fields are used for the explosion of structured articles to there components. The explosion of the
structured articles is mainly done in SAP ERP.
2008 SAP AG 13
Therefore a new customizing is defined that supports the explosion depending on the plant category
(distribution center or store) and the material category (lot, display or set). The customizing can be found in
the SAP reference IMG (SPRO): Logistics General + Material Master + Retail-Specific Settings + Settings
for Structured Materials + Structured Material in Logistics Process.
Depending on the settings in the customizing the explosion of structured articles is executed during the
extraction of the data to SAP BW. The necessary coding is located in a acti ve delivered BADI
implementation WRF_BWEXT_STRUKTART of BADI RSU5_SAPI_BADI. The BADI is also used and
relevant for DataSources 2LIS_03_BF and 2LIS_03_BX.
The fields ITEM_CAT contains the information if a record delivered by the DataSource is an original item or if
the item was created by the above mentioned BADI implementation WRF_BWEXT_STRUKTART. The field
will be interpreted in the start routine of the corresponding InfoSource 2LIS_02_SCL.
Value Meaning
00 Original position
01 Position created for retail by BADI implementation
WRF_BWEXT_STRUKART
The field REC_TYPE contains the information if the record contains is header component or a item
component of a structured article. This field is currently not in the data flow to SAP BW but can be used for
detailed analysis.
Value Meaning
0 Header component of a structured article
1 Component of a structured article
Currently in the SAP BW content there are no corresponding InfoObject for the 4 new fields and therefore no
mapping exists in the transformation from DataSource to InfoSource.
Process/ transaction keys
Application Process key Meaning
MM (02) 0 Undefined Operation/Vendor
MM (02) 1 Purchase Order/Vendor
MM (02) 2 Goods Receipt/Vendor
MM (02) 3 Invoice/Vendor
2008 SAP AG 14
MM (02) 4 Scheduling Agreement/Vendor
MM (02) 5 Returns Order / Vendor
MM (02) 6 Returns/Vendor
MM (02) 7 Credit Memo/Vendor
MM (02) 8 Contract / Vendor
MM (02) 9 Offer / Vendor
MM (02) 40 Inquiry / Vendor
MM (02) 41 Return Sched.Agreemt / Vendor
MM (02) 10 Undefined/ Intern. Comp. Code
MM (02) 11 Purch. Order/Intern. Comp.Code
MM (02) 12 GR/Intern. Company Code
MM (02) 14 Sched. Agreement/Int. Co. Code
MM (02) 15 Return Orders/Int. Comp. Code
MM (02) 16 Returns/Internal Company Code
MM (02) 51 Return Sched.-Agreement / Int. Comp. Code
MM (02) 20 Undefined/Cross-Company Code
MM (02) 21 Purchase Order/Cross-Co. Code
MM (02) 22 GR/Cross-Company Code
MM (02) 23 Invoice/Cross-Company Code
MM (02) 24 Sched. Agreemt/Cross-Co.Code
MM (02) 25 Returns Order/Cross-Comp. Code
MM (02) 26 Returns/Cross-Company Code
2008 SAP AG 15
MM (02) 27 Credit Memo/Cross-Comp. Code
MM (02) 28 Contract / Cross-Company
MM (02) 61 Return Sched.-Agreement/ Cross-Comp.
Code
Note: All the process keys are relevant for both Retail and CP customers!
Sales & Distribution
2LIS_11_VAITM: SD Sal es Document Items
This DataSource contains document data for sales orders at item level.
Relevant Communication Structures:
- MCVBAK Sales order document header
- MCVBAP Sales order document item
- MCVBKD Sales Document: Commercial Data
- MCVBUK Sales Document: Header Status; Admin.Data
- MCVBUP Sales Document: Item Status
Relevant extract structure:
- MC11VA0ITM with substructures
InfoObject Field in
transf.structure
Descripti on
0STORNO ROCANCEL Cancelling ind.
0DOC_NUMBER VBELN SD document
0REJ ECTN_ST ABSTA Rejection stat.
0S_ORD_ITEM POSNR Item
0STS_ITM UVALL Item
0STS_BILL UVFAK Item bill.data
0STS_PRC UVPRS Pricing
0STS_DEL UVVLK Item deliv.data
0QUOT_FROM ANGDT Valid from
0DOC_TYPE AUART Sales doc.type
0ORD_REASON AUGRU Order reason
0QUOT_TO BNDDT Valid to
0COMP_CODE BUKRS Company code
0BILL_BLOCK FAKSK Billing block
2008 SAP AG 16
0SOLD_TO KUNNR Sold-to party
0RATE_TYPE KURST Exch.rate type
0CUST_GRP1 KVGR1 Customer grp 1
0DEL_BLOCK LIFSK Delivery block
0STAT_CURR STWAE Statist. curr
0DOC_CATEG VBTYP Document cat.
0SALES_OFF VKBUR Sales office
0SALES_GRP VKGRP Sales group
0SALESORG VKORG Sales org.
0DISTR_CHAN VTWEG Distr. channel
0REASON_REJ ABGRU RejectionReason
0CH_ON AEDAT Changed on
0ORDER_PROB AWAHR Order probab.
0GROSS_WGT BRGEW Gross weight
0BWAPPLNM BWAPPLNM Application comp.
0PROCESSKEY BWVORG BW:Trnsctn key
0BATCH CHARG Batch
0EXCHG_CRD CMKUA Exchange rate
0EANUPC EAN11 EAN/UPC
0CREATEDON ERDAT Created on
0CREATEDBY ERNAM Created by
0CREA_TIME ERZET Time
0BILBLK_ITM FAKSP Billing block
0UNIT_OF_WT GEWEI Weight unit
0CML_CF_QTY KBMENG CumConfirmedQty
0CML_CD_QTY KLMENG CumConfirmedQty
0COND_UNIT KMEIN Unit of measure
0SALESDEAL KNUMA_AG Sales deal
0COND_PR_UN KPEIN Pricing unit
0CML_OR_QTY KWMENG Order quantity
0SUBTOTAL_1 KZWI1 Subtotal 1
2008 SAP AG 17
0MIN_DL_QTY LFMNG Min. dely qty
0STOR_LOC LGORT StorageLocation
0REQDEL_QTY LSMENG Required DlvQty
0MATERIAL MATNR Material
0MAT_ENTRD MATWA MaterialEntered
0BASE_UOM MEINS Base unit
0MATL_GRP_1 MVGR1 MaterialGroup 1
0NET_PRICE NETPR Net price
0NET_VALUE NETWR Net value
0NET_WT_AP NTGEW Net weight
0UNLD_PT_WE PABLA UnlPt ShiptoPar
0BILLTOPRTY PKUNRE Bill-to party
0PAYER PKUNRG Payer
0SHIP_TO PKUNWE Ship-to party
0PROD_HIER PRODH Prod.hierarchy
0FORWAGENT PSPDNR FwdAgent
0ITEM_CATEG PSTYV Item category
0SALESEMPLY PVRTNR Sales employee
0ROUTE ROUTE Route
0DIVISION SPART Division
0STAT_DATE STADAT Statistics date
0EXCHG_STAT STCUR Exch.rate stats
0SUB_REASON SUGRD Reason
0DENOMINTR UMVKN Denominator (Factor conv.:SalesUnit ->WH Unit)
0NUMERATOR UMVKZ Nominator (Factor conv: SalesUnit ->WH Unit)
0DENOMINTRZ UMZIN Denominator (Factor for converting sales units to base
units (target qty)
0NUMERATORZ UMZIZ Numerator (Factor for converting sales units to base
units (target qty)
0ST_UP_DTE VDATU UpdateDateStats
2008 SAP AG 18
0PRVDOC_CTG VGTYP Prec.doc.categ.
0VOLUMEUNIT VOLEH Volume unit
0VOLUME_AP VOLUM Volume
0SALES_UNIT VRKME Sales unit
0SHIP_POINT VSTEL Shipping point
0DOC_CURRCY WAERK Doc. currency
0COST WAVWR Cost
0PLANT WERKS Plant
0TARGET_QU ZIEME Target qty UoM
0TARGET_QTY ZMENG Target quantity
0TARG_VALUE ZWERT Out.agr.targ.vl
0SALES_DIST BZIRK Sales district
0SERV_DATE FBUDA Serv.rendered
0BILL_DATE FKDAT Billing date
0INCOTERMS INCO1 Incoterms
0INCOTERMS2 INCO2 Incoterms 2
0CUST_GROUP KDGRP Customer group
0ACCNT_ASGN KTGRD AcctAssgGr
0EXCHG_RATE KURSK Exchange rate
0TRANS_DATE KURSK_DAT Translation dte
0PRICE_DATE PRSDT Pricing date
0RT_PROMO WAKTION Promotion
0PRODCAT WMINR Prod.cat.no.
0ORDER_CURR WAERK_VBAK Doc. Currency
0DIV_HEAD SPARA Division
0DOC_CATEGR VGTYP_AK Sales doc.type ref.d
0WBS_ELEMT PS_POSID WBS element
0ORD_ITEMS ANZAUPO Order items
0FISCVARNT PERIV Fi.year variant
0TAX_VALUE MWSBP Tax amount
Process keys
SD (11) 000 Sales order / misc.
SD (11) 001 Sales order / standard
2008 SAP AG 19
SD (11) 002 Returns order / standard
SD (11) 003 Sales order / third-party
SD (11) 004 Returns order / third-party
SD (11) 005 Customer quotation
2LIS_11_V_ITM: SD Sal es Item Data Settl ement
This DataSource contains settlement values from sales documents (sales order) and delivery documents at
item level. It can be used for transferring open values from SD (for example, open order quantity).
- MCVBAK Sales order document header
- MCVBAP Sales order document item
- MCVBKD Sales Document: Commercial Data
- MC11V_0ITM with substructures
InfoObject Field in transfer
structure
Descripti on
0DOC_NUMBER VBELN SD document
0REJ ECTN_ST ABSTA Rejection stat.
0S_ORD_ITEM POSNR Item
0SOLD_TO KUNNR Sold-to party
2008 SAP AG 20
0STAT_CURR STWAE Statist. curr.
0REASON_REJ ABGRU RejectionReason
0BATCH CHARG Batch
0CREATEDON ERDAT Created on (1)
0BILBLK_ITM FAKSP Billing block
0OPENORDQTY OAUME Open orders qty
0OPENORDVAL OAUWE Open orders
0PAYER PKUNRG Payer
0ROUTE ROUTE Route
0DB_CRD_IND SHKZG Returns
0DIVISION SPART Division
0DENOMINTR UMVKN Denominator (Factor conv.:SalesUnit ->WH
Unit)
2008 SAP AG 21
0PLANT WERKS Plant
0TRANS_DATE KURSK_DAT Translation dte
0RT_PROMO WAKTION Retail Promotion
0DIV_HEAD SPARA Division
0OP_DOC_ITM ANZOAUPO Open order items
0DLV_QTY LFIMG_AVME Delivery qty
0DEL_VAL MCBW_LFWRT Del. order value
0NETPR_VKM MCBW_NETPR_AVKM NtPrSlsQtyOrItm
No transaction keys exist for this DataSource. Open values and quantities always relate to a specific sales
order and no differentiation is made, for example, between internal and external procedures.
(1) This field was also transferred in the DataSource to allow open orders (quantity, value) to be determined
correctly during BW updating. This date is necessary to ensure that the open order quantity is determined
correctly for the time period.
2LIS_12_VCITM: SD Shipping, Delivery item data
This DataSource extracts delivery document data at item level.
The following DataSources can also be used for transferring delivery document data. They have not yet been
used in Business Content for Retail / CP:
2LIS_12_VCHDR: SD Shipping, Delivery header data
2LIS_12_VCSCL: SD Shipping, Delivery schedule line data.
- MCLIKP Delivery document header
- MCLIPS Delivery document item
2008 SAP AG 22
- MC11VC0ITM with substructures
InfoObject Field in
transf.structure
Descripti on
0DELIV_NUMB VBELN SD document
0PICK_CONF KOQUA Confirmation
0STS_PICK KOSTA Picking status
0DELIV_ITEM POSNR Item
0GOODSMV_ST WBSTA GoodsMovementSt
0UNLOAD_PT ABLAD Unloading point
0SOLD_TO KUNAG Sold-to party
0SHIP_TO KUNNR Ship-to party
0DEL_TYPE LFART Delivery type
0SHIP_DATE LFDAT Delivery date
0CREDITOR LIFNR Vendor
0LOAD_PT LSTEL Loading point
0ROUTE ROUTE Route
0GI_DATE WADAT Planned GI date
0ACT_GI_DTE WADAT_IST Actual GI date
0GRS_WGT_DL BRGEW Gross weight
2008 SAP AG 23
0BATCH CHARG Batch
0CREATEDBY ERNAM Created by
0CREA_TIME ERZET Time
0BILBLK_DL FAKSP Block
0BUS_AREA GSBER Business area
0PICK_INDC KOMKZ Picking ID
0CONSU_FLAG KZVBR Consumption
0DLV_QTY LFIMG Delivery qty
0ACT_DL_QTY LGMNG Actual dlv.qty
0WHSE_NUM LGNUM Warehouse no.
0STRGE_BIN LGPLA Storage bin
0STRGE_TYPE LGTYP Storage type
0NET_WGT_DL NTGEW Net weight
0PAYER PKUNRG Payer
0ITM_TYPE POSAR Item type
2008 SAP AG 24
0SHP_PR_TMF VBEAF Fixed proc.time
0SHP_PR_TMV VBEAV Var. proc. time
0REFER_DOC VGBEL Reference doc.
0REFER_ITM VGPOS Reference item
0PRVDOC_CTG VGTYP Document cat.
0VOLUME_DL VOLUM Volume
0PLANT WERKS Plant
0NO_DEL_IT ANZLIPOS NoDlvItems
0DIVISION SPARA Division
0DEL_WA_DH WA_DELAY_LF GI delay
Process keys
SD (12) 100 Misc. customer delivery
SD (12) 101 Warehouse delivery / customer
IS-R(12) 102 Promotion delivery customer
SD (12) 103 Cross-docking / customer delivery
SD (12) 104 Flow-through / customer delivery
SD (12) 105 Distribution of returns / customer delivery
SD (12) 106 Customer returns
2008 SAP AG 25
SD (12) 150 Misc. delivery / cross-company-code
SD (12) 151 Warehouse delivery / cross-company-code
IR-R(12) 152 Promotion delivery / cross-company-code
SD (12) 153 Cross Docking / cross-company-code
SD (12) 154 Flow Through / cross-company-code
SD (12) 155 Distribution of returns / cross-company-code
SD (12) 156 Returns /cross-company-code
SD (12) 180 Misc. delivery / within company code
SD (12) 181 Warehouse delivery / within company code
IS-R(12) 182 Promotion delivery / within company code
SD (12) 183 Cross-docking / within company code
SD (12) 184 Flow-through / within company code
SD (12) 185 Distribution of returns / within company code
SD (12) 186 Returns / within company code
Note: The process keys 102, 152 and 182 are only relevant for Retail
2LIS_13_VDITM: SD Bill ing Document, Document item data
This DataSource extracts billing document data at item level.
- MCVBRK Billing document header
- MCVBRP Billing document item
- MC13VD0ITM with substructures
InfoObject Field in
transf.structure
Descripti on
2008 SAP AG 26
0BILL_NUM VBELN SD document
0BILL_ITEM POSNR Item
0BILL_TYPE FKART Billing type
0BILL_DATE FKDAT Billing date
0BILL_CAT FKTYP BillingCategory
0SOLD_TO KUNAG Sold-to party
0PAYER KUNRG Payer
0EXRATE_ACC KURRF Exch.rate-acct.
0STAT_CURR STWAE Statist. curr.
0DISTR_CHAN VKORG Sales org.
0SALESORG VTWEG Distr. channel
0DOC_NUMBER AUBEL Sales document
0S_ORD_ITEM AUPOS Item
0REBATE_BAS BONBA Rebate basis
0REBATE_GRP BONUS Vol. rebate grp
0GRS_WGT_DL BRGEW Gross weight
0BATCH CHARG Batch
0SERV_DATE FBUDA Serv.rendered
0INV_QTY FKIMG Billed qty
0BILL_QTY FKLMG Bill.qty in SKU
0SALESDEAL KNUMA_AG Sales deal
0CO_AREA KOKRS Controllng area
0COSTCENTER KOSTL Cost center
0TRANS_DATE KURSK_DAT Translation date
2008 SAP AG 27
0REQ_QTY LMENG Required qty
0TAX_AMOUNT MWSBP Tax amount
0NETVAL_INV NETWR Net value
0NET_WGT_DL NTGEW Net weight
0ITM_TYPE POSAR Item type
0PROV_GROUP PROVG Commission grp
0PRICE_DATE PRSDT Pricing date
0CSHDSC_BAS SKFBP Csh.disc.bas
0SCALE_QTY SMENG Scale quantity
0DIVISION SPARA Division
0DIV_HEAD SPART Division
2008 SAP AG 28
0REFER_DOC VGBEL Reference doc.
0REFER_ITM VGPOS Reference item
0VOLUME_DL VOLUM Volume
0COST WAVWR Cost
0PLANT WERKS Plant
0NO_INV_IT ANZFKPOS No.billng items
0GROSS_VAL BRTWR Gross value
Process keys
SD (13) 200 Misc. billing
SD (13) 201 Sales / standard
SD (13) 202 Credit memo / standard
SD (13) 203 Sales / third-party
SD (13) 204 Credit memo / third-party
2008 SAP AG 29
Inventory Management
2LIS_03_BF - Material movements from Inventory Controlling
This DataSource is used to transfer all material movements data from Logistics Inventory Management. Data
is created for each single item (stored in document table MSEG). No revaluations are extracted from
Financial Accounting (UM). DataSource, 2LIS_03_UM, is created for this process (see the next section).
Relevant Communication Structure
- MCMSEG (Material document, Event BF)
- MC03BF0 with substructure
The fields BWGEO, BWGVO, BWGVP and BWMNG will be multiplied by -1 if movements are cancelled (for
more information, see below). The original document fields, such as DMBTR and MENGE will, however,
remain unchanged and are an exact match of the characteristics for MSEG.
InfoObject Field in transfer-
structure
Descripti on Rocancel?
0STORNO ROCANCEL Cancel. ind.
0COORDER AUFNR Order
0VAL_CLASS BKLAS Valuation class
0DOC_DATE BLDAT Document date
0STOCKTYPE BSTAUS LIS stk values (3)
0STOCKCAT BSTTYP Stock cat. LIS
0PSTNG_DATE BUDAT Posting date
0COMP_CODE BUKRS Company Code
0BWAPPLNM BWAPPLNM Application comp. (4)
0MOVETYPE BWART Movement type
0STOCKRELEV BWBREL BW: Stock rel.
0CPPVLC BWGEO BW:CValLocCrcy X
0CPSVLC BWGVO BW:CValLocCrcy X
0CPSTLC BWGVP BW: RtlTLocCrcy X
0VAL_TYPE BWTAR Valuation type
0CPQUABU BWMNG BW: Qty BUn X
0PROCESSKEY BWVORG Transfer process
0BATCH CHARG Batch
0VALUE_LC DMBTR LC amount
0MATMREA GRUND Reason for mvt.
2008 SAP AG 30
0CO_AREA KOKRS CO area
0SOLD_TO KUNNR Customer
0WHSE_NUM LGNUM Whse number
0STOR_LOC LGORT Stor. location
0STRGE_BIN LGPLA Storage bin
0STRGE_TYPE LGTYP Storage type
0VENDOR LIFNR Vendor
0DOC_NUM MBLNR Material doc.
0QUANT_B MENGE Quantity
0DOC_YEAR MJ AHR Mat. doc. year
0PROFIT_CTR PRCTR Profit center
0DCINDIC SHKZG Debit/credit indicator (1)
0LOC_CURRCY WAERS Local currency
0PLANT WERKS Plant
0DOC_ITEM ZEILE Item
0CPNOITEMS NOPOS Counter Items X
0MOVE_PLANT UMWRK Receiving plant
(1) The debit/credit indicator shows the direction of the material movement (S =stock increase (receipt), H =
stock reduction (issue)). This indicator should be taken into account during InfoCube updating. The value
of the debit/credit indicator can usually be derived from the value of the process key (e.g. process key
001 =goods receipt external vendor ->debit/credit indicator =S). If material documents are canceled,
the cancellations can be easily recognized as they are differentiated from the original procedures by the
reversed debit/credit indicator (e.g. transaction key =001 and debit/credit indicator =H ->canceled
goods receipt vendor). In the supplied standard, cancellations reduce the original key figure. The
significance of the debit/credit indicator is explained in greater detail later in this document.
(2) The "Relevant to stock" indicator determines whether or not the material document line changes the
stock figure and must therefore be updated. Movements that do not cause a change in stock are
consumption postings or transaction postings in connection with inventory management by material
group (Retail only). This should be taken into account when updating stocks in SAP BW.
(3) The stock characteristic value (unrestricted use, in quality inspection etc.) is significant in combination
with the stock category (valuated, vendor consignment etc.). It is possible to model this in customer-
specific InfoCubes (caution: only quantities can be compared for stock categories other than valuated
stock, as changes in stock value do not allow projections to the stock characteristic values to be made).
2008 SAP AG 31
Stock category
Stock
characteristic
value
V
a
l
u
a
t
e
d

s
t
o
c
k
V
e
n
d
o
r

c
o
n
s
i
g
n
m
e
n
t

s
t
o
c
k
S
a
l
e
s

o
r
d
e
r

s
t
o
c
k
P
r
o
j
e
c
t

s
t
o
c
k
R
e
t
u
r
n
a
b
l
e

t
r
a
n
s
p
o
r
t

p
a
c
k
a
g
i
n
g
Unrestricted
use
X X
In quality
inspection
X X
Blocked X X
In Transit
etc... X X
(4) The application component increases in significance if mixed-industry customers use Industry 1 (CP, for
example), in one R/3 System, and Industry 2 (such as Retail) in another R/3 System. In such cases,
where the SAP BW System is supplied by both systems, the process key may be ambiguous.
Additional retail fields
InfoObject Field in
transfer-
structure
Descripti on Area which is using the
additional fields
- ITEM_CAT EA Retail BW Extr. Enhancement: Item
Type
Explosion of structured
articles
- REC_TYPE EA Retail BW Extr. Enhancement: Data
Record Type
- ATTYP Material Category
- VLFKZ Plant category
0RSL_STAUTO SAUTO Item automatically created ERMA Stock ledger
0RSL_STMAT MATST Structured material
0RT_SASTST VKSTT Value at Sales Prices Including Value-
Added Tax
0RT_SASTSV VKSTA Value at sales prices excluding value-
added tax
0RT_MOVTRAN UMLKZ Indicator: Movement type is stock transfer
2008 SAP AG 32
0RT_MOVRET RETKZ Indicator: Return from call
0RT_MOVINV INVKZ Indicator: Movement type is physical
inventory
0RT_MOVADJ KORR Indicator: Movement type is inventory
correction
0RT_MATPOST UMMATKZ Transfer Posting Material to Material
Normally the
same info. as
0LOC_CURRCY
WAERSST Currency Key
0RT_CPUDT CPUDT Day On Which Accounting Document Was
Entered
RMA (Retail Method of
Accounting)
0RMA_XCC RMA_XCC Relevant Valuation Method
0MA_LNK RMA_LINKP Item from Corresponding Stock Removal
0RMA_RFLG RMA_BWEXT_
REL
Flag: Cross-Company Code Stock
Transfer
Additional fields for explosion of structured articles:
The same append WRF_MC03BF0_ADDON_SMAT is used as described for the DataSource 2LIS_02_SCL.
If you need further information about the business logic behind these fields please read chapter 02-
Purchasing.
Additional fields for ERMA stock Ledger:
These fields are relevant if a customer wants to use the SAP BW Business Content in the area of ERMA
stock ledger, delivered with BI CONT 7.03 SP6. All fields are not automatically added to the extraction
structure. The fields must be added to the extraction structure by activating the corresponding business
functions and executing a XPRA (report RMCSBWXP_COM). Therefore also no mappings from ERP fields
to BW InfoObjects are delivered in the transformation. The InfoObjects in quotes are available in the
InfoSource and can be manually mapped to the source fields of the ERP.
Additional fields for RMA:
In case that the Business Function Retail Method of Accounting (ISR_RETAIL_RMA, ISR_RETAIL_RMA2,
ISR_RETAIL_RMA_3, ISR_APPL_AGENCY_4, ) is activated, the respective extract structure will be
augmented automatically by these additional fields. For this fields again no standard mapping to a BW
InfoObject exists but the table above can be used to create a manual mapping.
Application Process Key Meaning
MM (03) 000 Misc. receipts
2008 SAP AG 33
MM (03) 001 Goods receipt / vendor
MM (03) 004 Article transfer posting receipt
MM (03) 005 Stock correction inventory +
MM (03) 006 Stock correction other +
IS-R (03) 007 Receipt value-only article (single article posting)
MM (03) 010 Receipt from stock transfer
IS-R (03) 002 Merchandise clearing receipt
IS-R (03) 003 GR from DC
MM (03) 100 Misc. issues
MM (03) 101 Returns / Vendor
MM (03) 104 Article transfer posting issue
MM (03) 105 Stock correction inventory -
MM (03) 106 Stock correction other -
IS-R (03) 107 Issue value-only article (single article posting)
MM (03) 110 Issue from stock transfer
IS-R (03) 102 Merchandise clearing issue
IS-R (03) 103 GI from DC
IS-R (03) 201 Permanent markdown
IS-R (03) 202 Markdown cancellation
IS-R (03) 203 Transfer out RMA
IS-R (03) 211 Markup
IS-R (03) 212 Markup cancellation
IS-R (03) 213 Transfer in RMA
2008 SAP AG 34
IS-R (03) 450 Generic Article (not relevant)
Note: The process keys 002/003 and 102/103 further describe the processes from the core keys 010/110.
As can be seen from the overview, the process keys from Inventory Management can be divided into
receipts and issues. They can also be divided into canceled and regul ar procedures.
An S in the debit/credit indicator shows a regular receipt, while a regular issue is marked with an H. The
opposite is true for canceled procedures.
Procedure Descripti on Debit/credit
indicator S
Debit/credit
indicator H
0 Misc. receipts Regular Canceled
1 Goods receipt / vendor Regular Canceled
2 Merchandise clearing / receipt Regular Canceled
3 Goods receipt / DC Regular Canceled
4 Article transfer posting / receipt Regular Canceled
5 Stock correction inventory + Regular Canceled
6 Stock correction other + Regular Canceled
7 Receipt value-only article Regular Canceled
10 Receipt from stock transfer Regular Canceled
R
e
c
e
i
p
t
s
100 Misc. issues Canceled Regular
101 Returns receipt / vendor Canceled Regular
102 Merchandise clearing / issue Canceled Regular
103 Goods issue / DC Canceled Regular
104 Article transfer posting / issue Canceled Regular
105 Stock correction inventory - Canceled Regular
106 Stock correction other - Canceled Regular
107 Issue value-only article Canceled Regular
110 Issue from stock transfer Canceled Regular
I
s
s
u
e
s
NB: Cancellations for the DataSource are recognized by the entry 0STORNO =X (=ROCANCEL). The
fields maked with "X" in the table are transferred with negative values.
2LIS_03_UM - Stock Revaluations
This DataSource contains data from value-based revaluations from Financial Accounting (only data from
Financial Accounting (documents stored in table BSEG) that is generated because of revaluations). This
2008 SAP AG 35
data is necessary for updating value-based stock changes for valued stock in BW. The DataSource also
contains key figures that are referred to as "Cost-price revaluations".
Relevant Communication Structure:
- MCMSEG (Material document, Event UM)
- MC03UM0 with substructure
structure
Descripti on
0DOC_NUM BELNR Document number
0VAL_CLASS BKLAS Valuation class
0DOC_DATE BLDAT Document date
0PSTNG_DATE BUDAT Posting date
0MOVETYPE BWART Movement type
0CPPVLC BWGEO BW:CValLocCrcy
0CPQUABU BWMNG BW: Qty BUn
0PROCESSKEY BWVORG BW:Transaction key
0VALUE_LC DMBTR LC amount
0FISCYEAR GJ AHR Fiscal year
0CO_AREA KOKRS Controllng area
0SOLD_TO KUNNR Customer
0VENDOR LIFNR Vendor
0DCINDIC SHKZG Debit/credit
0LOC_CURRCY WAERS Local currency
0PLANT WERKS Plant
0CPNOITEMS NOPOS Counter Items
2008 SAP AG 36
0QUANT_B MENGE Quantity
0STORNO is not important for this DataSource as no cancellations in SAP ERP for revaluations have
occurred.
Process/transacti on keys
MM (03) 050 Misc. revaluation +
MM (03) 051 Revaluation / price change +
MM (03) 052 Revaluation / invoice verification +
MM (03) 150 Misc. revaluation -
MM (03) 151 Revaluation / price change -
MM (03) 152 Revaluation / invoice verification
2LIS_03_BX - Stock Initialization
In order to model stocks in BW, it is necessary to initialize the current operational stock in the source system.
To do this the DataSource 2LIS_03_BX can be used.
- MC03BX0 with substructure
The extract structure MC03BX0 includes the complete extract structure from DataSource 2LIS_03_BF
MC03BF0, there it is not described again.
A stock initialization must be started manually using transaction MCNB. There it is possible to schedule the
init at the store/article/storage location level. To get a better performance it is recommended not to switch on
the flag: Zero Stock to be transferred. To create zero stock information for the stock InfoCubes in SAP BW,
especially for the correct marker update, it is necessary to execute report SAP_REFPOINT_COMPLETE
(note 823951).
An additional performance improvement can be reached by switching of the complete RIS enrichment in
transaction MCH_ (refer to note 728360). It is not recommended to execute the stock initialization without
any restriction by plant, material or storage location. These input fields should be used to create work
packages for the stock initialization process.
2008 SAP AG 37
Figure 1: Stock Initialization for 2LIS_03_BX
This program should always be scheduled or run in the background.
Revaluation at Retail (Retail only)
2LIS_40_REVAL Revaluation at Retai l (Retai l onl y)
This DataSource is used to transfer item-exact data from the retail price revaluation document (USEG)
(Retail only).
- MCUSEG
- MC40RP0REV with substructure
structure
Descripti on
0STOCKRELEV BWBREL BW: Stock rel.
0CPPVLC BWGEO BW:CValLocCrcy
0CPSVLC BWGVO BW:SValLocCrcy
0CPSTLC BWGVP BW: RtlTLocCrcy
0CPQUABU BWMNG BW: Qty BUn
0CPQUASU BWMVE BW: Qty in SUn
2008 SAP AG 38
0RT_REVREAS PV_GRUND Reason SP chng
0DCINDIC SHKZG Debit/credit
0RT_NOAFFMA SPANN Not aff. margin
0DOC_YEAR UBJ AHR Rev.doc. year
0DOC_NUM UBLNR Value change doc
0DENOMINTR UMVKN Denominator
0NUMERATOR UMVKZ Nominator
0DOC_ITEM UZEIL Item number
0RT_REVDAT VPDAT SP change date
0PLANT WERKS Plant
0CPNOITEMS NOPOS Counter Items
Additional fi elds for retail
structure
Descripti on Area which is using the
additional fields
0RT_COSTAFF AFFECT_COST_VAL Adjust Cost Value
(Result)
Stock Ledger and RMA
0RMA_RFLG BWEXT_REL Relevant Valuation
Method
0RT_UPSTA UPSTA Item status of retail
revaluation document
0RT_SPRCHTY UAKT Change Category of
Sales Price Origin from
Old to New Price
0RT_VKSNO VKSALN_OLD Total inventory value at
retail without tax
0RT_VKSPO VKSAL_OLD Value of Total Valuated
Stock at Sales Price
The cursive fields where not directly added to the extract structure. That means that these fields are not
automatically available at customer side and must be added executing the XPRA concept. The fields must
be added to the extraction structure by activating the corresponding business functions and executing a
XPRA (report RMCSBWXP_COM).
Therefore also no mappings from ERP fields to BW InfoObjects are delivered in the transformation. The
InfoObjects in quotes are available in the InfoSource and can be manually mapped to the source fields of the
ERP.
2008 SAP AG 39
IS-R (40) 000 Undefined / Revaluation at Retail
IS-R (40) 001 Revaluation at Retail -
IS-R (40) 002 Misc. issues / Revaluation at Retail
IS-R (40) 011 Revaluation at Retail +
IS-R (40) 012 Misc. receipts / Revaluation at Retail
IS-R (40) 101 Markdown Cancellation
IS-R (40) 111 Markup Cancellation
IS-R (40) 201 Permanent Markdown RMA
IS-R (40) 211 Markup RMA
2008 SAP AG 40
General Information about usage of Business Content
Logi sti c Extract Structures
Basic Structure
Logistics Extract Structures are used for extracting movement data and have been created to replace the
transfer info structures that have been used in the past. Documents are either created, changed or deleted in
the application (for example, Purchasing, Inventory Management). The new data is then prepared online in
communication structures separate per application which are then updated the Central Delta Management
via the extract structures of the DataSource. The data transfer can be done in three different update modes,
direct delta (data is written directly into the delta queue), queued delta (first the data is collected in a qRFC
queue before the data will be transferred with a scheduled process to the delta queue) or unserialized V3
Posting (only used for application 03-Inventory Controlling). In transaction RSA7 the data can be used to
display the data in the Delta queue. With the transaction RSA3 it is possible simulate a BW extraction
depending on parameters like update mode, Package size.
A additional possibility is to load/reload a complete document history using the reconstruction functionality.
For each application a separate report/transaction exists that can be used to fill so called setup tables. This
setup tables are finally used to transfer the data to SAP BW if the uses chooses a full upload/request in the
corresponding Info Package of the DataSource.
Only one restructuring table exists for each extraction structure. It has the same name as the extraction
structure with SETUP as postfix, for example, extraction structure MC03BF0, restructuring table
MC03BF0SETUP.
Customizing Cockpit
With this Cockpit you can manage extract structures that are to be used to copy logistics movement-data
from Online Transaction Processing into the SAP BW. Extract structures are filled in with information from
the communication structures.
The cockpit contains the following functions, which are listed in their execution sequence:
1. Maintaining Extract Structures
Each extract structure can be maintained from customer based on the delivered SAP version. The extract
structure is provided with information by the communication structure assigned to it. You can use only certain
fields from the communication structure. SAP delivers extract structures that you can expand and change.
Extract structures are generated automatically after they are created, which generates fields that were not
there before (including units and compound characteristics). The extract structure is modelled after the
communication structure and created hierarchically. This step is unnecessary if users choose to introduce
additional fields.
2. Maintaining DataSources
You can use this function to call up general maintenance for DataSources for which you want to set which
fields can be selected or negated. For each field you can set values for Selection, Hide fields, Inversion
and field only know in customer exits. This is step is unnecessary if no additional fields have been included
in an extraction structure.
3. Activating the update
If you activate this, data will be written into the extract structures from that point on, both online and by filling
in the restructure table (see below).
2008 SAP AG 41
4. Update control
For each application it can be configured how the data is updated from the application to the central delta
management. Three possible options are available: Queued Delta, Direct Delta or Unserialized V3
Update.
Figure 2: LO-Extraction: Customizing Cockpit (transaction LBWE)
Log for Logistic Extract Structures (Tx LBWF)
You can control transfers to BW using a log. A user-related log is defined for each application, if the user
parameter MCL is set. The last posting procedure for each application is always recorded; existing log
entries are overwritten.
Recommendation
The log is only for test purposes. You should deactivate it during productive operation.
Overview about the Process of Reconstruction
Initialization must be prepared in SAP ERP (OLTP). A setup/reconstructing run fills setup tables which then
can be read during initialization (Full upload). In order to make it possible to reset if the setup process is
cancelled, its recommended to assign a name to each background processing run of the reconstructing
process. If the reconstruction process cancelled or was interrupted by archiving documents, the
reconstructing state is saved under this run name. If you then restart the process using the same name, the
system continues processing from the intermediate status that was saved. Once the run is completed
successfully, the intermediate status is deleted. Statistical setup should be run in the background because
depending on the selection criterias and depending on the amount of data the processes are very time
consuming. You can find the corresponding setup program in SAP BW customizing transaction SBIW under:
2008 SAP AG 42
Settings for Application-Specific DataSources (PI) + Logistics + Managing Transfer Information Structures +
Setup of Statistical Data + Application-Specific Setup of Statistical Data. As mentioned before for each
single application a separate transaction exists which will update the corresponding setup table. You can find
the transactions at the end of this document.
Figure 3: Statistical Setup extract structures
Deletion of Setup Tables Content (Transaction LBWG):
Since the data in the setup tables are no longer needed after initialization, you can delete the data. To be on
the safe side, you can also do this before the setup to ensure that data that has not already been setup is
available.
Deleting tables is carried out for all clients, for performance reasons (the tables will be dropped and then
recreated! )
Data Initialization in BW
Master Data
2008 SAP AG 43
It is recommended that master data is loaded first from the source system during initial supply of a SAP
BW System, before the first transaction data is loaded. This approach increases performance during initial
loading of transaction data.
Within the master data, the attributes and hierarchies should be loaded first, followed by the texts.
This sequence is merely a recommendation for supplying BW with data from the source systems initially, and
is not binding. It is also difficult to adhere to this sequence in the productive system.
Transaction Data (Without Stocks)
Differentiating between full and delta uploads is particularly important when transferring transaction data.
Performing a full upload is only useful for supplying a BW system initially or for statistical setup. Once the
BW System has been supplied with initial data, delta uploading should be used to transfer any new or
changed data to the BW System.
Stocks Initialization to SAP BW
Vari ous Scenarios
Three basi c scenarios to suit different customer requirements are described in detail here:
Scenario 1:
Your SAP ERP system went live periods ago and you want to use the SAP BW to report on some but not on
the complete set of historical data. For example your SAP ERP system contains about 2 years of historical
stock informations but as a starting point for reporting its enough to start with the last three historical
months.
For this scenario it is necessary to use all the available inventory movement DataSources 2LIS_03_BX,
2LIS_03_BF, 2LIS_03_UM and 2LIS_40_REVAL.
1. Log the ERP system for any activity
2. Empty all queues for the application 03 and 40
Therefore you have to run the collection run to empty the outbound queue for the applications inventory
controlling (03) and retailing (40) in transaction LBWE.
2008 SAP AG 44
Figure 5: Logistic Extraction Cockpit
After the step all entries in the qRFC queue should be gone. You can double-check the success using
transaction LBWQ.
Figure 6: qRFC Monitor
3. Delete all data in Delta Queue
Therefore you have two possible ways. First possibility is to start transaction RSA7 in SAP ERP and
delete existing entries for DataSources 2LIS_03_BF, 2LIS_03_UM and 2LIS_40_REVAL.
Figure 7 Delta Queue
The second alternative would be to go to the corresponding InfoPackage of each DataSource and
delete the existing Delta Init as shown in the screenshot.
2008 SAP AG 45
Figure 8 InfoPackage Deletion of the Delta Init
4. Clean Up the setup tables for application 03 and 40
To do that you have to execute transaction LBWG for application 03 and 40 to make sure that no
data is in the setup tables before you run the reconstruction.
Figure 9 Deletion of Setup tables per Application
5. Start the stock initialization process using DataSource 2LIS_03_BX and transaction MCNB
This process will now create a current stock snapshot as it is right now in the system. That means
the current stock information on the level of article, plant and storage location is stored in the
corresponding setup table. The transaction is very time consuming, therefore it is absolutely
necessary to strictly follow the performance hints mentioned in chapter of DataSource 2LIS_03_BX.
Figure 10 - Reconstruction for DataSource 2LIS_03_BX
6. Reschedule the jobs for filling the central delta management out of the qRFC and execute a Delta
Init without data transfer for DataSources 2LIS_03_BF, 2LIS_03_UM and 2LIS_40_REVAL.
2008 SAP AG 46
Figure 11 LBWE Job Schedule
At the end of this process the system is ready to handle new created transactions in a normal way as
before. You can validate the process using the transaction RSA7. For each of the DataSources a
separate green entry must exist.
Figure 12 BW Delta Queue
7. Unlog the user in SAP ERP
After finishing the step 5 it would be possible to unlog the users in the system. Important is that the
follow processes require most of the system resources looking at CP and also memory. Therefore for
response time for the unloged users will be slower than normal. Its recommended to keep the users
out of the system as long as possible.
8. Upload the initial stock information to SAP BW
Now the initial stock information based on DataSources 2LIS_03_BX must be uploaded to SAP BW.
In the Info Package you have to set the flag Generate Initial Status.
Figure 13 InfoPackage Upload the initial stock
2008 SAP AG 47
Finally when the data is correctly transferred to the cube, please compress the request with marker
update to determine and set the correct ending inventory. In the following screen the important
setting is highlighted.
Figure 14 Compression without marker Update
9. Execute the reconstruction of the history for documents for the past x months.
To fill the setup tables for DataSources 2LIS_03_BF, 2LIS_03_UM and 2LIS_40_REVAL with
historical data its necessary to schedule the specific reconstruction transactions.
DataSource Reconstruction Transacti on
2LIS_03_BF OLI1BW
2LIS_03_UM OLIZBW
2LIS_40_REVAL ORISBW
10. Full Upload of the historical stock information to SAP BW
For each DataSources the historical informations are transferred in a FULL Update InfoPackage to
SAP BW. After scheduling the uploaded to the DataTarget using a DTP the data must be finally
compressed without marker update. That means the historical data will not influence the current
ending inventory that was loaded with DataSource 2LIS_03_BX.
Figure 15 Compression with marker Update
11. Reschedule the Delta Uploads for the Inventory Movements
2008 SAP AG 48
Finally you can reschedule the daily delta upload for the DataSources 2LIS_03_BF, 2LIS_03_UM
and 2LIS_40_REVAL. Important is that these new data must be again updated with marker update.
Scenario 2:
All the material movements since the source system went live are to be transferred to the BW System.
The opening stock of the previous legacy system is posted to the R/3 System in the form of a material
document when the transfer of legacy data is posted. This allows the current stock to be calculated using the
sum of all the existing material documents (sum of all receipts and issues).
Only the material movements and revaluations must be loaded to the BW System using the InfoSources
2LIS_03_BF, 2LIS_03_UM and 2LIS_40_REVAL. The current stock is then calculated automatically by
adding all the receipts and issues. An additional stock initialization is not necessary. Important here is that
the complete history has to be compressed with marker update in the SAP BW otherwise the marker would
not get the correct ending inventory value.
This scenario should only be selected if the date on which the R/3 System went live is not too far in
the past, so that the system does not have to deal with an excessively large data volume.
It is also important when the BW System goes live to decide how far back into the past you want to look
and to select the time period to be analyzed carefully.
It would, of course, make little sense to perform setup of transaction data from the material documents for six
months ago and transfer the data to BW, if only the stocks from 2 months before the BW System went live
are to be analyzed. You should always check how many material documents were created in a particular
period.
Scenario 3:
Execute a stock initialization without uploaded any historical stock
Scenario 3 deals with the simplest situation. You dont want to use SAP BW to analyze historical stock
values that existed before the SAP BW System went live. Once the stock has been initialized (that is, once
the current stock from a source system has been transferred), all future material movements are to be
transferred.
For the scenario 3 you have to follow the same steps as described in scenario 1 excluding steps 9 and 10.
SAP BW General Remarks for Retail
As Retail customers deal with very large volumes of data, which, logically, affect the way data is stored,
administrated and evaluated, it is important to note the following points:
2008 SAP AG 49
The supplied Content, and particularly the InfoCube design, is intended only as an example, along the lines
of a Best Practice Scenario. It is important to ensure that the selected data design enables the information
required to be modeled realistically within the technical framework available.
It is important to select a data design takes into account the requirements of both the user and of the
system administrator. Thus, for example, all the stores of a particular distribution chain should be stored
in one InfoCube, and those belonging to another distribution chain should be stored in another. In POS
(storage at store/receipt number/article level), it is even recommended that a separate InfoCube is used
for each store. The data should be combined using MultiProvider technique.
Very large retailers should consider using several SAP BW Systems (one for each distribution chain, for
example) and combining the data at an aggregated level (enterprise/quarter) in a central BW System.
This is ideally supported by the fact that every InfoCube is, by definition, an InfoSource for either its own
or a different SAP BW System.
2008 SAP AG 50
2008 SAP AG 51
Tables, Transactions
Process/transacti on key:
- Activating and choosing industry MCB_
- Overview and maintenance MVB0
Extract structures:
DataSource Extract structure Setup table Setup Transaction
2LIS_02_HDR MC02M_0HDR MC02M_0HDRSETUP OLI3BW
2LIS_02_ITM MC02M_0ITM MC02M_0ITMSETUP OLI3BW
2LIS_02_SCL MC02M_0SCL MC02M_0SCLSETUP OLI3BW
2LIS_03_BF MC03BF0 MC03BF0SETUP OLI1BW
2LIS_03_BX MC03BX0 MC03BX0SETUP MCNB
2LIS_03_UM MC03UM0 MC03UMSETUP OLIZBW
2LIS_40_REVAL MC40RP0REV MC40RP0REVSETUP ORISBW
2LIS_11_VAHDR MC11VA0HDR MC11VA0HDRSETUP OLI7BW
2LIS_11_VAITM MC11VA0ITM MC11VA0ITMSETUP OLI7BW
2LIS_11_VASCL MC11VA0SCL MC11VA0SCLSETUP OLI7BW
2LIS_11_V_ITM MC11V_0ITM MC11V_0ITMSETUP OLI7BW
2LIS_11_V_SCL MC11V_0SCL MC11V_0SCLSETUP OLI7BW
2LIS_12_VCHDR MC12VC0HDR MC12VC0HDRSETUP OLI8BW
2LIS_12_VCITM MC12VC0ITM MC12VC0ITMSETUP OLI8BW
2LIS_12_VCSCL MC12VC0SCL MC12VC0SCLSETUP OLI8BW
2LIS_13_VDHDR MC13VD0HDR MC13VD0HDRSETUP OLI9BW
2LIS_13_VDITM MC13VD0ITM MC13VD0ITMSETUP OLI9BW
Task Transacti on
Customizing-Cockpit LBWE
2008 SAP AG 52
Deleting setup Tables LBWG
Extract structures log LBWF
Delta-Queue RSA7
Activating/Deactivating LIS Update MCH_
Extractor Checker RSA3
Important tables Meaning
TMCEXCFZ Extract structures, Fields Customer
TMCEXCFS Extract structures, Fields SAP
TMCEXACT Extract structures, Activating update DataSources
TMCEXEVE Extract structures, Events
2008 SAP AG 53
Related Content
Please include at least three references to SDN documents or web pages.
- 52 -
www.sdn.sap.com/irj/sdn/howtoguides
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-
98bd7c01e328Reference 2
2008 SAP AG 54
Copyright
2008 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,
zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere,
Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of
IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
J ava is a registered trademark of Sun Microsystems, Inc.
J avaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All
other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
These materials are provided as iswithout a warranty of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may
result from the use of these materials.
SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these
materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and
does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.
Any software coding and/or code lines/strings (Code) included in this documentation are only examples and are not intended to be
used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of
certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors
or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

Trade BW Logistic Extraction

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Trade BW Logistic Extraction

Uploaded by

Copyright:

Available Formats

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.

You might also like