Scribd Logo
Upload

Welcome to Scribd!

  • 33 views

    Appendix: © Sap Ag BC420 15-1

    Uploaded by

    chandra9000
    EX_0015

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    Appendix: © Sap Ag BC420 15-1

    Uploaded by

    chandra9000
    33 views6 pages
    EX_0015

    Original Title

    EX_0015

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    EX_0015

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    33 views6 pages

    Appendix: © Sap Ag BC420 15-1

    Uploaded by

    chandra9000
    EX_0015

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 6

    0

    Appendix

     SAP AG 1999

    © SAP AG BC420 15-1


    0.2
    Test Phase

    1 Create extract
    2 Transfer data
    3 Fix records that
    have errors
    1 1 1
    3 3

    Typical All
    Data 2 2 Data 2

    SAP SAP SAP

     SAP AG 1999

     No more than ten records should be used in the first test phase. After each successful test, the amount
    of data can be increased in stages. The final test should include the complete data to be transferred.
     Correct any errors that occur during the test phase:
     If there is an error in the data record (for example, incorrect postal code), correct the data record in
    the external system.
     If there is an error in a Customizing entry, fix the entry.
     If the error is in the conversion program, fix the program.
     You can only be sure that the actual data transfer will be free of errors, if the test runs successfully.

    © SAP AG BC420 15-2


    0.3
    Executing Data Transfer

    TEST

    GoingLive
    Test phase Execute Data
    integrity test transfer

    Create data extract

    Production
    system SAP

    Test system
    SAP SAP

     SAP AG 1999

     The actual productive transfer is not done directly after the test phase. After the test phase the
    integration test has to be run. Within the integration test all the required business processes are tested
    with data imported up to this time point.
     If the integration test is successful, then actual transfer can be carried out.
     Important: If Customizing changes have to be made during the integration test, it could lead to
    transfer errors. This means that each Customizing change involves having to test the transfer again.
     During the complete testing and integration phase the external system remains the productive system
    in which productive data is processed. No system is available during the actual productive transfer.
    Afterwards the SAP System takes over the role of productive system.

    © SAP AG BC420 15-3


    0.4
    Specifying Data for Transfer

     Is all the required data available in the external system (for


    example, company code) ?
     Missing data must be created from the data context

     Can all the fields of the external system be mapped?


     Are there dependencies with other objects?
     Schedule run

    Master data Transaction data

     SAP AG 1999

     Occasionally a field in the SAP System may not have a corresponding field in the external system. If
    this field is required in the SAP System, you can proceed as follows:
     If this value is the same for all data records, this value can be determined and specified as a fixed
    value
     If this value has a dependency, this must be specified. The dependency determines the value for
    each data record.
     If there is no field available in the SAP System for a field from the external system, you can proceed
    as follows:
     Consider whether the field is required at all in the SAP business process. If it is not needed, it can
    be left out.
     SAP fields that are not directly required for the business process, can be filled with this field.
     The business processes in the SAP System unavoidably involve a dependency. So only transaction
    data can be transferred, if the associated master data is already available. It is essential that you
    consider the dependencies and the sequence of the objects.

    © SAP AG BC420 15-4


    0.5
    System Landscape
    System Copy

    SAP SAP SAP


    Development System Quality Assurance Production

    000 000 000


    001 001 001

    Cross-Client Customizing
    Cross-Client Customizing

    Cross-Client Customizing
    066 066 066

    100 Customizing
    100 Test1 100 Production
    Client Copy
    200 Test2

    999 Backup 999 Backup

     SAP AG 1999 Transport

     The distribution of client-dependent and cross-client Customizing to all clients and systems in the
    system landscape is essential for data transfer.
     For example, before you can test data transfer in client 100 of a test system (quality assurance), you
    must transport the Customizing settings from the Customizing client in the development system to
    this test client.
     Important to note: During day-to-day use, transport of cross-client or client-dependent Customizing
    is often forgotten, which causes data transfer errors.

    © SAP AG BC420 15-5


    0.6
    Practical Solution

    REPORT sapbc420_bapd_call_lsmw.
    TABLES: dxfile.
    DATA: variant TYPE rsvar-variantt.
    Call Register DATA: progname LIKE sy-repid.

    SELECT-OPTIONS:
    DX-WB Interface filesin FOR dxfile-filename
    NO INTERVALS NO-DISPLAY,
    filesout FOR dxfile-filename
    NO INTERVALS NO-DISPLAY.

    READ TABLE filesin INDEX 1 INTO filesin.


    variant = filesin-low.
    Call with variant
    READ TABLE filesout INDEX 1 INTO filesout.
    progname = filesout-low.
    /SAPDMC/SAP_LSMW_INTERFACE
    SUBMIT (progname)
    * via selection-screen
    USING SELECTION-SET variant
    AND RETURN.

     SAP AG 1999

     For more information about the interface, see the DX-WB documentation.

    © SAP AG BC420 15-6

    You might also like