RELM_PL_USAGE_L1 SAP (Usage and Development Planning - Screen - Internal Usage) Structure details
Description: Usage and Development Planning - Screen - Internal Usage
Related tables to RELM_PL_USAGE_L1
Access table RELM_PL_USAGE_L1
Structure field list including key, data, relationships and ABAP select examples
RELM_PL_USAGE_L1 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 "Usage and Development Planning - Screen - Internal Usage" 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_RELM_PL_USAGE_L1 TYPE RELM_PL_USAGE_L1.
The RELM_PL_USAGE_L1 table consists of various fields, each holding specific information or linking keys about Usage and Development Planning - Screen - Internal Usage data available in SAP. These include MANDT (Client), INTRENO (Internal Key of Real Estate Object), PLUSSEQNO (Sequence Number of Usage), OBJRELGUID (GUID: Business Partner Object Relationship).. 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: Can be enhanced (character-type or numeric)
SAP RELM_PL_USAGE_L1 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 |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| INTRENO | Internal Key of Real Estate Object | RECAINTRENO | CHAR | 13 | RECAINTRENO | ||||
| PLUSSEQNO | Sequence Number of Usage | RELMPLUSSEQNO | NUMC | 4 | RECANUMBER | ||||
| OBJRELGUID | GUID: Business Partner Object Relationship | REBPOBJRELGUID | RAW | 16 | RECAGUID | ||||
| PLUSIND | Indicator for the Usage | RELMPLUSIND | CHAR | 1 | RELMPLUSIND | ||||
| PLUSTYPE | Usage Type of Parcel | RELMPLUSTYPE | CHAR | 6 | TIVLMPLUS | RELMPLUSTYPE | |||
| PLUSSUBTYPE | Subusage Type on Parcel | RELMPLUSSUBTYPE | CHAR | 6 | TIVLMPLUSSUB | RELMPLUSSUBTYPE | |||
| PLUSMEASVALUE | Size of Usage Area | RELMPLUSMEASVALUE | QUAN | 17(4) | REBDMEASVALUE | ||||
| PLUSMEASUNIT | Unit of Measurement for Usage Area | RELMPLUSMEASUNIT | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| PLUSISOPNEC | Operationally Necessary Area | RELMPLUSISOPNEC | CHAR | 1 | RECABOOL | ||||
| VALIDFROM | Date: Valid From | RECADATEFROM | DATS | 8 | RECADATEBEG | ||||
| VALIDTO | Date: Valid To | RECADATETO | DATS | 8 | REDAT | RECADATEEND | |||
| PLUSREALDATE | Date of Execution | RELMPLUSREALDATE | DATS | 8 | RECADATE | ||||
| XPLUSCOMMENT | Comments on Usage | RELMXPLUSGCOMMENT | CHAR | 60 | RECAXLDESCRIPTION | ||||
| XPLUSTYPE | Usage Type on Parcel - Text | RELMXPLUSTYPE | CHAR | 60 | RECAXLDESCRIPTION | ||||
| XPLUSSUBTYPE | Subusage Type on Parcel - Text | RELMXPLUSSUBTYPE | CHAR | 60 | RECAXLDESCRIPTION | ||||
| XPLUSIND | Indicator for Usage - Text | RELMXPLUSIND | CHAR | 30 | RECAXMDESCRIPTION | ||||
| .INCLU-BP | 0 | ||||||||
| PARTNERBP | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| ROLEBP | Business Partner: Role | REBPROLE | CHAR | 6 | Assigned to domain | BU_ROLE | |||
| SUBROLEBP | Business Partner: Role Type | REBPSUBROLE | CHAR | 4 | Assigned to domain | REBPSUBROLE | |||
| VALIDFROMBP | Date of Start of Relationship | REBPVALIDFROM | DATS | 8 | RECADATEBEG | ||||
| VALIDTOBP | Date of End of Relationship | REBPVALIDTO | DATS | 8 | REDAT | RECADATEEND | |||
| ROLECATEBP | Category of Role Category | REBPROLECATE | CHAR | 1 | REBPROLECATE | ||||
| XROLEBP | Name of Business Partner Role | REBPXROLE | CHAR | 30 | RECAXMDESCRIPTION | ||||
| XSUBROLEBP | Name of Role Type | REBPXSUBROLE | CHAR | 30 | RECAXMDESCRIPTION | ||||
| XPARTNERBP | Name/Address of Business Partner | REBPXPARTNER | CHAR | 80 | TEXT80 | ||||
| XNAMEBP | Short Name of Business Partner | REBPXNAME | CHAR | 50 | BU_TEXT50 | ||||
| XADDRESSBP | Compact Display of Address | REBPXADDRESS | CHAR | 80 | REBPXADDRESS | ||||
| ICON_DETAIL | Icon with Quick Info | RECAICON | CHAR | 137 | RECAICON | ||||
| ICON_PLUSIND | Icon with Quick Info | RECAICON | CHAR | 137 | RECAICON |
| Key field | Non-key field |
How do I retrieve data from SAP structure RELM_PL_USAGE_L1 using ABAP code?
As RELM_PL_USAGE_L1 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 RELM_PL_USAGE_L1 as there is no data to select.How to access SAP table RELM_PL_USAGE_L1
Within an ECC or HANA version of SAP you can also view further information about RELM_PL_USAGE_L1 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