How To Fix SPRX070 - Avoid using tables without surrounding tag for individual lines


SPRX070 - Overview

  • 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.


SPRX070 - Details

  • The SAP error message SPRX070, which states "Avoid using tables without surrounding tag for individual lines," typically occurs in the context of SAP Smart Forms or SAPscript when there is an issue with the structure of the form layout. This error indicates that the system has detected a table structure that is not properly encapsulated within a surrounding tag, which can lead to rendering issues or incorrect output.
    
    Cause: Improper Table Structure: The error is usually caused by a table being defined without the necessary surrounding tags. In Smart Forms, each table should be enclosed within a proper structure to ensure that the individual lines are correctly interpreted. Missing or Incorrect Tags: If the table rows or cells are not properly defined with the required tags, the system may not be able to process them correctly. Form Design Issues: The design of the Smart Form or SAPscript may not adhere to the required standards

    Already have an account? Login here!




Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


SPRX070 - Related SAP Errors

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author