ALE Change Pointers

[Former Member]

Hi,

I have a requirement of extracting customer master data through MDM_CLNT_EXTR tool.I have

done the settings for change pointers using message type DEBMAS & ADRMAS.But the existing

interfaces also uses the same message type for change pointers.

If I run the delta load through the MDM tool it will process the change pointers and will

set the field "ALE Process Indicator" as X(Processed).

I need the same set of fields for the other interface which is set for the same message

type.Since its processed already using the tool, it is not available for the other interfaces.
Please help me to sort out this issue.

Regards

Samee

[Former Member]

Hi Abdul,

I can suggest you a rough way, you will have to ponder and come up with a neat solution to this issue. What you can do is have a ZTEMP table, which should hold all your Interfaces. You can insert X for each interface run. So you know if not all the interfaces have run, you should not leave the ALE process indicator as 'X'. You will have to change the logic such that after each DELTA Load run, the change pointers for those records should get cleared(this can be done using an FM which i dont exactly remember, but can be searched) unless all the interfaces have 'X' set(ie, in the last interface run).

This solution is not perfect as I need to know the order and frequency of your interfaces. For eg, if any of the interface runs twice before the other interface is run, then it will pick up hte same data twice, hence creating an overload.

Hope this give you some idea.

Regards,

DN.

[Former Member]

Hi Samee

I'm not experienced with MDM data extraction at all but I've worked with ALE a lot. Normally, when processing change pointers to create ALE messages we would use transaction BD21/program RBDMIDOC.

Is there anything that the MDM_CLNT_EXTR tool does that BD21 does not? If there is no extra functionality in the MDM tool then have you considered setting up the partner profile and distribution model for the MDM system, in addition to the other interface system(s), and just let BD21 handle the processing of the same change pointers for both purposes?

Regards

Glen