Add a characteristic in the extractor

[former_member249672]

Hello,

I need to add a new characteristic in the delta extractor 2LIS_11_VAHDR.

I don't want to reload the data (initialization) in the infoprovider and I don't want to break the "delta" loading.

Is it possible to add the characteristic in the extractor then ? Are there special things to check before adding the fiels (like to delete LBWQ or RSA7) ?

I just want the new characteristic to be filled in the future with the future orders.

Can someone help me ?

Thank you for your answers.

Vanessa R.

[Former Member · Accepted solution]

Yes, You can add the char to the extractor without disturbing the current Init/Delta.

Ensure that you transport this into production as soon as you run the current delta so that you will not be in toruble of transporting when loading the data.

You will get data for the future orders only.

Regards, Siva

[former_member249672 · Accepted solution]

I've modified the ectraction struture to add the new field and now when I try the extraction by RSA3 in the source system, I have a dump IMPORT_ALIGMENT_MISMATCH.

It seems that the system doesn't like that I add a new characteristic. Are you sure about what you say ?

[Former Member · Accepted solution]

Try to fire the V3 job and clear LBWQ first ... then load delta to clear delta queue. and then try.

[former_member249672 · Accepted solution]

How can I fire the V3 job ?

I have cleared LBWQ queue and cleared the delta queue by loading my infopackage. And now I try to test the extractor by RSA3 in my source system but I always have my dump. I'm afraid I've broken the init/delta !

Is there something to do to correct that ?

II'd like to avoid the initialization of my infoprovider.

Thank you for your answers.

[Former Member · Accepted solution]

1. To fire the V3 job, you need to go to LBWE, and for 13: SD Billing BW you will under column "Update" click on option "Job Control" (you may run the job from there, just make sure that you make a note of any scheduling options that currently exist before executing immediately, and that you go back and restore those).

2. I think the error with RSA3 is to be expected, based on the scenario that you explain. For LO Cockpit, RSA3 pulls from the BW Set up tables for the application in question. If you did not delete the set up tables (using LBWG) and if you did not recreate these tables (OLI9BW for SD) after changing your datasource structure, then there is going to be a mismatch between the current extract structure and the one used to build your set up table. I do not think this breaks your delta. To test that your delta is still working you need to capture some change in R/3, and then look it up in LBWQ, then run the job as explained in point 1 above, and then check in RSA7 if you have the entry corresponding to your change. You may delete and rebuild the BW setup tables if you do not care about the last set up table and you insist in using RSA3.

[former_member249672 · Accepted solution]

Ok but the problem is when I fire the V3 job I have a dump message_type_x which confirms me that I think the init/delta is broken.

For the RSA3, I agree with you, if I try to read some data in the setup which have the old structure, it is normal that I dump.

But what is anormal is that when I create a new document, the LBWQ gets the new entry but it can't be passed to the RSA7 queue because of the dump when firing the V3 job.

What can I do then ?