Plant on Customer Master

Hi All,
I need to replicate the plant number from the ECC Customer Master onto the CRM Customer Master.
I have referred to note 493947. I executed the CUSTOMER_MAIN adapter object after this note. The SMW01 shows no error, but the relationship as "Vendor" has not got created.
Please advice.
Thanks,
Rinkal

Hello Rinkal,
Object DNL_PLANT generally brings in the plant data to CRM and maps it as BP.
Is this what you are looking for?
Thanks and Best Regards,
Shanthala Kudva.

Similar Messages

Plant specific customer master number range

HI Friends,
Is their is any option available in SAP for assigning plant specific number range to customer master record ?
Regards,
Chetan.

Dear Chentan,
No you cannot maintain Plant specific number ranges. WHat you can do is create seperate Customer account groups (SH, SP, BP, PY) for each Plant & assign unique number rages to eacg group.
But the above is recomended only if you have couple of plants say 2 or 3 plants. If you have multiple plants then it would to confusions. Also the standard system would not give Customer's outstanding Plant-wise & it can only give company code wise.
Thus having seperate Customer's number range for each plant does not seems to be much beneficial...
Hope the above helps.. .
Reward if useful...
Thanks,
Jignesh Mehta
Mumbai
98700 10230

How to download Delivering Plant of R/3 Customer Master in CRM BP

Hi,
We have successfully downloaded the Plants from ECC to CRM using the object DNL_PLANT which has successfully created BP's for PLants in CRM with BP Role=Plant and have updated the mapping in table CRMM_LOCMAP.
Now I want that the Delivering Plant mantained in ECC Customer Master Data (XD02 -> Sales Area Data -> Shipping Tab -> Delivering Plant Field) to be updated in the CRM Business Partners as BP Relationship.
The BP(Customer BP) should be updated as a BP Relationship "ZPLANT - Has Plant" with BP(BP of the Plant in CRM). This is not happening.
Can you please tell me the Steps to be performed in both CRM and ECC side to bring the ECC Delivering PLant as Relationship in CRM ?
Is the Delivering Plant change in ECC Customer Master Data does not gets captured in the BUPA_MAIN BDoc ?
When we change the Delivering Plant in ECC Customer Master Data, a BUPA_MAIN Bdoc gets triggered but when we look into the Bdoc we can not find the changed information of the Delivering Plant. I am not usre if this behaviour is right or not.
There is an OSS Note - 493947 which is quite old and talks about creating a Customer each for all the Plants in ECC and creating a Partner Function for Plant in the Customer Master Data. I am not sure if this process is still to be followed Or SAP has given some stadard settings to bring ECC Delivering Plant mantained in Customer Master to CRM.

To my knowledge oss note 493947 is still relevant
Edited by: Anders Brock-Faber on Apr 6, 2009 1:06 PM

Payment terms based on specific dist.channel, division and Plant but not from customer master.

Dear All
I have a requirement,
Generally payments terms from customer master will flow to sales order. but here my requirement is to get a different payment terms based on specific distribution channel, division, customer and plant those are there in sales order but not from customer master. is there any user exit or functional module to fulfill this requirement, or any other suggestion appreciated.
Thanks,
Reddy

This Problem you can solve without user exit too.
The Customer master data itself can solve the problem.
You can maitain diffrent Payment Term as per the sales area (Dist.Ch+Div+S.org) of customer master.
and each sales are wise u can change the plant also.
You just need to set your logic with the combination of sales are and plant. And need to assign which payment term should determine to sales order.
If you are rasing sales order with X sales area relavent to that payment term will trigger.
Hope above logic will work, otherwise you can go with user exit.

Customer master can only be associated with a single Plant Code

>>Customer master can only be associated with a single Plant Code. True or False
>>Plants are then extended to Company Codes, and can be extended to multiple Company Codes. T/F
>>SKUs are then extended to Plants. T/F
Please confirm..
Thanks

>>Customer master can only be associated with a single Plant Code. True or False - One customer can be assigned to multiple Sales areas and customer is not assigned to plant, A customer can buy products from a plant if plant is assigned to Sales org/Dis channel
>>Plants are then extended to Company Codes, and can be extended to multiple Company Codes. T/F - True
>>SKUs are then extended to Plants. T/F - True
Thank you
Kris

Report to fetch the text information from customer master sales data

Dear Experts,
We have come up with a requirement where the business want a report/list of the customers for whom a particular text is not maintained in customer master -sales data.
There are many Z text id are configured and are maintained in Sales data- extras- text. In addition, business also need some key fields from the customer master such as name, city, delv plant, payment terms, sales off, sales grp etc.
I could not get any standard table where the text is maintained with the customer numbers. Table STXH can give the customer numbers for a particular text id type but what is maintained against the given text id is not fetched from the table.
So we need the valuable inputs to realize the requirement.
As an proposal, we are aiming to develop custom Z report with the FM READ_TEXT to get the text information with the customer no ( object type KNVV and text id ). But for the additional information, what should be the actual logic for fetching the data. say if this FM is used, what should be the sequence of the logic and ideal selection parameters.
In addition, we aim to use BAPI BAPI_CUSTOMER_GETDETAIL2 to fetch some of the customer ifnormation but many fields are not found in this . can we use some other bapi which can provide the complete general/sales data of customer ( delv plant, sales off, sales grp, custo grp, incoterms, payment terms etc)
Kindly suggest accordingly.
Many thanks in advance.

Hi Dharmendra Kumar,
I guess the best would be to check in ABAP General forum on the READ_TEXT sequence/ logic etc..
For customer details, the available BAPIs are:
BAPI_CUSTOMER_GETDETAIL
BAPI_CUSTOMER_GETDETAIL1
BAPI_CUSTOMER_GETDETAIL2
However, you might have to check classes in SE24 to find any existing classes and its method yo give you all the information of a customer. Also check this thread: [BAPI for customer details like in IDoc DEBMAS;
Regards,
Raghu.

Query in customer master data upload ....?

Hi Guru's,
I am uploading the customer master data from presentaion server to customer tables using functional module SD_CUSTOMER_MAINTAIN_ALL.
while check the Function module separatly and it working properley and i am able to ctere customer...
and i am using the same function module in the program i am unable to upload ..could please check and let me know where i am doing mistake in the below program logis..and values also moving properly before calling function module..while calling the functinal module the controle comming out of the loop and program went to dump i am able to see the message in dump as like this(it may helpfull for resolve):
Name of function module...............: "SD_CUSTOMER_MAINTAIN_ALL"
Name of formal parameter..............: "O_KNA1"
Technical type of actual parameter....: "C"
Technical length of actual parameter..: 20 bytes
Technical type of formal parameter....: "u"
Technical length of formal parameter..: 3634 bytes
Name of formal parameter at caller....: "O_KNA1"
*& Report ZERP_CUSTOMER_CREATE_UPLOAD
REPORT zerp_customer_create_upload.
PARAMETERS:p_files TYPE string.
*DATA :xkunnr(10) LIKE kna1-kunnr. "unique KUNNR
DATA: gs_i_kna1 TYPE kna1,
 gs_i_knb1 TYPE knb1,
 gs_i_knvv TYPE knvv,
 gs_return TYPE bapireturn1,
 gs_i_bapiaddr1 TYPE bapiaddr1,
 gt_t_xknvi TYPE STANDARD TABLE OF fknvi,
 gwa_t_xknvi TYPE fknvi,
 gt_t_xknbk TYPE STANDARD TABLE OF fknbk,
 gwa_t_xknbk TYPE fknbk,
 gt_t_yknvp TYPE STANDARD TABLE OF fknvp,
 gwa_t_xknvp TYPE fknvp.
TYPES:BEGIN OF gty_itab1,
 abc(305),
 END OF gty_itab1.
DATA: gt_itab1 TYPE STANDARD TABLE OF gty_itab1,
 gwa_itab1 TYPE gty_itab1.
TYPES :BEGIN OF gty_itab2,
 ktokd(4), "customer account grp kna1
 kunnr(10), "customer kna1
 name1(35), "name1 kna1
 sortl(10), "sort filed kna1
 stras(35), "house number and adres kna1
 pstlz(10), "postal code kna1
 ort01(35), "city kna1
 land1(3), "country kna1
 telf1(16), "tele phone no kna1
 telfx(31), "fax num kna1
 kukla(2), "cust classificaion kna1
 bukrs(4), "company code knb1
 akont(10), "reconcilation acct knb1
 vkorg(4), "sales org knvv
 vtweg(2), "distr chan knvv
 spart(2), "division knvv
 zterm(4), "terms of payment knvv
 bzirk(6), "sales district knvv
 vkbur(4), "sales office knvv
 vkgrp(3), "sales grp knvv
 kdgrp(2), "cust grp knvv
 waers(5), "currency knvv
 konda(2), "price grp knvv
 kalks(1), "pricing procedure assign knvv
 lprio(2), "delivery plant knvv
 vsbed(2), "shipping conditions knvv
 vwerk(4), "delivering plant knvv
 inco1(3), "inco1 knvv
 inco2(28), "inco2 knvv
 kkber(4), "cred control area knvv
 ktgrd(2), "acc assgn grp knvv
 taxkd(1), "tax classification 4 cust knvi
 bankn(18), "bank account number knbk -
 xkunnr(10),
 END OF gty_itab2.
DATA: gt_itab2 TYPE STANDARD TABLE OF gty_itab2,
 gwa_itab2 TYPE gty_itab2.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
 filename = p_files
 filetype = 'ASC'
TABLES
 data_tab = gt_itab1
EXCEPTIONS
 file_open_error = 1
 file_read_error = 2
 no_batch = 3
 gui_refuse_filetransfer = 4
 invalid_type = 5
 no_authority = 6
 unknown_error = 7
 bad_data_format = 8
 header_not_allowed = 9
 separator_not_allowed = 10
 header_too_long = 11
 unknown_dp_error = 12
 access_denied = 13
 dp_out_of_memory = 14
 disk_full = 15
 dp_timeout = 16
 OTHERS = 17.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT gt_itab1 INTO gwa_itab1.
gwa_itab2 = gwa_itab1-abc(305).
APPEND gwa_itab2 TO gt_itab2.
ENDLOOP.
LOOP AT gt_itab2 INTO gwa_itab2.
SPLIT gwa_itab2 AT ',' INTO gwa_itab2-ktokd
 gwa_itab2-kunnr
 gwa_itab2-name1 gwa_itab2-sortl
 gwa_itab2-stras gwa_itab2-pstlz
 gwa_itab2-ort01 gwa_itab2-land1
 gwa_itab2-telf1 gwa_itab2-telfx
 gwa_itab2-kukla gwa_itab2-bukrs
 gwa_itab2-akont gwa_itab2-vkorg
 gwa_itab2-vtweg gwa_itab2-spart
 gwa_itab2-zterm gwa_itab2-bzirk
 gwa_itab2-vkbur gwa_itab2-vkgrp
 gwa_itab2-kdgrp gwa_itab2-waers
 gwa_itab2-konda gwa_itab2-kalks
 gwa_itab2-lprio gwa_itab2-vsbed
 gwa_itab2-vwerk gwa_itab2-inco1
 gwa_itab2-inco2 gwa_itab2-kkber
 gwa_itab2-ktgrd
 gwa_itab2-taxkd
 gwa_itab2-bankn.
*moving files values from ITAB2 work area to global structure related to FM.
gs_i_kna1-ktokd = gwa_itab2-ktokd.
gs_i_kna1-kunnr = gwa_itab2-kunnr.
gs_i_kna1-name1 = gwa_itab2-name1.
gs_i_kna1-sortl = gwa_itab2-sortl.
gs_i_kna1-stras = gwa_itab2-stras.
gs_i_kna1-pstlz = gwa_itab2-pstlz.
gs_i_kna1-ort01 = gwa_itab2-ort01.
gs_i_kna1-regio = gwa_itab2-land1.
gs_i_kna1-telf1 = gwa_itab2-telf1.
gs_i_kna1-telfx = gwa_itab2-telfx.
gs_i_kna1-kukla = gwa_itab2-kukla.
gs_i_knb1-bukrs = gwa_itab2-bukrs.
gs_i_knb1-akont = gwa_itab2-akont.
*I FOR GOT TO INCLUDE THE ZTERM VALUE IN EXCELL SHEET SO INCLUDED HARD CODE HERE
gs_i_knb1-zterm = '0001'.
gs_i_knvv-vkorg = gwa_itab2-vkorg.
gs_i_knvv-vtweg = gwa_itab2-vtweg.
gs_i_knvv-spart = gwa_itab2-spart.
gs_i_knvv-zterm = gwa_itab2-zterm.
gs_i_knvv-bzirk = gwa_itab2-bzirk.
gs_i_knvv-vkbur = gwa_itab2-vkbur.
gs_i_knvv-vkgrp = gwa_itab2-vkgrp.
gs_i_knvv-kdgrp = gwa_itab2-kdgrp.
gs_i_knvv-waers = gwa_itab2-waers.
gs_i_knvv-konda = gwa_itab2-konda.
gs_i_knvv-kalks = gwa_itab2-kalks.
gs_i_knvv-lprio = '02'. "gwa_itab2-lprio.
gs_i_knvv-vsbed = gwa_itab2-vsbed.
gs_i_knvv-vwerk = gwa_itab2-vwerk.
gs_i_knvv-inco1 = gwa_itab2-inco1.
gs_i_knvv-inco2 = gwa_itab2-inco2.
gs_i_knvv-kkber = gwa_itab2-kkber.
gs_i_knvv-ktgrd = gwa_itab2-ktgrd.
gwa_t_xknvi-tatyp = 'UTXJ'. "HARD CODE
gwa_t_xknvi-aland = 'US'. "HARD CODED
gwa_t_xknvi-kz = '0'. "HADR CODE
gwa_t_xknvi-taxkd = '0'. "gwa_itab2-taxkd.
APPEND gwa_t_xknvi TO gt_t_xknvi.
gwa_t_xknbk-bankn = gwa_itab2-bankn.
APPEND gwa_t_xknbk TO gt_t_xknbk.
gs_i_knb1-lockb = 'X'.
gs_i_knvv-kzazu = 'X'.
gs_i_knvv-kztlf = 'X'.
gs_i_knvv-perfk = 'X'.
gs_i_knvv-prfre = 'X'.
gs_i_kna1-spras = 'EN'.
CALL FUNCTION 'SD_CUSTOMER_MAINTAIN_ALL'
 EXPORTING
 i_kna1 = gs_i_kna1
 i_knb1 = gs_i_knb1
 i_knvv = gs_i_knvv
I_BAPIADDR1 =
I_BAPIADDR2 =
I_MAINTAIN_ADDRESS_BY_KNA1 = ' '
I_KNB1_REFERENCE = ' '
I_FORCE_EXTERNAL_NUMBER_RANGE = ' '
I_NO_BANK_MASTER_UPDATE = ' '
I_CUSTOMER_IS_CONSUMER = ' '
I_RAISE_NO_BTE = ' '
PI_POSTFLAG = ' '
PI_CAM_CHANGED = ' '
PI_ADD_ON_DATA =
I_FROM_CUSTOMERMASTER = ' '
IMPORTING
e_kunnr = xkunnr
o_kna1 = xkunnr
E_SD_CUST_1321_DONE =
 TABLES
T_XKNAS =
 t_xknbk = gt_t_xknbk
T_XKNB5 =
T_XKNEX =
T_XKNVA =
T_XKNVD =
 t_xknvi = gt_t_xknvi
T_XKNVK =
T_XKNVL =
T_XKNVP =
T_XKNZA =
T_YKNAS =
T_YKNBK =
T_YKNB5 =
T_YKNEX =
T_YKNVA =
T_YKNVD =
T_YKNVI =
T_YKNVK =
T_YKNVL =
 t_yknvp = gt_t_yknvp
T_YKNZA =
T_UPD_TXT =
 EXCEPTIONS
 client_error = 1
 kna1_incomplete = 2
 knb1_incomplete = 3
 knb5_incomplete = 4
 knvv_incomplete = 5
 kunnr_not_unique = 6
 sales_area_not_unique = 7
 sales_area_not_valid = 8
 insert_update_conflict = 9
 number_assignment_error = 10
 number_not_in_range = 11
 number_range_not_extern = 12
 number_range_not_intern = 13
 account_group_not_valid = 14
 parnr_invalid = 15
 bank_address_invalid = 16
 tax_data_not_valid = 17
 no_authority = 18
 company_code_not_unique = 19
 dunning_data_not_valid = 20
 knb1_reference_invalid = 21
 cam_error = 22
 OTHERS = 23.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF sy-subrc EQ 0.
 CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
 WRITE: / 'Error Message:', 'error in creation'.
ELSE.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
 WRITE: / 'costomer', gwa_itab2-kunnr, 'created'.
ENDIF.
ENDLOOP.

please let me know if my qestion is not clear...
and please cinfirm me ..that can i use the function module (SD_CUSTOMER_MAINTAIN_ALL) instead of BAPI (BAPI_CUSTOMER_CREATEFROMDATA1) for uploading customer master data.
please respond me ASAP.
thanks in advance and will give full points
thanks&regards
Srinivas.

Return to vendor via delivery customer master

Hi Gurus,
I am doing the return delivery to vendor(122) via delivery.
Now when I am creating the vendor and selceting Returns vendor and shipping
condition sytem (and account group for customer) is creating a customer master in
the background.
Now when I am seeing the customer master XD03 it is created with general data and
Sales Org data.no comapany code data is created.
And I can find that this customer is created for
Sales Org 1000
Dist. Chn 10/12/00
Now my question is why only this 3 combination is created and how it is determined
or where we maintain this in customization.
Thanking you

Hi,
Thanks for your valuable input.
But I find that My POrg 1000 is assigned to 10 plants ( other than my plant 1000)) in T024w
and at the customizing -> Assignment Sales Organization/Distribution Channel - Plant (table TVKWZ)
and My plant 1000 is assigned to at least 50 combination of S.org and D.ch (TVKWZ)
Just curious why out of so many combination system is creating only 3
Thanks in advance

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

More than one Plant in Customer Material record

In Customer Material Info record I want a option of more than one plant. Right now I can enter only one plant in customer material info record. What can I do to have a option of more than one plant in customer material info record.
Regards,
Kumar

hello, friend.
as i understand, you would want options for more than one plant (to choose from) and not to restrict the number of choices.
for practical reasons, you can only enter 1 (standard) plant in the customer-material info record. nevertheless, you can enter a different plant in the customer master, and another plant in the material master.
when you process the sales order, you can change the plant to any other choices, even those not included in the customer-material or customer master data, as long as these plant choices and your customer are assigned the same distribution channel. of course, your material should also be extended to these plants.
i hope this helped, even if a little.
regards.
jty

Custom Master Text Tables

Hi,
I'm creating a customer master report and having problem determining the text tables of some fields:
a.) Sales Region
b.) Sales Office
c.) Customer Group
d.) Delivery Priority
e.) Shipping Conditions
f.) Delivering Plant
g.) Partial delivery per item (Complete delivery indicator)
h.) Terms of payment
i.) Acct assgmt group
Appreciate any helpful hints.
Regards,
Mawi

currently, i dont hv SAP access, so, just am answering generically,
- you can get them with check tables relationship, in either SE11 or SE16
- use WHERE USED LIST of that particular field, then pick the table, which possess the T in the last position of the name
- also check, VALUE TABLEs at domain level in SE11
thanq
Edited by: SAP ABAPer on May 6, 2009 4:40 AM

Customer master creation or entering data into customer master.

Hi Friends
Can any give good example to create customer master from Account group to entering customer master data? so that to move forward.
Thanks in advance.

2.1 Customer Master
2.1.1 Account Group
2.1.1.1 Maintain Number Range for Account Group
Use
The purpose of this activity is to control number range of Account Group.
Procedure
Access the activity using one of the following navigation options:
IMG --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable --> Customer Accounts --> Master Data --> Preparations for Creating Customer Master Data --> Create Number Ranges for Customer Accounts --> Select the Icon to maintain Number Range
Transaction Code: SPRO
Data to be maintained:
No | From | To | Current No | Ext (Tick in Check Box)
01 | 0000000001 | 0000099999 | 0 | No
02 | 0000100000 | 0000299999 | 0 | No
XX | A | ZZZZZZZZZZ | Yes
2.1.1.2 Assign Number Range to Account Group
Use
The purpose of this activity is to maintain number range of Account Group.
Procedure
Access the activity using one of the following navigation options:
IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Assign Number Ranges to Customer Account Groups
Transaction Code : SPRO
Data to be maintained:
Group | Name | Number Range
0001 | Sold-to party | XX
0002 | Goods recipient | XX
0003 | Payer | XX
0004 | Bill-to party | XX
2.1.1.3 Define Account Groups with Screen Layout (Customers)
Use
In this step, you determine the account group of the customer.
Procedure
Access the activity using one of the following navigation options:
IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Define Account Groups with Screen Layout (Customers)
Transaction Code : SPRO
The groups indicated below are a few examples. There are many groups in Standard SAP & if we require additional Group, it can be copied from appropriate group & maintained.
Group | Name
0001 | Sold-to party
0002 | Goods recipient
0003 | Payer
0004 | Bill-to party
0005 | Prospective customer
0006 | Competitor
Select Sold-to-party > go to Details > Double Click on General data / Company code data / Sales data. It will take to next screen which details Tab Pages of General data / Company code data / Sales data. Double Click on Tab Page for example: Address, Control, Marketing & so on. Here you can maintain whether the field is to be Suppress, Req. Entry, Opt. entry or Display
2.1.2 Process to Create Customer Master
2.1.2.1 Initial Screen of Customer Master Maintainance
Use
The purpose of this activity is to maintain Customer Master Data. Customer Master Can be created for Sales & Distribution, in which it will be possible to maintain General Data Tab & Sales Area Tab. Alternatively it is also possible to maintain Complete / FI, in which it is possible to maintain General Data, Company Code Data & Sales Area Data (Complete) or General Data & Company Code (F1)
Procedure
Access the activity using one of the following navigation options:
SAP Easy Access > Logistics > Sales and Distribution > Master Data > Business Partner > Customer > Create > Sales and Distribution / Complete
Transaction Code : VD01 / XD01
Fields to be maintained in Initial Screen (referring Complete):
Field - Functionality
Account Group - Take a drop down & select appropriate Account Group
Customer Enter manually
Company Code - Take a drop down
Sales Organization - Take a drop down
Distribution Channel - Take a drop down
Division - Take a drop down
A Customer can be created with reference to an existing Customer & necessary data can be changed.
Reference
Field - Functionality
Customer - Enter manually
Company Code - Take a drop down
Sales Organization - Take a drop down
Distribution Channel - Take a drop down
Division - Take a drop down
2.1.2.2 General Data of Customer Master Maintenance
Use
The purpose of this activity is to maintain General Data. General Data is applicable to the customer centrally. Incase of extending Customer to another Sales Area, General data will remain the same.
Procedure
Fields to be maintained are as under:
ADDRESS
Field - Functionality
Title - Take a drop down
Name - Enter manually
Search Term - Enter Manually (Optional)
Street - Enter Manually (Optional)
House No - Enter Manually (Optional)
Postal Code - Enter manually
City - Enter manually
Country - Take a drop down
Region - Take a drop down
Control Data
Field - Functionality
Vendor - Enter Manually (Optional) To establish Customer Vendor Relationship.
Trading Partner - To be maintained incase of Inter-company Customer,
The above is for Illustration purpose. Please ensure to maintain the fields required.
2.1.2.3 Company Code Data of Customer Master Maintenance
Use
The purpose of this activity is to maintain Company Code Data. This is maintained by an FI person.
Procedure
Fields to be maintained are as under:
Account Management
Field - Functionality
Recon. Account - Take a drop down (Mandatory)
Payment Transaction
Field - Functionality
Terms of payment - Take a drop down.
The above is for Illustration purpose. Please ensure to maintain the fields required.
2.1.2.4 Sales Area Data of Customer Master Maintenance
Use
The purpose of this activity is to maintain Company Code Data. This is maintained by an FI person.
Procedure
Fields to be maintained are as under:
Sales
Field- Functionality
Sales Office - Take a drop down & maintain the appropriate SBU
Currency - Maintain the local / export currency.
Exch. Rate Type- Maintain M, incase of export / inter-company(if required) only.
Cust. Pric. Proc -This is maintained to pick the pricing procedure in Sales Order & Billing Document. It should always be maintained.
Customer Stat. Gr - This is recommended to be maintained to enable the data to flow to SAP standard report.
Shipping
Field -Functionality
Delivery Priority - Take a drop down & maintain the appropriate for Delivery purpose.
Order Combination - Maintain the tick
Shipping Condition -Take a drop down & maintain the appropriate for Delivery purpose.
Delivery Plant - Take a drop down & maintain the appropriate Plant.
Billing
Field - Functionality
Incoterm - Take a drop down & select. Maintain the Description manually.
Terms of payments -Take a drop down & select.
Account assignment Group -Take a drop down & maintain the appropriate. This is very important to be maintained, else it will give an error to release the billing document to accounting.
Tax - Take a drop down & select 0 or appropriate.
The above is for Illustration purpose. Please ensure to maintain the fields required.
Regards,
Rajesh Banka
Reward points if helpful

Customer Master - Tax Records

Hi - We have added a new plant in a new country and attached to Sales Organization. As a result, we need to update customer tax records for shipments from this plant. When I go in to XD99 (MASS) - It doesn't allow me to create new records option in KNVI object. Can you tell me the easiest way to add new records for this country in customer master? Thanks. I will award points for any helpful guidance.
Regards
R

Hi Surya,
Are you talking about the tax indicator?
If yes then you can change it in MASS.
T-code MASS --> Object KNA1 --> Select KNVI --> Execute --> Enter your customer --> Execute --> Click at "Select field" icon (extreme left) --> There is only one field Tax classification --> Select it --> Enter --> change the value in "New Values" --> Click at Carry out Mass change"
Hope it helps,
Regards,
MT

Material wise Sales area and customer master

Hi,
Suppose I have a plant 4002, if i want to see all the material of plant 4002 then i can see those to following MM60 transaction code but if i want to see a particular material and that material is belongs to which sales area and which customer master then how it could be possible .
Regards
Jibanjyoti

Hi,
You cannot see a material on customer basis unless it's MTO scenario, still try in t-code MB52.
Otherwise try in table level as suggested above.
Reg,
JJ
Edited by: Jagsap on May 26, 2011 2:01 PM

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

Plant on Customer Master

Similar Messages

Maybe you are looking for