Skip to Content

Material Movement

Hi there,

Please some one explain me what is the dependencs b/w the data sources

2lis_02_Bx

2lis_02_BF.

Thanks,

Rob

Add comment
10|10000 characters needed characters exceeded

2 Answers

  • author's profile photo
    Former Member
    Posted on Aug 19, 2007 at 05:18 PM

    Hello Rob, there are some information from help.sap.com BI Content.

    Stock Initialization for Inventory Management

    Technical name: 2LIS_03_BX

    Transaction Data (Movement Data)

    Application Component

    Materials Management (MM)

    Available as of OLTP Release

    SAP R/3 4.0B

    RemoteCube Compatibility

    No

    Prerequisites

    Activation of the DataSource.

    Use

    This structure is used to extract the stock data from MM Inventory Management for initialization to a BW system.

    Delta Update

    The DataSource only supports the update modes Full Upload and Creation of Non-Cumulatives.

    Fields of Origin in the Extraction Structure

    The fields are only filled from stock tables, and not from the tables MSEG or BSEG. This means that some of the fields listed here are never filled with data.

    -

    -


    Material Movements from Inventory Management

    Technical name: 2LIS_03_BF

    Transaction Data (Movement Data)

    Application Component

    Materials Management (MM)

    Available as of OLTP Release

    SAP R/3 4.0B

    RemoteCube Compatibility

    No

    Prerequisites

    Activation of the DataSource.

    Before you can extract data for material movements to a BW system, you must ensure that the transaction key is active.

    For this, see the following SAP Notes:

    · 353042: How-to: Activate transaction key (PROCESSKEY)

    · 315880: Missing event control after PI-A installation

    Use

    This structure is used to extract the material movement data from MM Inventory Management (MM-IM) consistently to a BW system.

    Delta Update

    A Delta update is supported. Delta procedure: ABR1 – Complete Delta with deletion flag using Delta queue (RemoteCube compatible) with serialization on request.

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Aug 20, 2007 at 12:15 PM

    hai,

    2lis_03_bxMaterial Stock(Tcode in R/3 is MCNB).

    This is used to extract an opening stock balance on a detailed level(material, plant, storage location and so on).At this moment , the opening stock is the operative stock in the source system.” At this moment” is the point in time at which the statistical setup ran for Datasource 2lis_03_bx. (this is bcoz no documents are to be posted during this run). It is not possible to choose a key date freely.

    2lis_03_bfMaterial Movements

    This Datasource is used to extract the material movements into the BW system. This DS provides the data as material documents (MCMSEG Structure).

    2lis_03_umRevaluations

    This Datasource contains data from valuated revaluations in Finanacial Accounting( document BSEG). This data is required to update valuated stock changes for the calculated stock balance in the BW.

    NO Marker Update

    This no marker update concept arrises if the cube contains a non -cuumulative key figures. say for example take the material movements cube where stock quantity is a non-cummualtive key figure. there the process of laoding the data into the cube involves in two steps.

    in the first step one should load the records pertaining to the opening stock balance/or the stock present at the time of implementation. at this time we will make marker to update( uncheck no marker update) so that the value of current stock quantity is stored in the marker. After that when we r loading the historical movements (stock movements made previous to the time of implementing the cube). at this time we have to check marker update so that the marker should not be updated ( bcs of these historical movemtns only the stock balance /opening stock quantity has been updated. i.e we have already loaded the present stock and the aggreagation of previous/historical data accumulates to the present data).

    Second after every successful delta loads, we should not check maker update ( we should allow to update marker) so that the chances in the stock quantity should be updated in the marker value.The marker will be updated to those records which are compressed.The marker will not be updated to those uncompressed requests. thats why for every delta load requests the requests should be compressed.

    This marker is mainly used to fetch the records value for reporting. it helps easily to get the values of previous stock qunatities while reporting.

    Update ur mail id i'll frwd dco reg this.

    Asign points if helpfull

    regards

    KP

    Add comment
    10|10000 characters needed characters exceeded