Internal Tables - comp1 comp2 ... Individual components of the lines of internal tables are addressed in a sequence of statements for processing internal tables. If not stated otherwise, the names comp1 comp2... have the following syntax:
Effect There are the following alternatives for component specification:
The name comp_name of a component can be specified directly.
If the data type of the components is character-type and flat, you can, using the same procedure as for subfield access, append an offset/length specification +off(len) to the name of the component to access the subareas of the component.
If the component is an object reference, the object component selector -> can be used to access all visible attributes attr of the referenced object. In this case, a component can be listed more than once. A bracketed character-type data object name can be specified, which contains the name of the component in upper case when the statement is executed.
The name of the component in name can contain an offset/length specification. It is not possible to specify the object component selector for access to attributes.
If name only contains blank characters, this component specification is ignored when the statement is executed. If name contains a component that does not exist, an untreatable exception is raised. As of release 6.10, the name of the component in name can also be in lower case. For tables with a non-structured line type, the complete table row can be addressed as a component using pseudo component table_line. Before release 6.10, no other component except for table_line could be addressed.
As of release 6.10, other components can be specified in addition to table_line. This is necessary, for example, if the line type of internal table is an object reference, and the value of the reference and the value of an attribute of the object are to be specified at the same time.
Note For tables with a non-structured line type, the only component that can be addressed is the pseudo component Ptable_line.
ARTICLE ( Version: 0042)
Internal Tables - comp1 comp2 ... Individual components of internal table rows are addressed in a range of statements for processing internal tables: If not stated otherwise, the following syntax applies to the labels comp1 comp2...:
Effect The following alternatives are available for specifying components:
You can specify the name of a component, comp_name, directly. If the data type of the components is character-like and flat, an offset/length +off(len) can be appended to the name of the component (as in a subfield access) to access subareas of the component. Only numeric literals or constants can be specified for off and len. If the component is structured, you can use the structure component selector - to access the sub_comp components of the substructure. If the component has a reference type, you can use the object component selector -> to access all visible attributes attr of the referenced object. In this case, a table component can be listed more than once. A parenthesized character-like data object name can be specified, which contains the name of the component (uppercase) when the statement is executed. The name of the component in name can contain an offset/length. You cannot specify the object component selector to access attributes. name is not case-sensitive. If name contains only blanks, this component is ignored by the statement. If name contains a nonexistent component, a non-handleable exception is raised. If the table has a non-structured row type, the whole table row can be addressed as a component using the pseudo component table_line. You can specify further components besides table_line. You need to do this, for example, if the row type of the internal table is an object reference and you want to specify the value of the reference and the value of an attribute of the object at the same time.
Notes If the table has a non-structured row type, the pseudo component table_line can be addressed as the only component. The components specified must not be elementary. A Customizing include cannot be specified as a component as long as it is empty.
ARTICLE ( Version: 0045)
Internal Tables - comp1 comp2 ... Individual components of internal table rows are addressed in a range of statements for processing internal tables: If not stated otherwise, the following syntax applies to the labels comp1 comp2...:
Effect The following alternatives are available for specifying components:
You can specify the name of a component, comp_name, directly. If the data type of the components is character-like and flat, an offset/length +off(len) can be appended to the name of the component (as in a subfield access) to access subareas of the component. Only numeric literals or constants can be specified for off and len. If the component is structured, you can use the structure component selector - to access the sub_comp components of the substructure. If the component has a reference type, you can use the object component selector -> to access all visible attributes attr of the referenced object. In this case, a table component can be listed more than once. A parenthesized character-like data object name can be specified, which contains the name of the component (uppercase) when the statement is executed. The name of the component in name can contain an offset/length. You cannot specify the object component selector to access attributes. name is not case-sensitive. If name contains only blanks, this component is ignored by the statement. If name contains a nonexistent component, a non-handleable exception is raised. If the table has a non-structured row type, the whole table row can be addressed as a component using the pseudo component table_line. You can specify further components besides table_line. You need to do this, for example, if the row type of the internal table is an object reference and you want to specify the value of the reference and the value of an attribute of the object at the same time.
Notes If the table has a non-structured row type, the pseudo component table_line can be addressed as the only component. The components specified must not be elementary. If possible for the data type (character-like and flat), an offset/length specification can also include adjacent components. A Customizing include cannot be specified as a component as long as it is empty.
ARTICLE ( Version: 0048)
Internal Tables - comp1 comp2 ... Individual components of internal table rows are addressed in a range of statements for processing internal tables. If not stated otherwise, the following syntax applies to the labels comp1 comp2...:
Effect The following alternatives are available for specifying components:
Directly specifying the name comp_name of a component. If the data type of the components is character-like and flat, an offset/length +off(len) can be appended to the name of the component (as in subfield access) to access subareas of the component. Only directly specified numbers or constants can be specified for off and len. If the component is structured, you can use the structure component selector - to access the sub_comp components of the substructure. If the component has a reference type, you can use the object component selector -> to access all visible attributes attr of the referenced object. In this case, a table component can be listed more than once. Specifying a parenthesized character-like data object name, which contains the name of the component (uppercase) when the statement is executed. The name of the component in name can contain an offset/length. The object component selector can also be specified for accessing attributes, however only those attributes can be addressed that are also known statically. name is not case-sensitive. If name only contains blank spaces, this component specification is ignored when the statement is executed. If name contains a non-existent component, a non-handleable exception is raised. Specifying the pseudo component table_line to address the whole table row as a component.
Notes You can specify further components besides table_line. You need to do this, for example, if the row type of the internal table is an object reference and you want to specify the value of the reference and the value of an attribute of the object at the same time. If the table has a non-structured row type, the pseudo comment table_line can be addressed as the only component. The components specified must not be elementary. If the data type allows it (character-like and flat), an offset/length can also include neighboring componentss A Customizing include must not be specified as a component if it is empty.
ARTICLE ( Version: 0050)
Internal Tables - comp1 comp2 ... Individual components of internal table rows are addressed in a range of statements for processing internal tables. If not stated otherwise, the following syntax applies to the labels comp1 comp2...:
Effect The following alternatives are available for specifying components:
Directly specifying the name comp_name of a component. If the data type of the components is character-like and flat, an offset/length +off(len) can be appended to the name of the component (as in subfield access) to access subareas of the component. Only directly specified numbers or constants can be specified for off and len. If the component is structured, you can use the structure component selector - to access the sub_comp components of the substructure. If the component has a reference type, you can use the object component selector -> to access all visible attributes attr of the referenced object. In this case, a table component can be listed more than once. Specifying a parenthesized character-like data object name, which contains the name of the component (uppercase) when the statement is executed. The name of the component in name can contain an offset/length. The object component selector can also be specified for accessing attributes, however only those attributes can be addressed that are also known statically. name is not case-sensitive. If name only contains blank spaces, this component specification is ignored in the execution of the statement. If name contains a non-existent component, a non-handleable exception is raised. Specifying the pseudo component table_line to address the whole table row as a component.
Notes A component cannot be specified more than once. However, you can specify further components alongside table_line. You need to do this, for example, if the row type of the internal table is an object reference and you want to specify the value of the reference and the value of an attribute of the object at the same time. If the table has a non-structured row type, the pseudo comment table_line can be addressed as the only component. The components specified must not be elementary. If the data type allows it (character-like and flat), an offset/length can also include neighboring componentss A Customizing include must not be specified as a component if it is empty.
ARTICLE ( Version: 0054)
Internal Tables - comp1 comp2 ... Individual components of internal table rows are addressed in a range of statements for editing internal tables and in table expressions. If not stated otherwise, the following syntax applies to the labels comp1 comp2...:
Effect The following alternatives are available for specifying components:
Directly specifying the name comp_name of a component. If the data type of the components is character-like and flat, an offset/length +off(len) can be appended to the name of the component (as in subfield access) to access subareas of the component. Only directly specified numbers or constants can be specified for off and len. If the component is structured, the structure component selector - can be used to access the sub_comp components of the substructure. If the component has a reference type, the object component selector -> can be used to access all visible attributes attr of the referenced object. In this case, a table component can be listed more than once. Specifying a parenthesized character-like data object name, which contains the name of the component (uppercase) when the statement is executed. The name of the component in name can contain an offset/length. The object component selector -> can be specified in name to read attributes, but only those attributes can be addressed that can be identified statically. name is not case-sensitive. If name only contains blanks, this specified component is ignored when the statement is executed. If name contains a non-existent component, a non-handleable exception is raised. Specifying the pseudo component table_line to address the whole table row as a component.
Notes A component can only be specified more than once if it has a reference type. Further components, however, can be specified alongside table_line. This is necessary, for example, if the row type of the internal table is an object reference and the value of the reference and the value of an attribute of the object are to be specified at the same time. If the table has a non-structured row type, the pseudo comment table_line can be addressed as the only component. The components specified must not be elementary. If the data type allows it (character-like and flat), an offset/length can also include adjacent components A Customizing include must not be specified as a component if it is empty. Message text extract from SAP system. Copyright SAP SE.
Search for further information about these or an SAP related objects
Comments on this SAP object
What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!