Extension of customers to sales areas

Dear friends,
I have around 5000 customers created in one sales area.Now I have to extend all these customers to another two sales areas.In VD01 manually I can do it.How can I do automatically  extension for all customers?Already customers are uploaded in production server  with first sales area.Now I have to extend all customers for remaining two sales areas in production server.can someone kindly guide me how to do it?
regards,
seetaram

Hello. Probably the easiest way of doing it is via transaction XD99 (Mass Maintenance: Customers). you may want to do it on MASS transaction, object type KNA1.
There you are able to change and/or create customer general data, company code data and sales area data.
You must select all related tables in order to extend sales area data views (KNVV, KNVP, KNVI).
Check field 'do not change existing data' on tab 'Data records to be changed'.
On tab 'Data records to be created' you can:
Create new records for an object
Create new records as a copy of an existing record, thus copying existing values
A record is technically a table entry and normally corresponds to an organizational level such as the plant data record.
Procedure
Enter the selection criteria for creating the new records.
Example 1
You want to create Spanish descriptions for all materials beginning with the letter M (assuming the Spanish descriptions do not already exist). As your selection criteria, you enter M* for the material number, and ES as the language.
Example 2
For the material M-1, you want to create descriptions in all languages defined in the system. As your selection criteria, you enter M-1 as the material number, and * for the language.
Enter the parameters for determining the reference record.
The individual key fields of the reference record are determined as follows:
If you specify a value for a reference parameter, the value you specify becomes the value for the corresponding key field in the reference record.
If you leave one or more of the reference parameters blank, the value you specified for the corresponding parameter for the new record becomes the value for the corresponding key field in the reference record.
If you do not specify any reference parameters, the reference record is identical to the new record. This is equivalent to working without a reference.
Example 3
You have carried out the steps as described in Example 1. The records created include, for example, M-1, M-2, and M-3, each with the language ES. You now have the following options:
As the reference value for the language, you enter EN for English, but leave the material number blank. As a result, the reference records are M-1, M-2, and M-3, each with the language EN.
As the reference value for the material number, you enter M-1, but leave the language blank. As a result, the reference records are M-1, M-1, and M-1, each with the language ES (Spanish).
As the reference values for the material number and language, you enter M-1 and EN (English) respectively. As a result, the reference record is now always M-1 with the language EN (English).
I hope it helps.
Best regards,
Jason Melo

Similar Messages

  • Customers without sales areas

    We are currently unable to save changes against certain business partners in transaction BP due to the error 'No authorization for displaying customers for sales area'.
    This error appears to be raised because the customer associated to the business partner has no 'Sales Area' information.
    Customers were probably created in this manner when we were setting up Business Partners with the Sponsor role for a Grants Management installation - for those Business Partners that could not be linked to an existing Customer, SAP automatically created a 'skeleton' customer record with the minimum of data and therefore no 'Sales Area'.
    Now, I can get around the authorization error by creating the existing customer again in XD01, using the same customer number, but this time entering 'Sales Area' information. This 'new' customer is then picked up by BP and changes to the Business Partner Sponsor role can then saved.
    However, I'm not sure what repercussions having two customer records - one with Sales Area data, one without - would have elsewhere. Is there a better solution? If not, is there a way to create these new records en masse (other than using a keystroke macro), given a large number of customers might have been set up without Sales Area data?

    Vincent,
    Check whether by extending (no need to create new Customer Master ) a single Customer Master you have some unexpeted events happening in system. if it is not affecting your business process anywhere then you can extend  the list of Customer masters by running SCAT.
    In case of any help let em know.
    Reward Points if it helps,
    Regards,
    N

  • AR table needed for customer payment terms specified by sales areas

    Hi Experts,
    What table can I use to see the payment terms of specific customers by sales areas? I have tried T052 and TVZBT but it is not possible to view or filter by sales areas and customers in those sales areas.
    Any help will be appreciated!
    Thanks,
    David

    Hi,
    check the  VBKD: To get sales related Business data like Payment terms etc.(VBELN, ZTERM)
    Regards
    Pramod

  • More than one sales area at 1 catalog

    Hi SDN,
    We have ecommerce 7.0 for SAP R/3.
    We have 1 product catalog at the SAP-system. This product catalog contains articles out of 6 different sales areas. In my case 7000 / 90 / 90, 7000 / 90 / 91,  7000 / 90 / 92, 7000 / 90 / 93,  7000 / 90 / 94, 7000 / 90 / 95. This product catalog couln't be changed because we have an import program for this and wouln't change that. There is no possibility to make 6 catalogs. It must be this one.
    The customers for this shop will have different sales areas:
    7000 / 90 / 90, 7000 / 90 / 91,  7000 / 90 / 92, 7000 / 90 / 93,  7000 / 90 / 94, 7000 / 90 / 95
    Each customer will have only one of this sales areas. Never 2 or more.
    My problem is, the SAP-Catalog only supports one sales area (Trx WWM1). If i set the sales area of the catalog to 7000 / 90 / 90, then only customers with sales area 7000 / 90 / 90 can login to the eshop. If a customer has the sales area 7000 / 90 / 91 he couldn't login to the eshop.
    I've already tryed to set the catalog sales area to an overall area 7000 / 99 / 99. But this worked not. If i set this, the customer needs that overall sales area too. The shop do not support overall sales areas.
    How can i solv this problem? Can you help me please?
    Is there some customizing for the SAP-catalog possible to support more than one sales area?
    Or some customizing possible at the eshop?
    IMPORTANT: We don't have CRM. We have a SAP R/3 (ECC6.0). Please do not give answers for CRM solutions.
    Thanks and best regards,
    Toni

    Hi Tony,
    If it is R/3 backend you are creating your catalog on WWM1. Try to assign a a Cross Division "00" to the catalog and add products from different Sales Areas.
    Do not forget to modify the Sales Area in the ShopAdmin > Transactions.
    Kind Regards,
    Felix.

  • Mass extension of material master to differnt sales area

    Hi,
    How can we extend material master to different sales area enmasse.?
    Regards
    Kantha

    A material master is not just linked to a sales area.
    you have to create sales views per sales org and distribution channel.
    there are many fields in there that need to be maintained, SAP stores this info in table KNVV
    if all data in the new sales area is equal to an existing sales area, then you can easily extend using MM17, if not, then you have to use LSMW.
    MMSC_MASS is for storage location extension, this is certainly not a transaction to create sales area data views.

  • Restrict creation of customers according to account group and sales area.

    Hey Guys,
    I have this scenario wherein we have to restrict the creation of customers according to the sales area and account group. Here is an example.
    Suppose I have a domestic customer say D01. Account group that I am using for this domestic customer is D001. Sales area is say D001/D1/D1. Now for exports I have E01 as customer. Account group is E001. Sales area is E001/E1/E1.
    Scenario is
    I should be able to create D01 only with account group D001 and in sales area D001/D1/D1. Customer D01 should not get created in account group E001 and sales area E001/E1/E1. Now to differentiate export and domestic customers we are using 'D' as a prefix for domestic customers and 'E' for export customers.
    Same thing applies for Exports. Customer E01 should only get created with account group E001 and sales area E001/E1/E1.
    Please advise on the same.
    Appreciate a quick response.
    Thanks in advance.
    Z

    2.1.1     Account Group
    2.1.1.1       Maintain Number Range for Account Group
    Use
    The purpose of this activity is to control number range of Account Group.
    Procedure
    Access the activity using one of the following navigation options:
    IMG --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable --> Customer Accounts --> Master Data --> Preparations for Creating Customer Master Data --> Create Number Ranges for Customer Accounts --> Select the Icon to maintain Number Range
    Transaction Code: SPRO
    Data to be maintained:
    No | From      | To | Current No | Ext (Tick in Check Box)
    01 | 0000000001 | 0000099999 | 0 | No
    02 | 0000100000 | 0000299999 | 0 | No
    XX | A | ZZZZZZZZZZ |      Yes
    2.1.1.2       Assign Number Range to Account Group
    Use
    The purpose of this activity is to maintain number range of Account Group.
    Procedure
    Access the activity using one of the following navigation options:
    IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Assign Number Ranges to Customer Account Groups
    Transaction Code     : SPRO
    Data to be maintained:
    Group | Name | Number Range
    0001 | Sold-to party | XX
    0002 | Goods recipient | XX
    0003 | Payer | XX
    0004 | Bill-to party | XX
    Use External Number Range for Account Group D001 and E001.
    Regards,
    Rajesh Banka
    Edited by: Rajesh Banka on Aug 7, 2008 3:22 PM

  • SALES AREA IS NOT DEFINED FOR CUSTOMERS

    dear All,
    1.I got this error while creating Sales Order,
    "Ship to Party x is not defined for Sales Area".
    2. while creating Customer Master I got the following error.
      "Sales Area  xxxx  10  20  is not defined for customers,"
    Can any body send soln ASAP.
    Thanks and Regards
    RAMS

    Hi,
    i think u have done this
    Define Sales Area
    SPRO
    Enterprise Structure
    Definition
    Sales and Distribution
    Maintain Sales Office
    Go to New entries and define the sales office
    Go to Address Icon and maintain the details and save it.
    Now Maintainain Common distribution channel and common division. common distribution channel and division helps in sharing maste data effectively. Assure you have 10 sales areas. it will b painful process to define a customer at all these areas. instead, it will be wise to create a common distribution channe and division. this can be used as a ref dchnl and divn fo other dchnl and divns. then the master data can be effectivel shared
    Go to Spro: Sales and distribution: Master Data : Define common division and disrtibution channel.
    Hope this will help you.
    Reward ?Point if helpful.
    Thanks,
    Raja

  • SALES AREA MPPS MP LP IS NOT DEFINED FOR CUSTOMERS

    At present I am working on integration of FI module with SD.When I am tryng to create Customer Master Record I am getting the error message "SALES AREA MPPS MP LP is not defined for customers".MPPS , MP , LP are sales org,dist channel,division created by me.Plase give solution.

    Maintain common distribution channel & common division using transaction codes VOR1 & VOR2.

  • Sales area VNMH 01 02 is not defined for customers

    Dear sir.
    I have some  questions, help me.
    I'm creating a customer, but I have an error " Sales area VNMH 01 02 is not defined for customers".
    I want to create plants, but I don't know the path.
    Finanly, how to create branches, departments, storages
    Help me deal the problem.
    Thank you very much.
    Regard,
    Hangvt

    Hi
    Please Check Img>SD>master data-->Common dist. channel / division
    Your Sales org with dist. channel/division will refered by some other dist. channel/division.
    Kindly replace with urs.
    example:
    common dist. channel
    ABCD     AB     AB
    Common division
    ABCD    CD      CD
    Do like this and u will not get the error.
    here we are assisning common reference dist. channel/ division for a dist. channel/ division
    reward if helpfull
    Muthupandiyan

  • Sales area JI00 JI JI is not defined for customers

    i created enterprise struv for SD
    DIVISION     JI
    Plant     JI00
    Sales Organisation     JI00
    Dist Chan     JI
    Divi     JI
    Sales Office     JI00
    Sales Grp     JI0
    Stor Loca     JI00
    Shipping Point     JI00
    Company Code     0001
    and all necessary assignmnets done successfully and consistency chk also , it is OK'
    now i am creating custoemr in XD01 then i got an error as Sales area JI00 JI JI is not defined for customers
    pls guide me wat to do, i am not done any other settings except i mentioned

    Hi,
    please check the following customizing:                                                                               
    - transaction SPRO                                                                               
    > SAP Customizing Implementation Guide                                    
      > Enterprise Structure                                                  
        > Assignment                                                          
          > Sales and Distribution                                            
            > Assign sales office to sales area                                                                               
    > Sales and Distribution -> Master Data                                   
              > Define Common Distribution Channels and Common Division.                                                                               
    - Transactions need to also be checked and maintaained if neccessary:     
         -> OVXG:  Define sales area                                          
         -> VOR1:  Joint Master Data: Distr. Channel                          
         -> VOR2:  Joint Master Data: Distr. Division                         
    Kind regards,
    Zsuzsanna

  • Sales area ABCD CB AB is not defined for customers

    Hi Guru,
                  When I was trying to create customer T-CODE:  XD01
    Getting following  error:
    Sales area ABCD CB AB is not defined for customers
    I am working on ECC6.
    could you please help me out?
    Regards,
    sha

    Hi
    Please Check Img>SD>master data-->Common dist. channel / division
    Your Sales org with dist. channel/division will refered by some other dist. channel/division.
    Kindly replace with urs.
    example:
    common dist. channel
    ABCD     AB     AB
    Common division
    ABCD    CD      CD
    Do like this and u will not get the error.
    here we are assisning common reference dist. channel/ division for a dist. channel/ division
    reward if helpfull
    Muthupandiyan

  • "Sales Area zzzz zz zz is not Defined for Customers"

    Hi All
             I am trying to create a customer using XD01. In my org structure there is only one sales org, one dist channle, one division and hence One Sales Area zzzz zz zz which I have set up in IMG. The Error I am getting is
    "Sales Area zzzz zz zz is not Defined for Customers"
    And Peformance Assistant gives the following message
    Message no. F2644
    Diagnosis
    The sales area specified has either not been defined (i.e. there is no entry in table TVTA) or it refers to another sales area for customers (customer division/customer distribution channel in the TVTA detail screen). This means that the customer master data of the sales area entered correspond to the data in the reference sales area and customer master data only needs to be maintained for this reference sales area.
    Procedure
    You can display the relevant and therefore valid sales areas for customers by selecting "Extras" -> "Sales areas" -> "All areas".
    I have already checked that
    1)My Sales area has been defined and Sales org is assigned to company code, Dist Channel and Division is assigned to Sales Org
    2)In Table TVTA my Sales Area Exist...
    3)I have tried creating my sales org by copying IDES sales org as well as creating a NEW sales org...however the error is still there
    Any Ideas???
    Thanks
    Raj

    Hi!
       This error is coming due to assinment is not made for common Divisions. You can assign this by going to SPRO>S&D>Define common divisions. Here you assign sales org ZZZZ , division ZZ, division for conditions ZZ, division for Customers ZZ. Then try to create customer master for ZZZZ ZZ ZZ .
    This assignment for master data can be created in one sales area and that can be referenced to other sales areas also without creating again.Read the help below for details.
    Define Common Divisions
         In this step, you define the divisions that common master data should
         apply to. The definition is valid within each sales organization.
         Example
         You can determine, for example, that the conditions which are valid in
         division "01" also apply to divisions "05" and "06".
         Note
         The common master data across various divisions refer to the conditions
         and the customer master data.
         You thus minimize the effort of entering and managing master data.
         In addition, you can extrapolate your own statistics per division
         without having to create master data in the different organizational
         subareas.
         Action
         For the divisions, define from which other division the master data
         should be copied.

  • Restrict extension of sales area to customer.

    How to restrict a customer master only for one sales area. Is this possible?
    i.e. the customer master is than not extended to another sales area.
    Thanks,

    Hi,
    You can give XD01 & XD02 authorizations to only allowed users. This will ensure that a particular sales customer is never extended by any other user.
    If you try to create an order in a sales order where the customer is not extended, then the system will throw an error.
    I presume this is the best possible way to solve your query.
    If helpful, please dont forget to reward points for contribution.
    Regards
    Ravi

  • COMMPR01 - sales area extension

    Hi All,
    We have the Sales areas downloaded from ECC and Org model is up to date.
       In the commpr01 transaction, when I go to extend the SAles area to the newly downloaded sales area; system is not displaying the newly downloaded sales area.
      could you please revert with the information on how to map the Product to newly downloaded sales areas.
    Best Regards,
    RLS

    HI
    1. From your problem it seems that, the materials are also downloaded from ECC.
    2. When the materials are downloaded from ECC to CRM, then the material has to be extended in ECC first and then through DELTA DOWNLOAD it will flow to CRM.
    3. Hence, please extend the material in the required SALES AREA in ECC. Once replicated, you will see that in COMMPR01 also.
    Hope this will help.
    Regards

  • Error while posting Customer with Multiple sales areas using DEBMAS05.

    Dear experts,
    We are generating IDOCS vis SAP DS for posting Customer master. The message type used is DEBMAS and basic type is DEBMAS05.  we have a requirement to create 1 customer with multiple sales areas. However, we are ending up with a strange error:  "Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1". Despite the IDOC going into status 51, the customer gets created and the 1st sales area too. the 2nd sales area however is not created!  The IDOC data definitely contains Name1, otherwise the customer would not have been created in the first place.
    As the error message is related to the Address data, I also explored upon exploring this erorr further on the lines of Central Address management where in the ADRMAS and DEBMAS have to be passed together(IDOC Serialiization).  OSS Note (384462)  provides further details about this. One Important point from the note is: 
    "As you have to specify the logical name of the sending system among other things, SAP is not able to make any default settings in the standard systems. When you use the serialization groups delivered as a standard by SAP, the address objects are imported before the master objects.Thus the sequence address data before master objects must only be adhered to if one of the following points applies to your application:
    Such fields are set as required entry fields that are only provided by the BAS in the Customizing of the customer or vendor master.
    For your customers, contact persons exist to which a private address or a different business address is assigned.".
    This is not the case in our situation, as we do not have required entry fields in customizing that are only provided by the BAS, so the error is all the more confusing and I am not too sure what the cause is.
    If someone have experienced the same issue before and have found a solution to it, kindly help out.

    I have found the cause and solution to this problem.
    This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
    This was resolved by splitting the IDOC into 2.
    The solution is to First post only the KNA1 segment and create the customer.
    In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”:  you would have got the KUNNR after the first step.
    Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC. 
    I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
    Cheers
    Venkat

Maybe you are looking for