SAP Note 1601052 - Extended checks for customizing of condition access sequence

Reason and Prerequisites
Extended checks in the customizing view for condition access sequences.
For details please check note 1600482.

Solution
The solution can be implemented by the following steps:
1. Implement the manual preparation steps valid for your release (new messages). This is only necessary before 4.6C.
2. Implement the automatic correction instruction (coding changes).
3. Apply the manual post-processing steps valid for your release.


------------------------------------------------------------------------
|Manual Post-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_APPL SAP Application |
| Release 45B All Support Package Levels |
| Release 46B All Support Package Levels |
| Release 46C Until SAPKH46C62 |
| Release 470 Until SAPKH47036 |
| Release 500 SAPKH50001 - SAPKH50025 |
| Release 600 SAPKH60001 - SAPKH60020 |
| Release 602 Until SAPKH60210 |
| Release 603 Until SAPKH60309 |
| Release 604 SAPKH60401 - SAPKH60410 |
| Release 605 Until SAPKH60507 |
------------------------------------------------------------------------


This note introduces a consistency check routine in the customizing view cluster for maintenance of access sequences.

After the coding changes have been implemented, the check routine has to be added and activated in the view cluster and its variants. This can be achieved by downloading and running the attached report
ZZ_VVC_UPDATE_NOTE_1601052.

The report has to be executed manually in the development system. The report adds routine V_T682_SAVE_CHECK to the save event of certain view cluster variants.


It is rarely possible that error messages arise (e.g. view cluster variants are locked by another user). In such a case the report has to be executed again after the situation that led to the error has been resolved (e.g.
user has unlocked the view cluster variants).
With this run all view cluster variants that were not updated due to the error situation should be updated.

IMPORTANT:
1. The report records the performed changes to a transport request. These changes should be transported together with the automatic coding changes from note 1601052. The report doesn't have to be
executed in the target (productive) systems.
2. It is not necessary to transport report ZZ_VVC_UPDATE_NOTE_1601052 to other systems than the development system.

In detail, report ZZ_VVC_UPDATE_NOTE_1601052 does the following:


a) The list of view cluster variants relevant for your release is determined.

b) The following view cluster variants are updated:
- V_T682
- VVC_T682_MA
Starting from release 4.6B furthermore:
- VVC_T682_VA
Starting from release 4.6C furthermore:
- VVC_T682_CQ
- VVC_T682_FA
- VVC_T682_KA
- VVC_T682_KE
- VVC_T682_MS
- VVC_T682_TP
- VVC_T682_TX
In case the check routine V_T682_SAVE_CHECK is already active for a certain view cluster variant, the view cluster variant is not updated.

c) All changed objects are recorded to a transport request. When you are asked by the report, you have to enter a transport request.

d) After the report was successfully run without any error message, the transport request contains two objects for every updated view cluster variant, e.g.:
R3TR VCLS VVC_T682_MA
R3TR TOBJ VVC_T682_MAC