cancel
Showing results for 
Search instead for 
Did you mean: 

Customized IDOC Issue

Former Member
0 Kudos

Hi,

Upto now we worked on standard IDOC's. so no issues upto now.

Now we are dealing with the customized idoc's. we have one standard idoc in R/3 200 client an we customized that idoc according to our requirement.

Now we transfered and released that IDOC from 200 client to 300 client for XI use.

When we are trying to Import the IDOC into IR we are unable to see that Z IDOC( Customized) in the IDOC list.

We have provided the SAP R/3 300 client user logon details only.

What may be the Issue

Regards

Suman

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Suman,

Did you complete the settings in WE82 where in you need to assign Idoc type to message type?

Also when you complete defining the IDoc in WE30, there is a menu transaction where in you check for the problems (Development Object >> Check)

Regards,

Suraj Kumar.

Former Member
0 Kudos

Hi Suraj,

When I check in WE30 of my 300 client. this is the status

Check extension ZWMMBID02

Extension ZWMMBID02 exists

Extension ZWMMBID02 is released

Extension ZWMMBID02 is not linked with any logical message

No predecessors exist

Extension ZWMMBID02 is assigned to basic type WMMBID02

Check segment Z1MBXYH

Segment Z1MBXYH consistent

Check segment Z1MBXYI

Segment Z1MBXYI consistent

Check segment Z1SERNR

Segment Z1SERNR consistent

Check segment Z1MBXYJ

Segment Z1MBXYJ consistent

What it is saying

Former Member
0 Kudos

Hi Suman,

Extension ZWMMBID02 is not linked with any logical message

No predecessors exist

This means that you did not assign any message type to extended idoc type in WE82. You need to complete the settings and once again check until everything is consistent.

Because when Idoc is imported into XI, it is recognized as <message type>.<idoctype>.

Normally when you find the answer is helpful, you need to reward it as helpful and again ask another question. This is how it goes.

Regards,

Suraj Kumar.

Former Member
0 Kudos

HI Suman,

Please goto tcode WE82--->Check if the Message Type is assigned to the IDOC type created in WE30.

The above log that idicates that you have properly created the IDOC type now you have to assign it to Message Type in WE82.

Please refer below link for all IDOC configuration..refer if you have missed any link

idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133

IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario

Thanks

swarup

Former Member
0 Kudos

Hi Suman,

Go through this link.

[Step by Step of Enhancement of IDoc Type|http://saptechnical.com/Tutorials/ALE/IDOCExtension/IDOCExtension.htm]

Regards,

Suraj Kumar

Former Member
0 Kudos

Hi,

Thank you suraj

Regards

Suman

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

You need to add Mesage Type to the Extended IDoc.

Add message Type to the Extended IDoc in Transaction WE82.

Please follow steps in Transaction WEDI to extended the IDoc.

In WEDI Transaction --> Go to DEVELOPMENT

and follow all the below steps:

IDOC Segemnts -- WE31

IDOC Types -


WE30

Message Types -


WE81

IDOCType/Message Types --- WE82

For Outbound Processing

Create Process Code --- WE41

For Inbound Processing

Register Function Module --- BD51

Assign Function Module,Message Type to IDOC Type -- WE57

Create Inbound Process Code --- WE42.

Please follow above mentioned Steps.

Now IDOC will be available in XI to import.

Thanks,

Kishore.

prateek
Active Contributor
0 Kudos

Make sure that the custom segments are released properly.

Try deleting the existing metadata from idx2 and regeneratet the metadata.

Regards,

Prateek

Former Member
0 Kudos

Hi,

In IDX2 also we are unable to see the Z IDOC

Regards

Suman

Former Member
0 Kudos

then check all objects are released and maintained in we82, we30.

BR,

Alok

prateek
Active Contributor
0 Kudos

Try to load it manually in idx2, and see wht error occurs.

Regards,

Prateek