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
Showing results for 
Search instead for 
Did you mean: 

How to resolve Idoc error status 02

former_member392866
Active Participant
0 Kudos

Hi Experts,

I'm creating extended idoc for MATMAS05 and additionally adding one new segment Z1SEG contains 4 fields.

when i'm trying to generate idoc.. i'm getting error status 02 as below

Segment Z1SEG is unknown in Release 701 /

how to resolve this error.. i searched in SDN also but not getting answer for this type of description error .

Thanks to all..

Regards,

Balaji.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

Please do the following checks:

1.) Whether the segement Z1SEG has been released in WE31.

2.) In the partner profile,please check wthether the extension is maintained.

BR,

Nitin

11 REPLIES 11

david_liu1
Advisor
Advisor
0 Kudos

Hello,

If you want to exchange IDocs between different releases, you should know followings as background:
Data are sent through an RFC-call, by sending all available data in a long string.
For performance reasons the decision has been made, not to search for all segments for the actual length of the release and to delete everything behind, but: the receiver gets the name of the segment version (e.g. E2XXX001) and for this segment version he can know, which fields he is interested in. So all for him not known things can be ignored.
The systems certified for ALE, should know the meaning of segment versions and then only look at the fields, relevant for the given segment version. Exactly the segment version from field SEGNAM will be transmitted, which has been last released for the version, maintained in the partner profile.
The versions are numbered consecutively.
Please read also SAP note: 136629 "EDI/IDoc: Segment release and version".

If you have your own segmentm you can create a new IDoc type. When you do so, you have the option, to make it a successor of your existing type.  It is the same with standard IDoc types, e.g. ORDERS01 - ORDERS05. After creating the successor, you will have to link that new IDoc type
to the message types it is used with in transaction WE81. In general it is not possible, to change a segment definition, which has been created in a previous release.
This concept of the release strategie ensures, that the different releases are compatibel.
You always have to create a new segment definition with a new segment field (with the appropriate length) for your actual release. In the transaction WE20, outbound options, in the field "Seg. release in IDoc type" you can define, which segment release should be used for the

communication.
You can get a more detailed description for this field through the F1-help.
For your own segments the new segment versions can be created in the transaction WE31 : "Segment   > Create with template". If your ZSEGMENT (Z1SEG) isn't released, you must

release this and change the release information (table EDISDEF, field RELEASED) to the
release needed by you.

Regards,

David

Former Member
0 Kudos

Hi,

Please do the following checks:

1.) Whether the segement Z1SEG has been released in WE31.

2.) In the partner profile,please check wthether the extension is maintained.

BR,

Nitin

0 Kudos

Hi Nitin,

1. My custom segment released.

2. In partner profile extentions also maintained .

is there any additional settings to be need like receiver side ?

Regards,

Balaji.

0 Kudos

Hi,

Can you just check your settings in WE82,whether you have maintained the IDOC type,extension and correct version ?

  BR,

Nitin

0 Kudos

Nitin,

As below i maintained extension with 702 release version .

MATMAS - MATMAS05 - Z1MATMASXI - 702

as you said correct version. i maintained as 702 .

Is there any problem with release version ? if yes, how to resolve this conflict ?

Thank you.

Regards,

Balaji.


0 Kudos

Hi Balaji,

Yes the release version is an important field and it should match correctly with your IDOC type version.Otherwise, it will throw error.

BR,

Nitin

0 Kudos

Hi Nitin,

previous in we82

MATMAS - MATMAS05 -              -  470

Now i entered new entry as

MATMAS - MATMAS05 -   Z1MATMASXI01  -  720

I think Hopefully we have to use latest version right ? or can we use old vesion like 470 for new entry? could you please elaborate on this conflict ?

As per you said If i change 720 as 470, is it work(resolve status 02 error)?

Regards,

Balaji.

0 Kudos

Hi Balaji,

The entry in WE82 is version dependent means that the version that you have added for IDOC shall be used for generating IDOC.Hopefully this should resolve your error.If not, I suggest you to set a 'message statement' breakpoint in the FM: Master_IDOC_Distribute and check in the debug , where actually it is throwing this error.

BR,

Nitin

0 Kudos

Hi Balaji,

Could you update the status , whether your issue is resolved or not ?

BR,

Nitin

0 Kudos

Hi Nitin,

Thanks for your all useful information .

we resolved this issue by doing some configuration to message type (this message type is implemented internally only not for global).

Thank you.

Regards,

Balaji.

VijayCR
Active Contributor
0 Kudos

Hi You use the Latest version of which the IDoc is present and check which version your IDES system is.Also Please check all the basic setting of Idoc and Check if any notes have to be implemented.

https://scn.sap.com/thread/791896 Please check if this link is helpful.

Thanks,

Vijay.