Issue with outbound IDoc PEXR2003/PEXR2001 Missing segment and Unable to debug.

[akshayrajkumar]

Hi everyone,

I am currently facing an issue wherein the outbound IDOC of Base Type PEXR2003, We have a segment E1IDUU2 needs to be filled. But The parent segment E1IDPU3 and E1IDPU1 is not getting filled either. When we tried to debug the IDocs in the usual way when the payment is processed from F110 t-code, it doesn't trigger any of the ABAP breakpoints and after a lot of research, I understand that FI Idocs can't be triggered in the same way where SD and MM IDocs are triggered. Since all the blogs that I searched were almost two decades ago, I wanted to see if anyone has solution for my following queries.

I have couple questions.

1. How to trigger the FI IDoc to debug?

2. The idoc is standard without any customization in User Exits (Checked already), from which table does the E1IDPU3 additional sub item data is mapped from or do we need enhancement to fill these fields?

Thanks in advance!

[Sandra_Rossi]

The important question: did you use all the possible debug modes? (update task, user/external breakpoint instead of session breakpoints)

NB: the segment E1IDUU2 of the IDoc type PEXR2003:

[akshayrajkumar]

@Sandra_Rossi

Yes. I have tried all those. Still the debugger didnt trigger.

[Ryan-Crosby]

Several segments are filled using user-exit functions and whether anything is executed is controlled by entries in table 'FEDICUS' (FI EDI Control for Calling Customer Functions per Segment).

Regards,

Ryan Crosby

[akshayrajkumar]

No. No User Exits are implemented yet, atlease the exits related to this segment. So this is a complete standard idoc

[Ryan-Crosby]

@akshayrajkumar that wasn't a question, it was a statement. Several of the segments are only filled by implementing user-exits based on control entries defined in the table 'FEDICUS'.

[akshayrajkumar]

@Ryan-Crosby Ya got it! Let me check.