Customer master extension

Hi,
how to extend a ustomer to another distribution channel.
As of noe
sales or: 7000
dist: 80
Division: 00
I need the customer master extend 81,82, 83 distribution channel.
how to do this
regards
s

Hi SP
Assuming that you have cerated a customer 1000 in the sales area 7000 /80 / 00.
Now as you need to extend the same customer 1000 to 81, 82 ,83 distribution channels also
create VD01 for the same customer 1000 and enter the sales area as 7000 / 81 / 00 and fill the feilds and save it
in the same way extend the customer 1000 to 7000 / 82 / 00 and 7000 / 83 / 00 sales areas
Now your customer 1000 is available in all 4 sales areas
7000 / 80 / 00 ,
7000 / 81 / 00
7000 / 82 / 00
7000 / 83 / 00
another solution is mantian common distribution channels
Go to VOR1 and enter distribution channel as 80 for all 81,82 and 83 distribution channels
Now when you create a customer in distribution channel 80 , he will be available in all other distribution channels also
Regards
Srinath

Similar Messages

Vendor master extensions by customer

Hi
Anybody here knows which are all the fields that can be enhanced by customer in Business partner screens?
Is it possible for a customer to add another Tab or is it strict to fields?
Is it possible to enhance all kind of BPs like Supplier/Bidder/Invoicing party, purchasing company etc.?
Any idea how a customer can enhance using new Weddynpro based UI?
-Jijesh Poduval

Hi
Which SRM version is using ?
Please See this thread for creating customer fields in BBPMAININT Transaction.
Look for the OSS Note for more details.
Note 675800 - Business partner enhancement SRM on maintenance screen
Vendor Master Extension in SRM
Supporting link ->
F4 for customer table fields
Re: Adding new fields in VEndor master data in EBP
Do let me know.
Regards
- Atul

Update Telephone Extension of Customer Master

Hi all,
I want to update Telephone Extension of the Customer through my program. Is there any function module which would update the Extension.
the case is I am getting an inbound idoc which does not process the Extension as the extension segment is added by me. Now how to map the Extension with the extension in the Customer Master i don't know.
Can u'll help me in this.
Thankx in Adv

in this there are a list of functional modules ..there are many functions used for various purposes...
http://www.sapgenie.com/abap/functions.htm
check it..
reward if helpful...

Customer master creation using IDOC

Hi friends,
           I am trying to create customer master into SAP using Idoc. Here pblm is some partner functions already defaulted i want to create some new entries in partner functions when i try to do it online its working fine when i try with idoc the defaulted partner functions are appears double times can any one has any idea whts happening.
E1KNVVM
    E1KNVPM (Master customer master partner roles)
        MSGFN : Function
        PARVW : Partner function
        KUNN2 : Customer number of business partner
        DEFPA : Default partner
        KNREF : Customer description of partner
        PARZA : Partner counter
the pblm is with these segment.
Thanks,
Naren.

Hi naren,
The segment E1KNVPM is standard one.Nothing can be done over it . U shold create new segments in we31 and add as
extension to the basic type and try..
Regards,
Nagaraj

Customer Master using Appended structure KNA1

Hi
We have to update few ZZ description fields in ZAKNA1, which are not part of user interface in XD01/02/03. The available options are such as LSMW, Batch input require code addition through user exit ZXF04U01/ EXIT_SAPMF02D_001.
I would like to use BAPI as we have a plan to use web services. Any idea how to extend the BAPI's such as BAPI_CUSTOMER_CHANGEFROMDATA1 or BAPI_CUSTOMER_CREATEFROMDATA1 using best practice? I donu2019t find any extension structures like other BAPIu2019s have. Without ExtensionIn and ExtensionOut parameters, a BAPI can not be enhanced correct?
The version we are using is ECC 5.0. Any ideas with customer master BAPI will be greatly appreciated.
Bala

Hi Bala,
Just some general comments without having looked at your specific problem. Since you're on ECC 5.0 you cannot use the new [Enhancement Framework|http://help.sap.com/saphelp_nw2004s/helpdata/EN/94/9cdc40132a8531e10000000a1550b0/frameset.htm], which would make such changes more easy...
A rather awkward workaround for extending the BAPI's is sometimes to add append structures to an IMPORT parameter of the BAPI. However, this is a rather dangerous and limited approach, because you might get into trouble depending on where the structures are used (i.e. if you add a field, it might cause harm in other programs that use the structure) and you also have to study the source code to see if you even could utilize those additional fields.
A pretty generic option in lieu of other approaches is to generate a custom wrapper function module around the standard BAPI. Within your custom BAPI you can add the missing fields as parameters, call the standard BAPI and then do the additional updates. The big advantage of such a solution is that
<ol>
<li>Your change/additional logic is obvious (not hidden in a customer exit or BAdI, which are often harder to find when troubleshooting or changing functionality)</li>
<li>Any changes to the standard BAPI will automatically also take effect in your custom BAPI (since you didn't copy the original one); this excludes of course interface changes, but here you anyhow would have to do something...</li>
</ol>
Should you have custom fields that are already exposed on the customer maintenance screens via enhancements, then you might want to consider using the wrapper approach, but simply export the additional data to memory, then call the standard BAPI and within the customer/user exits handling the additional fields fill them via an import from memory.
Cheers, harald

Customer Master - ADRNR field details.

Hi SDiens,
This is regarding Customer Master data.
Use T-code "SE16" then enter Table Name "KNA1" to see values for any particular Master record for eg. 1000.
In this you will find some Values in field "ADRNR, MCOD1, MCOD2". whereas if you open the same record with "XD02" you cannot see this values.
Even I am not entering this vause while creating records using "XD01". Can someone explain where can I see this Values.
Matter urgent.
Helpful answers will be rewarded.
Cheers
RC

Hi,
I looked in to this issue and got this information sto you please go through ADRNR number is the number provided internally by the system.and the remaining 2 fields MCOD1, MCOD2 are there in General data tab.
Address number
Internal key for identifying a Business Address Services address.
For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.
Business Address Services
I. General
You can manage addresses conveniently using a standard function module interface with Business Address Services. There are interfaces for maintenance with or without dialog and an address maintenance transaction.
Address attributes
An address in Business Address Services is a complex attribute of a primary object which saves only the reference to the address key. (In certain constellations, controlled redundancy is possible).
The address management distinguishes between addresses on the basis of time dependency and international formats.
The database structures allow for the date-dependency of addresses, but all function modules currently use date-independent addresses (the default validity range is 1.1.00001 - 31.12.9999).
Address types
Addresses are distinguished according to the application context in which they are used:
"Normal" addresses (Address type 1): This type of address can either be associated with an application object or be on its own.
Typical examples are the addresses of organizational units (for example, company code, plant), delivery address, functional location, and so on.
Such an address is identified in the DB by a 10-digit address number.
Examples: company code 0001 has address 4711
 customer MIKE has address 5678
Private addresses of persons (Address type 2): These are addresses which are assigned to exactly one natural person, with extended attributes compared to the normal addresses (title, part of name, etc.) for the person. The person with the address-relevant attributes is an independent object, which is maintained in Business Address Sercices.
Personal addresses are assigned to exactly one person, and can not be referred to by other application objects. The complete address object (person with address) can have several uses.
For identification, a 10-digit number for the person and a 10-digit number for the address are required.
A person (identified by the 10-character address) can have several addresses.
Example: business partner CHARLY is a natural person and has two addresses:
a) the first address is identified by person number 1234 and address number 3333.
b) the second address is identified by person number 1234 and address number 3357.
Addresses of persons in companies (Address type 3): These are addresses which contain the properties of a person in a company, with attributes such as Department, room number, extension.
Any normal address (address type 1), but not a private address, can be the company address.
The address of a person in a company is identified, like a private address by a 10-digit number each for the person and for the address.
Example: business partner CHARLY (see above) is contact person at business partner SAP_AG with company address 4444; CHARLY's contact person address is identified by person number 1234 (see above) and address number 4444.
These three address objects constitute an abstract data structure. The function group SZA0 contains function modules for accessing these address types. There are function modules for maintenance (create, change and delete), and to read and to search for each address type. There are also function modules to maintain and read all communication types which are supported by R/3, for each address type.
Function modules for private addresses begin with the prefix 'ADDR_PERSONAL_', those for addresses of a person in a company begin with 'ADDR_PERS_COMP'. Other function modules which begin with 'ADDR_' are for normal address maintenance, or in some cases, function group management.
The function modules manage the data structure using a maintenance interface. The underlying tables must not be accessed directly. This could lead to inconsistencies in data structures which contain fields from several tables.
Address maintenance
Addresses should be maintained as far as possible using standard dialogs which are available in other function groups.
Popup, subscreen and full screen dialog techniques are used.
The parameter transaction SADR can also be used for maintaining normal addresses which do not depend on an application object. These addresses cannot be distributed by ALE.
For more information, see the SZA1, SZA5 and SZA7 function group documentation.
For information about address validation see the documentation of function group SZAR.
If addresses are to be maintained without dialog, or if a user maintenance dialog is necessary for special requirements, addresses can also be maintained directly using the function modules of the function group SZA0. The standard dialogs of the function groups SZA1, SZA5 and SZA7 are also implemented with them.
Conversion of existing SADR/SADRP addresses
Most old addresses will be converted for the new central address management (Business Address Services) for Release 4.0.
From Release 4.5, all SD document addresses (previously SADR), customer addresses (previously only KNA1), supplier addresses (previously only LFA1), business and private addresses of (customer) contact persons (previously SADR) and bank addresses (previously SADR) will also be in Business Address Services (central address management).
Release notes Central address management for 4.0A and Central address management in Release 4.5 contain detailed information.
II. Maintenance without dialog (function group SZA0)
The contents of the function group can be classified as follows: management modules, which either apply to the function group as a whole or ensure correct database storage, address object maintenance (create, change, delete) modules, and address object communications address processing, for example, telephone, fax, or mail addresses.
Organization
Local memory:
Save
ADDR_MEMORY_SAVE: Saves the local memory contents in the database. All address data changes made since the first call of any function module in the function group are then permanent. Numbers must have been assigned to all addresses and persons before storing.
Delete
ADDR_MEMORY_CLEAR: Deletes the local memory contents. All address data changes made since the first call of any function module, or the last local memory save, are discarded. This module should be called after extensive read operations or when returning to the application.
Number assignment:
When assigning numbers to addresses or persons, their (first) use must be specified.
ADDR_NUMBER_GET
Assigns an address number, i.e. converts a temporary address number (address handle) into a permanent address number which is saved in the database key.
ADDR_PERSON_NUMBER_GET
Assigns a person number, i.e. converts a temporary person number (person handle) into a permanent person number which is saved in the database key.
Where used:
A permanent address or person number must have been assigned before a (further) use can be entered.
ADDR_REFERENCE_INSERT
Inserts a new use in an existing address.
ADDR_REFERENCE_DELETE
Deletes a use of an existing address.
ADDR_PERSON_REFERENCE_INSERT
Enters another use for an existing person.
ADDR_PERSON_REFERENCE_DELETE
Deletes a use for an existing person.
Applications are also deleted by the normal delete operations when the application passed to the delete modules is not the only one, or most recent one.
Address object methods
Read:
Read address objects
<Address object>_GET: Reads a (fully qualified) address. All versions of this address are read into local memory, and are subsequently accessible without database access.
ADDR_PERSONAL_GET_ALL: Reads all private addresses for a person. All versions of this person's private address are read into local memory, and are subsequently accessible without database access.
Read address object block
<Address object>_GET_ARRAY: Reads several (fully qualified) addresses. The database and the local memory are read. All address versions read are subsequently in local memory and can be accessed without database access.
Insert:
<Address object>_INSERT
Inserts an address.
<Address object>_VERSION_INSERT
Inserts a version of an address.
ADDR_PERSONAL_COMPLETE_INSERT
Inserts a private address with full specification of personal and address data, in contrast to ADDR_PERSONAL_INSERT, where the person data already exist.
ADDR_PERS_COMP_ASSIGN
Assigns a company address to an existing person, in contrast to ADDR_PERS_COMP_INSERT, where the person is also newly entered.
Change:
<Address object>_UPDATE
Changes an address version. (In particular the standard version, "the" address, is changed.)
Delete:
<Address object>_DELETE
Deletes an address. All existing address versions are deleted.
<Address object>_VERSION_DELETE
Deletes one version of an address.
Search:
<Address object>_SEARCH
Searches for addresses, which can be partially qualified (e.g. by attribute value specification). Only the database contents are searched (the local memory should be saved first, under certain circumstances).
Communication addresses
Read:
<Address object>_COMM_GET
Reads the communication addresses of an address object for a particular communication type. All communications addresses of the specified communication type, for the specified address object are read into local memory, from where they can subsequently accessed without database access.
Maintain:
<Address object>_COMM_MAINTAIN
Maintains the communications addresses of an address object for a particular communications type. Maintenance comprises: create, change and delete. All communications addresses thus maintained can be accessed in local memory without database access.
III. Maintenance with dialog
Function groups SZA1, SZA5, SZA6, SZA7 and the parameter transactions SADR and SADP
--> Overview in the SZA1, SZA5 and SZA7 function group documentation.
IV. Application examples
0. General
 - The function group does not need explicit initialization.
 - Address data changes are only written to the database after
 'ADDR_MEMORY_SAVE' has been called.
 - Before the 'ADDR_MEMORY_SAVE' call, all temporary
 address and person handles must be converted to external
 numbers.
1. Read access to normal address (address object 1)
Selection parameter for a normal address
 data: begin of selection
 include structure addr1_sel.
 data: end of selection.
Attributes of a normal address
 data: begin of result.
 include structure addr1_val.
 data: end of result.
Specify selection parameters
 clear selection. "no handle, default nation, today
 selection-addrnumber = t001-adrnr.
Read normal address
 call function 'ADDR_GET'
 exporting address_selection = selection
 importing address_value = result
 exceptions address_not_exist = 1
 parameter_error = 2
 version_not_exist = 3
 internal_error = 4.
 case sy-subrc.
 endcase.
Result output
 write: / result-name1,
 / result-street, result-house_num1,
 / result-post_code1, result-city1.
Delete local memory after end of processing
 call function 'ADDR_MEMORY_CLEAR'
 exceptions unsaved_data_exist = 1
 internal_error = 2.
 case sy-subrc.
 endcase.
2. Search for a normal address (address object 1)
Search parameters for a normal address
 data: begin of selection
 include structure addr1_find.
 data: end of selection.
Result table for a normal address search
 data: begin of result occurs 0.
 include structure addr1_val.
 data: end of result.
Address group table
 data: begin of dummy occurs 0.
 include structure adagroups.
 data: end of dummy.
Number of addresses found
 address_count like sy-tabix.
Specify search parameters
 clear selection.
 selection-name1 = 'SAP*'.
 selection-city1 = 'Walldorf'.
Search for normal address
 call function 'ADDR_SEARCH'
 exporting search_in_all_groups = 'X'
 search_for = selection
 importing addresses_found_count = address_count
 tables search_result = result
 address_groups = dummy
 exceptions parameter_error = 1
 internal_error = 2.
 case sy-subrc.
 endcase.
Result output
 loop at result.
 write: / result-name1,
 / result-street, result-house_num1,
 / result-post_code1, result-city1.
 endloop.
3. Bulk processing of normal addresses (address object 1)
Table of selection parameters for a normal address
 data: begin of selection occurs 20.
 include structure addr1_sel.
 data: end of selection.
Table of attributes for a normal address
 data: begin of result. occurs 20.
 include structure addr1_val.
 data: end of result.
Error table
 data: begin of errors occurs 0.
 include structure addr_error.
 data: end of errors.
Specify selection parameters
 clear selection. "no handle, default nation, today
 selection-addrnumber = t001-adrnr.
 append selection.
 clear selection.
 selection-addrnumber = vbpa-adrnr.
 append selection.
 ... enter further selections in table selection ...
Read normal address in blocks
 call function 'ADDR_GET_ARRAY'
 tables address_selection = selection
 address_value = result
 error_table = errors
 exceptions parameter_error = 1
 internal_error = 2.
 case sy-subrc.
 endcase.
Result output
 loop at result.
 write: / result-name1,
 / result-street, result-house_num1,
 / result-post_code1, result-city1.
 endloop.
Delete local memory after end of processing
 call function 'ADDR_MEMORY_CLEAR'
 exceptions unsaved_data_exist = 1
 internal_error = 2.
 case sy-subrc.
 endcase.
4. Create a normal address (address object 1)
Address number, address handle, address group, address data
 data: address_number like adrc-addrnumber.
 data: address_handle like szad_field-handle.
 data: address_group like addr_ref-addr_group value 'DEBI'.
 data: begin of address_data.
 include structure addr1_data.
 data: end of address_data.
Use details
 data: begin of usage.
 include structure addr_ref.
 data: end of usage.
Error table
 data: begin of errors occurs 0.
 include structure addr_error.
 data: end of errors.
Return codes
 data: rc_insert like szad_field-returncode.
 data: rc_number_get like inri-returncode.
 data: rc_memory_save like sy-subrc.
 data: lv_check_address like szad_field-flag.
Fill address record and determine temporary address identifier
 address_data = ...
 address_handle = ...
Deactivate address check if required
 lv_check_address =
Insert address in local memory
 call function 'ADDR_INSERT'
 exporting address_data = address_data
 address_group = address_group
 address_handle = address_handle
 check_address = lv_check_address
 importing address_data = address_data
 returncode = rc_insert
 tables error_table = errors
 exceptions address_exists = 1
 parameter_error = 2
 internal_error = 3.
 case sy-subrc.
 when 0.
 if rc_insert = 'E'.
 Analyze error_table and call special further processing
 because the address has errors and was not created.
 endif.
 endcase.
 ... process other application objects
 or modify Business Address Services
 local memory ...
 ... before saving potential application objects:
Declare final use to address management
 usage-appl_table = ...
 usage-appl_field = ...
 usage-appl_key = ...
 usage-addr_group = address_group.
Assign address number
 call function 'ADDR_NUMBER_GET'
 exporting address_handle = address_handle
 address_reference = usage
 importing address_number = address_number
 returncode_numberrange = rc_number_get
 exceptions address_handle_not_exist = 1
 internal_error = 2
 parameter_error = 3.
 case sy-subrc.
 endcase.
 ... immediately afterwards:
save local memory after processing
 call function 'ADDR_MEMORY_SAVE'
 exceptions address_number_missing = 1
 person_number_missing = 2
 internal_error = 3
 database_error = 4
 reference_missing = 5.
 case sy-subrc.
 endcase.
delete local memory
 call function 'ADDR_MEMORY_CLEAR'
 exceptions unsaved_data_exist = 1
 internal_error = 2.
 case sy-subrc.
 endcase.
V. Terms/Glossary
Address/Person group
Addresses and persons can be assigned to an address or person group. One address or person can be assigned to several groups (multiple assignment). This allows e.g. the same address to occur as customer and supplier address, and also allows searches to be limited to certain groups, instead of always searching all addresses.
Logical groups of addresses and persons can be formed.
The address groups required by applications are established by the application developer in consultation with the SAP Business Address Services. Customers can define their own groups in the customer name range for their own developments.
Address/Person handle
Address data are saved in the database and address and person numbers are assigned only when the application data are saved. Application programs must call the appropriate function modules. Business Address Services hold the data in internal tables in the local memory of the function group SZA0. Before saving after creation, addresses or persons are identified by an address or person handle, via which address objects can be accessed until the data are saved in the database.
The handle of a person, a normal address or a person in a company is determined by the application program.
The following procedure is recommended for both the address and person handles:
The first 10 places contain the name of the table in which the address or person is referred to. The next 10 places are used for the name of the field containing the reference, and the application data set key can be written in the remaining 120 places. This can be a temporary key, as the database key is only completed when saving in many application areas.
In this way the application developer can manage the addresses with the data which he or she is accessing anyway.
Ambiguities are avoided in complex transactions in which addresses for different applications are kept simultaneously in the same roll area for SZA0 (a serial number may not be sufficient as a handle).
Communication addresses
A communication addresse in the central address management is the identification number or address of a communication connection of one of the following communication types: telephone, fax, teletex, telex, SMTP, R/Mail, X.400 or RFC.
e.g. the complete telephone number (dialling code + telephone number) is the identification of the communication address of type telephone.
Address/Person number range
The address and person number range defines the valid external identifications (database key value range) for addresses or persons. For reasons of compatibility, the same number range applies as for 'old' SADR and SADRP addresses. Specifically, address and person numbers are drawn from the same number range. This simplifies the conversion of old SADRF and SADRP addresses.
Address versions
The (international) version of an address is an independent address object data set, in which a different display style of an address can be maintained in a code page (e.g. in Japan in Kanji, Katakana or Hiragana).
These are not independent addresses
The part of the address object which does not depend on the display style is always in the standard version.
In customizing (transaction SADV or under Cross-application components -> General application functions -> Address management -> Maintain address version display formats) you can set which other versions, in addition to the normal display style, are to be offered for maintenance.
Where-used list
In the where-used list, the application objects in which an address or a person are referred to is recorded. The where-used list is a technical support for the repeated use of addresses or persons in the three address types and therefore refers to the (sub)object address and person.
Immediately before calling the function module 'ADDR_MEMORY_SAVE', the function modules 'ADDR_NUMBER_GET', or 'ADDR_PERSON_NUMBER_GET' must be called once for every normal address and once for each person (for private addresses and addresses of a person in a company). The (permanent) use of the address or the person in the application must be specified. In exchange the calling program gets the assigned numbers of the addresses and persons for the references in the application data records.
Then (still before the 'ADDR_MEMORY_SAVE' call), other uses of addresss or persons can be specified via the function modules 'ADDR_REFERENCE_INSERT' or 'ADDR_PERSON_REFERENCE_INSERT' for multiple use.
This is always possible once the address or person number is assigned.
At the end of processing, the data must be saved in the database (as for all other address data) with the function module 'ADDR_MEMORY_SAVE'.
Thanks,
Sree.Manam
Edited by: manam narayana on Jun 18, 2008 9:00 AM

How to set custom master page for social/sites.aspx in sharepoint 2013

How to set custom master page for social/sites.aspx in sharepoint 2013.?
File path is
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\FEATURES\SocialDataStore\SocialDataStoreList\sites.aspx
Thanks in advance

Hi,
You could open the sites.aspx in Notepad or SharePoint designer, and set the master page to your own master page directly via editing:
<%@ Page language="C#" MasterPageFile="~masterurl/custom.master" Inherits="Microsoft.SharePoint.Portal.WebControls.FollowedContentWebPartPage,Microsoft.SharePoint.Portal,Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c"
%>
Regards,
Rebecca Tu
TechNet Community Support

SharePoint 2013 - Custom Master Page / Page Layout

Hi there,
- I've covert an HTML file using Design Manager >> Edit Master Pages to convert successfully. Now I've a custom master page.
- I changed my default master page to custom master page and it looks fine. But the problem is when I try to edit the page all the web parts (snippets) are appears at the bottom of custom master page.
- So I created new page layout
- After conversion successful.
- When I can click on new page this message shows up.
Sorry, something went wrong
An invalid or empty reference to a Cascading Style Sheet file was specified. Valid references must specify only a filename that ends with a ".css" extension
Thanks for help

Hi Tim,
As per my understanding try to do check the below things,
Try to restore the previous version of master, page layout and the home page and cross check the malfunctioned part by comparing both current and previous content
Check for special characters added in page layout ,page
Cross with the content type mapped with this new page layout
Check for custom solution is retracted from Farm
Optionally check for any updates gone in server
OR
Refere the below URL if the above wont works,
https://social.msdn.microsoft.com/Forums/en-US/5045369c-c330-4dc8-97fe-b9ad04830037/css-error-when-changing-the-master-page?forum=commserver2009
Vijaivel

Customer master extend

Hi,
Customer master extend division wise
I need to extend 1 customer to 3 divisions one time
T-code - xd01

Hi Rahul,
you can consider two solutions for this.
one going to VD01 / XD01 : add one more division to create sales area data to the customer. Since you have 3 divisions this process needs to be done 3 times.
In real time we develop LSMW / BDC programs to do mass upload of customer extensions.
second : You can config common division by taking one of divisions as reference to the remaining two. Maintain the customer for sales area with common divsion.
In real time you cannot simply do it as you want but take the business into consideration which way they want to go.
regards
sadhu kishore

Send customer master via ALE

Hi experts,
If sending customer master via ALE (message type) between R/3 systems, some fields cannot be sent, such as search term 2, street 2, etc.
Change basic type, or use BDC? Any solutions? Pls advise. Thx.

Hi ,
Goto we30 you will find Basic Type , Extension
When you will create an extension means you want to add some additional segments to the available basic type, in your case it is debmas01.
1. segments will be created in we31(segment create) and have to be released( Edit- set release).
2. After releasing segments go to we30 create Idoc extension ( staring with "Z" ) and add the custom segments(created in we31) to the extension under the segments as per your requirement.
There is no need to create another basic type, only extension is needed.Also add the extension which u created in partner profile.
Regard's
SHAIK.

Creation of partner functions for customer master with LSMW

Hello,
I try to create partner functions together with a customer via Batch Input in LSMW.
Object: 0050, method: 0000, program name: RFBIDE00, program type: B.
I use the structure BKNVP (Customer master partner functions) to create a new partner and set values for the fields KTONR and PARVW.
When I start the batch input the fields are filled in correctly in a new dynpro. After the confirmation of these values the dynpro changes back to the partner functions sscreen, but the value for KTONR isn'n being transferred. So I get an error message.
Is it only possible to update partner functions with that BI or what is going wrong ?
Thanks in advance and regards
Alex

Hi Alex,
Could you specify what error message you are getting?
Thanks!
Rudra

Creation of Customer master using CLASS( 'MAINTAIN_BAPI')..

I am creating customer master by class 'MAINTAIN_BAPI'. So all fields are sucessfully created except the field 'Remarks / Comments' on customer..Please suggest for the same as far as posiible..
<< Moderator message - Everyone's problem is important. But the answers in the forum are provided by volunteers. Please do not ask for help quickly. >>
Edited by: Rob Burbank on Jul 18, 2011 10:06 AM

Hi Yogesh,
Hi,
sorry to reply after the message closure.
Maybe you will read it.
SD_CUSTOMER_MAINTAIN_ALL is used in standard during the maintenance of a consumer using the standard customer master data transaction XD01 & XD02.
It is not intended to be used out of the transaction and in no case it should be used out of its original context. Due to the specificity of the function module, out of the original context we may face limitations and data inconsistencies.
For the maintenance of customers, there is NO BAPI and NO direct function module.
There are some functions modules like the one above where the name is looking nice. But these should not be used.
BAPI_CUSTOMER_CREATEFROMDATA1 is part of them. This one uses SD_CUSTOMER_MAINTAIN_ALL, so the above remark is still valid. Moreover, this BAPI is to be used only from process SAP Product Catalog. Out of it and due to its limitation, a lot of troubles are expected.
Sorry.
Below ECC 2005 (6.00), the only solution was batch input and DEBMAS idocs. See [note 384462|https://service.sap.com/sap/support/notes/384462]
Starting with ECC 2005 (6.00) and above: a synchronisation tool has been introduce. See class CMD_EI_API and VMD_EI_API
Hope this helps.
BR
Alain

Problem in creation of Customer Master

Hi gurus,
I am facing problem in creation of customer master.
I have created a account group zz01 copying from 0001.which has internal no. assignement for the customer.
Now i am trying to create a customer master, at partner functions level under sales area data... the system is asking for the no. for each partner functions.. when i tried to manually enter, the system is not taking any number nor it is letting me save the data.
Please help me out in acertaining, what could be the issue.
regards
Gupta
[email protected]

its due to the number ranges that is specified in the partner determination ... chech what is the number range assigned in the parner determination ,,, so once u check that u have to manually enter the number between that range only .. this should solve ur problem...
path to check the number range is as below :
spro-img-logistic generalbusiness partner-customers---define account groups and field selection ---
at this point click position button at the bottom and give ur account group .. select ur account group and click detail button .. now inside that u can see the specified number range .. dafault is 08 ( means u can specify between 400000 to 499999)..
and some times u may not have defined number range... check urs and create accordingly ... this should solve ur problem...
rewards if solved ..
thank you
madhan

Error in creation of customer master...

Dear SAP masters,
While creating customer master I am getting this error "Field KNVK-NAME1 does not exist in field status tables (TMOD*)".How can I resolve this?

Hi,
What are SAP Notes?
SAP Notes give you instructions on how to remove known errors from SAP Systems. They include a description of the symptoms, the cause of the error, and the SAP Release and Support Package level in which the error occurs. SAP Notes that contain correction instructions can be implemented using Note Assistant.
You need to log on to www.service.sap.com. This would ask for a S-User ID and Password. Check with your System Administrator for the same.
Once logged on, go to the link Help & Support --> Search for SAP Notes. Provide the SAP Note number. Read the note carefully and do the needful.
Contact your Basis person. He would be able to help you.
Regards,
Rajesh Kumar

Fields in customer master ?

hai.
how to make some fields in the customer master to appear in the grey mode and not in change mode to the user in the change customer master data screen (XD02)
kindly update ?
regards
sriram.

Hi
It is done at the account group level.
The path is as follows.
SPRO-FINANCICAL ACCOUNTINGAR and APCUSTOMER ACCOUNTSMASTERDATAPREPARATION FOR CREATING CMDDEFINE ACCOUNT GROUPS WITH SCREEN LAYOUT
Here in every screen, you can control the nature fo the fields of CMR
Rwd if it helps.

Customer master extension

Similar Messages

Maybe you are looking for