Message 'can only work in client 001 during data transfer

[Former Member]

Hello Experts,

Recently I setup a interface between ECC and SCM system for EWM, my data transfer was working fine until last couple of days when I getting this error message on the SCM side.

Message in CFM2 comes up as

Function/Q/SAPAPO/CIF_LOC_INBOUND

Text: You can only work in client 001

And not sure why because I have not made any changes to settings.

Can someone please suggest what might be going wrong and what needs to be done?

Thanks

Bhaskar

[Former Member]

Issue resolved using OSS Note-Note 1507802 - Error message BRAIN009 during CIF

[Former Member]

Hello,

I Used the OSS note Note 1498542 - CIF returns error message BRAIN009 to resolve the issue.

The main note-Note 1507802 - Error message BRAIN009 during CIF this should help.

Thanks and regards,

Bhaskar Mandal

[frank_horlacher]

I think this is in conjunction with the BW client.

please see note 522569 ´to solve the issue.

[Former Member]

Hi Pawan,

Thanks for your response.

However this does not address the issue, because I checkd all the client settings and LS assignments, all points to 100 client.

I looked at the tcode-/n/sapapo/cq and both my ECC and SCM systems are listed, however the connection for the ECC system ilooks like disconnected.

Can you suggest where else I could look for and try to resolve this issue?

Thanks

Bhaskar

[former_member209769]

Hi Bhaskar,

If CQ shows that you R/3 system's connectivity is broken, then ask your Basis team to correct the same.

Check out the outbound queues in APO and in R/3 (in T-code SMQ1). You should most likely be seeing that there are stuck queues in outbound on both the sides (I would assume that you must be having some regular data transfers).

Try to activate the queues, you would see an error message that might be helpful in resolving the issue.

Your Basis team needs to check the RFC connection in SM59, and then see whether the password of RFC user needed to be reset/unlocked, or something else (there could be multiple scenarios). If this part is ok, then we would need to check more things, but first let me know the result for this check.

Thanks - Pawan

[former_member209769]

Hi Bhaskar,

I have not worked on EWM, and don't know if CIF connectivity is used differently.

But let me try to propose a general way forward based on your error message.

It seems that your CIF data is trying to reach a client where you are not authorized to work, or where CIF settings are not maintained properly.

Should be linked to RFC connectivity between R/3 and APO (unless it's due to some SAP bug).

Check out the following:

1) Which APO client is your CIF model pointing to? You would most likely be able to find this out by seeing the name of "logical system" for your CIF Integration Model (IM). It seems the CIF IM is pointing to some client which is something other than client 001.

Also, my guess would be that this client that you maintained in CIF IM is no longer having settings relevant for CIF, or something else.

2) Go to your APO system, and again cross-check which client you are using. Next go to /n/sapapo/cq and see which R/3 systems are having active connections to your APO system. The "logical system" corresponding to your R/3 system/client should be there in the list. if not, ask your Basis team if they made any changes recently.

PS: I would assume that you should get this same error for CIF of any object, not only material (unless the corresponding IM points to a different client in APO).

Let me know the results of your checks, and if this helps you in finding out the root cause.

PS: Logical system normally would have a naming convention like <System name>CL<Client>. e.g. PR1CL310. Here PR1 is system name and client is 310.

Thanks - Pawan