‎2007 Mar 16 11:03 AM
Hi Experts,
When i am triggering the Idoc through the program i'm getting Idoc Status = 26 : Error during syntax check. This error i'm getting both in the outbound and inbound.
Is it nessasary to release the custom segments before we trigger the idoc??
Plz guide me what steps to be taken to clear the above error.
Thnks
Santosh
‎2007 Mar 16 11:07 AM
Good, there is a problem while filling idoc segments.
Have a look at the idoc structure in WE30 and see whether
1) the mandatory segments are filleds
2) repitative logic is filled, ( if a segment allowed for max 2 times, it should not be filled with more than 2)
etc....
Cheers
Manohar
‎2007 Mar 16 11:07 AM
Good, there is a problem while filling idoc segments.
Have a look at the idoc structure in WE30 and see whether
1) the mandatory segments are filleds
2) repitative logic is filled, ( if a segment allowed for max 2 times, it should not be filled with more than 2)
etc....
Cheers
Manohar
‎2007 Mar 16 11:07 AM
Hi,
It's a must to release the SEGMENTs FIRST and then the IDOC Type .
Do and check.
Regards,
Anji
‎2007 Mar 19 8:46 PM
If you're using a custom segment that is not released the syntax check will fail always, release your custimization.
‎2007 Mar 19 9:07 PM
Hi,
Status - 26 stands for IDoc structure error.
If an IDoc in the IDoc queue has the above status, the entries are transmitted to the external system. If it has any other status, a transactional RFC is sent. It is not enough to check only the IDoc Queue because although an IDoc may have been created correctly, a problem could have occurred during transmission. Transmission problems are checked in table TRFC Queue
It is NOT mandatory for custom segment to release.
The release mechanism is for in order to be able to create a new successor, you must have released the predecessor. The object cannot be changed again after being released. The release can be canceled if no successors for the development object have been created.
Segment definitions which have NOT been released are assigned the default value "000" as a version number.
aRs