Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Model distribution not possible in 4.7

former_member233435
Participant

‎01-26-2015 11:53 AM

0 Kudos

Hello,

We have refreshed QAS client with client copy (data) from PRD system.

Afterwards, we created ALE model (BD64) in QAS and when we try to distribute it to DEV system we get an error:

"Client XXX is not available. Please choose an existing client".

If we create model in DEV, distribution to QAS works, but after finishing model setup, sending idocs from QAS to DEV fails with the same error:

"Client XXX is not available. Please choose an existing client".


In dev_rfc logs we can only see the same message:


**** Trace file opened at 20150126 122009 CET SAP-REL 640,0,155 RFC-VER 3 865711

======> Client XXX is not available. Please choose an existing client

ABAP Programm: SAPLBD22 (Transaction: BD64)

Called function module: MODEL_VIEW_REPLICATE

User: ALEUSER (Client: XXX)

Destination: DEVCLNT100 (handle: 4, 73508497, {54C4E81F-7BD3-051D-E100-0000AC180AF2})

**** Trace file opened at 20150126 123459 CET SAP-REL 640,0,155 RFC-VER 3 865711

======> Client XXX is not available. Please choose an existing client

ABAP Programm: SAPLERFC (Transaction: BD87)

Called function module: ARFC_DEST_SHIP

User: ALEUSER (Client: XXX)

Destination: DEVCLNT100 (handle: 1, 74404664, {54C4E9BD-7BD3-051D-E100-0000AC180AF2})


**** Trace file opened at 20150126 123619 CET SAP-REL 640,0,155 RFC-VER 3 865711

======> Client XXX is not available. Please choose an existing client

ABAP Programm: SAPLARFC (Transaction: BD87)

Called function module: ARFC_DEST_CONFIRM

User: ALEUSER (Client: XXX)

Destination: DEVCLNT100 (handle: 2, , {54C4E9BE-7BD3-051D-E100-0000AC180AF2})


Of course system is defined in SCC4, logical systems are correctly assigned.


Before client copy ALE worked ok.


Any ideas how to correct this error?


Best regards,

Sasha

2 REPLIES 2

raymond_giuseppi
Active Contributor

‎01-26-2015 12:00 PM

0 Kudos

Did you check for BDLS (logical system, execute conversion) as well as SM59 (RFC, check connections, client, user/pwd) ?

Regards,

Raymond

former_member233435
Participant
In response to raymond_giuseppi

‎01-26-2015 2:08 PM

0 Kudos

Hi Raymond,

All is well in SM59.

Since we copied data only during client copy this conversion should have been already made during that process as is written in BDLSS. We did copy client from PRD to QAS before and we did not need to run BDLSS for ALE to run ok.

Could BDLSS resolve this?

Regards,

Sasha