Upload
vikasbumca
View
215
Download
0
Embed Size (px)
Citation preview
7/30/2019 Logical Database2
1/9
LDB2
EVENTS
7/30/2019 Logical Database2
2/9
LDB Events
1. PUT node.2. PUT .
Effect You can only use this statement in the database
access program of a logical database whose
structure contains the node node. You use it topass data read by the logical database to its user.
This is either an executable (type 1) program with
the logical database entered in its programattributes, or a program that is using the functionmodule LDB_PROCESS.
7/30/2019 Logical Database2
3/9
LDB Events
In the first case (executable programs), the "PUT node." or" PUT ." statement triggers the "GET node. " event in theprogram. In the second case, the corresponding callbackroutine is called, and the data from the work area node oris passed back to it. Then, the PUT subroutines of the next
nodes in the structure are called (if the user wants datafrom these subordinate nodes). Finally, the "GET nodeLATE." event is triggered, if it is used in the executable
program, or the corresponding callback routine isexecuted.
7/30/2019 Logical Database2
4/9
LDB Events
The variant that you use depends on the type of the
node.
Variant 1 PUT node.
Effect
This is the standard variant that applies to all nodesthat do not have the type "Dynamic Dictionary Type".
In this case, the data object assigned to the node (that
has the name node) has a fixed type and has been
created globally in the database program..
7/30/2019 Logical Database2
5/9
LDB Events
This data object is f il led by the logical databasebefore the PUT statement is processed. If you are
working with an executable program, the work areais shared by the database program and theexecutable program
Consequently, the contents of node areautomatically available to the corresponding GETevent when the PUT statement occurs. If you areusing the logical database through the functionmodule LDB_PROCESS, the data object node ispassed to the callback routine in the PUT statement.
7/30/2019 Logical Database2
6/9
LDB Events
Variant 2
PUT .
Effect
You use this variant for nodes with the type "Dynamic DictionaryType". In this case, the NODES node. statement creates not only
the data object node in the database program, with the static typedefined for it in the logical database (this data object is alsoavailable to the executable program), but it also creates a fieldsymbol node. The logical database can read the runtime type of the
node from the automatically generated internal tableDYN_NODE_TYPES.
7/30/2019 Logical Database2
7/9
LDB Events
This is an internal table without header line and with the structure
DYN_NODES, which consists of the fields NODE and TYPE. This
type must belong to the list of types allowed for the node by thelogical database (Transaction SE36). In the database program, the
field symbol must be assigned to a data object with this type (using
the ASSIGN statement). The data object must be filled before thePUT statement is processed. "PUT " behaves exactly like "PUT
node" in non-dynamic cases, with the exception that is passed to the
user instead of node.
7/30/2019 Logical Database2
8/9
LDB Events
NODES CHARLY. " static dictionary type SPFLINODES DYNNODE. " Dynamic dictionary type, static type
SFLIGHT...
FORM PUT_CHARLY.SELECT * FROM SPFLI INTO CHARLY WHERE ...PUT CHARLY.
ENDSELECT.ENDFORM.
7/30/2019 Logical Database2
9/9
Thank You