Customer Master data.. Bank Account No.

Hi
In customer master data ( XD01) > General Data > Payment Transaction > Bank Details 
we maintain. Bank key , Bank Account and other details.
my concern is , by maintaining customer bank account number in customer master data, what are the integrated effects to FI > Bank Accounting > House Bank ?  ( On Invoice Creation, Payment Receipt , Credit note, Debit note all FI Transaction ).
Actually we want to use it just for information & reporting purpose.   NOT  FOR ANY AUTOMATIC RECEIPT \  Integration to FI > BANK Accounting \ House Bank.
Thanks

Hi.
'customer master data, what are the integrated effects to FI > Bank Accounting > House Bank ?' House bank not linked with Customer master data(only if customer affiliated company).
Bank details in customer could be used eg for invoicing(printing form)

Similar Messages

  • Vendor master data - Bank Account field len too short

    Dear Expert,
    My client trying to create a vendor when she maintains the Bank account number under the bank detail and she encounterred error message "Entry in field Bank Acct. No is longer than 10 characters" where can I extend the field to 11 characters?
    thank you

    Hi,
    Maximum length for bank account number is 18.
    The error message is because, for the country, standard SAP allows only 10 chars.
    To change this,
    1. Go to t-code OY17
    2. Change the bank account number /bank number length accordingly.
    Regards,
    Sridevi
    Edited by: Sridevi on Jul 31, 2009 9:45 AM
    Edited by: Sridevi on Jul 31, 2009 9:45 AM

  • Change account groups in vendor/ customer master data

    Hi,
    Do you think is possible to change account groups in vendor/ customer master data?
    Thanks

    Hi,
    Good evening and greetings,
    Changing the account groups will redetermine the Reconciliation account, which will be creating a chaos during Audit Reconciliation. But if there is a requirement, please go through the following link
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f534545a11d1a7020000e829fd11/frameset.htm
    Please reward points if found useful
    Thanking you
    With kindest regards
    Ramesh Padmanabhan

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

  • 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 has 2 bank accounts, which one in payment run?

    Hello,
    I have searched the community, but haven't found the answer, so I added this discussion:
    We have customers with more than one bank account.
    When we do a payment run (F110), it always selects the first account in the list (tab payment transactions in general data customer master).
    How can we arrange that the second account (another than first) is being selected/used in the payment run?
    Is there a setting in the customer master?
    Thanks!

    Hi there,
    In customer master data, tab payment transaction, use the field Bk.typ.
    it's used to determine the bank accnt see SAP help text
    Partner Bank Type
    Key you enter in the line
    item to specify which business partner's bank the system should use.
    Procedure
    In the business partner's master record:
    If several bank accounts exist in a customer or vendor master record, you can
    assign different keys for these accounts.
    In the item:
    To use a particular bank of the business partner for the payment of an item,
    enter the appropriate key in the item. The payment program then pays the item
    via the business partner's predefined bank.

  • Modifying Customer Master Data - Internal error - Message no. F2531

    Hi experts,
    We have updated the bank details of a specific customer master data. Now when we display it, specifically in bank details, we get the following error message:
    Internal error: FI_TECH_ACCNO_READ_TRY SY-SUBRC <> 0
    Message no. F2531
    Does anyone know what it means? Can anyone help me?
    Thanks in advance.
    Best regards,
    Andreia Nascimento

    Hi Andrea,
    This message is a SAP standard message and it is not modyfiable in OBA5. The one reason for this may be you are trying to enter bank account which programme is not able to find. If this is not in your case you can take help of abaper and debugg the program.
    Regards

  • Retrieving Dunning Clerk's name from Customer master data

    Hi all,
    I have to retrieve the dunning clerk's name in report ZRSD0001 (Customer Master Data Report).
    There are standard methods to call the subroutine to retrieve the texts for some field like the bank statement text:
    PERFORM TEXTFIELD_CALL(RSAQEXCE) USING   KNB1 'KNB1' 'XAUSZ' TEXT_KNB1_XAUSZ.
    This works perfectly. But it fails when I use the same method to retrieve the dunning clerk's name:
    PERFORM TEXTFIELD_CALL(RSAQEXCE) USING KNB5 'KNB5' 'BUSAB' TEXT_KNB5_BUSAB.
    So any other standard subroutine that I can use instead of using a sql statement myself ?
    Thanks.

    Hi,
      Why do you want to use a standard routine for this?? If you know the customer number(KUNNR), Company Code(BUKRS) and Dunning Area(MABER) You can get Dunning clerk(BUSAB) from KNB5 and using this BUSAB and BUKRS you can go to table T001S to get the SNAME which is Dunning Clerk's name.
    Thanks,
    Kavitha

  • 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

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

  • 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

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

  • Not able to create customer master data with country code US

    Hey All,
    I am not able to create customer master data in the Transaction Code XD01/FD01 with the country code as US.
    The error message for the same is NO JURISDICTION CODE COULD BE DETERMINED. I have checked the tax code settings but could not locate the problem.
    Request you to provide me with a solution.
    Thanks & Regards
    VK

    Hey all,
    I have checked the field in the account group(OBD2) but its in optional status
    and also checked the country settings for US in the transaction code OY17 still the same error message, but when i tried checking the settings for a differnt company code's customer data base i can see that there is a number mentioned in the address tab under tax jurisdiction feild (beside time zone) which is not populating for this company code.
    so, do anyone know where exaclty we mention this number so that it populates in that field of address.
    hope am clear
    hope to receive  a solution
    thanks & regards
    vinila

  • Change Message Control for Customer Master data

    Hi Friends,
    I have to choose/populate a message when the user is about to create an already existing customer.
    In SPRO --> Financial Accounting --> Accounts Receivable and Accounts Payable --> Customer Accounts --> Master Data --> Preparations for creating customer master data --> "change message control for customer master data" ...
    OK...
    When u click this it goes into Change View "message control by User" Overview screen wherein u can insert new messages and texts and the type of message ....
    Now .....
    I want to display the 145th message (F4 help of the Message column) ..... it picks up the text "Customer found with same address;check"..... with Online mesasage type 'I' and batch type 'I' and with standard type '-' ..
    I want to have the same message with message types 'E','E', and 'I' respectively.......
    How is this possible (or) what should i do to meet my requirement :-|
    Expecting ur answers
    Thanks in advance ........
    Cheers,
    R.Kripa.

    Hey yes it is not possible (as of now
    I ve met the requirement by just using message statement in the program itself ............
    My requirement is met but still if anyone knows about this do answer / reply
    Thanks
    Cheers,
    R.Kripa.

  • Missing Tax information of Customer Master data

    Dear all,
    I have an error with Customer Account Group. I create a customer account group as Z001 (Domestic customer). After that, I go through Financial Accounting - Account Receivable and Account payable - Customer Account - Master Data - Preparation for Creating Master Data -Define Account Group with screen layout (customers) (also with Define Screen Layout per activities). And for Control Tab, I set all items are optional. But when creating Customer master data for this group, when going to SALE AREA DATA, Tab BILLING DOCUMENT, I found that the Tax information part is missing.
    I try to set all items are optional, but can't resolve this problem. Can you help me ?
    Thank you very much for your help,
    Sylvecat.

    Hi
    Goto TCODE : OVK3 and maintain the Customer Taxes
    Path : SPRO > Sales and Distribution > Basic Functions > Taxes > Define Tax Relevancy Of Master Records
    VVR

Maybe you are looking for