Client Copy and Data Transport

S

CD

B

R

V

olution Management Guide

lient Copy and ata Transporting

ank Analyzer – IAS Solution

elease 3.0

ersion 2.00 – April 2004

SAP AG Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

JAVA® is a registered trademark of Sun Microsystems, Inc. © Copyright 2003 SAP AG. All rights reserved. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Any Java™ Source Code delivered with this product is only to be used

by SAP’s Support Services and may not be modified or altered in any way.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

Documentation on the SAP Service Marketplace You can find this documentation under the address service.sap.com/instguides. HTML, DHTML, XML, XHTML are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Symbols

Symbol Meaning

Attention

Example

Note

Recommendation

Syntax

Solution Management Guide

Content

Content 1 BASICS ..................................................................................................................................................... 5

1.1 INTRODUCTION ................................................................................................................................... 5 1.2 BANK ANALYZER SYSTEM SET-UP ALTERNATIVES ............................................................................ 5 1.3 CLIENT COPY FOR BANK ANALYZER .................................................................................................. 6

2 POSSIBLE SCENARIOS........................................................................................................................ 7 2.1 LOCAL CLIENT COPY .......................................................................................................................... 7 2.2 REMOTE CLIENT COPY........................................................................................................................ 8

3 BANK ANALYZER TOOLS & SERVICES ......................................................................................... 9 3.1 TRANSACTION /BA1/AT_INIT ........................................................................................................... 9 3.2 CUSTOMIZING / SYSTEM CONFIGURATION .......................................................................................... 9

3.2.1 SOBJ and FINB TR Objects ....................................................................................................... 9 3.2.2 RFC Destinations ....................................................................................................................... 9 3.2.3 Local Attributes / Exception table ............................................................................................ 10 3.2.4 Bank Analyzer System/Landscape Configuration..................................................................... 10

3.3 REPORT /BA1/RF0_MD_MAND_COPY......................................................................................... 10 4 CLIENT COPY PROCESS DESCRIPTION ...................................................................................... 10

4.1 PREPARATORY STEPS........................................................................................................................ 10 4.2 SETTING UP THE NEW CLIENT/SYSTEM ............................................................................................ 11 4.3 PREPARATION OF TOOL BW (REMOTE CC ONLY)............................................................................. 11 4.4 MAKING A TECHNICAL CLIENT COPY (LOCAL/REMOTE) .................................................................. 11 4.5 PREPARING FOR CC POSTPROCESSING .............................................................................................. 12 4.6 STARTING CC POSTPROCESSING ....................................................................................................... 14 4.7 LOG ANALYSIS AND EVALUATION .................................................................................................... 14

4.7.1 Accessing the Relevant Postprocessing Logs ........................................................................... 14 4.7.2 Analysis/Interpretation of the log messages............................................................................. 14 4.7.3 Restart ...................................................................................................................................... 15

4.8 IMPORT OF INFOSETS (REMOTE CC) ................................................................................................. 15 4.9 COMPLETING BW OBJECTS AND MASTER DATA .............................................................................. 15 4.10 RELEASE THE NEW CLIENT................................................................................................................ 16

5 TRANSPORT ......................................................................................................................................... 16 5.1 RFC DESTINATIONS.......................................................................................................................... 16 5.2 BEFORE EXPORT ............................................................................................................................... 16 5.3 AFTER IMPORT .................................................................................................................................. 16 5.4 SETTINGS THAT CANNOT BE TRANSPORTED .................................................................................... 17

6 LANGUAGE ACTIVATION (ONLY RELEVANT FOR MULTI-LINGUAL SYSTEMS)........... 17

7 SYSTEM CHECK TOOLS ................................................................................................................... 18 7.1 FDB.................................................................................................................................................. 18

7.1.1 FDB Configuration Check........................................................................................................ 18 7.1.2 Overview of the Segmentation Service Structure...................................................................... 19 7.1.3 OTS Monitor............................................................................................................................. 19

7.2 DERIVATION TOOL............................................................................................................................ 19 7.3 TOOL „RESULT DATA BASE”.............................................................................................................. 19 7.4 TOOL „MODULE EDITOR“ .................................................................................................................. 19

February 2004 4


Client Copy

You will find the actual version of this document in OSS-Note 692388.

1 Basics

1.1 Introduction Transport and client copy processes within Bank Analyzer are often accompanied by complex check and activation processes that are driven by different applications. For this purpose the Bank Analyzer provides a special infrastructure and uses a tool (FIN-B transport tool) that offers many features to meet the requirements.

This document covers all the steps necessary to create a valid client copy without transaction data based on Bank Analyzer Release 3.0 technology. Before going into details, some aspects need to be clarified:

Firstly, the various Bank Analyzer system set-up alternatives are described briefly, because they need to treated individually in the client copy process.

Secondly, this chapter defines what the term client copy means for Bank Analyzer.

1.2 Bank Analyzer System Set-up Alternatives This document assumes knowledge of the Bank Analyzer concepts and only summarizes the facts relevant for the client copy process.

The Bank Analyzer IAS and Basel II solutions comprise Bank Analyzer Core and a Reporting Business Information Warehouse (BW). The Reporting BW is not covered in this text, because it can be independently set up. In other words, the Reporting BW is a standard BW and can be treated accordingly.

BW Standard Copy

The standard client copy process for a BW system works as follows: A BW system consists of the client 000 and one additional client. Client 000 exists for technical reasons in every SAP system and must not be used. Check note 116432. Consequently, after the successful installation of a BW system, client 000 must be copied as described in note 116520. Once a BW has been set up like this, additional objects in this system/client may be created manually or by using the BW transport tool, but not by “client copy” mechanisms.

Additional notes of interest

• 325470 Activities after client copy in BW source systems

• 325525 Activities after client copy in BW source systems

Bank Analyzer Core

The Bank Analyzer Core itself is also made up of two parts, namely Tool BW and the “rest”, which includes the software component “Bank Analyzer” (BANK-ALYZE). In this document, the “rest” is referred to simply as “Bank Analyzer” (in contrast to Tool-BW).

February 2004 5


Client Copy

As described in note 588003, three different alternatives exist for setting up the Bank Analyzer Core:

1. Each Bank Analyzer client has its own Tool-BW. This solution has been introduced for Release 1.0 and is still supported. All clients are totally independent of each other.

2. All Bank Analyzer clients share the same Tool-BW, which is a remote system. Data separation is done by using the technical field 0SOURSYSTEM, which implies that the clients share the same data model.

3. All Bank Analyzer clients share the same Tool-BW, which is a local system. Data separation is done by using the technical field 0SOURSYSTEM, which implies that the clients share the same data model. This scenario is recommended most.

The actual nature of the process for copying a Bank Analyzer Core client depends upon the option chosen.

1.3 Client Copy for Bank Analyzer Usually, a client copy works in the following way: The system takes the source client and copies it unchanged except for the client field itself, thereby creating a new target client that behaves like the old one.

This picture is wrong even for the standard SAP applications; some objects – for instance database table definitions - are not client dependant themselves, but may contain information that is, for instance the entries in a database table. This information has to be replicated, changing the client from source to target client. This can be handled by SAP Basis functionality in most cases. For details, see the SAP library.

For Bank Analyzer, the picture gets more complex because of the highly generic data modeling approach, which includes the generation of central structures, tables and even programs, and the fact that the set-up of the Bank Analyzer Core system may be individually chosen from three alternatives.

Even though throughout this document the term “client copy” is used, it is much more helpful to think of a different process, namely the “creation with template” process. The outcome of a client copy process as described in this text is a new client which has the same business-related features as the template client but not the same objects.

This means that even though the technical objects in the new client and the template are not generally the same, the new client behaves in the same way as the template. Consistent customizing of the template will result in consistent customizing in the new client. Inconsistent Customizing will remain inconsistent in the new client. The business processes of the template based on template customizing will work in exactly the same way in the new client. Given identical input data, the results produced in both clients will be also be identical.

Some restrictions remain:

• Transaction data is not be covered by this process. Copying transactional data from the template to the new client is not supported in Release 3.0.

The process described in this document consists of manual steps and the execution of suitable programs.

Other copy techniques such as database copy or client transport are not covered by this document.

February 2004 6


Client Copy

2 Possible Scenarios

2.1 Local Client Copy

The local client copy has to handle two alternatives:

1. a local tool-BW or one remote Tool BW (data separation by 0SOURSYSTEM)

2. one remote Tool BW for each Bank Analyzer Core client (“Release 1.0” scenario, not recommended, similar to Remote Client copy)

February 2004 7


Client Copy

2.2 Remote Client Copy

The remote client copy has to handle two alternatives:

1. a standard BW client exists in the remote system

2. a standard BW client does not exist in the remote system

Restrictions:

o Mixing of BW standard clients and non-BW standard clients in the client copy process is not allowed and will produce inconsistencies. Only two remote copy scenarios are supported:

o The BW standard client of the template may be copied to create the BW standard client of the target.

o A non BW standard client may be copied to a non BW standard client.

February 2004 8


Client Copy

3 Bank Analyzer Tools & Services

3.1 Transaction /BA1/AT_INIT The FIN-B transport tool itself provides an IMG structure for relevant customizing activities, which can be entered with transaction FINB_TR_IMG.

The Bank Analyzer contains its own transaction /BA1/AT_INIT for entering the tools and services required for transporting data, making client copies, and for basic configuration. This transaction is designed for a system administrator or developer to deal with all kinds of issues and tasks related to these topics.

The initial screen of transaction /BA1/AT_INIT is divided in four major parts:

• Customizing

• Client Copy

• Transport

• Language activation

To make a client copy or postprocess a transport, you need the authorization object FB_SRV_TR with activity 16 (Execution). If you do not have this authorization, several buttons on this screen are inactive.

3.2 Customizing / System Configuration

3.2.1 SOBJ and FINB TR Objects The customizing area deals with the different kinds of settings and tables that are relevant. The transport objects (SOBJ) are the basis for each transport process. SOBJ objects belong to SAP standard. Additionally, there are settings within the FIN-B transport tool that are based on the SOBJ objects. Both SOBJ and FINB transport objects are provided by SAP.

3.2.2 RFC Destinations The FIN-B transport tool needs valid RFC destinations for each client (except for Early Watch client 066; the RFC destination for client 000 is needed for technical copy) in the system in order to perform after-import processes that are assigned to the import client. This is necessary since the technical client during after-import is always 000 even though the relevant import client is not 000.

Check that each (relevant) client has a valid RFC destination. Use the button “Check RFC Destinations” next to “Assign RFC Destinations” to get an overview of the assigned RFC destinations per client and check if they are valid respectively.

February 2004 9


Client Copy

3.2.3 Local Attributes / Exception table In some situations it can be useful to set local attributes for the transport objects in order to exclude specific objects temporarily, or to analyze specific objects. This can be done using the exception table. The following flags can be set per object:

• No Client Copy The corresponding object is neglected during the client copy analysis phase and client copy postprocessing.

• Debug (Expert Mode, special skills needed, that are not covered by this document) The after-import process is interrupted by a break-point or delayed by a big number loop right before the call of the corresponding object’s after-import methods. This feature can be used for analysis purposes. Batch processing of the after-import execution can be caught using the transaction SM50 by finding the waiting process .

This table should be used temporarily and should be empty under normal circumstances. Do not forget to remove any settings in this table after the analysis. If there are settings, this is indicated on the initial screen which displays their number next to the corresponding button.

3.2.4 Bank Analyzer System/Landscape Configuration There are a few basic system settings for the Bank Analyzer (system landscape and RFC Destinations for Accounting) that can also be accessed via /BA1/AT_INIT.

3.3 Report /BA1/RF0_MD_MAND_COPY Report /BA1/RF0_MD_MAND_COPY replicates master data belonging to BW InfoObjects from one SourceID to another. The report can be started by pressing the button Copy BW Master Data.

You will be prompted for the name of the characteristic or characteristics, the source and the target client. The report copies the master data locally or remote, changing the value of compounding field Source System-ID (0SOURSYSTEM). The report must be started in the target client, because the new value for 0SOURSYSTEM will be taken for the log-on client.

It is possible to copy master data for characteristics, that are not compounds to 0SOURSYSTEM. In this case, check the checkbox “Incl. Cross-Client Master Data”

4 Client Copy Process Description

4.1 Preparatory Steps The client copy process can be considered as a mass transport that includes all the settings of a client. This means you also transport settings that might be inconsistent or obsolete and might lead to activation problems and error messages in the target client. Thus we recommend you to ensure that the source client settings are as consistent as possible to avoid having to process error logs in the target client afterwards.

There are some tools and monitors to check the system’s status; these are listed in chapter Error! Reference source not found..

Make sure that nobody works on the system during the whole client copy and postprocessing phases. The client can be released for general use only after having finished all steps described below.

February 2004 10


Client Copy

4.2 Setting Up the New Client/System First create a new client using transaction SCC4. Assign a logical system to the new client.

Remote CC:

• Make sure that the source and target systems have the same support package level with respect to all software layers (Basis, ABA, FIN-B, Bank Analyzer)

• Set up the new system and the new client as described in the BW documentation (see above):

o As a copy of client 000 if no standard client exist

o As a copy of the BW standard client if the BW standard client exists

• Transport all non-SAP DDIC and ABAP Repository objects from the source system to the target system. Both systems must have the same DDIC state before the Remote Copy can be started

4.3 Preparation of Tool BW (Remote CC only) • Configure Tool BW as described in note 631416 so that it can be used in the Bank

Analyzer context This includes mainly three aspects:

o create a User in the BW standard client

o create an RFC connection to the BW standard client using the previously created user

o maintain the table RSADMINA

• Make sure that “MYSELF customizing“ is set Prerequisites: IMG customizing set, in particular:

• BW Standard client must already be defined (according to note 631416)

• The logical name of the client must already be defined

• BW Batch User must already be set up (according to note 631416)

• Start the Administrator Workbench transaction (transaction RSA1) with a user that has administrator authorization (especially for ALE RFC Destination and User Management). The system then creates the Myself-connection automatically.

• You can check the Myself-connection: Choose Administrator Workbench -> Modeling -> Source Systems. Choose “check” for the source system with the Myself-Icon . Should errors come up in connection with partner profiles, try to “restore” the Myself system.

4.4 Making a Technical Client Copy (Local/Remote) You do this before you start the classic client copy process (with transaction SCCL and SCC9 etc.).

Make sure that you have set the RFC Destination of the source client properly. To check the settings, you can use the RFC Destination Check function within transaction /BA1/AT_INIT next to RFC Destination Assignment

February 2004 11


Client Copy

Start the client copy process in the target system.

Note that not all profiles are allowed: Copy processes including transaction data are not supported by Bank Analyzer release 3.0 and will produce unusable copies. The following profiles are permitted:

• SAP_CUST

• SAP_CUSV

• SAP_CUSX

• SAP_UCSV

• SAP_UCUS

4.5 Preparing for CC Postprocessing To prepare for the postprocessing of client copies (both local and remote), proceed as follows:

1.) Log on to the new client with a user that has sufficient authorization (e.g. SAP_ALL, all Bank Analyzer Expert Roles)

2.) Check/Set System Landscape Parameters (IMG Bank Analyzer Basic Settings Define System Landscape) for the new client

3.) Check/Set RFC Destination in target client

4.) Check/Set logical system for new client (transaction SCC4)

5.) Assign RFC Destination for the accounting system depending on the system set-up (IMG Bank Analyzer Accounting Basic Settings Assign RFC Destination) or Maintain View V_ACCLSYS01 Please see note 665154.

Remote CC:

Before the main postprocessing can be started, the following two steps have to be taken in the target client:

• Generation of SAP InfoObjects in BW:

o Call /BA1/AT_INIT Postprocessing BA

o Select button ‘Objects for BW Generation’

o Start the report (e.g. as batch job)

This step will be included in the main postprocessing once again. However, it is recommended to start this step separately, because it will create and activate basic objects (e.g. fixed characteristics) without which the following steps will not be able to function properly. Therefore the following steps should be started only if the logs do not show errors.

• Import the InfoObjects as a transport from the source Tool BW.

o You can gather the relevant InfoObjects very easily by creating a transport request including all InfoObjects registered in the InfoObjectCatalog that is assigned to the

February 2004 12


Client Copy

source client (check IMG -> Bank Analyzer -> Basic Settings -> Edit Global Settings for Characteristics and Key Figures). You need to transport all characteristics.

o If you have manually assigned InfoObjects to local characteristics, they, too, need to be transported. Ideally, they are all contained in one designated InfoObjectCatalog. If this is not the case, you can also identify the InfoObjects from table /BA1/F0_LOC_OPT: You need to transport all InfoObjects whose characteristics have an initial value in the field IOBJ_GEN_TYPE. (Local fields are created with a reference to a data element. In case the data elements have not been created and shipped by SAP, they, too, need to be transported. This text assumes, that the data elements are already available in the target system.)

This extra effort is not necessary as long as you have all InfoObjects

generated for local characteristics.

• Activate the Business Accounting fields

o The fields needed for Business Accounting are not generated, but shipped with the BW Business Content (BW-BCT). Use transaction RSA1 Administrator Workbench of BW in the BW standard client of the Tool BW to activate them: Activate all InfoObjects of the InfoObjectCatalogs 0ACC_MANDATORY and 0EACC_COMMON_CHA01.

• Import the manually assigned ODS-Objects form the source Tool BW.

o If you have manually assigned ODS-Objects to Primary Objects, they, too, need to be transported. Ideally, they are all contained in one designated InfoArea. If this is not the case, you can also identify the relevant ODS-Objects using the customizing view IMG -> Bank Analyzer -> Financial Database -> General Functions for the Financial Database -> Data Retrieval -> Index Function -> ODS Objects -> Register OTS/ODS Objects. Alternatively, you may want to access the underlying table directly: Transport the following ODS-Objects of table /BA1/TF3_LEADOBJ:

all ODS-Objects listed in field ODSO_LEADOBJ which have an initial value in the field ODSO_LEADOBJ_GEN

all ODS-Objects listed in field ODSO_AO which have an initial value in the field ODSO_AO_GEN_TYPE

This extra effort is not necessary as long as you have all InfoObjects

generated for local characteristics. In this case, please make sure that you have

individually provided the InfoArea which the ODS-Object should be generated into.

If this is not the case, use the customizing view mentioned above (Register

OTS/ODS Objects).

You can check whether postprocessing is ready to be started by using the Check Option in the “Postprocessing Tool” report.

February 2004 13


Client Copy

4.6 Starting CC Postprocessing Start Postprocessing

• The system displays the initial screen of transaction /BA1/AT_INIT

• Choose Postprocessing BA

• Start the report; we recommend that you start the report in batch mode, since the job can take some time to complete.

After starting the report in batch mode and returning to the initial screen of /BA1/AT_INIT, the number next to the button indicates that the batch job is running. The number disappears (or decreases) when the job is done. You can check the log of the processed objects during the process by choosing Logs.

The process continues regardless of any error messages or even program terminations caused by the applications.

It is recommended to start the full post processing only once. After the first full run, re-starts should cover only previously incorrect transport objects as described in chapter [4.7.3].

4.7 Log Analysis and Evaluation

4.7.1 Accessing the Relevant Postprocessing Logs The postprocessing of client copies produces message logs that possibly contain error messages of various kinds, including hard program interruptions (E-messages or short dumps) if there have been any.


• Choose Logs next to the button “Postprocessing BA”

• Choose the corresponding log from the list. The newest log is the first in the list.

• The log contains information about what happened during processing. Each object called in the processed sequence of objects creates its own logs, which can be displayed by double-clicking on the corresponding line.

4.7.2 Analysis/Interpretation of the log messages Logs contain different types of messages:

• Success messages give you detailed information about the objects/data involved in the process

• Warnings refer to data that should be checked

• Error messages that indicate inconsistent Customizing in the new client. You should analyze these if they already existed in the source client. Since a client copy comprises all customizing settings, including those that are obsolete or have become invalid. These are processed and produce error messages in the log if they cannot be activated properly.

Correct the customizing and restart the process from this object or

February 2004 14


Client Copy

Check if the error messages are caused by activation errors in previously processed objects

• If there are messages that indicate a hard program interruption, there may be short dumps to be found in the system’s short dump history (Transaction ST22). For this purpose the exact time of this interruption is added to the corresponding message, which can be used to find the corresponding short dump. This type of message should not occur and should be reported to SAP via OSS/CSN. Please use the transport object specified, and note 684134 to find the correct CSN component.

4.7.3 Restart After having analyzed the logs and potentially corrected/added settings in the system, you can restart postprocessing.


• Choose Postprocessing (BA)

• Choose Incorrect Objects from Logs. This displays the list of existing logs with date/time/creator and the total/error number of objects. Only the logs containing error objects can be chosen.

• Choose the logs that are relevant for the restart; these objects are extracted from the logs and set as selection filter for the report

4.8 Import of InfoSets (Remote CC) Import the relevant InfoSets from the source system via transport. An InfoSet is relevant, if it is used, has been used or will be used to read FDB information from. Therefore, InfoSets that include generated ODS-objects that might hold information about FDB primary objects, are usually relevant.

There is no information in the system which could tell you, which InfoSets to transport. It is therefore recommended to put the relevant InfoSets into one designated InfoArea. Alternatively, you may want to transport all InfoSets, but then import errors will occur whenever the ODS-Objects, which the InfoSet is providing a view for, are not available in the system.

Use BW Administrator Workbench (Transaction RSA1) -> Transport Connection to select and transport the InfoSets.

4.9 Completing BW Objects and Master Data Copy/Import of InfoObject master data:

Remote CC:

The master data belonging to InfoObjects has to be imported by means of BW extraction/staging tools. Alternatively you can use the report /BA1/RF0_MD_MAND_COPY with the corresponding RFC Destinations.

Local CC:

The existing data must be copied by changing the 0SOURSYSTEM value. This can be done using the report /BA1/RF0_MD_MAND_COPY.

February 2004 15


Client Copy

4.10 Release the new Client If all steps are executed the new client can be released for general use. After having released the client the post processing tools should not be executed anymore, because it may occur that the client data changed after the release will be overwritten by stored data coming from the source client.

5 Transport

5.1 RFC Destinations Each client that is target of imports needs to have a RFC Destination assigned. Check that each target client has a valid RFC Destination:


• Choose Check RFC Destination” , which is next to the button “Assign RFC Destinations”

• Execute the report and check the results

Note that these settings are local and cannot be transported

5.2 Before Export The before export processes are important for certain applications that need to perform checks and data gathering when a transport request is about to be released. Sometimes applications cause error messages and prevent the transport request from being released.

• The Before Export Event can be tested:


• Choose Test/Analyze Transport Request.

• Enter the transport request and press return

• With the right-hand mouse button, click on the transport request and choose (Before) Export execution

To debug the Before Export Process you can set a debug flag in the exception table (button “Exception table” in /BA1/AT_INIT) for the corresponding object. Do not forget to remove the flag after the analysis is done.

5.3 After Import Lots of objects in Bank Analyzer need after import processes to activate or check data or objects. Each After Import Process produces logs that contain important information if all activation processes were finished correctly or if any problems occurred.

February 2004 16


Client Copy

Note that from the system’s point of view, the After-Import Method Execution of all Bank Analyzer Objects is done with one call of a function module provided by the transport tool. This call comprises all transport entries for all objects. The transport tool itself does not have a transport object since it has no customizing to be transported . For this reason the transport object mentioned in the header entry in the log is accidentually taken from the list of transported objects. The Bank Analyzer transport objects that have actually been processed are listed below the header entry. If there are any problems, or the program aborts, refer to note 684134 to identify the corresponding OSS component.

The After Import Process of a transport request can be tested:


• Choose Transport Request Test/Analysis

• Enter the transport request and press return

• With the right-hand mouse button, click on the transport request and choose (After) Import execution

The After-Import Processing can also be (re-)started if the default After-Import Process failed:


• ChooseTransport Request Postprocessing

• Start the report (use batch mode if the transport request is large)

• Check the logs (choose Logs next to button “Transport Request Postprocessing”)

To debug the After Import Process you can set a debug flag in the exception table (button “Exception table” in /BA1/AT_INIT) for the corresponding object. Use transaction SM50 to catch the batch process that remains in an endless loop. Do not forget to remove the flag after the analysis has finished.

5.4 Settings That Cannot Be Transported The following settings cannot be transported, and therefore have to be maintained locally in each client or system:

• RFC destinations of transport tool (see Error! Reference source not found.)

• RFC destinations of Accounting

6 Language Activation (only relevant for multi-lingual systems)

If the system (that is the texts implied in configuration) is multi-lingual (translated), there is an additional step that you must make in order to transfer translated texts to generated objects (e.g. key figures in BW). The following prerequisites have to be met before you can perform this activity:

February 2004 17


Client Copy

• The settings have been configured in one specified original language and have been translated to secondary languages e.g. using the translation tools (SE63)

• All target languages have been installed in the system (Table T000C)

• The activation processes within the customizing transactions have been carried out, so that the system works properly in the original language

To activate texts in translated languages proceed as follows:

• The system displays initial screen of transaction /BA1/AT_INIT

• Choose Language Activation

• Specify the languages for the text transfer

• Start the report (online or in batch mode)

• The log is displayed immediately and can be accessed later by choosing Logs, which is next to the button ‘Language activation’ at /BA1/AT_INIT.

This event cannot be transported itself and therefore has to be executed in each relevant Bank Analyzer System/Client.

Technical Background:

Some customizing transactions generate system objects with a language depended text. The texts are maintained within the customizing transactions. As a basic principle at the time of generation the texts will be transferred only in the logon language to the generated objects respectively.

If the texts of the generated objects however are directly relevant for operative processing (this means the texts appear on the screen having been directly read from the generated object) the language activation is necessary to keep the texts up to date.

7 System Check Tools After a client copy or transport process it may be necessary to check the status of certain important objects both in the source system and in the target client/system. For this purpose there are some transactions (“monitors”) that can be used to obtain a quick overview of the system status.

7.1 FDB

7.1.1 FDB Configuration Check The FDB Configuration Check can be found under IMG: Bank Analyzer Financial Data Base Utilities for the Financial Database Execute Configuration Check. This includes the monitors for characteristics and key figures. The following aspects will be checked:

• system landscape: checks are the same as for IMG activity Define System Landscape for Bank Analyzer

February 2004 18


Client Copy

• characteristics: checks are the same as for Characteristic Monitor • technical fields: checks are the same as for IMG activity Register Technical Fields • key figures: checks are the same as for Key Figure Monitor • ODS: checks configuration necessary for Index Functionality • Positions checks configuration necessary for Positions • Business Transactions checks configuration necessary for Business Transactions • Cash Flows checks configuration necessary for Cash Flow generation

7.1.2 Overview of the Segmentation Service Structure Call transaction /BA1/F0_SGS_START and choose Goto Mass Processing

7.1.3 OTS Monitor In the IMG choose Bank Analyzer -> Financial Database -> General Functions for the Financial Database -> Object Transfer Structure -> OTS Monitor

7.2 Derivation Tool The client copy process for derivation rules is very complicated and can lead to errors.

To validate the results of a client copy, compare table TABADRS in client and target client using transaction SCMP.

7.3 Tool „result data base” The term result data base (RDB) denotes either a data base table that contains data or a Bank Analyzer tool. In this paragraph, the tool RDB is meant. The state of the objects generated by the tool (RDB) can be monitored with transaction /BA1/R4_RDBGEN_ALL. This transaction lists all generated objects grouped by applications. The status of each object is represented by a traffic light symbol.

7.4 Tool „module editor“ The module editor after import / postprocessing methods try to generate all active and inactive module versions in the system. Only deactivated version will not be generated. This is necessary for the test functionality offered by this tool.

If the source client contained inconsistent modules, their activation will fail in the target. With report /BA1/P3_REGENERATE, you can try to active single modules or start a mass activation. If this activation fails, it might be due to incomplete or inconsistent customizing. Please analyze these modules in the source client.

The report has a “no generation” flag. In this mode, the report will simply analyze, if generation of modules is necessary.

February 2004 19

Date post:	03-Nov-2014
Category:	Documents
Upload:	mohdnizam31
View:	36 times
Download:	0 times

Client Copy and Data Transport

Documents