ODS Capability of 2LIS_02_SCL

All,
I am having an issue with the 2LIS_02_SCL (Purchasing Schedule lines extractor) that I just cannot figure out.
Here is the situation....
I have created an ODS layer in front of a set of data targets...one data target is a cube that is modeled from the 0PUR_C01/04 design, with some enhancements, and the other is the 0PUR_DS03 with some enhancements.
Now, my ODS layer is set up like this...
2LIS_02_SCL enters first into PSA...like normal.
Then the data from the PSA is loaded into a set of ODS objects I have created. Basically, each ODS is exactly the same, with the only difference being the start routines.
In each start routine, I delete all records I do not want. For instance, I have ODS objects for the process keys...(PO's are stored seperate than GR's, same for IR's)
So, 2LIS_02_SCL goes into "N" number of ODS objects, that look the same, just each one keeps only subsets of data.
POs/Scheduling agreements
Goods REceipts
Invoice Receipts
Returns..
etc...
The main three I am concerned with are the first Three..PO's, GR's and IR's.
The start routines only keep the proper process keys. For instance:
PO's ODS:
DELETE DATA_PACKAGE WHERE PROCESSKEY NE '001' AND
                          PROCESSKEY NE '011' AND
                          PROCESSKEY NE '021' AND
                          PROCESSKEY NE '004' AND
                          PROCESSKEY NE '014' AND
                          PROCESSKEY NE '024'.  
GR's ODS:
DELETE DATA_PACKAGE WHERE PROCESSKEY NE '002' AND
                          PROCESSKEY NE '012' AND
                          PROCESSKEY NE '022'.   
IR's ODS:
DELETE DATA_PACKAGE WHERE PROCESSKEY NE '003' AND
                          PROCESSKEY NE '023'.  
etc...
Now, I have mapped everything correctly. (STORNO is mapped to 0RECORDMODE.)
The key of all ODS objects is the PO number, Item and Schedule line.
Note:
Now, originally, I had thought to keep all process key types in one ODS, and to do that, I would have just needed to add another key of PROCESSKEY to the ODS. But, I wanted the flexibility to possibility to be flexible with having to process the same data over and over. Just some reasoning why I don't use just one ODS....
Now, what I am seeing is incorrect GR and IR quantities.
My Schedule line values (Scheduled Quantities) are completely correct!  But in the ODS layer I am seeing GR and IR values that don't completely match up.
Now, I understand certain conditions in R/3 make schedule lines behave interestingly. For instance, over deliveries, or under deliveries are allocated to the first open Schedule line. Meaning, if I have an open schedule line of 100 PC and I get a GR of 150 PC, then 100 PC is allocated to the 100 PC schedule line and 50 PC is allocated to the next open schedule line. But for some reason I am not getting the correct values. But SAP handles that and on the delta's allocates occordingly, and in my ODS objects, I just overright.
So, if today, I have this situation:
PO___ITEM__LINE___SCDQTY____RECQTY
123___10_____14______50_______25
123___10_____15______100_______0
123___10_____16______200_______0
123___10_____17______200_______0
Then tomorrow, I receive 150 PC:
PO___ITEM__LINE___SCDQTY____RECQTY
123___10_____14______50_______50
123___10_____15______100______100
123___10_____16______200_______25
123___10_____17______200_______0
*then this is what I should see....but sometimes I do not!
Now, I am certain I have mapped the data correctly from the ODS layer to the cube layer. For instance, for one process key type, a Key Figure value means one thing, and for another, that same key figure, may mean something else. For instance, CPQUAOU is both a GR qty and and IR qty, given the right Process key is determined.
Also, is there a limit on the LBWQ entries? I remember hearing something about 300,000 entries in the queue before you may lose data?
Also, is there a transaction I can look at in R/3 to see if any LBWQ (SMQ1) entries have been deleted? I used to remember this, but forgot it a while back...
I think the ODS design is correct. So, it points me back to R/3. But I want to make sure I don't have any flaws before I resort to trying to figure out what the functional teams have done on the R/3 side.
I have also investgated the PSA and it appears that on the PO Process key type (4), I have a schedule line that has both the same GR and PO qty. But in the GR ODS, I don't have teh GR...which makes we wonder what in the world SAP is doing with that schedule line?
So, I am wondering if any of you gurus have come across this and how you corrected the issue(s).
Thanks in advance!
Cheers!
Steve

Stev, Am strongly suspecting on Schedule line (Infoobject)as it is been defined as a key field, per my knowledge if the schedule lines are differ then you wont get the reference values..
Why dont you remove schedule line IO for once and upload the data.
Hope you get some clues...

Similar Messages

  • How to add a new field in target ODS that is not available in source ODS ?

    Hello every one , this is the first time i am placing a question
    - Currently we have an existing ODS based on 2LIS_02_SCL data source. This ODS is already in production.
    We have a requirement to use this existing ODS as our source to load required data in to two different data targets which also are ODS.Their update rules are different.
    Problem: There is  now a requirement to include a new field (PO need date) in the two target ODS. As this field in not available in our source ODS . How do we go about adding this.
    concern: As the source ODS is already in Production, How do we go about loading data if this new field is added.
    Anticipating your co operation.

    The new field is 0SCL_DELDATE  (planned delivery date of document schedule line)
    It is already there in the comm structure of our source ODS. But as it was not needed earlier in the source ODS, it was not used/added.(i.e not there is the source ODS update rules)
    But now as we are basing our targets on this source ODS.
    How do i go about doing this.
    The main idea of doing it this way is because we do not want to reload data from R/3.

  • Inventory Management ODS

    Hi
    What precautions to be taken before loading BF data into the ODS. Do we have any standard ods available in the business content.
    My requirement is i have a report which is developed in ABAP but due to performance now they want that report to be developed in BI.
    The data is comeing from AFPO, AFRU, MSEG, MKPF, VBAP.
    In MKPF they want only posting date and from MSEG only movement types but not any goods issue qty or recepit qty like that.
    REgards
    Annie

    Hi
    The DataSource 2LIS_03_BX 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.
    The DataSource 2LIS_03_BF is used to extract the material movements into the BW system. This DataSource provides the data as material documents in the MCMSEG structure.
    1.   Initialization of the current stock (opening balance) in the R/3 source system (transaction code in R/3: MCNB).
    2.   Setup of statistical data for material documents in the R/3 source system.
    3.   Loading the opening stock balance (InfoSource 2LIS_03_BX) into InfoCube 0IC_C03. In the InfoPackage, choose the upload mode “Create opening balance”.
    4.   Compressing the request containing the opening stock that was just uploaded. Make sure the "No marker update" indicator is not set.
    5.   Loading the historical movements into the InfoCube 0IC_C03 via the DataSource/InfoSource 2LIS_03_BF. Choose the upload mode "Initializing the delta process" here.
    6.   After successfully uploading the historical material movements, the associated request has to be compressed. You must make sure the "No marker update" indicator is set.
    7.   Schedule the V3 update for 03 area.
    8.   Delta uploads can be started with the DataSource 2LIS_03_BF from this point in time on.
    As of 3.0B, SAP delivers InfoCube 0IC_C03 for reporting on R/3 inventory data in BW. This gets updated from the InfoSources 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM.
    Please go through the following links:
    http://help.sap.com/saphelp_nw04/helpdata/en/fb/64073c52619459e10000000a114084/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    InfoCube: 0IC_C03
    ODS Capability
    For the ODS capability of this extractor, see the SAP Note 581778: ODS capability of extractors from Inventory Management.
    Cheers
    Pagudala

  • How to load delta to 2 target ODS 's from a single ODS using process chains

    Hi BW Gurus
    I am having a current ODS based on 2LIS_02_SCL, deltas also are working fine for it.
    our  requirement was based to have 2 target ODS on this existing ODS by using export generate datasource.
    I have to build a process chain that should enable us to load delta in our target ODS.
    Earlier manually for DEV purposes ,i was using the Update data into data targets from the source ODS, this was enabling us to load deltas. But to automate this process we will require a process chain.
    Finally , is there any process type in process chain for " Export generate Datasource".
    please suggest a good methodology for this scenario.
    Thanks in advance.

    Hi Ashfaq,
       Loading from ODS to CUBE is same as loading from datasource to ODS only.
    1. Create export datasource.
    2. Create update rules from ODS(export datasouce) to CUBE.
    3. Create infopackages(if you dont want to use generated once).
    4. include infopackage in process chain to load fromODS to CUBE.
        Intialize first manually and change settings in process chain infopackage to "Delta".
    5. You can append/enhance existing process chain(loading from datasource to ODS).
    Hope it Helps
    Srini

  • LO cockpit help

    hi
    I have deleted the data from Cube and PSA and Info package for an LO cockpit data source to make a fresh load in to BI (in sandbox)...Now I went to LBWG and deleted set up tables...and then filled the set up tables again...now when I load the init by running the infopackage its giving only 54 records...can any one tell me where am making the mistake ? Did I forget any step in ECC ?
    Please advice...Just tell me how to reload the init ...FYI I have deleted the data from PSA and Info package scheduler as well....I need to load from ECC again
    Regards

    Check the base tables itself first to confirm the number of entries match,also after deleting the set up tables check in RSA3 to see if its completely deleted..
    More insights
    LOCOCKPIT
    Steps
    1)LBWG - Delete Set-up tables
    2)LBWE -->Application area(Purchasing)
    Activation of extract structures
    Click >Structure>Maintenance
    Click>Datasource>2LIS_02_HDR
    Click>Update>Active
    Click>Update Mode>Queued Delta
    Green light should appear on each extraction structures after all STEPS
    3)SBIW settings-based on Application area
    Inventory Controlling
    IMPORTANT - ORDER OF LOADING
    ALWAYS LOAD in order as BX datasource first then BF datasource and then UM datasource in cube
    a)SBIW>Setings for Application -specific Datasources(PI)>Logistics-->Settings:Inventory Controlling -->
    Select Determine Industry sector
    Select Transaction Key Maintenance for SAP
    Transaction key is used for Process key mappings w/t these the data would not load in to BW though it would come in PSA
    b)Select Stock Initialization or TCODE - MCNB
    Purchasing
    a)SBIW>Setings for Application -specific Datasources(PI)>Logistics-->Settings:Purchasing
    Select Determine Industry sector
    Select Transaction Key Maintenance for SAP
    4)Fill Set up tables
    SBIW>Setings for Application -specific Datasources(PI)>Logistics>Managing extract structures>Initialization>Filling in the set up table>Application specific setup of statistical data.
    OR
    OLI*BW -example for Inventory transaction is OLI1BW
    5)BW -Replicate datasources
    Loading data steps-
    1)LBWQ (Empty the queue by deleting the entries if its FRESH installation or Execute Job through Job control and empty the queue)
    2)LBWG (Delete set up tables)
    3)SBIW(OLI*BW) Fill set up tables ,use BLOCK check box
    4)Make an INIT from BW  (Data now flows from LBWQ to RSA7)
    5)Set up a V3 update job in R/3 ,frequency daily/periodic
    Inventory Cube -
    1)Load BX datasource
    2)Load BF datasource (No checkmark on Marker update)
    3)BW - Compress cube with YES Checkmark Marker update
    4)Remove Check Mark
    5)Delta
    6)BW - Compress cube with YES Checkmark Marker update
    IMPORTANT -
    Note 691721 - Restoring lost data from a delta request
    Note 581778 - ODS capability of extractors from Inventory Management
    MB51 transaction to check the report
    LBWE - Lo Cockpit
    0info_rec is not included in 2LIS_02_ITM or 2LIS_02_SCL (urgent)
    Note 396647 - FAQ: V3 update: Questions and answers
    SM13 usage Note 328181 - Changes to extract structures in Customizing Cockpit
    Note 602260 - Procedure for reconstructing data for BW
    Update methods - V1 ,V2,V3
    Gist of LO Cockpit Delta
    Hope it Helps
    Chetan
    @CP..

  • Records not showing in Report

    Hi All,
    I'am facing peculair issue, We have an issue where inventory is showing in -ve.
    From 2LIS_03_BF we are loading the data to DSO, from DSO again to Cube.
    I can see Reocrds in Cube for a certian Plant , Storage Location and Material combinations....when I gave same selection criteria in Report the records are not shown in Report. I have checked Query designer too if there are any condition applies but there are no conditions as such expet Special Process Indicator K is excluded.
    so i checked Special process indicator for that material but its not K.......its Blank.
    Inorder to recover the issue, I have selectivdely deleted the material, Plant and Storage location combination and reloaded the data to cube and compreessed the request without checking No marker Update.
    Please need inputs here.
    SujanR

    Hi,
    Use 2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM to 0IC_C03 Cube and design the report.
    Use :See the steps how to load the data to 0IC_C03.
    Treatment of historical full loads with Inventory cube
    Setting up material movement/inventory with limit locking time
    See some importent SAP Notes in Invventory Lods.
    Note 747037 - Update of before images in ODS objects
    Note 752492 - Non cumulative keyfigures are incorrectly allowed in ODS
    Note 581778 - ODS capability of extractors from inventory management
    Note 684465 - BWVORG for purchasing data sources
    Note 417703 - Missing duplicate record during extraction with 2LIS_03_BF
    Note 929378 - 2LIS_03_BF, 2LIS_03_BX, 2LIS_03_UM and BI 2004s
    Note 745788 - Non-cumulative mgmnt in BW  Verifying and correcting data
    Note 352762 - Collective note purchasing extractors and setup
    Note 353042 - Howto Activate transaction key (PROCESSKEY)
    Note 352344 - Process key + reversals in Inventory Management
    Note 586163 - Composite Note on SAP R3 Inventory Management in SAP BW
    Thanks
    Surendra Kumar Reddy Koduru

  • Inventory Management with u0091Material Document No.u0092 and u0091Purchase order No.'

    Hello,
    We have defined Inventory Management InfoCube analog to 0IC_C03 without ‘Material Document No.’ (R3 Field MBLNR) and ‘Purchase order number’ (R3 Field EBELN). We are loading the data from standard extractor 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM. It works fine. We have alreday read the whitepaper “Inventory Scenarios in BW”.
    Question:
    Now the ‘Material Document No.’ and ‘Purchase order number’ have to report in BEx. As ODS can not be built in Inventory Management, so we can’t include these fields in ODS and update data from ODS into another InfoCube with Document No. or order number.
    We don’t want to include these fields Document No. and Order number. in existing InfoCube because of performance reason.
    Could you tell me how we can implement such a scenario?
    Thanks for the answer.
    Best regards,
    Moha

    hi Moha,
    perhaps check
    Note 581778 - ODS capability of extractors from Inventory Management
    Note 773823 - P25:ODS objects cannot be loaded with opening stock
    hope this helps.

  • Inventory Management with u0091Material Document No.u0092 and u0091Purchase order No.u0092

    Hello,
    We have defined Inventory Management InfoCube analog to 0IC_C03 without ‘Material Document No.’ (R3 Field MBLNR) and ‘Purchase order number’ (R3 Field EBELN). We are loading the data from standard extractor 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM. It works fine. We have alreday read the whitepaper “Inventory Scenarios in BW”.
    Question:
    Now the ‘Material Document No.’ and ‘Purchase order number’ have to report in BEx. As ODS can not be built in Inventory Management, so we can’t include these fields in ODS and update data from ODS into another InfoCube with Document No. or order number.
    We don’t want to include these fields Document No. and Order number. in existing InfoCube because of performance reason.
    Could you tell me how we can implement such a scenario?
    Thanks for the answer.
    Best regards,
    Moha

    hi Moha,
    perhaps check
    Note 581778 - ODS capability of extractors from Inventory Management
    Note 773823 - P25:ODS objects cannot be loaded with opening stock
    hope this helps.

  • Noncumulative Cube Copy for Inventory IC where compression is not possible

    Dear All
    We have got Month (0RT_C37) and Week (0RT_C36) Inventory Infocubes. Compression has never been done on any of this cube. The data is fine and result is coming correct but output is very slow. We have done the initialization on this cube on mid of 2008. We have to copy the entire cube to a ZCube and do the compression performed on that Zcube. Our system is BW7.3 SP Level11 and we are going to upgrade to 7.4 .  We tried to move the marker values(RECORDTP=1) to the Zcube with DTP setting (Initial Non-cumulative for Non-cumulative values) which is not happening. But other values with movements we are able to move. The only OSS note found to address this issue is1426533 which is not relevant for us. Is there any workaround for the situation where no compression is ever happened on the cube and the compression is impossible due to some issues, hence we want to copy the entire data to another Zcube and perform the compression there.
    Regards
    Reshoi

    Hi Reshoi,
    There is no DSO for 2LIS_03_BF in Business Content as far as I know. It is possible to create a DSO yourself. Please review SAP Note 581778 - ODS capability of extractors from inventory management and the related SAP Notes carefully if you want to go into this direction.
    Please have a look at the document Re-initialization of the Material Stocks/Movements cube (0IC_C03) with 2LIS_03_BF, 2LIS_03_BX and 2LIS_03_UM in BW 7.x for contains a step-by-step instruction and lots of valuable information.
    Re. the downtime, there are ways to minimize it. Please see SAP Note 753654 - How can downtime be reduced for setup table update. You can dramatically reduce the downtime to distinguish between closed and open periods. The closed periods can be updated retrospectively.
    Please refer to document How to Handle Inventory Management Scenarios in BW (NW2004) for an evaluation of different Inventory Management scenarios.
    I also would like to recommend you to review SAP Note 419490 - Non-cumulatives: poor query performance for 5 performance tips.
    Last but not least, you might want to have a look at the following SAP Notes:
    SAP Note 436393 - Performance improvement for filling the setup tables;
    SAP Note 602260 - Procedure for reconstructing data for BW.
    Best regards,
    Sander

  • Inventory Management DSO Capabilities

    Hi All,
    In a typical inventory management scenario (for 0IC_C03), we have inventory datasources (BF, BX and UM) directly feeding the cube.
    Due to system architecture we now have to place data coming from these datasources into a DSO first and then feed the inventory cube.
    Please guide me as to what should be the key combination for the DSOu2019s of these datasources (i.e. for BX, BF and UM) .
    Regards
    Anshul

    Hey!
    Search in OSS for the following note:
    Note 581778 - ODS capability of extractors from Inventory Management
    This will help you for this what you need to know.
    I think for BX is a DSO not necessary because you use it just for the initial load.
    Best regards,
    Peter

  • Please explain about the RODELTAM table

    Hi,
    I am going thru the RODELTAM table. I understand that this table is used to check my delta type.
    I had clicked on contents button and then on the execute button. Now the screen that appears has a table with few columns and there is the text log column in the end. I don't understand how to read this table and some terms mentioned in this table.
    The first column is DELTA and underneath this column, there are few abbrevations such as ABR, A, ADD, AID, AIED, AIM AIMD D, E NEWD, NEWE, O, and X. Can someone please expand each of these terms, and explain what does each of these terms mean?
    The columns that are shown are:
    1. DELTA:
    2. ONLYFULL,
    3. UPDM_NIM
    4. UPDM_BIM
    5. UPDM_AIM
    6. UPDM_ADD
    7. UPDM_DEL
    8. UPDM_RIM
    9. DREQSER
    10. DELATYPE
    11. TXTLG
    Also please expalin me the purpose of each of the above mentioned columns.
    Thank you.
    TR.

    Hi,
    RODELTAM table contains the details abt DELTA PROCESS like
    ABR, A, ADD, AID, AIED, AIM  ets
    Delta only with Full Upload (ODS or InfoPackage Selection)
    A ALE Update Pointer (Master Data)
    ABR Complete Delta wth Deletion ID Using Delta Queue (Cube-Cap.)
    ABR1 As 'ABR' Procedure, but Serializatn only Request by Request
    ADD Additive Extraction Using Extractor (e.g.LIS-InfoStructures)
    ADDD As 'ADD' but via Delta Queue (Cube Enabled)
    AIE After Images Using Extractor (FI-GL/AP/AR)
    AIED After-Images with Delete Indicatr via Extractr (FI-GL/AP/AR)
    AIM After Images Using Delta Queue (e.g. FI-AP/AR)
    AIMD After Images wth Deletion ID Using Delta Queue (e.g. BtB)
    CUBE InfoCube Extraction
    D Unspecific Delta Using Delta Queue (Not ODS-Capable)
    E Unspecific Delta Using Extractor (Not ODS-capable)
    FIL0 Delta Using File Import with After Images
    FIL1 Delta Using File Import with Delta Images
    NEWD Only New Records (Inserts) via Delta Queue (Cube Enabled)
    NEWE Only New Records (Inserts) via Extractor (Cube Enabled)
    O
    ODS ODS Extraction
    X Delta Unspecified (Do Not Use!)
    check RODELTAMT BW Delta Process (Text)  table also for more details and also
    check this link
    http://help.sap.com/saphelp_nw04s/helpdata/en/84/81eb588fc211d4b2c90050da4c74dc/frameset.htm
    Hope this helps
    Anand Raj

  • Business Content Inventory Management (0IC_C03) Cube

    I am thinking of adding a data staging ODS to our Inventory Management model.  However, I wanted to check whether the delivered cube 0IC_C03 is aggregated or whether it is a representation of the R3 extraction.  If the latter is the case I do not see the purpose of an additional ODS layer.  Could anyone pass their thoughts? Thanks

    hi Niten,
    check oss note 581778-ODS capability of extractors from Inventory Management
    Symptom
    Data is not updated into the ODS when you load certain data records of the 2LIS_03_BF extractor.
    Other terms
    ODS, 2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 0STORNO, ROCANCEL, RODMUPDMOD, 0RECORDMODE, Inventory Management, 0IC_C03,
    Application 03, Logistics Extraction Cockpit, LBIW
    Reason and Prerequisites
    The 2LIS_03_BF extractor does not return any "connected" after and before images, as in the SD extraction, for example.
    Originally, the extractor was only designed for updating into an InfoCube. The extraction method was converted from the "D" delta process to "ABR1" with PI 2000.1 patch 4, or PI-A 2000.1 patch 4 so that it could be updated into an ODS object (see notes 322303, 385703 and 323811).
    If documents are canceled in Inventory Management, a new document is generated (new document and item number).
    This type of operation is transferred into BW with the "ROCANCEL" field set to 'X'. This results in the necessary inversion of quantities or value key figures. A new record is generated for this in the ODS (the "preceding document" has another key).
    Example:
    ODS key: Doc.
    Movement data:
    Document   Item    Document year   Movement type     Qty     ROCANCEL
    4711       1       2002             101              +100
    4712       1       2002              102              -100     X
    ODS contents:
    Document   Item.   Document year   Movement type    Quantity
    4711       1       2002             101                 +100
    4712       1       2002                                   -100
    The "Movement type" field was set to "initial" in the data record for document "4712" by the processing during the ODS update.
    Document 4712 is a before image (0RECORDMODE = 'X') for the ODS. Therefore, this data does not arrive in the ODS. Nevertheless, the before image (document 4712) does not have any context with the after image (document 4711) because there are different keys (document/item/document year). The SAP R/3 inventory management controls these activities with new material documents and (reversal) movement types.
    BW technology note no. 747037 provides more information.
    Solution
    You have two options to evaluate cancellations or operations which contain reversal movement types and ROCANCEL = "X" in the ODS:
    1. Implement a start routine
    Insert the following code into the start routine of your update:
    ODS key: Material doc.|Item number|Calendar year
    BEGIN******************************
    LOOP AT DATA_PACKAGE.
      if DATA_PACKAGE-recordmode eq 'X'.
        DATA_PACKAGE-recordmode = ''.
        modify DATA_PACKAGE.
      endif.
    endloop.
    END********************************
    2. Change the transfer rules
    With the transfer rules, do not assign the "ROCANCEL" DataSource field to the "0RECORDMODE" InfoObject in the InfoSource. As a result, only records with "0RECORDMODE" = ' ' are transferred to the ODS. For the ODS, the after images whose characteristics or key figures that are set to overwrite, are not deleted.
    Other special features when updating the extractors of the inventory management into ODS objects:
    1. 2LIS_03_BF and 2LIS_03_UM
    a) ODS capability
    For more information, see notes 322303, 323811 and 385703.
    b) Key creation
    For 2LIS_03_BF, see note 417703.
    The following keys are available for 2LIS_03_UM:
    1. MCMSEG-BUKRS
    2. MCMSEG-BELNR
    3. MCMSEG-GJAHR
    4. MCMSEG-BUZEI
    Field no. 4 is not delivered as standard in the extract structure, but it can be added using the Logistics extract structures Customizing Cockpit.
    Field no. 1 may not be included in the relevant organizational structure.
    2. 2LIS_03_BX (up to and including 3.0B 2LIS_40_S278)
    The dynamic stock calculation from stocks (2LIS_03_BX) and movements (2LIS_03_BF) is only possible with (non-cumulative) InfoCubes.
    Using ODS technology is only useful in this context for:
    - an Enterprise DataWarehouse layer
    - the realization of a snapshot scenario:
    See the How to paper for this topic at:
    -> http://service.sap.com/bw
    -> left navigation area: SAP BW InfoIndex
    -> info index: N ("Non-cumulatives") ->
    "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
    Use note 773823 to update the 2LIS_03_BX InfoSource into an ODS.
    Note also that you cannot update any key figures into an ODS object (see notes 752492 and 782314).

  • How to modify the Generic Delta in Standard Data Source...?

    Hi BW Guru's,
    We have one issue like all values are coming from customer master data data source 0CUST_COMPC_ATTR which is delta capable. Recently the functional guys done some modification on customer by remapping the field to sales rep. this will be impact on collector field (this is generic field - ZZ field). Now there will be frequent changes for collector field and the delta is not able to pick up the changed values in to BW system. 
    I have tried in different ways but not resolved finally i got some clue which as follows:
    Data source 0CUST_COMPC_ATTR shows delta process as 'E' Unspecific Delta
    Using Extractor (Not ODS-capable) in RSA2.
    Now i would like to change the option to delta process to ‘D’ unspecified delta using delta queue (not ODS-capable).
    Can any one give advice me on this.  Your help will be appreciated.
    Thanks in Advance,
    Venkat

    Hi Olivier,
    Thanks for quick response.
    I am sorry for not mentioning the module on which i am working.
    I am working on FI-CO extraction.  I heard that In FI-CO the delta queue does not support because it won't support V3 Delta mechanism.
    But any how i will try with ROOSOURCE and let you know the status of it.
    If any advices please revert back with suitable suggestions.
    Thanks and Regards,
    Venkat

  • How does delta know the value of keyfigures to substract?

    Hi
    I was wondering... I have a delta load to a ODS. The delta would go like this:
    doc nr.     item nr.     qty
    111111    0000010     15
    111111    0000010     -15
    111111    0000010     19
    But how does the delta know that it has to subtract 15 before it adds 19? Is it just looking in the ODS for a record with the same primary key? In that case, how does it then know what to subtract when it is an infocube that is the target?
    Thanks in advance.
    Kind regards,
    Torben

    Hi Torben,
    Delta Process is the Property of the Datasource as mentioned by Tripple K.
    You can go to table ROOSOURCE in OLTP (R/3) sytem and check the property of the Datasource for which you are extracting the data.
    And also you can see table RODELTAM to see details about a particular Delta Process Type.
    RODELTAM table contains the details abt DELTA PROCESS like
    ABR, A, ADD, AID, AIED, AIM ets
    Delta only with Full Upload (ODS or InfoPackage Selection)
    A ALE Update Pointer (Master Data)
    ABR Complete Delta wth Deletion ID Using Delta Queue (Cube-Cap.)
    ABR1 As 'ABR' Procedure, but Serializatn only Request by Request
    ADD Additive Extraction Using Extractor (e.g.LIS-InfoStructures)
    ADDD As 'ADD' but via Delta Queue (Cube Enabled)
    AIE After Images Using Extractor (FI-GL/AP/AR)
    AIED After-Images with Delete Indicatr via Extractr (FI-GL/AP/AR)
    AIM After Images Using Delta Queue (e.g. FI-AP/AR)
    AIMD After Images wth Deletion ID Using Delta Queue (e.g. BtB)
    CUBE InfoCube Extraction
    D Unspecific Delta Using Delta Queue (Not ODS-Capable)
    E Unspecific Delta Using Extractor (Not ODS-capable)
    FIL0 Delta Using File Import with After Images
    FIL1 Delta Using File Import with Delta Images
    NEWD Only New Records (Inserts) via Delta Queue (Cube Enabled)
    NEWE Only New Records (Inserts) via Extractor (Cube Enabled)
    O
    ODS ODS Extraction
    X Delta Unspecified (Do Not Use!)
    The Datasource contains a field called ROCANCEL which is mapped to 0RECORDMODE in BW(if ODS is present in BW Data Flow). The Role of this field is to indicate the Cancellation of data record , similarly the field 0RECORDMODE determines whether the records are added to or overwritten. It determines how a record is updated in the delta process: A blank character signifies an after image, ‘X’ a before image, ‘D’ deletes the record and ‘R’ means a reverse image.
    By mapping ROCANCEL to 0RECORDMODE the data extraction and concept of delta is realised in BW.
    So while modelling the Data Flow in BW and Delta mechanism in BW the Datasource property (ROOSOURCE and RODELTAM) plays a vital role in Modelling.
    Basically this ROCANCEL Field will have values like "blank" - after image, and "X" - before image and if you check in RSA7 for the records extracted in your last delta run you will find multiple records for same key fields, as there are multiple images (After, Before, Reverse etc) depending on Delta Process of Datasource.
    Hope this clears.
    Please let us know if you have further queries.
    Thanks!
    CK

  • Extraction shipment cost 2lis_08trfkz

    Hi,
    I have a problem with shipment cost. A shipment cost is assigned to a transport.
    Datas are updated to BI system. When I delete a shipment cost in order to create an other one and assign it to the same transport, BI system detects changes, but it create 2 register with the same transport number but different shipment cost. I need a DSO to store data, but the KEY FIELD must be transport numer, shipment cost and shipment cost item. Then tha data are update into a cube.
    Is there into SAP R/3 a field when I can store deleted shipment costs? The used table is VFKP, but there is no place where I can store deleted shipment cost. Do you know how I can solve this problem?
    Thank you very much

    Hi pcamp :
       The solution for you is to add to your DSO the Reversal Indicator (InfoObject 0STORNO), this way you can identify the deleted Shipments/Shipment Cost documents when the 0STORNO = 'R'. If the 0STORNO = '' then the document exists in the ERP.
    You could either make 0STORNO part of the Data Fields or Key Fields of you DSO, depending on your particular needs (overwrite or preserve existing records).
    Hi Ramesh:
       As you mentioned before, the SAP Note 440166 explains that there is ODS Capability for Shipment and Shipment Costs DataSources.
    Depending on the Support Package of your SAP System you may need to apply the corrections, according to the follwoing SAP Note: 440416 - BW OLTP: Correction report for change of delta process.
    Regards.

Maybe you are looking for