Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-RA (Application Component) Risk Analysis⤷
JBRC (Package) Customizing for SAP Banking Risk Management
IMG Activity
| ID | _JBWO | Transport Report |
| Transaction Code | S_KK4_13000218 | IMG Activity: _JBWO |
| Created on | 19990830 | |
| Customizing Attributes | _JBWO | Transport Report |
| Customizing Activity | _JBWO | Transport Report |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _JBWO |
In this step, you create a transport request for transporting into a target system.
After you have made your settings, you can collect all the
objects which belong to these settings (table entries, data elements, domains, tables etc.) in a transport request.
The source system collects all the dependent objects and puts them in a transport request. After they have been imported into the target system, the Data Dictionary objects are automatically activated.
Note that you have to regenerate the RM data area environment after the import, even though the status of the RM data area is 'active' and no further actions have to be carried out.
Requirements
The source and target systems must have the same SAP release (maintenance upgrade).
Recommendation
In this step, you create a transport request which is based on the current settings. For this reason, you should not add any new objects or make any other settings while the transaction is running. It is possible to perform the following two steps separately: 'Create transport request' (what is to be transported) and 'Export' (database copy). If you make further settings between the time you create the transport request and perform the export, the changed objects will be processed, however, no new objects will be accepted in the transport request. This can lead to inconsistencies in the target system after the import.
You are therefore recommended not to make further changes to settings between these two steps.
When the objects are collected for the transport request, the system cannot test which of the objects to be exported already exist in the target system. This means that objects can sometimes be imported and overwrite objects created in the target system. To avoid such problems, you are recommended to set up a single source system from where you can send to one or more target systems. However, you should not create any new objects (RM data areas, characteristics, key figures etc.) in the target systems.
Activities
- Choose a transport object class.
- Enter a transport request.
- Choose the objects to be transported.
- Choose the dependent object classes.
- Transport the request.
Further notes
When you are transporting reports note that the RM data area itself is a dependent object. Normally you should only select the checkboxes 'Report' and possibly 'Form'.
Reports whose names contain special characters cannot be transported for technical reasons. To transport such reports, you need to create a new report without special characters using the original report as a reference (Copy from).
To guarantee the consistency of the entire system, some of the tables and table entries which are referenced in RM are not transported. Only those ABAP/4 development workbench objects generated in RM and the table entries administrated in RM and changed during configuration are transported. Any settings which can be made in RM but which also have effects outside the application are not transported. This is to protect the consistency of the target system.
The following list contains the objects which are not transported.
- Master data tables for characteristics which were not freely defined for the RM data area (characteristics selected from master data tables)
- Fiscal year variants
- Authorization objects
- The Data Dictionary structure ZAUTHCUST (or authorization objects which are the result of customer modifications)
- Transaction data is not transported either.
Transport Objects in the Individual Object Classes
The following transport objects (listed with their dependent object classes) may be transported:
- Reports
- Forms
- Key figures
- Transport of reports
Note: Only choose the dependent object class 'Form', not 'RM data area'.
The following are transported:
- Report definitions
- Characteristic groups for the information system.
- Header and item lines
- Transport of forms
The following are transported:
- Form definitions with (or without) key figures
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | _JBWO | 0 | I070004703 | Market Risk Analysis |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | JBWO | IS-B:RM | Transport Report |
History
| Last changed by/on | SAP | 19990831 |
| SAP Release Created in |
