Skip to content

ABAP Keyword Documentation →  ABAP − Reference →  Processing External Data →  Data Cluster →  EXPORT 

EXPORT - Internal Additions

Other versions: 7.31 | 7.40 | 7.54

Internal Additions

Other versions: 7.31 | 7.40 | 7.54

These additions are for internal use only. Do not use them in application programs.

Extras

1. ... CODE PAGE HINT cp

2. ... USING subr[(prog)]

Addition 1

... CODE PAGE HINT cp

Effect

In cp, a code page from database table TCP00 can be specified that overwrites the ID saved automatically.

Addition 2

... USING subr[(prog)]

Effect

This addition can be specified for EXPORT TO DATABASE if a table work area dbtab is declared for the relevant database table using TABLES. The addition FROM wa is not permitted. The data is not exported to the database table. Instead, the subroutine subr is called for each row that would be written to the database without this addition. In the subroutine, the data can be accessed that would otherwise be written to the database table in the table work area dbtab.

The subroutine must either be defined in the same program or in a program, prog, specified explicitly. Its name must be prefixed with the name of the database table ("dbtab"). The subroutine must have a USING parameter of type any, which is currently not supplied.


Notes

  • For external use, TO INTERNAL TABLE is provided instead of TO DATABASE ... USING.
  • Specifying an external program prog is the same as the obsolete variant of PERFORM.
  • The tables used as the export/import tables must have structures for data clusters in multiple rows, since TABLES cannot be used for deep structures.


Example

See IMPORT - Internal Additions