Stop IDOC and Change pointer creation - during Data loads

[ramesh_ananthaiah]

Hello Friends,

We are implementing a SAP solution for North America and during cut-over if we are loading Master data from Legacy we should impose a restriction on not create change pointers and IDOC for Vendor, PO and Materials for NA. Where as same should work seemlessly for Europe and Asia company codes.

Is there a way to restrict the same?

Please help ASAP.

Kind Regards

Ramesh

[ramesh_ananthaiah]

Hello Friends,

We are implementing a SAP solution for North America and during cut-over if we are loading Master data from Legacy we should impose a restriction on not create change pointers and IDOC for Vendor, PO and Materials for NA. Where as same should work seemlessly for Europe and Asia company codes.

Is there a way to restrict the same?

Please help ASAP.

Kind Regards

Ramesh

[Former Member]

Yes use BD61 to stop creation of all change pointer. Once the data is loaded, switch back on.

[ramesh_ananthaiah]

Can we  restrict change point creation in BD61 for certain company codes only?

[Former Member]

No.. In that case you have to use filters in your distribution model, as long  as the Company code is on a mandatory segment it will stop the idoc generation.

Or

you can use BADI IDOC_CREATION_CHECK and set CREATE_IDOC as blank inside method IDOC_DATA_CHECK based on your condition.

[Former Member]

Rudra,

The badi IDOC_CREATION_CHECK is something new to me. Is this triggered for all outbound idocs? Does this need some sought of config before the same can be used?

V.

[Former Member]

Hi Vikram,

This BADI is called from FM MASTER_IDOC_DISTRIBUTE and  COMMUNICATION_IDOC_CREATE and ALE_IDOCS_CREATE ( Replacement for MASTER_IDOC_DISTRIBUTE for asynchronous BAPIs ).

So I would say it covers almost all the outbound master data sending via Idocs and also the custom program where we use those above mentioned FM.

I am yet to find a Master data object which does not call this BADI while generating the outbound Idoc.

No there is no special configuration needed but it may not be available to older version before ECC. Not sure about that. And Transaction data is not covered as you might know that we have other techniques to stop them.

R

[Former Member]

Thanks Rudra.

[Former Member]

For idocs you can probably add a filer using company code via BD64.

For change pointers, I don't think you can stop creating based on company codes. There is no such option in BD50. You either activate or deactivate but you can try using the badi BDCP_BEFORE_WRITE. See if you can add a check before the CP is created using the badi.

V.

[ramesh_ananthaiah]

Thanks you Vikram n Rudra