RDI partner profile determination

Hi Experts,
we try to setup a raw data interface to several partners via IDOCs. Basically it works and
we can "print" data of a form marked with RDI Output mode = I to a Unix-File or to an
RFC-destination (via appropriate port definitions in the partner profiles).
But now we face the problem that an "RDI-form" is printed always to all partner profiles /
ports where in the corresponding distribution models the message SAPRDI is defined.
Function Module MASTER_IDOC_DISTRIBUTE:
  SELECT * FROM TBD05 INTO TABLE GT_FTBD05-TBD05[]
                             WHERE MESTYP = MESTYP.
  LOOP AT GT_FTBD05-TBD05 INTO WA_TBD05.
    IF   WA_TBD05-CUSTMODEL = SPACE
      OR WA_TBD05-SNDSYSTEM = SPACE
      OR WA_TBD05-RCVSYSTEM = SPACE
      OR WA_TBD05-MESTYP    = SPACE
      OR WA_TBD05-SNDSYSTEM = WA_TBD05-RCVSYSTEM.
      DELETE GT_FTBD05-TBD05.
    ENDIF.
  ENDLOOP.
How can we specify the only right partner profile / port (= destination)?
Any help is very appreciated.
Thank you in advance
Thomas Rehm

Hi,
Definition of parameters for the electronic interchange of data with a trading partner using the IDoc interface. To communicate with a partner using the IDoc interface, you must have a partner profile.
Purpose:
You must maintain the partners with whom you communicate via IDocs in the partner profiles: choose the message to be sent to the partner and define the path to be used, as well as how inbound messages are processed.
Prerequisites:
·  Master data must be available in the system for partners.
·  A port is also selected in the outbound partner profiles.This port must be configured already.
Just have a look at these links:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b803343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/start.htm
/thread/136978
regards,
Gunasree.

Similar Messages

  • Output Determination / Partner Profile

    I have a vendor with an LI Partner Profile setup in the system. Every time an invoice is posted against this vendor, I need the system to generate an IDOC for external transmission.
    How do I setup the output determination to make this happen?
    Thanks - points will be rewarded.

    I just did changes with my access sequense, was using Sales Org/ShipTo/BillTo but just changed to Billing Type and it worked fine, I got my error.
    Just one more question, I am doing this output via medium 6 and date 4 (send immediately) now since my output is founf in the billing doc and it is saving properly what is my next job to create the programme?
    Please provide me the steps.
    Thanks for your help !!!
    Aman

  • WE20 - partner profiles: inbound parameters - how to determine process code

    Running standalone scenario on SRM 5.0.
    First of all, it is not possible to "generate partner profiles" automatically in BD64 (distrubution model) in the backend system for message types:
    BBPIV, BBPCP, ACC_GOODS_MOVEMENT, ACLPAY and MBGMCR.
    The following error is displayed:
    BBPCO
    Inbound parameters for message type BBPCO could not be created
    Enter a valid process code
    etc.
    When trying to create partner profiles manually in WE20, how do I determine the process codes for the different message types?

    Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
    Solution
    Check and if necessary, correct the following entries:
    1. Assign function module to message type
    Transaction WE57
    The following entries are required:
    Module IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
    Type F F
    Basic type BBPIV01 BBPCO01
    Msg type BBPIV BBPCO
    Direction 2 2
    Object type BBPBUS2081 (not for Release 3.1)
    Note that object type BBPBUS2081 is not defined in Release 3.1*. In
    this case, the 'Object type' entry remains empty.
    2. Characteristics of inbound function modules
    Transaction BD51
    The following entries are required:
    Inbound FM IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
    Input type 1 1
    03.09.2008 Page 2 of 3
    Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
    Dialog allowed No No
    3. Create the missing process code with Transaction WE42 (change inbound
    process code). You can name the process code whatever you want. 'IV01'
    or 'CO01' are examples.
    The entry should look like this:
    Process code IV01 (CO01)
    Description BBPIV (BBPCO) inbound invoice
    Option ALE Processing with ALE service
    Processing Type Processing by function module
    Save the entry. You are then on the detail screen. Enter:
    Module (inbound)
    Function module
    IDOC_INPUT_BBP_IV (IDOC_INPUT_BBP_ACC_PO)
    Application object
    Object type
    BBPBUS2081 (- no entry -)
    4. Maintain the process code that has just been created in the partner
    profile for the logical system.
    Transaction WE20
    Partner type 'LS'
    regards
    Muthu

  • Error while creating Partner Profile

    Hi.
    While generating the Partner profile for the distribution model
    The following error is coming :
    Outbound parameters for message type CREMAS CREMAS04 could not be created
    Please enter a valid value for the output mode
    Outbound parameters for message type SYNCH SYNCHRON could not be created
    Please enter a valid value for the output mode.
    Furher while processing the Idoc its giving the error 'Entry not found in outbound table'.
    Kindly help in resolving the error.
    Thank u in advance.
    Pranali.

    Hello Prashant,
    You are missing some configuration for the partner function;
    Go- to
    SPRO>IMG>QM>Quality Notifications>Notification Creation>Partners>Define partner Determination Procedure>
    Again Select "Define Partner Determination Procedure".
    Select Quality management> Change Partner
    Now Select Q2.
    Compare settings with Partner Determination Procedure on any other client. Also check Partner functions on the same screen.
    Amol.

  • Getting EDI:Partner profile not available.

    Hi,
    I am a newbie to SAP XI. As I am doing File to IDOC scenario, I am getting error - EDI:Partner profile not available.
    <u><b>My Scenario details</b>:</u>
    1. Created RFC Destination, RFC port, logical System and Partner profile in both Sender (XI) as well as Receiver(SAP R/3) systems.
    2. Created SWCV, Technical sys, Business Systems in SLD. I used the Logical system created (for SAP R/3) on XI system in my business system.
    3. Created Data type, Message type, Message interface, Message Mapping and Interface mapping in Integration Repository and activated them.
    4. Imported IDOC from SAP r/3 system during Namespace creation and used it for mapping.
    5. used Integration Directory wizard to create Communication channels, Sender & Receiver agreements, Receiver Determination, Interface Determination.
    6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.
    7. Activated all Standard Change list items.
    The file for the above Scenario has been picked up amd i am getting "Chequered Flag" on both ends in "SXMB_MONI" monitor. When i change over to SAP R/3 to check idocs created (i.e., T.code - we05) my scenario idoc status is 56 and it says.. Status; Idoc with errors added.
    I  have gone through many of the forum suggestions and blogs regarding this issue, but still not able to resolve my problem.
    can somebody suggest me solution please.
    Thanks,
    Vijay.

    Hi,
    <i>6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.</i>
    >>>Check this for Reciever Business System.. not for Sender system..
    BTW, if you get chequered flag in XI, then idoc data is sent from XI. Can you check  all the data from XI is populated in the idoc structure in SAP R/3 in we05...by clicking each segment.. if so, then there is no problem from XI..
    check WE20 ..partner profile configuration in R/3 also check inbound parameters are given
    Regards,
    Moorthy

  • Partner profile and partner number in output of order/invoice.

    Hello Experts,
    I want to know how system pick partner profile from output type triggered in sales order/invoice??
    I could see partner profile is different from partner number exist in output triggered in sales order/invoice.
    I want to know the triggering point of idoc from SO/invoice.
    Thanks

    The phrase "ouptut goes to partner" indicates that the partner will be recipient of the output type.  E.g., ship-to partner will be the recipient of the delivery and the delivery note.
    The use of an output partner in the output condition record is used to control the output device used in the output determination - a completely separate issue.
    Unless you are (e.g.) using different printers for outputs which will be sent to different partners, you would likely be better off using a more generic access for your output condition records.
    HTH
    James

  • Partner Profile and its configuration.

    Hi all,
    I am creating an SD IDoc using EDI and send it between two servers.
    I need to know what is a partner profile and why should we create it.
    what are the steps to be followed in maintaining a partner profile and its configuration.
    Any pointers will be highly apppreciated.
    Thanks in advance,
    Regards,
    Jose
    Edited by: Jose Anthony Reddy on Dec 17, 2007 11:23 PM

    Hi Jose,
    Below is a material you can go through .
    Creating an Outbound Partner Profile
    Here you must enter the data manually. Alternatively, you can also transfer the default values from Customizing.
    If you are not yet on the change screen of your desired partner, choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Agreement (WE20).
    1. Position the mouse on your partner in the required partner type node. Choose in the Outbound Parameter table.
    Key Fields
    2. You have already determined partner number and partner type in general partner processing. The partner function from the master data defines the addressee, that is, it is used for further classification purposes. If you have selected outbound processing under Message Control (MC), the function must be identical to the corresponding Message Control field. Otherwise, it is optional.
    Partner A (customer 1110) wants to order a material from partner B (vendor 1014). Partner B is of the partner type “LI” (vendor) and must choose the Message Control value “VD” (vendor) as the partner function because orders must always be processed using Message Control.
    3. Specify the business process with the “logical” message, within which the IDoc type is used. The logical message is described by three parameters: The message type is based on EDIFACT message types: For example, a purchase order is of type “ORDERS”. You can further divide the message type with the optional fields message code and message function.
    4. Configure the test indicator if you want to send the message as a test.
    Message, partner and test indicator are the seven key fields of the outbound partner profiles (the client comes in addition to these). Also see the graphic at the end of this section.
    Other Fields
    5. In the Outbound options tab page, you can determine whether IDocs are forwarded immediately to the receiving system. You should ensure that your entries are compatible with the Message Control priorities, if you have chosen outbound processing under Message Control. A list of recommended combinations is provided in the section Outbound Processing Under MC: Procedure.
    6. You have already defined the Recipient port in Port definition.
    7. If a port of type TRFC is used, the Queue Processing field is visible. You can use the indicator to specify whether IDocs are to be sent with qRFC. This sending technique is only possible for recipient SAP systems as of SAP Web AS 6.20.
    You should only set this flag if it is really necessary that the IDocs sent are received in the receiving system in the same sequence as they were sent by the sender system. Queuing can cause posting delays in the receiving system, because an IDoc in the queue cannot be posted. In this case, the following IDocs in the queue cannot be posted until the error is resolved.
    8. If you have set the Queue Processing indicator, the Rule Name field, which you must then also maintain, appears as well. The rule name defines the rules for queue names. You can specify these rules in the transaction qRFC IDoc Queue Name Rules (WE85).
    9. Specify the IDoc type as the Basic type with or without extension. If you want to use a view of your IDoc type (for example, to improve the performance), specify this here.
    The figure below shows the m-to-n relationship between logical messages (business meaning) and IDoc types (technical format). Message 1, for example, is always assigned to one IDoc type, while message 3 is assigned to two IDoc types. IDoc type 2, in turn, is also assigned to 2 logical messages.
    10. The segment release specifies the release from which the segment definitions (not the IDoc type definition) originates. We recommend that you leave this field blank so that the most recent segment definition is used.
    11. You can propose an EDI standard, version and EDI message type for the receiving system in the tab page EDI Standard. Most subsystems, however, should be able to determine these EDI settings themselves (from the logical message).
    12. You can define permitted agents for cases in which exceptions occur. This entry overrides the entry in the general partner profiles. Depending on the message, therefore, the exception can be handled by different agents of the same partner.
    13. You can specify whether syntax errors are to be ignored or are to lead to a processing error (Cancel Processing flag under syntax check in the tab page outbound options). For more information about exception handling and permitted agents, refer to the following section: Exception Handling
    14. If your hardware supports it, create partner and message specific telephony data for outbound IDocs. For more information, see General Partner Profile.
    Graphic: Outbound partner profile fields (general)
    Key fields are shown in gray. The values for partner, message and test indicator (and client) therefore provide a unique ID for the IDoc type in outbound processing.
    Regards,
    Praveen

  • How system pick partner profile in order/invoice

    Hello Experts,
    In invoice [VF03], I could see system determine output type RD00 and partner function BP so system is taking Bill to party from invoice and putting there. I checked the output condition record for that invoice [VV33] there there partner number is not assign to partner function BP. I understand this.
    BUT my questing is, How system is picking partner profile to create the Idoc for that invoice??
    Partner profile and Bill to party both are different.
    How Idoc creating process start when we save sales order/ Invoice ???
    I want to know the triggering point from where system start idoc creating for sales order/ invoice ???
    Thanks

    INBOUND processing the IDOCs are transferred to the interface and stored in te SAP system. The document data is generated in the course of workflow.
    In this section the SAP  system is made known to the upstream system (startrfc program parameters). Conversele, the upstream system is made known to the SAP System via the port definition.
    INBOUND Processing - Create Function Module.
    This function module is called when a message type, of the ZINVRV, comes into the receiving system.  This needs to be configured.  The function module is passed the IDOC as a parameter.
    Use the T.code WE19 to test inbound function module in debugging mode.
    Use the T.code EW05 to view the IDOCs and their statuses.
    Rewards if useful.

  • IDocs, INVOIC partner profile configuration

    Hi,
    I need to receive the INVOIC IDocs from sender system.
    Sender(S) system is new system
    receiver(R) system is already exisitng system.
    I tried to configure the inbound settings in receiver syste. But message type INVOIC, process code INVL, FM all are already available and configured for some ohter systems.
    Now if i configure only partner profiles and distribution model, then is it work.
    Thanks
    Kiran

    Kiran,
       INOVOIC, INVL, Process codes etc come with the standard system. They can be configured for any partner profile and any sender system.
    First, you need to determine the inbound connection. Will the new sender system (S) going to follow the same RFC connection already setup for other sender systems? E.g. Are all the inbound IDOC's flowing through PI or a single EAI system?
    If yes, then you just need to setup a new partner profile and use the same port already setup for your existing connections.
    If no, then you have to determine how the sender system will connect with SAP. Will they drop files in the SAP's application server? After dropping can they execute the startrfc.exe with required parameters. If they can then you can just proceed with creation of a port to listen that folder (assuming the RFC connection is already setup for that connection) and move ahead with partner profile creation and other mandatory setups. If they cannot trigger the startrfc.exe, then you have to define a new RFC destination (SM59) and a new port (WE21) to read data for this RFC destination. You have to determine when to read the data (e.g. explicit host type etc).

  • Partner profile generation

    Hi,
      while generating the partner profile it is askimg for partner no but i don't have any partner system is there any option to configure the same system as seneder and receiver , if it is possible tell me the procedure how can we do that.
    Thanks in advance,
    Sasi.

    u can use a business service as sender as well as reciever.
    click on the business service->give the outbound  message interface name in Outbound  + (below) give the inbound message interface name....so during reciever determination u can give the sender service as the reciever.

  • Having multiple Goods Suppliers in Partner profiles of Vendor - Uses

    Hi All,
    We use multiple goods suppliers in partner profiles of vendor so that if the supplier has manufacturing facilitiy at various places for same material and he supplies us from one of them as lsited in the PO.
    Above is one of th use of having multiple goods suppliers in partner profiles of vendor.
    Other than above are there any specific benefits , can some one help me in listing  out .
    Regards,
    Vengal Rao.

    do you need to follow up an individual order with a GS or many many orders at one time?
    I am not aware of any standard PO report by partner roles.
    In general the GS partner is just for information purposes, except you are doing business in European Union, then the GS partner is taken instead of the vendor to determine the country of dispatch for the Intrastat reporting.

  • EDI: partner profile for shipping point or plant

    I want to issue idocs for delivery notes based on shipping point or plant, not shipto party as is usual.
    How can I go about this?
    It looks like I need to create a new partner type. Or can I use logical systems?
    If logical system is used, then how do I make the connection document->LS?
    The external system uses the RCVPRN to determine which warehouse to handle the delivery for.
    I am changing the RCVPRN in a user exit now, but this still requires creating/ changing all partner profiles for shipto parties.
    Any ideas? previous experiences?
    Thanks,
    phillip

    Hi Phillip,
    it looks like I need to create a new partner type. Or can I use logical systems?
    > Yes, you can use LS
    If logical system is used, then how do I make the connection document->LS?
    > You can use FM: MASTER_IDOC_DISTRIBUTE to send the outbound IDOC...
    Regards,
    Hendy

  • Invoice EDI error : EDI: Partner profile inbound not available

    Hi  EDI experts ,
    We are connecting our SAP ECC 6 ( Ehp 4) system to 3rd party system Mincom via SAP PI, to send PO Creation message (Outbound) and receive Vendor Invoice message( inbound).  We already done all the settings..Output determination procedure, Partner Profile ( WE20) , Port creation , Condition Records, EDI settings in SPRO for invoice..etc as below:
    Logical system ( BD54)
    ECC system - EDACLNT112,
    PI systems u2013 IDACLNT210
    Third party u2013 LSMINCOM
    Port ( WE21)
    IDACLNT510 : For PI with RFC destination IDACLNT510
    Partner ( WE20)
    LSMINCOM :  (Partn.Type LS)
    Outbound parmtrs.- Partner Role- LS, Message : ORDERS , Port - IDACLNT510
    Inbound parmtrs.- Partner Role- LS, Message : INVOIC , Message Variant- MM, Process code u2013 INVL, Trigger immediately (Process code INVL have  Identification - IDOC_INPUT_INVOIC_MRM, Option ALE u2013 Processing with ALE services , Processing type- processing by functional module)
    Here PO Creation is working fine . IDoC of PO outbound message have below details :
    Recipient information:
    Port :     IDACLNT510 (Logical system & Port created in WE21 )
    Partner Number :  LSMINCOM   ( Logical system and Partner created in WE20)
    Partn.Type :  LS        
    Function :  LS     
    Sender information:
    Port :  SAPEDA ( donu2019t know how it created..but in WE21..it is not there)
    Partner number:   EDACLNT112 ( Logical system and Partner created in WE20)
    Partn.Type :  LS        
    Partner Role :Blank
    Just started testing, our PI team is sending the IDoC, with wrong information on partner & other data, so inbound IDoC failing with error u201CEDI: Partner profile not availableu201D. Oaky. I reprocessed these failed IDoCs by changing Partner data just opposite (i.e. Sender info as Recipient info & vice versa) to successful PO Creation O/B message in WE19 in EDIDC and when I click on u201CStandard Inboundu201D, then another window open giving error message u201CPartner profile not maintainedu201D and creates new IDoC with status 56
    EDI: Partner profile inbound not availableMessage no. E0337
    Diagnosis
    An inbound partner profile could not be found with the following key:
    /LSMINCOM/LS//INVOIC///X/
    This involves the key fields of table EDP21:
    -SNDPRN  partner number of sender
    -SNDPRT  partner type of sender
    -SNDPFC  partner function of sender
    -MESTYP  logical message type
    -MESCOD  logical message code
    -MESFCT  logical message function
    -TEST    test flag
    Procedure
    Please check the inbound partner profiles.
    Execute function
    I am not getting exactly what inbound partner profile could not be found or what is the problem here . Can anyone suggest me what should be the problem and solution on it ?
    Thanks
    NAP

    Narendra,
    Please advice what was the solution.

  • IDOC Partner Profile

    Hi Experts,
                      What is the partner type we use in Partner profile for XI Linkage. I know we use LS for ALE Links.
    Thank you
    Kris

    Please check the following links which explains about the partner type Customer (KU) and Vendor (LI)
    http://www.*******************/2009/02/edi-idoc.html
    http://www.sap-img.com/sap-sd/partner-determination-for-sales-doc.htm
    http://www.sapdb.info/partner-determination-in-sap-sd/

  • 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

Maybe you are looking for