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, you can replace the ID addition in the IMPORT FROM DATABASE statement with these additions when importing database tables. When you specify id1 and id2, the same rules apply as for id.

The data cluster with an ID in which the first part matches the value of id1 is imported. If MINOR-ID id2 is also specified, the data cluster with an ID in which the second part (in the positions after the number of characters specified in id1) is larger or equal to the value of id2 is imported. The search ends once the first matching ID is found.


Notes

  • When using id2, it is important to note that this data object must contain either only digits or only letters, because mixed forms can lead to differing search results (depending on the platform).
  • The use of MAJOR-ID and MINOR-ID is obsolete because the specified ID is not unique. The required ID can be generated by a program instead.


Example

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