Get Application Components actions
Get Application Components actions retrieve the application components for a set of objects from the specified RFC Destination. The action stores the results in a Table dataset.
The RFC Destination must have a valid Object Links Cache database. This can be generated using the Create Object Links Cache workflow from the Prerequisites templates folder
| Action property | Description |
|---|---|
| Result | A Table dataset that stores the objects from the Source table and their retrieved application components. |
| RFC Destination | An RFC Destination parameter or dataset referring to the SAP system from, which to retrieve application components. The RFC Destination must have a valid Object Links Cache database as described above. |
| Source | A Table parameter or dataset that stores the SAP objects for which to retrieve application components. The table should have a NAME column that stores each object’s name, and a TYPE column that stores each object’s type. |
The Result dataset has the following columns:
| Column | Description |
|---|---|
| NAME | The name of an object from the Source table. |
| TYPE | The type of the object from the Source table. |
| PS_POSID | The object’s application component represented as a path in the SAP application components hierarchy. |
The Get Application Components action handles special cases like methods (METH), which don't have a direct application component. In this case the action uses a method’s containing class to identify its application component.
The Get Application Components action supports Function Groups (FUGR) stored as Programs (PROG). In this case, the action returns the PS_POSID value associated with the Function Group.
Example
