Customer Record Creation - XD01

hello,
I am trying to upload data like Street2, street3 and street 4 which can be viewed in the street address drop down in transacction XD01/02. In call transaction i am not able to upload.
Please can anyone tell me the reason why it is doing so?
Thanks and Regards
Swarna

It will be stored in ADRC Table. So you can upload the Street2, street3 and street 4 in ADRC table.
Goto KNA1 table give the customer take the address number (ADRNR) -> Then goto table ADRC give the ADRNR in the field ADDRNUMBER.
Regards,
Prakash.

Similar Messages

Problem in creating customer record thru xd01

1. I cant create CMR thru XD01
*Error : Account 101 already Exist*
2. In VL01N
error1: copying not possible because entry is missing in table TCPCL AKOR (sales order) TAN
Error 2. Number of copying routine for the TABLE LIPS is missing in table TVPCL

You seem to ask 2 different questions at the same time.
This is quite confusing.
I suggest you close this message and open 2 different posts with specific questions.
Regards,
Franck

Automatic creation of Credit customer management after XD01

Hi,
What is the customizing needed to generate automatically the Credit customer management (FD32) after the creation of customer master data (XD01) ?
Please hep
Regards.

Make default setting in transaction OB45
Regards,
SDNer

Error while uploading Customer creation ( XD01) using Call Transaction

Hi Experts,
While recording XD01, i checked on Use Central Address Management checkBox,
i got two pop-ups,
   1. Postal code 500018 in country IN does not exist.
   2. City Hyderabad in country IN does not exist.
i accepts those pop-ups by Clicking on Yes Button.
while executing in All Screen Mode it executes without errors,
But in No Screen mode i am getting error in address screen and in the messtab i got MSGV1= 500018 (postal code) and
FLDNAME =   SZA1_D0100-TITLE_MEDI.
Is there any other way to get the Title in title list box without using Use Central Address Management Check Box,
without checking Use Central Address Management Check Box, i am not getting the title in the title list box while displaying in XD02.
Please help me out to solve the problem.
Thanks & Regards,
Karthick.

Hi,
I solved this problem.
By changing the configuration Data through the path spro->SAP NetWeaver-> General Settings->set Contries->Set Contry-Specific Checks and click on the Contry code, a screen will display the default checks. Previously it is configured to a particular location with respect to Pincode , i updated as per my requirement. So the pop-ups are not coming and it workes fine in all Modes(A/N/E) of BDC.
The Title problem is also solved by revised recording of XD01.
Then my problem is solved.
Thanks & Regards,
Karthick.

While doing LSMW standard method for Customer master creation..

while doing LSMW standard method for Customer master creation.....
In 13th step I am getting this king of error
FB012 Session 1 : Special character for 'empty field' is /
FB007 Session 1 session name ZPROJ was opened
FB109 Trans. 1 : Transaction xd01 is not supported
FB016 ... Last header record ...
FB014 ... BKN00-STYPE 1
FB014 ... BKN00-TCODE xd01
FB014 ... BKN00-KUNNR
FB014 ... BKN00-BUKRS
FB014 ... BKN00-VKORG A1
FB014 ... BKN00-VTWEG 00
FB014 ... BKN00-SPART 0
FB014 ... BKN00-KTOKD
FB014 ... BKN00-KKBER BP01
FB013 ....Editing was terminated
Can anyone help how to solve this?

Hello TJK,
FB012 Session 1 : Special character for 'empty field' is /
This is the special function in LSMW, for empty field system will put / sign automatically, so you need not to worry about that.
FB007 Session 1 session name ZPROJ was opened It is opening session ZPROJ which is your project name/object name.
FB109 Trans. 1 : Transaction xd01 is not supported
Check out your field mapping and conversion rule for object.
FB013 ....Editing was terminated
It is not finding proper field mapping rule / file inputs so the sytem terminates the LSMW object.
Check your field mapping and conversion rule, check your source fields, save the file in tab delimited format.
Hope this helps.
Regards
Arif Mansuri

Problem in customer master creation using BAPI_CUSTOMER_CREATEFROMDATA1

Hi Guru's...
i am unable to go forward...
can you please help me out in this customer master creation....
what are the fileds i am using while creating in XD01 (account group,name,country)then i am able create and the customer number is autogenerated.
using same field values i am trying to test the BAPI initially but i am unable to execute the BAPI BAPI_CUSTOMER_CREATEFORMDATA1.
in this one draw back is when compare to the XD01 peocess is account group.
account group is mandataory in XD01 process and in BAPI test there i sno field for giving this account group field value.....may be this is one reason....(if it is mandatory where i have to provide in BAPI test..)
and i tried in BAPI test using customer reference ID also....
please guide me....
please let me know if my question is not clear...
Thanks in advance
Srinivas...

thanks rajani ur valuble reply..
but i am looking for creating at a time 'n' number of customer's using BAPI (the coustomers data will be in flat file in presentation server....)
please advise me ..
let me know if my question is not clear...
thanks in advance
srinivas....

SAP ISU Schedule Records creation

Hi
Experts,
We are now approaching a phase in our project where we need to create NEW Schedule Records for coming years. SAP Default setting restricts upper limit for Schedule record creation as seven years but I know that we can over-ride that also.
My question is that
Does anyone has created schedule records in their project for more than seven years in one go & have you faced any problems.
What is rationale behind SAP standard limit of seven Years or what sort of problems can be expected if we over-ride the SAP limit of Seven years.
Thanks,
Manish

Hello satish
Step 1:
Create Framework Id( assign hidden & visible components)
Step 2: Create CIC profile
Step 3: create Org unit and assign person
Step 4: Assign CIC profile to Org. unit (or) person
Path : Easy access screen
Logistics>Customer service>Customer Interaction center>Adminstration>CIC structure>Org.Structure(Change,T.code-PPOMW)>select Org. unit
In this screen on the top i.e menu bar find Go To
Go To>detail Object>Enchanced object description
Now u r in Maintain object page(T code-PP01)
Now in the Active tab page select CIC profile
Now in menu bar Edit>create infotype
Again u r in new page(T code-PP01)
Enter the CIC profile Id which u have created in customizing
Run T code- CIC0
I hope u r able to see the screen now
Rgds
Madhusudhan

Adding custom fields to XD01 transaction

Hi All,
I need to add custom fields to the Customer create transaction (XD01). Can anyone tell me the feasibility of having screen-exits or BADIs to acheive the same? I have searched for screen exits but could found none, and regarding BADI's i found these CUSTOMER_ADD_DATA, CUSTOMER_ADD_DATA_CS and CUSTOMER_ADD_DATA_BI. Unfortunately there is no default code assigned to these BADI's. Please tell me how we can acheive the requirement. we dont have any include too in the KNA1 table hence i feel going with APPEND structure.
Thank You
Yugandhar K

Hello Mahesh B
In short
The Number field determines the display order of the Tabs on your new screen. The i_taxi_fcode parameter is the text you entered, or will enter, in the Function Code field on the Label Tab Pages.
In long
In the IMG activity Prepare Modification-Free Enhancement in Customer Master Record, you add a Screen Grp code (e.g. Z1) and a description. Then you select Z1 and double-click the Label Tab Pages folder on the left.
Now, add one or more records in this Label Tab Pages screen. Each record you add will cause a Tab to be displayed on your new Z1 screen (once you implement the screen with a program as described in earlier posts).
The fields of the Label Tab Pages records are:
- NUMBER, which determines the order that the Tabs will be displayed;
- FUNCTION CODE, this is passed to the BAdI as i_taxi_fcode;
- DESCRIPTION, which becomes the Label displayed on the Tab; and
- ICON, which, if entered, will display beside the Label on the Tab.
Example records:
10, Z1_TR1, Tab1description, <blank icon field>
20, Z1_TR2, Tab2description, <Some Icon>
I prefixed my FUNTION CODEs with the screen group (e.g. Z1_TR1 and Z1_TR2).
More than one BAdI can be implemented in the system at the same time, so you should use the Screen Grp (e.g. Z1) and/or the Tab FUNCTION CODE (i_taxi_fcode - e.g. Z1_TR1) to determine when to execute your custom code.
Below is an example implementation of the get_taxi_screen method in the customer_add_data_cs BAdI.
If a user were to click on the second Tab of the Z1 screen group, the Z1_TR2 case would be executed and screen 200 would display on this Tab screen. If the user clicked back to the first tab, the Z1_TR1 case would be executed and screen 100 would display on this Tab.
method if_ex_customer_add_data_cs~get_taxi_screen .
case flt_val.
 when 'Z1'.
 case i_taxi_fcode.
 when 'Z1_TR1'.
 e_screen = '0100'.
 e_program = 'Z_PROGRAM_NAME'.
 e_headerscreen_layout = ' '.
 when 'Z1_TR2'.
 e_screen = '0200'.
 e_program = Z_PROGRAM_NAME'.
 e_headerscreen_layout = ' '.
 endcase.
endcase.
endmethod.
Hope this helps.
Allan

Problem with Multiple record creation using BAPI BAPI_PRICES_CONDITION

Hi,
I am working on IS Media Sales And Distribution wherein i am using BAPI BAPI_PRICES_CONDITION for condition record creation in TCODE JC9B. I am able to create one record using this BAPI for one sales promotion but having problem while creation of multiple records for the same sales promotion wherein my internal table have multiple records. It gives me error that data in BAPICONDIT is missing.
I am aatching followig code for reference
BAPI have field of varkey which i am filling as combination of sales org. + distn channel + sales promotion + delivery type
In this varkey delivery type is changing for sales promotion Can be said that one sales promotion can have multiple delivery type .
Am i giving the correct varkey for each itration of internal table ?
I am attaching code for reference.
Here loop it_cond contain one promotion and multiple delivery type.
sales org distn ch promotion delivery
0100 01 zsalesprom 03
0100 01 zsalesprom z3
LOOP AT it_cond INTO wa_cond.
Get next condition number
 CALL FUNCTION 'NUMBER_GET_NEXT'
 EXPORTING
 nr_range_nr = '01'
 object = 'KONH'
QUANTITY = '1'
SUBOBJECT = ' '
TOYEAR = '0000'
IGNORE_BUFFER = ' '
 IMPORTING
 number = number
QUANTITY =
RETURNCODE =
EXCEPTIONS
INTERVAL_NOT_FOUND = 1
NUMBER_RANGE_NOT_INTERN = 2
OBJECT_NOT_FOUND = 3
QUANTITY_IS_0 = 4
QUANTITY_IS_NOT_1 = 5
INTERVAL_OVERFLOW = 6
BUFFER_OVERFLOW = 7
OTHERS = 8
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
Here i am concacating varkey for each new delivery
CLEAR : l_min,l_length,l_var.
CONCATENATE wa_cond-vkorg wa_cond-vtweg wa_cond-wrbakt INTO l_var.
l_length = STRLEN( l_var ).
IF l_var+14(2) IS INITIAL.
WRITE wa_cond-lifart TO L_VAR+14.
l_length = STRLEN( l_var ).
ENDIF.
W_LINE = W_LINE + 1.
*First table in BAPI
 wa_bapicondct-operation = '009'.
 wa_bapicondct-cond_usage = 'A'.
 wa_bapicondct-table_no = '506'.
 wa_bapicondct-applicatio = 'J0'.
 wa_bapicondct-cond_type = 'RATE'.
 wa_bapicondct-varkey = l_var.
 wa_bapicondct-valid_to = wa_cond-datbi.
 wa_bapicondct-valid_from = wa_cond-datab.
 wa_bapicondct-cond_no = number. "
 APPEND wa_bapicondct TO it_bapicondct.
*Second table in BAPI
 wa_bapicondhd-operation = '009'.
 wa_bapicondhd-cond_no = number.
 wa_bapicondhd-cond_usage = 'A'.
 wa_bapicondhd-table_no = '506'.
 wa_bapicondhd-created_by = sy-uname.
 wa_bapicondhd-creat_date = sy-datum.
 wa_bapicondhd-applicatio = 'J0'.
 wa_bapicondhd-cond_type = 'RATE'.
 wa_bapicondhd-varkey = l_var.
 wa_bapicondhd-valid_from = wa_cond-datab.
 wa_bapicondhd-valid_to = wa_cond-datbi.
 APPEND wa_bapicondhd TO it_bapicondhd.
*Third table in BAPI
 wa_bapicondit-operation = '009'.
 wa_bapicondit-cond_no = number.
 wa_bapicondit-cond_count = wa_cond-cond_count.
 wa_bapicondit-applicatio = 'J0'.
 wa_bapicondit-cond_type = 'RATE'.
 wa_bapicondit-calctypcon = 'C'.
 wa_bapicondit-scaletype = 'A'.
 wa_bapicondit-cond_value = wa_cond-kbetr.
 wa_bapicondit-condcurr = wa_cond-konwa.
 wa_bapicondit-promotion = wa_cond-wrbakt.
 APPEND wa_bapicondit TO it_bapicondit.
*Fourth table in BAPI
 wa_bapicondqs-operation = '009'.
 wa_bapicondqs-cond_no = number.
 wa_bapicondqs-cond_count = wa_cond-cond_count.
 wa_bapicondqs-currency = wa_cond-kbetr.
 wa_bapicondqs-condcurr = wa_cond-konwa.
 wa_bapicondqs-cond_unit = 'EA'.
 wa_bapicondqs-LINE_NO = W_LINE."'0001'.
 APPEND wa_bapicondqs TO it_bapicondqs.
*Fifth table in BAPI
 wa_bapicondvs-operation = '009'.
 wa_bapicondvs-cond_no = number.
 wa_bapicondvs-cond_count = wa_cond-cond_count.
 wa_bapicondvs-currenckey = wa_cond-konwa.
 wa_bapicondvs-currenciso = wa_cond-konwa.
 wa_bapicondvs-currency = wa_cond-kbetr.
 wa_bapicondvs-condcurr = wa_cond-konwa.
 wa_bapicondvs-curren_iso = wa_cond-konwa.
 wa_bapicondvs-LINE_NO = W_LINE."'0001'.
 APPEND wa_bapicondvs TO it_bapicondvs.
 CALL FUNCTION 'BAPI_PRICES_CONDITIONS'
EXPORTING
PI_INITIALMODE = ' '
PI_BLOCKNUMBER =
 TABLES
 ti_bapicondct = it_bapicondct
 ti_bapicondhd = it_bapicondhd
 ti_bapicondit = it_bapicondit
 ti_bapicondqs = it_bapicondqs
 ti_bapicondvs = it_bapicondvs
 to_bapiret2 = it_bapiret2
 to_bapiknumhs = it_bapiknumhs
 to_mem_initial = it_cnd_mem_initial
 EXCEPTIONS
 update_error = 1
 OTHERS = 2
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = 'X'
IMPORTING
RETURN =
 CLEAR : wa_bapicondct,wa_bapicondhd,wa_bapicondvs,wa_bapicondqs.
 CLEAR : wa_bapicondit.
 ENDLOOP.
 ENDIF.
ENDIF.
Kindly Suggest.
Thanks
Parag

Solved By myself
There is problem while passing data to internal table for item level

Error occurs during Asset Master Record Creation.

Hello SAP Gurus,
The error occurs during asset master record creation.
Our fiscal year variant is Z6 (July to June). The asset was acquired in June 15 (previous fiscal year) but was only set up on July 30 (this fiscal year) . When we put the depreciation start date as 15 June the error appeared. While saving the Asset master we are getting below error.
We tried the same with Post Capitalization of Asset (ABNAN) there also we are getting same error.
ERROR: - as below
u2003
SYST: *You cannot determine the period for rule 02 to 05.08.08 ( todayu2019s date )*
*Message no. AA613*
*Diagnosis*The system could not determine a depreciation period on 05.08.08 for period control 02 of the period control method of phase N1 of depreciation key INTERN-00001-0000.
Procedure
Maintain the assignment of the periods for the period control entered.
Proceed
If the period control you entered is a standard period control, you can assign the periods automatically.Proceed
Please find enclosed attachment for clear description of the error.
Please share your experiences regarding this subject.
Thanking you in anticipation.
Regards,
Suresh.
09986375966

Hi,
have you generated the period controls properly? If not, the error is raised correctly by the system.
To generate period controls go to:
IMG Asset Accounting -> Depreciation -> Valuation Methods -> Period Control -> Generate Period Controls / or you can use OA84
Regards,
Markus

Make a field required on record creation, read only after that

Hello,
Does anyone know of a way to make a pick-list field required on record creation, but read-only after that? The other twist to this is that we need to allow this field to also be read-write for all the integration edits, since this field's value could change in the enterprise database.
Thanks,
Neal G.

Hi !
I think you can add a validation rule for that. Something like :
IIf(PRE('<YOURFIELD>') IS NULL, <> '', = PRE('<YOURFIELD>'))
This means that if the previous value of your field is null (it's a creation), so the value must be different than blank. Else, it must be equal to the previous value, so not modified.
I didn't tested it, but I let you get back to me if it works... or not !
You'll just have to add a message saying that this field is required on creation and readonly after...
Hope this will help, feel free to ask more !
Max

Mass Maintenance will recognize any customer record in workflow process

Hi gurus,
Please help me on the Workflow process, how to handle below workflow scenario, is there any logic be hand this.
please see in BOLD workflow issue.
1.2     As-Is Business Process
Currently Data Maintenance teams use standard SAP transaction XD07 to change Customer Account Groups. The standard transaction XD07 allows only one Customer Account Group to be changed at a time. The process is to be manually repeated for every customer. After the Account Group is changes in the request client (X07(10)), an RFC call is made to the BOR client (X07(20)) and then to the transaction client (X08(10)) to change the Customer Account Group as the SAP ALE process does not support Account Group Changesu2026
1.3     To-Be Business Process
From time to time, bulk customer data updates will be needed. This can be the result of business situations that cause multiple updates to be performed for given customer fields such as Customer Account Group field. A new program must be developed to let the user mass update the Customer Account Group field (KNA1-KTOKD). The Program should be accessed on demand using a new T.Code (YMDM_ACCTGRP_CHG).
Business users will submit a spreadsheet in the appropriate upload format to CDM along with written approval from the Food Service data owner to execute the upload in P07. CDM will execute the upload, record all documentation for the audit change log and notify the submitter when complete
1.4     To-Be Business Process Flow Diagram
1.5     Enhancement Functionality
The following are the requirements:
u2022     This tool will enable a user to perform bulk update to the customer account group field.
u2022     The utility should let the user upload a u201CTab delimitedu201D file to mass update the Account Group field.
u2022     The Load File will have 3 columns, Customer Number (KNA1-KUNNR), Current Account Group (KNA1-KTOKD) and New Account Group (KNA1-KTOKD).
u2022     The Program must utilize the process behind the standard SAP transaction XD07 to change customer Account Groups in X07(10).
u2022     The standard customer ALE (DEBMAS) process does not support Customer Account Group changes, so the mass change program must use the RFC functionality to change he Account Groups in the BOR (X07(20)) and Transaction system (X08(10)).
u2022     Workflows for all updates performed using this T.Code are automatically approved. No manual approval steps will be needed after data load.
u2022     Mass Maintenance will recognize any customer record that has an open workflow. If a customer record is already in the request queue, it is u201Coff limitsu201D for any bulk update. That update request to that particular customer record must be rejected.
u2022     Provide the option to run the process in validation mode and update mode.
u2022     Report all hard and soft legacy field errors on a validation report. All u201Chardu201D legacy field validations should be passed before allowing update mode to run.
u2022     The upload process will produce an error log for all records not loaded into the system.

see newer message. Problem appears to be related to gmail

PROBLEM IN CUSTOM IDOC CREATION

Hi Friends,
                I'm facing a problem in custom idoc creation plz try to assist me
1.As per the information i have i'm creating segment in we31
for cremas01 idoc.But when i enter the name for segment i'm getting message "Name range Voilation particular name which i had given is not permitted in customer system?
Plz clarify this,and are there any formalities which i should look for before creating custom idoc?
Good answers will be rewarded.
                                                                          Regards,
                                                                           Vinod.

The Problem might be.... with the naming of the segment.
Standard segments should be created with 'E1' and all the custom segments are created using 'Z1' and the name with 8 characters long only is permitted.
Reward Points if useful.

BPM + MDM Multi record creation

Hi everyone!
We are developing Master Data Governance scenario with MDM + BPM. The key concept is creation, update and approval of MDM record in a BPM process. Tasks are human based.
So we came upon the following question.
Is it possible somehow to model the process in the way that Create Record task will include multi record creation. So that the user can create several records at once (one by one) - and they will then be maintained in a single process instance. It's also perfect if the user will see prior created records (during that specific process run of course) on his screen in a task UI. For example when user is creating the third record he can refer to previous two that he has already created while performing that task.
I must note that we are using CE 7.2 so that we don't have access to BPM API. That's a limitation.
Any guidelines or ideas on that case will be highly appreciated.
Thanks in advance,
Peter

Hi Peter,
We have successfully implemented one such scenario. I hope you are using WDCs.
You can follow this approach:
1) Take ResultSet and ItemDetails WDC in wrapper DC application.
2) You can create record in ItemDetails and save it in MDM.
3) Retreive the record id of created record by ItemDetailsInterface.getRecord.getid
4) Set this record id in ResultSet's context i.e. RecordIDs.
5) Follow the same process again and you will have multiple records created. Also user can see the records created in the process.
6) While passing them, get the array of records from ResultSets context, you can read it and store it as a comma separated string context while passing to BPM.
7) In the, lets say, Approver screen, retrieve this comma separated stream of records and set again as a array in ResultSet of an Approver.
This way you can have multiple records created in a single process.
-Abhijeet

How to restrict customer records being displayed using 'sales_channel_type' criteria in customer search form at 11g?

OS: Linux
DB: 11.2.0.3
ERP: 11g
Hi There,
     I would like to create a new custom responsibility, which the responsibility is having access to Standard Customer Form (ARXCUDCI.fmb) , but I would like to make a restriction in the customer search form is that, everytime the responsibility user search by customer number, customer name, party name or what ever search field, I would like to limit to restrict further of searching criteria where SALES_CHANNEL_TYPE = 'RTL' is allowed to populate the customer records, there rest of customer records are not allowed to search out.
    This SALES_CHANNEL_TYPE column is from HZ_CUST_ACCOUNTS table.
    I have tried the Form Personalization already, but the customer searching form has too many fields for user to search, therefore form personalization will be putting all over the places in the form. Therefore I saw others recommended of doing "Custom DLL"...may I know for my scenario, how to I go about Customer DLL? or any other more effective solution?
   Appreciate if anyone can share your experience related to matter above.
Regards,
Lygine

Hi Lygine,
The personalization i sent you works in this way:
-It does not matter which field you choose to enter the query.
-If a record is found, when the form opens and the cursor hits the Customer Name field, the personalization looks for the content of the Sales Channel field.
-If the content of this field is different from the 'RTL' string, the form Customers form (ARXCUDCI) is cleared.
Independently from the field you fill to perform the query, is a record is found, the Customer Name field is the first the cursor hits when the form is opened.
Octavio

Customer Record Creation - XD01

Similar Messages

Maybe you are looking for