CREATION OF CUSTOMER PARTNER FUNCTIONS IN LSMW

Hi
I want to add more partner functions to customer master through lsmw in change mode. I developed a LSMW for this using transaction code XD02 with recording of partner function screen only. when i run the batch input session, it shows all the records processed sucessfully. But actually it does not add any record to partner functions. Can you help pls as how to add more partner functions to customer master in change mode using LSMW
thanks in advance
Best Regards,
SAVIO

Hi James,
Did you map the partner functions like sold to party(SP), Ship to party(SH), Bill to party(BP) and payee(PY) functions on your sheet. If so, what is the error msg u r getting??
Regards
Aravind

Similar Messages

  • CREATION OF CUSTOMER PARTNER FUNCTIONS IN LSMW   (URGENT)

    hi experts ,
    iam using lsmw, batch/direct input method using object "0050", method "0000", program name "RFBIDE00". iam sucessfully able to map field values for the mandatory fields for transaction"xd01", but while executing the session, in the last screen the system ask's me for the partner function values, iam unable to assign/map values to the partner function from the flat file....
    pls help me out on resolving the issue ...
    Regards,
    James...
    Valuable answers will be rewarded.......

    Hi James,
    Did you map the partner functions like sold to party(SP), Ship to party(SH), Bill to party(BP) and payee(PY) functions on your sheet. If so, what is the error msg u r getting??
    Regards
    Aravind

  • Adding N-number of customer partner functions to a customer using LSMW.....

    Hi Abapers,
              I had a requirement to add some 500-600 customer partner functions(bill-to-party,payer,ship-to-party) to a single customer(sales rep or employee customer) using LSMW.
              I uploaded the customer(500) master using LSMW, and i want to add 499 customer partner functions(bill-to-party,payer,ship-to-party) to the 1st customer .
              So, i want to know how to do this using LSMW or BDC, and give me suggestions to overcome this....
    Thanks,
    Dilip.B

    I have responded to similar queries in one of the threads.
    Please find the URL of that discussion:
    [Re: LSMW   |Re: LSMW]
    Instead of Vendor you need to use CUSTOMER number and Chose the standard customer master program for LSMW. In recording you wont be able to acheve this.
    Hope this helps.

  • Custome Partner Function from SD to CO-PA

    Hi,
    I have created 3 custom partner functions and have assinged in customer master. I need these 3 custom partner function to be transfered to CO-PA during billing. Is there a easy way around to achieve this, coz there are some SAP notes which are sort of confusing and complex, since we are already live in production, we cant take a chance on the SAP Note.
    If somebody experienced like this, could you please share the knowledge, how to achieve this.
    Thanks.
    With Regards
    gj

    Hi Gj,
    There are no simple way around to get the customer partner function in to CO-PA during billing. You must follow the notes to get the correct value transfered to CO-PA. I will outline the steps below so that you do not miss anything.
    I am going to try to summarize the basic steps to add one or
    more new partner function(s).  For more detailed information
    please see the notes 36557, 32878, 12682 and 93658 although some o
    these notes are known for you.
    Add new domain/data element for the new partner function in the
    ABAP/4 Data Dictionary.
      Examples are the data elements KUNAG, KUNWE, KUNRE, KUNRG,
      SPDNR, and VRTNR in structure MCPARTNER. This is where the
      partner functions for the Standard Sales Information System are
      defined.
    Save the new partner field in structure MCPARTUSR (user part of
      structure MCPARTNER) or, if available extend structure
      MCPARTUSR by an append structure (ZAMCPARTUS).
    Make sure that the check tables and foreign key relationships are
      maintained for the new fields in structure MCPARTUSR
    Define the assignment of partner function <  > new partner
      field in the communication structure.
      Program RMCSUZ10, routine USR_PARTNER_GET.
      Add the line as in the example of note 12682 given.
    Include the corresponding field via transaction 'KEA0' from the
      structure PAPARTNER into the Profitability Analysis data structures
    If your new partnerrole is a representative/sales employee please
      apply note 32878.
    Should you have implemented note 43002 (to prevent a field overflow
      in pricing) please follow note 93658 and use userexit
      userexit_pricing_prepare_tkomp instead of
      userexit_pricing_prepare_tkomk.
      userexit_pricing_prepare_tkomp is contained in Include MV45AFZZ
      (sales order) and RV60AFZZ (billing)
    Add the new field to the structure 'KOMPAZ' as in note 93658
      described and  NOT  to the structure 'KOMKAZ' (note 36557)
      (you have used both structures)
    Generate the operating concern and check if the following entries
      are included in TKEZU:
      Charact.  BTran Table      Field name  Offset  Length
      XXXXX     KEDR  KOMP      YYYYY
      XXXXX     KEDR  KOMP      YYYYY
      XXXXX     KEDR  KOMP      YYYYY
      XXXXX = Field name of the partner function in the  profitability
      analysis
      YYYYY = Field name of the partner function in structure KOMP
    (these entries should be made automatically here).
    If you need more than one partner function please repeat the
    steps as described above for your need.
    Regards,
    Abhisek

  • Help for custom Partner Function

    Hi,
    I'm on SRM 5.0 ECS.
    I create two custom partner function and now I need to add they a search help.
    How can I do this?
    I will take data from R3, but I know how to build a search help, I need to know how give it to the partner function.
    thanks
    enzo

    I solved.

  • Customer Partner Function

    Hello Experts,
    I am from EHS Module.. I am creatig Scenario for report Shipping.
    In that I am creating Customer.
    I am using Account Group: 0002 Goods Receipts
    As per SAP Guide,
    "If User created the customer in the account group 0002, the SR (MSDS Recipient) and WE ( Goods Receipient) functions will appear automatically in Customer Partner Function.
    But when I am creating Customer in My system using account group 0002, those mentioned Customer Partner Funcition are not getting cretaed Automatically instaed SH ( GOods Receipt) is getting created.
    Could you please guide me what setting I need to do in order to create Customer Partner Function SR (MSDS Recipient) and WE ( Goods Receipient)  Automatically while creating Customer.
    Thanking You
    Regards
    Amol

    Hi,
    IMG >>> SD >>> Basic functions >>> Partner determination
    First you create partner determination procedure or copy from std. AG
    Then double click on partner functions in procedure
    Include your two partner functions in procedure and tick mark to mandatory (Also remove tick marks of other partner functions which u don't need)
    Now double click partner determination procedure assignment
    Assign partner functions in front of account group - 0002
    Now double click on Account group - Function assignment
    Assign account groups in front of your two partner function
    Then create customer partner functions will come automatically
    Kapil

  • Need a user exit to add custom partner function in sales order @ item level

    Hi,
    Need a user exit to add custom partner function in sales order at item level. Goto --> Item --> Partner.
    Thanks,
    Thiyagi

    HI Leo
      To add a condition price for a condition type, this has to be assigned in the <b>pricing procedure</b>. For each condition type in a pricing procedure, we will have <b>access sequences</b>. If we follow this approch, the price is automatically extracted basing on the access sequences when condition records are maintained. For this, no coding is required and everything can be done by configuration by Functional consultant.
       Naren is right to point out on the same.
      If you need to change the price for a particular condition which already exists, you can go by <b>pricing routines</b>. Go through transaction <b>VOFM</b> for the same. 
       I advice you to discuss with your functional consultant and understand the requirement and then go for modifying accordingly.
    Kind Regards
    Eswar

  • LIS enhancement MCS10001 and customized partner function

    Dear all,
    We have a customized partner function (in addition to sold-to, bill-to, payer and ship-to) in SO and we would like to capture the value of it to BW
    However, I can't do it in enhancement MCS10001
    Could anybody suggest possible solution to it?
    Thanks in advance
    Steve

    Dear all,
    Could anybody suggest solution for my problem?
    Valuable answer will be awarded
    thanks
    Steve

  • Customer block VD05, for SO customized partner function

    Dear all,
    Good day!
    I was trying to block customer using VD05, to ensure this customer will not be used in SD Transaction, SO, DO, Billing.  It works for the Sold to party, Ship to party partner function in documents, but doesnt work for the customised partner function for eg ZC - Consignee.
    Is there anyway to make blocked customers, cannot be used in customized partner function as well?
    Thanks in advance
    Kevin

    Hi,
    In your case, I would use userexits to check it in customer updation, SO documents, invoices and so on.
    I hope this helps you,
    Regards,
    Eduardo

  • Sales Area check for custom partner function

    When processing sales orders in our system, it does not check the sales area for the customer of a custom partner function.  Can this be setup via config or is there a an exit that can be used for this.
    Thanks,
    Roy

    Yogesh -- Thanks for your response. However, it does not address the functionality issue.
    Currently, I created new partner function ZZ (for example).
    I assigned this partner function ZZ to account group Z000.
    I created new partner XYZ in account group Z000, in sales area XX00/XX/XX.
    I created a sales order in sales area YY00/YY/YY.
    Problem is that system allows me to assign partner XYZ to this sales order.
    How do I prevent this?
    How do I enfore that system will only allow partner XYZ in the sales order, if the partner is created in the same sales area?
    Edited by: krist d on Dec 13, 2010 4:33 AM

  • Org determination in transaction based on custom Partner Function

    Hi All,
    I am trying to figure out how can I modify the partner determination procedure and org data profile to determine the sales area (org,dc,div,so,sg) in a transaction automatically without having to choose the sales org.
    Here is the set up:
    Sales Org ->Soff->Sales group are permitted for Org determination in ppoma_crm.
    Custom Partner Functions - Y1 and Y2 assigned to Sales Partner Function Category
    Access Sequence YXXX has the following set up:
          Source                        PF                 Function Category          Usage
    10  COM_PARTNER_A
    20 CRM_PARTNER_C  Sold to Party 
    30 CRM_PARTNER_C                         Activity Partner                 CRM
    40 CRM_PARTNER_C Sales Prospect
    50 CRM_PARTNER_C Activity Partner
    Partner Procedure YPP001 has the following setup:
    Function    Access Sequence
    14              User                         Recurring
    15              YXXX                       Recurring
    21              0001                        Recurring
    23              YXXX                       Recurring
    Y001                                           Recurring
    Y002                                          Recurring
    Y1            YXXX                       Recurring
    Y2            YXXX                        Recurring
    Org Data Profile YORGPROF01 is maintained for Scenario SALES with Org Model Deter Rule 10000177. Sorg and Dc mandatory set.
    The transaction type YOPP is configured as shown:
    Org Profile YORGPROF01
    Partn Func Org Activity Partner
    Partner Determination Proc YPP001
    Now here is the issue:
    We want that when we create transaction YOPP it should fill the Org data including Sales Office and Sales group from the partner associated with the PF Y1 which gets assigned automatically when the account is selected on the transaction.
    With the above setting, it populates all the sales offices and sales groups that have been marked for determination in ppoma_crm (which we don't want it to do). We need it marked for determination so the BP's master data associated with Y1 shows up the sales group and sales office.
    When the account is selected on the transaction and Y1 is determined via partner determination, we would want the sales Org also to get determined automatically from the Y1 partner's master data.
    Anything that can be changed in the above settings to make this happen?
    Thanks
    PC

    Hi
    Although i have no practical experience with this but an educated guess would be to use Partner function determination . If you have 'employee responsible ' PF , Then u can further use him for org determination.
    May be this helps...
    Regards
    Ruchi

  • How can I add customer partner function entries in LSMW?

    I am using SAP ECC 6.0 with best practices installed. I am able to create sold-to customers using the batch input program RFBIDE00. 
    When I try to add partner function entries using structure BKNVP, it appears that the partner ID stored in KTONR is not populating SAPMF02D screen 324 after it is entered on screen 2324. I receive a “Data is incomplete; check” error.  I could not find an SAP note or other solution to correct this problem. 
    While searching for a solution, I found a few recommendations to use the IDOC message DEBMAS to create the partners function entries instead of batch input.  When I try to use this approach, I am receiving an error “Deletion is not allowed: SP is mandatory function”.  I was trying to add an SH (WE Ship-To) at the time. I found a reference that explained that all partners were replaced when this IDOC message is used.  It further explained that this should work if all partner references were included in the message.  This approach did not work either. I still receive this error if I omit or include an SP (AG Sold-To) record.
    Does anyone have a solution to either problem or another approach?

    Hi
       You can use LSMW :-
    1) Create a project , sub project and an object.
    2) execute it from 1 st screen to enter the object.
    3) You will find proces steps.
    4) In Maintain Object Attributes  choose Program Name RFBIDE00.
    or I-DOC or the way you want the input to be.
    5) You can proceed from there following the instruction..

  • Creation of new partner function for VENDOR

    Hi,
    I've a requirement to create some Partner functions for vendors while creation of vendor. Some Partner functions are available by default and some we need to add. but while doing a BDC we are not able to find how many of them are available or where to put the new Partner function?
    Please let me know, if there is any BAPI availble..
    Regards,
    Anupam

    Try below LSMW batch input method its very esay to upload data
    Object               0040   Vendor master
    Method               0001   Standard
    Program Name         RFBIKR00
    Program Type         B   Batch Input

  • Partner function upload-lsmw

    Dear Experts,
    how to upload partner functions by using LSMW. I developed LSMW and if i go to partner function tab there is only one partner function field is available I need to upload 4 partner functions. Can any one help me out in this regard.
    regards,
    siva

    Hello Sivasai Myneni,
    Demo Example 1
    LSMW to Update Customer Master Records with Transaction Recording
    Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as
    Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as
    CUST_obj as shown in Figure 1.
    Figure 1 Conversion Task with Project, Subproject and Object
    The main screen of LSMW provides wizard-like step-by-step tasks, as shown in Figure 2. To complete your data conversion, you
    need to execute these steps in sequence. Once a step is executed, the cursor is automatically positioned to the next step.
    Note that these steps may look different depending upon your Personal menu settings. You could make step numbers visible by
    ‘Numbers on’ icon or hidden by ‘Numbers off’ icon. You can execute a step by double-clicking on the row. Toggle icon
    ‘Doubleclick=Display’ or ‘Doubleclick=Edit’, makes the step in ‘display’ mode or ‘change’ mode.
    Figure 2 LSMW Wizard – initial screen
    Step 1: Maintain Object attributes
    In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio
    button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as
    XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.
    Figure 3 Object type ‘Transaction Recording’
    The system calls the transaction code XD02 and prompts you to complete the Change
    Customer transaction, as shown in Figure 4. Enter the key customer information (I entered customer number 1000, sales
    organization 1000, distribution channel 01, and division 00) and choose ‘Sales’ view within ‘Sales area data’. Make changes to
    these three fields (I entered, sales office 1010, sales group 110, and customer group 01) and save the transaction.
    Figure 4 Transaction recording for Transaction Code ‘XD02’
    Once the transaction is completed, R/3 records the flow of screens and fields and saves the information, as shown in Figure 5.
    Figure 5 Transaction recording overview
    Note that the fields are populated with default values. The values you entered when you recorded the transaction are set by
    default.
    Note that if you have more fields in the recording than needed, you can remove them by clicking ‘Remove Screen field’ icon.
    Observe that the transaction-recording process stores field names in a technical format. By pressing the F1 key on individual
    screen fields and then pressing the F9 key, the system displays technical names. You then can replace the technical names with
    descriptive names. Double-click on the field RF02D-KUNNR and enter the name as KUNNR and the description as Customer
    Account Number and remove the default value. (See Figure 6.)
    Figure 6 Field attributes
    Similarly, double-click on all other fields with default values and make appropriate changes. Once you have made changes, the
    recording overview screen looks like what you see in Figure 7.
    Figure 7 Transaction Recording Overview – with screen field attributes
    Save your changes. When you go back to the initial screen, you will see that the initial screen steps have changed. Since you want
    to import data via the BDC method, the Direct Input and IDoc-related steps are hidden, as they are not relevant.
    Step 2. Maintain Source Structures
    Give a name and a description to the source structure (Figure 8).
    Figure 8 Source Structure
    Step 3. Maintain Source Fields
    In this step, you need to list what fields are present in the source structure. The easiest way is to click on ‘Table Maintenance’ icon
    to enter Fieldname, Type and Length for each field as shown in Figure 9.
    Figure 9 Source fields of source Structure
    Note that your input file will have four fields as key fields and you need to update three fields in the system.
    Step 4: Maintain Structure Relations
    Execute a step to ‘Maintain Structure Relations’. (See Figure 10.) Since, there is only one Source and Target Structure, the
    relationship is defaulted automatically.
    Figure 10 Structure Relation
    Step 5: Maintain field mapping and conversion rules
    Field RF02D-D0310 represents that you chose ‘Sales view’ for the customer Master screen accordingly its value should be set to
    X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of ‘X’.
    If your source file already has the field value, you choose rule ‘Source Field’.
    Keep cursor on field ‘KUNNR’ and click on ‘Assign Source field’ icon to choose source field CUSTOMER from structure XD02S as
    shown in Figure 11.
    Figure 11 Assign source fields
    Similarly, assign ‘Source Field’ rules to the remaining fields.
    Once all the fields are mapped, you should have an overview screen as shown in Figure 12.
    Figure 12 Field mapping and Conversion rules overview
    Step 6: Maintain fixed values, translations, user-defined routines
    You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case,
    that step is not required.
    Step 7: Specify files
    In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is
    present on my PC (local drive) as C:\XD02.txt. (See Figure 13.)
    Figure 13 File attributes
    Create an Excel file (Figure 14) with your data and save it as a Tab-delimited text file on your local drive (C:\) and name it XD02.
    txt.
    Figure 14 Source data in Excel file (saved as Tab delimited file)
    Step 8: Assign files
    Execute step ‘Assign Files’ (Figure 15) and the system automatically defaults the filename to the source structure.
    Figure 15 Assign file to Source Structure
    Step 9: Read data
    In this step, LSMW reads the data (Figure 16) from the source file (from your PC’s local drive). You have the option to read only
    selected rows and convert data values to Internal format.
    Figure 16 Read Data
    Step 10: Display read data
    This step (Figure 17) is optional. If required, you can review the field contents for the rows of data read.
    Figure 17 Display Read Data
    Step 11: Convert data
    This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined,
    source fields are mapped to target fields.
    Step 12: Display Converted data
    Again this is an optional step to view how the source data is converted to internal SAP format (Figure 18).
    Figure 18 Display Converted Data
    Step 13: Create batch input session
    Once the source data is converted in an internal format, you can create a batch session to process updates (Figure 19).
    Figure 19 Create Batch Input Session
    Step 14: Run Batch Input Session
    You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for
    managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in
    the system. You can confirm this by viewing the customer master records (XD03).
    Note! Browsing thru these 14 steps, you may get a feeling that this is a very lengthy and time-consuming activity. However, for
    the purposes of demonstration, I have made it detailed. Although it looks lengthy, actually it takes hardly few hours from start-to-
    finish! After playing around with few simple LSMW scripts, you will find it so easy to change and create more complex ones.
    Demo Example 2
    LSMW to Update Customer Master Records with Standard Object
    As an alternative to using ‘Transaction Recording’, you could also use a standard SAP object to update Customer Master Records.
    Business Object ‘0050’ is already pre-defined in the system with standard Batch Input Interface Program ‘RFBIDE00’.
    Create an Object CUST_OBJ within Project as LSMW_DEMO and Subproject as CUSTOMERS as shown in Figure 20.
    Figure 20 LSMW Object with Standard SAP Object
    Note! For the Demo example 2, I will list only those steps that are different from the first demo example.
    Step 1: Maintain Object attributes
    You will be updating the customer master records with the help of Standard Batch Input; therefore, choose radio-button Standard
    Batch/Direct Input as shown in Figure 21. Enter Object ‘0050’ for Customer Master records and default method ‘0000’ and click
    on Save.
    Figure 21 Standard Batch/Direct Input Object Attributes
    Step 4: Maintain Structure Relations
    Sales view of Customer Master is stored in table KNVV. Accordingly, you need to update structure BKNVV. However, in addition,
    the Standard Object ‘0050’ also requires updates to BGR00, BKN00 and BKNA1 structures. (If you do not maintain Structure
    relations for mandatory entries, you might get a message such as ‘Target structure BKNA1 needs a relation to a source structure’.)
    Even though you don’t want to update any fields in these structures, you need to create a relationship with source structures. In
    all, you need to create relationship for four target structures.
    Create relationship between source structures XD02S with these target structures with icon ‘Create Relationship’ .
    Keep Cursor on these four target structures and click on icon ‘Create Relation’ and structure relations are maintained as shown in
    Figure 22.
    Figure 22 Structure Relation
    Step 5: Maintain field mapping and conversion rules
    – Keep your cursor on ‘TCODE’ field and click on ‘Insert Rule’ icon
    Figure 23 LSMW Conversion Rules
    Choose radio button ‘Constant’ (Figure 23) to enter value ‘XD02’ transaction code.
    – Keep your cursor on field ‘KUNNR’ and click on ‘Assign source field’ icon
    Choose source field ‘Customer’ from source structure ‘XD02S’. (See Figure 24.)
    Figure 24 Assign Source fields
    – Similarly, choose source fields for Sales Organization, Distribution Channel, and Division. (See Figure 25.)
    Figure 25 Field Mapping and Conversion Rules
    – Scroll down to structure BKNVV fields and assign source fields to three fields Sales Office, Sales Group, and Customer Group
    (Figure 26).
    Figure 26 Field Mapping and Conversion Rules
    Save and go back to main screen.
    Step 12: Display Converted data
    When you convert data, LSMW automatically converts into the appropriate structure layouts, as required by Standard program
    (RFBIDE00). (See Figure 27).
    Figure 27 Converted data into multiple structures
    Note that if you had only one record in source file, the converted file has four records.
    Earlier, creating this input file, so that the standard interface program can read it, was a big nightmare, the primary reason being
    that it could have multiple record layouts. Even for a simple conversion with one input record, you would have to create this
    complex file with many record layouts. The advantage of LSMW is that it prepares these multi-layout files automatically.
    Step 13: Create batch input session
    Once source data is converted in internal format, you can create a BDC session to process the updates (Figures 28 and 29).
    Figure 28 Create BDC Session
    Figure 29 BDC Session ‘CUST_OBJ’ created
    Regards
    AK

  • Amend Customer Partner Functions

    HI,
    I have a requirement to change a default  partner function that has been created as part as an interface that creates the customer in sap from an external system.
    For example, a Payer partner function has been created with Customer No 9999 and it should be 9998.
    What is the best solution for achieving this?
    thank you for your help
    I

    For this you can use below LSMW method through XD02 tcode
    Object               0050   Customer master
    Method               0002   Extended PSM
    Program Name         RFBIDEK0
    Program Type         B   Batch Input

Maybe you are looking for