ABR delta

Hi Experts,
I am using 2LIS_02_ITM. It uses ABR images for 0recordmode.
I found in psa for a certain PO, the image is Blank which means After image.There is no other images.
I like to clarify what does this mean.
Does it mean that this is a new record and no change was ever applied to the time of delta queue entry creation and subsequent load in BI?
Or does this mean its a CHANGED record where AFTER IMAGE indicates a change and after image could not have come from a new record which should be indicated by recordmode N?
Please help confirm for me this understanding.
best regards
Pascal

Hi ,
Just to correct my previous post i said :'So in your case if you are seeing only blank in 0recordmode and there is no other images , that means its a new record .' It should be actually 'So in your case if you are seeing only blank in ROCANCEL field in datasource and there is no other images , that means its a new record .'
See , in standard extractors we have a field called as ROCANCEL which is mapped to your 0recordmode in BI side .
So if a new record is coming from ECC i.e in this case a 0recordmode will be N.
If an existing record is changed then 0recordmode will have value 'X' signalling that its a previous image and blank meaning that it is an after image.
In case of DSOs only after image goes to the active table and in change log you can find the two entries .
If its a cube directly , both before and after images will be sent with previous image as negative value .
Hope the above reply was helpful.
Kind Regards,
Ashutosh Singh

Similar Messages

ABR delta extractor and entries written to the delta queue

Hello Everyone,
We have an ABR extractor and it's behaving like this:
For example fields: PM Order Number, Post Goods Issue Date, Start Date, Work Qty, Projected Qty
Create the PM order the entry is written perfect to the delta queue:
10019987, blank, 04/29/2009, 100 PC, 90 PC
Now, if we perform a confirmation on the PM order we see the following:
10019987, 04/29/2009, blank, 0 PC, 90 PC
Now if we change something on the PM order header we see the following:
10019987, blank, blank, 100 PC, 0 PC
When this comes over to BW we don't get good results in our ODS.
Basically we don't get our Post Goods Issue date and Work Qty gets blanked out. Basically, the last change to the order gets written to the ODS and isn't correct.
Shouldn't it do the following:
10019987, blank, 100 PC, 90 PC
10019987, 04/29/2009, 100 PC, 90 PC
10019987, 04/29/2009, 100 PC, 90 PC
10019987, 04/29/2009, 04/29/2009, 100 PC, 90 PC------this gets sent as last record with all fields updated. We choose all these fields in the extract structure.
Thanks

Hello Martin,
Below is a snapshot of the delta queue (you can see the Cancel). Question: How do you control what record is updated and what others are not? We thought the cancel won't update and the others will in order they were updated to the delta queue (and that appears how it's behaving):
Scenerio #1 (sorry, can't remember sequence of steps done in system, but thought I'd mention)
Cancel, Order Number, Release Date, Posting Date, Material, Plan Qty, Confirmed Qty
blank, 10019987, 04/29/2009, blank,       , 4415, 100, 0
blank, 10019987, 04/29/2009, 04/30/2009, 4415, 0,    100
blank, 10019987, 04/29/2009, blank,         4415, 100, 100
X,       10019987, 04/29/2009, blank,         4415, 100, 100
Scenerio #2
cancel, order, release date, posting date, material, plan qty, confirm qty
blank, 100019989, 04/29/2009, blank, 4415, 50, 0
then we perform a confirmation for 50 pieces and this is how the delta queue looks like
cancel, order, release date, posting date, material, plan qty, confirm qty
blank, 100019989, 04/29/2009, blank, 4415, 50, 0
blank, 100019989, 04/29/2009, 04/30/2009, 4415, 0, 50 <----
second line
Notice the second line now has plan qty at 0 and confirm at 50. Plan should always show 50 (or whatever the plan amount is. Something doesn't seem correct here??
Now, if we change something on the order header, we get the correct plan qty of 50 (and confirmed still 50), but then the posting date is blank. So when this comes over to BW we get correct plan and confirmed qty, but posting date is blank. This really makes no sense because if you have confirmed qty populated with a quantity then you have a posting date.
Thanks!

ABR complete delta with deletion flag via delta queue (cube compartible)

Hello
DS 2LIS_04_P_COMP is delta enabled with ABR complete delta with deletion flag via delta queue (cube compartible)
Is it possible to use this type of delta for ods? If yes , what kind of changes are required
Thanks

Hi
ABR means
A - After Image
B - Before Image
R - Reverse Image
Since updating DSO is usually in overwrite mode it requires After Image.
So u can use the data source with ABR delta to load into DSO (ODS).
Cheers.

How to handle the deleted PO in BW?

Hello All,
We are facing the following critical problem and need your support if any one of you is experienced before.
1. BW system still gets through the data even the PO document is already deleted in R/3 side!
2. The used data flow is as follows:
    DS: 2LIS_02_ITM => ODS without any intermediate data target and report is built on ODS. BW report is shown with negative
    values for the deleted PO documents which are not at all acceptable.
3. There is no field u2018LOKEZu2019 used in the existing data source (2LIS_02_ITM). Would my problem will be solved if I use LOKEZ
    field.
4. If point 3 is correct, then what would be the procedure to go ahead?
Suggestion would be really helpful...
Best Regards
KS

Hi
Check the below link
http://help.sap.com/saphelp_sm32/helpdata/en/58/f6383fdb800804e10000000a114084/frameset.htm
as your Data source support ABR -Delta process, check whether you have mapped ROCANCEL field in data source to 0RECORDMODE in DSO.
As Data source is of ABR type, you can use DSO of Additive or Overwrite functionality
Hope this helps
Regards,
Venkatesh

2LIS_02_SCL loaded to DSO

Hi,
I have just started up a purchasing project.
According to SAP standard solution 2LIS_02_SCL is loaded into DSO's with a key containing: Document, Item, Schedule line.
However, as far as I can see, a lot of info is lost in that concept.
Ex. for the following field in the extractor:
BWGEOO u2013 Purchase Value in Order Currency
The value contained in this field depends on the information stored in the field BWVORG (BW Transaction Key).
The field determines if the value is derived from a purchase order, a goods receipt, or an invoice.
From the top of my head, it therefore seems profitable to use a DSO with a key that ALSO contains the BW Transaction Key.
In that way BWGEOO holds the Order value, GR Value ot IR Value, depending on the whether BWVORG is 1, 2 or 3 (3 records)
In the SAP standard setup BWGEOO just holds the value for the last event (one record).
However, are there any pitfals in that approach?
Thanks in advance.
Lars

Hi Lars,
As Elangovan Subbiah suggested, keyfigure model is better to reduce no of records.
3 key figures for Order value, GR Value ot IR Value.
One more: As datasource: 2LIS_02_SCL is ABR delta capable and should load to CUBE or ODS in Addition mode only. If you are loading in Overwrite mode, you need to be very careful.
Please check: [Purchasing Data (Schedule Line Level)|http://help.sap.com/saphelp_nw04/helpdata/en/8d/bc383fe58d5900e10000000a114084/frameset.htm]
Hope it Helps
Srini
[Dont forget to close the call by assigning poings.... - Food for Points: Make a Difference through Community Contribution!|https://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/007928c5-c4ef-2a10-d9a3-8109ae621a82]

Inventory Management Extractors via DSO to Cube 0IC_C03

Dear experts,
to fulfill the requirements of DataWarehouse spirit using Entry-, Harmonization- and Reporting-Layer I want to use for Inventory Management a Data Flow from extractors 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM via DSO/DSOs and later on to Cube 0IC_C03.
In this forum there are some opened threads about this issue, but none has been resolved! Many hints are about the "How to Inventory Management..." - some other say: "You can use DSO's!" - others say: "Don't use DSOs!". So: Where is the truth? Is there anybody who can provide a really praticable way to implement the above mentioned data flow?
I'm so excited about your suggestions and answers.
Thanks in advance and regards
Patrick
--> Data Flow has to be in BW 7.0

Hi Patrick,
Yes indeed there is.
Using DSOs in inventory flow is absolutely possible. Here's what you need to know and do:
1 - Firstly don't be apprehensive about it. Knowledge is power! We know that inventory uses ABR delta update methodology and that is supported by DSOs so no doubt abt it.
2 - Secondly Inventory is special because of non-cumulative and several rule group at cube level for BX and BF.
3 - Now as you want to use a DSO and I am presuming that this will be used for staging purpose, use a write optimized DSO as the first layer. While mapping from DS to this DSO, keep one to one mapping from field to Info-objects.
4- Keep in mind that from Infosource to 0IC_C03 there would be multiple rule groups present in transformations.
These rule groups will have different KPIs mapped with routines. The purpose is that from ECC only 1 field for quantity (BWMNG) and one field for value (BWGEO) is coming but from Infosource to 0IC_C03 the same fields in different rule groups are mapped to different KPIs (Stock in transit, vendor consignment, valuated stock etc) based on stock category, stock type and BW transaction keys.
5- So create a write optimized DSO. map it one to one from datasource fields. create/copy transformations from this DSO to cube maintaining the same rule groups and same logic.
6- you can also use standard DSO and create rule groups and logic at DSO level and then do one to one from DSO to Cube.
Keep in mind that these rule groups and logic in them should be precisely the same as in standard flow.
This should work.
Debanshu

ROCANCEL Field problem SD 2LIS_11_VAITM

Hi
I am facing a problem in which one SD report i am getting few sales order which are cancelled in R/3 but still coming in my report.
I checked in 2lis_11_vaitm and there is no value coming in ROCANCEL field.
0STORNO is reversal indicator but there is no data in it.
I am using 0SD_c03 for reporting cube.
What can be the possible solution to block cancelled records coming in report.
Thanks
Navneet

Hello,
We are using Addition mode for a Quantity KF then we are getting as following way from PSA to cube
PSA ( from R3)
Document number   Quantity item
1234                           5          10
After we cancel that record with reason code PSA pulls 2 records
Doc-num     Quantity   item   ROCANCEL
1234              -5           10       X
1234               5            10      ' '
After I load into DSO (in BI 7.0)
Active table has Doc-num     Q    item
                              1234          5    10
samething happens after the activation. It should get 0 but it shows order quantity has 5
I mapped ROCANCEL --> 0recoremode in the tech rule group in the tranformation. Also 2LIS_11_item is a ABR Delta mode to handle before and after image.
I am unable to trace because change log has empty for rocancel.
Any ideas?
Thanks,
Abby.

ABR,ADR delta methods

Dear SDN,
I need the different types of delta methods provided like ABR ADR.
What are others.
Regards,
Rahul

You can find all the delta methods in table RODELTAM.
Take a look at this thread for more information...
Delta Process

Delta Process different for different fields in purchasing (2LIS_02*)

Hi,
My second question for the day and its something that has been bothering me for some time now. We use some of the PUR extractors to get PO information such as SCL line, ITEM, goods receipts etc.
For the past few days I have noticing that some fields in the extractor fetch only after images(AIE) whereas some fields gives full delta (ABR). Due to this some infoobjects had to set to overwrite and some to add in our ODS.
I was wondering why its behaving like this on a field level and if there is any place to set these settings.
The only place I can think of is ROCANCEL field in RSA6 but ROCANCEL is only for reversals.
Any thoughts?
Thanks

It seems that (SAPLEINS)T_EKPO[] and (SAPLEINS)T_EKKN[] and (SAPLEINS)T_EKET[] works, but not (SAPLEINS)T_EKKO[].
Table T_EKKO is not know. Isn't that strange?

Generic delta with function module

Hi Gurus,
Is it possible to create a generic DataSource with delta support using function module following the queue delta mechanism (u can get some function moduel in MCEX function group, and check the outbound delta queue before and after update in transaction smq1.
I can store the delta data using qRFC and collective update mechanism. but I don't know how to create a generic data with delta and how to attach a rfc destination (& logical system) to the data source. The Source system information is stored in the table "ROOSGEN". Is there any configuration setting required to do the same.
Regards,
Jugal

Jugal,
What I understand you to be asking is if it is possible to create a generic delta extractor which uses the delta queue. If this indeed is your question the answer is yes.
First you need to create your data source so it is visible via tx RSA5 and need to make sure that the delta type (ie ABR, AIM)is set appropriately for the datasource.
The issue however is determining from where you will associate your delta hook (when will you write to the queue)? I have in the past utilized BTE's, Business Transaction Events to write information out to the delta queue, you can see a list of available BTE's in your system via tx FINF.
Once you find a place to write your deltas from you call the below FM with the appropriate datasource.
RSC1_TRFC_QUEUE_WRITE.
Once you have done this the standard BW extractor for deltas will pull the information from the delta queue. But from what I understand you just want to know how to associate the data with the delta and that is the FM listed above.
Hope this helps,
Cheers,
Scott
> Hi Gurus,
>
> Is it possible to create a generic DataSource with
> delta support using function module following the
> queue delta mechanism (u can get some function moduel
> in MCEX function group, and check the outbound delta
> queue before and after update in transaction smq1.
> I can store the delta data using qRFC and collective
> update mechanism. but I don't know how to create a
> generic data with delta and how to attach a rfc
> destination (& logical system) to the data source.
> The Source system information is stored in the table
> "ROOSGEN". Is there any configuration setting
> required to do the same.
>
> Regards,
> Jugal

Issues with 0PP_C03 delta loads

Hi,
I loaded the data from 2LIS_04_P_ARBPL & 0PP_WCCP to 0PP_C03. Initialization of the data load went fine. Did the delta loads to BI and observed that I am not getting any of the Key figure data in the cube. All the values are showing as Zero.
When I observed the in the PSA table and in the RSA3 , I observed that for every order 2 entries got created, One is with +ve values and another with u2013ve. So at the end while updating to cube its nullifying the values. Because of this reason I am not able to view the latest data which is updated as Deltas.
I am not sure what settings I missed. Could some one please help me to fix this issue.
Thanks & Regards,
Shanthi.

Thanks Francisco Milan and Shilpa for the links. Itu2019s very useful. But still I didnu2019t able to find the cause of the issue.
My data source 2LIS_04_P_ARBPL is of ABR type and the update mode for KF is Summation. In the data source level, I am getting the values with before & after image (same entries one with +ve & another with u2013ve) and as I am using the u201CSummation as my update type for KF its getting nullified.
Because of this reason I could not able to get the values in my report. Could any one pls help me on this as I am reaching the go-live date. I need to address this issue immediately. Thanks for all your inputs.
Regards,
Shanthi.

How will the system handle delta in the below scenario

How will the system handle delta in the below scenario
Day 1
DS--->DSO
PSA
Document Number| Customer | sales value
1001| RAMLAL | 10000
Your change log for DSO will read
Req1| 1001|RAMLAL|10000|N
DSO(overwrite)
1001|RAMLAL|10000|
Day 1
DSO--->Cube
Req1| 1001|RAMLAL|10000|
Day2
DS--->DSO
PSA
Document Number| Customer | sales value
1001| RAMLAL | 30000
Your change log for DSO will read
Req2 | 1001 | RAMLAL | -10000 | X
Req2 | 1001 | RAMLAL | 30000
DSO(Overwrite)
1001 | RAMLAL | 30000
Day 2
DSO--->Cube
Req1|1001|RAMLAL|10000|
Req2|1001|RAMLAL|20000|
Please explain with example
Scenario 1: Req1 & Req2 are deleted ONLY from change log on Day 3
On Day 4:
DS--->DSO
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 10000|C
What will happen to the Sales Value in the cube?
What will happen to the Req1&Req2 in the cube?
Thanks
Tanya

Tanya,
Please explain with example
Scenario 1: Req1 & Req2 are deleted ONLY from change log on Day 3
On Day 4:
DS--->DSO
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 10000|C
What will happen to the Sales Value in the cube?
What will happen to the Req1&Req2 in the cube?
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 10000 |C
--> Here 1000 is not correct value, as 1000 is change to 3000. It should be 3000. record should be as below.
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 30000 |C
--> As this data related to sales, and i hope you are using standard ABR extractors(Business Content).
ABR datasources delivers before and after images.
Before image:
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | -3000 |C
Before image:
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 0 |C --> value changed from 3000 to Zero.
If you are loading in additive or Overwrite into an ODS total sales for 1001 at end of day 4 will be Zero.
Hope it helps
Srini

Cube 0PP_C03 consists DS 2LIS_04_P_ARBPL(with int. delta), 0PP_WCCP(full)?

Hi,
i have an cube 0pp_c03 having DS 2lis_04_p_arbpl have option full and int. delta update for info package AND 0pp_wccp with full update.
what type of updation for each data source will be ideal?
Is it possible to set delta for DS other than LO - ex: 0PP_WCCP?
Best regards,
dushyant.

Thanks Francisco Milan and Shilpa for the links. Itu2019s very useful. But still I didnu2019t able to find the cause of the issue.
My data source 2LIS_04_P_ARBPL is of ABR type and the update mode for KF is Summation. In the data source level, I am getting the values with before & after image (same entries one with +ve & another with u2013ve) and as I am using the u201CSummation as my update type for KF its getting nullified.
Because of this reason I could not able to get the values in my report. Could any one pls help me on this as I am reaching the go-live date. I need to address this issue immediately. Thanks for all your inputs.
Regards,
Shanthi.

FI-SL Delta Handling: Note 328197

Due to a project requirement we are considering the implementation of note 328197, in order to extract FI-SL data in Delta Mode (ABR). FI-SL Extrators are already in use with some Virtual InfoCubes, and we would like to access the same DataSources to feed a Basic InfoCube
The questions we have about this implementation are:
1 - Will the Extractors modified to Init-Delta Mode still be accessible with Virtual InfoCubes?
2 - Is it possible to de-implement Note 328197?
3 - Considering that Note 328197 acticipate a standard functionality of R/3 4.7 is it fully supported?
Did somebody experienced on such a problem?
Many thanks in advance ... 10 points for sure, if you have a good answer!
GFV

While I haven't used this report I can tell you the following information:
1. Take a look at field VIRTCUBE in table ROOSOURCE. This talls you if a data source is available for a virtual cube. The delivered reports don't change the field so virtual cubes should work fine.
2. Basically yes even if I don't think it should be necessary. All the datasources still run in full mode.
But you should be very careful de-implementing it. I would do it only if absolutely necessary.
3. The note is fully supported. You only need to make sure that you discard the mentioned changes during 4.7 upgrade (especially if you don't do it soon but in some years).
Best regards
Dirk
3.

Blog Clarification: Role of BI developer to get Deltas functional (part 1)

Hi,
I will appreciate some clarification on the following blog that I reviewed:
/people/swapna.gollakota/blog/2007/12/27/how-does-a-datasource-communicates-delta-with-bw
This blog seems to be suggesting that as a BI developer, you need to know the DELTA TYPEs for each datasource (selected in R3) and with that knowledge, you will be in a better position to choose Update types in ODS/DSO Overwrite or Addition, in the BW/BI environment.
At least that is what I came up with from the review.
1. For each datasource you activate as a BW developer in the BW environment, do you really need to go to R3 and study this datasource through the table RODELTAM to see the datasource type e.g. ABR, ABR1, etc and all the settings such as serialization =1 or 2?
2. I thought these datasouces, e.g. 2LIS_02_HDR are SAP delivered, ready to be used, isnu2019t it?
So, I understood that a decision will have to be made between ABR and ABR1 as the delta type.
i. whose responsibility is it to make such decisions?
ii. The R3 folks or the BW developer?
iii. What influences such decision making?
iv. In this table(RODELTAM), on R3, I saw several u201CXu201Ds under different columns, who sets these?
3. There were also discussions as to whether a datasource supports DSO/Cube or not?
Does this support the argument to study a datasource on R3 side in the table RODELTAM before using it?
Thanks

1. For each datasource you activate as a BW developer in the BW environment, do you really need to go to R3 and study this datasource through the table RODELTAM to see the datasource type e.g. ABR, ABR1, etc and all the settings such as serialization =1 or 2?
If you are a newbie and using it for the first time ofcourse you have to.But I would simply use RSA2 transaction than those tables.
2. I thought these datasouces, e.g. 2LIS_02_HDR are SAP delivered, ready to be used, isnu2019t it?
So, I understood that a decision will have to be made between ABR and ABR1 as the delta type.
i. whose responsibility is it to make such decisions?
ii. The R3 folks or the BW developer?
iii. What influences such decision making?
iv. In this table(RODELTAM), on R3, I saw several u201CXu201Ds under different columns, who sets these?
Ofcourse its BW developer who deals with BW related things.
iii. What influences such decision making?
Your datamodel.
3. There were also discussions as to whether a datasource supports DSO/Cube or not?
Does this support the argument to study a datasource on R3 side in the table RODELTAM before using it?
Datasource supports DSO/Cube, thats the whole point for determining the type of delta.
Hope this helps.

ABR delta

Similar Messages

Maybe you are looking for