ORDERS05 IDOC to pass order type RE

Hello All,
We want to receive EDI 180 returns document from our warehouse. I figure I'll map the EDI document to ORDERS05. I need to pass order type RE to create the returns order in VA01. Where in the IDOC do I put the RE?
Thank you.
Farhaud

Dear Farhaud,
E1EDK01 (Document header general data)
BSART (Document type)
You can get more details from transaction WE60 -> Basic type: ORDERS05
I hope this helps.
Best regards,
Ian Kehoe

Similar Messages

  • How can i pass the  segments and fields to the ORDERS05 IDOC

    Hi All,
    I want to use ORDERS05 Idoc type for creating sales order. How can I pass the order type, sales org., distr. channel, division, sold-to-party, material and quantity to the Idoc?
    please help me out in this.
    thanks in advance
    jasmine

    Hi,
    Goto WE19 TC and there select your IDOC and there u can pass the data.
    Regards,
    Phani

  • Creating a Purchase Order using ORDERS05 Idoc

    Hi Experts,
    I need to create a purchase order using ORDERS05 Idoc, with the data I am using a sales order is gettig created but I need to create a PO insted of SO.
    Please let me know what is difference between a PO and SO while using ORDERS05. Also please let me know what are all the fields that needs to chaged in the Idoc.
    Thanks,
    Suma

    Hi,
       I'm looking at a similar problem, can we use ORDERS05 IDOC basic type to create a Purchase Order?
       What is the inbound processing FM?  I tried IDOC_INPUT_ORDRSP, but it seem to only allow changes to a PO, and not creation of a PO.
       For IDOC_INPUT_ORDERS FM this one seem to only create Sales Orders?
       Which inbound FM should i be using?
    Regards.

  • Generating idoc for Purchase orders - ORDERS05

    Hi,
    Can you please let me know how to generate idoc for Purchase orders - ORDERS05-manually, not by activating change pointers.

    hi
    i believe u wont have this functionality as it is a transcational data and the one way of doing it by configuring output types only.

  • Passing values to outbound ORDERS05 idoc.

    Hi,
    I have to do an enhancement wherein whenever a PO is created and sent through EDI an outbound idoc will be created which will contain some additional data in some segemnts.For e.g. I have to fill stras, ort01 and pstlz fields of segment  E1EDPA1 from KNA1 where lifnr value is equal to the lifnr in PO.
    How do I pass the values to the segment and append it to the idoc data?
    Need help urgently!!
    Thanks,
    Sandeep.

    Hi,
    Check the code below:
    FUNCTION ..........
    Checking the Purchase Order types
      PERFORM fill_bsart.
    Selecting the data and putting it into the final internal table.
      PERFORM fill_final.
    Checking the case inorder to populate the data in the new segments
      CASE int_edidd-segnam.
        WHEN gc_e1edk01.
        Populate Header segment
          PERFORM f_populate_header.
        WHEN gc_e1edp01.
        Populate Item segment
          PERFORM f_populate_item.
      ENDCASE.
    ENDFUNCTION.
    FORM f_populate_header .
      CLEAR: gv_e1edk01, gv_hsegment.
      MOVE int_edidd-sdata TO gv_e1edk01.
      MOVE : gv_e1edk01-belnr TO gv_hsegment-purchase_order,
             gv_e1edk01-bsart TO gv_hsegment-order_type.
      CLEAR: gs_final.
    Reading the final internal table with Index 1 and moving the data to int_edidd
      READ TABLE gt_final INTO gs_final INDEX 1.
      IF sy-subrc EQ 0.
        MOVE: gs_final-eknam TO gv_hsegment-eknam.
        MOVE: gs_final-stras TO gv_hsegment-street,
              gs_final-netwr TO gv_hsegment-netwr,
              gs_final-oknam TO gv_hsegment-po_approver.
        MOVE: gv_hsegment TO int_edidd-sdata,
              gc_hseg TO int_edidd-segnam.
        APPEND int_edidd TO int_edidd.
        CLEAR int_edidd.
        CLEAR : gs_final.
      ENDIF.
    ENDFORM.                    " f_populate_header
    FORM f_populate_item .
      CLEAR: gv_isegment,gs_final.
      MOVE int_edidd-sdata TO gv_e1edp01.
    Reading the final internal table with key ebelp and moving the data to int_edidd
      READ TABLE gt_final INTO gs_final WITH KEY ebelp = gv_e1edp01-posex.
      IF sy-subrc EQ 0.
        MOVE: gs_final-bsart TO gv_isegment-order_type,
              gs_final-eindt TO gv_isegment-eeind,
              gs_final-ebelp TO gv_isegment-ebelp,
              gs_final-ean11 TO gv_isegment-ean11,
              gs_final-numtp TO gv_isegment-numtp,
              gs_final-txz01 TO gv_isegment-txz01,
              gs_final-meins TO gv_isegment-meins,
              gs_final-idnlf TO gv_isegment-idnlf.
        MOVE: gv_isegment TO int_edidd-sdata,
              gc_iseg     TO int_edidd-segnam.
        APPEND int_edidd TO int_edidd.
        CLEAR int_edidd.
      ENDIF.
    ENDFORM.                    " f_populate_item
    FORM fill_bsart .
      CONSTANTS: lc_i TYPE c  VALUE 'I',
                 lc_eq TYPE char2 VALUE 'EQ',
                 lc_ylro TYPE char4 VALUE 'ylro',
                 lc_yspo TYPE char4 VALUE 'yspo',
                 lc_ylso TYPE char4 VALUE 'ylso',
                 lc_ysub TYPE char4 VALUE 'ysub',
                 lc_yvwh TYPE char4 VALUE 'yvwh'.
      CLEAR: gt_bsart.
      gt_bsart_line-sign = lc_i.
      gt_bsart_line-option = lc_eq.
      gt_bsart_line-low = lc_ylro.
      APPEND gt_bsart_line TO gt_bsart.
      CLEAR :gt_bsart_line.
      gt_bsart_line-sign = lc_i.
      gt_bsart_line-option = lc_eq.
      gt_bsart_line-low = lc_ylso.
      APPEND gt_bsart_line TO gt_bsart.
      CLEAR :gt_bsart_line.
      gt_bsart_line-sign = lc_i.
      gt_bsart_line-option = lc_eq.
      gt_bsart_line-low = lc_yspo.
      APPEND gt_bsart_line TO gt_bsart.
      CLEAR :gt_bsart_line.
      gt_bsart_line-sign = lc_i.
      gt_bsart_line-option = lc_eq.
      gt_bsart_line-low = lc_ysub.
      APPEND gt_bsart_line TO gt_bsart.
      CLEAR :gt_bsart_line.
      gt_bsart_line-sign = lc_i.
      gt_bsart_line-option = lc_eq.
      gt_bsart_line-low = lc_yvwh.
      APPEND gt_bsart_line TO gt_bsart.
      CLEAR :gt_bsart_line.
      LOOP AT gt_bsart INTO gt_bsart_line.
        IF xekko-bsart NE gt_bsart_line.
          EXIT.
        ENDIF.
      ENDLOOP.
    ENDFORM.                    " fill_bsart
    FORM fill_final .
      REFRESH :gt_ekko.
    Getting the data from EKKO table
      SELECT ebeln
             bsart
             ernam
             lifnr
             waers
             bedat
             ekgrp
       FROM  ekko
       INTO CORRESPONDING FIELDS OF TABLE gt_ekko
      WHERE bsart EQ gv_e1edk01-bsart
        AND ebeln EQ gv_e1edk01-belnr.
      IF sy-subrc EQ 0.
        SORT gt_ekko BY ebeln ekgrp.
      ENDIF.
      REFRESH: gt_ekpo, gt_t024, gt_erev, gt_lfa1.
      IF NOT gt_ekko[] IS INITIAL.
      Getting the data from EKPO
        SELECT ebeln
               ebelp
               bstyp
               txz01
               matnr
               idnlf
               menge
               meins
               netpr
               netwr
               ean11
         FROM  ekpo
         INTO CORRESPONDING FIELDS OF TABLE gt_ekpo
          FOR ALL ENTRIES IN gt_ekko
        WHERE ebeln EQ gt_ekko-ebeln.
        IF sy-subrc EQ 0.
          SORT gt_ekpo BY ebeln ebelp matnr.
        ENDIF.
      Getting the data from EREV
        SELECT   bstyp
                 edokn
                 edokp
                 revno
                 oknam
           FROM erev
           INTO CORRESPONDING FIELDS OF TABLE gt_erev
           FOR ALL ENTRIES IN gt_ekko
         WHERE bstyp EQ gt_ekko-bstyp.
        IF sy-subrc EQ 0.
          SORT gt_erev BY bstyp oknam.
        ENDIF.
      Getting the data from LFA1
        SELECT lifnr
               stras
          FROM lfa1
          INTO CORRESPONDING FIELDS OF TABLE gt_lfa1
           FOR ALL ENTRIES IN gt_ekko
            WHERE lifnr EQ gt_ekko-lifnr.
        IF sy-subrc EQ 0.
          SORT gt_lfa1 BY lifnr.
        ENDIF.
      Getting the data from T024
        SELECT ekgrp
               eknam
          FROM t024
          INTO CORRESPONDING FIELDS OF TABLE gt_t024
           FOR ALL ENTRIES IN gt_ekko
         WHERE ekgrp EQ gt_ekko-ekgrp.
        IF sy-subrc EQ 0.
          SORT gt_t024 BY ekgrp eknam.
        ENDIF.
      ENDIF.
      IF NOT gt_ekpo[] IS INITIAL.
      Getting the data from MARA
        SELECT matnr
               ean11
               numtp
          FROM mara
          INTO CORRESPONDING FIELDS OF TABLE gt_mara
           FOR ALL ENTRIES IN gt_ekpo
         WHERE matnr EQ gt_ekpo-matnr.
        IF sy-subrc EQ 0.
          SORT gt_mara BY matnr ean11.
        ENDIF.
      Getting the data from EKET
        SELECT ebeln
               ebelp
               eindt
          FROM eket
          INTO CORRESPONDING FIELDS OF TABLE gt_eket
           FOR ALL ENTRIES IN gt_ekpo
         WHERE ebeln EQ gt_ekpo-ebeln.
        IF sy-subrc EQ 0.
          SORT gt_eket BY ebeln ebelp eindt.
        ENDIF.
      ENDIF.
    Moving the data to the final internal table
      LOOP AT gt_ekpo INTO gs_ekpo.
        gs_final-ebelp = gs_ekpo-ebelp.
        gs_final-matnr = gs_ekpo-matnr.
        CLEAR :gs_ekko.
        READ TABLE gt_ekko INTO gs_ekko
                 WITH KEY ebeln = gs_ekpo-ebeln BINARY SEARCH.
        IF sy-subrc EQ 0.
          gs_final-ebeln = gs_ekko-ebeln.
          gs_final-bsart = gs_ekko-bsart.
          gs_final-lifnr = gs_ekko-lifnr.
          gs_final-ekgrp = gs_ekko-ekgrp.
        ENDIF.
        CLEAR : gs_mara.
        READ TABLE gt_mara INTO gs_mara WITH KEY matnr = gs_ekpo-matnr.
        IF sy-subrc EQ 0.
          gs_final-ean11 = gs_mara-ean11.
          gs_final-numtp = gs_mara-numtp.
        ENDIF.
        CLEAR: gs_t024.
        READ TABLE gt_t024 INTO gs_t024 WITH KEY ekgrp = gs_ekko-ekgrp.
        IF sy-subrc EQ 0.
          gs_final-eknam = gs_t024-eknam.
        ENDIF.
        CLEAR: gs_eket.
        READ TABLE gt_eket INTO gs_eket WITH KEY ebeln = gs_ekko-ebeln.
        IF sy-subrc EQ 0.
          gs_final-eindt = gs_eket-eindt.
        ENDIF.
        CLEAR: gs_erev.
        READ TABLE gt_erev INTO gs_erev WITH KEY bstyp = gs_ekko-bstyp.
        IF sy-subrc EQ 0.
          gs_final-oknam = gs_erev-oknam.
        ENDIF.
        CLEAR:gs_lfa1.
        READ TABLE gt_lfa1 INTO gs_lfa1 WITH KEY lifnr = gs_ekko-lifnr.
        IF sy-subrc EQ 0.
          gs_final-stras = gs_lfa1-stras.
        ENDIF.
        APPEND gs_final TO gt_final.
        CLEAR :gs_final.
      ENDLOOP.
      SORT gt_final BY ebeln ebelp.
    ENDFORM.                    " fill_final
    Regards
    Kannaiah

  • ORDERS05 IDoc User Exit - Create Sales Order

    Greetings,
    I'm working at a client where they are using the ORDERS05 IDoc in conjunction with the Process code ORDE to create customer finished goods sales orders in a 46C system. When the IDoc segment E1EDP19 is qualified with "003" and the article's UPC/EAN is supplied in the material field and conversion of the UPC to material is executed during processing when the sales order type is "ZEDI" however this conversion is not executed with any other sales order type, so I suspect a user exit routine however I checked the usual suspects.
    MM06E001
    VEDB0001
    MCP20008
    MM06E001
    VEDA0001
    But not code for the UPC to material conversion.
    Any insight is alway appreciated and rewarded.
    Thanks!

    Joseph,
    Take a look in the function module EXIT_SAPLVEDA_001, see if there's an include there. We have an include there containing our Customisations, including for the E1EDP19 segment.
    Cheers, Paul.

  • How to pass header/item text in inbound ORDERS05 IDoc

    Hi,
    I'm trying to create Sales Order from an inbound ORDERS05 idoc thru SE19.
    How do I pass the header text and item text to the Sales Order?
    What should be the value of E1EDKT1-TDOBJECT and E1EDKT1-TDOBNAME?
    An early response is highly appreciated.
    Regards,
    Gajendra

    Hi Gajendra,
    What is the significance of "TDOBJECT" and "TDNAME"?
    <b>TDOBJECT</b>: application object of the text
    The field is part of the text key. It contains the name of the text object to which the text is allocated. This object must be defined in table TTXOB.
    <b>TDNAME</b>: name of the text
    The field is part of the text key. It contains the name of the text module. This name may be up to 70 characters long. An internal structure of the text name is preset by the text object, but not interpreted by SAPscript.
    <b>TDID</b>: ID of the text
    The field is part of the text key. It contains the name of the text ID to which the text module belongs. The text ID must be defined in table TTXID together with the text object.
    <b>TDSPRAS</b>: language key of the text
    The field is part of the text key. It contains the language key of the language used to enter the text lines of the text module. The language key must be defined in table T002.
    Hope this will help.
    Regards,
    Ferry Lianto

  • Required fields for Purchase Order through ORDERS05 idoc

    Hi,
    I'm creating PURCHASE orders from ORDERS05 IDOC through XI. Could anyone tell me what all segments and fields are required for this purpose, if they have done this earlier.
    Regards,
    Vijay

    Hi Vijay,
    It depends how the input is populated. Anyway to know about Mandatory Segment /Fields, you can go to Transaction code WE30 in the R/3 system and give the idoc name and open the structure. There you can get to know about Mandatory Segments/fields etc with the help of Occurences
    Regards,
    Moorthy

  • Batch Number field in IDoc for Process Orders (message type LOIPRO01)

    Hello PP experts,
    Just wanted to ask if anyone of you have worked with message type LOIPRO01 (IDoc for process orders)
    There is a segment-field in this IDoc  E1RESBL-CHARG which has description of "Batch Number"
    We tried to assign a Bath Number for an Order (using t-code COR2 --> "Goods Recpt" tab under "Receipt" section), generated an IDoc for this order, but upon checking the E1RESBL-CHARG field of the IDoc it is not populated with the Batch Number.
    The material in the process order is FERT, so technically we're trying to assign a Batch Number in one of the process orders for a Finished Goods material type,  so not on the component level.
    Can anyone here verify:
    1. is the E1RESBL-CHARG field of IDoc LOIPRO01 intended for the Product Batch Number?  If Yes, how do we populate that for in the IDoc?  --> Do I need to have a Reservation/Dependent Requirement for the Product for the Batch Number to be populated in the IDoc?
    2. If E1RESBL-CHARG can not be populated for a Product that has no Reservation/Dependent Requirements, Do I have any option of populating this field with just the Batch Number assigned to the Process Order of that product?

    Solved - LOIPRO01 IDoc does not pick up the Batch Number from AFPO table, instead from table RESB.    We need batch from AFPO and just created a lookup using the Process Order Number as import param

  • Order type 'OR' has not been defined for sales area (IDOC related)

    Hi,
    iam getting the status error as order type 'OR' has not been defined for sales area for ORDERS inbound idoc(it's in status 51),i looked at EDPAR(voe4) table and edsdc(voe2) tables,  the sales area has been defined, i don't know why iam still getting this error. please let me know if anyone have any idea or faced any kind of this problem.
    Thanks

    Hi,
    I believe this is nothing to do with the setting the IDOC value..Some config is missing...
    Check to make sure if there is a record found in the view V_TVAKZ for the combination..
    IF not check with your function consultant regarding this..
    Thanks,
    Naren

  • Inbound ORDERS05 IDoc - Create SD Sales Order (EDI)

    I having an issue in inbound ORDERS05 IDoc processing to create SD sales order where the sales unit of measure for the material is getting lost/replaced. We are sending sales unit of measure in the E1EDP01-MENEE field, we are also sending the material UPC in teh E1EDP19 (003) segment relying on UPC material determination rules to resolve the material for the sales order. During this process of material determination the sales unit of measure is getting lost/replaced. I know as if we send the actual SAP material in the E1EDP19 segment (no material determination required) the sales unit of measure is unchanged. In this SAP system multiple sales unit of measure are maintained for each individual UPC code. Just looking for input on where to look to resolve this, config, user exits, etc..

    I can't say for sure what you should be doing, as I don't know how you have setup your material master, or how your Customers order. We have some Customers that always want EAches, some that always want OUTers, then some who want whatever UOM is assigned to the GTIN (UPC) that they order, which could be one of several. We have our custom code in ZXVEDU03.
    Cheers, Paul.

  • Issue in passing process order related to order type ZGP9.

    Hi Experts,
    There has been a development done in CIF user exit to block process orders having order type ZGPD & ZGP7. But we are also facing issue for process order flow for order type ZGP9. 
    1. To avoid double counting of Depack orders (order type ZGPD) in actual production key figure of SCIPIO, stop sending actual production for order types ZGPD from P1 to SCIPIO.      
    2. To block Rework (ZGP7) and De-pack (ZGPD) Process order in CIF from SCIPIO end, Add one extra field in Custom Structure CI_ORDCUS which transfers Process Orders to APO. This field will capture "Order Type" for Process Orders and send it to APO.
    could any body suggest me why the issue is coming for process order ZGP9.

    Hi Venkat,
    1) Check whether the user exit is implemented properly
    2) Check whether the process order showing ZFGP9 is
    created recently?
    3) Archive that process order and try creating a manual
    process order and check.   If still error persists, use an
    abapper to check which table is calling that order type
    and accordingly you can proceed.
    Regards
    R. Senthil Mareeswaran.

  • Incoming ORDERS05 - how to pass PR00 for a line item

    Hi
    I am working with IDOC type ORDERS05 for creating sales orders, debit/credit memo in SAP.  I want to pass value of PR00 for the order. I tried using segment E1EDP05 but not successful.
      If anybody has passed value of PR00 using ORDERS05, please help
    TIA
    Koustav

    I think the solution is in oss note: 388120
    So that the conditions and terms of payment are transferred from ORDERS or ORDCHG IDOCs to the sales order, message VG201 or VG 202 has to be deactivated for EDI
    However I am not in front of SAP and cannot verify immediately

  • Segment management in ORDERS05 IDOC.

    Hi there.
    I have two questions, one is very focused on text management in ORDERS05, the other one is more generally speaking.
    1 - Text management in ORDERS05 IDoc:
    I have texts in my purchase order that I fill in, and then generate my IDoc. When looking at IDoc detail through WE05 or WE02, my texts are not visible neither in E1EDKT1 nor E1EDPT1 segments. Basically, those segments are not even created in my IDoc. Why? Anything to do in PO and/or ALE customizing?
    2 - More general:
    I need to have, in my E1EDS01 segment, the total quantity I order in my PO. So, I need a segment with qualifier '004' in SUMID, then my quantities. Currently, I only have SUMID='002' and my total value amount. How can I define (or it is defined by the system) the type of information I have in my segments, or segments themselves?
    Please tell me if not clear at all.
    Thanks for your answers.
    Chris.

    Thanks Dani.
    I checked the T166A table and found that the following entries are missing for my cases: EKPO and EKKO for my ZNB PO type.
    Shall I just put an entry for those two things in that table and this will allow me to get my texts in my ORDERS05 IDoc?
    For point 2, as I am not an ABAP developper, I do not understand what to do. I can deal with customizing, but not with ABAP programming on that subject.
    Thanks anyway at least for the first part of the answer.

  • Inbound Function module to process ORDERS05 IDOC

    Hi,
    My requirement is to create pre-booked Purchase order.
    I have to extend the ORDERS05 IDoc for this requirement. It is an inbound IDoc.
    I found the function module IDOC_INPUT_ORDERS. But I have a doubt will it work for Purchase orders because i found most of the data inside the function module are relevant for Sales order creation.
    Can you please suggest me a suitable function module to process this Inbound Idoc and create purchase order.
    Regards,
    Balaji. R

    Hi,
    The message type and basic idoc type for the processing of purchase orders:
    PORDCH                 PORDCH01                -- For change
    PORDCR1               PORDCR101              -- For Create
    Regards,
    Ginu Litta Raj

Maybe you are looking for