Application Development 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: 

A question about IDOC field in PO outbound

Former Member
0 Kudos

Hello Expert,

In one SAP system, when user creates one PO, the system will send out one IDOC. the IDOC message type is ORDERS and basic type is ORDERS05.

In the WE02, I find the E1EDK05-KRATE is 3.0.

I want to know, is the mapping between IDOC field and Po data preconfigured, or hard-coded in the system by coding?

If it's preconfigured, where can I find the mapping between IDOC and PO?

Thanks,

Best Regards, Johnny

1 ACCEPTED SOLUTION

Former Member
0 Kudos

E1EDK05 segment contains header pricing conditions from the PO.

The outbound ORDERS IDoc is created from PO output by standard EDI function IDOC_OUTPUT_ORDERS

You can find how E1EDK05-KRATE is mapped from following the path

SE37 -> IDOC_OUTPU_ORDERS -> perform fuellen_idoc_inttab. -> perform fill_header_cond. -> perform fill_e1edk05.

Here you can see that E1EDK05-KRATE is mapped from header condition rate field tkomvd-kbetr

If you open the related PO in ME23N, you will see that IDoc contains an E1EDK05 segment for each pricing condition type that you find in ME23N Header -> Conditions screen

1 REPLY 1

Former Member
0 Kudos

E1EDK05 segment contains header pricing conditions from the PO.

The outbound ORDERS IDoc is created from PO output by standard EDI function IDOC_OUTPUT_ORDERS

You can find how E1EDK05-KRATE is mapped from following the path

SE37 -> IDOC_OUTPU_ORDERS -> perform fuellen_idoc_inttab. -> perform fill_header_cond. -> perform fill_e1edk05.

Here you can see that E1EDK05-KRATE is mapped from header condition rate field tkomvd-kbetr

If you open the related PO in ME23N, you will see that IDoc contains an E1EDK05 segment for each pricing condition type that you find in ME23N Header -> Conditions screen