Skip to content

ABAP Keyword Documentation →  ABAP - Reference →  Obsolete Language Elements →  Obsolete Processing of External Data →  Obsolete Access to Data Clusters 

IMPORT - obs_id

Short Reference

Other versions: 7.31 | 7.40 | 7.54

Obsolete Syntax

... MAJOR-ID id1 [MINOR-ID id2] ...

Effect

Outside of classes, the addition ID of the statement IMPORT FROM DATABASE can be replaced by these additions when database tables are imported. When id1 and id2 are specified, the same rules apply as for id.

A data cluster is imported whose ID in the first part matches the value of id1. If MINOR-ID id2 is also specified, the data cluster is imported whose ID in the second part (at the positions after the number of characters specified in id1) is greater than or equal to the value in id2. The search is canceled once the first match is found.


Notes

  • When using id2, note that this data object must either only contain digits or only letters, since mixed forms can produce differing search results (depending on the platform).
  • MAJOR-ID and MINOR-ID are obsolete, since the specified ID is not unique. The ID can be created in the program instead.


Example

If a data cluster with the ID "Sausage" was exported, this statement is found when MAJOR-ID "Sau" is specified. It is also found if "ab" is specified as MINOR-ID, but it is not found if "yz" is specified as MINOR-ID.