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

Payext Idocs Issue - E1IDPU1

Former Member
0 Likes
1,497

Hi,

I am an Idoc novice, but stumbling around trying to find my way. I have configured my system (ECC6.0), to send payments to our group IHC, however I have an anomoly that I cannot figure out.

It seems to refer to reference details (BKREF) in the master data (but i may be following a red herring). If I pay a vendor with this field populated I have an idoc that works and E1IDPU1 has a hierarchical structure, however, if I pay a customer, E1IDPU1 is not structured in the same way and the child segments follow immediately, so my idoc fails, with status 26

Can anyone advise areas that I need to look at to troubleshoot, as I am at a loss where to look.

Any help would be greatly appreciated.

Thanks

Jackie

Hi,

I am an Idoc novice, but stumbling around trying to find my way. I have configured my system (ECC6.0), to send payments to our group IHC, however I have an anomoly that I cannot figure out.

It seems to refer to reference details (BKREF) in the master data (but i may be following a red herring). If I pay a vendor with this field populated I have an idoc that works and E1IDPU1 has a hierarchical structure, however, if I pay a customer, E1IDPU1 is not structured in the same way and the child segments follow immediately, so my idoc fails, with status 26

Can anyone advise areas that I need to look at to troubleshoot, as I am at a loss where to look.

Any help would be greatly appreciated.

Thanks

Jackie

5 REPLIES 5
Read only

Jelena_Perfiljeva
Active Contributor
0 Likes
1,193

What IDoc type are you using?

Read only

0 Likes
1,193

Jelena,

I am using PEXR2002 - PAYEXT. I have had some help from another forum, that has shown that it is not BKREF that is causing the issue, so I am currently trawling through RFFOEDI to see at what point the idoc is populated to see if I can debug from there - slow progress!!

Regards

Jackie

Read only

Jelena_Perfiljeva
Active Contributor
0 Likes
1,193

I found your post on another forum. It seems that you're just using a standard IDoc/Message without any enhancements. All things considered, I would recommend sending a message to SAP. They should be able to figure it out and at least provide some kind of explanation.

Also in WE05 you should see a more detailed message under the status and the segment in error should be marked in red. If you have not already done so, you might want to check if there are more details available.

Read only

0 Likes
1,193

Hi,

I have checked WE05 already, and that doesn't give me any more information.

Regards

Jackie

Read only

0 Likes
1,193

Hi Jackie,

The issue decription, idoc status 26 and sub-segments not aligned, suggest that the IDoc failed due to syntax error. Standard code doesnt cause any syntax error in forming the segments of the idoc.

Here syntax error with the Idoc means that the structure of the Idoc was not according to the standard. This happens wheenever there is a user exit implemented to append a segment or sub segment to the idoc structure.

My suggestion would be to check for any user exit implementation and see if there is any incorrect coding that modifies the idoc structure. The exact segment which causes this syntax error would be mentioned in the status log of the idoc.

Hope this helps!

Best regards,

Sidhartha