EDI: Syntax error in IDoc (segment cannot be identified)

[Former Member]

Hi,

We added custom segments to an IDoc and we can see that Idoc segments are correctly populated. However, at we02 we can see that idoc structure isn't ok, and it retrieves the following sintax error:

EDI: Syntax error in IDoc (segment cannot be identified)

Do you guys know where could be the problem?

Thanks,

Luí

[Former Member]

Is the name of extension for the IDOC type present in the control record of the IDOC generated...?

Thanks,

Renjith

[former_member188685]

Hi,

after adding those segments you need to release it.

check it menu you can see the release option, you need to release it.

then only it will work.

regards

vijay

[former_member188685]

Hi,

if you are not released the newly created one's then do it.

in the menu edit-> set release

click on it and release.

then try.

regards

vijay

[Former Member]

Hi,

we already checked the control record and also if the segment are released. Everything seems ok.

So, do you guys know more possible reasons?

Thanks,

[Former Member]

is the custom segment that is populated attached to the correct parent node ??

also make sure that there are no missing required segments...

Thanks,

Renjith.

[Former Member]

Hi,

It's really weird. The custom segment is well populated, and correctly attached to parent node.

The parent node is the only mandatory idoc segment.

Do you have more configurations to check?

Thanks,

Luis

[Former Member]

Hi,

At EDID4 with SE16 I can see that Hierarchy level is not ok, is defined as 0 (zero).

Howeve, when we do a segment display at WE30, the Hierarchy level is ok, is defined as 3.

Do you guys know what is the issue?

Thanks,

Luí

[Former Member]

Hi Luis,

When populating the custom segment, are you making sure that the value for PSGNUM(for the custom segment) is the SEGNUM of its correct parent node ?

Thanks,

Renjith.

[Former Member]

Hi,

At EDID4 with SE16 I can see that Hierarchy level is not ok, is defined as 0 (zero). Also, the PSGNUM is different than SEGNUM of correct parent node.

Do you guys know where I can configure it?

Thanks,

Luí

[Former Member]

How is the custom segment data populated ?

Is it an outbound IDOC and the custom segment is populated using an exit ?

then the logic needs to put there....

If it is an inbound idoc..then whoever is generating the idoc should take care of populating these meatadata related to the segments correctly...

Thanks,

Renjith

[Former Member]

Hi,

We created a Z report to populate the custom segment.

Also, we checked that CIMSYN table don't have the field HLEVEL and the field PARPNO well configurated.

Should we change this configuratiosn at CIMSYN table?

Thanks,

Luí

[Former Member]

Hi Luis,

The entry in the CIMSYN gets created, when the extension is created from WE30.

So if you feel that it is incorrect, you can delete and recreate the extension from WE30.

could you write the code which fills the custom segment ?

Thanks,

Renjith.

[Former Member]

Hi,

Did you check the partner profile settings.

Did you explicitly mention any version number there?.

Did you mention the correct message type?.

Did you mention the extended IDOC type there.

Please let me know if i can help you out further.

Thank you.

regards,

karun M

[Former Member]

Hi,

We solved the issue right now.

The problem was on the function that populate the idoc. It populated the segment in a diferent segment order than the IDoc structure defined.

Thank you very much guys, I really appreciated!

Thanks,

Luí

[Former Member]

Hello All,

I also had the same problem. I would just like to know what do the following statements mean?

1. The segment Z1EDP03 is assigned to a group whose header segment does not occur.

2. The segment Z1EDP03 does not exist in the syntax description of the basic type INVOIC01 (extension Z2FININVOIC01X001).

3. The sequence of segments in the group in which the segment appears is incorrect.

For now, I can't still figure out the cause of the error.

I am looking forward to your answers.

Thank you.

-Baron-