Need to export customer master data in a batch input file

Hello all,
I'm searching for a solution to export customer master data out of a R/3 system (Release 470).
The challenge is that the file must have the same structure like the file for batch input of customer master data (import file of the program RFBIDE00).
So, has anybody an idea, if there is a standard tool to get such a file? Or has anybody developed a report creating this structure by his own?
Thanks for your help,
kind regards,
Dietmar

Hi,
I have also come across the same problem as above. There is a standard program RFBIDET0 which has to be customized to get the file which can be uploaded to RFBIDE00. Do anybody come across this kind of problem before and have a program already. It will be of great help, if you can forward the program or guide.
Regards,
Vishnu Priya

Similar Messages

Getting error while uploading gl master data using LSMW batch input data

Hi Experts,
I am getting error while uploading the GL master data through lsmw using batch input recording.
After completion of all steps at the time of running batch input session error i am getting is "maintain EN language discription"
and Pls tell me is it possible to upload transactional data using lsmw? if yes pls explaing briefly.

Hello,
Kindly post in the FI forum to get a better response.
Regarding the issue you might check whether the correct column is being picked up where you have maintained the description.
Kind Regards // Shaubhik

Need to Create Customer Master Data under Multiple Sales Areas

Hi Gurus,
         My requirement is to create a customer under multiple sales areas by processing the Inbound Idoc function module "IDOC_INPUT_DEBITOR"( After generating Outbound Idoc and outbound is processed successfully).
         But, when I am trying to send the multiple sales areas information in segment "E1KNVVM". It is creating the customer under first sales area filled in first E1KNVVM segment and it is giving error that "Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1" and it is not creating the customer under other sales areas.
        Following are the details of the Outbound Idoc which I have processed.
        Idoc Basic type : DEBMAS06
        Message          : DEBMAS
        I have filled required fields in E1KNA1M and E1KNVVM segments. But filled E1KNVVM segments twice with different sales area data.
      Please help in solving this problem?

is it really just one IDOC?
I have never seen that SAP just does a part of one IDOC.
the structure of DEBMAS ist like this:
E1KNA1M
--E1KNVVM
E1KNVPM
E1KNVDM
E1KNVIM
--E1KNB1M
which means for your example it should be like this
E1KNA1M
--E1KNVVM
E1KNVPM
E1KNVDM
E1KNVIM
--E1KNVVM
E1KNVPM
E1KNVDM
E1KNVIM
--E1KNB1M
and in this case I am very certain that it would never just process and create the part for one sales area.
Maybe your customer already exists from ealier tests with just one sales area.
Display your IDOC in WE02 or WE05 and make sure you have a value in name1 field

How to upload different views of customer master data using LSMW-IDOC

I need to upload customer master data using LSMW Idoc method for my client. Now customer will have different views like main view, Sales data, Company code data, Partner function data etc. And except main data all other data can be multiple for each customer. We are going to upload data from tab delimited .TXT file. Should I propose different LSMW for upload different views for the customer from different .TXT files? or we can upload all the customer related data (like main view data and partner function data )from a single .TXT file. Kindly suggest which one in convenient and how we can prepare the data file in both cases.

convinient is the method that you can handle.
but as the guy who loads the data you have to load the data like they are available, like it is convinient for others to prepare the data.
In general there is no problem to use an IDOC method to load a customer master with multiple comany codes and several sales orgs in one shot.
the data can be in one source file, but need then to be maintained in a certain way
Example1: all data in 1 structure
GD1 - CC1 - SO1
GD1 - CC2 - SO2
GD1 - CC2 - SO3
in this case the GD (general data) is redundand in each line which has different Company code data or different Sales Org data
Example2: all data in 3 sturcures but one file
GD1
.CC1
.CC2
..SO1
..SO2
..SO3
Example3: data delivered in 3 files - you join the files in LSMW, they must have a common identifier like the old customer number in the beginning of each file
FILE General data:
GD1
GD2
GD3
file Compamy code data:
CC1
CC2
CC3
file Sales org data:
SO1
SO2
SO3
LSMW is flexible and can handle each of this scenarios, are you flexible too?

Customer master data, Materials master data integration Integration in XI

Dear Experts,
I need your help in the following cases
We are integrating MDM 5.5 to ECC6.0 via XI 3.0.
1. I am not able to understand exactly what interfaces, mappings, integration scenarios from sap delivered MDM Business Content need to use for integrating customer master data , Materials from MDM 5.5 to ECC 6, As we are using standard content.
2. What idoc types needs to be created in ECC for these two scenarios ( customer, material /products).
3. Is there any way to see the field mappings easily in XI , as the MDM standard business content for XI used xslt mapping programs .
Could you please give helping hand with step by step procedure for customer, material integration in XI.
Help is rewarded and greatly appreciated.
Best Regards.
nag.

Hello Nag,
1. I am not able to understand exactly what interfaces, mappings, integration scenarios from sap delivered MDM Business Content need to use for integrating customer master data , Materials from MDM 5.5 to ECC 6, As we are using standard content.
If you import Business Content of MDM 5.5. You should easily figure out that by looking at the Message Mapping for DEBMAS03 IDoc.
.2. What idoc types needs to be created in ECC for these two scenarios ( customer, material /products).
No need to create any Master IDocs in SAP system. You can find them with the name DEBMAS (For Customer) and MATMAS (Material).
3. Is there any way to see the field mappings easily in XI , as the MDM standard business content for XI used xslt mapping programs .
If you really want to know how the XSL Mapping is programmed. You can export the XSL from XI and open it in standard XML /XSL editor (say Stylus Studio ) to see how the output is programmed
Regards,
Ashwin M
Dont forget to mark helpful answers

How to use the customer types in customer master data

how to use the customer types in customer master data?
menu path is Extras -> account group info -> customer types

hi,
This is an option given to you to choose (if you need to) the way you perceive this customer.Here you get options including ompetitors,Salespartner, prospect,
default sp ,consumer.
See it helps you to differentiate between prospect(which you may use for quotation or inquiry purpose)Sales partner and the competetor.
I hope this clarifies your quiery.Reward points if so.
Thanking you,
Best regards,
R.Srinivasan

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.

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

Error during create CR for MDGC "Enter a relevant role for creation of customer master data"

Hello Experts,
I am unable to create a Customer CR in 'MDG 6.1 Customer UI' , the UI throws an error saying "Enter a relevant role for creation of customer master data".It looks like it is expecting me to mention the BP role ( like FLCU01 Customer or FLCU00 FI Customer ) , but I don't see that BP role section in the Customer UI to mention .
While creating the vendor CR , I am able to enter the BP role ( like FLVN01 vendor or FLVN00 FI Vendor ) in the UI BP Role section.
Following are the UI's for Customer and Vendor
Customers BS_OVP_BP: BS_OVP_CU > OVP: BS_CU_OVP - I do not see BP role section here.
Vendors BS_OVP_BP: BS_OVP_SP > OVP: BS_SP_OVP - This is working fine , I see BP role section here.
Please advice what I am missing here , what should I do for the successful CR creation . Should I change the UI for Customers or do I need to do anything in CVI configuration.
Thanks,

Hi Abdullah,
You were right in the first place the UIBB is missing , the UIBB 'Role' was present in the 'Search Customer' page but not available in the 'Create Customer CR' page , so I created the 'Role' UIBB again and was able to create the CR now . Not sure how it got deleted in the first place , is there any options where we reset the UI screen to the default initial configuration
But after approving the CR , only the Business Partner BP is getting created and the Customer is not getting created . Not sure what might be the issue now. Is there any config that tells to automatically create customer when BP is created. I was able to create Vendor using the create Vendor CR before.
Thanks

Copy mode of payment from customer master data to sales order,

Hi Gurus,
Hope all is fine.
I have a small doubt. If we want to transfer the mode of payment from customer master data to sales order, do we have to use Exit- MV45AFZZ.
Can't we transfer the data without the exit?

Hi,
I have tested this in sand box.Thought the customer master is having payment method ( payer ) ,It is not copying from customer master to sales order but if you maintain manually in sales order ,it is copying into billing document level.FYI see below snap shot.
Note:If you want it from customer master into sales order,may be you need to take help of abaper on this.
BR's,
Naren

Customer master data creation

Hello Folks,
I need some confirmations please :
1 . customer master data (cmd) is created at account group and company code level.
So, if a customer is a customer of 3 company codes of a company , 3 customer master records needs to be created where the number range of the customer code being the same and the company code is different and the account group remains the same?
2. A customer can buy from any sales area combination in company code, but only 1 customer master record is created ? If so, 1 customer code is for any Sales areas for a customer?
So, Sales area is data fields in a customer master record and only account group and company code and the customer code are key fields in the definition of customer master record?
Please confirm for me. Thanks.
regards
Ravi

Hi Ravi,
_Extension of the CMR_
a.     If the Customer is buying from under 1 Company Code and multiple Sales Areas then you need to extend the CMR for all sales area.
b.     However when the sales areas change the Customer No., General data and the Company code data does not change
While Extending the CMR by changing the Sales Area:
a.     In XD01 or VD01 enter the Account Group of the customer which is to be extended
b.     Enter the customer no.
c.     Enter the New sales area
d.     The system will take you directly to the sales area data
e.     The Company Code data and the General data cannot be chosen.
While extending the CMR for different company codes:
a. In XD01 or VD01 enter the Account Group of the customer, which is to be extended
b. Enter the customer no.
c.     Enter the New Company code
d.     The system will take you directly to the Company Code Data
e.     The Sales Area Data and the General data cannot be chosen.
While extending the CMR for different company codes and sales Areas:
a. In XD01 or VD01 enter the Account Group of the customer, which is to be extended
b. Enter the customer no.
d.     Enter the New Company code
e.     Enter the New Sales Area
f.     The system will take you to the Company Code Data
g.     Then you can go to the Sales area data.
h.     The General data cannot be chosen.
Tables Used for CMR:
Table Name     Used For
KNA1         General Data
KNVV         Sales Area Data
KNB1         Company Code Data
Q. Why are there 3 Data Groups or 3 different Tables for one customer?
Ans. Since the Customer is expected to buy in more than one sales area and also in some cases in more than one Company code different data sets need to be maintained but however some data remain same, so to avoid data redundancy you maintain 3 different tables.
Hope this helps,
J Nagesh

Sales condition in customer master data

Hi,
We need to show in the customer master the the price conditions of the customer. This prices conditions depends on the material and on the customer type but basically we need to show the standar discount the customer has on each material class. For example, er need to show for customer 1 that he has 40 % discount in material class A and 35 % discount in material class B.
I haven't seen how to show price conditions y customer master data, if we can't read from R/3 we can upload it from a file.
Any solution is welcome.
Thanks and regards.

Thanks Luis, Rakshith,
I'm going to upload the conditions (or try at least), I have another question about this. You said that the conditions which has Sold_to party in the key would be shown, we have conditions which have in the key fields from the customer, like price group. Can this conditions be shown too?
Best Regards.

Problem in Customer Master data

Hio friend
I need some examples what type of problems or issues or ticket comes at clients in Customer Master data maintenance. If possible send some scnerios with solution also how it was solved.
Thanks
Raj

Hi,
1. 'Entry GVK 0000140000 does not exist in SKB1 - check your entry'.
Solution :Reconcilation account 140000 has to be created in GL Master Data - T.code FS00.
2. Customer is Vendor and Vendor is customer.How do you see the net profit?
Solution : In customer Master , you have to input vendor master and in vendor master, you have input customer master, tick the clearing with customer box on the vendor record and the netting with vendor box on the customer record, Payment can be made by Automatic Payment PRogram.
Additionally search SDN with the search word customer master, you will find losts of real time problems with solutions.
Please let me know if you need more information.
Regards
Sridhar M

Unable to extract Customer Master data from MDC

Hello,
We creating an MDM-XI-ERP2005 Customer scenario. We want to work with all bussiness scenarios (not customizing scenario).
First I'm trying to extract Customer Master Data from EP 2005 using MDM_CLNT_EXTR.
I have created a New Variant which properties are:
Variant: CUSTOMER_TOTAL
Description: Send all customer data to MDM
Extraction Object: CUSTOMER_EXTRACT.
Target System: PI7.
But, the display jobs shows the following error: Could not determine recipients for message type MDMRECEIPT. Job cancelled after system exception.
We need to focus the problem. We have done the following ALE configuration.
SALE transaction:
In Basic Settings -> Logical Systems -> Define Logical System we have add the following logical systems:
              EUS100
              MDM: Master Data Management
              PI7: Process Integration 7.0
WE21:
Transactional RFC -> PI7, IDOC record types SAP Release 4.x
RFC destination: SAPSLDAPI
BD64
New Model -> PFMC
Add message type: Model iview: PFMC
                             Sender: EUS100
                              Receiver: PI7
                             Message Type: DEBMDM
WE20 transaction shows:
Partner profiles -> Partner Type LS (logical system)
                    PI7: Outbound parmtrs. DEBMDM, SYNCH.
Any idea will be very helpful,
Thanks in advance
Marta.
Edited by: Marta Sánchez on Jul 9, 2008 12:34 PM

Sorry because I made a mistake in my previous message. ALE seems to be correctly configured. I'll try to update correctly my current situation:
In WE02 I can see al IDOCs that I'm trying to send to XI. All them have the IDoc Status = 3 (Data Passed to Port OK) instead of 12 Status Dispatch OK :(. So, It seems an tRFC error.
SM58 shows me more trails: "Basic type 'DEBMDM06' is unknown"
before that I have done the following steps at SAP ERP:
    1. WE21: I have created a PI7 port with 700PI70CLNT RFC.
    2. SM59: I have checked successfully 700PI70CLNT RFC connection.
    3. WE20: I have created a PI7 Partner Type LS with the following inbound and outbound parameters: DEBMDM and MDMRECEIPT.
    4. BD64: I have created a Distribution Model with DEBMDM and MDMRECEIPT message types.
and at SAP PI:
     5.IDX: Port: SAPEUS. Client: 111. RFC Destination: PI7.
     6. technical and business system for sender SAP system(System Landscape Directory)...
- Maybe some of the previous steps is not correct....
- Is RFC Destination = PI7 is correct in step #5?
- Is also necessary to configure more steps in PI system like RFC destinations or Transactional port?
- I have read that is neccessary to check that the option "transfer idoc immediately" in we20. How?
Please any idea will be very helpful.......
Thank you!
Best regards,
Marta.

How to maintain the e-mail field in customer master data

Hi to all,
i need to do the field e-mail obligatory in the customer master data when i create a new customer(transaction FD01), but in customizing and in the user exit SAPMF02D this field is not present in the various structure/tables enabled (the table is ADR6 but not is in the list).
How i can do? Thanks in advance for any reply!!

Dear,
Check the Functional Module through SE37 : BPAR_M_FI_MODIFY_EXECUTE_NEU
And also check the Note: 703094.
Hope it will solve.
Regards,
Kishore K
Edited by: kishore babu on Dec 21, 2009 3:38 PM

Need to export customer master data in a batch input file

Similar Messages

Maybe you are looking for