Message type: E = Error
Message class: SPRX - Proxy Generation
Message number: 072
Message text: Item is part of recursion (see long text for additional information)
The type contains recursions. This means that a type references itself
(possibly indirectly).
Example:
A packing unit is described by its length, width, height, and content.
The content can also consist of packing units.
<complexType name="PackingUnit">
<sequence>
<element name="length" type="int"/>
<element name="width" type="int"/>
<element name="height" type="int"/>
<element name="content" type="PackingUnit"
maxOccurs="unbounded"/>
</sequence>
</complexType>
In ABAP, recursively defined structures are not possible.
Currently, the only solution is to replace a recursive reference by a
reference to the data element XSDANY, so that the structure looks like
this:
Dictionary structure PACKING_UNIT
Field LENGTH TYPE INT4
Field WIDTH TYPE INT4
Field HEIGHT TYPE INT4
Field CONTENT TYPE PACKING_UNIT_CONTENT_TAB
Dictionary table type PACKING_UNIT_CONTENT_TAB
Line type XSDANY (not TYPE PACKING_UNIT)
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The programmer must fill this XSDANY field correctly. For moreThe system displays a warning for each type which is part of a
recursion. The type cannot be activated if the DDIC type to be
generatedalso contains a recursion.
To be able to activate the proxy you have to "break" the recursion by
mapping at least on chain of each recursion to XSDANY. This is done by
setting the flag <DS:DE.PRX_USE_XSDANY>Untyped mapping</> in the detail
vie of the corrosponding data type.
Error message extract from SAP system. Copyright SAP SE.
SPRX072
- Item is part of recursion (see long text for additional information) ?The SAP error message SPRX072, which states "Item is part of recursion," typically occurs in the context of product structure or bill of materials (BOM) management. This error indicates that there is a recursive relationship in the item hierarchy, meaning that an item is referencing itself directly or indirectly, which can lead to infinite loops in processing.
Cause: Recursive BOM Structure: The most common cause is that the BOM or product structure has been defined in such a way that an item references itself or is part of a circular reference with other items. Incorrect Configuration: This can happen due to incorrect configuration or data entry when creating or modifying BOMs or product structures. Data Migration Issues: If data has been migrated from another system, it may have introduced inconsistencies or recursive relationships.
Solution: Review BOM Structure: Check the BOM or product structure for any items that reference themselves or create a circular reference. You can
Get instant SAP help. Sign up for our Free Essentials Plan.
SPRX071
Keys and uniqueness relationships ignored
What causes this issue? The interface description uses one of the following language elements: <key> <keyref> <unique> <selector...
SPRX070
Avoid using tables without surrounding tag for individual lines
What causes this issue? The interface description defined a repetition group (a strictly table-type structure): <sequence maxOcxurs="unbounde...
SPRX073
Object not (yet) activated (DDIC log => detail button)
What causes this issue? There were activation errors in the DDIC.System Response The system issues an error message and will not allow you to contin...
SPRX074
Object still being used; cannot delete object
What causes this issue? Unable to delete object because references still exist.System Response The object in question (type/name) <ZH>&V1&...
Click on this link to search all SAP messages.