Kontakt

Ansicht
Dokumentation

BRF_TRANSPORT_GEN - Program BRF_TRANSPORT_GEN

BRF_TRANSPORT_GEN - Program BRF_TRANSPORT_GEN

RFUMSV00 - Advance Return for Tax on Sales/Purchases   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this report to

  • Copy BRF objects
  • Write BRF objects to transport requests
  • Copy BRF objects and then write to transport requests

You can use this report as an alternative to report BRF_TRANSPORT_SIMPLE.

Integration

Prerequisites

  • For each table there must be a transport class that implements interface IF_TRANS_GEN_BRF.
  • You can change the transport classes in one of the following ways:
  • By means of this report

  • By means of report BRF_GENERATE_TRANSPORT_CLASSES

You can schedule this report periodically.

Features

Selection

The selection screen comprises the following sections:

Enter the application class.

Leave the fields Import Status and Version unchanged.

You can use the Exclude Group field to remove an object group from the selection..

Specify which BRF objects you want to copy or transport.

You can make the following settings:

  • Only SAP Objects
  • Only Customer Objects
  • All Objects

Specify which operation you want to execute. In addition, enter the source client for the relevant operation.

The following operations are possible:

  • Copy
The system copies all selected BRF objects of the source client to the target client. The system checks whether a BRF object already exists in the target client. Depending on the result of the check, the system performs one of the following activities:
  • If the BRF object exists, the system overwrites this BRF object.

  • If the BRF object does not yet exist, the system creates this BRF object in the target client.

Notes:
  • Run the report in the client to which you want to copy the BRF objects (target client).

  • You can only copy within one system.

  • In contrast to Identical Copy, the system does not delete any BRF objects in the target client.

  • The system does not consider any orphaned or excluded table entries.

'Orphaned' means that there is an entry for a BRF object in the specialization table but not in the main table. This means that the BRF object is no longer used.
  • Identical copy
This operation has the same significance as Copy, but with the following difference:
If the target client contains BRF objects that do not exist in the source client, the system deletes these BRF objects. With Copy, the system does not delete these BRF objects.
So 'Identical Copy' means that the status of the BRF objects in the source and target client is identical.
  • Copy and Rename
This operation has the same significance as Copy, but with the following difference:
The system copies all selected objects to a new application class. You must have already created this cross-client application class. An identical copy is made, in other words, any existing objects are deleted.
  • Transport
The system writes the selected BRF objects of the target client into a transport request.
Notes:
  • Run the report in the system and client from which you want to transport the objects.

  • The client must be a Customizing client.

  • The system does not transport orphaned or excluded BRF objects. These BRF objects remain in the database.

  • Copy and Transport
This is a combination of the two operations Copy and Transport.
Run the report in the system and client to which you want to copy the objects or from which you want to transport the objects.
  • Clear and transport
The system deletes orphaned (see also the last note under Copy) or excluded BRF objects from the database and writes them into a transport request.

If you set the Simulation indicator, the system ignores all operations that lead to changes in the database. This is also valid for generation of transport classes.

Standard Variants

Output

The list of results comprises the following parts:

  • On the left, the system displays all tables in which the operation was executed.
The system also displays the following additional information:
  • For each table Insert/ Update/ (Delete), the number of inserted/updated/deleted entries

  • the number of data sets that were read from the database at the start (old)

  • the number of datasets that were actually executed for the operation (current)

  • If you double-click to select a table on the left of the screen, the system displays additional information on the Insert/ Update/ (Delete) entries on the right of the screen.

Activities

The operations of the report are executed by ABAP classes. You must generate these classes in each system. The following variants are available:

  • Generate
The system executes the generation in dialog mode.
Caution: Depending on the number of tables, the generation can take several minutes.
  • Generation in background
The system executes the generation in background processing.
  • You can also generate the transport classes periodically.
To do so, schedule report BRF_GENERATE_TRANSPORT_CLASSES in the Background Job Scheduler.

The generated classes have the following naming convention: ZBRF<Table Name>

Example






RFUMSV00 - Advance Return for Tax on Sales/Purchases   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 8219 Date: 20240520 Time: 061905     sap01-206 ( 88 ms )