RPLM_TS_ORDER_PRTNR_CUST_UI SAP (User Interface Structure for Service Order: Customer) Structure details
Description: User Interface Structure for Service Order: Customer
Related tables to RPLM_TS_ORDER_PRTNR_CUST_UI
Access table RPLM_TS_ORDER_PRTNR_CUST_UI
Structure field list including key, data, relationships and ABAP select examples
RPLM_TS_ORDER_PRTNR_CUST_UI 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 "User Interface Structure for Service Order: Customer" 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_RPLM_TS_ORDER_PRTNR_CUST_UI TYPE RPLM_TS_ORDER_PRTNR_CUST_UI.
The RPLM_TS_ORDER_PRTNR_CUST_UI table consists of various fields, each holding specific information or linking keys about User Interface Structure for Service Order: Customer data available in SAP. These include PARNR (Partner), KUNUM (Account Number of Customer), NAME1 (Name 1), NAME2 (Name 2).. 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 RPLM_TS_ORDER_PRTNR_CUST_UI 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 |
| PARVW_EXT | Partner Function | PARVW | CHAR | 2 | Assigned to domain | PARVW | PARVW | PAR | |
| PARNR | Partner | I_PARNR | CHAR | 12 | ALPHA | I_PARNR | |||
| KUNUM | Account Number of Customer | QKUNUM | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | |
| NAME1 | Name 1 | AD_NAME1 | CHAR | 40 | TEXT40 | ||||
| NAME2 | Name 2 | AD_NAME2 | CHAR | 40 | TEXT40 | ||||
| STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
| POST_CODE1 | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
| CITY1 | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
| COUNTRY | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| REGION | STATE (State, Province, County) | REGIO | CHAR | 3 | Assigned to domain | REGIO | |||
| TEL_NUMBER | First telephone no.: dialling code+number | AD_TLNMBR1 | CHAR | 30 | CHAR30 | ||||
| FAX_NUMBER | First fax no.: dialling code+number | AD_FXNMBR1 | CHAR | 30 | CHAR30 | ||||
| DATUM | System Date | SYDATUM | DATS | 8 | SYDATS | ||||
| UZEIT | System Time | SYUZEIT | TIMS | 6 | SYTIME | ||||
| TZONSP | Time Zone for Partner | TZONSP | CHAR | 6 | Assigned to domain | TZNZONE | |||
| VTXTK | Name | VTXTK | CHAR | 20 | TEXT20 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RPLM_TS_ORDER_PRTNR_CUST_UI using ABAP code?
As RPLM_TS_ORDER_PRTNR_CUST_UI 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 RPLM_TS_ORDER_PRTNR_CUST_UI as there is no data to select.How to access SAP table RPLM_TS_ORDER_PRTNR_CUST_UI
Within an ECC or HANA version of SAP you can also view further information about RPLM_TS_ORDER_PRTNR_CUST_UI 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