IDOC Setup

Dear Experts,
I need to do a IDOC setup for inbound IDOCS in SAP ERP.
After doing all the steps I think I have, I use We19 to do get an IDOC using an existing one and modifying the sender and receiver. I try to find the Functional module for inbound idocs which I dont seem to.What steps I have to do to ensure this that when I use my new defined message type linked to the Functional Module.
After I execute the IDOC I get a message EDI: Receiver port in control record is invalid.
I have maintained the partner profile (We20)also with new logical system which is sender (outside of SAP) to the SAP which es already defined as a port.
EDI: Partner profile not available
Need your help

Hi Andy,
check the ALE settings again:
Here is a quick guide for you:
First of all you need two logical systems, one will act as sender and other as reciever .
1)Define logical systems through BD54.
2) Assign clients to logical systems (SCC4)
3) Create RFC Destination (SM59)
4) create port(we21)
5) Create Partner profile
If all these steps are done then go to BD64, there
1) Create Model view
2) Mention your sender and Reciever for that Model (logical systems)
3) Mention The message type
4) Distribute your model view through Environment -> Distribute
If model view is distributed sucessfully that means messages can flow sucessfully between two systems. To ensure your your model view is distributed sucessfully, take special care while setting up partner profiles in sending and recieving system.
Now please ensure that you have not missed any step and all steps are carried out sucessfully.
Regards
Vinod

Similar Messages

  • Idoc Setup For Automatic Payments

    could any body share Step for IDoc setup for  Automatic Payments?
    Thanx in in advance.
    Indra.

    Idoc Setup For Automatic Payments .

  • Idoc setup::Partner profile for Logical system

    HI All,
    I am using Idocs to transmit my invoice details from ECC to PI, but every time I do this for a new customer I have to setup a partner profile for the customer whose invoice is to be sent. I setup the partner profile using WE20, I setup the partner profile for partner type KU(Customer) in the we20,
    Is there any way we can setup partner profile for LS(Logical system) in we20 & I don't have to setup partner profile for each & every customer for which Idoc is to be generated.
    Please provide some useful information/help to handle this business scenario.
    Regards, 
    Saurav Singh

    Hi Saurabh,
    Please refer SAP Note 1103146 and check.
    Please also refer the below link:-
    http://www.sapgeek.net/2011/07/sap-idoc-tutorial-maintain-partner-profile/
    Thanks & regards,
    Rahul Verulkar

  • ALE / IDOC setup

    I did ALE setup to Send Idoc from R/3 to XI. I generated Idoc and sent to XI. Idoc status on R/3 is 03 - Idoc sent to R/3 System or external program ).
    In XI I did setup Port for R/3 system using IDX1.
    However the Idoc sent from R/3 to XI did not reached XI. What could be a problem ?. Would someone guide me please.
    I did everything one possibly do using step by step guide.
    When I do consistency check using BDM5, all messages are green and one in RED with folowing message
    Checks in Partner System XXXXXXXXX
    Test function in partner system : connection closed

    Hi Ram,
    As Bhavesh told, check in transaction sm58 if u can see any errors.
    Did u create port SAP<SID> in “idx1” in the XI box and relevant RFC destination for the same from XI Box to sending system?
    Also see if these links help you...
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
    Where is my IDoc??? Sent from R/3 to XI
    Configuring to receive a iDoc in R/3 sent by XI
    Regards,
    Abhy
    Message was edited by: Abhy Thomas

  • IDOC setup for SLD

    Dear XI experts,
    I woule like to ask you when I want to do the PI setup for IDOC sending and receiving in the SLD, as to what steps I have to take for this. I had done the setup and chosen ABAP as a choice in the Technical and Business system, however, I am not clear where I should define the Integration server to be able to choose this when I create a Technical and Business system and do the assignment of the Integration server.
    Perhaps I need to do step by step the SLD setup for  IDOC sending and receiving from SAP Backend and viceversa to find what I am missing.
    Thanks for your input.
    Best regards

    Hello,
    Check this blog "How To Configure IDoc Adapters" https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
    It consist all setting including all steps required for SLD.
    BR,
    Dzmitry

  • REMADV Idoc setup

    I want to send REMADV Idoc (remitance advice) to vendors after payment run F110 is complete. I have completed following steps
    1. in Vendor master checked the flag for "Pay. Adv. by EDI)
    2. Maintained variant for program RFFOEDI1 and selected variant in F110.
    3. maintained partner profile for vendor. with message type REMADV, Idoc type "PEXR2002".
    After I run payment run, I do not get the Idoc. The log shows that no records selected for RFFOEDI1.
    Can some please let me know what I am missing?
    Thank you
    Shrikant

    In program there is a check for field REGUH-EDIBN. In our case the field is blank, and that is why the data does not get selected. Any ideas what needs to be done so that the field have value is 'X". I have maintained partner profile for vendor ( without message control) already.
    Shrikant

  • Scheduling Agreement --- IDOC Setup

    Hi,
    Please let me know the Configuration for SA for Inbound & Outbound IDOC
    Regards
    Amey Kulkarni

    HI,
    I don't know if you're talking about SD Schedulling Agreements or MM Purchasing Schedulling Agreements.
    For the second type there is also an important IDOC output:
    - message type: DELFOR / DELJIT
    - basic type: DELFOR02
    that carries Delivery Schedule Forecast and/or JiT lines that you release and send to supplier.
    to receive despatch advice from Supplier there is:
    - message type: DESADV
    This messages are predefined in SAP so you only need to set them in WE20 t-code for each Supplier as partner.
    To outbound Delivery Schedule with IDOC (EDI)  it is also needed to maintain Output type LPH1 in MN10 t-code and sometimes in SPRO in Message settings for Schedulling Agreement Delvr Schd release output,
    Best Regards,
    Tomek

  • ALE/EDI : IDoc Setup

    Hello...
    While setting Partner Profile when I am assigning the process code & FM Name it giving me the following error
    Application object type is not planned
    Message no. B1405
    Diagnosis
    The application object type '' is not permissible for the input function module 'Z_IDOC_INPUT_ZORDER01'.
    Something wrong with the FM I guess.... Some setting I am missing...
    Let me tell What all I have done....
    (1) WE30
    (2) WE81 - Message Type
    (3) BD59 - Object Type
    (4) WE57 - Linking Message type to FM
    (5) BD51 - FM settings
    (6) WE20 - Partner Profile....
    On step six its giving the above error....
    Please Guide how to resolve this issue....
    Thanks & Warm Regards
    Ankur Jain

    Hai Ankur
    check the following Links
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    ALE and IDOCs
    iDocs
    IDOCs !!!!!! need your help
    idocs
    ALE, EDI and IDOCS
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    ALE---IDOC Creation Steps
    01 Error --> Idoc Added
    30 Error --> Idoc ready for dispatch(ALE Service)
    then goto SE38 --> Execute the Program RBDMIDOC
    29 Error --> ALE Service Layer
    then goto SE38 --> Execute the Program RSEOUT00
    03 Error --> Data Passed to Port ok
    then goto SE38 --> Execute the Program RBDMOIND
    12 Error --> Dispatch ok
    Inbound Status Codes
    50 Error --> It will go for ALE Service Layer
    56 Error --> Idoc with Errors added
    51 Error --> Application Document not posted
    65 Error --> Error in ALE Service Layer
    for 51 or 56 Errors do the following steps
    goto WE19 > give the IDOC Number and Execute>
    Press on Inbound function Module
    for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
    ALE IDOC
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Create Model View
    Tcode BD82 ? Generate partner Profiles & Create Ports
    Tcode BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 !V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Thanks & regards
    Sreenivasulu P

  • IDOC Listener setup in SAP 4.6C

    Hello,
    from the documentation I've found the Idoc setup should be quite standard, but still real life is different. The 4.6C system here has no registered server program option in the SM59. When I try to test the connection I get the following error: program <PROGID> not registered / CPI-C error CM_ALLOCATE_FAILURE_RETRY.
    The operating system is HP-UX.
    I would be glad to receive any hints.
    Kind Regards,
    Christoph Mertins

    https://forums.sdn.sap.com/click.jspa?searchID=12426260&messageID=5211759 might help.
    As this question is not directly related to MII would suggest you to search other forums as well.

  • IDOC ISSUE full point assigned

    Hi all
    I m facing problem to upload data through idoc.the scenario is like we receive electric meter reading in flat file format. And to upload that data JAVA code is written which will create an IDOC FILE this authorization is only give to 2-3 person in organization and to basis guy also as user changed it’s password in SAP and in JAVA the java code is not going to create the IDOC file and data is not going to upload. after changing user password in sap system ,user not able to upload the data.
    ISU_MR_UPLOAD01 is the idoc file generated. So is there any authorization issue, password issue how to see and view IDOC IN SAP, can any one help me out into this.
    The error with java throws is as;
    1ST ERROR IN TRACE FILE
    ERROR file opened at 20061109 133610 India Standard, SAP-REL 640,0,59 RFC-VER 3  MT-SL
    T:2736 ======> User TR has no RFC authorization for function group SYST .
    T:2736 <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
    2ND ERROR ON COMMAND PROMT
    C:\j2sdk1.4.2_07>cd bin
    C:\j2sdk1.4.2_07\bin>java sandsupload
    Creating IDoc...Exception in thread "main" com.sap.mw.idoc.IDoc$Exception: (2) I
    DOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ISU_MR_UPLOAD01
    " is unavailable.
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:233)
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:187)
            at com.sap.mw.idoc.jco.JCoIDoc.createDocument(JCoIDoc.java:10521)
            at sandsupload.main(sandsupload.java:35)
    the part of java code
    try {
                //create a JCo client pool
                JCO.addClientPool( "MyPool",    //pool name
                                   3,           //maximum pool connections
                                   "333",       //SAP client
                                   " TR",    //user ID
                                   " XYZ",  //password
                                   "EN",        //language
                                   " 1.1.1.1   ", //app server host name
                                   "00" );   //system number
                //create an IDoc repository
                IDoc.Repository idocRep = JCoIDoc.createRepository("MyIDocRepository", "MyPool");
                //create a new and empty MATMAS02 document
                System.out.print("Creating IDoc...");
         Line where it shows error
                IDoc.Document doc = JCoIDoc.createDocument(idocRep, "ISU_MR_UPLOAD01");
                //get the root segment from the document
                //The root segment does not contain any fields or data. It is only
                //used as the standard parent segment and won't be transmitted when
                //the document is sent to an SAP system.
                IDoc.Segment segment = doc.getRootSegment();
                //create and add a new and empty child segment of type E1MARAM
                //and fill the segment data

    Seems like the error is because the user passed through the JCO call does not have the necessary authorizations...in SAP. Trace the authorizations for that user and grant what is needed... in particular the functions about the IDOC setup and structure used by the repository...
    Enjoy

  • Using IDoc to convert Purchase Order as Sale Order between two Company code

    Dear Experts,
    We are in need of implementing IDoc.
    We have 2 Company codes. One in US and another in India.
    The US Company receives Customer Order and PR is generated automatically for the Third Party Sale Order.
    The PO is also generated based on this PR against the Vendor code (Indian Company actually created as a Vendor code also)
    Now, the PO from Us Company should be converted as Order in Indian Company. The PO sending Plant is the Customer in this case.
    Now,
    1. How we go about this using IDoc.
    2.How do we capture the Sold-to-Party ( US Compnay in thsi case) and the Ship-to-Party ( Direct Customer of US Company)
    Please share your experties on this.
    Regards,
    Ramki

    Hi Ramki,
    Since the goods are selling between 2 company codes.. you should ideally use inter company process i.e. choose plant as Indian plant and etc..pls search the forum for intercompany process set up or refer to the setup required for Intercompany :
    [http://www.sap-img.com/sap-sd/inter-company-sales-process.htm]
    The above setup will help you in dealing with your question 2.
    On question 1: Once you setup the intercompany you won't require IDocs setup.
    I hope this helps.
    Regards,
    Raghu.

  • Userexit in idoc

    Hi Friends,
    I have one extension idoc type requirement, now i want to insert the code in userexit. how can i find the user exit related to the idoc.

    Hi,
      can u explen what is your Scenario, here i am given some userexit for idoc.
    u can find it from SMOD
    MWMIDO01
    MWMIDO02
    MWMIDO03
    MWMIDO04
    MWMIDO07
    MWMIDO08
    MWMIDO09
    MWMIDO10
    MWMIDO11
    MWMIDO12
    MWMIDO13
    SIDOC001
    SIDOC002
    EX......
    MWMIDO01 (User Exit)
    With this user exit, the contents and structure of IDOC WMTOID01
    'Transfer order' can be influenced customer-specifically in the outbox.
    Call transaction and other important requirements
    The user exit is performed in the function module that sets up IDOC
    WMTOID01. This is done after the IDOC setup but before it is transferre
    to the ALE interface. The standard function module for setting up IDOC
    WMTOID01 is called L_IDOC_CREATE_WMTOID01. The IDOC setup is part of th
    transfer order generation. This means that the source code can run both
    asynchronously in the update program and online. For this reason, all
    error messages must be issued as abend messages to guarantee a correct
    termination with rollback. Furthermore, you must not use any key words
    such as COMMIT WORK, ROLLBACK WORK, LEAVE, or the like.
    Parameters and options
    The user exit in the program is function module EXIT_SAPLLIDO_001. In
    order to be able to use the user exit, you must create Include ZXLIDU01 and activate the enhancement with transaction CMOD. As parameters, you
    can use the transfer order and IDOC data:
    o   TO header (import parameter I_LTAK)
    o   TO items (table parameter T_LTAP)
    o   Control record of the IDOC that has been set up (import parameter
         X_IDOC_CONTROL)
    o   Data records of the IDOC that has been set up (table parameter
         T_IDOC_DATA)
    This user exit can basically be used to:
    o   change or redetermine the data in IDOC WMTOID01 that were determined
         during the standard procedure or provide partners with additional
         information using empty fields of this IDOC.
    o   change or enhance the data for controlling the IDOC processing in
         the control record of the IDOC.
      o   If you enhanced the basic IDOC WMTOID01 with your own segments, you
          have to fill these segments including the necessary data.
      The user exit returns the modified IDOC data to the calling program by
      means of the following parameters:
      o   Control record of the IDOC that has been set up (export parameter
          X_IDOC_CONTROL)
      o   Data records of the IDOC that has been set up (table parameter
          T_IDOC_DATA)
      The modified IDOC is passed on by the calling program to the ALE
      interface for sending.
      Although changes to table T_LTAP are without any meaning, they should
      still not be made.
      Examples
      Below, you will find some conceivable changes including the necessary
      source code.
      o   You want to send additional data on TO item level. These data are
          transferred in the standard segment of IDOC WMTOID01.
          With field 'Goods recipient', information is transferred whether the
          external system should additionally print accompanying documents for
          the sent transfer order. The indicator for printout from the TO
          header and the printer from the TO items are specified in this
          field.
          In addition, a separate description is written into the field
          'Unloading point'.
      INCLUDE ZXLIDU01
          tables: e1ltori,
           loop at t_idoc_data.
    *........Zusatzinfos aus dem Transportauftrag..........................
         if t_idoc_data-segnam = 'E1LTORI'.
            move t_idoc_data-sdata to e1ltori.
            loop at t_ltap
             where tanum eq i_ltak-tanum
               and tapos eq e1ltori-tapos.
              exit.
            endloop.
            if sy-subrc eq 0.
              move i_ltak-drukz to e1ltori-wempf.
              move t_ltap-ldest to e1ltori-wempf+2.
              move e1ltori to  t_idoc_data-sdata.
              modify t_idoc_data.
            endif.
    *........Zusatzinfos die individuell beschafft werden..................
            move 'USER-EXIT' to e1ltori-ablad.
            move e1ltori to  t_idoc_data-sdata.
            modify t_idoc_data.
         endif.
        endloop.
    o   The IDOCs that have been set up are to be transferred to the
         external system via two different logical destinations, depending on
         the transport type. This requires two different partner profiles.
         The partner profile depends on the message type, message variant and
         message function. Message function 'EIN' is used for stock
         placements whereas 'RES' is used for all other movements. You have
         to maintain the partner profile for these two message functions
         'EIN' and 'RES' as well.
      INCLUDE ZXLIDU01
       if i_ltak-trart eq 'E'.
         move 'EIN' to x_idoc_control-mesfct.
       else.
         move 'RES' to x_idoc_control-mesfct.
       endif.
    For transfer orders on deliveries, the external system requires
    additional delivery data such as name of the goods recipient, route,
    shipping point, and the like. In this case, the large amount of
    additional data can only be transferred via an additional IDOC
    segment. That is, you have to define a seprate IDOC type that
    consists of the basic IDOC type WMTOID01 and a separate enhancement
    type. In the enhancement type, you define the new segment, for
    example Z1LTORZ, that refers to the standard segment E1LTORH. Filling the data of the new segment can be done as follows.
      INCLUDE ZXLIDU01
          tables: e1ltori,
                  z1ltorz,
                  edidd,
                  likp.
          data: flg_neues_segment.
          data: begin of xidoc_data occurs 0.
                 include structure edidd.
          data: end   of xidoc_data.
      *....>>> Neues Segment anlegen Z1LTORZ <<<.............................
      *........Bestehendes IDOC sichern......................................
      loop at t_idoc_data.
        move t_idoc_data to xidoc_data.
        append xidoc_data.
      endloop.
    *........Neuen IDOC-Typ und Erweiterungs-Typ im Kontrolsatz fortschr...
      move:
           'ZZWMTOID' to x_idoc_control-doctyp,
           'ZWMTOID1' to x_idoc_control-cimtyp.
    *........Aus dem bestehenden IDOC ein neues IDOC erstellen.............
           dabei wird das neue Segment aufgebaut und eingebettet
      refresh t_idoc_data.
      loop at xidoc_data.
    *........Merken:neues Segment soll nach dem Segment E1LTORH kommen.....
           if xidoc_data-segnam = 'E1LTORH'.
             flg_neues_segment = 'X'.
           endif.
       *........Standard-Segmente übernehmen..................................
           move xidoc_data to t_idoc_data.
           append t_idoc_data.
       *........Neues Segment übernehmen......................................
           if flg_neues_segment eq 'X'.
       *........Lesen Lieferung und Daten in neues Segment übergeben..........
             if not i_ltak-vbeln is initial.
               select single * from likp
                where vbeln eq i_ltak-vbeln.
               if sy-subrc eq 0.
                 clear t_idoc_data.
                 move-corresponding likp to z1ltorz.
       *........Neues Segment sichern.........................................
                 move 'Z1LTORZ' to t_idoc_data-segnam.
                 move z1ltorz to t_idoc_data-sdata.
                 append t_idoc_data.
               endif.
             endif.
           endif.
           move space to flg_neues_segment.
         endloop.
    if it is help full to u please give max rewad point.

  • Problem in triggering MATMAS IDOC through BD10 transaction

    Hi,
         My scenario is to trigger an IDOC(MATMAS)in BD10 and store it as an XML file in the physical directory.
    I have created a logical system for this and also created partner profile for the logical system defined.
    Further i've have configured XML Port has my reciever port of the outbound message type(MATMAS). But when i trigger the IDOC, it says that "1 Master IDOC setup for the message type MATMAS" and "0 Communication IDOCs generated" and the outbound IDOC is not recieved at the concerned directory.  Please help me out in solving this issue.

    Hi,
    While doing configuration u must take care of creation of Distribution model. Here you need to give message type,sender & receiver.
    At the same time you need to generate partner profiles. Results should give 'SYNCH' along with all info.
    Check all the inbound/outbound parameters are correct or not.
    If you satisfy with this pls close this issue and allocate some points.
    Regards
    KER.

  • IDOC question on Message type and Basic Type - Partner Profile

    Hi all,
    I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
    My question is about the setup of Partner Profile creation (WE20).
    When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
    Questions:
    1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables.  I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
    2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
    Thanks.
    tuff

    Tuff,
    Below are my thoughts,
    There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
    OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
    Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order -  ORDRSP.
    And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
    Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
    In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
    2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
    Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
    Regards,
    Chen

  • IDoc number generation is random

    We are trying to have a ALE-IDoc setup such that IDoc gets written as a text file to a application server directory.
    When we defined the port, we defined it as a file port. In the file port, we specified a folder on the SAP application server, where the file has to be created. Now when we generate the IDoc, this set up should automatically create a Idoc file in the specified folder.
    The Idoc itself is getting generated with valid data each time but the file isn't getting created always, even when the IDoc generation program is run with same data selection criteria. Interestingly, the Idocs which get written to files succesfully have a number range of 1000 and above, whereas the Idocs which couldn't get downloaded to files have a number range of 2000 and above.
    So my question is why are the numbers not serial, for both the successful and failed Idocs? Is there some setting which is forcing the system to pick the 2000 range for unsuccessful Idocs and 1000 range for successful ones? If yes, where is that setting?
    I read the following posted at another website "SAP assigns a range of Idoc numbers to each app server, so depending on which app server you hit your message will be assigned a number in that range".Can somebody validate that?
    The failed Idocs have the following status message:
    Status 02: Error passing data to port
    and the description is
    An error occurred when an outbound file was opened with 'OPEN DATASET'. The name of the outbound file is:
    /usr/sap/EQ0/put/HCM/ADP/outbound/HROT_UM_00002003 with operating system error msg.:No such file or directory

    We have resolved the problem.
    The Basis team had created the folder used for downloading the files only on one of the application servers (where the Idoc number range is 1000 and plus) but not on the other (where the Idoc number range is 2000 and plus). So when the process was hitting the application server, it couldn't locate the directory path and hence the OPEN DATASET statement was failing.
    So as soon as we created the directory, the problem got resolved.

Maybe you are looking for