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.

Similar Messages

  • Delete Customer Master Data OBR2

    Hi
    I'm using LSMW to import data. I would like to delete it afterwards. Transaction OBR2 which is in spro Financial Accounting (New) -> Accounts Receivable And Payable -> Customer Accounts -> Master Data -> Delete Customer master data.
    But it does not delete the sales are segment, it also does not allow me to delete general data if sales segment exists.
    Can anyone please let me know if there is another way around this? Any other way to delete this test data???
    Thanks in advance

    Hi
    Please go through the SAP documentation on how to perform deletion of customer master data.
    This may help you in executing the function correctly.
    <b>Delete Customer Master Data</b>
    In this activity, you delete the master records for customers by using a program. Only use this program in the test phase.
    Note
    The company code for which master records are to be deleted, may not yet be flagged as productive.
    Only master records for accounts which do not have any transaction data may be deleted.
    Requirements
    The general customer master data is only deleted for customers who are not also created as customers in Sales and Distribution.
    Activities
    Delete the master records for the required company codes.
    Additional information
    Refer to the SAPF019 program documentation for further information on the program.
    Deleting Master Data
    Description
    This program deletes master data in Financial Accounting and is designed for preparing the system for productive startup. It deletes:
    •     Customer master data
    •     Vendor master data
    •     G/L account master data
    You can run this program in three different ways:
    1. Deleting general master data (in G/L accounts in one chart of accounts)
    2. Deleting master data dependent on company code
    3. Deleting general master data and master data dependent on company code
    For each deletion run, you can specify whether or not the system should take into account the deletion flag in master records ("Delete per deletion flag only"). If it takes into account deletion flags, it uses the following standard logic:
    Option 1: The "All areas" deletion flag must be set.
    Option 2: The "Specified co. code" deletion flag must be set.
    Option 3: It is sufficient to have the "All areas" deletion flag set.
    Note: Deletion blocks are always checked at general data and company code-dependent data level. If there is a block at company code-dependent data level, then the general data is not deleted either. The deletion block takes precedence over the deletion flag.
    General master data in Financial Accounting can also be used in other SAP applications:
    •     Customer master data in Sales and Distribution
    •     Vendor master data in Purchasing
    •     G/L accounts as primary cost elements in Cost Accounting
    The program deletes the following:
    •     Change documents for master data
    •     SAPscript text files
    •     The following data is deleted for customers:
    o     General master data
    o     Bank details
    o     VAT registration numbers
    o     Addresses
    o     Classifications
    o     Credit management: across control areas
    o     Credit management: centrally
    o     Unloading points
    o     Tax indicators
    o     Contact persons
    o     Licenses
    o     Partner function limit
    o     Shipping data
    o     Master data in the company code
    o     Dunning data
    o     Linked data
    •     The following data is deleted for vendors:
    o     General master data
    o     Bank details
    o     Contact persons
    o     VAT registration numbers
    o     Addresses
    o     Classifications
    o     Master data in the company code
    o     Dunning data
    o     Linked data
    •     The following data is deleted for G/L accounts:
    o     General master data in the chart of accounts
    o     Names in the chart of accounts
    o     Key word list in the chart of accounts
    o     Master data in the company code
    o     Sample accounts, if selected
    For customer and vendor contact persons, the addresses are not determined from central address management until the actual runtime. Therefore differences can arise as to the number of addresses in the detail log between the test run and the update run.
    Automatic worklists for customers and vendors are also deleted with the general master data. Matchcodes are always deleted.
    You may have to fix the number ranges after the program run.
    The system makes changes to the database in the update run only. It will then also write a system log entry for documentation.
    Requirements
    General master data can only be deleted if no other application makes reference to the account. Use the resetting programs from
    •     Sales and Distribution (customer master data)
    •     Purchasing (vendor master data)
    •     Cost Accounting (G/L account master data)
    If you want to delete only general master data, master data dependent on company code cannot have been created in Financial Accounting.
    If you want to delete master data in a test company code, master data dependent on company code cannot have been created in any other company code except the test company code. The productive indicator cannot be set for the company code.
    If a customer or vendor is referenced by another customer or vendor (for example, via fiscal address or alternative payee), you can only delete the referenced master record by deleting the referencing master record at the same time.
    Furthermore, you can only delete master data in Financial Accounting if no transactions have been posted to the corresponding accounts. If there are transaction figures in one of the selected accounts, you have to manually access and run program SAPF020 (reset transaction data from a company code) before you can delete that account.
    Output
    The log lists every table which is processed in the program selection.
    You can also create a detail log for each account type to find out why certain data cannot be deleted. The detail logs show you what other company codes and applications use the data and how customers and vendors are linked to one another.
    Note
    Since deleting or displaying even smaller volumes of data can result in runtime problems, you should run this program as a background job. Currently, the program individually deletes matchcodes for each master record in the database. Several match code IDs refer to each matchcode. This can place a considerable load on the database.
    You cannot delete transaction data in individual accounts.
    Important: The archiving programs in Financial Accounting are designed for the productive system.
    If you are running this deletion program for the first time, then you must start program SAPF047 before deletion in order to generate link information.
    I hope this may be of help to you
    Good Luck
    Hari

  • Customer master data copying from one sales order to other

    Hello Friends,
    I have requirement on customer master data maintenance, When ever i create a customer in one sales area it has to copied automatically to other sales area.Even if i change also system should replicate the changes to same customer in other sales area.
    How can i achieve this?
    Please help me

    Hello,
    Create Common Distribution Channels & Common Divisions.
    This will make sure that Master Data you create for one Sales Area is valid for other Sales Areas also...
    Proceed here:
    IMG - Sales and Distribution - Master Data - Define Common Distribution Channels
    IMG - Sales and Distribution - Master Data - Define Common Divisions
    Hope this helps,
    Thanks,
    Jignesh Mehta

  • 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

  • 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.

  • XD01 assertion failed error while updating customer master data

    Hi Guys,
    This is an error when I use transaction XD01 to create customers accounts, If you have any ideas do let me and we'll try it....
    The error does not let an BDC or LSMW progress as well. There are also no recent sap notes on the same.
    The error is as follow
    ASSERTION_FAILED
    Short text
    The ASSERT condition was violated.
    What happened?
    In the running application program, the ASSERT statement recognized a
    situation that should not have occurred.
    The runtime error was triggered for one of these reasons:
    - For the checkpoint group specified with the ASSERT statement, the
    activation mode is set to "abort".
    - Via a system variant, the activation mode is globally set to "abort"
    for checkpoint groups in this system.
    - The activation mode is set to "abort" on program level.
    - The ASSERT statement is not assigned to any checkpoint group.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    The following checkpoint group was used: "No checkpoint group specified"
    If in the ASSERT statement the addition FIELDS was used, you can find
    the content of the first 8 specified fields in the following overview:
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    I have a company code CG01 with sales organization CTS0 and I want to transfer or extend all the customer master data to another company code CG03 with the sales organization CTS0
    The things that I have tried and not work
    using xd01, fd15, fd16, fd01, does not wok and gives the error as above
    The things that I have tried and it works
    Change the sales organization from CTS0 to CTS1 I am able to post the customer master data, using any of the above tcodes and it does not give any error, however the client wants to sales organization to remain CTS0
    So please give me any ideas as per your experience as this transfer of master data has to happen by Monday, else I'll be fried by my boss
    My number is 9820029197
    Will also keep you'll posted on any developments on this case,
    Ronan Pinto

    >
    > Firstly I am from SAP FI, so totally new to SAP SD
    >
    Then you are best person to explain the reason on why the same sales organization, can't be assigned to different company codes. When a sales is done through one sales organization, then will the  profit/loss be accounted in different company codes. Is it legally allowed in the country, where your customer is doing business? How you are going to develop the  balance sheet? Again being the FI person, you are best judge to provide the details to your customer and not a SD guy.
    >
    > 1) How did the system not give an error while putting the data inside CG02 with sales organisaton same as CST0 same as in company code CG01.
    >
    I dont see any other method than removing the assignments in the backend and uploading the data. You can consult a Basis person to find the  change logs for the assignment table. In my opinion, removing the sales organization from a company code assignment just for loading a customer master data and then reassigning to original sales org is  a crooked method and/or not a professional method.
    >
    > 2) Since I have limited experience of SD, If I have to convince my client about the use of CTS1 sales organisation or a unique sales organisation against his argument that it worked for company code CG02, how should I do it.......
    >
    As explained above, how the sales will be accounted  in different company codes (even if the system allows  to assign the same sales org to different company codes)?
    I would recommend you to post this question in FI forum (after closing here) to check what are the legal implications for this scenario.
    Regards,

  • What is a shipping condition in customer master?

    Kindly give some info about the shipping condition which we use for shipping point determination. Where and how it is configured in customer master?

    shipping conditions:-
    For example, it might have been agreed with the customer that the goods are to be
    delivered as soon as possible.Thus 'How are the goods being shipped?'
    <a href="http://i164.photobucket.com/albums/u40/a_la_bakwaas/1.jpg">On the basis of shipping condition 01</a>, the loading group CRANE and the plant 0001, the system
    determines shipping point 0001 for the item. Instead of this shipping point, you can also select
    shipping points 0002 and 0003 if, for example, you know that shipping point 0001 is out of
    operation or does not have the capacity to deal with the item at the time when delivery is to take place.
    The Why:-
    Criteria for <b>Route Proposal</b> in the Sales Order
    Determining the route in the sales order depends
    on the following factors:
      Country and departure zone of the shipping point
      <b>Shipping condition</b> from the sales order
    For example, it might have been agreed with the customer that the goods are to be delivered as soon as possible.
      Transportation group from the material master record (Sales/Plant Data screen) You can use the transportation group to group together goods with the same
    characteristics (for example, bulky goods or goods that must be transported in refrigerated trucks).
      Country and transportation zone of the ship-to party (Control screen in the customer master
    record)
    and the <b>configuration requirements</b> involved are as follows :-
    you have to maintain the shipping conditions in the Customer master record under 'Shipping'["sales area data" tab],shipping point etc.
    imglogistics executionshippingBasic Shipping Functions-Shipping Point and Goods Receiving Point Determination--Define Shipping Conditions by Sales Document Type
    also
    Please maintain the appropriate shipping points for the combination of Shipping Conditions + Loading Group + Plant in the T-code: OVL2
    for defining a different shipping condition--> go to Tcode OVL3 i.e picking location determination then have different determinations i.e same Shipping Point+ Same Plant+ Different Shipping Conditions+Different Storage Location.
    and
    SPRO --> Logistics Execution --> Shipping --> Basic Shipping Functions --> Shipping Point and Goods Receiving Point Determination --> Assign Shipping Points
    Shipping Condition (from Sales Order Type or Customer Master data) + Loading Group (from Material Master) + Delivering Plant (from Customer Material Info or Customer Master Data or Material master data) = Shipping Point
    hope this helps.

  • Demo - Extraction of Customer Master Data from SAP R/3 ECC6 to MDM5.5

    Hello,
    I am new to MDM . Would appreciate if someone can give a solution to the below request.
    We are doing a demo project in our Company to extract all the master data related to SALES cycle. We are doing an extraction of Customer Master Data. Currently we have the unlicensed version of MDM and very soon we will get the licensed version.
    We have the Customer Master Repository created in MDM Console. The IDOC type we are using is DEBMDM05.
    Is there a easy way to map the fields of IDOC to the MDM Repository. Right now we are doing a manual process of comparing the IDOC fields and MDM Repo in an excel but this is tedious and time consuming.
    Can anyone suggest an easier way to identify so that we know which fields match correctly.
    Thanks
    Leena

    Hi Leena,
    First of all you have 2 options to generate IDOCs from SAP R/3 system
    1.mdmgx>one IDoc per record
    2.mdm_clnt_extr>for generating single IDoc having entire set of records.
    Secondly,if you want to get the data mapped automatically,you should use standard maps provided by SAP(Business Content).
    If at all you have created new fields then you should manually map those fields.
    If any other queries pl ask
    Reward points if found useful
    Regards,
    Pramod.

  • Customer Master Data Report

    Hi,
        How can i see the report of customer master data..
    Like for sale order it is va05...
    So how for a customer master data?
    Ashis

    Hi
    there is no standard report for that...
    go to SE16... enter table KNA1  -- for all customers please note this gives all customers in your client
                                        KNB1 -- for company code wise list
                                        KNVV -- for sales area wise list..
    after entering the table press enter ... give the selection criteria.. and execute.. this will fetch you the list of customers
    Muthu
    Edited by: Muthupandiyan on Feb 21, 2008 12:31 PM

  • 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

  • Question about terms of payment of company code tab of customer master data

    Hi:
    As I know there are two places to be maintained terms of payment of customer master data, one is in billing documents of sales area data tab and I understood it will default to the one in sales order when you create, another is in company code tab and I don't know what does it be used for? Could you advise?

    Hi
    Along with the payment terms, the reconciliation account number and the dunning procedure is set specifically for the customer to the particular company code.
    This would be the default data for all transactions specific to the customer in specific company code.
    If you extend the customer to another company code, you can have different recon, payment terms etc.
    All FI transactions are relative to these settings.
    In SD when you process, any changes to the particular customer can be modified and it will supercede the default settings of PT
    Reg
    Suresh

  • Impacts in COPA of changing material and customer master data

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

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

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

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

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

  • Change Logs for customer master data in 3.1 H version

    Hello All
    Are they any existing reports or change logs for viewing changes to customer master data in 3.1h version.  I want to be able to report based on changes made to customer master.
    I know there is a good report in 6.0 version for this- S_ALR_87012182.
    If I have to develop a custom program for this in 3.1h. Which table I should use? KNA1 or CDPOS.
    Any ideas will be appreciated.
    Hema.

    Hi,
    Please check the filter settings maintained for the adapter object CUSTOMER in R3AC1. The same filter settings can be referred in tables Table: CRMFILTAB (R/3) and SMOFFILTAB(CRM) as per srinivas's reply.
    Check the sales area of the customer maintained (Sales Area, Division, Distribution Channel etc.) and see if the current filter settings are restricting the customer from getting replicated in CRM. If everything is maintained fine then check for any failure Bdocs in SMW01 or SMW02.
    Regards,
    K

  • Report customer master data comparison

    Hello Experts,
    Using transaction SE38, we would like to run report customer master data comparison. Could anyone provide the report name?
    Thank you

    Hi Thanks.
    Can you provide report used for sales summary?
    Thanks again

Maybe you are looking for

  • How do you restore the "Last Date Played" notice in the iTunes window for songs?

    How do you restore the "Last Date Played" note in the iTunes window of playlists?  I lost this a couple of weeks ago, and had someone explain the steps to take (which are not on the iTunes "Help" menu).  Thanks.

  • Troubles playing certain AVI files on Intel Mac

    I have an Archos 604 WiFi and previously an Archos AV500. On my old PPC machines, the AVI files created by the Archos played just fine in Quicktime. However, I recently upgraded to all Intel-based Macs and I can no longer play the files. Here's the i

  • Lost my project (.fla) but got my (.flv)

    Hi everyone, my problem is that my old computer *exploded* last week and i was making a project for my dad so I lost my (.fla) file. But, I have an animation of that same project in (.swf) on my USB Key because I've exported it just before my compute

  • Annoyed. I thought it was resolved but it's not.

    I still can't view my broadband usage under the 'My services' section. I've requested help before on the forum and marked it as a solution because I was provided with a form to email off however having recieved my email from the BT help desk/complain

  • データの保存に関して

    数値データの保存に関して質問があります. 現在,compactRIOを用いて実験装置の制御を行っております. 数値データの保存には,スプレッドシートに書き込むを用いているのですが,パソコン上のファイルに直接書き込んでいるためか,サンプリング時間を5ms以下にすることができません. 1ms間隔でデータを保存したいのですが,どのようにすればよいのでしょうか? クラスタで一度1msで表示してから,クラスタ表示機からデータをコピーしてexcelに貼り付けるなどすれば,1msで保存することが可能なのですが