Sales Area Creation

Hi Everyone,
I have a problem here and appreciate if somebody can help me.
I created a sales area 9090/90/90
When I try to create a customer master with VD01 and click on All Sales Areas, my sales area shows here as 9090/01/01.
Where am I going wrong.

Hi
In VD01 the sales area you see is the one customer is created for..if you want to extend it to the new sales area
You've to key in the sales area manually and create it.
Regards
Raghu.

Similar Messages

Sales area creation for existing customer

Hi Guru's,
Good Day to all.. .
Here my requirement is i need to update the customer data in KNVV table based on below conditions.
My Selection screen is
Customer :
Sales Org :
My checks are...
The program has to check if each inserted customer (select options) is opened on all the sales areas based on the inserted sales organizations (salesorganization + Distr. Channel = “FF” + Division = “AA”/”BB”/”CC”/”DD“).
If the involved customer isn’t created on all the sales areas (select options) it must be automatically opened on the missing ones.
It means before creating i need check that customer is available in the above mentioned divisons or not.?
If customer is not available with the above divisions i need to create a new reocrd with missing division (remaing field values are same only diviosion will get change)
For this do we have any BAPI's . I have checked few but i could not find the correct one.
Can anyone please help in this regards.
Thanks in Advance
Sravan Kumar

Hi there,
Customer master data will usually have external num assignment where you will give the customer num manually. If that is the case, create a new customer master ABCD in VD01 for sales area 1000 / 01 / 01 for eg. If you want to extend the same customer to a different sales area, then in VD01, give the custromer name ABCD & give new sales area details 2000 / 02 / 02. Then ABCD will be extended to both sales areas. But make sure that you assign the shipping / billing & partner data accordingly.
Same way if you want to extend the customer to different company code. You do it in XD01.
Is this what you asked?
Regards,
Sivanand

Restrict the creation of customer master records at sales area level

I know that you can supress fields at the company code and sales area level in customer master, but, is there a way in configuration to restrict the creation of a customer master record at the company code and sales area levels? Only the general data level is needed for this customer account group.
Any help would be greatly appreciated!!

Hi
Create the Customer Master without entering the Company Code and sales Area. The system will allow and ask you to fill only the General Data.
The other way is that Create a Account Group and suppress its all Fields of Accounting View and Sales Area View, so that for that account group you will have to maitain only the General view.
Regards
Amitesh Anand

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Business Partner creation - Sales Area Data retrieves blank divisions

During business partner creation, the sales area data assignment block will retrieve a list of all relevant sales organizations, distribution channels, and divisions that are replicated from ECC. This is working fine. However, it also adds to this list with the sales organizations, distribution channels, and blank divisions. Blank divisions do not exist in either ECC or CRM. It appears to be using the dummy division settings, but I have attempted to configure with the indicator "CRM Header Div. Active" as both active and inactive, to no effect. The only time I have been able to condense this list into a single line has been when I actually activated dummy divisions -- to which CRM would now retrieve only sales organizations, distribution channels, and blank divisions. This is not an ideal solution either.
How do I get the system to remove the blank divisions from being displayed? It is very confusing to the users, not to mention polluting the screen.
Example (both are being displayed, I only want the one with an actual value to be displayed):
Sales Org = 1000, Dist Chan = 10, Division = blank
Sales Org = 1000, Dist Chan = 10, Division = 10

any insight woudl be much appreciated. thanks.

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

How many table are affected when sales order creation(O2C)

Hi all,
HOw many table are affected when sales order creation, can any one please help ,and please give me a description indepth please please. I know some of the table affected
Thanks&Regrads,
Surya

Hi Kantur Shekar madhuri,
Would you confirm the whether in your schedule line category is activated for "Product Allocation" or not.
if not please activate and re run your scenario.
Regards
Arun

Hide Sales Areas with division during BP change/creation

Hi,
in the BP Change or create process you can assign sales areas. In our application we see our sales areas twice. One are with divion and one sales area without division assigned to the same sales organisation and distribution channel.
In CRM we want to enter data just for sales areas without divisions during BP creation/change. Is it possible to hide the sales areas with divisions ?
Thanks for help,
Oliver

Hi
I am guessing that you have downloaded the sales org structure from R/3. What version CRM are you running? Do you have Division active?
Have a look at note 720488 and 742796 (+ 774689 - part II).
Cheers
Dom

Automatic creation of Company Code and Sales Area Data for Customer Master

Hi,
We have a organisation structure setup with multiple company codes and sales areas.
A customer will be created using VD01 via the Sales Order VA01. Because the customers are created using VD01 we need to automatically extend the customer for the various company codes and sales areas. The data on these views will be populated using reference customers.
Any recommendations on the best approach (technically) to auto extend the customer master would be appreciated.
I'm reluctant to use BDC's because of performance. We are in a Retail environment.
Thanks in advance
Craig

The sample code has been taken from the SAP notes - in which have the affected as outlined in the example.
The codes does not do what my requirements are, which is to identify the next available number in isolation of the BP type.

Default Sales area data during BP Account creation in WebUI

Hello everyone,
I have got a requirement where I need to populate Sales, Shipping and Billing data whenever a BP Account is created in WebUI.
Based on Sales Org selected the corresponding details as to be populated by default. This functionality exists in standard BP transaction whenever we create a BP in Sold-to-Party and select Sales Org.
Can we implement the same functionality in WebUI as well using any standard Function modules.
Please Help.
Thanks in Advance,
Naveen

Hi Pratyasha!
Thanks for your reply. I figured, that by explicitly calling the commit FM, system commit procedures are interrupted.
The thing is, that just by calling the FM for adding the sales areas does not result in those sales areas acutally created. What I mean is, that after the BAdI is executed, no sales areas are maintained for the newly created customer. All the more funny, since this exact same procedure is working for creating relationships. See following code:
READ TABLE it_changed_instances INTO ls_changed_instances INDEX 1.
* Get BP-Number for sy-user
CALL FUNCTION 'CRM_ISA_IUSER_GET_BP_TO_ALIAS'
    EXPORTING
      username         = sy-uname
    IMPORTING
      business_partner = lv_user_partner.
* Map GUID to partner number
CALL FUNCTION 'BUPA_NUMBERS_GET'
    EXPORTING
      iv_partner_guid = ls_changed_instances
    IMPORTING
      ev_partner      = lv_partner
    TABLES
      et_return       = lt_return.
CLEAR lt_return.
* Create employee responsible
CALL FUNCTION 'BUPR_RELATIONSHIP_CREATE'
    EXPORTING
      iv_partner_1_guid = ls_changed_instances
      iv_partner_2      = lv_user_partner
      iv_relationship   = 'BUR011'
      iv_date_from      = sy-datlo
      iv_date_to        = '99991231'
      iv_testrun        = ' '
      iv_x_save         = ' '
      iv_xdfrel         = 'X'
    TABLES
      et_return         = lt_return.
which is in the same BAdI and acutally results in this relationship beeing created for my newly created customer. Works fine, just not for sales areas.
I´ll be grateful for any comments on that issue!
Kind regards
Christoph

Account Creation - Badi for Default values for BP Role and Sales Area

Hi all,
my requirement regards the possibility to create a new prospect (a link should be available in the navigation bar or create section).
Logically, a bp role as "Prospect" and particoular sales area should be created automatically.
I created an implementation for the BADI definition "BADI_CRM_BP_UIU_DEFAULTS". But don't know how to create the default values for BP role and Sales area:
In my code
assign cr_me->('VIEW') to <lv_view_name>.
if sy-subrc ne 0.
exit.
endif.
lv_viewname = <lv_view_name>.
case lv_viewname.
when 'AccountDetails.htm'.
I obtain the viewname "AccountDetails" , the related context "Header". After I don't know how to proceed to obtain the related entities through the relationship BuilRolesRel and BuilSalesArrangementRel.
Am I following the right way? Is there another solution to prepare the output for default values?
Any kind of suggestion will be appreciated.
Regards, Roberto

go to spro>cross-application components>sap busines partner>business partner> basic settings>field groupings>Configure Field Attributes per BP Role
Double click the business role which you want to customaze (e.g. 'A') and change the proper settings.
Regards.

BP Creation in Web UI - How to enable Sales Area data?

Hello Gurus
We are using CRM 2007 and create BPs in CRM and then have them replicate to OLTP. This works as desired if I launch Transaction BP and maintain the record.
But in Web UI, I dont see many of the fields that are necessary for replication such as Account group for R/3 customer acct group. Nor do I see a tab for sales area data maintenance. I am logging on to Web UI with SALESPRO profile. How do I enable enter of key information in Web UI BP maintenance, so that I could see the replication from CRM to OLTP R/3.
Please advice.
Thanks
Jai

Hi Jai,
I am glad that the answer was helpful for you.
In the create mode just the details view is available, as this is the way the component BP_HEAD is implemented.
To understand this please open the component workbench, component BP_HEAD. Go to the runtime repository and compare the window CorpAccountNew(this is for the create mode) with the default window named MainWindow. In the first one just a sole view is offered.
But after you change from the create mode to edit mode (push the save button and then the edit one) you will actually see all the assignment blocks. Maybe this helps. But if you still see the need of the sales area assginment block it can easily be made available via a customer UI enhancement.
Good luck and best regards,
Erika

Problem in customer creation for sales area

Hi all,
I could not create a customer for given Sales Org , DC and Division...
SAP Throwing error as "above mentioned sales area is not defined for the customer...
Karthick

Karthick V ,
When you create a Customer either in XD01 or VD01 Care should be taken while entering the "sales area" and the "customer" (Domestic customer or Export Customer or one time customer) again within this there is no. ranges which will be classified either Internal or External.
So care should be taken when you create a customer.
1. Check In IMG --> Enterprise structure -->Assignement --> SD --> Set up sales Area, whether you have created sales area (Check other assignements too. within Sales and Distribution). Generally check your Assignment sequence with reference to SD Process.
2. Check in OBD2 What Account groups have been used (you maintain different account groups this where you classify customer)
3. Check Assign no ranges to customer Account Groups
4. Check whether you have maintained common Distribution Channels and Common Divisions.
Regards
Sathya
Edited by: Sathya Pavan Yedavalli venkata on Apr 30, 2009 7:26 AM

Sales area check in quotation creation (VA21)

Hi
When we process quotations in our system, it does not check the sales area for the customer or the material. Hence we can create a quotation in a sales area for which a customer/material is not registered. No error message is given. This causes problems when creating the order with reference to the quotation because the sales area is copied across.
Is there any way we can get the quotation to check the sales area without putting custom code in to a user exit? In other words, is there some piece of config missing?
Thanks
Jon

Hi
The problem is not with the customer, it is with the material.
My customer is set up in sales area:
Sales org 0100, Dist chl 10, Division 10, as well as 0100/10/25.
The material in question is only created within division 10.
However, I can create the quotation using VA21 in sales area 0100/10/25. This sales area gives me the wrong division for my material. I always assumed that the sales area was checked against the customer and material before being allowed - for example if I process an order in VA01 (without reference to a quotation), and use the same customer and material combination in sales area 0100/10/25, SAP issues message V1370 ("Division 25 in the header deviates from division 10 in the item").
Jon

Create default sales area data on BP creation using BUPA_GENERAL_UPDATE

Dear all!
We have the following requirement: whenever a user creates an organization in WCUI, we need to create some default data for the BP in the background, such as relationships (employee responsible, etc) and sales area data.
I have created an implementation for BADI BUPA_GENERAL_UPDATE and use it to add the desired data. For relationships, this is working just great, but I´m having trouble with the adding of sales area data, since the system is not properly saving the data. I use the following code:
* Assign data for sales area
MOVE: 'O 50000632' TO ls_sales_area-sales_organization,
        '01'   TO ls_sales_area-distribution_channel,
        '01'   TO ls_sales_area-division.
ls_data-customer_group1 = '330'.
ls_data-customer_group2 = '003'.
ls_data-customer_group3 = '002'.
ls_data-customer_group4 = '006'.
ls_data-customer_group5 = '021'.
ls_data-pay_guar_proc   = '0001'.
CALL FUNCTION 'CRM_BUPA_FRG0010_ADD'
    EXPORTING
      iv_partner_guid = ls_changed_instances
      is_sales_area   = ls_sales_area
      is_data         = ls_data
      iv_x_save       = ' '
    IMPORTING
      et_return       = lt_return
      ev_error        = lv_error.
CALL FUNCTION 'CRM_BUPA_FRG0010_SAVE_COMMIT'.
Problem is, that with the call of
CALL FUNCTION 'CRM_BUPA_FRG0010_SAVE_COMMIT'.
I get a short dump of type "SYSTEM_ON_COMMIT_INTERRUPTED", but without the call, the sales area data is not saved. I tried the same code in a Z-report (not in a BADI) and it worked just fine.
Any ideas on how to commit the data so the sales areas will be saved? Helpful answers will be rewarded!!
Thank you all & Kind regards
Christoph

Hi Pratyasha!
Thanks for your reply. I figured, that by explicitly calling the commit FM, system commit procedures are interrupted.
The thing is, that just by calling the FM for adding the sales areas does not result in those sales areas acutally created. What I mean is, that after the BAdI is executed, no sales areas are maintained for the newly created customer. All the more funny, since this exact same procedure is working for creating relationships. See following code:
READ TABLE it_changed_instances INTO ls_changed_instances INDEX 1.
* Get BP-Number for sy-user
CALL FUNCTION 'CRM_ISA_IUSER_GET_BP_TO_ALIAS'
    EXPORTING
      username         = sy-uname
    IMPORTING
      business_partner = lv_user_partner.
* Map GUID to partner number
CALL FUNCTION 'BUPA_NUMBERS_GET'
    EXPORTING
      iv_partner_guid = ls_changed_instances
    IMPORTING
      ev_partner      = lv_partner
    TABLES
      et_return       = lt_return.
CLEAR lt_return.
* Create employee responsible
CALL FUNCTION 'BUPR_RELATIONSHIP_CREATE'
    EXPORTING
      iv_partner_1_guid = ls_changed_instances
      iv_partner_2      = lv_user_partner
      iv_relationship   = 'BUR011'
      iv_date_from      = sy-datlo
      iv_date_to        = '99991231'
      iv_testrun        = ' '
      iv_x_save         = ' '
      iv_xdfrel         = 'X'
    TABLES
      et_return         = lt_return.
which is in the same BAdI and acutally results in this relationship beeing created for my newly created customer. Works fine, just not for sales areas.
I´ll be grateful for any comments on that issue!
Kind regards
Christoph

Sales Area Creation

Similar Messages

Maybe you are looking for