Problem in IDOC ORDERS04 Extension

Hi all,
Can any one guide me how to extend ORDERS04 outbound IDOC whenever triggered with ME22N

if you want to extend idoc
you can do it by going to transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
then creating a new idoc.
after that when a screen comes opt for "create as copy"
and give name orders04 give discription and continue.
now you can add new segments( or alter the segment structure)
you can refer http://www.sapgenie.com/ale/whitepaper.htm
document .
hope this will help you.
if it doesn't help reply.
regards,
Hemendra

Similar Messages

  • Problem in Idoc type

    Hi Experts,
    I am facing one strange issue in idocs.
    I am having a scenario where for particular LS i have assigned HRMD_A06 basic type and ZHRMD_A06 extension in partner profile.
    and i am trying to implement badi HRALE00OUTBOUND_IDOC.
    in this badi at runtime wrong message type is getting picked up at the runtime(checked in debugging). But at the end it displays proper basic type.
    so for me it is getting difficult to write logic in this badi.
    Please guide is there any particular setting apart from partner profile where we assign message type to LS.

    Hi,
    In problem in idoc type , that below link will helpful to you.
    Try this link,
    http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/technology/sap/18/
    Regards,
    Sekhar

  • Problems with IDOCS

    Hi everyone!
    I'm working with IDOCs and I am having the following problem:
    I'm modifiying a specific standart IDOC (DELVRY03), adding a new structure called ZSTRUCTURE. When making an example to create the IDOC I am not able to find the new structure that I have just created in the IDOC.
    Does anybody know why? Maybe the structure is empty, is this a problem?
    Thank you very much.
    Regards

    hi,
       I dont think u can direct modify sap standard idoc type.
       Instead u can go for Idoc extension.
       Create structure ie segment u want to add say EDIT->set release
        and in we30 choose extension create zobject type  with extension as standard idoc and choose EDIT->set release
       and goto we80 add msgtype,Basic idoc type, extension.
       I think this will  fix ur problem.
    Regards
    Shanmukhi

  • Communication problem the web server extension (WGATE) failed to receive a

    Hi,
    When a user tries to access his timesheet he get the below error:
    <b>communication problem the web server extension (WGATE) failed to receive a response from the ITS web service</b>
    Only ONE user is getting this error. If everyone get\s the same we can check on the ITS side, but if only ONE user is getting it.
    Please help.
    Regards,
    PK

    HI ALL,
    Thanks for your time. The issue got resolved however without cheking the logs itself. The problem was with the scripfile. All other users and all other scripts were working, except one. And it got recified.
    Regards,
    P. Kumaravel.

  • Problem in Idoc creation in ME22N

    Hi All,
    We are facing a problem in Idoc creation in transaction ME22N.Our requirement is to trigger an output type and create a idoc everytime a change is made to a particular Purchase Order.
    Presently however,for some vendors,when we change the plant at the item level,an Idoc is not created(with a message that the changes are not relevant to create an Idoc).Any other change to the Purchase Order like changes in quantity or price,results in successful Idoc creation.
    We have also noticed that this happens only in the case of certain vendors.The Customer Info records and vendor data are all believed to be fine.
    Are any other config settings required to be maintained for this?
    Thanks in advance!
    Regards,
    Nejuma Iqbal

    Hi Nejuma,
    I don't think there is any problem with cofiguration settings.u r getting the idocs for some vendors .
    if iam not wrong u r giving LS in the tcode(we20).The method which u r using is change pointers.As u r using standard idoc all the settings will be done.
    Only settings u have to do is
    1>generate partner profiles(WE20)
    2>Distribute model view(BD64).
    REGARDS,
    Nagaraj

  • HR Programming :  Problem with IDOC HRMD_A

    Hello ,
    We use Idoc HRMD_A for transferring PA records from
    one R3 system (ECC5) to another R3 system (46d).
    We have a problem - The Idoc doesn't check the data
    inserted against the database check tables and
    inserts wrong values into the target system database.
    (At least that what has happened when we transferred
    wrong value of MASSN in 0000 records).
    Is there something we can do ?
    Maybe - Some flag we can sign in order a check against check tables will be done ?
    Is it a problem with this IDOC ?
    Thanks .
    I appreciate any help.
    Nitzan S.

    Consultancy note 134085 :
    "Ultimately you are responsible for consistency of this data. SAP saves this data directly on the database without checking the single fields and consistency of the data records (time constraints check, writing change pointers, value check) because the consistency for an R/3 - R/3 lingage is of course ensured."
    The IDOCs were intended for R3->R3 data replication, and not for data loads/interfacing. Since you're having problems, I'm guessing in addition they require the same SAP version as well.

  • Problem with IDoc scenario - IDocs do not aarive to XI

    Hi guys!
    I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
    REALLY strange...
    Any suggestions?
    IDX2 metadata loaded.. I think, all needed settings are done.
    Question - do I need to set up LS in XI ABAP part?
    Thanx, Olian!
    P.

    Hi Olian ,
    just check if u have followed all the following steps
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2) a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name
    Regards,
    AshwinM

  • Problem sending IDOC DESADV  /AFS/DELVRY03 to XI

    Hi Gurus,
    I have problems sending IDOCs DESADV (basic type /AFS/DELVRY03) created by function LSEND_IDOC to XI system. IDOC is correctly created by R3 system (AFS ECC 5.0) and correctly sent on the XI port (Status: Data passed to port OK - 03), but XI system doesn't receive IDOC.
    If I resend the same IDOC by WE19 tcode goes ok!!
    In R3 sending system nothing warnings/errors in syslog or sm58.
    Any suggests? Thanks in advance.

    Issue solved! It is necessary close the master idoc with a commit

  • XI IDOC ORDERS04 create sales order update VBKD_BSARK

    Hello
    I have created a sales order interface from an external partner who sends a file (Purchase order), XI reads and transfers to R/3 via IDOC ORDERS04 to create the sales order.  this works fine, but i need the purchase order type field VBKD-BSARK to be updated for further processing of order confirmations and deliveries (the customer also has manual orders created which are handled differently).
    in the XI mapping i have mapped the required entry for VBKD-BSARK into E1EDP02-BSARK, but it does not work.  I notice that this is at line itme level.  i have had a good look through the segements in ORDERS04 but I cannot find any reference to PO type.
    I also tried mapping the required data to E1EDK14 'QUALF'=013 .. this did not work either.  i use FM IDOC_INPUT_ORDERS and can only find reference to vbap-bsark  but this is not working.  it always takes the default setting.
    Does anyone have any ideas?  I have to use ORDERS04 as we have user enhancements for sales orders that are not available with SALESOREDERCREATEFROMDAT2.  which may work ok.
    cheers
    Nick

    Hi,
    Can u tell me the steps to create a sales order using idoc, i've created a bapi but thats a temprory use. I wanted to created a sales order automatically when a purchase order is saved after data entry is completed.
    Please let me know if u can help me, i wanted to do it using idoc
    Regards
    Sanju

  • Problems with specifying File Extension of E-Mail attachment

    Hi everybody
    I have a problem that seems to be so simple that it almost drives me crazy that I cannot find a solution for it.
    I need to send the content of an internal table (some lines) as a mail attachment to a specified mail address.
    The format should be normal ASCII, so when I open it with any text editor (e.g. Notepad),  I want to have all my lines there (including CR/LF).
    The problem now is - The extension of this mail attachment must be ".key", so the attached file should have the name "L_12345.key" (for example).
    For E-Mailing I use FM "SO_NEW_DOCUMENT_ATT_SEND_API1".
    This part works fine, also the attachment part works in general.  (I receive the mail and I receive the attachment).
    BUT I get either an attachment with the name "L_12345.txt" or "L_12345.key.txt" and in correct format, or I get an attachment "L_12345.key", where the name is correct but format is wrong (no CR/LF - everything in one line).
    Example:
    =======
    Attachment-Content should be:
    Line 1
    Line 2
    Line 3
    Name of Attachment should be: L_12345.key
    What I tried:
    TEST 1 **
    Declare Attachment in Packing list. ..
      ls_packing_list-transf_bin   = ' '.
      ls_packing_list-head_start   = 1.
      ls_packing_list-head_num     = 0.
      ls_packing_list-body_start   = 7.  "Startline of Attachment
      ls_packing_list-body_num     = 3.  "No of Attachment lines
      ls_packing_list-doc_type     = 'RAW'. 
      ls_packing_list-doc_size     = 3 * 255.
      ls_packing_list-obj_name     = 'ATT01'.
      ls_packing_list-obj_descr    = 'L_12345'   "Attachment name
      APPEND ls_packing_list TO lt_packing_list.
    ==> Result: Attachment Filename = L_12345.txt
    ==> File as I need it (ASCII with CR/LF), but extension wrong
        Line 1
        Line 2
        Line 3
    TEST 2 **
    Same as TEST 1, but with:
      ls_packing_list-obj_descr    = 'L_12345.KEY'   "Attachment name
    ==> Result: Attachment Filename = L_12345.KEY.txt
    ==> File as I need it (ASCII with CR/LF), but extension wrong
        Line 1
        Line 2
        Line 3
    TEST 3 **
    Declare Attachment in Packing list. ..
      ls_packing_list-transf_bin   = ' '.
      ls_packing_list-head_start   = 1.
      ls_packing_list-head_num     = 0.
      ls_packing_list-body_start   = 7.  "Startline of Attachment
      ls_packing_list-body_num     = 3.  "No of Attachment lines
      ls_packing_list-doc_type     = 'KEY'.
      ls_packing_list-doc_size     = 3 * 255.
      ls_packing_list-obj_name     = 'ATT01'.
      ls_packing_list-obj_descr    = 'L_12345'. "Attachment name
      APPEND ls_packing_list TO lt_packing_list.
    ==> Result: Attachment Filename = L_12345.KEY
    ==> File Format is wrong:
        Line 1          Line 2     Line3
    I have tried several other Extensions (DOC_TYPE), it seems, that the File format is only correct with "RAW", but it seems with "RAW" SAP adds ".txt" as extension to the filename.
    Does anyone know how I can achieve having an e-mail attachment with multiple text lines and name "<anyname>.key"
    Any help (if possible with example code ?) would be highly appreciated.
    Many thanks
    Harald

    hi,
    check the following code.
    *&      Form  send_email
    FORM send_email.
    CLASS cl_abap_char_utilities DEFINITION LOAD.
    CONSTANTS: con_cret TYPE c VALUE cl_abap_char_utilities=>cr_lf.
    *Body of mail
      CLEAR objtxt.
      CLEAR objtxt[].
      objtxt = 'Dear abc'.
      APPEND objtxt.
      CLEAR objtxt.
      APPEND objtxt.
      objtxt = 'Attached herewith is the detail list of materials.'.
      APPEND objtxt.
      CLEAR objtxt.
      APPEND objtxt.
      objtxt = 'Regards,'.
      APPEND objtxt.
      objtxt = 'Admin'.
      APPEND objtxt.
      DESCRIBE TABLE objtxt LINES tab_lines.
      READ TABLE objtxt INDEX tab_lines.
    *Mail description
      CLEAR docdata.
      docdata-doc_size  = ( tab_lines - 1 ) * 255 + STRLEN( objtxt ).
      docdata-obj_name  = 'List'.
      docdata-obj_descr = 'List of materials'.
      docdata-obj_langu = sy-langu.
    *Packing list for main document
      CLEAR objpack.
      CLEAR objpack[].
      objpack-head_start = 1.
      objpack-head_num   = 0.
      objpack-body_start = 1.
      objpack-body_num   = tab_lines.
      objpack-doc_type   = 'RAW'.
      APPEND objpack.
    *Attachment data
      CLEAR objbin.
      CLEAR objbin[].
      CONCATENATE
            'field1' 'field2' 'field3' 'field4'
        INTO objbin SEPARATED BY ','.
      CONCATENATE con_cret objbin INTO objbin.
      APPEND objbin.
      LOOP AT it_material_list INTO wa_material_list.
        MOVE-CORRESPONDING wa_material_list TO wa_char_material_list.
        CONCATENATE
              wa_char_material_list-field1
              wa_char_material_list-field2
              wa_char_material_list-field3
              wa_char_material_list-field4
          INTO objbin SEPARATED BY con_tab.
        CONCATENATE con_cret objbin INTO objbin.
        APPEND objbin.
        CLEAR objbin.
        CLEAR wa_char_employee_list.
      ENDLOOP.
      DESCRIBE TABLE objbin LINES tab_lines.
      READ TABLE objbin INDEX tab_lines.
    *Packing list for attachment document
      CLEAR objpack.
      objpack-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objbin ).
      objpack-transf_bin = 'X'.          "check these values
      objpack-head_start = 1.          "check these values
      objpack-head_num   = 1.          "check these values
      objpack-body_start = 1.          "check these values
      objpack-body_num   = tab_lines.
      objpack-doc_type   = 'KEY'.
      objpack-obj_name   = 'Attachment'.
      objpack-obj_descr  = 'Report.KEY'.
      APPEND objpack.
    *Email receiver's list
      CLEAR reclist.
      CLEAR reclist[].
      reclist-receiver = mail_id.
      reclist-rec_type = 'U'.
      APPEND reclist.
    *Function module to send email with an attachment
      CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
        EXPORTING
          document_data              = docdata
          put_in_outbox              = 'X'
          commit_work                = 'X'
        TABLES
          packing_list               = objpack
          contents_bin               = objbin
          contents_txt               = objtxt
          receivers                  = reclist
        EXCEPTIONS
          too_many_receivers         = 1
          document_not_sent          = 2
          document_type_not_exist    = 3
          operation_no_authorization = 4
          parameter_error            = 5
          x_error                    = 6
          enqueue_error              = 7
          OTHERS                     = 8.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
    ENDFORM.                    "send_email
    Edited by: vikram shah on Sep 25, 2008 5:28 PM

  • Problem with idoc DEBMAS

    Hi everybody.
    We have a problem with idoc DEBMAS.
    This idoc is sent from R3 to PI throw change pointers then the idoc is field only with the data modified in the master custumer.
    We need the information fill it in the segment /IDOC/E1KNA1M/E1KNVVM to determine the receiver determination but this segment is not always sent.
    What can be done in R3 to send always this segment.
    We dont want to sent the whole data but always this segment.
    Any idea???
    Thanks a lot!!!!!

    Hi,
    As E1KNVVM segement is not mandatory, when you are triggering IDoc based on change poitner data might not populted in the E1KNVVM segment until some sales data is changed.
    if you need that segement always just copy the Idoc type and make it mandaotry field.
    otherwise yoy can populate some fields like STDVRS with the reruried constant and can use in your receiver determination.
    Regards,
    Suresh

  • SAP IDOC ORDERS04 Doc type support ?

    How do I get an update for specbuilder that has the SAP-IDOC ORDERS04 document type ?

    Hello,
    It is not available in B2B Document editor standards library.
    SAP used to provide these on their website at http://ifr.sap.com/catalog/query.asp
    However, that page was removed about a year ago. There is an article about it here
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5520
    Rgds,Ramesh

  • Error while Importing Idoc with Extension

    Hi All,
      I already imported idoc with extension and working fine. When I tried to transport the Idoc from Dev XI to Prd XI . I got the following error
    The objects as displayed in the navigation tree are possibly not up-to-date.
    So I tried to Re import the Idoc in IR but it is ending with below error
      + com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: The objects as displayed in the navigation tree are possibly not up-to-date.
    I already saw some threads in SDN for this error but I am not getting solution.
    Can anyone provide a solution ASAP for the above error .
    Regards,
    Prakash

    > When I tried to transport the Idoc from Dev XI to Prd XI . I got the following error
    Why are you transporting it form Dev? Why not from QA to Prd.
    Since this is a Z-IDOC so check if the extension has been released from R3 after doing any modification.
    Regards,
    Sarvesh

  • Problem in IDOC generation

    Hi Freinds,
    I am facing some problem in IDOC creation . We have used MATMAS03 as basic  type. And activated the chang poineter. But for some materials it is not generating IDOC.
    When we saw table BDCPS with the change pointer number from BDCP it is showing some other Message type MATMASAD instead of MATMAS for the materials for wch IDOCS not sent. Can you please tell me where it is getting from  this message type .

    Hi,
          check with below mentioned  tcodes.  
          BD50 - This tcode for Activate Change Pointer for Msg Type.
          BD52 - Tcode for Activate change pointer per change.doc object  or  record.
        Goto BD52 -> enter the message type as 'matmas'  and enter.so that u find the object type,table name and field name.
          The status of change pointer can easily be checked from   BDCPV table/view.

  • Mapping ansix12 to idoc orders04

    hi ,
    I have created the data type in the integration repository and i bought the message type for message mapping, but i need to know how to map this with idoc  orders04 and im not sure with the loop concept in XI for mapping. like mapping for more than one line item.
    if any one have any idea idea abt it pls helpme.
    thankx.

    hi ,
    I have to map the ansi x12 file to idoc meta data and for mapping do i need to write a XML schema for the the ansix12 file .. i need help reagrding this .
    thankx .

Maybe you are looking for