0BPARTNER_ATTR delta problem with custom field

[martin_kuma2]

Hey Gurus,

The standard extractor: 0BPARTNER_ATTR has been enhanced with one custom field: ZZ_FIELD. (The field has been added to the BP GUI and as via an include to 0BPARTNER_ATTR)

Now, when I change the ZZ_FIELD in the BP GUI, I get a change document. When I check the RSA7 for delta entry I do NOT get any deltas. (When I run delta extraction to BW, same behaviour)

Full extraction works of course.

What did I miss please?

Will reward any suggestions.

Thanks

Martin

[martin_kuma2]

Solved by switching do generic delta

[Former Member]

Hello Martin,

Can you please ellaborate on the solution that you applied?

I have a custom field added to logistics extractor 2lis_12_vcitm and that field is having similar issues.

Only thing, in case of some deliveries, it indeed updates this custom field with correct data and in other cases, it does not..remains in earlier state.

I would appreciate any inputs you may have

thanks!

[Former Member]

Hello Martin,

Can you please ellaborate on the solution that you applied? I really appreciate that. Thanks a lot.

[Former Member]

Hello Martin,

Can you please ellaborate on the solution that you applied? I really appreciate that. Thanks a lot.

[Former Member]

Hi,

First check in RSA3 (source system) whether the data is displayed in this fied. If the data is shown in the RSA3, then it will automatically transferred to BW.

Some times after enhancement of the datasource, we forgot to uncheck the hide field. Please check that also in RSA6.

If your problem is not solved, then carrout the debugging from RSA3. For doing this put a break point in custom field userexit in CMOD transaction.

Hope this helps.

Regards,

Sreenivas.

[martin_kuma2]

Hi Sreenivas,

Thank you for your response.

You may have missed the note about the FULL load:

Full extraction works of course.

I should have marked it more visible.

The field is visible and mapped correctly. The delta is not triggered if only this one field is changed.

Martin

[Former Member]

Hi Martin

There is always this dilemma regarding enhancement of a LO master data extractor. So if you write a code in CMOD for the master data extractor enhancement, the enhanced field won't be delta enabled. For LO transaction datasources, the enhanced field can be made delta enabled by enhancing the communication structure in LBWE and writing the code in SMOD instead of CMOD. The only work around for master data enhanced field could be to run regular full loads for the master data which will get you the correct values for all the fields.

You can refer one of my post regarding a simlar problem

Thanks

Rishi