Idoc CREMAS generated by change pointer do not contain all segments

[AymericDony]

Hello Dear Expert,

We are facing an issue with one requirement in the Supplier idoc generation (CREMAS) based on Change Pointer.

When you modify a field in the supplier (XK02), if the field is indicated in BD52 as being a “change pointer”, then it will cause the generation of a CREMAS idoc to transmit the information to an external system.

However, only the segments linked to the modified field will be present in the idoc.

How can all the segments and all the informations from the supplier be always sent and present in the CREMAS idoc when this idoc is generated via the change pointers? Even if only a "change pointer" field on general data is modified ?

For example, if you only modify the general data of a partner, then the idoc will only contain the "E1LFA1M" segment:

If the company code data is also modified, then the "E1LB1M" segment will be generated :

Thanks in advance.

Best Regards,

[vincent_lock]

Hi Aymeric

You can achieve what you want by implementing BADI enhancement spot VENDOR_ADD_DATA_BI.

Use method PROCESS_ALE_OWN_CHANGE_POINTER. Though no change pointers have been written for the segment(s) you want (the ones you'd get via BD14 for instance), you can 'fool' the system into thinking they had been written, by adding an entry into the relevant itab.

For instance, you mentioned LFB1, so you'd insert an entry into T_LFB1_KEY to indicate you want the segment output.

Regards

Vincent Lock

[Garcia]

Hi Aymeric,

From what I can remember, that situation is not achievable via standard settings.

Try searching for past similar requirements without restricting on a specific idoc message, like for example:

https://blogs.sap.com/2016/02/05/send-material-in-full-change-pointers-option-in-bd10/

All the best,

[AymericDony]

Thank you for your reply.

Indeed, the only possibility seems to be to hijack standard transactions...

Finally, we will opt to set up an odata service that covers our needs.

Best Regards,