Testing orders05 idoc in we19 and populating E1EDK14 segment

Experts
I am trying to test the orders message in we19.
I am inputting all the values for the segment fields.
But probelm comming while populating the E1EDK14 .
We need to input the sales area , sales doc type in this.
Here it shows two fields to input one is qualifer and other orgid.
In quarlifer it is taking only one value if i am trying to input other it is overriding.
Example i am inputting 006 and again i am trying to input 007 but 006 is overriden by 007.
If this is the case then how can i tell to the system which is sales org , which isdistribution channel, which is division etc.
help please.

Hey there
'If this is the case then how can i tell to the system which is sales org , which isdistribution channel, which is division etc.'
You need to distinquish with the help of qualifers field in the segment ie 006,007,008,012,017 etc and it depends on what type of data we are feeding.
'Here it shows two fields to input one is qualifer and other orgid.'
Yes E1EDK14 has two fields only ie QUALF & ORGID.
"In quarlifer it is taking only one value if i am trying to input other it is overriding."
As per my understanding from your concern I hope you are trying to input in the single segment all the values of header data , this is wrong.
For this you need to create another segment below the present one.
Simply  press the create icon (F5) , you will get another E1EDK14 segment , and do the same as per your need.
So finally you will be having like this....
E1EDK01
E1EDK14   006DIVISION
E1EDK14   007DC
E1EDK14  008SORG
ELEDK14  012ORDTYPE
E1EDK05
and so on ..
Let me know if you still face any problem in this case, Happy to help you.
Best Regards,
Vvieks
"Grow and help others to grow"

Similar Messages

  • Error in number range while testing inbound idoc via we19

    hi all,
    i have done all configurations but while testing the inbound idoc via we19 i am getting an error 'error in assigning number to idoc'..i checked and found that the number range object for idoc is edidoc in it number interval is defined from 1 to 99
    i dont think that anything is wrong with the number object..
    Can u tell me how dow i eliminate this error?

    Increase Higher limit the reason is when you look at current idoc number ( This idoc number already exists ) ,it will not create new idoc number.
    System will get the number from SNRO Based on IDOC Object.
    Just look at EDIDC and see the current idoc number.
    Simple example :
    I have one number - 100 ,it is already exists in database,if i insert same record to the database ,did system will accept ?
    Thanks
    Seshu

  • Testing Inbound IDoc via WE19...

    Hi,
    I am trying to learn IDOCs via WE19.
    I just took a sample IDOC from WE02 and tried to test in WE19.
    I am trying to understand what do we mean by following:
    1) Process Inbound IDOC via file ?
    2) Process Inbound IDOC via function module ?
    Regards,
    Rajesh,

    Rajesh,
    Go thru this link
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

  • ORDERS05 Idoc Type Extension

    Hello,
    I am extending the segment E2EDKA3 in ORDERS05. Please let me know any user exit or any other way to populate the values in the extended segments.
    I am adding these fields: VBPA-KUNNR,VBPA-ADRNR,VBPA-XCPDK & VBPA-ADRNP                         .
    Thanks in advance,
    Suresh

    Hi Suresh,
    Go through this info ucan able to do.
    Enhancement of IDoc Type
    Usually enhancement takes place when the content in IDocs provided by SAP are not sufficient for the business process. IDoc extension can take place whenever dictionary table has a new structure appended required by the business process. 
    In brief IDoc extension takes place when extra fields are required for the business process.
    Let us take a scenario and understand the process of IDoc extension.
    In this scenario say visitor is different from the actual customer who has came to the sales office in behalf of the customer to obtain the quotation or inquiry etc. Or an authorized agent qualified by the actual customer to order for items. So a field by name NAMEVI (Visitor) is added to Customer master data. As there is no provision given by SAP to handle this, we need to extend an IDoc. 
    The standard message type and IDoc type provided by SAP are DEBMAS and DEBMAS05. 
    Consider the data in the table below for extending the IDoc. These details can be understood in different sections in the process of extending it. 
    Basic IDoc type      DEBMAS05
    Version      4.7
    IDoc extension      DEBMASEXT
    Custom segment      Z1KNA1
    Fields in Custom Segment      Visitor
    Parent of Custom Segment      E1KNA11
    Outbound process
    Step1. Customize kna1 table by appending a structure provided by SAP (ZAKNA1) 
    Component                Component Type
    VISITOR                     NAMEVI
    Step2: Write a module pool program to update some existing customers to add data  for Visitor. 
    Step3: Create a custom segment
    Transaction Code: WE31
    Segment type: Z1KNA11   Click  (create). Provide short text 
    Field Name                Data element
    VISITOR                NAMEVI
    Save 
    Step4: Create IDoc extension
    Transaction      WE30
    Object Name      DEBMASEXT
    Choose Extension
    Click   and it leads to next screen.
    Linked basic type: DEBMAS05
    Provide description and enter
    Observe all the segments to be copied into your IDoc extension from linked basic
    type.
    Select E1KNA11 and click  (create segment) to obtain a popup window
    Provide the required values and observe child segment Z1KNA11 to be added to
    parent segment E1KNA11. 
    Step5: Release segment and IDoc extension
    Transaction: WE31
    Segment type: Z1KNA11
    Path: Edit à Set release
    Step6: Assign Basic type to extension / messages
    Transaction: WE82
    Click  , then 
    Select DEBMAS message type against DEBMAS06 basic type
    Click   provide the information
    Message Type      Basic Type      Extension      Version
    DEBMAS      DEBMAS06      DEBMASEXT           4.7
    Delete the earlier one from which it was copied.
    Save. 
    Observe the result as follows
    Step 7: Check and Transport IDoc extension
    Transaction: WE30
    Object name: DEBMASEXT
    Path: Development object à Check
    Ensure that there are no errors or warnings
    Now transport
    Path: Development à Transport 
    Step8: Find suitable user exit for writing code to support IDoc extension
    Transaction: SE84.
    Click Enhancements
    In short text provide customer
    Find suitable enhancement to be VSV00001 
                             Alternative way
    Transaction: SMOD
    Click F4 help for Enhancement
    Path: F4help à SAP Applications à Logistics general à Logistics Basic Data à
    Business partners à Vendor Master.
    Find the enhancement as VSV00002, which is an approximate user exit.
    Now search for different extensions like VSV00001. Then see for its components.
    Identify the appropriate user exit to be ‘EXIT_SAPLVV01_001’ (Create Export of
    Additional Customer Master Segments). This user exit can be used in outbound ALE
    process, meant for filling the data into custom segments. 
    You have to identify here another user exit as ‘EXIT_SAPLVV02_001’, which is
    helpful for inbound ALE process. This user exit can be used to read the segments
    and post it to Application repository. 
    Step9: Develop a project to encapsulate enhancements and components.
    Transaction: CMOD.
    Enhancement: custex and click Create to provide attributes.
    Click Enhancement Assignments.
    Provide VSV00001, short text and save.
    From the initial screen of the transaction, select components and click change.
    Find 4 components to be added.
    Activate them.
    Select user exit EXIT_SAPLVV01_001 for outbound process and double click it. It leads to function builder.
    Double click on provided include program ZXVSVU01 and press enter.
    Now, write supporting code for IDoc extension, i.e., populating custom segments in IDoc.
    Check the code and activate.  
    Code in ZXVSVU01
    *& Include           ZXVSVU01                                         *
    *In this scenario, the E1KNA11 has been extended to accommodate
    *User-defined fields in the customer table kna1. The name of the
    *extended
    *segment is z1kna11. There is one custom field: visitor
    *Data declarations
    DATA: kna1m like e1kna1m,
          kna11 like e1kna11,
          z1kna11 like z1kna11,
          w_kna1 like kna1. 
    make sure you are processing correct message type
    check message_type eq 'DEBMAS'.
    make sure data is added after the correct segment
    check segment_name eq 'E1KNA1M'.
    since customer number is not passed in this user exit, you need to go
    through the data records to find the customer number
    loop at idoc_data.
      case idoc_data-segnam.
         when 'E1KNA1M'.
           move idoc_data-sdata to kna1m.
         when 'E1KNA11'.
           move idoc_data-sdata to kna11.
      endcase.                             " case idoc_data-segname.
    endloop.                               " loop at idoc_data. 
    select data from the user-defined fields in kna11.
    select single *
      from kna1                            " Customer master table
      into w_kna1
    where kunnr = kna1m-kunnr.
    if sy-subrc eq 0.
    set the idoc extension name for control record
      idoc_cimtype = 'DEBMASEX'.
    clear custom fields from kna1 to extended segment
      clear z1kna11.
    copy custom fields from kna1 to extended segment 
    move-corresponding w_kna1 to z1kna11. " field name must be same
    condense all fields of extended segment
      condense: z1kna11-visitor.
    populate segment name in the data record, copy data contents into it 
    and append the data record to existing data records in
      move 'Z1KNA11' TO IDOC_data-segnam.    " administrative section
      move z1kna11 to idoc_data-sdata.       " data section 
      append idoc_data.
    endif.                                 " if sy-subrc eq 0.
    Step 10: 
    Define Logical System
    Assign client to Logical System
    Maintain RFC Destination
    Maintain Customer Distribution Model
    Generate Partner Profiles
    Distribute Customer Distribution Model
    INBOUND PROCESS
    Step 11: Append the custom structure to the table KNA1 similar to the process done
            in outbound process.
    Step 12.
    Define Logical System
    Assign client to Logical System
    Generate Partner Profiles
    Step 13. Execute the transaction to ‘Send Customers’ from Outbound system.
    Step 14. Now in the Inbound system, create the project in the similar way as done at
            outbound side.
    In the user exit EXIT_SAPLVV02_001, find include ‘ZXVSVU02’. Write the code to
    support IDoc extension.
    Code in ZXVSVU02
    *&  Include           ZXVSVU02                                         *
    data: kna1m like e1kna1m,
          kna11 like e1kna11,
          z1kna11 like z1kna11.
    data fs_kna1 type kna1.
    message i000(0) with 'INBOUND PROCESS CALLED'.
    LOOP AT IDOC_data.
      case idoc_data-segnam.
        when 'E1KNA1M'.
          kna1m = idoc_data-sdata.
        when 'E1KNA11'.
          kna11 = idoc_data-sdata.
        when 'Z1KNA11'.
          z1kna11 = idoc_data-sdata.
          select single *
            from kna1
            into fs_kna1
           where kunnr = kna1m-kunnr.
          if sy-subrc eq 0.
            update kna1
               set visitor = z1kna11-visitor
             where kunnr = kna1m-kunnr.
          else.
            idoc_status-docnum = idoc_control-docnum.
            idoc_status-status = '51'.
            idoc_status-msgty = 'E'.
            idoc_status-msgid = 'ZE'.
            idoc_status-msgno = '005'.
            idoc_status-msgv1 = kna1m-kunnr.
         append idoc_status.
          endif.                           " if sy-subrc eq 0.
      endcase.                             " case idoc_data-segnam.
    endloop.                               " LOOP AT IDOC_data.
    Step 15. Assign FM to extension/Message type
    Transaction:      WE57
    Path: Change à New Entries
    Select ‘IDOC_INPUT_DEBITOR’ against DEBMAS06 basic type, to fill extra
    information as shown below.
    Function Module          Basic Type     Message Type          Extension
    IDOC_INPUT_DEBITOR     DEBMAS06     DEBMAS          DEBMASEXT
    Step 16. Execute the transaction to ‘Get Customers’.
    And observe that records with extra data are saved in database.
    Rewards some points.
    Rgds,
    P.Nag

  • [IDOC] Test customized IDOC

    Hey,
    created a customized IDOC in system A and added an inbound
    process code.
    Now I would like to test the IDOC in we19 from system B, but the customized
    IDOC doesn't exist (of course) there.
    How to test this IDOC? Do I have to transport this in system B?
    Can I test IDOC also in system A himself? I just want to test if the configuration
    of process code works.
    In system A I can use we19 with standard inbound, but which receiver port do
    I have to use? I just have created a port to system B. For testing IDOC in just
    one system, do I have to create also a port/logical system to system A?
    thanks
    chris
    Edited by: Christian Riekenberg on Jul 8, 2008 4:18 PM

    I think you want to test only the process code calling the IDoc inbound function module correctly or not?
    If you have RFC connection between B to A. then go to WE19 create a dummy entry giving all the following details
    Receiver                            Sender
    Port                                Port                
    Partner No.                         Partner No.         
    Part. Type                          Part. Type          
    Partner Role                        Partner Role
    Message Type        
    and check in system A that IDoc you got received. It will show as an error , but that errors should shows it getting created in the inbound function module call
    a®

  • 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

  • Dump while testing Idoc from WE19-OBJECTS_OBJREF_NOT_ASSIGNED

    Hi Experts,
    I am trying to Post inbound PO idoc from we19 tcode.
    MessageType:PORDCR1
    Idoctype:PORDCR102
    FM:BAPI_IDOC_INPUT1
    while testing this Idoc it is going dump.
    Runtime Errors     :    OBJECTS_OBJREF_NOT_ASSIGNED
    Short text            :    Access via 'NULL' object reference not possible.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
         caught in
        procedure "PROCESS_COMPONENTS" "(FORM)", nor was it propagated by a RAISING
         clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component (variable: "L_ITEM").
        An object reference must point to an object (an instance of a class)
        before it can be used to access components.
        Either the reference was never set or it was set to 'NULL' using the
        CLEAR statement.
    Could you plz suggest how to resolve this issue.
    regards,
    Bhuvan.

    Hi,
    Please implement the OSS Note 1409498 (Relavent to your problem).
    I am sure it will resolve your issue.
    If not solving your than You can serch for relavent SAP note on SAP serivce market place.
    Regards,
    Lokesh.
    Edited by: Lokesh Tarey on Apr 15, 2010 2:31 PM
    Edited by: Lokesh Tarey on Apr 15, 2010 2:33 PM

  • How to Correct and Re-send new idoc # in WE19

    Hi Expert
    Can you please give me the steps to correct and re-send (new idoc) in WE19.
    Here is the situation:
    Outbound ASN failed in EDI for having special char in field ARKTX(E1EDK08-E1EDP07-E1EDP09-ARKTX).
    Here I just need to remove special character from the material description. I found the value where i need to make changes but from that point I don't know where to go in the screen to save that change and generate new idoc #.
    Please provide steps...
    Thanks in advance for you help !
    Thanks,
    Darshak

    Hi
    As suggested by Jurgen you need to follow the same step, i am just adding the screenshot to make it more visual
    Step 1
    Step 2
    Step 3
    STEP 4
    Remember you can make the change only for the failed idoc,if you will try to follow the above process for the IDoc which are in 53 /03 status system won't allow to make the change

  • IDOC - Delete unwanted segments and reprocess the IDOC by WE19

    HI all,
    I have an issue and wanted your help at this point of time.
    Case - Assume that an Idoc has been rejected by system due to few bad segments. Later i dentfied that in the Idoc few segments were bad and rest are good.
    If i use transaction WE19 for copying the Idoc and during selection of the segment if i delete the bad segments and copy the rest which are good. Will the Idoc be processed sucessfully with a new Idoc number so that the Bad segments i will fix it up manually in ERP. Kindly suggest. If possible let me know if any implication behind that or anything you like to add in the process to help me out.
    Kindly advice me.
    Regards,
    Pratap
    Edited by: pratap kumar on Dec 20, 2007 5:02 AM

    Hi Pratap,
    Which Idoc did you process. For each message type certain segments are Mandatory.
    for example in WPUBON01 -->following segments are mandatory
    Control Record --- Message type / Partner Type / Port / Server ID etc.....
    E1WPB01        --- Date / Time / Partner Number etc...
    E1WPB02        --- Article type / Article Number / Quantity etc...
    E1WPB03        --- Condition Type / Amount etc...
    E1WPB06        --- Payment method / Total Amount / card number etc...
    In control record we will have the  port / System ID etc.
    If other segments are not there leave it....it will process successfully.....
    To find out error segment refer  Table  EDID4 and correct the segment and post it.
    Regards,
    ManiKumaar

  • Help on ORDERS05 IDoc mapping..

    Hi Experts,
       Please help me out in finding out the IDoc Segment fields(ORDERS05) equivalent to the following SAP fields.
      20  Quantity             VBAP  KWMENG  Num(6)
      21  Unit of Measure  VBAP  VRKME      Char(3)
      22  Gross Price       KONV  KBETR       Curr(11.2)
      23  Discount           KONV  KBETR       Curr(11.2)
      24  Surcharge         KONV  KBETR       Curr(11.2)
      25  Net Value         KONV  KBETR       Curr(11.2)
      26  Cost Object 
      31 Payment Terms  VBKD  ZTERM      Char                E1EDK01 -ZTERM
      32 Footer Msg1      STXI     n/a             Char
      33 Footer Msg2      STXI     n/a             Char
      34 Footer Msg3      STXI     n/a             Char
      35 Total                 KONV  KBETR       Curr                E1EDS01 -SUMID (004)
           I thought for
               Quantity               :  E1EDP01-MENGE
               Unit of Measure    :  E1EDP01-MENEE
               Gross Price          :  E1EDP01-PREIS
               But when i went to WE19 and posted the idoc by populating the above segment fields its not getting updated in the sales order, instead in the created sales order it shows quantity as 0 and its not getting updated.
         so iam not sure whether these segment fields (in ORDERS05 IDoc) are the right fit for quantity, UoM and Gross price. Please provide me the correct segment fields mapping for the above SAP fields.
         Actually Gross price, surcharge, discount and Net value are calculated automatically by SAP while creating the sales order based on the amount and quantity entered - right..? Then do i need to populate the values for these fields also in IDoc for testing using WE19.
         Please reply me.
        Thanks in advance,
        karthik.

    In sales order,these quantity updating in Tatget quantity,look at VBAP Table ..
    You will get good idea..
    Reward Points if it is helpful
    Thanks
    Seshu

  • EDIDP02 Segment in ORDERS05 Idoc

    We are in the process of testing outbound and inbound idocs of PO order create and order confirmation.
    While testing manually in WE19, i can sucessfully post the idocs.
    But, from the sap notes and the forums I have gone thru, I have observed that inbound ORDERSP idoc errors out unless it has EDIDP02 segment to it.
    Does Outbound idoc also need to have this segment to it? If so how can i get it and send it to vendor ?
    I do not see in standard config this idoc segment getting populated. Is this segment only populated when vendor sends the confirmation to us , if so , how..
    Please let me know
    Points will be awarded
    Thanks
    AH

    Hi Guys ,
          I do have the same kind of requirement where i need to populate two additional segments of E1EDP05 in the INVOIC01 idoc. I have two questions.
    1. should i populate it in the inbound function module rite before posting or
    in the outbound function module before its being created.
    2. Which user exit should i use.
    3.The data i need to add , should it be hard coded, because ive already been given the doc saying that i should populate two segments of E1EDP05 in IDOC with currency types 12 and 31.
    Guys Its a little urgent.
    Thanks,
    Venkat

  • Error while testing Inbound Idoc

    The error message "Interface for function Z***** is incorrect*." is shown while trying to test an incoming IDOC in we19.
    PL HELP!!!!!!!
    The procedure followed by me was,
    WE31 created custom segments,
    WE30 Created custom basic type,
    we81  Custom message type,
    se37 function module,
    we82,
    we57,
    bd51,
    we42,
    bd67,
    we20,
    Am not able to figure out why exactly is the error message being shown.
    please tell me if a step was missed or what the possible error is, I think the parameters of function module are correct....

    Hi friend,
    if it is help full please give max reward point.
    Standard program, RBDMOIND is scheduled or executed online to determine whether the communication was successful. If IDoc is Dispatched to destination system, RBDMOIND updates the status of the IDoc to 12 (Dispatched OK), Otherwise remains in status 03.
    Two programs enable cross-system reporting:
         RBDSTATE: It reports the status of the incoming IDocs to sending system, using ALEAUD message and ALEAUD01 IDoc
         RBDAUD01: It executed on sending system to analysis the audit log and display the output as a report          
    IDoc Status in Receiving System          IDoc status in Sending System via ALEAUD
    53 – Application docu posted     =>     41 – Application docu created in receiving sys
    51 – Error: Application docu      =>     39 – IDoc in receiving sys. Status repeated
         not posted                         each time RBDSTATE runs.
    68 – Error: No further processing     =>     40 – Application docu not created
    ALE Auditing
    BDM7          =>     ALE Audit: Statistical Analysis
    BDM8          =>     ALE Audit: Sending the Confirmations
    RBDSTATE     =>     Run on Receiving System to return Audit Message

  • How to Test, Inbound idoc ,with out the Sender System, using a Text File

    Hi Guru's .
    we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
    on the same client.
    we wanted to test this idoc with text file from our local machine.
    Can anyone give us detail steps.like how to create  File layout
    with Segment name,and values for the fields.how to pass this file to the system.
    Thanks in advance.

    Hi Aparna.
    My requirement is to test the idoc with Inbound File.
    Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
    when i am trying to do this syst complaing about
    Partner Profile not available, and some times
    port not available. and some  times with
    'No further processing defined'.
    but i maintained part profiles and port perfectly.
    Can you help me in testing with test 'File' port.

  • Need to change the segment data in Inbound ORDERS05 IDOC

    Hi:
    I need to change sales area coming in E1EDK14 segment. I need to determine SAP sales area stored in TVARV table and pass it to the E1EDK14 segment.
    I am using exit EXIT_SAPLVEDA_002. In this I am looping DIDOC_DATA and checking if segment is E1EDK14 and then writing my logic and modifying the DIDOC_DATA. I am also modfying DXBDCDATA. However the fields are properly getting populated on screen but  when I went WE05 to check the IDOC the changed fields are not getting reflected in IDOC.
    Please let me know where else I have to change in order to show it in IDOC.
    Thanks.

    Toni,
    I atlast tried IDOC_DATA_MAPPER BADI and it is working fine for me.
    Appreciate your help.
    The following is the sample code I wrote inside the BADI.
    LOOP at data into wa-data.
       CASE wa_data-segnam.
           when 'E1EDP01'.
               wa_mapp-segnum    = wa_data-segnum.
              wa_mapp-feldname   = MATNR.
              wa_mapp-value         = '000000000000115123'.
              wa_mapp-save_type = c_x.
              APPEND wa_mapp TO mapping_tab.
            MOVE 'X' TO have_to_change.   "IDOC Data have to be changed with newly determined values
            IF protocol-stamid IS INITIAL.       "Populate with atleast one value
              protocol-stamid = 'ZMM'.
            ENDIF.
            IF protocol-stamno IS INITIAL.
              protocol-stamno = '001'.
            ENDIF.
       ENDCASE.
    ENDLOOP.
    Thanks.

  • Testing of Idoc to file scenario

    Hi Gurus,
    I have completed the Idoc to file scenario, But how should I test the whole scenario??!!
    Because of my functional guy is absent for this week and I do want to test my scenario, whether its working properly or not??!!
    Note: As I knew, we19 tcode, it asks some Idoc number and other info to do the same.. could you please help me out?!!
    Thanks.,
    Stallin

    Hi
    Just for testing purpose..you can use WE19..
    First goto transaction WE02 and put Basic type : MATMAS03 as filter criteria, change your creation date to select little old idocs and run...on next screen your will see number of idocs "MATMAS03" with green status(if there is any in that period..otheriwse change period again).
    Then goto WE19 and put existing idoc number in the field existing idoc and and presss F8...On next screen press "Standard outbound processing".
    Can also use we19 and change control record ( Double click in EDIDC segment) to your sender / recever partner profile.. and run
    Thanks

Maybe you are looking for