SD-EDI Inbound ORDERS05

Hi people!
I want to receive sales orders from customers by EDI.
When receiving the IDOC, the customer sent me his EDI partner number. (Operational point)
How to translate the 13 digit number to my SAP customer number?
I have WE20 actualized, the EDPAR table is also actualized...
The message ORDER have the operational code ORD asigned with the function INPU_IDOC_ORDER.
When processing the IDOC, the system was not able to determine the customer number from that external partner informed.
Can someone help me please? There is something I done wrong...
The steps I've done:
(Example)
- VOE4 - My SAP customer: 11 - Ext. function: SP - External Partner: 840000000000001
- WE20 - Partner Type KU:
Internal Parameters: Partner role: SP - Message type ORDERS - Process Code ORDE
Function: IDOC_INPUT_ORDERS
THe PI / XI station send me the IDOC to an Logic partner:
- WE20 - Partner Type LS:
Internal Parameters: Partner role: SP - Message type ORDERS - Process Code ORDE
Function: IDOC_INPUT_ORDERS
Debuging the process the system try to select the incorrect information with incorrect data into:
Process Code ORDE
Function: IDOC_INPUT_ORDERS
PERFORM interpret_idoc_orders
So, execute:
- Auftragskopf Partnerinformationen -
- partner data -
WHEN 'E1EDKA1'.
MOVE IDOC_DATA-SDATA TO E1EDKA1.
PERFORM ZUORDNEN_ORDERS_E1EDKA1.
Then execute:
- Auftraggeber -
- order party -
WHEN 'AG'.
IF E1EDKA1-PARTN EQ SPACE
AND E1EDKA1-LIFNR NE SPACE.
- ermitteln Partnernummer aus Tabelle EDPAR -
- determine partnernumber from table EDPAR -
PERFORM EXTERNAL_PARTNER USING IDOC_CONTRL-SNDPRN
E1EDKA1-LIFNR
E1EDKA1-PARVW
E1EDKA1-PARTN.
ENDIF.
And that perform does ( in my opinion, an worng select into EDPAR)
FORM EXTERNAL_PARTNER USING INPART
EXPART
PARTNERROLLE
PARTNER.
SELECT SINGLE * FROM EDPAR WHERE KUNNR = INPART
AND PARVW = PARTNERROLLE
AND EXPNR = EXPART.
Thans in advance for any help!

Hi,
EDIDC-SNDPRN has to contain you My SAP Customer number i.e. in your example it is "0000000011( Remember you are using "KU" type of partner profile. So EDIDC-SNDPRN has to be valid customer in your system) and additional you need to send your external partner number in E1EDKA1-LIFNR field where E1EDKA1-PARVW = 'AG' and this should solve the problem. So if you are using XI you may need to use value mapping concept in order to populate EDIDC-SNDPRN correctly.
Do not forget to populate EDPAR-KUNN2 ( Internal customer/Last field of the EDPAR table) field as well. You may fill it up with the same number as "0000000011".
Hope this helps.
Regards,
Rudra

Similar Messages

  • 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.

  • EDI inbound Purch Order - Changes needed

    Hi all,
      I have EDI inbound purchase orders that get created into sales orders in sap.  This use message type ORDERS and process code ORDE.   Question is for some of  these inbound purchase orders,  i may need to add a new material to existing sales orders that are created previously.  To make changes to existing sales order, can i use the same message type and process code ?     Have anyone come across such situation ?
    thanks
    Joyce

    Hi Joyce,
    The IDOC Type remains the same for create/change/confirmation etc, the system uses the partner profile to know the kind of action it must take on a given IDOC, parameters like message type and process code help the system to process the IDOC accordingly.
    IDOC Type      Message Type      Process Code      Action taken
    ORDERS05     ORDERS                 ORDE                  Create Order
    ORDERS05     ORDCHG                ORDC                  Change Order
    ORDERS05     ORDRSP                 ORDR                  Confirmation
    My bad, the segment name is E1EDP01 --- Go to WE30, open up idoctype ORDERS05, look for E1EDP01 segment, double click on this segment and you will see the field ACTION.
    Regards,
    Chen

  • EDI Inbound-Port definition

    Hi,
    We are doing EDI Inbound for PO. For this I need to define the port(Sender Port) as in the control record(i.e as they r sending) .If they change their port it is not working what shold I do for this.
    regds,
    Vinsa.R

    Hi,
    As i mentioned before, the sender should inform any change in control parameter so you can change your port too.
    Check with the sender if they can provide this information before changing. I do not what is the terms of your company with this sender, but they should inform you before doing any change.
    <b>Option-2</b>
    The other option you have is, you create your custom program which runs before RSEINB00. In this program you have to,
    - read each and every file from this UNIX directory
    - read the control record.
    - check if SNDPOR is what you have defined in your system
    - if not then change it and save it back.
    You can check the source code of FM <b>'IDOC_INBOUND_FROM_FILE'</b> to see how SAP read this file. ( Program RSEINB00 calls this FM internally ). This will give you an idea, how to read control record.
    I do not know if option-2 of changing control record in file will affect anything else or not.
    Let me know if you have any question.
    Regards,
    RS

  • Oracle EDI Inbound & Outbound setup docs R12.1.3 overview

    Hi Gurus,
    Please share with me setup docs for Oracle EDI Inbound & Outbound . If possible Pros and Cons of EDI .. as we're suggesting this for one of our esteemed client in UK.
    Also let me know below are possible are not with Oracle EDI functionality :
    Plug in custom solution or logic to dervice item Pricing, Item Cross Reference and Unit of Measure while creating Sales order in EBS ?
    Many thanks,
    Mahe

    Duplicate - Oracle EDI Inbound and Outbound setup docs R12.1.3

  • EDI :  inbound processing error.

    Hi All,
    I am facing the below error
    "Entry in inbound table not found" status 56.
    I am setting a new EDI inbound interface for goods reciept GR:
    We have got a flat file which we are trying to upload from SAP directory.
    after uploading i am getting the above error. The error points at Partner Profile details stating the details doesnot exist. But i cross checked and its all correct.
    - Partner Profile created.
    - Message type exixt in INBOUND Parameters.
    If i reprocess this failed idoc using we19 selecting INbound function module "L_IDOC_INPUT_WMMBXY" then it gets processed successfully.
    If i reprocess this failed idoc via editing and then running report RBDINPUT for processing edited idoc status 69, then the probelm persist.
    I dont know what i am missing.
    Thanks in advance.

    Hi,
    I am getting the same error.
    Can u please help me on this.
    Thanks and Regards
    Neha Kapoor

  • EDI Inbound ( need code sample )

    Hi Guus,
          I have an object to develop , its and EDI inbound interface . Can some one send me sample code or atleast guide me from where I can start.
    Regards
    Avi.......

    Hi ,
    plz go through the below code..
    FUNCTION zsd_idoc_input_order_change.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(INPUT_METHOD) LIKE  BDWFAP_PAR-INPUTMETHD
    *"     VALUE(MASS_PROCESSING) LIKE  BDWFAP_PAR-MASS_PROC
    *"  EXPORTING
    *"     REFERENCE(WORKFLOW_RESULT) LIKE  BDWFAP_PAR-RESULT
    *"     REFERENCE(APPLICATION_VARIABLE) LIKE  BDWFAP_PAR-APPL_VAR
    *"     REFERENCE(IN_UPDATE_TASK) LIKE  BDWFAP_PAR-UPDATETASK
    *"     REFERENCE(CALL_TRANSACTION_DONE) LIKE  BDWFAP_PAR-CALLTRANS
    *"  TABLES
    *"      IDOC_CONTRL STRUCTURE  EDIDC
    *"      IDOC_DATA STRUCTURE  EDIDD
    *"      IDOC_STATUS STRUCTURE  BDIDOCSTAT
    *"      RETURN_VARIABLES STRUCTURE  BDWFRETVAR
    *"      SERIALIZATION_INFO STRUCTURE  BDI_SER
    *"  EXCEPTIONS
    *"      WRONG_FUNCTION_CALLED
    Work areas for the idoc tables.
      DATA: wa_data    TYPE edidd.
      status = '53'. "initial
    Read the control data information of idoc.
      READ TABLE idoc_contrl INTO gwa_control WITH KEY mestyp = 'ZORDRPLY'.
      IF sy-subrc EQ 0.
    Extract the data from the segments.
        LOOP AT idoc_data INTO wa_data             "LOOP AT idoc_data
        WHERE docnum = idoc_contrl-docnum.
          CASE wa_data-segnam.                     " CASE gwa_data-segnam
            WHEN 'Z1SCSK'.                          "Header data
              MOVE wa_data-sdata TO gwa_z1scsk.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = gwa_z1scsk
                IMPORTING
                  output = gv_vbeln.
            WHEN 'Z1SCSP'.                          "Item data
              MOVE wa_data-sdata TO gwa_z1scsp.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = gwa_z1scsp-posnr
                IMPORTING
                  output = gv_posnr.
              gwa_z1scsp-posnr = gv_posnr.
              APPEND gwa_z1scsp TO i_z1scsp.
          ENDCASE.                                 " CASE gwa_data-segnam
        ENDLOOP.                                     "LOOP AT idoc_data
    Update the sales order
        PERFORM order_change.
      ELSE.
    Begin of Mod-001
        status = '51'.
        bapi_retn_info-type       = 'E'.
        bapi_retn_info-id         = 'ZSDM'.
        bapi_retn_info-number     = '028'.
        bapi_retn_info-message_v1 =  'Wrong'.
        bapi_retn_info-message_v2 =  'Message'.
        bapi_retn_info-message_v3 =  'Type'.
       RAISE wrong_function_called.
      ENDIF.                                            " IF sy-subrc EQ 0
    *Start wf
      PERFORM wf_start
                 USING
                        idoc_contrl-docnum
                        gv_vbeln
                       CHANGING
                         bapi_retn_info.
    *end of starting of wf
    *set status
      IF status = '53'.
        bapi_retn_info-type       = 'S'.
        bapi_retn_info-id         = 'ZSDM'.
        bapi_retn_info-number     = '028'.
        bapi_retn_info-message_v1 =  gv_vbeln.
        bapi_retn_info-message_v2 =  'Changed.'.
        bapi_retn_info-message_v3 = 'Succcessfully'.
      ENDIF.
      PERFORM idoc_status_ord_change
              TABLES idoc_data
                     idoc_status
                     return_variables
               USING idoc_contrl
                     bapi_retn_info
                     status
                     workflow_result.
    End of Mod-001
    ENDFUNCTION.
    FORM idoc_status_ord_change
         TABLES idoc_data    STRUCTURE  edidd
                idoc_status  STRUCTURE  bdidocstat
                r_variables  STRUCTURE  bdwfretvar
          USING idoc_contrl  LIKE  edidc
                value(retn_info) LIKE   bapiret2
                status       LIKE  bdidocstat-status
                wf_result    LIKE  bdwf_param-result.
      CLEAR idoc_status.
      idoc_status-docnum   = idoc_contrl-docnum.
      idoc_status-msgty    = retn_info-type.
      idoc_status-msgid    = retn_info-id.
      idoc_status-msgno    = retn_info-number.
      idoc_status-appl_log = retn_info-log_no.
      idoc_status-msgv1    = retn_info-message_v1.
      idoc_status-msgv2    = retn_info-message_v2.
      idoc_status-msgv3    = retn_info-message_v3.
      idoc_status-msgv4    = retn_info-message_v4.
      idoc_status-repid    = sy-repid.
      idoc_status-status   = status.
      APPEND idoc_status.
      IF idoc_status-status = '51'.
        wf_result = '99999'.
        r_variables-wf_param   = 'Error_IDOCs'.
        r_variables-doc_number = idoc_contrl-docnum.
        READ TABLE r_variables FROM r_variables.
        IF sy-subrc <> 0.
          APPEND r_variables.
        ENDIF.
      ELSEIF idoc_status-status = '53'.
        CLEAR wf_result.
        r_variables-wf_param = 'Processed_IDOCs'.
        r_variables-doc_number = idoc_contrl-docnum.
        READ TABLE r_variables FROM r_variables.
        IF sy-subrc <> 0.
          APPEND r_variables.
        ENDIF.
      ENDIF.
    ENDFORM.                    "idoc_status_ord_change
    ***INCLUDE LZSD_FS007_ORDERCHANGEF01 .
    *&      Form  order_change
          This Form is used for updating the DB tables(vbap,vbep)        *
    FORM order_change .
    Declaration of internal tables.
      DATA : i_vbap TYPE STANDARD TABLE OF vbap,
             i_vbep TYPE STANDARD TABLE OF vbep.
    Declaration of workareas.
      DATA : wa_vbap TYPE vbap,
             wa_vbep TYPE vbep.
    Declaration of constants.
      CONSTANTS : lc_sno(3)     TYPE c VALUE '039',
                  lc_ino(3)     TYPE c VALUE '040',
                  lc_msg(4)     TYPE c VALUE 'ZSD',
                  lc_emsgty(1)  TYPE c VALUE  'E',
                  lc_smsgty(1)  TYPE c VALUE  'S',
                  lc_estatus(2) TYPE c VALUE  '51',
                  lc_sstatus(2) TYPE c VALUE  '53'.
    Declaration of variable.
      DATA : lv_index TYPE syindex,
             lv_zzproddt TYPE sydatum.
    Fetch the data from vbap
      SELECT * FROM vbap INTO TABLE i_vbap
      WHERE vbeln EQ gv_vbeln.
      IF NOT i_vbap IS INITIAL.
    Fetch the data from vbep
        SELECT * FROM vbep INTO TABLE i_vbep
          FOR ALL ENTRIES IN i_vbap
          WHERE vbeln EQ i_vbap-vbeln
          AND posnr EQ i_vbap-posnr.
    Modify production option date (zzproopdt) of i_vbap
    and production date(zzproddt) & original production date(zzoprodt)
    of i_vbep with the data sent by SCS.
        lv_index = 1.
        LOOP AT i_z1scsp INTO gwa_z1scsp.
          LOOP AT i_vbap INTO wa_vbap WHERE posnr = gwa_z1scsp-posnr.
            IF sy-subrc EQ 0 .
      Copies the date value in gwa_z1scsp-zzproopdt to wa_vbap-zzproopdt,
      if valid date is there in gwa_z1scsp-zzproopdt
              PERFORM validate_date USING gwa_z1scsp-zzproopdt
                                          wa_vbap-zzproopdt.
              IF NOT wa_vbap-zzproopdt IS INITIAL.
                MODIFY i_vbap FROM wa_vbap TRANSPORTING zzproopdt.
              ENDIF.
      Copies the date value in gwa_z1scsp-zzproddt to lv_zzproddt,
      if valid date is there in gwa_z1scsp-zzproddt
              PERFORM validate_date USING gwa_z1scsp-zzproddt
                                          lv_zzproddt.
      If gwa_z1scsp-zzproddt is not initial then only update in VBEP.
              IF NOT lv_zzproddt IS INITIAL.
                LOOP AT i_vbep INTO wa_vbep FROM lv_index.
                  IF wa_vbep-posnr GT wa_vbap-posnr.
                    lv_index = sy-tabix.
                    EXIT.
                  ELSEIF wa_vbep-posnr EQ wa_vbap-posnr.
                    wa_vbep-zzproddt = lv_zzproddt.
             Update Original Production date only when its initial.
                    IF wa_vbep-zzoprodt IS INITIAL.
                      wa_vbep-zzoprodt = wa_vbep-zzproddt.
                    ENDIF.
                    MODIFY i_vbep FROM wa_vbep TRANSPORTING zzproddt zzoprodt.
                  ENDIF.
                  CLEAR wa_vbep.
                ENDLOOP.
              ENDIF.
            ELSE.
    Begin of Mod-001
              status =  lc_estatus.
              bapi_retn_info-type       = lc_emsgty.
              bapi_retn_info-id         = lc_msg.
              bapi_retn_info-number     = lc_ino.
              bapi_retn_info-message_v1 =  gwa_z1scsp-posnr.
            ENDIF.
          ENDLOOP.
           IF sy-subrc EQ 4.
            status =  lc_estatus.
            bapi_retn_info-type       = lc_emsgty.
            bapi_retn_info-id         = lc_msg.
            bapi_retn_info-number     = lc_ino.
            bapi_retn_info-message_v1 =  gwa_z1scsp-posnr.
          ENDIF.
          CLEAR: wa_vbap, gwa_z1scsp.
        ENDLOOP.
      ELSE.
        status =  lc_estatus.
        bapi_retn_info-type       = lc_emsgty.
        bapi_retn_info-id         = lc_msg.
        bapi_retn_info-number     = lc_sno.
        bapi_retn_info-message_v1 =  gv_vbeln.
        EXIT.
    End of Mod-001
      ENDIF.
    Update the DB tables
        UPDATE vbap FROM TABLE i_vbap.
        UPDATE vbep FROM TABLE i_vbep.
    ENDFORM.                    " order_change
    *&      Form  VALIDATE_DATE
    Converts the date into DATS format and check if it is valid,
    if valid returns date in p_date_dats else clear it.
         -->p_date_c8    Date in Char format send by SCS
         -->p_date_dats  Date in DATS format.
    FORM validate_date  USING    p_date_c8 TYPE char8
                                 p_date_dats TYPE dats.
      CLEAR p_date_dats.
      p_date_dats = p_date_c8.
      CALL FUNCTION 'DATE_CHECK_PLAUSIBILITY'
        EXPORTING
          date                      = p_date_dats
        EXCEPTIONS
          plausibility_check_failed = 1
          OTHERS                    = 2.
      check sy-subrc NE 0.
        CLEAR p_date_dats.
    ENDFORM.                    " VALIDATE_DATE
    *&      Form  wf_start
          text
         -->P_IDOC_CONTROL_DOCNUM  text
         -->P_GV_VBELN  text
         <--P_BAPI_RETN_INFO  text
    FORM wf_start  USING    p_idoc_control_docnum
                            p_gv_vbeln
                   CHANGING p_bapi_retn_info TYPE bapiret2.
      INCLUDE <cntn01>.
      DATA: agents  LIKE swhactor OCCURS 1 WITH HEADER LINE,
            process_type TYPE char1,
            idoc_no TYPE edidc-docnum,
            creator LIKE swwwihead-wi_creator.
      swc_container wi_container.
      swc_create_container wi_container.
      swc_set_element wi_container 'Document_no' p_gv_vbeln.
      swc_set_element wi_container 'Process_type' '1'.
      swc_set_element wi_container 'Idoc_no' p_idoc_control_docnum.
      CALL FUNCTION 'SWW_WI_START_SIMPLE'
        EXPORTING
          creator                      = creator
          task                         = 'WS90200019'
        TABLES
          agents                       = agents
          wi_container                 = wi_container
        EXCEPTIONS
          id_not_created               = 1
          read_failed                  = 2
          immediate_start_not_possible = 3
          execution_failed             = 4
          invalid_status               = 5
          OTHERS                       = 6.
      IF sy-subrc <> 0.
        p_bapi_retn_info-type   = 'E'.
        p_bapi_retn_info-id = sy-msgid.
        p_bapi_retn_info-number = sy-msgno.
        p_bapi_retn_info-message_v1 = sy-msgv1.
        p_bapi_retn_info-message_v2 = sy-msgv2.
        p_bapi_retn_info-message_v3 = sy-msgv3.
        p_bapi_retn_info-message_v4 = sy-msgv4.
      ENDIF.
    ENDFORM.                    " wf_start..
    The idoc configurations for customized idoc (inbound) are..
    1>WE81
    2>WE31
    3>WE30
    4>BD51(Attach ur zfunction mdoule)
    5>WE57(Attach ur zfunction mdoule to message type and basic type)
    6>we42
    7>WE20...
    Regards,
    nagaraj

  • Inbound ORDERS05, Ship-to party PO number

    Hello,
    we're trying to include the ship-to party's PO number in segment E1EDP02, qualifier 044 in an inbound ORDERS05 IDoc. However the data doesn't appear in the sales order. If we do the same on the header level and use E1EDK02, 044 instead it works just fine. Unfortunately this is not viable in this scenerio as the ship-to party's PO differs from line to line.
    Any ideas?
    Thanks,
    Sven

    Hi
    See Note 753153 - FAQ: Customer-functions in IDOC_INPUT_ORDERS. Check if EXIT_SAPLVEDA_001 gives you any possibility to do it.
    I hope this helps you.
    Regards
    Eduardo

  • 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

  • EDI inbound invoices in Western Europe

    All,
    Looking for anyone with experience in doing inbound EDI invoicing in Western Europe.   What VAN (value added network) do you use and what is your archiving process?  
    Regards,
    Sandra

    we continue to look for VANS that have experience in the space.

  • EDI Inbound Interface

    Dear Friends,
    In our organization, there is a third party involved into stocktake and provide us input flat files for each plant separately. These files are loaded into SAP automatically as iDoc, this is working good.
    Some details of EDI configuration are
    Partner Type KU: (Each Plant is being configured as a customer Partner Type KU)
    Inbound Parameter, Message Type : WVINVE
    Process Code: WVIN
    Identification: IDOC_INPUT_STORE_INVENTORY
    Option ALE: Radio Button "Processing with ALE Services"
    Processing Type: Radio Button "Processing by function module"
    I am trying to find out where is these automation done? (I mean how incoming data is being loaded into sap automatically?)
    and where(directly etc) initially incoming data is being stored into SAP?
    Regards,
    Sunny

    Hi,
    IDocs are nothing more than structured ASCII data, you could always process them directly with an ABAP. This is certainly the quick and dirty solution, bypassing all the internal checks and processing mechanisms. We will not reinvent the wheel here..
    Please check the below link...
    http://www.idocs.de/www5/EDI/HTML/IDocBook.htm#_Toc8400370
    Hope it may help you.
    Kuber

  • Changing IDOC Control Record for EDI inbound Orders Creatiion

    Hi,
         When I try to process the Inbound orders Idocs file through the GENTRAN EDI System.IDOC's were errored out, because of the Partner function was not defined for the Customer ( Legacy ) ( Type KU ) in the SAP.
            Is there any user exit/badi/Configuration to change the Legacy Partner(Customer) to the SAP Partner(Customer) mapping and update the IDOC Control record with the SAP Partner. I am calling EDI_DATA_INCOMING Function module and IDOC_INPUT_ORDERS.IDOCs errored out with Message EO-332 ( Partner function not defined ). 
    Advance Thanks,
    Balaji.

    It's been a long time since I have done any IDOC processing. 
    Go to SE37 and enter the function module IDOC_INPUT_ORDERS.  Display the source code.  Search for "CALL CUSTOMER".  You should see several "CALL CUSTOMER-FUNCTION" lines.  These are enhancements where you can manipulate the IDOC data.  If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value.  Double-clicking on the number in quotes will bring you to an "EXIT_" function module.  A "ZX" INCLUDE program is referenced.  If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it.  The values passed into the function module are available in the INCLUDE.
    Ideally, you should create a project in transaction CMOD that references the chosen enhancement.  This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

  • ORA-24816 Error on EDI inbound processing

    We are encountering an issue for EDI X12  inbound data files which have extraneous characters. B2B initially failed throwing  “ Document Protocol Identification error “ .
    To resolve this, we enabled flag  “b2b.edi.enablePeprocess” to true , after which it started processing fine in DEV environment , however it throws below exception in QA environment .
    Internal Exception: java.sql.SQLException: ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column
    Error Code: 24816
    Call: INSERT INTO B2B_WIRE_MESSAGE (ID, JOB_ID, ACKNOWLEDGEMENT_MODE, LABEL, ATTRIBUTE2, MESSAGE_DIGEST, ATTRIBUTE4, MESSAGE_ID, ATTRIBUTE3, ATTRIBUTE5, CPST_INST_CREATED_TIME, CREATED, LAST_RESUBMITTED_TIME_STAMP, MODIFIED, LAST_VIEWED_TIME_STAMP, MSG_SIZE, DELIVERED_ENDPOINT, PASSWORD, DIRECTION, PORT, ENCRYPTION_CERTIFICATE, PROTOCOL_COLLABORATION_ID, ERROR_CODE, PROTOCOL_MESSAGE_ID, ERROR_DESCRIPTION_CLOB, PROTOCOL_TRANSPORT_BINDING, ERROR_TEXT_CLOB, REFER_TO_PROTOCOL_MESSAGE_ID, EXCHANGE_REMAINING_RETRY, RESUBMIT_COUNT, FROM_ADDRESS, SIGNING_ALGORITHM, SIGNING_CERTIFICATE, MESSAGE_STATUS, SIGNING_PROTOCOL, LAST_VIEWED_USER_NAME, STATE, DIGEST_ALGORITHM, TO_ADDRESS, ENCRYPTION_PROTOCOL, TRANSPORT_CERTIFICATES, ERROR_TEXT, TRANSPORT_CORRELATION_ID, EXCHANGE_RETRY_INTERVAL, TRANSPORT_HEADERS, ATTRIBUTE1, TRANSPORT_PROTOCOL, CHANNEL_NAME, TRANSPORT_PROTOCOL_VERSION, ERROR_DESCRIPTION, TRANS_SECURITY_PROTOCOL, HOST_NAME, TRANS_SECURITY_PROT_VERSION, ENCRYPTION_ALGORITHM, URL, LAST_RESUBMITTED_USER_NAME, USER_NAME, EXCHANGE_ATTEMPT_COUNT, VERSION, PAYLOAD_STORAGE, PACKED_MESSAGE, RESUBMIT_REF_TO) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
            bind => [A513532C140185965980000010261DFC, null, SYNC, null, null, rLdBG4pYQf76lQXJZdl43gE7QqE=^M
    We checked many options for the differences between Dev & QA , but could not find a root cause . 
    Version : 11.1.1.6

    Hi,
    I am getting the same error.
    Can u please help me on this.
    Thanks and Regards
    Neha Kapoor

  • Status 56 : EDI Inbound Partner Profile not available

    I am trying to load an inbound 856 IDoc from EdI subsystem to SAP. It si giving me an error 56 saying Inbound partner profile not available.
    I have set up the partner as Vendor in we20. Is there any other place that I need to set up the partner. We have inbound docs coming in as a customer(KU) but this is first vendor set up
    Do you know what I am missing?
    When I clicked on status message 56 -- says  /ICPLPLIVA/LI/LF/DESADV///T/....key fields missing in EDP21? is the error really meant that?
    Thanks in advance

    Hi,
    Can you tell us about the IDoc control record?
    In order to determine whether need to setup LI or KU partner profile.
    Please go to WE02 and check the IDoc control record.
    What are the values in partner tab?
    Port             ???
    Partner number   ???               
    Partn.Type       ???                                   
    Function                                                            
    Port             ???
    Partner number   ???
    Partn.Type       ???                             
    Partner Role      
    Regards,
    Ferry Lianto

  • Edi Inbound program

    hI Experts,
    Can any body help me how to write Inbound program in EDI with Technical Description. My requirement ls like this When the company is paying amount to vendors, The company has to send amount information to bank by using transaction F110. When ever bank receives the information it has to display 'information received'. When ever bank is processed it has to display information ' payment proceed'.
    I will give you maximum points.
                                                                                Thanks
                                                                                    Satya.

    Hi,
    For inbound process generally the file from legacy system comes in xml FORMAT to EDI subsystem now it will be converted to IDOC file format or an idoc format.
    if u get in IDOC file format then u need to use WE16 tcode .Now u need to put ur IDOC file in the application server directory and in WE21 U need to create a file port and then in the inbound file tab need to specify the application server path where u stored the IDOC file.
    Now go to WE16 and give the directory path as well the file port and execute ,u will see an idoc will be created and can get the datails in WE02/WE05 tcode.
    if u straight away get in idoc format then u can test in WE19 tcode by using the message type radio button ,Give the control record information and data record information   and then u need to specify the FM which actually triggers the idoc inWE57 and u need to give that name in WE19 .Now press on execute button u will find the creation of idoc.
    For inbound process the only method we have is processcode method which is attached to a FM in we42 ,whcih trigggers the idoc.
    please have a look at the below programs
    RBDMANI2
    RBDMANIN
    Regards,
    Nagaraj

Maybe you are looking for