List Customer master Filelds (URGENT)

Dear All,
Can you Please provide the list of Customer master fields in one Place.
Please Do the Needful (IT IS URGENT)
Regards,
Vinay

Hi
Do the following.
Go to SE11 and put below tables one by one
KNA1                               General Data in Customer Master          
KNA1VV                             Customer Master View KNA1 KNVV           
KNAS                               Customer master (VAT registration numbers
KNAT                               Customer Master Record (Tax Groupings)   
KNB1                               Customer Master (Company Code)           
KNB4                               Customer Payment History                 
KNB4_AEDAT                         BW FI: KNB4 Extraction using AEDAT       
KNB5                               Customer master (dunning data)           
KNBK                               Customer Master (Bank Details)           
KNBW                               Customer master record (withholding tax ty
KNC1                               Customer master (transaction figures)    
KNC1_AEDAT                         BW FI: KNC1 Extraction using AEDAT       
KNC3                               Customer master (special G/L transaction f
KNC3_AEDAT                         BW FI: KNC3 Extraction usign AEDAT       
KNEA                               Assign Bank Details and Payment Methods to
KNEX                               Customer Master: Legal Control - Sanctione
KNKA                               Customer master credit management: Central
KNKA_AEDAT                         BW FI: KNKA Extraction using AEDAT       
KNKK                               Customer master credit management: Control
KNKKF1                             Credit Management: FI Status Data        
KNKKF2                             Credit Management: Open Items by Days in A
KNKKF2                             Credit Management: Open Items by Days in
KNKK_AEDAT                         BW FI: KNKK Extraction usign AEDAT      
KNKO                               Assignment of Cost Est. Number to Config.
KNMT                               Customer-Material Info Record Data Table
KNMTK                              Customer-Material Info Record Header Tabl
KNMT_REF                           Test - Search Help for KNMT             
KNOB                               Assignment of Cost Est. Number to Config.
KNVA                               Customer Master Loading Points          
KNVD                               Customer master record sales request form
KNVH                               Customer Hierarchies                    
KNVI                               Customer Master Tax Indicator           
KNVK                               Customer Master Contact Partner         
KNVL                               Customer Master Licenses                
KNVP                               Customer Master Partner Functions       
KNVS                               Customer Master Shipping Data           
KNVT                               Customer Master Record Texts for Sales  
KNVV                               Customer Master Sales Data              
KNZA                               Permitted Alternative Payer             
You will get all the needed fields.
Hope this helps. reward if helpful
kind regards
sandeep

Similar Messages

  • User Exit for managing Customer Master Texts- Urgent

    Hi All,
    I have a requirement in which the the Customer Master Central texts for certain text Id's are to be maintained in such a way via XD02 that whenever any changes are made and it is saved the changes become non editable and added with user date and time and then the user can add additional line of texts but cannot edit the earlier ones. So in this way the earlier texts are prevented from accidental deletion and any new addition has a stamp( User,date,time) to determine who changed it and when. I searcehd for any exit in the program but could find only one i.e. EXIT_SAPMF02D_001
    Is this requirement faesible in standard SAP?
    Now to me this exit could not serve any purpose.Please help.
    thanks,
    Manish

    Hi,
         use the following BADI's which will suitable for ur reqirement
    business Add-In CUSTOMER_ADD_DATA_CS .
    business Add-In CUSTOMER_ADD_DATA
    Regards

  • How to track changes in Customer master. Urgent Please

    Hi ,
    in VD03 for a Customer, when looked for changes made.
    Enviornment -> Account changes -> All fields.
    and then selected All changes, it shows me number of entries are deleted, I am wondering about why & how this happened and wanted to trace down,
    Can you guys help me,
    I looked at CDHRD table and found the entry but this is shown as BatcH..how can I trcae down, pls let me know.
    Thanks & Regards
    Sharat
    Message was edited by:
            Sharat Reddy Tekulapally
    Message was edited by:
            Sharat Reddy Tekulapally

    Hi
    You can go to tcodes VD04 or XD04 for individual customer
    For multiple customers, you can make use of the tcode OV51,
    Rewards pls.

  • Customer master list report

    Hi,
    1) How can I generate the customer master report?
    2) How can I generate the blocking/deletion customer mater list report?
    Can I get any standard report as mentioned above.
    Thanks
    Devendra

    Hi,
    Some of the Standard reports in SD are:
    Sales summary - VC/2
    Display Customer Hierarchy - VDH2
    Display Condition record report - V/I6
    Pricing Report - V/LD
    Create Net Price List - V_NL
    List customer material info - VD59
    List of sales order - VA05
    List of Billing documents - VF05
    Inquiries list - VA15
    Quotation List - VA25
    Incomplete Sales orders - V.02
    Backorders - V.15
    Outbound Delivery Monitor - VL06o
    Incomplete delivery - V_UC
    Customer Returns-Analysis - MC+A
    Customer Analysis- Sales - MC+E
    Customer Analysis- Cr. Memo - MC+I
    Deliveries-Due list - VL04
    Billing due list - VF04
    Incomplete Billing documents - MCV9
    Customer Analysis-Basic List - MCTA
    Material Analysis(SIS) - MCTC
    Sales org analysis - MCTE
    Sales org analysis-Invoiced sales - MC+2
    Material Analysis-Incoming orders - MC(E
    General- List of Outbound deliveries - VL06f
    Material Returns-Analysis - MC+M
    Material Analysis- Invoiced Sales - MC+Q
    Variant configuration Analysis - MC(B
    Sales org analysis-Incoming orders - MC(I
    Sales org analysis-Returns - MC+Y
    Sales office Analysis- Invoiced Sales - MC-E
    Sales office Analysis- Returns - MC-A
    Shipping point Analysis - MC(U
    Shipping point Analysis-Returns - MC-O
    Blocked orders - V.14
    Order Within time period - SD01
    Duplicate Sales orders in period - SDD1
    Display Delivery Changes - VL22
    Reward points if useful
    Regards,
    Amrish Purohit

  • Customer Master Price List

    Does anyone know if I can run a SAP transaction code that I can get a customer master price list report?  I need to see the customer, item #/SKU# and list price for all items sold to the cusomter.  Any help would be appreciated.  Thanks

    Hi,
    I don't think we have tcode for Customerpricelist but
    You can Get all items for the customer from KNMT Table. get the condition records(KUNMH) for these Materials from A091 table and finally get KBETR (price) based on the condition record from the KONP table. This would be termed as list price-
    Try to post the issue in respective forum ....
    Regards,
    Satya

  • URGENT:Creating customer master using Sd_Customer_Maintain_all

    hello all ,
    I am creating customer master using SD_Customer_Maintain_All.I will be thankful if somebody Can  tell me how to pass data to this function module.Better if somebody can provide code.
    Thanks.
    Sandeep.

    hello all ,
    I am creating customer master using SD_Customer_Maintain_All.I will be thankful if somebody Can  tell me how to pass data to this function module.Better if somebody can provide code.
    Thanks.
    Sandeep.

  • Sales orders/ invoice and customer master URGENT!!!!!

    how can i correct this problem...... customer is linked to the wrong customer master, customer is supposed to be a canadian customer but linked to US customer master? in terms of currency
    Also when the Sales order and Invoice was created for this customer they were inoviced in US dollars and not in Canadian Dolllars how do i reverse change currency from US to Canadian?
    Does this mean that the sales order has been linked to the wrong customer master?

    hI,
      In this case if the invoice had not posted to A/C use vf11 and cancel invoice.and use vl09 and riverse pgi and delete the delivery and by going to VA02 delete order.
      since u r saying that this customer falls under canadian customer while crweating CMR select A/C group of canadian customer then check all the critical fields of inco terms,payment terms,currency as per the standard and follow the subsequent sales process.
      cross check the sold to party details weather invoice had made against proper sold to party or not?if not just cancel invoice and subsequent documents.
      if the material had already dispached and you find there is any difference in total invoice value,create accordingly the needed Credit memo or debit memo with the proper reason.
    later as a permenent solution mark this CMR for deletion and create new CMR with proper accounting group.

  • Customer Master - ADRNR field details.

    Hi SDiens,
    This is regarding Customer Master data.
    Use T-code "SE16" then enter Table Name "KNA1" to see values for any particular Master record for eg. 1000.
    In this you will find some Values in field "ADRNR, MCOD1, MCOD2". whereas if you open the same record with "XD02" you cannot see this values.
    Even I am not entering this vause while creating records using "XD01". Can someone explain where can I see this Values.
    Matter urgent.
    Helpful answers will be rewarded.
    Cheers
    RC

    Hi,
    I looked in to this issue and got this information sto you please go through ADRNR number is the number provided internally by the system.and the remaining 2 fields MCOD1, MCOD2 are there in General data tab.
    Address number
    Internal key for identifying a Business Address Services address.
    For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.
    Business Address Services
    I. General
    You can manage addresses conveniently using a standard function module interface with Business Address Services. There are interfaces for maintenance with or without dialog and an address maintenance transaction.
    Address attributes
    An address in Business Address Services is a complex attribute of a primary object which saves only the reference to the address key. (In certain constellations, controlled redundancy is possible).
    The address management distinguishes between addresses on the basis of time dependency and international formats.
    The database structures allow for the date-dependency of addresses, but all function modules currently use date-independent addresses (the default validity range is 1.1.00001 - 31.12.9999).
    Address types
    Addresses are distinguished according to the application context in which they are used:
    "Normal" addresses (Address type 1): This type of address can either be associated with an application object or be on its own.
    Typical examples are the addresses of organizational units (for example, company code, plant), delivery address, functional location, and so on.
    Such an address is identified in the DB by a 10-digit address number.
    Examples: company code 0001 has address 4711
              customer MIKE has address 5678
    Private addresses of persons (Address type 2): These are addresses which are assigned to exactly one natural person, with extended attributes compared to the normal addresses (title, part of name, etc.) for the person. The person with the address-relevant attributes is an independent object, which is maintained in Business Address Sercices.
    Personal addresses are assigned to exactly one person, and can not be referred to by other application objects. The complete address object (person with address) can have several uses.
    For identification, a 10-digit number for the person and a 10-digit number for the address are required.
    A person (identified by the 10-character address) can have several addresses.
    Example: business partner CHARLY is a natural person and has two addresses:
    a) the first address is identified by person number 1234 and address number 3333.
    b) the second address is identified by person number 1234 and address number 3357.
    Addresses of persons in companies (Address type 3): These are addresses which contain the properties of a person in a company, with attributes such as Department, room number, extension.
    Any normal address (address type 1), but not a private address, can be the company address.
    The address of a person in a company is identified, like a private address by a 10-digit number each for the person and for the address.
    Example: business partner CHARLY (see above) is contact person at business partner SAP_AG with company address 4444; CHARLY's contact person address is identified by person number 1234 (see above) and address number 4444.
    These three address objects constitute an abstract data structure. The function group SZA0 contains function modules for accessing these address types. There are function modules for maintenance (create, change and delete), and to read and to search for each address type. There are also function modules to maintain and read all communication types which are supported by R/3, for each address type.
    Function modules for private addresses begin with the prefix 'ADDR_PERSONAL_', those for addresses of a person in a company begin with 'ADDR_PERS_COMP'. Other function modules which begin with 'ADDR_' are for normal address maintenance, or in some cases, function group management.
    The function modules manage the data structure using a maintenance interface. The underlying tables must not be accessed directly. This could lead to inconsistencies in data structures which contain fields from several tables.
    Address maintenance
    Addresses should be maintained as far as possible using standard dialogs which are available in other function groups.
    Popup, subscreen and full screen dialog techniques are used.
    The parameter transaction SADR can also be used for maintaining normal addresses which do not depend on an application object. These addresses cannot be distributed by ALE.
    For more information, see the SZA1, SZA5 and SZA7 function group documentation.
    For information about address validation see the documentation of function group SZAR.
    If addresses are to be maintained without dialog, or if a user maintenance dialog is necessary for special requirements, addresses can also be maintained directly using the function modules of the function group SZA0. The standard dialogs of the function groups SZA1, SZA5 and SZA7 are also implemented with them.
    Conversion of existing SADR/SADRP addresses
    Most old addresses will be converted for the new central address management (Business Address Services) for Release 4.0.
    From Release 4.5, all SD document addresses (previously SADR), customer addresses (previously only KNA1), supplier addresses (previously only LFA1), business and private addresses of (customer) contact persons (previously SADR) and bank addresses (previously SADR) will also be in Business Address Services (central address management).
    Release notes Central address management for 4.0A and Central address management in Release 4.5 contain detailed information.
    II. Maintenance without dialog (function group SZA0)
    The contents of the function group can be classified as follows: management modules, which either apply to the function group as a whole or ensure correct database storage, address object maintenance (create, change, delete) modules, and address object communications address processing, for example, telephone, fax, or mail addresses.
    Organization
    Local memory:
    Save
    ADDR_MEMORY_SAVE: Saves the local memory contents in the database. All address data changes made since the first call of any function module in the function group are then permanent. Numbers must have been assigned to all addresses and persons before storing.
    Delete
    ADDR_MEMORY_CLEAR: Deletes the local memory contents. All address data changes made since the first call of any function module, or the last local memory save, are discarded. This module should be called after extensive read operations or when returning to the application.
    Number assignment:
    When assigning numbers to addresses or persons, their (first) use must be specified.
    ADDR_NUMBER_GET
    Assigns an address number, i.e. converts a temporary address number (address handle) into a permanent address number which is saved in the database key.
    ADDR_PERSON_NUMBER_GET
    Assigns a person number, i.e. converts a temporary person number (person handle) into a permanent person number which is saved in the database key.
    Where used:
    A permanent address or person number must have been assigned before a (further) use can be entered.
    ADDR_REFERENCE_INSERT
    Inserts a new use in an existing address.
    ADDR_REFERENCE_DELETE
    Deletes a use of an existing address.
    ADDR_PERSON_REFERENCE_INSERT
    Enters another use for an existing person.
    ADDR_PERSON_REFERENCE_DELETE
    Deletes a use for an existing person.
    Applications are also deleted by the normal delete operations when the application passed to the delete modules is not the only one, or most recent one.
    Address object methods
    Read:
    Read address objects
    <Address object>_GET: Reads a (fully qualified) address. All versions of this address are read into local memory, and are subsequently accessible without database access.
    ADDR_PERSONAL_GET_ALL: Reads all private addresses for a person. All versions of this person's private address are read into local memory, and are subsequently accessible without database access.
    Read address object block
    <Address object>_GET_ARRAY: Reads several (fully qualified) addresses. The database and the local memory are read. All address versions read are subsequently in local memory and can be accessed without database access.
    Insert:
    <Address object>_INSERT
    Inserts an address.
    <Address object>_VERSION_INSERT
    Inserts a version of an address.
    ADDR_PERSONAL_COMPLETE_INSERT
    Inserts a private address with full specification of personal and address data, in contrast to ADDR_PERSONAL_INSERT, where the person data already exist.
    ADDR_PERS_COMP_ASSIGN
    Assigns a company address to an existing person, in contrast to ADDR_PERS_COMP_INSERT, where the person is also newly entered.
    Change:
    <Address object>_UPDATE
    Changes an address version. (In particular the standard version, "the" address, is changed.)
    Delete:
    <Address object>_DELETE
    Deletes an address. All existing address versions are deleted.
    <Address object>_VERSION_DELETE
    Deletes one version of an address.
    Search:
    <Address object>_SEARCH
    Searches for addresses, which can be partially qualified (e.g. by attribute value specification). Only the database contents are searched (the local memory should be saved first, under certain circumstances).
    Communication addresses
    Read:
    <Address object>_COMM_GET
    Reads the communication addresses of an address object for a particular communication type. All communications addresses of the specified communication type, for the specified address object are read into local memory, from where they can subsequently accessed without database access.
    Maintain:
    <Address object>_COMM_MAINTAIN
    Maintains the communications addresses of an address object for a particular communications type. Maintenance comprises: create, change and delete. All communications addresses thus maintained can be accessed in local memory without database access.
    III. Maintenance with dialog
    Function groups SZA1, SZA5, SZA6, SZA7 and the parameter transactions SADR and SADP
    --> Overview in the SZA1, SZA5 and SZA7 function group documentation.
    IV. Application examples
    0.  General
        - The function group does not need explicit initialization.
        - Address data changes are only written to the database after
          'ADDR_MEMORY_SAVE' has been called.
        - Before the 'ADDR_MEMORY_SAVE' call, all temporary
          address and person handles must be converted to external
          numbers.
    1.  Read access to normal address (address object 1)
    Selection parameter for a normal address
        data: begin of selection
                include structure addr1_sel.
        data: end of selection.
    Attributes of a normal address
        data: begin of result.
                include structure addr1_val.
        data: end of result.
    Specify selection parameters
        clear selection. "no handle, default nation, today
        selection-addrnumber = t001-adrnr.
    Read normal address
        call function  'ADDR_GET'
             exporting  address_selection = selection
             importing  address_value     = result
             exceptions address_not_exist = 1
                         parameter_error   = 2
                         version_not_exist = 3
                         internal_error    = 4.
        case sy-subrc.
        endcase.
    Result output
        write: / result-name1,
               / result-street, result-house_num1,
               / result-post_code1, result-city1.
    Delete local memory after end of processing
        call function 'ADDR_MEMORY_CLEAR'
             exceptions unsaved_data_exist = 1
                          internal_error     = 2.
        case sy-subrc.
        endcase.
    2.  Search for a normal address (address object 1)
    Search parameters for a normal address
        data: begin of selection
                include structure addr1_find.
        data: end of selection.
    Result table for a normal address search
        data: begin of result occurs 0.
                include structure addr1_val.
        data: end of result.
    Address group table
        data: begin of dummy occurs 0.
                include structure adagroups.
        data: end of dummy.
    Number of addresses found
        address_count like sy-tabix.
    Specify search parameters
        clear selection.
        selection-name1 = 'SAP*'.
        selection-city1 = 'Walldorf'.
    Search for normal address
        call function  'ADDR_SEARCH'
             exporting  search_in_all_groups  = 'X'
                          search_for            = selection
             importing  addresses_found_count = address_count
             tables     search_result         = result
                          address_groups        = dummy
             exceptions parameter_error       = 1
                         internal_error        = 2.
        case sy-subrc.
        endcase.
    Result output
        loop at result.
          write: / result-name1,
                 / result-street, result-house_num1,
                 / result-post_code1, result-city1.
        endloop.
    3.  Bulk processing of normal addresses (address object 1)
    Table of selection parameters for a normal address
        data: begin of selection occurs 20.
                include structure addr1_sel.
        data: end of selection.
    Table of attributes for a normal address
        data: begin of result. occurs 20.
                include structure addr1_val.
        data: end of result.
    Error table
        data: begin of errors occurs 0.
                include structure addr_error.
        data: end of errors.
    Specify selection parameters
        clear selection. "no handle, default nation, today
        selection-addrnumber = t001-adrnr.
        append selection.
        clear selection.
        selection-addrnumber = vbpa-adrnr.
        append selection.
        ... enter further selections in table selection ...
    Read normal address in blocks
        call function  'ADDR_GET_ARRAY'
             tables     address_selection = selection
                         address_value     = result
                         error_table       = errors
             exceptions parameter_error   = 1
                          internal_error    = 2.
        case sy-subrc.
        endcase.
    Result output
        loop at result.
          write: / result-name1,
                 / result-street, result-house_num1,
                 / result-post_code1, result-city1.
        endloop.
    Delete local memory after end of processing
        call function 'ADDR_MEMORY_CLEAR'
             exceptions unsaved_data_exist = 1
                          internal_error     = 2.
        case sy-subrc.
        endcase.
    4.  Create a normal address (address object 1)
    Address number, address handle, address group, address data
        data: address_number like adrc-addrnumber.
        data: address_handle like szad_field-handle.
        data: address_group like addr_ref-addr_group value 'DEBI'.
        data: begin of address_data.
                include structure addr1_data.
        data: end of address_data.
    Use details
        data: begin of usage.
                include structure addr_ref.
        data: end of usage.
    Error table
        data: begin of errors occurs 0.
                include structure addr_error.
        data: end of errors.
    Return codes
        data: rc_insert like szad_field-returncode.
        data: rc_number_get like inri-returncode.
        data: rc_memory_save like sy-subrc.
        data: lv_check_address like szad_field-flag.
    Fill address record and determine temporary address identifier
        address_data   = ...
        address_handle = ...
    Deactivate address check if required
        lv_check_address  =
    Insert address in local memory
        call function  'ADDR_INSERT'
             exporting  address_data    = address_data
                         address_group   = address_group
                         address_handle  = address_handle
                         check_address   = lv_check_address
             importing  address_data    = address_data
                         returncode      = rc_insert
             tables     error_table     = errors
             exceptions address_exists  = 1
                         parameter_error = 2
                         internal_error  = 3.
        case sy-subrc.
          when 0.
            if rc_insert = 'E'.
              Analyze error_table and call special further processing
              because the address has errors and was not created.
                endif.
        endcase.
        ... process other application objects
            or modify Business Address Services
            local memory ...
        ... before saving potential application objects:
    Declare final use to address management
        usage-appl_table = ...
        usage-appl_field = ...
        usage-appl_key   = ...
        usage-addr_group = address_group.
    Assign address number
        call function  'ADDR_NUMBER_GET'
             exporting  address_handle           = address_handle
                          address_reference        = usage
             importing  address_number           = address_number
                          returncode_numberrange   = rc_number_get
             exceptions address_handle_not_exist = 1
                          internal_error           = 2
                         parameter_error          = 3.
        case sy-subrc.
        endcase.
        ... immediately afterwards:
    save local memory after processing
        call function  'ADDR_MEMORY_SAVE'
             exceptions address_number_missing  = 1
                         person_number_missing   = 2
                         internal_error          = 3
                         database_error          = 4
                         reference_missing       = 5.
        case sy-subrc.
        endcase.
    delete local memory
        call function 'ADDR_MEMORY_CLEAR'
             exceptions unsaved_data_exist = 1
                          internal_error     = 2.
        case sy-subrc.
        endcase.
    V. Terms/Glossary
    Address/Person group
    Addresses and persons can be assigned to an address or person group. One address or person can be assigned to several groups (multiple assignment). This allows e.g. the same address to occur as customer and supplier address, and also allows searches to be limited to certain groups, instead of always searching all addresses.
    Logical groups of addresses and persons can be formed.
    The address groups required by applications are established by the application developer in consultation with the SAP Business Address Services. Customers can define their own groups in the customer name range for their own developments.
    Address/Person handle
    Address data are saved in the database and address and person numbers are assigned only when the application data are saved. Application programs must call the appropriate function modules. Business Address Services hold the data in internal tables in the local memory of the function group SZA0. Before saving after creation, addresses or persons are identified by an address or person handle, via which address objects can be accessed until the data are saved in the database.
    The handle of a person, a normal address or a person in a company is determined by the application program.
    The following procedure is recommended for both the address and person handles:
    The first 10 places contain the name of the table in which the address or person is referred to. The next 10 places are used for the name of the field containing the reference, and the application data set key can be written in the remaining 120 places. This can be a temporary key, as the database key is only completed when saving in many application areas.
    In this way the application developer can manage the addresses with the data which he or she is accessing anyway.
    Ambiguities are avoided in complex transactions in which addresses for different applications are kept simultaneously in the same roll area for SZA0 (a serial number may not be sufficient as a handle).
    Communication addresses
    A communication addresse in the central address management is the identification number or address of a communication connection of one of the following communication types: telephone, fax, teletex, telex, SMTP, R/Mail, X.400 or RFC.
    e.g. the complete telephone number (dialling code + telephone number) is the identification of the communication address of type telephone.
    Address/Person number range
    The address and person number range defines the valid external identifications (database key value range) for addresses or persons. For reasons of compatibility, the same number range applies as for 'old' SADR and SADRP addresses. Specifically, address and person numbers are drawn from the same number range. This simplifies the conversion of old SADRF and SADRP addresses.
    Address versions
    The (international) version of an address is an independent address object data set, in which a different display style of an address can be maintained in a code page (e.g. in Japan in Kanji, Katakana or Hiragana).
    These are not independent addresses
    The part of the address object which does not depend on the display style is always in the standard version.
    In customizing (transaction SADV or under Cross-application components -> General application functions -> Address management -> Maintain address version display formats) you can set which other versions, in addition to the normal display style, are to be offered for maintenance.
    Where-used list
    In the where-used list, the application objects in which an address or a person are referred to is recorded. The where-used list is a technical support for the repeated use of addresses or persons in the three address types and therefore refers to the (sub)object address and person.
    Immediately before calling the function module 'ADDR_MEMORY_SAVE', the function modules 'ADDR_NUMBER_GET', or 'ADDR_PERSON_NUMBER_GET' must be called once for every normal address and once for each person (for private addresses and addresses of a person in a company). The (permanent) use of the address or the person in the application must be specified. In exchange the calling program gets the assigned numbers of the addresses and persons for the references in the application data records.
    Then (still before the 'ADDR_MEMORY_SAVE' call), other uses of addresss or persons can be specified via the function modules 'ADDR_REFERENCE_INSERT' or 'ADDR_PERSON_REFERENCE_INSERT' for multiple use.
    This is always possible once the address or person number is assigned.
    At the end of processing, the data must be saved in the database (as for all other address data) with the function module 'ADDR_MEMORY_SAVE'.
    Thanks,
    Sree.Manam
    Edited by: manam narayana on Jun 18, 2008 9:00 AM

  • Report to fetch the text information from customer master sales data

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

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

  • Reg: Customer Master Creation in BAPI

    Hi All,
    How can i find the fields, which are all used in
    BAPI_CUSTOMER_CREATEFROMDATA1 and in
    BAPI_CUSTOMER_CREATEFROMDATA...
    And how can i find the sap given sequential/flat file
    for customer master.
    Thanks & Regards
    arun

    most of the fields will be present in the BAPI function. some fields may not be avialable in that BAPI. first list out the fields what you want, then you check the fields in BAPI,  and also you can go for LSMW Recording method or LSMW batch input method.
    check this batch input program RFBIDE00 .
    For testing the BAPI you have to input the data manually in SE37. First create a sample customer in XD01, use the same data for testing the BAPI.

  • 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

  • BAPI to add additional partner functions in customer master(KNA1)

    Hello All,
    I wanted to add additional partner functions(2) to the list of partner functions which gets added by default while creating a customer. I am currently using BAPI_CUSTOMER_CREATEDATA1 to create the customer master. There i do not find any option to add my partner functions.
    NOTE: I need to update KUNN2 field as well while adding my partner functions.
    Could anyone please help here?
    Regards,
    Jay

    Hi,
    No you should not feel confident with SD_CUSTOMER_MAINTAIN_ALL.
    It is used for only one very special case. The maintenance of consumer. And this should only be true from the transaction itself.
    There exists other cases, one of the oldest one is the BAPI_CUSTOMER_CREATEFROMDATA1. But is is exclusively reserved for SAP Online store.
    Despite the fact CMD_EI_API is quite difficult to use, it has the main benefit that is it supported if being triggered directly.
    For the maintenance of customers, there is NO BAPI and NO direct function module.
    There are some functions modules like the one above where the name is looking nice. But these should not be used.
    The only valid solutions are :
    Below ECC 2005 (6.00), the only solution was batch input and DEBMAS idocs. See note 384462
    Starting with ECC 2005 (6.00) and above: a synchronisation tool has been introduce. See class CMD_EI_API and VMD_EI_API
    Hope this helps
    BR
    Alain

  • Account Group and partner functions in customer master records

    Hi Gurus,
    I need your help to confirm the following understand if correct:
    1. To create customer master record for partner function Ship-To, need to create a customer master record using the uniquely assigned account group for Ship-To , that is, 0002 . In this ship-to master record, define in its partner function tab, the other partner functions related to it. 
    2. To create the above, it cannot be achieved by just assigning the partner functions in the partner function tab of SOLD-To customer master record , created using account group 0001.
    Question:
    1. How does the system know or allow what codes a user can select (f4) or enter manually when defining in customer master record's partner function tab, the partner functions and their respective codes?
    How is this controlled? Is it by user authorization? or will user / sales administrator be able to select any codes tied to a partner function?
    2. Lets say there are 2 partner functions : Sales employee VE and 9E called Sales Representative. Both of these partner functions are of Partner Type PE.
    When defining in customer master record's partner function tab, how does the system know what codes is selectable for the administrator for each of these partner functions?
    best regards
    M Russo

    hi russo,
    this is to inform you that,
    1. yes you are right.
    2. you need to follow the steps as you said.
    Question:
    1. that you can find in the search basing on account group for partners.  that assignment we should know russo which SH to be assigned to which SP.  no need to have authorization for that, make a note of the list of SH and SP to be assigned that's all.
    yes, he will able to select any SH from the list but make sure that we assign the correct SH to the list of SP.
    2. that you will be defining it in Partner Determination Procedures.  at the time of CMR creation you have to select the correct code that will get populated in sales order.
    hope this clears your issue.
    balajia

  • Need Business case Explaination about the Field in Customer Master

    Hi all,
    I have a doubt in Customer master Record
    1. Customer Group
    2. Price Group
    3. Price list
    4. Customer Stat.group
    What I mentioned above fields i need business case explination, but all the above fileds are explaining  about the Price and Statistics about the report. By using F1 Help i can understand but i need business case
    Is there any link between those fields ?
    @ Please dont close the thread if it is basic question please provide the details and link because i serached in Google but i couldn't able to findout

    hi
    anuradha,
    In my knowledge customer pricing group is the main in the customer master ,
    you will one test case in customer pricing group in customer u can not fill it,  the same customer u can rise the sale order , system sows earorr message, no customer master records maintain, it means when u create the sale order system  take pricing procedure , pricing procedure determination ; sales area+customer pricing procedure +document pricing procedure assign to pricing procedure,(ovkk) ,
    customer statical group
    Sales Organization      0001   Sales Org. 001
    Distribution Channel    01
    Division                       00
    Cust.stats.grp              1      'A' Material
    CustGroupMaterial       1      'A' Material
    StatGrpSalesDoc         2      Returns, Credit Memo
    StatGrpDocumentItm     1      Returns, Credit Memo
    Update Group               1      SIS: Sales Document, Delivery, Billing Document
    it is the static updating group for item level,
    Sales Organization     0001   Sales Org. 001
    Distribution Channel    01
    Division                        01
    Cust.stats.grp             1      'A' Material
    StatGrpSalesDoc        1      Order, Debit Memo
    Update Group              1      SIS: Sales Document, Delivery, Billing Document
    it is for static updating group for header level
    it is use full in vov7 ,
    price list and price group it is use full pricing to the customers,  you can check it sale order header in sale tab u can find your required fields,

  • Customer master data using LSMW std batch input

    Hello all,
    i m using LSMW method to create customer master records in the SAP system.
    we need to cover all the fields for addresses.
    Following are my doubts :
    1. some address fields are gettng truncated while loading customer master using std batch input program (for ex name1,name2,name3,name4,street..)
    2. some fields are not part of std batch input program . how to load that fields
    3. if we load address data first and then other customer data ,how to handle internal number range?
    4. how to upload internation address data in the system? is there any bapi for that?
    5 . how to upload additional communication data in address (ex mail,URL)
    Please help asap. its required urgently.
    thanks
    Jigs
    note : helpful ans will be rewarded.

    Message type DEBMAS
    Idoc type DEBMAS**  where ** is highest number available in your system (check via WE30). e.g. DEBMAS06

Maybe you are looking for