Attributes in Customer Master

Hi,
I'm trying to change the name of the attributes in the customer master to more descriptive names. Does anyone know how to go about this?
Thanks, Debbie

Use tcode CMOD:
goto->text enhacements->keywords->change
pls. reward if helpful
Roberto

Similar Messages

Update marketing attribute and customer master data via Survey Response

Hi,
I am creating a marketing survey. I have come to a point where I am able to get the reponses posted by the business partners.
Now I would like to update the BP's directly when they respond. The challenge here is I want to update both Marketing attribute and Customer master.
Is this possible with standard function modules. I am using version 4.0. Please let me know.
Regards,
Hemanth

Hello Hemanth,
Check my last response in the below thread, it could be a reason.
update marketing attributes in BP via survey
Thanks
Raja Pamireddy
CRM Marketing Forum Moderator.

Client independent Views in Material/Customer Master

Hi All,
What are all the client indepedent views in a Material Master?
and in a customer master?
thanks,
Viren.

Hi,
1.Transaction Code - MM01 / MM02:
2.Transaction Code - XD01 / XD02.
3.Transaction Code - VOV8:
for first - Master Data Settings
we need to do the appropriate settings in Material Master Data and Customer Master Data. Also we have the Customization
part, which we will see below. Now let us see the Master Data setting involved enabling the complete business process flow.
Second - Define Product Attributes in Material Master
menu path to define Product Attributes in Material Master:
Logistics - SD - Products - Material - Other Material - Create or Change:
OR Transaction Code - MM01 / MM02:
Here, you can enter the Material Number for which you need to assign the Product Attribute values. Go to Sales Org 2 view in
Material Master Record and in that select appropriate Product Attributes as per requirement. For Example, Select "Product
Attribute - 3" for materials with more than or equal to 1% of specific Chemical used (like Benzene related content) during
its production.
Third- Define Product Attributes in Customer Master
Follow the below menu path for defining the Product Attributes in Customer Master:
Logistics - SD - Business Partner - Customer - Create or Change:
Or Transaction Code - XD01 / XD02.
Edited by: RAJEEV SHARMA on Aug 19, 2010 5:01 PM

Customer master-general data-attribute-creation

Hi,
I would like to use the attribute 1 to 10 fields in customer master general data to fill up relavant to customer . i have seen some SCN postings regarding activation of those fields technically.
i want to create some data in the attribute same like customer group 1 , while creation of customer master , i shall select the drop down and save it
what is the menu path/transaction code for that please
Thanks and regards,
Pratheep

Hi
Check this menu path and also check below document in which Suhaib Bin Aziz has explained how to find SPRO path from front end screen.
How to find SPRO Path from any Particular Screen
Thank$

Customer Master Definable Attributes to Sales Order and Pricing

Hello,
I have a requirement to set a customer master flag using freely definable attributes. I am planning to use KNA1-KATR10 from the GENERAL Customer Master data. We do not want the flag to be sales area specific. The flag will be on the ship to customer.
I need to determine how to copy this flag into the sales order and then also to ensure that this field is available for evaluation in a pricing requirement routine.
How do i accomplish this? An alternative would be to use the Customer Grp fields , KNVV-KVGR1 but i am guessing the process would be similar.
Best Regards

If you want to save Katr10 to the order, you will have to
1. Append new fiield to VBAK within an append structure like zzvbak.
2. Retrieve Katr10 and move to VBAK in MV45afzz form userexit_move_field_to_vbak.
3. Append new field Katr10 to pricing communication structure komk in include komkaz.
4. If you retained Katr10 as field name then you are done since there is a move corresponding from vbak to komk, if not you need to move this to komk in MV45afzz form userexit_pricing_prepare_tkomk.
The field will now be populated and available in your pricing requirement routine. Hope this helps.
Matt

Simple Master Data Attribute Add Custom Infoobject

Hi I added one custom infoobject zcustplace to 0busentity master data infoobject as an Navigation attribute and then activating 0busentity but it is giving me error
like this "ORA-20000: Insufficient privileges
ORA-06512: at "SYS.DBMS_STATS", line 2150 ORA-06512: " Do I need to do any thing else to add this new nav attribute to obusentity master data attributes since this obusentity is already there in cube and ods.
Please help
Thanks
Soniya Kapoor

You may wish to get this OSS checked with DBA
Note 963760 - 'ORA-20000: Insufficient privileges' for creating statistics
Hope it Helps
Chetan
@CP..

Customer Master Data attributes are missing in BW when populated in R3?

Hi,
We have got a problem like - Customer Master Data attributes are missing in Business Warehouse when populated in R3.
<b>Eg.</b>
Account Number: 1081202 - No customer clasification. In BW it is not assigned.
Account Number: 2023902 - In BW region field is not assigned, In R3 it shows SA.
No customer clasification, in R3 it shows OP.
How do we check & resolve this problem.

Hi Venkata,
Its a master data.
How will the PSA come into picture.
Its directly loaded into the characteristic. no PSA is used in between.
We need to run manually the hierarchy/attribute change run?
Please give the steps for running it manually.
<b>Shabar Alibhai:</b> I dont have the sufficient R/3 authorisations for checking the data in r/3 side.
The problem needs to be identified with respect to BW side only.
Thanks & Regards

Impacts in COPA of changing material and customer master data

Dear experts,
In my company we are considering following scenario:
Currently mySAPerp 6.0 is implemented for all modules for the mother company.
We have developed a new global template where there are significant changes versus the existing system, especially in the SD processes. Material and customer master also change significantly in terms of content in the tables/fields and/or values in the fields.
The idea was to build the template from scratch in a new machine and roll-out all group affiliates, but now we are considering the possibility of making an evolutionary of the current system and try to stretch it to the processes defined in the global template.
The scenario we want to analyze is: Keeping same organizational structure in terms of Company code, CO area and Operating Concern in existing SAP client and make an evolutionary of the existing settings to the global template processes.
The doubts we are having are the following:
Changing material & customer master data: Impact in COPA
Option 1: Material master data and customer master data codes are maintained but content in the tables/fields is changed substantially, both in terms of logical content of specific fields and/or the values in the specific fields. We have following examples of changes.
Case 1: source field in material master changes logical content. E.g. Material master field MVGR1 is currently used for product series (design line) and the content changes to be the Market Segment. The product series will be moved to a classification field. At least 5 other fields are affected by this. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 2: the source field is not changed so that the logical content of the field remains but the values change, i.e. for the same concept there will be different codifications. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 3: Characteristics where currently the source material master field is a Z field and the derivation is via table look up and where the Z field changes to a classification field. How can you convert the existing COPA line items to ensure that attributes are aligned? Should new characteristics be created or just change the derivation logic of the characteristic?
Option 2: Material master data and customer data codes are re-created (codification of records is changed), meaning that new material and customer codes will exist and content in tables/fields is changed (as in option 1)
Case: material and customer codes are changed. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Iu2019ve never phased a similar scenario and I fear that maintaining operating concern while changing source master data and also SD flows (we have new billing types, item categories, sales doc. Types, order reasons) may lead to inconsistencies and problems in COPA.
I would like to ask you experts if you have come across a similar scenario and if from your experience, it is something feasible to do or there are many risks involved. What can be the impact of this scenario in existing Operating Concern for both option 1 and 2 and what would be the key activities to perform to adapt the existing operating concern. What will be the impact of the needed conversions on P&L reporting?
Sorry for the long story. I hope you can help me out.
Thanks and Regards,
Eric

Hi,
First i think you will need to test if it works for new COPA documents created via billing.
If it works fine then the issue is if you wish to apply these changes to the historical data already posted.
Normally there are transactions like KE4S where you can repost the billing document to COPA
However this may not be viable for bulk postings
You can perform realignment (KEND) but this only works at the PA segment level (table CE4XXXX)
regards
Waman

What is the difference of customer master data between CRM and ECC

Dear all,
We are helping customer to evaluate using CRM or ECC to manage there customer master data, focusing on the benefit of using CRM system.
Can any one help to compare the difference between these two system?
some tips in my mind are:
1. CRM has a friendly user interface for user to adjust the layout, hide/display favourite information according to actuall req.
2. In CRM, user can change the field/assignment block description easilly
3. in CRM7.0, user can add new customzing field easilly via AET
4. CRM has a good any analysis platform to provide pie chart analytic
5. CRM store more customer infor. than ECC, such as Marketing attribute, account classfication...anything else?
any other benefit to use CRM for customer master data? Pls help!!!
Thanks very much!!
BR,
Hedy

I would agree with most of the topics you mentioned. Just one remark to topic number 5. Business partner doesn't have more data than erp. It has some more marketing oriented data, but on other hand doesn't have all finincial and credit data that are relevant for erp financial transactions.
In our company we have the following scenario: all business partners are created in crm (because there the sales activities are started and because we don' clasify at the begining all partners as customers but as prospects. and of course it has nicer user interface). but when we are closing the deals (ordreds are transfered to erp), we fill some additional (financial) data of that partner on erp side and clasify partners as customers.
Regards.

How can I include Customer Hierarchy in Customer master IDoc -DEBMAS06 ?

Hi,
I am generating Customer master IDoc using basic message type DEBMAS06. But when I include customer hierarchy data while creating customer master, it is not included in any of the segments. The segment containing the data from KNVH is not included in standard.
How do I include this hierarchy data in the IDoc? If I create a segment, under which basic segment should it be included and how to update the data in the segment?
Can anybody help?
Points assured.
Best Regards,
Rajendra

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

Customer Master Text data label display in BEx query

Hi,
In my query output i have the customer number and its text displayed. The data comes from customer master infoobject.
But the label is displayed only for customer number.
But I need the label for text also needs to be displayed.
Kindly let me know is there any possibilities to display the label for the text.
Regards,
Indhu

Hi Induja ,
For 0CUSTOMER , name attribute is there so it will work fine, for others like 0MATERIAL, 0COMP_CODE etc. you can follow the steps which i have posted in above reply.
Use the same steps for 0Material, creation of Z- infoobject with reference char. of 0Material.....
Create one custom 'z' InfoObject lets say ZCUSTOMER with Reference Characteristic of 0CUSTOMER and add it to the data target, map it with same field for which 0CUSTOMER is mapped and load data into target (DSO, cube) or if you are reporting on multiprovider then assign it.
Because ZCUSTOMER is created with reference of 0CUSTOMER and mapped with the same source field , ZCUSTOMER will act as copy of 0CUSTOMER.
In query designer drag 0CUSTOMER and ZCUSTOMER. change display setting
0CUSTOMER display as Key only
ZCUSTOMER display as Text only.

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

Customer master details

hello guru's,
                my requirment is i need to upload Customer Master details using BAPI in LSMW. can anyone tell me the Business Object Type and Method name ..i know message type and idoc type for Customer Master bt i dont know how to search the Business Object type and Method...

Hi,
Object          0050
Method          0000
Program Name    RFBIDE00
As an alternative to using u2018Transaction Recordingu2019, you could also use a standard SAP object to update Customer Master Records. Business Object u20180050u2019 is already pre-defined in the system with standard Batch Input Interface Program u2018RFBIDE00u2019.
Create an Object CUST_OBJ within Project as LSMW_DEMO and Subproject as CUSTOMERS as shown in Figure 20.
Figure 20 LSMW Object with Standard SAP Object
Note! Only steps that are different from the recording method are listed here.
Step 1: Maintain Object attributes
You will be updating the customer master records with the help of Standard Batch Input; therefore, choose radio-button Standard Batch/Direct Input as shown in Figure 21. Enter Object u20180050u2019 for Customer Master records and default method u20180000u2019 and click on Save.
Figure 21 Standard Batch/Direct Input Object Attributes
Step 4: Maintain Structure Relations
Sales view of Customer Master is stored in table KNVV. Accordingly, you need to update structure BKNVV. However, in addition, the Standard Object u20180050u2019 also requires updates to BGR00, BKN00 and BKNA1 structures. (If you do not maintain Structure relations for mandatory entries, you might get a message such as u2018Target structure BKNA1 needs a relation to a source structureu2019.)
Even though you donu2019t want to update any fields in these structures, you need to create a relationship with source structures. In all, you need to create relationship for four target structures.
Create relationship between source structures XD02S with these target structures with icon u2018Create Relationshipu2019 .
Keep Cursor on these four target structures and click on icon u2018Create Relationu2019 and structure relations are maintained as shown in Figure 22.
Figure 22 Structure Relation
Step 5: Maintain field mapping and conversion rules
-- Keep your cursor on u2018TCODEu2019 field and click on u2018Insert Ruleu2019 icon
Figure 23 LSMW Conversion Rules
Choose radio button u2018Constantu2019 (Figure 23) to enter value u2018XD02u2019 transaction code.
-- Keep your cursor on field u2018KUNNRu2019 and click on u2018Assign source fieldu2019 icon
Choose source field u2018Customeru2019 from source structure u2018XD02Su2019. (See Figure 24.)
Figure 24 Assign Source fields
-- Similarly, choose source fields for Sales Organization, Distribution Channel, and Division. (See Figure 25.)
Figure 25 Field Mapping and Conversion Rules
-- Scroll down to structure BKNVV fields and assign source fields to three fields Sales Office, Sales Group, and Customer Group (Figure 26).
Figure 26 Field Mapping and Conversion Rules
Save and go back to main screen.
Step 12: Display Converted data
When you convert data, LSMW automatically converts into the appropriate structure layouts, as required by Standard program (RFBIDE00). (See Figure 27).
Figure 27 Converted data into multiple structures
Note that if you had only one record in source file, the converted file has four records.
Earlier, creating this input file, so that the standard interface program can read it, was a big nightmare, the primary reason being that it could have multiple record layouts. Even for a simple conversion with one input record, you would have to create this complex file with many record layouts. The advantage of LSMW is that it prepares these multi-layout files automatically.
Step 13: Create batch input session
Once source data is converted in internal format, you can create a BDC session to process the updates (Figures 28 and 29).
Figure 28 Create BDC Session
Figure 29 BDC Session u2018CUST_OBJu2019 created.

Customer master (XD02) with LSMW

Hi All,
I am trying to update customer master (XD02) with LSMW. But i the First step i.e. Maintain Object Atrributes... when I clic batch input recording & try to give a recording name in th second line... it throws an error saying "Enter a vali Value"... It does not accept a recording name & does not allo me to click Recording : Overview button .
Has this error to do anything with the settings??... The sandbo in which I am working has the component version "SAP R/ Enterprise"(found out by System --> Status) ... Please Help

hI,
You will have to create recording first & then select from drop down box of "Batch Input".
To create recording pls follow this:
Go TO T code : LSMW
Create Project, Subproject & objects.
In Maintain Attributes - press F8
In menu bar
Goto---> recording overview
Now you can create your recorindg which wil be avaliable for selection.
rgds,

Project Code Maintenance on Customer Master level

HI Experts,
I have some requests from users if they can maintain their Project Code Value in the Customer Master (Company Code). Do we have a field for this or I should be adding a custom field?
I appreciate your inputs. Thanks!

Hi,
You can use the Attributes field in the customer master. These can be maintained from XD02-->General Data Button --> Extras (Menu) --> Additional Data --> Attributes.
To maintain entries in the field Goto SPRO--> IMG --> Logistic General --> Business Partner --> Customers --> Control --> Define Attributes.
Regards,
Deepak

Attributes in Customer Master

Similar Messages

Maybe you are looking for