Ansicht
Dokumentation

CRM_SRQM_CHKLST_VER_ - Enable Checklist Versioning

General Data in Customer Master   ABAP Short Reference  
This documentation is copyright by SAP AG.

When you run this report, objects in BRFplus are created that enable checklist versioning.

The Customizing content that is applicable for versioning is stored in decision tables in BRFplus.

You need to select your checklist versioning strategy. This strategy is based on whether you will use Transport Requests and whether you will use the Versioning Mode as Versioning On or Versioning Triggered by Transport.

Note: It is difficult to change your checklist versioning strategy once you have run the report.

• Versioning Mode: You select either Versioning On or Versioning Triggered by Transport.

• Transport Request: It is mandatory for you to enter a transport request if you select Versioning Triggered by Transport but it is optional if you select Versioning On for the Versioning Mode.

Versioning On: This refers to the BRFplus concept that in addition to the initial version that exists for each object, you can create a new inactive version whenever a previously activated object is changed and saved. The cumulated changes to the object version are frozen in that version once it is activated. You can select this Versioning Mode either with or without a Transport Request.

• If your list of checklists is different across your systems, select Versioning On without a Transport Request. With this option, you don't have to transport the BRFplus content between systems. You can simply synchronize and activate your latest customizing changes in each system with BRFplus using the Synchronize Checklist Customizing report.

• If you use Versioning On with a Transport Request, you can transport your Customizing changes and BRFplus content between systems, starting with your master system. If you use this versioning strategy, you do not need to run the Synchronize Checklist Customizing report in each system.

Versioning Triggered by Transport: You should only select Versioning Triggered by Transport if you have one master system where you make all your customizing changes for your checklists and you want to officially rollout a new version at the moment you transport the BRFplus content. This option can be used when the list of checklists and their customizing in SPROare exactly the same between systems. Using this option means that in addition to transporting your customizing changes from SPRO, you will also be transporting your Customizing content in BRFplus between systems. This transport-dependent versioning strategy refers to the BRFplus concept where a version is frozen not by activation, but by transporting the activated object to another system. In other words, the same version can be activated several times as long as it is not transported.

Generate First Version in BRF+: This checkbox is only for your information. The first active snapshot of your Customizing is automatically generated with this report when the report creates the BRFplus decision tables.

• If you are using a versioning strategy with the Versioning On mode and you don't provide a Transport Request, the versioning of your Customizing is local and the first snapshot is created right away. With a transportable application in this versioning mode, you must transport the first version that is also created right away by the report before applying any new changes to your customizing.

• If you are using a versioning strategy with the Versioning Triggered by Transport mode, versioning depends on your transport. This report creates the first version of your Customizing right away in your master system. You must transport this first version before applying new changes.

You have three versioning strategy options.

1. If you do not provide a Customizing Transport Request, you must select the Versioning Mode as Versioning On. If you are using this strategy, you will create a local BRFplus application that will be assigned to your local $TMP development package. The BRFplus objects and content will not be transportable from one system to another with a transport request. You must run this report in each system to create your local BRFplus application.
2. If you provide a Customizing Transport Request and select the Versioning Mode as Versioning On, you will be creating a transportable BRFplus application. If you are using this strategy, you will be able to transport the BRFplus content and objects between systems, therefore you do not need run this report on all of them. You use your transport to deploy your BRFplus objects and content instead.

The versioning, however, will not be controlled by transporting the BRFplus content. The versioning is determined by the activation of your changes using the Synchronize Checklist Customizing report.

1. If you provide a Customizing Transport Request and select the Versioning Mode as Versioning Triggered by Transport. You can transport your BRFplus content at the same time as your customizing changes. You must transport your first version in BRFplus before applying new changes. Keep in mind that your subsequent new versions will take effect the moment you release your customizing transport request with all of the changes that you synchronized with Synchronize Checklist Customizing report.

If you know your content differs from one system to another, you will probably transport irrelevant customizing content that does not apply to all systems or you will be missing customizing entries specific to some systems. Be aware that this might cause some inconsistencies.

This report can take some time to execute.

Caution: Do not change the data in BRFplus directly. Always use the provided reports.

After running this report, you can view your application in BRFplus by running transaction brf+ and searching for application CKL.

BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 7464 Date: 20240523 Time: 174201     sap01-206 ( 155 ms )