Ansicht
Dokumentation
EXIT_RC1AVGE1_001 -
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
You can use this SAP enhancement to define a function module exit that you can use to filter reports that were generated by the system because they could have been affected by a change to a specification or phrase. Reports such as these are referred to in the following text as 'reports with potential changes'. The system then determines whether the filtered reports whether they actually were affected by the changes to the specification or phrase. Filtering reduces the runtime of worklist (WL) generation.
The customer exit can be found in the function group XC1A and is called after the reports with potential changes have been determined, and before the reports are actually checked.
The reports with potential changes are not filtered by default, or in other words, all reports are checked for actual changes.
The enhancement has the following interface parameters:
- X_REPORT_SUB_TAB (Specification -> Report changes)
This table contains all reports that could have changed because of direct changes to specifications. The table contains the following information:
- Technical key of report with potential changes
- Logical key of report with potential changes
- Technical key of changed specification
- Logical key of changed specification
- Change type (S for specification change)
- X_REPORT_SUB_PHRASE_TAB (Phrase -> Specification -> Report changes)
This table contains all reports that could have changed because they were generated for a specification that contains a phrase as a characteristic value that changed since the last time the worklist was generated. The table contains the following information:
- Technical key of report with potential changes
- Logical key of report with potential changes
- Technical key of changed specification
- Logical key of changes specification
- Change type (P for phrase change)
- Technical key of changed phrase
- Logical key of changed phrase
- Language in which the phrase has changed
- Technical key of property in which the phrase is present as a characteristic value
- Technical key of value assignment header record in whose value assignment items the changed phrase is present as a characteristic value.
- Internal characteristic key of characteristic that has the changed phrase assigned as a value
- Characteristic name of characteristic that has the changed phrase assigned as a value
- Sort sequence of value assignment in which the changed phrase is present as a characteristic value
- X_REPORT_SUB_USAGE_TAB (Specification -> Specification -> Report changes)
This table contains all reports that could have changed because they were generated for a specification that contains a specification that has changed, either as a component in a listing or as a reference specification. Multi-level relationships are also taken into account for listings and components (for example, specification A has changed, and specification A is present in specification B as a component. Specification B is contained as a component in specification C. Therefore in addition to the report for specification A, the report for specification B and for specification C has also possibly changed). For the where-used list, only specifications are taken into account that have changed directly (in other words, not due to changes to phrases). The table contains the following information:
- Technical key of report with potential changes
- Logical key of report with potential changes
- Technical key of specification changed indirectly
- Logical key of specification changed indirectly
- Change type (C for specifications that contain the changed specification in a listing or a component and R for specifications that contain the changed specification as a reference specification)
- Technical key of changed specification
- Logical key of changed specification
- Change type 2 (S for specification changes)
- Technical key of the specification used, in other words, the component of the specification in the
listing or of the reference specification. The two following table entries would be the result for the example mentioned above:
| Report with | Spec. | Changed | Component |
| potential | changed | spec. | (of spec. changed |
| changes | indirectly | indirectly) | |
| ---------------------------------------------------------------- | |||
| Report for spec. B | Spec. B | Spec. A | Spec. A |
| Report for spec. C | Spec. C | Spec. A | Spec. B |
- Type of usage (component or reference specification)
- Direct usage indicator
- Technical key of property in which the specification used is present
- Technical key of value assignment in which the specification used is present
- Sort sequence of value assignment in which the specification used is present
- If a specification used is a component, the table also contains various information about the component, such as the component type.
- X_REPORT_SUB_PHRASE_USAGE_TAB (Phrase -> Specification -> Specification -> Report changes)
This table contains all reports that could have changed because they were generated for a specification that contains a specification that has changed, either as a component, in a listing, or as a reference specification. This specification may have changed because a phrase that is assigned to it as a value assignment has changed. The same rules as above apply to the changed specification as regards the where-used list. However, only specifications are taken into account that have changed due to phrase changes. The table contains the following information:
- Technical key of report with potential changes
- Logical key of report with potential changes
- Technical key of specification changed indirectly
- Logical key of specification changed indirectly
- Change type (C for specifications that contain the changed specification in a listing or a component and R for specifications that contain the changed specification as a reference specification)
- Technical key of changed specification
- Logical key of changed specification
- Change type 2 (P for phrase changes)
- Technical key of changed phrase
- Logical key of changed phrase
- Language in which the phrase has changed
- Technical key of property in which the phrase is present as a characteristic value
- Technical key of value assignment header record in whose value assignment items the changed phrase is present as a characteristic value
- Internal characteristic key of characteristic that has the changed phrase assigned as a value
- Characteristic name of characteristic that has the changed phrase assigned as a value
- Sort sequence of value assignment in which the changed phrase is present as a characteristic value
- Technical key of the specification used, or in other words, the component of the specification in the listing or the reference specification.
- Type of usage (component or reference specification)
- Direct usage indicator
- Technical key of property in which the specification used is present
- Technical key of value assignment in which the specification used is present
- Sort sequence of the value assignment in which the specification used is present
- If a specification used is a component, the table also contains various information about the component, such as the component type.
- X_REPORT_SBGV_LAYOUT_TAB (Phrase -> Layout -> Generation variant -> Report changes)
This table contains all reports that could have changed. This is because these reports were generated for a generation variant whose layout changed due to a change to a phrase used in the layout within a Desc./Phrase symbol. The table contains the following information:
- Technical key of report with potential changes
- Logical key of report with potential changes
- Technical key of changed generation variant
- Logical key of changed generation variant
- Change type (V for change to generation variant)
- Document key of layout
- Technical key of changed phrase
- Logical key of changed phrase
- Language in which the phrase changed
Notes:
- Due to the different change types that are taken into account in the five tables, it may be the case that the same report is specified more than once as the report with the potential changes. This means that if a report with potential changes is not to be checked, it must be removed from all five tables. (The tables are processed in the order that they are returned from the customer exit.)
- If you delete an entry from the table X_REPORT_SUB_TAB because you consider that the changes made to the specification are not relevant, we recommend that you delete all entries in the table X_REPORT_SUB_USAGE_TAB in which the specification appears as a changed specification. This is because these are entries that are based on the same specification change.
- If you delete an entry from the table X_REPORT_SUB_PHRASE_TAB because you consider the change to the phrase to be not relevant, we recommend that you also delete all entries in the table X_REPORT_SUB_PHRASE_USAGE_TAB in which the corresponding phrase appears as an indirect reason for change.
CPI1466 during Backup General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 14689 Date: 20240420 Time: 094935 sap01-206 ( 156 ms )
