Customer master details

hello guru's,
                my requirment is i need to upload Customer Master details using BAPI  in LSMW. can anyone tell me the Business Object Type and Method name ..i know message type and idoc type for Customer Master bt i dont know how to search the Business Object type and Method...

Hi,
Object          0050  
Method          0000
Program Name    RFBIDE00
As an alternative to using u2018Transaction Recordingu2019, you could also use a standard SAP object to update Customer Master Records. Business Object u20180050u2019 is already pre-defined in the system with standard Batch Input Interface Program u2018RFBIDE00u2019.
Create an Object CUST_OBJ within Project as LSMW_DEMO and Subproject as CUSTOMERS as shown in Figure 20.
Figure 20  LSMW Object with Standard SAP Object
Note! Only steps that are different from the recording method are listed here.
Step 1: Maintain Object attributes
You will be updating the customer master records with the help of Standard Batch Input; therefore, choose radio-button Standard Batch/Direct Input as shown in Figure 21. Enter Object u20180050u2019 for Customer Master records and default method u20180000u2019 and click on Save. 
Figure 21 Standard Batch/Direct Input Object Attributes
Step 4: Maintain Structure Relations
Sales view of Customer Master is stored in table KNVV. Accordingly, you need to update structure BKNVV. However, in addition, the Standard Object u20180050u2019 also requires updates to BGR00, BKN00 and BKNA1 structures. (If you do not maintain Structure relations for mandatory entries, you might get a message such as u2018Target structure BKNA1 needs a relation to a source structureu2019.) 
Even though you donu2019t want to update any fields in these structures, you need to create a relationship with source structures. In all, you need to create relationship for four target structures. 
Create relationship between source structures XD02S with these target structures with icon u2018Create Relationshipu2019  . 
Keep Cursor on these four target structures and click on icon u2018Create Relationu2019 and structure relations are maintained as shown in Figure 22. 
Figure 22 Structure Relation
Step 5: Maintain field mapping and conversion rules
-- Keep your cursor on u2018TCODEu2019 field and click on u2018Insert Ruleu2019 icon 
Figure 23 LSMW Conversion Rules
Choose radio button u2018Constantu2019 (Figure 23) to enter value u2018XD02u2019 transaction code.
-- Keep your cursor on field u2018KUNNRu2019 and click on u2018Assign source fieldu2019 icon 
Choose source field u2018Customeru2019 from source structure u2018XD02Su2019. (See Figure 24.)
Figure 24 Assign Source fields
-- Similarly, choose source fields for Sales Organization, Distribution Channel, and Division. (See Figure 25.)
Figure 25 Field Mapping and Conversion Rules
-- Scroll down to structure BKNVV fields and assign source fields to three fields Sales Office, Sales Group, and Customer Group (Figure 26).
Figure 26 Field Mapping and Conversion Rules
Save and go back to main screen.
Step 12: Display Converted data
When you convert data, LSMW automatically converts into the appropriate structure layouts, as required by Standard program (RFBIDE00). (See Figure 27).
Figure 27 Converted data into multiple structures
Note that if you had only one record in source file, the converted file has four records.
Earlier, creating this input file, so that the standard interface program can read it, was a big nightmare, the primary reason being that it could have multiple record layouts. Even for a simple conversion with one input record, you would have to create this complex file with many record layouts. The advantage of LSMW is that it prepares these multi-layout files automatically.
Step 13: Create batch input session
Once source data is converted in internal format, you can create a BDC session to process the updates (Figures 28 and 29). 
Figure 28 Create BDC Session
Figure 29 BDC Session u2018CUST_OBJu2019 created.

Similar Messages

  • Custom Master Detail form not working In EBS

    Custom Master Detail form not working In EBS
    Hi all,
    I have two custom tables -- 1) XXX_DIE_Headers
    2) XXX_DIE_LINES
    I developed a Master Detail form based on above tables. XXX_DIE_Headers is the Master Block (Single record) & XXX_DIE_LINES is the detail block ( Multi line block ).
    Yes, I used Appstand,Template.fmb for developing this form. The Master block has three fields out of which Two are required fields and i have given initial value for them.
    As i deployed it in APPS(EBS),everything about it is working fine (insert,delete,master-detail behaviour) except querying.
    When i press F-11 , It pops up a message "Do you want to save changes you have made" Choice - yes,no,cancel.
    I don't want this message to pop up.
    The scenario is :- I open the form.( without entering ) Press F11 . The message Pops up.
    Please give me suggession on how to work it around so as form directly goes to query mode ,without popping the message.
    regards
    ravi

    It seems that you are changing a database value in your form, do you have any changes in WHEN-NEW-FORM-INSTANCE???
    what the form is trying to tell you that you have changed something, do you want to save it?
    I suggest you debug your form and see what's happening step by step.
    Tony

  • Finding field KNA1_OIDRC in ECC6 / ERP2005 on the Customer Master details

    Hi to all SAP Gurus
    Could someone kindly advice how to find screen field "Diff.Ref.Co"/ Mag Area(KNA1_OIDRC) in the ECC6 environment. in the previous release of SAP 4.6C it was situated on General data in the Control Data tab. I have found SAP Note 973001 but this has not solved our problem. i have also checked in configuration to make sure the screen is a required entry.
    Thanks
    Phenyo

    Hi,
    Verify if
    1. In SAPLOI0_MF02D and screen number 7123, the attributes of the field Diff. ref. code (KNA1-OIDRC). is 084.
    2. Table TMODP has ONLY this entry
    E     T077D-FAUSA     084     Differential Reference Code
    3. Check customizing in OB20 and also in SPRO -> Logistics-General -> Business Partner -> Customers-> Control   -> Define Account Groups and Field Selection for Customers
    Best Regards,
    Hema

  • Unrelated data in master detail sections of a custom BIP  report deployed in R12 EBS

    We have a custom Master Detail BIP report generated by calling XDO APIs from a custom Java concurrent program (common_report_attachment) . This Java concurrent program is called from another custom concurrent program (po_validation) that processes a batch of POs in a single concurrent request.
    PO_Validation Program (processes a batch of POs per request) -> Java Concurrent Program -> BI Publisher Report APIs
    BIP report generates data for master detail sections based on two sql queries (given below) that have 'where' clause based on a common external parameter "P_TRX_HDR_ID".
    NOTE: No explicit data link is used NOR an output column of parent query is used in the where clause of detail query as bind parameter.
    - <dataTemplate name="NAPPB2BPORPT" description="Data Template for B2B PO Report" version="1.0">
    - <properties>
      <property name="xml_tag_case" value="upper" />
      <property name="db_fetch_size" value="200" />
      <property name="scalable_mode" value="on" />
      </properties>
    - <parameters>
      <parameter name="P_TRX_HDR_ID" dataType="number" />
      </parameters>
    - <dataQuery>
    - <sqlStatement name="Q_PO_HDR">
    - <![CDATA[
    SELECT poh.po_number                                     PO_NUMBER
              , poh.quote_number                             QUOTE_NUMBER
              ---- other columns -----
             FROM nappcust.napp_o2i_po_headers poh
                ,napp_aso_quote_headers_v naqv
               WHERE 1=1
               AND naqv.quote_number=poh.quote_number
               AND poh.header_id = :P_TRX_HDR_ID
      ]]>
      </sqlStatement>
    - <sqlStatement name="Q_LINES">
    - <![CDATA[
    SELECT  pol.item                                            ITEM
          , pol.partner_part_number                             PARTNER_PART_NUMBER
          -- other columns --
       FROM napp_o2i_po_lines pol
       , napp_o2i_po_headers poh
       , aso_quote_lines_all aqla
       , mtl_system_items_b msib
    WHERE 1=1
      AND poh.header_id               = pol.header_id
      AND pol.header_id               = :P_TRX_HDR_ID
      AND aqla.quote_header_id        = poh.QUOTE_HEADER_ID
      AND msib.inventory_item_id      = aqla.inventory_item_id
      AND msib.organization_id        = aqla.organization_id
      AND (pol.quote_line_number       = aqla.quote_line_id
           OR pol.quote_line_number    = aqla.quote_line_id||1)
      ]]>
      -- Added for the defect 13954
      </sqlStatement>
      </dataQuery>
    - <dataStructure>
    - <group name="G_PO_HDR" source="Q_PO_HDR">
      <element name="PO_NUMBER" value="PO_NUMBER" />
      <element name="QUOTE_NUMBER" value="QUOTE_NUMBER" />
      --- mappings for other columns of "Q_PO_HDR"
      - <group name="G_LINES" source="Q_LINES">
      <element name="ITEM" value="ITEM" />
      <element name="PARTNER_PART_NUMBER" value="PARTNER_PART_NUMBER" />
        --- mappings for other columns of "Q_LINES"
      </group>
      </group>
      </dataStructure>
      </dataTemplate>
    Issue: Sometimes when the parent concurrent request runs for a batch with multiple POs the report generated for the last PO has inconsistent data in the master and detail sections. To elaborate, the detail section is having correct data pertaining to the PO identified by the parameter "P_TRX_HDR_ID". However, the master section is having data pertaining to the previous PO processed from the same batch.
    This issue is not occurring consistently and is not reproducible at will. I
    'm suspecting this could be because of not having data link between the queries but confirm from someone who has experienced this issue.
    Regards,
    Srinath

    is there any way from the page, can we pass the some values, which can identify the page level data?
    if so pass the parameter to BIP report query.

  • Creation of Customer Master with Sales Data

    Hi Experts,
    I have a requirement in whic i have to Create/Change Customer Master through Custom program.
    The Customer Master details will be stored in file and Retrieved through program with the following Tables to be Updated
    KNA1 - Customer Master
    ADRC - Address
    ADR2 -  Telephone Number
    ADR3 - Fax Number
    ADR6 - E-Mail Addresses
    KNVV - Customer Master Sales Data
    KNVP - Customer Master Partner Functions
    KNVK - Customer Master Contact Partner
    From SDN  i came to know about  CMD_EI_API . Can you please tell me which is the method suitable for Creation/Change of Customer Master with the above details.
    Regards,
    Shrikanth R

    Hi Experts,
    Please help me how to use MAINTAIN_BAPI method in Class CMD_EI_API  in order to create Customer Master.
    Regards,
    Shrikanth R
    Edited by: SHRIKANTH R on Jul 15, 2010 11:59 AM

  • Master Detail on same page

    Hi,
    I have a custom master detail requirement. The page is currently only for CREATE, no query requirement. There are 2 custom tables involved and a common column (process_id).
    When I only have the MASTER detail on the page (VO-EO) and save it is fine, saves to table1.
    Now I want to add the ability to save 1..* records in the detail table.
    So I navigate to page, enter the master data as above, tab down to the detail section and enter a number of fields (say 3 new rows of detail).
    What are the basic steps to go about this. I appreciate there is some information in the Dev guide but it is a bit complex for what I require I think.
    I am thinking (and currently tying).
    Create new EO for detail table
    Create new VO for detail
    Create an EO association (is this needed???)
    Create a View Link between master and detail.
    Associate the VO with the same AM as the master.
    Add a new table region to the form...
    Now this all works in that I can display above. What is required to allow me to save successfully after entering the data.
    This is an urgent request, so any help much appreciated.
    Robert

    PPR to the rescue!
    Try changing the singleSelection element to include your additional field in it's targets list. eg:
    <singleSelection
      model="${bindings.OtherView1Iterator}"
      text="Select and ">
      <primaryClientAction>
        <firePartialAction
             targets="_uixState MyOtherFantasticField"
             source="OtherView112"
             event="select"/>
      </primaryClientAction>
    </singleSelection>And you'll need to add an id to your field such as:
    <messageTextInput
      model="${bindings.blah}"
      id="MyOtherFantasticField"/>Hope this helps.
    CM.

  • Problem with fetchedRowcount in master-detail.

    Hi all,
    Good morning.
    I have a custom master detail page (Sales Module, called from Opportunities page).
    The master region is query-only and the detail is an updateable advanced table.
    I'm trying to delete in the detail exactly the same way the tutorial proposes.
    I navigate to the master record (and using the viewlink to the detail records...) using an initquery method in the am. that is called from the controller in the processrequest using invokemethod.
    My problem is that the vo.fetchedrowcount in the master is correct but in the detail is allways 0. So I can't delete the record.
    I've tried also vo.getrowcount and get 0 (in the delete method of the am.)
    I've tried vo.setpreparedforexecution(true) with the same result. (in the delete method of the am.)
    I've tried in the controller an initquery for detail with the same result.
    I've tried in the controller a table.querydata(...,true) with the same result
    Any help would be appreciated.
    Juanje

    Hi again,
    Thanks for the rapid response.
    I've implemented de master as a messageComponentLayout which includes several messageStyledText items.
    The detail is an advancedtable which includes several messageTextInput items.
    I have not used "table in table" to implement the master detail.
    I only use a viewlink to join the master vo. and the detail vo. but only in the bc4j side.
    You mean, should I fill the viewlink property in the advancedtable?
    Now the detail records are shown correctly, and I can create records without problem.
    Thanks
    Juanje

  • Customer Master export to excel sheet

    Hi Friends,
    How can I export/download the customer master details (general data, sales are data and company code data) in an excel sheet from the system.
    Regards,
    Wasim.

    HI,
    Go to Se16 and download the tables KNA1 (General Data), KNB1 (Company code data), KNVV (Sales area data).
    How to download:  Menu bar - system - list - save local file -- spreadsheet.
    Br.
    Ramana

  • User detail in custom master page

    Hi All,
    I want to make appear logged in user detail in master page. 
    In SharePoint 2013, User can see "about me" detail in System account appearing at top right corner. 
    I want same user detail to appear in custom master page. I am not sure where we can look for it. 
    I guess we need to copy user detail tag from oslo master page and can paste in our custom master page. 
    But i am not sure where to find this. 
    Any help is much appreciated.
    Thanks..
    Rakesh

    Hi,
    According to your post, my understanding is that you wanted to display user information in the master page.
    We can register SPSWC at the top of the master page to call the user profiles.
    Register SPSWC at the top of the master page:
    <%@ Register Tagprefix="SPSWC" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
    Register the propertys below the starting Form tag:
    <SPSWC:ProfilePropertyLoader runat="server"/>
    There are some good articles for your reference.
    http://chayadigital.wordpress.com/2012/03/20/displaying-user-information-on-a-master-page-in-sharepoint-2010/
    http://chrisstahl.wordpress.com/2012/12/21/user-information-in-sharepoint-2010-with-help-of-the-spcwc-control/
    http://blog.bugrapostaci.com/2011/06/22/sharepoint-2010-change-your-display-of-wellcome-name/
    Thanks & Regards,
    Jason
    Jason Guo
    TechNet Community Support

  • 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

  • Creating master-detail VO in custom AppModule method

    Hi.
    I need to create master-detail view objects and save them in DB in my custom AppModule Service Interface method.
    I have the next master-detail view objects:
    RegistryVO (1) -- (*) RegistryItemVO
    Also I have a view link for this relationship.
    I wrote custom method with next signature:
    Integer createRegistry(RegistryVORowImpl registry) {
    Then, I added this method to my AppModule Service Interface.
    Method works fine, but only master row is created and inserted to DB (only Registry but not RegistryItem). I.e. when I testing this method in EM I fill full RegistryVO with nested RegistryItemVO data but in my method RegistryVO comes without nested RegistryItemVOs.
    Then, I added SERVICE_PROCESS_CHILDREN custom property to view link (RegistryVO-RegistryItemVO) as it described in chapter 11.2.5 of Fusion Developer 's Guide for Oracle Application Development.
    After that nested RegisttryVO in my method contains nested RegistryItemVOs.
    In my custom method i need to set primary key for RegistryVO. So I set it in registryVO to PK attribute and set it in nested registryItems to FK attribute.
    But when I doing commit I have an exception:
    Exception while executing the business logic: JBO-26048: Constraint "PP_PST_RG_IT_PP_PST_FK" is violated during post operation "Insert" using SQL stat
    ement " *INSERT INTO PP_PERSON_ST_RG_ITEM* (PP_PERSON_ST_RG_ITEM_ID,IN_DOCUMENT_ID,POL,FULLNAME,NAME,FULLOT,TIN,D_ROG_DT,D_REEST
    _DT,PROCESSING_DT,PROCESSING_STATE_CD,RECEIVE_YEAR) VALUES (:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11,:12)".: ORA-02291: integrity
    constraint (PP_PST_RG_IT_PP_PST_FK) violated - parent key not found
    It seems that only registryItems are commited in DB. I'm not seeing INSERT for Registry in ServieInterface log...
    But if I setting primary key for RegistryVO when I invoking method (if I setting id for registry in test console of EM, not in method) - it's work fine .
    What I'm doing wrong ?
    How can I create custom method for AppModule Service Interface to create master-detail view objects and set PK for master and FK for details within method ?
    Edited by: user2975420 on 19.10.2010 4:46
    Edited by: user2975420 on 19.10.2010 4:49

    Thanks for reply, John.
    I have already added master and detail view objects usages to my AppModule Data Model. And yes, I add detail VO as child of master.
    It seems that the reason of my problem is another...
    I can't create master/detail when I'm setting id of master in custom method. If I set id of master in input parameter (RegisterVORowImpl) then method invokes successfull.
    I noted one moment - if I'm not setting SERVICE_PROCESS_CHILDREN custom property for view link, I can set id of master VO inside method. But in this case my master VO haven't got nested RegisterItemVOs.
    Edited by: user2975420 on 19.10.2010 10:23
    Edited by: user2975420 on 20.10.2010 1:31

  • FM to upload Customer master Contact details.......

    Hello frndz,
      Is there any FM to upload Customer master Contact details.......
    regards,
    ajit.

    Hi Ajit,
    To upload the customer master contact details ,
    use the FM BAPI_PARTNEREMPLOYEE_CREATE.
    And to update the already created contact details,
    use the FM BAPI_ADDRESSCONTPART_CHANGE .
    also see link.
    Help with function mocule BAPI_ADDRESSCONTPART_CHANGE
    Thanks,
    Kanishak
    Do contact if any more quiries

  • CIN DETAILS FOR CUSTOMER MASTER

    Hi
    Friends
              when i am creating excise invoice with referrance to sales invoice an error is coming.--
              CUSTOMIZATION FOR CUSTOMER 100000 MISSING IN TABLE CIN CUSTOMER MASTER.
              How i will resolve the porblem, if it is possible plz provide me required configuration details
    regards
    Ambarish

    Hi Ambarish,
    Please maintain the CIN detail in the Customer master 100000
    Through menu>Environment>CIN details (CntrlShiftF12)
    If the details not able to maintain then
    Please go to OMT3E transaction,
    In Dialog structure
    Click on user screen reference
    Add the username and assign IN
    Then when creating the customer master, CIN details tab will be available.
    I hope it will help you,
    Regards,
    Murali.

  • ADD or Change Bank Details in the Customer master

    Hello Gurus,
    I am looking for a BAPI or Function Module that will help me to update the Payment Transaction Tab of the customer master that contains the Bank details. I tried using BAPI_BUPA_BANKDETAIL_ADD and BAPI_BUPA_BANKDETAIL_CHANGE, but these are allowed to be used if only Business Partner is created for the payer/customer in SAP R/3.
    For every customer we donot have BP created in R/3, hence the above bapis donot help to meet my requirement.
    Has any of you had this requirement and used any bapi or any other method to add / change bank details.
    Expecting lots of options from you experts,
    Thanks & Regards in advance,
    Casimer

    hi, thnks for the update,
    i have followed as per your guidelines,  but i could not able to generate the report  , i have included the tables  knb1, kna1 and knvv.  and in the list field i have selected all the dialog box  , and in the selection list i am selecting according to the customer account group .
    but i cannot able to excuete the report it says  "no data has been selected"  and it says the following msg
    "When executing a query on the selection screen, no data was found for the criteria you entered. Therefore, no list could be generated."
    is there any problem in choosing the table  should i have to choose according to the  order level , like  General data, company code data, and sales area data   .  
    can u help me on this
    thanks

  • Customer master Bank details

    Hi,
    In customer master/vendor master bank details tab whose bank details we have to give. customer bank details or our own bank details. Can anyone please tell and what is the use of this tab

    HI,
    In Customer and Vendor Master Bank Details Screen, you need to maintain the respective Bank details of the Customer and Vendor. you need to create Bank key in FI01(Provided by Customer or Vendor) and need to update that Bank key in Customer or Vendor Master.
    Currently we are maintaining Vendor Bank Key in Vendor master data and i have cearted a Query for master data. client will use the Query and check the Bank key (Bank Key Contains Bank Details of the Vendor) makes the payment to the proper Bank account.

Maybe you are looking for

  • CFMAIL Any Faster In CF8? How many mails per minute?

    Hi there, We are currently running CF 7.02 and are considering upgrading to 8. I've seen lots of articles extolling the speed increases in CF8 over 7 etc. but I wondered if there was much of a performance increase in regards to CFMAIL? We send out va

  • Proper connection between av receiver and iMac (network setting)

    What would be the proper network setting, to connect an av receiver (connected to cable router/modem)? Tech support peeps at Harman Kardon say I need to share my "Music Library", for the home network feature to work and allow me to stream music from

  • CRM Order related

    Hi All, I have created sales order by logging through contact person in B2B- ISA.Now i want to check in which tab pages the Following Information should be in CRM -GUI.       1.Contact person Details       2.Order Channel(eg:internet or telephone cal

  • Delivery document creation using vl01n

    Hi, I want to create a delivery document using VL01n.i need to create the doc for a particular selected item if there are many items for the order.i want to delete the remaining documents. how to handle this in BDC.

  • Forefront for Exchange Server is not blocking emails by IP

    I have 3 Servers for Exchange: Client, Mailbox, and Edge. I have Antispam configured on my Edge server with IP Block list enabled but I am getting numerous emails from China's IP block even though I blocked all of the .cn network. The following is en