Get Example source ABAP code based on a different SAP table
• GET PROPERTY OF - OLE ABAP Statement
GET PROPERTY>, OLE Short Reference >
ABAP_SYNTAX GET PROPERTY OF ole prop = dobj $[NO FLUSH$] $[QUEUE-ONLY$]> $[EXPORTING p1 = f1 p2 = f2 ...$]. >
ABAP Addition 1 ... NO FLUSH> 2 ... QUEUE-ONLY> 3 ... EXPORTING p1 = f1 p2 = f2 ...>
What does it do? Assigns the content of the property prop> of an automation object ole> to the data object dobj>. The automation object must have been created using the special statement CREATE OBJECT>> for automation objects. The description of the statement CREATE OBJECT> applies to the typing> of ole>. The typing of the data object dobj> depends on the properties of the automation property prop>. System Fields> sy-subrc>Meaning> 0Object properties passed successfully. 1Error in communication with SAP GUI. 2Error in function call in SAP GUI. 3Error when setting a property. 4Error when reading a property. • NO FLUSH GET PROPERTY - OLE • QUEUE-ONLY GET PROPERTY - OLE
ABAP Addition
ABAP Addition
What does it do? The description of the statement CREATE OBJECT>> applies to the meaning of the NO FLUSH> and QUEUE-ONLY> additions. • EXPORTING GET PROPERTY - OLE
ABAP Addition
What does it do? The addition EXPORTING> can be used to assign the actual parameters f1 f2 ...> to the parameters p1 p2 ...> of the automation object, where the data type of the data objects f1 f2 ... > depends on the requirements of the property.
Example ABAP Coding
This example reads the Visible> property of an Excel table that was created at runtime. This property specifies whether the table processing is visible or runs in the background. The variable vis> is typed as an integer because Excel passes an integer value. ABEXA 00304 ABAP_EXAMPLE_END