Kontakt

Ansicht
Dokumentation

BRF_COPY_IMPL_CLASSES - Program BRF_COPY_IMPL_CLASSES

BRF_COPY_IMPL_CLASSES - Program BRF_COPY_IMPL_CLASSES

BAL_S_LOG - Application Log: Log header data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

When you create a new application class, you can use this report as follows:

  • You can use the report to copy the implementing classes (expression types, action types, and so on) of the BRF from application class SYSTEM to the new application class.
  • You can use the report to copy the implementing classes (see above) and at the same time create the new application class directly.
This means that when you implement the BRF, you can group several steps into one.

If you have already created your application class, you can use this report as follows:

  • You can use it to add other implementing classes to an application class that has already been created.
Notes:
  • Ensure that you only specify object types that are missing in the application class. Otherwise, the system overwrites any existing object types (in their original configuration).

  • You cannotuse this report to delete implementing classes.

Integration

  • This report is an important part of the BRF.
It does not make sense to implement the BRF for a new application class without this report.
  • You can fine-tune all the settings that you make here later on when you maintain the relevant object types.

Prerequisites

  • You need an application based on ABA 700.
  • You have created corresponding transport requests.
Note: If transport issues are not relevant for you, you can ignore the following information.
  • If you want to create the cross-client part of an application class as well, you must have created a transport request for development objects (Workbench request) in the current client.

If you do not have any Workbench request, you must use transaction BRFAPL01, as previously, to create the cross-client part of the application class in a suitable client (typically in the development client).
  • You must have created a Customizing request for all other objects.

Note: It is often the case that you cannot do both these things in the same client, because the development landscape requires a development client and a separate Customizing client.

Features

Selection

Make the following settings here:

  • Enter the required application class.
  • Specify whether the system should also create the cross-client part of the application class (flag Create Cross-Client Appl.Class). In this case, you must enter a name for the application class in the Short Textfield.
  • Specify whether the system should also create the client-specific part of the application class (flag Create Client-Spec.Appl.Class).

The following combinations are possible for setting the two flags Create Cross-Client Appl.Class and Create Client-Spec.Appl.Class:

  • You set neither of the two flags.
In this case, both the cross-client part (using transaction BRFAPL01) and also the client-specific part (transaction BRFAPC01) must have already been created.
This is the standard behavior.
  • You set both flags.
In this case, neither the cross-client part nor the client-specific part must have already been created.
This is the enhanced behavior.
  • You only set the flag Create Client-Spec.Appl.Class.
In this case, the cross-client part must have already been created.

Note: Theoretically, you could just set the flag Create Cross-Client Appl.Class. However, this setting does not make sense as this constellation should not occur in practice.

  • Sub-section Source Client for Object Types
In the Source Client field, the system shows the client of the source system (of the current system) from which the system copies the implementing classes (object types) of application class SYSTEM to the current client.
If this default setting is not correct, you can change the default setting and enter the required client.
  • Sub-section Expression Types
Here you define which expression types you want to copy.
Note:
This flag is set by default with all expression types except for:
  • Simple Formula
Use the SAP Formula instead of the simple formula.
  • Reference-Like Expression
Only use the expression type Reference-Like Expression if you also use the two action types BOR Event and Start Workflow.
  • Sub-section Action Types
Here you define which action types you want to copy.
Note:
By default, this flag is set with the action types Function module call and Message output. Only set the flag with other action types if you really need the action type in question.
  • Sub-section Event Type
Here you can define whether the system should automatically create an object type for events.
The individual flags have the following significance:
  • None

The system does not create any event type.
  • Standard class

The system creates event type 1EVENT and in doing so uses the standard maintenance class and the standard runtime class for events. The system displays these standard classes in the fields Maintenance Class for Events and Runtime Class for Events.
  • Application-specific class

You have created your own maintenance class and/or your own runtime class for events. Store these classes in the fields Maintenance Class for Events and Runtime Class for Events.
The system then creates event type 1EVENT according to the classes you defined.
  • Sub-section Rule Types
Here you can define whether the system should automatically create an object type for rules as well.
The individual flags have the following significance:
  • None

The system does not create any rule type.
  • Standard class

The system creates rule type 1RULES and in doing so uses the standard maintenance class for rules. The system displays this standard class in the field Maintenance Class for Rules.
  • Application-specific class

You have created your own maintenance class for rules. Store this class in the field Maintenance for Rules.
The system then creates rule type 1RULES according to the class you defined.
  • Sub-section Rule Set Types
Here you can define whether the system should automatically create an object types for rule sets as well.
The individual flags have the following significance:
  • None

The system does not create any rule set type.
  • Standard class

The system creates rule set type 1RULESET and in doing so uses the standard maintenance class for rule sets. This system displays this standard class in the fieldMaintenance Class for Rule Sets.
  • Application-specific class

You have created your own maintenance class for rules. Store this class in the field Maintenance Class for Rule Sets.
The system then creates rule set type 1RULESET according to the class you defined.
  • Sub-section Technical object types
Leave the default settings unchanged.

Here you can define whether the report should only be executed in a simulation run, or in a realtime run.

Standard Variants

No variants are delivered, and so there is no explicit standard variant.

Output

If you also create the cross-client part of an application class, the system displays a dialog screen in which you must assign a package. You might also have to assign a Workbench request.

With the other objects you might have to assign a Customizing request.

The system displays a list with the table entries that have been added. These have the same meaning as the added object types.

If an error occurs during the report run, the system outputs a corresponding error message.

Activities

  1. Check the standard settings and adjust them to your requirements.
  2. Start the report.

Example

  • You want to create a new application class (Z_MYAPPLCLASS, for example) that refers completely to BRF standard objects.
In this case, make the following settings:
  1. Enter application class Z_MYAPPLCLASS.
  2. Set the two flags Create Cross-Client Appl.Class and Create Client-Specific Appl.Class.
  3. Enter a short text for the application class.
  4. In the sections Event Types, Rule Types and Rule Set Types, set the flag Standard Class.
Leave all other settings unchanged.
  • You want to furnish an application class (like Z_MY_TINY_CLASS) with restricted functional scope. The cross-client and client-specific parts of the application class have already been defined. You have already created your own runtime class for your BRF events (ZCL_MY_EVENT) and your own maintenance class for rules (ZCL_MY_RULES_MNT). You do not want to use rule sets.
In this case, make the following settings:
  1. Enter application class Z_MY_TINY_CLASS.
  2. With the expression types, only set the flags Constant, SAP Formula and Simple Access, in other words, remove the flag with all other expression types.
  3. In the section Event Types, set the flag Application-Specific Classes and enter ZCL_MY_EVENT as the runtime class.
  4. In the section Rule Types, set the flag Application-Specific Class and enter ZCL_MY_RULES_MNT as the maintenance class.






ROGBILLS - Synchronize billing plans   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 13838 Date: 20240531 Time: 113702     sap01-206 ( 133 ms )