Customer Master -Name 1 field

Dear All,
The user called in stating that he is not able to view the complete name in Cust Master Data-NAME FIELD (under Title).Now we are using third paty tool to create and upload data made from lotus notes.Any help appreciated.
Regards
Amay

hi,
the name field occupies 40 alphanumeric in length if that is not sufficient you can use the name2,3 & 4 which occupies the same length.
or
there is some other method called field exit, sit with your abaper and give him some instructions lke how much length it has to get extended...etc.
he will do it for your business.
regards,
balajia

Similar Messages

Customer master recon account field is disabled

Hello folks,
The recon account field in the customer master field is disabled, wouldn't allow me to enter the recon account.
Don't know how it happened. I was able to do that before, I have few customers with valid recon account. Even when I try to copy those customers, it wouldn't copy the recon account. Any ideas, greatly appreciated.
Thanks,
Tony.

Dear,
There could be two reasons.
1. Use transaction OBD2 and check the field of your customer group whether recon account field is not surpressed or display.
2. Use transaction OB20 and check the field status per activity.
Regards,
Chintan Joshi

Creating Customer Master records(ship to accounts)

Hi Gurus,
i am very munch new to abap plz help me to solve my issue..
my req. is to create a load program to create ship to accounts,information is being provided in an EXCEL spreadsheet which will include the following fields. Also listed below contains information that have default values. i have to use XD01.
Customer Create Initial Screen
Field Description     Excel Spreadsheet Column     Default Value
Account Group                                                      0002
Customer (Ship To)     C
Sales Organization                                                       BMX
Distribution Channel                                                       60
Division                                                                        00
Address Tab
Field Description     Spreadsheet Column     Default Value
Name                             D
Name 2                             E
Search Term 1              F
Street 2                            G
Street 3                            H
Street                              I
Postal                            J
City                                    K
Country                             L
Region                            M
Transportation Zone     N
Control Data Tab
Field Description     Spreadsheet Column     Default Value
Industry                                   O
Shipping Tab
Field Description     Spreadsheet Column     Default Value
Order Combination                                          Leave blank
Shipping Conditions                                           Should be 01
Plant                                     P
Billing Document Tab
Field Description     Spreadsheet Column     Default Value
Rebates                                                            Should be marked
Price Determination                                            Should be marked
Incoterms                                                                    PPD
Terms Of Payment             Q
Tax Classification           1
THANKS AND REGARDS,
SAP8752ABAP.

Hi,
you can check on the LSMW being used for customer master creation, the fields what you had mentioned are normal fields and will be available in the standard batch / direct input under the object 0050 & program name RFBIDE00.
just map the excel fields with the fields indicated in the LSMW.
for step by step procedure on using LSMW, check below
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
in this example on page 3 Batch input recording is used, you can use Standard Batch / direct input with the parameters i had given earlier.
Thanks & Regards
Ilango

Mass change in Vendor & Customer Master

Hi All,
Is there any Mass change available in Vendor & Customer Master?
Thanks
Pankaj Garg

Hi,
Enter t-code MASS.
Enter object as per below mention detail
KNA1: -Customers
LFA1: - Vendors
Then click on execute button, You can see the list of fields for vendor & customer master.
Select field as per your requirement and click on execute button then change data as per your requirement.
Regards,
Mahesh Wagh

Customer Master zone Customer Transportation Zone Is Greyed

Dear Friends
I want to make customer master transportation zone field to be optional entry.I did necessary changes in OBD2,OB20 and OVT0.After making optional entry in all area it is been with grey mode that is not editable.But if I change as required entry then it is changed as required field that is editable mode.But I need only optional entry.Can any one help me on this...
Regards
Ganesh
Posting in all CAPs or BOLD, represents shouting, kindly avoid this in your future post.
Message was edited by Moderator: Jyoti Prakash

I did necessary changes in OBD2,OB20 and OVT0
In OB20, which one you have selected and through which tcode you were checking?
G. Lakshmipathi

Edit Customer master

Hi All,
I have a requirment where I need to Change/Edit the data from Customer Master for following fields.
General Data -> Address -> Region
General Data -> Control Data -> County code
Company code Data -> Account management -> Recon. account
Company code Data -> Payment Transactions -> Payment history period
Sales Area Data -> Sales-> Sales Group
Sales Area Data -> Billing Documents Data -> Taxes(table)
Sales Area Data -> Partner Functions -> Partner Function(table).
I don't want to do a BDC. Is there any BAPI/BAPIs to achieve this or any other way.
I dont think BAPI_CUSTOMER_CHANGEFROMDATA1 can do all of the above changes.
Regards,
DNP

Hi,
I was able to achieve through 'SD_CUSTOMER_MAINTAIN_ALL'
Regards,
DNP

How to Flag Customers in Customer Master (in SD)

Hi,
I've read a few earlier posts regarding customer master and since I could not find an answer for my query I am posting it here.
I have a question regarding the customer master in SD: Is there a way to Flag Customers for reporting purposes in Customer Master for SAP SD.
Is there some standard funtionality in SAP to do so ?
We have a few customers that belog to the US governmnet and due to government regulations if we do certain amount of busniess with them or gov agencies or government contractors we need to send the gov a formal report.
So for this reason we need to flag customers so we can run reports and see how much is being done.
I wanted to know if there are some other users/ companies that are doing this and if so how are they handlling such situations?
I would appreciate if some one could help me with this as this is knid of an urgent requirement.
Thanks in advance.
Neha

Hi,
SAP has given some standard report based on those reports you can see the sales values for customer,material,based on sales orders and billing document etc.. like this.
but if you want to see theese reports frist you have to configure this (LIS Logistics Information System)
Path:SPRO>Logistics-General>Logistics information system>Logistics data warehouse>Updating>Updating control>Settings:Sales, here you have to set in statistic group,update group settings.
Againe here defined statistic groups are assigned in customer master fro the field statistic group in sales area data>sales tab.
Likewise you can also activate based on material and sales documents in above specified path.
Thank you,

Customer Master - Customer Category

Hi All,
Customer Master having a field called Customer Category, Presently its having 2 records, I would like to add a new record in that. As i checked lookup forms, there is no category, but when i check the below query its showing 2 records like (CUSTOMER,PROSPECT).
SELECT * FROM FND_LOOKUP_VALUES_VL WHERE LOOKUP_TYPE='CUSTOMER_CATEGORY'
If there is anyway to add a new customer category please tell me. It will be more useful to solve this issue.
Version Used: R12.1.1
Edited by: user568657 on Jun 10, 2011 5:50 AM

Hello.
You can navigate to /Setup/System/Quick Codes/Receivables, query for CUSTOMER_CATEGORY type and create a new customer category.
Octavio.

Dunning - clearing the customer master data?

Customer XYZ has been dunned. Customer master updated with dunning level = 1 and last date dunned. Once customer pays invoice, is this automatically cleared by the system, or does user have to do this manually (clearing of dunning level and last date dunned in customer master)?

The field KNB5-MAHNS (dunning level in the customer/vendor master
record) is not the actual dunning status of the customer/vendor,
but the highest dunning level customer/vendor got the last time
customer/vendor was dunned.
This is mentioned in the F1 help of this field.
If customer pays all the repayments etc., then customer will not be
dunned, but that customer will forever keep his dunning level, even if
there are no more open items.
You can change the KNB5-MAHNS field manually in the master record in
fk02/fd02.
Also, please review and apply note 6591 if you would like to reset the
dunning data.
Hope that helps:
Jon

Retrieving Dunning Clerk's name from Customer master data

Hi all,
I have to retrieve the dunning clerk's name in report ZRSD0001 (Customer Master Data Report).
There are standard methods to call the subroutine to retrieve the texts for some field like the bank statement text:
PERFORM TEXTFIELD_CALL(RSAQEXCE) USING KNB1 'KNB1' 'XAUSZ' TEXT_KNB1_XAUSZ.
This works perfectly. But it fails when I use the same method to retrieve the dunning clerk's name:
PERFORM TEXTFIELD_CALL(RSAQEXCE) USING KNB5 'KNB5' 'BUSAB' TEXT_KNB5_BUSAB.
So any other standard subroutine that I can use instead of using a sql statement myself ?
Thanks.

Hi,
Why do you want to use a standard routine for this?? If you know the customer number(KUNNR), Company Code(BUKRS) and Dunning Area(MABER) You can get Dunning clerk(BUSAB) from KNB5 and using this BUSAB and BUKRS you can go to table T001S to get the SNAME which is Dunning Clerk's name.
Thanks,
Kavitha

Why can't I find the field remark when I use LSMW to create customer master

I want to create customer master data with LSMW.
Object               0050   客户主记录
Method               0000
Program Name         RFBIDE00
Program Type         B   Batch Input
but I can't find the field 'Comments' which is in view general data -> address.
pls help me to find it.
tks!

Hi,
This is quiet simple.
See when you enter your Tcode in LSMW & start recording, on the first screen where you enter the customer details to create, you see a tick below "Use central adress management"
Just tick this & record you will get comment in your recording
Hope this helps you
Regards,
Dhananjay

Report needed: Customer master TAXKD field changes

We are looking to track changes made to TAXKD (tax code) in customer master.   Is there any report we could generate weekly that would detail changes made to the field.
Also, we'd like what change was made. (i.e. customer number, date, field changed from 0 to 2)
Thanks,
Michelle

Hi Michelle,,
Those changes will be recorded in the CDHDR and CDPOS tables with your field name based on the dates..
and also with the Old value and the New value
from the CDPOS
pass
OBJECTCLAS = 'DEBI'.
OBJECTID      = Your document number "optional
TABNAME    = 'KNV1.
FNAME       =   'TAXKD'.
if you pass these thins you will get the in the fileds VALUE_NEW and VALUE_OLD
hope these informatino useful to you.
Thanks
Edited by: Prasanth on Apr 13, 2009 7:40 PM

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 include a new field for checking duplicate customer master

Dear All
we have activated the standard procedure to check duplicate customer master data. This is a standard procedure as below :-
Procedure:
Run SM30, key in Table V_T100C, select Display or Maintain, set App area F2. Here you can change current settings.
Check the transaction OBMSG for application area F2, where these messages are maintained and at this place you can convert the message from warning to error.e user needs one more field to be added to this check.
It is working perfectly fine but it only compares two fields for duplicates in the customer master i.e the customer city and name.
Is there a way to include a new field in this procedure ? For example we also want the system to check duplicate entries for field name " street 5" and give a warning /error message incase if there is another entry already existing on the master data.
regards,

Hi
Use the enhancement SAPMF02D to check these values.
Regards
Eduardo

Customer Master Fields for LSMW (Only FI View)

Hi,
We are implementing SAP FICO at one of our clients' site. They are not implementing SD. Can anyone tell me what are the minimum required fields for creating a customer master? Even if you give the table name whwere I could get this info, thats great.
Thanks and Regards
Madhu Vutukuri

Hi Madhu,
In General Required fields for Customer master creation are :
Customer name
Address
Recon account
Some other important fields
Sort key
Terms of payment
Payment methods
Have a look at Tables KNA1(General data) & KNB1(Co.code data).
Having said the above, required fields for customer master will vary depending on your customer account group field status.
Let me know if you require any further info
Thanks
Kalyan

Customer Master -Name 1 field

Similar Messages

Maybe you are looking for