Question Re: 0recordmode issues in Technology Q&A

0recordmode issues

sap_user62 — Fri, 15 May 2015 18:32:01 GMT

Hello Friends,

Env- BW 7.3

I am facing some challenges in getting updated records which are deleted in ECC. I use datasource 2lis_11_vaitm.

Model is -- data source-->DSO1-->DSO2-->CUBE

I tested the following scenario. I deleted few line item from an existing contract in ECC and saved it.

The delta queue shows line items which are deleted with "R" in the ROCANCEL field.

I mapped the ROCANCEL field of the data source to the 0RECORDMODE field of the DSO1. Loads look good. Change log table has the deleted line items with status "R" in 0recordmode. And in active data tables the lines are cleared out.

0RECORDMODE of DSO1 and DSO2 are already mapped in the transformation by the system. I did not have to change here.

Here the change log table does not show the lines which are deleted with a "R" status. It does not even have those lines.

Now as this is an existing contract, the active data table actually shows the lines which have been deleted too. This is not what is expected.

All the DTP's are taken from the Active data table(without archive).

Very strange thing is this test works good in the sandbox with the same settings for DTP and same transformation.

Thanks a lot for your time and inputs

Ed.

Re: 0recordmode issues

ccc_ccc — Fri, 15 May 2015 18:48:05 GMT

Hi ,

Filter only those records in DTP and extract and see DTP log how the records are coming try to debug and check what record mode it has.

Thank you,

Nanda

Re: 0recordmode issues

sap_user62 — Tue, 26 May 2015 15:40:34 GMT

Thanks Nanda for your reply.

I have debugged the code in dev. However debugging does not allow me to capture the values of 0recordmode.

I tried to check the data in the new data table, change log table and active data table after the loads.

I have seen that from 1st level dso to 2nd level dso the load goes fine. ( load only contains the deleted record test data)

The new data of 2nd level DSO has recordmode as "R" for deleted records.

However the change log table after activation has no data at all.

So the active data still contains records with the deleted items.

I have activated the transformation from 1st to 2nd level DSO and also activate the 2nd level DSO.

No positive results.

Thanks

Ed.

Re: 0recordmode issues

sap_user62 — Mon, 01 Jun 2015 20:24:27 GMT

Hello All,

Further information, DSO1 has 2 keys and DSO2 has 4 keys(common 2 keys with DSO1).

The problem comes in activation of the 2nd level DSO. The new data table looks good.

Is it a known issue.

Ed,

Re: 0recordmode issues

ccc_ccc — Mon, 01 Jun 2015 20:42:27 GMT

What is the error message.

Re: 0recordmode issues

Former Member — Mon, 01 Jun 2015 21:05:30 GMT

Hi,

Can you please check following things for me?

Please check the update mode of your KF's. If there is any KF with summation mode.

In ECC go to table ROOSOURCE & check the delta type of your data source. It should be type ABR.

For deleted orders check if you are getting before image 'X' entries in PSA.

Thanks,

Ajit

Re: 0recordmode issues

sap_user62 — Wed, 03 Jun 2015 15:21:27 GMT

Thanks Nanda and Ajit for your replies.

Nanda- I do not get any error message or errors. The data does not get reflected properly.

Ajit-

Key figures are overwrite mode. Delta is ABR, the data source used is 2lis_11_vaitm. with enhancements

Delta queue, PSA and DSO1 has proper recordmode for deleted entries.

The logic in DSO1- DSO2 works in this fashion.

DSO1 - key1, key3

DSO2 - key1, key2, key3,key4.

According to the logic in the transformation, DSO2 can add 1 record from DSO1 or 2 records from DSO2. There is a logic for adding new lines in DSO2 according to a condition.

Now when we have only 1:1, the record mode works very good, the "R" status is carried through and the active data table of DSO2 has the item deleted.

The problem arises, if there is a 1:2, the change log has 2 entries but the new table has only 1 entry.

Thanks

Ed.

Re: 0recordmode issues

sap_user62 — Thu, 23 Jul 2015 19:27:59 GMT

Update:

SAP suggests that 0recordmode does not work good in case of deletions from one level DSO to second level DSO if the keys from DSO1 and DSO2 are not same.

1358780 - Limitations of DATASTORE loading senarios

Re: 0recordmode issues

sander_vanwilligen — Sun, 26 Jul 2015 00:25:43 GMT

Hi Ed,

The SAP Note is indeed relevant and describes issues as you are facing now. I only wonder how you implemented the Transformation (end routine, expert routine, ... - if so, please share the coding). Can you also please share some additional details to obtain a full picture? Last but not least can you please give some examples of both cases?

Best regards,

Sander

Re: 0recordmode issues

sap_user62 — Mon, 27 Jul 2015 18:19:30 GMT

Scenario -

DSO1 - keys -2- Sales Document, Sales document item

DSO2- keys -4 - sales document, sales document item, billing plan number, billing plan item

billing plan is updated in a DSO which is drop and full load everyday from a ECC Custom table.. Depending on data from billingplan DSO, one or two lines get added to the second level DSO.

Now if the one the line item in sales document is deleted, that particular line will have the recordmode as "R", but from the billing plan DSO, there is no concept of recordmode, the entry is directly deleted on reload.

This caused a mismatch in the change log table for the data that exist and new data that is generated.

Existing data will have a billing plan number and item, but the new record which is generated in the delta load does not have this new entries.

The solution has not yet been implemented, but I would think on these lines.

need to take a dump of active data table before the start of transformation. (start routine)

Then for the records which have recordmode as "R", do not do a lookup on billingplan DSO, instead look at the active data table and fill the values for billing plan and billing plan item.

Then check if the change run table would actually be able to delete all the lines.

Re: 0recordmode issues

sander_vanwilligen — Sat, 01 Aug 2015 01:43:13 GMT

Hi Ed,

Thanks for explaining the issue in detail. I am getting the point now. Your approach seems to be right to me. You will need extra logic to determine if a record exists in the active table.

One question I would like to ask. Do you really need the extended key of DSO2? How would the solution look like if in DSO2 you only have the key fields Sales Document and Sales Document Item? You add Billing Plan Number and Billing Plan Item as additional data fields. Then you only need one record and update Billing Plan Number and Billing Plan Item is they exist.

Best regards,

Sander