SPRX070 - Avoid using tables without surrounding tag for individual lines


SAP Error Message - Details

  • Message type: E = Error

  • Message class: SPRX - Proxy Generation

  • Message number: 070

  • Message text: Avoid using tables without surrounding tag for individual lines

  • Show details Hide details
  • What causes this issue?

    The interface description defined a repetition group (a strictly
    table-type structure):
    <sequence maxOcxurs="unbounded">
    <choice maxOcxurs="unbounded">
    <group maxOcxurs="unbounded">
    We do not recommend this definition because the individual table rows in
    the XML instance do not have a surrounding tag.

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    Example
    The XML schema contains:
    <element name="Struc">
    <complexType>
    <sequence>
    <element name="Field1" type="string"/>
    <sequence maxOccurs="unbounded">
    <element name="Field2" type="string" minOccurs="0"/>
    <element name="Field3" type="string" minOccurs="0"/>
    </sequence>
    <element name="Field4" type="string"/>
    </sequence>
    </complexType>
    </element>
    A valid XML fragment is as follows:
    <Struc>
    <Field1>xxx</Field1>
    <Field2>yyy</Field2>
    <Field3>zzz</Field3>
    <Field2>xxx</Field2>
    <Field3>yyy</Field3>
    <Field4>zzz</Field4>
    </Struc>
    In this scenario there are several problems for the handling of the
    mapping between ABAP structures and xml data:
    1. If all fields are optional it is impossible to derive all table rows
    uniquely. In the above example, the ABAP table could have 2, 3 or 4
    lines.
    2. If some of the optional fields are missing, the simple transformation
    used for mapping the xml to ABAP will have problems determining when the
    table lines are finished and might even lose the information of <Field4>
    <(>,<)><ZH> ie there is a risk of dataloss. </>
    3. In some situations, e.g. with tables inside tables, some of which
    have no line tags, <ZH>endless loops </>may occur inside the simple
    transformation.

    System Response

    A warning appears for this type.

    How to fix this error?

    Define the repetition groups with
    <element maxOccurs="unbounded" ...>

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message SPRX070 - Avoid using tables without surrounding tag for individual lines ?




    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Feature Free Access Free Trial
Basic SAP error explanation T-Code Explanation T-Code Explanation 2
Step-by-Step Usage Guide Step-by-Step Step-by-Step 2
Interactive SAP Coach Assistance Interactive SAP Interactive SAP 2
AI Troubleshooting for T-Code Errors AI Troubleshooting AI Troubleshooting 2

Related SAP Error Messages

Click the links below to see the following related messages:


SAP messages fall into 3 different categories: Error messages (message type = E), Warnings (W) or Informational (I) messages.

An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant