cancel
Showing results for 
Search instead for 
Did you mean: 

IDoc type ZSNA056 could not be found

former_member407089
Participant
0 Kudos
2,785

During activation of Source System in BW in RSA1 I get an error:

DIAGNOSIS

"IDoc type ZSNA056 could not be found".

PROCEDURE

"Please enter an IDoc type that exist"

Does anyone know what type of IDoc is this, and how can I generate it? Google doesn't give a solution.

Accepted Solutions (1)

Accepted Solutions (1)

former_member21257
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

To correct the issue:

1) tcode WE30: The type ZSNA056 must exist in BW system.

If it does not exist, create it as a copy of type RSSEND.

2) Afterwards, enter the following in the view maintenance of view

EDIMSG (tcode SM30):

Message type RSSEND, IdocType as specified above, Release

corresponding to the release you are currently using.

3) Please make sure your entries for RSBASIDOC are identical in BW.

Rgds,

Colum

shindead1
Participant
0 Kudos

This helped me as well..

Answers (2)

Answers (2)

former_member407089
Participant
0 Kudos

Thanks Colum Cronin for the suggestion. That really was the solution I was looking for.

emjay
Active Participant
0 Kudos

Hello

Since you have been trying to create connections between BW & R3 multiple times it has created IDOC types in the R3 system. I would do the following steps:

1. Try to delete the connection in BW.

2. Delete Logical Systems in both systems BW & R3 (T-Code SM59)

3. Delete Partner Profiles in both systems BW & R3 (T-Code WE20)

4. Delete Idoc Types created in both systems BW & R3 (T-Code SE11, Table Name RSBASIDOC) - be careful delete only the idoctypes that were created for BW & R3 system combinations.

After completing all the steps above try to recreate the connection and activate the connection.

Hope this helps.

former_member222937
Participant
0 Kudos

Hi P008754 & Colum Cronin,

Even I am also facing same problem "IDOC TYPE ZSD**** could not found etc...u201D.

I have tried your proposed solution for this error.

Now error has been resolved.

Thanks alot...

Regards,

Kshitij R. Deshmukh - K.D.