Skip to Content

IDOC execution would be always a challenging tasks for the beginners. Here I tried to explain the various IDOCs in SAP POSDM with their mandatory segments for successful execution.

Segments mentioned as per their structure order and RED are the mandatory ones. We must have valid data for the RED segments, for executing the IDOC.

WPUBON                       POS interface: Upload sales docs (receipts) non-aggregated

       E1WPB01                        POS interface, upload sales docs header data

           E1WPB02                        POS interface, inbound processing sales docs items

               E1WPB03                        POs interface, inbound processing sales docs conditions item

               E1WPB04                        POS interface, inbound processing sales docs tax item

               E1WXX01 Segment for Customer Enhancements to be used as required

           E1WPB05                        POS interface: inbound proc.sales docs, header, and conditions

           E1WPB07                        POS interface: inbound processing sales docs tax segment

           E1WPB06                        POS Interface, Upload Sales Documents Tender Type

 

WPUUMS                       POS interface: Upload sales data (compressed)

        E1WPU01                        POS interface: inbound sales, header segment

            E1WPU02                        POS interface, inbound sales, items

                E1WPU03                        POS interface, inbound sales discounts

                E1WPU04                        POS interface, inbound sales, item taxes

                E1WPU05                        POS interface: inbound sales item taxes (values)

                E1WXX01 Segment for Customer Enhancements to be used as required

WPUTAB                       POS interface: Upload day-end closing POS

        E1WPZ01                        POS interface: inbound day-end closing, header segment

            E1WPZ02                        POS interface: inbound payment list item

                E1WXX01 Segment for Customer Enhancements to be used as required

WPUFIB                       POS interface: Upload Fin.Acc. Interface SRS/POS

        E1WPF01                        POS interface: inbound proc. acc. doc. header segment

            E1WPF02                        POS interface, accounting document upload, item segment

                E1WXX01 Segment for Customer Enhancements to be used as required

WPUWBW                       POS interface: Upload goods movements

        E1WPG01                        POS interface, inbound, goods movements, header segment

            E1WPG02                        POS interface, upload goods movements, items

                E1WXX01 Segment for Customer Enhancements to be used as required

Hope this will the beginners in POSDM.

Please share your comments if you like to add more on this.

Thanks,

Venkatesan.

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Evans Kang

    Dear Venkatesan,

    I’ve create test data from POSDM TCode MAN0, include sales items, discounts, taxes and Customer Enhancements data, after I maintain these data, I execute standard task 0014 create WPUUMS idoc, it always creates Segments : E1WPU01, E1WPU02, Segment E1WPU03 – E1WPU05 and E1WXX01 nerver shows, how can I create Segment E1WPU03 – E1WPU05 and E1WXX01 when I execute standard task 0014?

    best regards,

    Evans.

    (0) 
    1. Venkatesan Balakrishnan Post author

      Hi Evans,

      E1WPU03, 04 & 05 – are related to sale Item level discount and tax records.

      If you have created Transaction level discount/tax, there are chances of missing the segments. Please try test by adding item level data.


      If you still missing the segments, then you have to check the configuration under “PIPE->POS Transactions”


      Thanks,

      Venkatesan.

      (0) 
      1. Evans Kang

        Hi Venkatesan,

        I ‘ve try to config POS Transation, but nothing happened! and I ‘ve debug when I execute standard task 0014 – create WPUUMS IDoc, I don’t why the structure “Discount” & “Tax” in the it_transaction have no any data, at the same time I check the standard task 0010-Create WPUBON IDoc, the structure “Discount” & “Tax” in the it_transaction have data, how do I solve this issue?

        when I executed task 0014, the POSDM will call this METHOD, and the table already have no any Discount & Tax data in the structure!

        METHOD /posdw/if_ex_task~call .

           CALL FUNCTION ‘/POSDW/IDOC_OUTPUT_WPUUMS’

             EXPORTING

               ir_parameters   = ir_parameters

             IMPORTING

               er_after_commit = er_after_commit

             TABLES

               it_transactions = it_transaction

               et_message      = et_message

               et_objectlink   = et_objectlink.

        ENDMETHOD.

        (0) 
        1. Venkatesan Balakrishnan Post author

          Hi Evans,

          PIPE –> POS Transactions –> Define discount types –> Select your defined discount type –> Check what you have assigned ‘Incl/Excl Task Grp’ under ‘Task processing’ tab (It should be 0010 or 0001).

          Ensure that same has been assigned with WPUUMS through ‘Assign Task to Task Group’

          Please try and let me know if this helps.

          Thanks,

          Venkatesan

          (0) 
  2. Siva sankar Yarra

    Hi Venkatesan,

    Would like to know How to map SAP ECC WPUUMS idoc to POSDM trasnaction number.

    In my retail project we are SAP POSDM to receive the sales transactions from POS, once transactions are posted to POSDM using PI, then using PIPE dispatcher IDocs sales transactions will be posted to SAP ECC. So once sales idocs posted to ECC, would like to know how to map idoc to pos trasnaction number.

    (0) 

Leave a Reply