RPYCLPA SAP (Class library Repository API: Parameters) Structure details
Description: Class library Repository API: Parameters
Structure field list including key, data, relationships and ABAP select examples
RPYCLPA is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Class library Repository API: Parameters" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_RPYCLPA TYPE RPYCLPA.
The RPYCLPA table consists of various fields, each holding specific information or linking keys about Class library Repository API: Parameters data available in SAP. These include CMPNAME (Component name), SCONAME (Subcomponent name), VERSION (Version indicator (active/inactive)), LANGU (Language Key).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified
SAP RPYCLPA structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| CLSNAME | Object Type Name | SEOCLSNAME | CHAR | 30 | SEOCLSNAME | CLASS | |||
| CMPNAME | Component name | SEOCMPNAME | CHAR | 30 | CHAR30 | ||||
| SCONAME | Subcomponent name | SEOSCONAME | CHAR | 30 | CHAR30 | ||||
| VERSION | Version indicator (active/inactive) | SEOVERSION | NUMC | 1 | SEOVERSION | ||||
| LANGU | Language Key | LANGU | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
| DESCRIPT | Short Description | SEODESCR | CHAR | 60 | AS4TEXT | ||||
| CMPTYPE | Component type | SEOCMPTYPE | NUMC | 1 | SEOCMPTYPE | ||||
| MTDTYPE | Method category | SEOMTDTYPE | NUMC | 1 | SEOMTDTYPE | ||||
| AUTHOR | Author | CNAM | CHAR | 12 | SYCHAR12 | ||||
| CREATEDON | Created on | RDIR_CDATE | DATS | 8 | SYDATS | ||||
| CHANGEDBY | Last changed by | UNAM | CHAR | 12 | SYCHAR12 | ||||
| CHANGEDON | Changed On | RDIR_UDATE | DATS | 8 | SYDATS | ||||
| PARDECLTYP | Parameter Declaration Level (User View) | SEOPARDECL | NUMC | 1 | SEOPARDECL | ||||
| PARPASSTYP | Passing type for parameter | SEOPARPASS | NUMC | 1 | SEOPARPASS | ||||
| TYPTYPE | Typing | SEOTYPTYPE | NUMC | 1 | SEOTYPTYPE | ||||
| TYPE | Associated Type of an Interface Parameter | RS38L_TYP | CHAR | 132 | RS38L_TYP | ||||
| TABLEOF | Table indicator | SEOTABLEOF | CHAR | 1 | CHAR1_X | ||||
| PARVALUE | Initial value | SEOVALUE | CHAR | 132 | TEXT132 | ||||
| PAROPTIONL | Optional parameter indicator | SEOOPTIONL | CHAR | 1 | CHAR1_X |
| Key field | Non-key field |
How do I retrieve data from SAP structure RPYCLPA using ABAP code?
As RPYCLPA is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on RPYCLPA as there is no data to select.How to access SAP table RPYCLPA
Within an ECC or HANA version of SAP you can also view further information about RPYCLPA and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects