Restrict XD01 and XD02 t-code while creating customer data directly but not for BP t-code.

[former_member542237]

Our users are only supposed to change business partner data with transaction BP, but NOT the customer data directly with the help of transactions XD01-XD02.

Is there any way to restrict XD01,XD02 t-codes while executing this t-code directly and when we use BP t-code, the authorization problem would not occur for this.

[sez41]

What have you tried so far?

Doesn't simply locking these t-codes via SM01 work?

[former_member542237]

Hi Kivanc,

Firstly, I go through this suggestion ( Please check in below link ) to implement the SAP Note 1895335 or 1895612.

https://archive.sap.com/discussions/thread/1998073

I found this in our system that it can not be implemented.

If we lock these t-codes XD01,XD02, will it affect the working of BP?

[sez41]

I am not sure, that's why I was wondering whether you've tried it. Simply test in QA system and see whether it works.

[former_member542237]

Hi Kivanc,

It works fine for t-code BP, but while uploading the BP documents, it's creating a problem.

[sez41]

And what is that problem exactly?

[former_member542237]

Hi Kivanc,

There is custom t-code to upload the mass BP data, while executing this,it called XD01 in background but XD01 is locked.

Hence,it is showing that XD01 is locked as pop-up message.

[sez41]

Well what would you expect?

I suppose you should be thinking about changing the behaviour of the z-program. Creating customers via barch input is never best practive even in SAP ECC.

[former_member542237]

Hi Kivanc,

We are creating customer data using BP t-code and uploading the mass BP data using custom t-code.

We need to think over that.

Thanks for your overall help. 🙂

[former_member542237]

Also, Is there any Sap note ( same as SAP Note 1895335 or 1895612 ).that we can implement to achieve the requirement?