BW error after ERP client copy

[jorge_velasquez]

Hi Experts,

I am facing an issue trying to transfer data from QAS to BW.

I checked note 886102 - System Landscape Copy for SAP NetWeaver BW .

Everything seems to be ok but tx BD87 IDOCs got stuck.

After I run report RSEOUT00 in tx SE38 IDOCs works fine and status is green.

RFCs are fine and also authorization check.

Any clue?

[former_member188883 · Accepted solution]

Hi Jorge,

Please check whether logical systems names are changed after client copy .

Execute BDLS to adjust the logical system name,

Regards,

Deepak Kori

[jorge_velasquez · Accepted solution]

Hi,

client copy was refresh from PRD to QAS so logical system can still be the cause?

I can´t see PRDCLNT400 on list.

Regards

[former_member188883 · Accepted solution]

Hi Jorge,

Logical system name can be an issue as PRD and QAS will have different logical system names within table entries as well.

GUIDs also create problems in data transfer post copy. So when you copy ECC client BW client should also be copied to avoid issue with GUID

Regards,

Deepak Kori

[jorge_velasquez · Accepted solution]

Hi,

What Can I do if I can´t see on list PRDCLNT400 in Tx BDLS (QAS) ?

Regards.

[Sriram2009 · Accepted solution]

Hi

I thing you have to restore connection in transaction RSA1 select the source system. just do restore connection in Bw system. during this process its will ask you type the user id "remote"(BW & ERP user id remote & password ) in both systems. and than your can replicate the changes

BR

SS

[jorge_velasquez · Accepted solution]

Hi,

Issue is solved after check WE20 and WE21 and restore connection in RSA1 (aleremote and bw_user as system user)

Regards.

[ACE-SAP]

Hi

The BDLS phase integrated in the ERP client copy process do not convert the logical systems used as a reference for BW system.

You will need to run a BDLS to convert 'bwprdxxx' => 'bwqasxxx'.

Make sure in WE20 that the partner profiles for BW target are active this can block the Idoc exchange.

Regards