Logical Systems & SRM Customizing

[Former Member]

Dear Experts,

I would like to guarantee BDLS won't be executed within our SRM Productive environment. Unfortunately, according to the functional team and because of customizing requirements, it appears logical systems cannot be generic enough to guarantee the process. For instance, the organizational structure refers to <SID>CLNT<MANDT> instead of alias like 'ECC'.

Any advice to ensure to the infrastructure team they will never run BDLS after transports?

Thanks and Regards,

Ludovic

[Former Member]

Hi,

You can restrict user's from executing BDLS by removing the autorisation objects needed to execute it from the user's roles. (May be you could discuss this with your Security team as to how to prevent users from accessing a Tcode)

Regards,

Nikhil

[Former Member]

Hi,

thanks for your prompt answer. Unfortunately, the issue is a bit more complex.

1) We have defined a backend RFC in SRM : <DEV>CLNT100

2) We have define a distribution model in BD64 referencing this RFC connection

3) We tried to define R3 and SRM as alias within the customizing : "master data/ALE Options/logical sytem", SMOEAC, etc... (refering <DEV>CLNT100)

4) We have changed the organizational structure PPOMA_BBP in order to reference R3

5) Under "Master Data>Determining financial system for product type", we have defined (source = R3 / target = SRM) and so on, and so on...

6) We have launched the replication and then tried to retrieve products categories from PPOMA_BBP

Unfortunately, there is no existing product type under logical system R3 but under <DEV>CLNT100 and the shopping cart doesn't work => missing logical system

However, when naming the logical system <DEV>CLNT100 (instead of R3), everything is working ...

Unfortunately, when we will transport additional customizing to another system, this customizing will refer <DEV>CLNT100 instead of <PRD>CLNT100.

On site, SRM experts use to launch BDLS after customizing transports in productive systems in order to modify the SID. We cannot afford to launch BDLS in a productive environment which will probably take several hours to run.

Thanks for your recommandations,

Sincerly,

Ludovic

[Former Member]

Dear experts,

We found a solution by implementing BADI BBP_DETERMINE_LOGSYS. Actually, the logical system within the SRM infrastructure part of the customizing is based on generic alias (system independant) while the logical system which depends on system settings (ALE, Distribution Model) is SID dependant. As result, functional customizing which will be transported (PPOMA_BBP, Products, ...) refer to the generic alias.

Kind Regards,

Ludovic