ABAPEXPORT_DATA_CLUSTER_PARAM - EXPORT DATA CLUSTER PARAM

ROGBILLS - Synchronize billing plans   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

EXPORT - parameter_list

Short Reference

Syntax

... {p1 = dobj1 p2 = dobj2 ...}
  | {p1 FROM dobj1 p2 FROM dobj2 ...}
  | (ptab) ... .

Additions

1. ... p1 = dobj1 p2 = dobj2 ...

2. ... p1 FROM dobj1 p2 FROM dobj2 ...

3. ... (ptab)

Effect

A datacluster can be defined statically by a list p1 = dobj1 p2 = dobj2 ... or p1 FROM dobj1 p2 FROM dobj2 ... and dynamically through specification of a bracketed internal table ptab. If the data cluster is too big for the memory, an exception is raised.

Note

To export objects that are referenced by reference variables, use the statement CALLTRANSFORMATION to serialize and then export these objects if the class of these objects implements the interface IF_SERIALIZABLE_OBJECT.

Addition 1

... p1 = dobj1 p2 = dobj2 ...

Addition 2

... p1 FROM dobj1 p2 FROM dobj2 ...

Effect

In case of a static export, the content of the data object dobj is stored under the name pin the cluster. The name of a parameter p can contain no more than 255 characters. The syntax forms p1 = dobj1 p2 = dobj2 ... and p1 FROM dobj1 p2 FROM dobj2 ... are synonymous. You can use all data types except reference types for thedata object dobj or data types that contain reference types as components. If a data object dobj is an internal table with aheader line, thetable body is addressed instead of the header line.

Notes

• We recommend that you use the syntax = as opposed to FROM since = is also used in other ABAP statements to transfer data.
  
• Outside classes and if the name does not contain addressing information such as aninstance component selector or anoffset/length specification, you can use theobsoleteshort form dobj1 dobj2 ... for the static variant. In doing so, all data objects are implicitly stored under their name in the data cluster.
  
  
  

Addition 3

... (ptab)

Effect

In the dynamic case, the parameter list is specified in an index table ptab with two columns.These columns can have any name and must be of type "character". In the first column of ptab,you have to specify the names of the parameters and in the second column the data objects in upper case.If the second column is initial, the name of the parameter in the first column has to match the nameof a data object. The data object is then stored under its name in the cluster. If the first column of ptab is initial, an uncatchable exception is raised.

Note

Outside of classes, you can also use a single-column internal table for parameter_list. This is the dynamic variant of theobsoleteshort form, for which the data objects specified in the table are implicitly stored under their name in the data cluster.

BAL_S_LOG - Application Log: Log header data   PERFORM Short Reference  
This documentation is copyright by SAP AG.


Length: 4675 Date: 20120522 Time: 054209     triton ( 113 ms )