2LIS_11_V_SCL

[Former Member]

We have one extractor named 2LIS_11_V_SCL. This is meant to send ABR images. I have checked the ROCANCEL mapping and it is mapped to 0RECORDMODE correctly. The KFs are set to "Overwrite". But some how the extractor is not sending the reverse images. As a result, if an item has been deleted in R/3, this is not recognized by this extractor. I have compared this with the other extractors like 2LIS_11_VAITM which is sending reverse images correctly and found no difference between these two.

I am not sure if I am missing out on anything else that I need to check.

We have thought of a workaround to overcome this. We will zero out the KFs in the extractor user exit if the line item does not exist in the VBAK/VBAP table.That way, we can deal with deleted Line Items.

But, before we do that, I wanted to check with you all if you have come across this problem. Any input on this is highly appreciated.

Thank You,

Anjana Banerjee

[former_member188011 · Accepted solution]

Hi Anjana:

On the scenario you described, when records are deleted R/3 the 2LIS_11_V_SCL Extractor sends an "R" on the ROCANCEL field, you can see those "R" on PSA.

On the other hand, the DSO doesn't show records with "R" on the 0RECORDMODE, because the "R" is just used to delete the records previously inserted on DSO with the same values on the Key Fields.

For more details you can take a look at the blog by Swapna Gollakota.

"How does a datasource communicates "DELTA" with BW?"

/people/swapna.gollakota/blog/2007/12/27/how-does-a-datasource-communicates-delta-with-bw

Regards,

Francisco Milán.

P.S. Review the Key defined on your DSO, it might be incorrectly defined and this could be causing some problems.

[Former Member]

Hi ,

Please check :SAP Note Number: 440679

Symptom

One or several of the following problems can occur in the deletion of an item or schedule line or an entire document of application 11 or 12, if at least two DataSources are updated into the same ODS object:

1. The ODS contains deleted data records in spite of transfer of a reverse image. By mistake the key figures are not all initial in this case.

2. If you delete an item or a schedule line in the document and recreate them afterwards, individual key figures are initial by mistake.

Additional key words

Cause and prerequisites

Prerequisite is that at least one of the DataSources involved transfers a reverse image during the deletion (in the OLTP System ROCANCEL = "R" and in the BW System 0RECORDMODE = "R"). All DataSources of applications 11 and 12 deliver a reverse image during deletion, except for DataSources 2LIS_11_V_ITM and 2LIS_11_V_SCL. Prior to implementation of Note 426731 the latter DataSources transfer also reverse images at event VA (Order) if you delete an order item or an order schedule line.

The deletion and creation of schedule lines often occurs in particular for rescheduling runs.

Examples:

An ODS object is updated by DataSources 2LIS_11_VAITM and 2LIS_11_V_ITM. The key fields in the ODS are order number and number of the order item. Key figure 'Order Quantity' is updated cumulatively from field KWMENG of DataSource 2LIS_11_VAITM. Field OAUME of DataSource 2LIS_11_V_ITM updates cumulatively key figure 'Open Order Quantity'.

Example on point 1.:

1. Step: Create item 10 in order 4711 with quantity 10.

-> In the ODS the result is:

Order Item Order Quantity Open Order Quantity

4711 10 10 10

2. Step: delete item 10 in order 4711.

-> If the 2LIS_11_VAITM record (transferred as a reverse image) is updated into the ODS object first, the system first deletes the corresponding data record in the ODS, and afterwards the 2LIS_11_V_ITM record generates it again (the 2LIS_11_V_ITM record is transferred as an after image with changed signs after installation of Note 426731). However, now not all key figures are initial.

Order Item Order Quantity Open Order Quantity

4711 10 0 -10

Example on point 2.:

1. Step: Create item 10 in order 4712 with quantity 5.

2. Step: delete item 10 in order 4712.

3. Step: Create item 10 in order 4712 with quantity 5 again.

It is assumed that no data was transferred into the BW System between the three steps. In addition it is assumed that now the data records belonging to DataSource 2LIS_11_V_ITM come into the ODS for the update first.

-> In the ODS the first result is:

Order Item Order Quantity Open Order Quantity

4712 10 0 5

After also the data records belonging to DataSource 2LIS_11_VAITM are updated into the ODS, the result in the ODS is:

Order Item Order Quantity Open Order Quantity

4712 10 5 0

The Open Order Quantity was now initialized by the update of the reverse image transferred by DataSource 2LIS_11_VAITM

The system does not set up the Open Order Quantity again because DataSource 2LIS_11_VAITM does not update the Open Order Quantity.

Solution

This is a basic problem which can, however, only occur if more than one DataSource is updated into an ODS.

In order to not waive reverse images generally, you must solve this problem individually per ODS object:

In the start routine of the update rules of each of the involved DataSources into the ODS object, set feature "R" of InfoObject 0RECORDMODE to " " in the corresponding data records.

This has the effect that a data record once created is never deleted from the ODS and that all DataSources consistently update the contained key figures.

-Vikram