DEBMAS - Partner Profile Confusion

I confused about configuring of DEBMAS Idocs.
I need to unload the customer information from SAP into XI.
I have done some customuzing:
1) Maintain Logical System (SALE)
2) Assign client to LS.
3) Maintain Port (WE21)
4) Activate Change Pointer for DEBMAS.
Now as I think I have to create partner profile in WE20.
But there is the problem.
1) I don't know what type of partner I have to use for our Customer(KU or GP)? What should I configure in WE20 for DEBMAS?
2) And we have some thousands Customer. Really We have to create all of them in WE20?
Can I define some groups (or something else) of the customers and point them in Partner Profile?
Thank You!

U can try logical system select XI as logical system and do the partner profile for XI LS.
1) I don't know what type of partner I have to use for our Customer(KU or GP)? What should I configure in WE20 for DEBMAS?
2) And we have some thousands Customer. Really We have to create all of them in WE20?
Can I define some groups (or something else) of the customers and point them in Partner Profile?
i think if there are n no of customer then n no of partner profile is created.
refer the below link for sending the KU type:
Edited by: Chirag Gohil on Apr 15, 2008 10:14 PM

Similar Messages

  • 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|], 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!

  • Partner profile in case of Idoc to File scenario

    I have ECC system and PI system. Scenario as :
    ECC will send the Idoc to PI ..PI system will Convert this to flat file and provide it to Legarcy system
    I made Partner profile in sending system (ECC) and maintained Message type 'MATMAS' as Outbound.
    Do i need to maintained the MATMAS in Partner profile of PI also?.
    As PI has copied the Idoc MATMAS.MATMAS05 from ECC.
    I am confused please suggest

        MATMAS05 should be configured as outbound paramters of ECC and no need to configure any thing at PI Partner Profile..
    All you need to do is to create the Distribution model as sender (ECC) receiver (PI) and message type as MATMAS05...
    with appropraite RFC destination name and port.....
    if you are new to distribution model and like to know tcodes for the same just check the below link

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

    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.

  • Partner Profile for file to IDOC scenario

    Hi experts,
    I am doing file to Idoc scenario. I did the ALE configuration steps between XI and r/3. For sender (ThirdParty) system, I defined Business system. While defining partner profiles in WE20 I got confused, whether to Give XI logical system Name or Third party logical system name. Please clarify..........

    >>I defined Business system. While defining partner profiles in WE20 I got confused, whether to Give XI logical system Name or Third party logical system name. Please clarify..........
    in most cases you will only use one logical system in WE20
    this will be XI's logical system - and you can route all the traffic
    via this logicail system - this is the most popular case
    for more about IDOCs and XI have a look at my book:
    Mastering IDoc Business Scenarios with the SAP XI
    Michal Krawczyk - XI/PI FAQ

  • Delivery split through VLSP along with JIT Calls with AW Partner profiles

    Hi SAP SD/LE Guru's,
    I have one critical issue to resolve immediately in my implementation of SAP 4.6C system in multinational automotive industry. It's in the area of Delivery split along with AW - Duns number partner profile and JIT calls.
    Here is the scenario:
    1. JIT(Just In time) calls will be created through EDI based on the ship-to, PO Nos, Duns number.
    2. The requirements will be updated in Scheduling Agreements JIT Delivery schedule.
    3. Picking is done based on the requirements.
    4. Packing, Deliveries and Handling units are created: Note: Each handling unit is linked to one JIT Call.
    5. Based on the Shipments, Deliveries needs to be split into further sub-deliveries.
        Ex. One Delivery has two HU's. This needs to be split into another delivery so that one HU need to be detached from original and attach to new delivery. At the same time corresponding JIT call also need to be detached from original delivery and attach to new delivery. This can be done through VLSP : Subsequent split(Outbound delivery). Split profile: 003 - split based on Quantities.
    The issue: When executing delivery split using VLSP and split profile: 003, the system is terminating and giving short dump.
    The error analysis says that AW - Duns number is creating the problem. The short dump occurs in SAPLV05I in Function module: SD_PARTNER_UPDATE.
    There is an SAP note: 154766 related to this problem says that Partner header should be used only once in copy control.
    But in customization of copy control from Sales order to Delivery, there is no VBPA Partner header.
    I appreciate if you can provide solution for delivery split and resolve this short dump issue.
    Murali Chintakunta

    In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
    What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?

  • Process code & Partner Profile Issue

    Hi Experts ,
    Hi ,
    I need to configure partner profile with a external system . I will be receiving customer data from the ext System .
    I though of using msg type DEBMAS and msg type
    and process code DEBM. I see its uses function module IDOC_INPUT_DEBITOR.
    So what exactly this function module does ?
    I was wandering if I need to create new Process code / Function Module .
    My requirement is receiving the customer data along with address , shipping informations , customer no . So that when I drop orders its becomes available.

    Hi ,
    Check all the settings needed for an R/3 - XI- R/3 scenario..... In ur case R/3 to XI is working fine and u have to check the XI-R/3 side.
    Check the RFC destination ( Both in XI and in R/3)
    Check the logical system name
    PORT, Partner profile .....

  • "error no:58" partner profile not maintained in idoc.

    Hi to all,
             i am new member to this site already searched forums for solution.
    can anyone help us out to solve the following error while simulating inbound idoc.Error:58 " partner profile not maintained"
    we tried with msg type CREMAS and DEBMAS.created partner profiles,rfc connection as procedural but same error results.
    also give some useful links to process idocs.
    we want ur valuable suggestions,thanks in advance.

    link for inbound idocs is given below
    Please check in the receiver side if the partner profile is configured correctly.
    Go through the link below in order to maintain partner profile.

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

    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.

  • Partner profiles in PI

    Hello all,
    I am doing a File to Idoc Scenario. I have done almost all the configutations and now a bit confused about the partner profiles. What are they for and where they are used? Should I create the partner profiles both for the sender (third party)  and the receiver systems (ECC) on the receiver system (ECC)?  or  Should I create just for the Sender system?
    Please help.
    Thank you.

    1. You must have a partner profile to communicate with a partner using the IDOC interface. This will provide the parameters for electronic interchange of data with Trading partner in SAP
    2. Partner profile should be created at receiver system for sender system to receive the IDOC this is called Outbound partner profle
    3. You can send partner profiles to the receiving systems  if you are sending IDOC
    Useful document

  • Partner profiles  in idoc.

    Dear Experts,
    I am using 800 client for sending and 810 for recieving.
    I am using message type MATMAS to send  material to 810.
    for this how to create ports and partner profiles I am getting confuse in these two areas remaining are ok .
    help me in this case

    To create partner profiles and ports,
    At the sender (client 800):
    Port: Port is required for the outbound message type and hence port generation is required only at the sender. Goto transaction WE21and selecting u201CTransactional RFCu201D under u201CPortsu201D and clicking on u201CCreateu201D at the application toolbar as shown will pop up an option if you want to u201CGenerate port nameu201D or u201COwn port nameu201D. Selecting u201CGenerate port nameu201D will end up in a system generated port name, while selecting u201COwn port nameu201D would ask the user to enter the port name of his choice. You need to provide the RFC destination created in SM59 in the previous steps connecting to client 810.
    Partner Profile: At client 800, you will create the outbound message type, MATMAS. Enter the message type (MATMAS in this case). Mention the port created in the previous step. Select the Output mode as u201CTransfer IDoc immediatelyu201D or u201CCollect IDocsu201D based on the requirement. When u201CCollect IDocsu201D is created, it will ask for the packet size (which tells how many IDocs would be transferred in one LUW) else, packet size is taken as u201C1u201D by default when u201CTransfer IDoc immediatelyu201D is selected. Fill in the u201CBasic Typeu201D (can be obtained from transaction WE82). Click on u201CSaveu201D.
    At the receiver (client 810):
    Port: Not required as we are not sending back any acknowledge messages from the reeiver.
    Partner Profile: At client 810, you will create the inbound message type, MATMAS. Enter the message type (MATMAS in this case). Mention the process code (obtained from transaction WE64). The u201CProcessing by Function Moduleu201D can either be u201CTrigger by background programu201D or u201CTrigger Immediatelyu201D as per the requirement. Click on u201CSaveu201D.
    Hope this makes it clear regarding your query on creating ports and partner profiles.
    ~ Bineah.

  • Logical system and partner profile configuration

    I have a SQL server which is defined as a Business system in my landscape. It is sending records to ECC 6.0 which makes it a JDBC to IDOC scenario (inbound IDocs)
    First question is do I have to mention a logical system name for the SQL server Business system too ?
    Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
    Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
    Thanks in advance.

    Hi Sam,
    > First question is do I have to mention a logical system name for the SQL server Business system too ?
    Yes, In SLD You have to specify logical system name of the SQL server business system while creating SQL system.After importing business system into Integration directory,in Adepter-Specific Identifiers  you can see logical system name of SQL server business sytem which you defined in SLD.
    > Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
    Yes,You have to create Logical system in ECC system for SQL system(Logical system name must be with the same name as logical system name you have given in XI SLD in previous question)
    > Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
    In WE20 You have to maintain partner profiles for SQL server Logical system
    For example: If SQL server Business system name is SQLDEVBS and logical system name is SQLDEVLS
    In ECC you have to create logical system as SQLDEVLS and
    Partner profiles for SQLDEVLS in WE20.
    Please let me know if you have any issues.

  • Multiple Logical Systems in Partner Profile for one instance

    Can we create multiple Logical Systems in Partner Profile (WE20) for one instance or one System?  If it is possible, can we create Logical System with respect to Plant/Country?

    I am not quite sure if I understood your problem completley. But let's see...
    Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
    You can find more information about it in this guide here on SDN:
    Link: [High Availability;
    More information about High Availability Setups for SAP System can be found here on SDN:
    Link: [High Availability]
    If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
    Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|]
    Hope this helps.
    Best regards,

  • Partner profile is not getting updated in FSCM.

    Hi All,
    We are using FSCM for credit management. We have a issue wherein partner profile are not created for a customer.
    We created a customer and hwne checked we found that the partner profile is not there for the customer. We are checking the master data but not able to find the exact reason.
    Can somebody help me solving this issue.

    Which version of ECC are you using?
    In ECC 6.0, you have to activate CVI (Customer Vendor Integration)

  • Limitation on number of partner profiles

    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

Maybe you are looking for