Kontakt

Ansicht
Dokumentation

RICL_BRF_TRANSPORT_SIMPLE - Copying and Transporting BRF Objects from FS-CM

RICL_BRF_TRANSPORT_SIMPLE - Copying and Transporting BRF Objects from FS-CM

TXBHW - Original Tax Base Amount in Local Currency   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report executes the following activities:

  • Writes transport entries for BRF objects
  • Copies and then writes transport entries for BRF objects

Integration

This report is a preliminary version that will be replaced by a similar BRF version later. It is therefore part of the Claims Management system and not part of the BRF, which belongs to the application basis.

Prerequisites

Features

Selection

The selection screen is divided into the following sections that group related parameters or settings by subject:

  • Main selection
The only field available here is the application class. The permitted values are: ICL (claim) and ICLE (claim bundle).
You also have the option of copying/transporting the BRF application class FLIGHT (flight example).
This is a required entry field.
  • Subselection
Leave the entries for the import status (A) and version (0000) as they are.
  • Object restriction
The BRF objects delivered by SAP (normally) start with digits. Customer and partner objects start with letters.
You can use the radio buttons to control which BRF objects are copied/transported. The following settings are possible:
  • SAP objects only

  • Customer objects only

  • All objects

  • Exclusion group
BRF objects can belong to a group. Sometimes you may not want to copy/transport BRF objects.
If that is the case, group those BRF objects together in one group and enter that group here. The BRF objects in this group will not be copied/transported.
  • Operations
Here you define which operations are executed. The following operations are possible:
  • Copy

All BRF objects in the specified client (this cannot be the current client) that have been determined from the selection criteria are copied to the current client. You can only copy objects within a system. The report used for this must be executed in the target client. The objects that have been copied are added to the target client, and existing objects are changed accordingly. No objects are deleted in the target client. Obsolete and excluded objects are not copied.
  • Identical copy

This is the same as copying except that objects in the target client, which do not have an equivalent in the source client, are deleted in the target client. A transport entry is written for this. Obsolete and excluded objects are also deleted.
  • Transport

Transport entries are written for all BRF objects in the current client that have been determined according to the selection criteria. The current client must be a Customizing client.
You must then enter a transport request when the system asks you for one. The report must run in the system and client from which you want the objects to be exported.
Obsolete and excluded BRF objects are not included in the transport, but are not deleted from the database either.
  • Copy and transport

All BRF objects in the specified client (this cannot be the current client) that have been determined according to the selection criteria are copied to the current client. Transport entries are written for the objects that have been copied. You must then enter a transport request when the system asks you for one. The report must run in the system and client into which you want the objects to be copied and from which you want them to be exported. Obsolete and excluded objects are not copied or transported.
  • Clear and transport

This is the same as transporting, except that obsolete and excluded BRF objects are deleted from the database. Transport entries are written for this.
The system runs a basic consistency check on the BRF objects for all the settings. Obsolete database entries, which are inaccessible to the BRF, are not copied or transported. However, they are not normally deleted (unless you choose clear and transport).
  • Display options
As part of the preparation process for the BRF objects, a list is generated, showing the BRF objects affected up to database level.
The entries are as follows:
  • Entries that are copied/transported (success messages)

  • Entries that are excluded from being copied/transported (warnings and errors)

If a table entry is not copied/transported, the system specifies a reason why the entry has been added to the list of warnings/errors (typical example: Obsolete entry).
You can use the first three indicators to define the scope of the results list.
The fourth indicator determines the level of detail per data record. For each data record, you can have all fields or just the key fields displayed.
  • Additional settings
Note: This is only relevant for SAP.
The objects to be copied can be made anonymous, in other words, the entry for the person responsible for the object can be changed from the user ID to "SAP".
  • Simulation
In simulation mode, all operations that change the database are skipped.

Standard Variants

Output

The results list, which is like a log, consists of two parts:

  • The first part lists all table entries affected when the report runs, provided you have set at least one of the first three indicators in the Display Options section.
  • The second part lists all tables affected with the number of inserts and updates executed. The number of deletes is only hypothetical since no deletes are executed.

Activities

  1. Transport
Start this report in the client whose entries you want to export/transport (source system and client).
  1. Copy
Start this report in the client to which you want to copy the entries of another client in the same system (target client).
  1. Select precisely one of the possible application classes (ICL, ICLE, FLIGHT).
  2. All other parameters/settings are optional. However, select your default settings to make them as general as possible.

Note:

  • If you want to make changes to the database, you must deactivate simulation mode explicitly.
  • If you just want to clear entries (without transporting them), select transport and clear only.
If the current client is not a Customizing client, the system does not ask for a transport request, but clears the objects.
If the current client is a Customizing client, the system asks for a transport request.
  • Make sure that you do not need to transport the deletion entries.
Once you have checked this, you can delete the related transport request after clearing.

Example






rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 8987 Date: 20240520 Time: 051206     sap01-206 ( 119 ms )