Ansicht
Dokumentation
ABENC1_CONSUMER_RULES_STRUCT - C1 CONSUMER RULES STRUCT
CPI1466 during Backup Addresses (Business Address Services)This documentation is copyright by SAP AG.
C1 Contract Rules for Consuming Structures
Non-key elements can be added to or changed in global types as structured DDIC types or CDS entities. Those types can be released APIs themselves or can be used for typing attributes or method parameters of releases classes or interfaces. Also the position of non-key Elements can be changed. This impacts all operations with APIs that rely on a certain number of components of a structure and on their position. Main examples are:
Includes
Including a released structure into another structure.
Possible Problems
Error, when a component is added that already exists.
Mitigation
Include a released structure only by renaming its components with suffixes.
Assignments and Comparisons
Assignments and comparisons between data objects that are typed with the released structured type and data objects that are typed otherwise can occur for:
Possible Problems
Depending on the change all kinds of errors might occur. Especially, the following allowed changes can affect the rules for processing structures fundamentally:
- Adding numerical components to a formerly character-like structure.
- Shifting the positions of numerical or deep components to formerly character-like sections.
Mitigation
No assignments or comparisons between released structures and data objects that are typed otherwise. No usage of otherwise defined structures in ABAP SQL. The various CORRESPONDING mechanisms can be used to mitigate the problem, but they are not failsafe in all situations.
Unstructured Access
Processing the content of a released structure without addressing single components as for example:
- String processing (on complete structure)
Possible Problems
Depending on the change (see above) all kinds of errors might occur.
Mitigation
No processing of released structures without accessing single components.
Field Symbols
Addressing released structures with field symbols by using:
- ASSIGNING addition when working with internal tables
Possible Problems
When the addition CASTING is used, deep components must appear with exactly the same type and position in the assigned structure.
Mitigation
No casting assignment of released structures to field symbols.
RFC
Passing released structures to remote RFMs.
Possible Problems
Deep components are not supported in RFC.
Mitigation
No passing of released structures to remote RFMs.
CPI1466 during Backup rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 4652 Date: 20240511 Time: 204027 sap01-206 ( 51 ms )
