Limitation on number of partner profiles

Hi,
I am working on SAP Retail implementation. As you know, in SAP Retail, we consider each store as customer and there will be seperate partner profile of type customer for each store.This is for integrating SAP with point of sale (store).
Since number of stores are more, around 1000, i feel it's not good solution to create 1000 partner profiles. Please let me know whether there is any alternative for this and also whether there is any limitation on number of partner profiles that we can create.

There is no limitation for partner profile creation
Regards,
Prateek

Similar Messages

  • Customizing (Automatically add a customer in WE20 partner profiles under KU

    Hi,
    Is it possible to add a customer automatically in WE20 under Partner type KU.
    I mean when ever a customer is added in R3 or by any standard transaction code where we can create automatically all the existing customers under Partner type KU?

    Hello,
              It is not possible to add a Customer automatically to the Partner Profiles (WE20).
              I believe creating Customer and maintaining the same Customer Number in Partner Profiles are two different & independent tasks because it is not necessary for every customer to be part of the EDI Transmission.
             Hence, people maintain partner profiles as per their requirement, not necessarily for every Customer created in SAP.
    Hope it was clear.
    Thanks and Regards,
    Venkat Phani Prasad Konduri
    Edited by: Konduri Venkata Phani Prasad on Sep 11, 2008 11:05 PM

  • EDI  partner profile  deactivated

    Hi
    while client refreshed EDI Partner profile deactivated why this thing happening .
    Thanaks & advance

    Hi,
    When we are sending the Idoc from XI / PI system, it is taking the partner number from Partner Profile used for sending the same from XI / PI System.
    We are configuring the same into tcode IDX1, please check the same.
    The same partner profile is used in your port number in IDX2, where you have imported the idoc matadata.
    Sandeep

  • EDI partner profile copying

    I need to set up hundreds of trading partners for orders, deliverys, ship confirm, etc.
    Has anyone used the function modules in the EDI6 group to do this automatically. I'd like to supply a list of customer numbers and have the WE20 partner profiles all come out the same.
    There are two function modules: EDI_PARTNER_COPY_COMPLETE and EDI_AGREE_PARTNER_INSERT that look promising. But, I wanted to check with other forum users for recommendations.

    Hi,
    When we are sending the Idoc from XI / PI system, it is taking the partner number from Partner Profile used for sending the same from XI / PI System.
    We are configuring the same into tcode IDX1, please check the same.
    The same partner profile is used in your port number in IDX2, where you have imported the idoc matadata.
    Sandeep

  • 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

  • Why T-RFC Port canu2019t handle Partner Profile Segment Release Version.

    Can TRFC Port handle the segment release of each of the segment if configured in Partner Profile.
    As per sap, in Partner Profile,  if we maintain the two field "Seg. Release in IDoc Type"  and "Segment Application release" to a SAP Release lower than the current release version then all the segment populated by the IDoc adapter should be populated as per the lower release structure.
    For test Purpose I have created two IDoc using File Port and TRFC port and for both of then I have maintained the Partner Profile Fields  "Seg Release in IDoc Type" and "Segment Application Release" as 46C although the latest release is 701. 
    In the IDoc there is a custom segment ZE1PMX with two Version Release 46C & 701. 46C is having 7 Fields and 701 is having 9 fields.
    Test using TRFC Port: Using TRFC port the IDoc that is getting generated are not having the segment structure of release 46C instead of that it is taking the segment structure of latest release 701 which is having 9 fields.
    Test using File Port: Using File port the IDoc that is getting generated are having the segment structure of release 46C instead of latest release 701 which is having 7 fields which is desirable.
    I have also done these testing in other SAP release like 700 and found that while saving the partner profile with a lower  segment release number it throws an warning message as "Segment definitions missing for release 620/620" and IDocs are not getting generated with a error status Code 2 "Segment E1BPMEPOITEM1 is unknown in Release 620 /". But from release 701 sap allows us to save the Partner Profile without warning and also creates the IDoc without error but the segments takes the latest release structure instead of the release maintained in the Partner Profile.
    If any one has already done some investigation on this issue please let me know why there is a difference in TRFC Port and File Port. Is there any other configuration that is missing for T-RFC Port.

    Hi Dennis
    This forum is focused on [SAP NetWeaver Gateway|http://www.sdn.sap.com/irj/sdn/gateway], i.e. the (relatively) new OData/REST-orientated mechanism to expose ERP data and functions.
    You're talking about the ('classic') Gateway i.e. the service that runs on port 33<SYSNR>. As a result, you are better off posting in the forum that covers that Gateway, i.e. [Application Server Infrastructure|SAP NetWeaver Application Server;
    The names do make it confusing, for sure.
    Good luck!
    dj

  • Partner profile activation

    hi,
    basis team did some work(replacing logical system of r/3 dev system) and i checked whether bw objects configuration is fine. i'm unable to see datasources in datasource level of rsa1, but able to see in infoprovider(data flow) level of rsa1,eventhough i replicated datasources meta data. i tested on bw dev system whether full update or delta updates are working or not. i'm getting same error message: partner profile not active. after error analysis given by system: xxx(parner number) entry, check edpp1(parmer profile) table'(partner number & partner type). Checked particular entry xxx partner profile is inactive status. how to make partner profile active? can basis or abaper do this work?
    regards,
    V N

    Hi,
    Tell the BASIS team to maintain the EDI partner profile. They can do this work.
    Cheers,
    Kedar

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

  • Partner Profile Configuration(Outbound Enteries)

    Hi,
    I was trying to make a business partner with the BP Role “Master Tenant with Customer Account”. At the time of saving I got following error:
    Entry in Outbound Table not found
    Message No E0400
    No partner profile(Outbound) could be foundusing following key
    B3TCLNT800/LS//HRMD_ABA///
    This refers to key fields in Table EDP13
    RCVPRN  Partner Number
    RCVPRT  Partner Type
    RCVPFC  Partner Function
    MESTYP  Logical Message
    MESTYP  Message Code
    MESCOD  Message function
    TEST        Test indicator
    Please check EDI profiles.
    And it directed me to transaction code WE20.
    Could you please help me in making the desired settings and explain why this needs to be done.
    Regards,
    Lata

    Hi,
    I guess either you are using CRM or Flexible Real Estate Management.
    Pl confirm the exact transaction code you are using. Are you using BAPI ?
    For creating the Partner profile,
    Go to WE20,
    Click on Create button.
    Give the Partner Number, Give Partner Type as " LS"
    User type- US
    Agent - Your User ID
    Give the Message types in the Outbound/ inbound parameters.
    Pl reply for further clarifications
    Thanks
    Siva

  • Partner Profile creation

    Hi
    I have an idoc-xi-file scenario. For this I want to create partner profile(of partner type LS) in ECC system using we20.
    When I entered partner no. as DX1CLNT100 and saved (after filling all the information) it is throwing the error saying
    "The partner number 'DX1CLNT100' does not exist for the partner type LS".
    If it won't exist how to make it available ??
    thanks
    kumar

    Hi,
    You need to have the Logical system available for this, - BD54
    SAP Network Blog: Configuration steps required for posting idoc's(XI)
    Configuration steps required for posting idoc's(XI)
    A Step-by-Step Guide on IDoc-to-File Using Business Service in the Exchange Infrastructure Integration Directory
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
    These are the required steps for IDoc to File scenario...
    In R3 (i.e., your IDES system)...
    RFC dest to XI (sm59) - any name
    Logical system (bd54) - any name
    Port to XI (we21) - any name
    Partner profile for the logical system (we20) - use Logical system name created in bd54
    In XI...
    RFC dest to R3 (sm59) -
    Port to R3 (idx1) -
    create metadata for the idoc (idx2)
    In sld...
    create business system for R3 with Logical system name as r3 sys.
    In we19
    and give in control record as
    Sender : Port ; Partner
    Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
    see the below links
    ALE configuration for pushing idocs from SAP to XI
    Introduction to IDoc-XI-File scenario and complete walk through for starters.
    idoc settings Configuration steps required for posting idoc's(XI)
    Also
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    IDOc testing - Generate Test Case for an IDOC Scenario
    Thanks
    Swarup
    Edited by: Swarup Sawant on Sep 8, 2008 3:53 PM

  • Partner profile not available.

    Dear Folks,
    i am doing the scenario JDBC to IDOC. For that i did all the necessary ALE settings and configured the systems. While executing that scenario. In we02, i am getting the error partner profile not available eventhough i configured it. From the error i found that, in technical info, partner number and port are different. And i am getting some Default parnter number and port.
    From my observations, i checked the Sender business system and i found that, logical system which was mentioned for this business system is replicating as a default parnter number in the technical info.
    please guys i need your valuable suggestions to eradicate this error.
    Regards,
    Dileep

    Hi Mark,
    I checked the payload and i am not using header mapping.
    I tested the same by doing some modification like, In sender business system, i replaced the default logical system name with which i am using.Then idoc status is changed to status 50. But i am getting the Default port as previously said.
    one more thing is , whenever i am getting this partner profile error, it is hitting one of my Company portals. i.e., displaying this partner profile issue in MSS(managerial self service) of HR Portal.
    I was little bit confused of why it is hitting the portal?
    what would be the key point for their connection?
    Please help.
    Regards,
    Dileep

  • IDoc Receiver, Error in we02 - EDI: Partner profile inbound not available

    Hi All,
    I have a problem when creating a receiver IDoc from XI to R/3.
    I have successfully tested the IDoc when populating the receiver information from the payload. However I want this information to be populated automatically based on the logical systems.
    When I do this I get the following error in the IDoc in R/3:
    EDI: Partner profile inbound not available
    In the control record the sender information is all correct but in the recipient information the partner Number with type LS is populated, but port is not populated.
    I have done the following steps.
    •     the sender is a Business Service so I have created a logical system directly adapter-specific identifiers in the sender service in the integration directory.
    •     In the receiver business system I have imported the logical system into the adapter-specific identifiers in the ID from that specified in the SLD.
    •     In the receiving R/3 system using SALE/BD54 I have created a logical system for the source system.
    •     In the receiving R/3 system using we20 I have created a partner profile of type LS with the same name as the source logical system.
    •     IN PI/XI system in transaction IDX1 I’ve created a port (SAP<SID> where <SID> is the system ID of the receiving R/3 system) and the client of the R/3 system, and the RFC destination of that system (<SID>CLNT<clnt>, as specified in SM59).
    •     In the IDOC Adapter (receiver) I have entered the RFC destination and port matching those created above. All checkboxes are UN-checked eg. take sender from payload, take receiver from payload, Apply control record values from payload, etc. are all NOT checked.
    I think that I’ve done everything correctly, but I get the error in we02 in R/3: “EDI: Partner profile inbound not available.”
    Any help will be greatly appreciated (and rewarded, obviously).
    Thanks,
    Matt.

    HI Matt,
    Can you please copy paste the exact error message....In your error message it will show you Exact partner Number / Logical System name and other parameters...just compared if you have all parameters set in your partner profile comparing to error message...
    If you can giev screen shot of both..then probably would be easy to point out error.
    Hope this will help.
    Nilesh

  • Generation Partner Profiles from ALE Distribution Model

    Hi ABAP/EDI experts,
    I am a trainee. I am getting training from Pvt consultancy. I am working on SAP Demo systems.
    I am trying t generate an IDoc using ALE method.
    IN SALE window, I created two logical systems,ZVK_SS_800 and ZVK_SS_820. I assigned them to two clients 800 and 820 respectively.
    In SM59 i created an RFC connection ZVK_RFC004 of type 3. Here I gave the client Number as 820. ( I'm not sure what to give)
    In BD64, I created an ALE Model and added the message type MATMAS with Sending and Receiving Logical systems.
    From the Environment drop down menu , selected generate partner profiles and executed with defaults checked. ( Transfer IDocs Immediatley and Trigger Immediately).
    I got the following log.
    Log For Partner Profile Generation:
    Partner:
    In Green Color
    Partner ZVK_SS_800 as partner has been Created ( Sending System)
    Partner ZVK_SS_820 as partner has been Created (Receiving System)
    Port:
    In Red Color
    Port Cloud not be Created
    RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
    Enter the RFC destination and Restart the generation.
    Please help me to fix this probelm.
    Any kind of Help will be surely rewarded.
    Thanks,

    From SM59, you can Test your RFC Connections between Clients.  I would do this from Client 800 and test the Connection to Client 820.   If that checks okay, I would then try SM59 on Client 820.   Check the RFC Connection from Client 820 to Client 800.   Be sure you have your Logical Systems defined on Both Clients.   You can also double click on your Error Message to see if there is a Long Text Available that might give you further information as what needs to be corrected.   I am not an Expert in this area, but have setup several ALE Models for my Variant Configuration without any problems.  If you could include your EMail Address on your Business Card I could EMail you my instructions.   Your Basis person may also be able to help you based upon your Error Message.

  • Configuring ALE Logical Systems and Partner Profiles

    hi,
    Trying to build a scenario which deals with two third party systems transfering XML file from one to another. Sender is using a file adapter. Reciever is using an Idoc adapter. However the pre-requisite mentioned for this exercise are that ALE logical systems and partner profiles must be configured (these steps are not outlined in the exercise) . Could i get help on what steps i need to carry out for sender/reciever to configure logical systems and partner profiles.
    regards,
    Manpreet

    Hi Manpreet
    At the R/3 system the partner profile should be maintained for both the third parties.
    for creating the partner profile go to transaction we20, give the
    partner number :your logical system name or customer number or vendor no
    partner type:LS(logical system)or ku(customer)OR LI(vendor)
    give the message type in the outbound parameters
    after this double click on the message type and give the login deatils for the RFC destination define the port and all
    if you still have problem please reply back
    Thanks
    Rinku

Maybe you are looking for