Logical system Name Change Via Transport

[alok_jaiswal]

Hi All,

Recently we made changes in parallel processing profile customizing table  (/SAPAPO/SDP_PAR) and created entries for Macro Jobs and CIF.

For Application "CIF Delta Report", Logical system is mandatory and in Dev we gave the APO Dev Logical System Name (AD1XXX). Now when we moved the changes to Quality, expectation was that Logical system name for CIF Entry in the table would change to AQ1XXX - However, it still shows as AD1XXX there. Moreover AD1XXX entry is not a valid entry in Quality System and even when we see Drop Down values for that column (Press F4) - Only APO and ECC Quality systems names are appearing.

Please suggest how can this logical system name be corrected. One option is running BDLS, but when this TR moves to Production there also we might end up in same scenario (Logical system as AD1XXX instead of AP1XXX) and running BDLS in Production wont be approved.

Please suggest if there is any other option to handle this.

Regards,

Alok

[rupesh_brahmankar3]

Hello Alok,

Access transaction BDLS.

Input the Old Logical System name.

Enter the New Logical System name.

Set flags "Test Run" and "Check existence of New Names in Tables"

In "Tables to be Converted", enter table name /SAPAPO/SDP_PAR.

Execute same without Test run

Please refer SAP Note 887971 - CCR: Documentation is missing for the parallel processing

Best Regards,

R.Brahmankar

[alok_jaiswal]

Hi Rupesh,

Thanks for replying.

As suggested earlier, We know BDLS can be one of the options, but issue is when this TR would move to Production we would not have authorization to run BDLS directly in production to convert the logical system name from AD1XX to AP1XXX

So this is the reason we are not going with BDLS and looking if any other alternative exists.

Regards,

Alok

[rupesh_brahmankar3]

Hello Alok,

I don't think there is any alternative in standard SAP, you may refer to OSS knowledge base article  1708883 - How to change the Logical System in the Delta Report Parallelization Profiles.

Best Regards,

R.Brahmankar

[frank_horlacher]

Hi Alok,

we describe a solution in our

SAP Rapid Deployment Solutions (RDS)

Quick Link

                Access SAP Rapid Deployment Solutions (RDS) directly via
                  http://service.sap.com/rds

SAP Demand and Supply Network Planning rapid-deployment solution

Quick Link

    Access this area directly via
http://service.sap.com
/rds-dpa

In confgiguration guide

Central Master Data Replication (SCO)

you can read how it is done with

Create Entries in Table
TVARVC for Logical System Variable in Variants

Frank

[Former Member]

Hi

There are two cases where you need to do this

1. When you will copy one system say production environment on say test  or quality system. All the production connection system mapping gets transferred to thos systems. BAsis need to run BDLS to get the correct source system mapping and client mapping in order to get the correct data loaded in BW system.Else when u will load you will start getting the production data!!

2. when you will create new system or environment automatically mapping needs to be carried out wrt the new system source system mappings.

3. SE21 - Package builder for Transports.

4. TRAnsport layer needs to be adjusted

5. RSLOGSYSMAP needs to create entries for new system and client ,else transports might fail

Please let us know if it helps

Amol

[alok_jaiswal]

Hi Amol,

I could not understand, how options you suggested would help in this case.

Issue here is that TR movement from Dev to Quality is changing the Logical system name incorrectly, so would like to know how it can be corrected without running BDLS in destination system.

Regards,

Alok

[Former Member]

Hi Alok

Ideally we should run the BDLS topic. In case you don´t want to run, you can change it by getting into debugging mode.

It should be very easy technique and any developer can help you to do it. But as I mentioned that´s not the standard process but will definitely solve your problem.

In future you should follow above propose solution.

Thanks

Amol

[alok_jaiswal]

Hi Amol,

Only thing which is baffling for us is why the Transport request is unable to change the Logical system pointing to correct destination.

We have seen earlier with process chains for example, when we move the TR from Dev to Quality then Logical system gets changed automatically at all places in variants/source systems etc.

However in this case,it is still showing incorrect Logical system in Quality.

I know BDLS/changing the table entry in Debug Mode can help to solve this - but I was thinking if we have any other options as it is very common change and thought there could be some other options instead of these bandaged solutions.

Thanks for your reply.

Regards,

Alok

[Former Member]

As I mentioned, ideally logical systems get corrected when we move the TR across the landscape.

is it possible for you to check with your basis team, if respective tables where we define source and target logical systems defined correctly like RSLOGSYSMAP.

If you have respective tables maintained correctly then you should not face the issue.

Thanks

Amol

[alok_jaiswal]

Hi Amol,

I checked the entries in table RSLOGSYSMAP and could see entry where Original system name is AD1XXX and Target system as AQ1XXX - so ideally in this case, it should have worked?

Regards,

Alok

[Former Member]

Dear Alok

As also mentioned below by our colleagues, either BDLS or changing via debugging mode( if you have authorization) are the mainly and only 2 ways. The table table RSLOGSYSMAP plays roles in more into DP or BW areas.

Thanks

Amol

[Former Member]

Dear Alok,

Usually Basis team runs a report which changes the name of all Logical Sytems from Dev. to Qualtiy or to Prod. The logical system name is not req. only for CCR or CIF, in back end logical system name is used.

Regards,

Anil

[alok_jaiswal]

Hi Anil,

Yes that report is generally BDLS. But here in this case, we would not have authorization to run BDLS directly in production to convert the logical system name from AD1XX to AP1XXX

regards,

Alok