cancel
Showing results for 
Search instead for 
Did you mean: 

Changing organizational structure in SRM

Former Member
0 Kudos

Hi All,

We are in production with SRM 4.0 since 1.1.2006 and using R/3 since 2003.

Our company intends to change the organizational structure (delete, merge, move

organizational structure).

We are going to copy our PROD systems (both R/3 and SRM) to other systems to be able to apply and check the changes.

Problems:

1. How is it possible to replace “LogsysXXX” to that of the new backend for each attribute in the organizational structure, for every organizational unit? The attributes are not inherited data because they differ from one another, and there are many of them within the org structure (for example the attributes “plant”, “purchasing org and group” have the “LogsysXXX” defined as part of the parameter. There are about 600 users with 50 attributes each in all the org structure; therefore a manual process would not be acceptable.

Note: We didn’t copy the HR organization to the SRM org structure.

2. Documents which are being processed and at the time of “copy client” and were already created in SRM (PO, POR, SC), point to the old backend (“LogsysXXX”).

How do we change this pointer in existing documents to the new backend system?

Best regards,

Rami

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Rami,

to summarize:

- run BDLS to change Logical System in all tables refering this field

- run RH_OM_ATTRIBUTE_REPLACE to replace Logical System in organizational attribute values (infotype 1222) (can not be processed by BDLS as attribute value is not with LS type).

Rgds

Christophe

yann_bouillut
Active Contributor
0 Kudos

Hi Rami,

It is RHOMATTRIBUTES_REPLACE as RH_OM_ATTRIBUTE_REPLACE does not exist.

Kind regards,

Yann

Answers (2)

Answers (2)

yann_bouillut
Active Contributor
0 Kudos

Hi Rami,

Please check former post :

Kind regards,

Yann

Former Member
0 Kudos

Hi RAMI BEN

Use Transaction BDLSFirst run in test mode.

We had done a client copy where in client 500 was refering to logsys name of client 600 and in that case we deleted all the masters and re- replicated them in SRM client 500 from r3 500.

How ever later we found this transcation BDLS .

check i guess this should work to change the logsys names in the tables.

regards,

Nimish sheth