Error when running BDLS

[Former Member]

Dear expert,

BDLS as the final steps of system refresh (ECC), i failed with error

i scheduled it as the background job

error: "Data inconsistency when running program RBDLSMAP, form routine PROCESS_SPECIAL_OBJECTS"

And also i can't not run the BDLS again , by error "new logical already assigned" and I failed to delete the entry in BD54

Anyone have idea?

And i would also like to know the risk if we skip the BDLS running after refresh

Best regards,

kate

[Sriram2009 · Accepted solution]

Hi Kate

1. Have you completed the post refresh tasks?

2. Could you check this SAP Notes

1293891 - Problems in transaction BDLS

1250197 - BDLS: Termination with message "Data inconsistency"

Regards

[Former Member · Accepted solution]

Hello Siran

I've check the note

"Use the Note Assistant to implement the correction instructions" does it mean to use Tcode SNOTE to implement to note?

And here i need to 'snote' both the note?

That is all?

Thank you !

Kate

[divyanshu_srivastava3 · Accepted solution]

Hi Kate,

Check if this note is relevant to your release or not ?

Use SNOTE to apply corrections.

Regards

[Former Member · Accepted solution]

Dear Sriram,

First Sorry too fast for mistyping your name.

2nd , even I try now with BDLS , it failed due to <new logical name > already assigned to the client
096

I check the BD54 , I can not delete the entry

BR,

Kate

[divyanshu_srivastava3 · Accepted solution]

Hi Kate,

Is this your current client ?

Can you look in SCC4 for the client logical system name and client permission ?

Regards

[Former Member · Accepted solution]

Hi Div,

yes, they are related .

i could implement in the current 096 client not client 000 right?

BR,

Kate

[Sriram2009 · Accepted solution]

Hi

For that reason I am asked you post system refresh task? kindly refer the link

BR

SS

[divyanshu_srivastava3 · Accepted solution]

Yes you can, however, correction which are cross client and SPs are applied in 000 client.

Regards,

Divyanshu

[divyanshu_srivastava3 · Accepted solution]

Hi Kate,

When you are running in background, a job is started for the same.

Can you check the job logs, because the below error is too generic

 it failed due to <new logical name > already assigned to the client 096

Regards

[Former Member · Accepted solution]

Dear Divi

So i'd better implement them in 000 with user SAP*?

[divyanshu_srivastava3 · Accepted solution]

Why to use sap* ?

[divyanshu_srivastava3 · Accepted solution]

Use any authorised user ID from any client.

[Former Member · Accepted solution]

Dear Div,

here is the error when delete it from BD54

Best regards

K

And Am I have to delete it from SALE (se attached), I think it is too dangerous

Kate

[former_member182657 · Accepted solution]

Hi Kate,

You need to check under trax SCC4 in client 096.Here you'll find it under assigned logical system,just unassigned the same and save the client settings again and try to delete it from BD54.

Hope this will help you.

Regards,

Gaurav

[Former Member · Accepted solution]

Dear Gaurav

It work!

then I run BDLS again.

others told me BDLD should be running for a long time since it changing all the tables

but I go to the sm37 the job RBDLSMAP is "finished" less than one minute(no error this time) and now in sm66 no more BRG job is running , is it strange?

My question: how to check that the BDLS is running or finished correctly?

thank you !

[former_member182657 · Accepted solution]

Hi Kate,

Nice !!.

For your query

how to check that the BDLS is running

kindly refer SCN thread

Regards,

Gaurav

[Former Member · Accepted solution]

Thank You the notes given worked in my case

[former_member182657]

Hi Kate,

Need to check with transaction WE20,try to delete logical system with the mentioned transaction and do the process again.

Regards,

Gaurav

[former_member182657]

Hi Kate,

Kindly check for SCN thread

Hope this will help you.

Regards,

Gaurav

[divyanshu_srivastava3]

Hi Kate,

1st of all, you should change the status of your system from production to quality, as BDLS is not permitted to run in production system.

Logical systems are system/client representation in ALE framework, if you haven't converted them correctly, you should fix them asap.

Read this on how it changes the fields of data types LOGSYS and EDI_PARNUM.

BDLS Performance Problems - ABAP Connectivity - SCN Wiki

Regards

[former_member182657]

Hi Kate,

Could you please check SAP Notes  1293891 - Problems in transaction BDLS

and   1250197 - BDLS: Termination with message "Data inconsistency"

Hope this will help you.

Regards,

Gaurav