idoc not reaching TST from DEV

[Former Member]

Hi,

We want to transport variant config characteristics from DEV to TST. We are using SAP provided transaction BD91 to select a given characteristic and giving the destination logical system TSTCLNT100. In WE05 I can see that the idoc was sent successfully to the destination port. But in SM58 in DEV i get the following error "No authorization to send idocs with message type CHRMAS".

In the receiving system I do not see anything. I checked BDM2 in DEValso, the receiver idoc is 000000000. I checked the authorizations in SU53, but everything is fine.

Can anyone tell me what is the issue.

Also I would like to know if the config in WE20 is correct. In source(DEV) system for logical system TSTCLNT100 the outbound message type is CHRMAS while in destination system(TST) for logical system TSTCLNT100 the inbound msg type is CHRMAS.

Do I need to do anything for DV2CLNT100 logical system in WE20 in DEV or TST. Anything need to be done in BD64. These systems already exists since many years, so we have not generated any partner profiles thru BD64.

Thnx in advance

[Former Member]

Hi,

We want to transport variant config characteristics from DEV to TST. We are using SAP provided transaction BD91 to select a given characteristic and giving the destination logical system TSTCLNT100. In WE05 I can see that the idoc was sent successfully to the destination port. But in SM58 in DEV i get the following error "No authorization to send idocs with message type CHRMAS".

In the receiving system I do not see anything. I checked BDM2 in DEValso, the receiver idoc is 000000000. I checked the authorizations in SU53, but everything is fine.

Can anyone tell me what is the issue.

Also I would like to know if the config in WE20 is correct. In source(DEV) system for logical system TSTCLNT100 the outbound message type is CHRMAS while in destination system(TST) for logical system TSTCLNT100 the inbound msg type is CHRMAS.

Do I need to do anything for DV2CLNT100 logical system in WE20 in DEV or TST. Anything need to be done in BD64. These systems already exists since many years, so we have not generated any partner profiles thru BD64.

Thnx in advance

[Former Member]

Hi,

try giving temporary SAP_ALL to the user you use for the RFC destination in the target system.

By the way you see the message in WE05 in status 03 that means the idoc is not successfuly delivered but just passed to the idoc port. When an idoc is succesfully delivered you will see in status 12 (after running the report RBDMOIND).

Yor configuration looks ok just in WE20 of the target system (TST) you have to define under the logical system of the sender (DV2) the idoc as inbound and not under the target logical system (TST).

Kind Regards,

Sergio

[Former Member]

Hi,

I already have SAP_ALL authorization for me and the user executing BD91.

I have the CHRMAS message type in inbound params in DV2 logical system as well as TST logical system, just being on the safe side, but still nothing works

You are correct, the status is not 12, but even i execute the report RBDMOIND in DV2, it says 43 in trfc queue, which are the ones erroring out.

I have put up a question to SAP, but i doubt they will give any answer.

[Former Member]

Hi Pulin,

sorry, not sure I got you but have you tried givin the user that is defined in the RFC destination in SM59 (not the user who run the transaction) must have SAP_ALL ?

Regarrds,

Sergio

[Former Member]

Hi,

I am using my own user id and password in SM59, as I have SAP_ALL acess and also I can login to TST with my uid.

I have posted this issue to SAP, may be they might give an answer.