Nothing Special   »   [go: up one dir, main page]
Scribd Logo
Upload

Welcome to Scribd!

  • 491 views

    Source System Connection After ECC Refresh

    Uploaded by

    khan
    The document provides steps for refreshing an existing non-productive source system by copying the productive source system, including deleting copied source system assignments, renaming the target system and converting logical system names, and performing BW-specific adaptations like restoring the source system connection and repairing the delta queue.

    Copyright:

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

    Source System Connection After ECC Refresh

    Uploaded by

    khan
    491 views9 pages
    The document provides steps for refreshing an existing non-productive source system by copying the productive source system, including deleting copied source system assignments, renaming the target system and converting logical system names, and performing BW-specific adaptations like restoring the source system connection and repairing the delta queue.

    Original Description:

    Source System Connection After ECC Refresh

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides steps for refreshing an existing non-productive source system by copying the productive source system, including deleting copied source system assignments, renaming the target system and converting logical system names, and performing BW-specific adaptations like restoring the source system connection and repairing the delta queue.

    Copyright:

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

    Source System Connection After ECC Refresh

    Uploaded by

    khan
    The document provides steps for refreshing an existing non-productive source system by copying the productive source system, including deleting copied source system assignments, renaming the target system and converting logical system names, and performing BW-specific adaptations like restoring the source system connection and repairing the delta queue.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 9
    At a glance
    Powered by AI
    The document outlines the steps to refresh a non-productive source system by copying the productive source system. It involves deleting connections between the copied source system and original BW system, renaming the copied source system, and performing BW-specific adaptations.

    The procedure involves checking table RSBASIDOC to determine existing source system connections, executing function module RSAP_BIW_DISCONNECT to delete obsolete BW connections for each entry in the table, and deleting obsolete RFC destinations pointing to the original environment.

    The target SAP source system steps include renaming the target SAP source system and converting the logical system names using transaction BDLS, and deleting all obsolete RFC destinations pointing to the original environment.

    Source system connection after ECC refresh

    Created logical system for EQ1-330, dont need it run bdls directly

    Note 886102
    ===================================================
    ==================
    Scenario C3

    You want to copy a single source system of a BW system; the BW system is not
    copied. You want to refresh an existing non-productive source system (of a non-
    productive BW system) by copying the productive source system [PRD to NPS,
    refresh].

    Phase 6: Final Activities in Target Environment

    Step 6.4: Delete copied source system assignments


    Directly after the copy, there is a connection between the copied SAP source system
    and the original (productive) BW. Delete the source system connections of the copied
    SAP source system without changing the source system connections between the
    original BW and SAP source system connection by executing following procedure:

    Check table RSBASIDOC in the newly copied target SAP source system to determine
    all existing source system connections.

    If the table is empty, you do not have to execute function module


    RSAP_BIW_DISCONNECT.

    If entries exist, note down all these entries: fields RLOGSYS and SLOGSYS.

    Note: Do not delete the RFC destination between the target SAP source system and
    the productive BW system! The system needs the destination during the deletion to
    obtain metadata information from the productive BW system (only a read access).

    Execute function module RSAP_BIW_DISCONNECT in the copied target SAP source


    system using the following parameters:

    I_BIW_LOGSYS = <RLOGSYS>

    I_OLTP_LOGSYS = <SLOGSYS>

    I_FORCE_DELETE = 'X'

    This step deletes all obsolete BW connections. Repeat this step for all entries in table
    RSBASIDOC.

    Caution: DO NOT enter a value in the field "RFC target sys". This would cause the
    function module to run in the system specified there!

    In the copied source system: Delete all obsolete RFC destinations pointing to the
    original environment.

    Step 6.7: Rename the target SAP source system and convert the logical
    system names
    Assign the name assigned to the overwritten SAP source system (logical system
    name, table T000) to the target SAP source system. Use transaction BDLS to convert
    the logical system name in all the relevant tables. No other activities can be
    performed in the system during conversion.
    Read Notes 121163 and 369758 for details about transaction BDLS.

    Step 6.8: Perform BW-specific adaptations


    Restore the source system connection in the BW system connected to the overwritten
    SAP source system
    Start the Administrator Workbench / Data Warehousing Workbench (RSA1), right
    mouse click on the source system, and choose Restore.

    Repair the delta queue


    In the BW system: Execute report RSSM_OLTP_INIT_DELTA_UPDATE for each
    datasource, which has an active init request. Provide the field 'ALWAYS' with value 'X'.
    This will push the init / delta information of the BW into the source system, thus
    allows to continue loading delta or to do a new init.

    ===================================================
    ==================

    SE16

    RSBASIDOC
    Restore
    Define source system in rsa1 and again restore
    Activate
    Then
    It came to
    Took back

    Taking lot of time approx 10-20 mins adapter activation

    BI done

    You might also like