Application Development and Automation 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: 
Read only

regarading IDOC status 26 ,syntax error

Former Member
0 Likes
5,968

Hi All,

we have some problem to create IDOC type ORDERS05 for Purchase Order.

*ERROR STATUS 26:*

(SYNTAX ERROR IN IDOC (SEGMENT CANT B IDENTIFIED))

msg number E0078:

The segment E1EDK14 does not occur at the current level of the basic type ORDERS05 (extension ) AND

e1edk14 segment missed.instead of 5 ,it shows only 4.

*ERROR STATUS 26:*

(SYNTAX ERROR IN IDOC (MANDATORY DATA MISSING))

msg E0072:The segment E1EDK01 has the attribute 'Mandatory' in the syntax description of the basic type ORDERS05 (customer enhancement ).

header data was totally different.

it contains street fields,n country ,,like dat,instead of document number

However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.

This happens for order create (ORDERS) and for order change (ORDCHG)

Do you have any idea to solve the problem? I'm using a standard IDOC.

1 ACCEPTED SOLUTION
Read only

paruchuri_nagesh
Active Contributor
0 Likes
3,384

hi

Usually posting program contains your logic which exists in process code this process code contain function module nothing but posting program

and also

check whether u r using

1) sap standard program

2) user defined program

3) enhancing sap program using user exits

if it is standard program check all ur ALE settings once again

if ur using user defined check ur program logic and compare it with idoc structure

if ur enhancing sap standard program check partner profiles using correct message & idoc type

check your user exit logic

reward if u find helpful

Thanks&Regards

Nagesh.Paruchuri

Hi All,

we have some problem to create IDOC type ORDERS05 for Purchase Order.

*ERROR STATUS 26:*

(SYNTAX ERROR IN IDOC (SEGMENT CANT B IDENTIFIED))

msg number E0078:

The segment E1EDK14 does not occur at the current level of the basic type ORDERS05 (extension ) AND

e1edk14 segment missed.instead of 5 ,it shows only 4.

*ERROR STATUS 26:*

(SYNTAX ERROR IN IDOC (MANDATORY DATA MISSING))

msg E0072:The segment E1EDK01 has the attribute 'Mandatory' in the syntax description of the basic type ORDERS05 (customer enhancement ).

header data was totally different.

it contains street fields,n country ,,like dat,instead of document number

However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.

This happens for order create (ORDERS) and for order change (ORDCHG)

Do you have any idea to solve the problem? I'm using a standard IDOC.

6 REPLIES 6
Read only

Former Member
0 Likes
3,384

Hi,

here we have some standard programs to rectify this syntax errors.

go to se38

give standard program RSEOUT00 go for execute,

give idoc number and basic type(message typ) and then execute.

then your syntax error will rectify and the idoc gets a status code of 03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK

Regards.

swami.

Read only

Former Member
0 Likes
3,384

Satya,

1. In tcode WE31-->enter the segment name E1EDK14 --> Display

check whether it is get released or not.

2.E1EDK01 is mandatory segment you might have not entered required detaisl to this segemnt in aplication

Read only

0 Likes
3,384

hi murali krishan,

e1edk14 released.

wenever v create PO and then save.

it triggers idoc automatically.

so u hav clear idea.

now giv me solution plz.

Read only

0 Likes
3,384

Murali,

As the E1EDK14 segment is a SAP standard so no need to check it is released or not. Obviously it will be released.

Regards,

Santosh

Read only

paruchuri_nagesh
Active Contributor
0 Likes
3,385

hi

Usually posting program contains your logic which exists in process code this process code contain function module nothing but posting program

and also

check whether u r using

1) sap standard program

2) user defined program

3) enhancing sap program using user exits

if it is standard program check all ur ALE settings once again

if ur using user defined check ur program logic and compare it with idoc structure

if ur enhancing sap standard program check partner profiles using correct message & idoc type

check your user exit logic

reward if u find helpful

Thanks&Regards

Nagesh.Paruchuri

Read only

Former Member
0 Likes
3,384

Hi Satya,

1. For the second error jst try to trigger the Idoc once again from the transaction WE19 filling all the missing values in the E1EDK01 segment.

2. For the first error i am not sure why it is cmng. coz the segment E1EDK14 is not an mandatory segment. If u pass the values or not pass the values to the segment it must not affect the idoc.

Anyway jst try the first metod and let me know what is the result.

Regards,

Santosh