RCPFS SAP (External planning tool: auxiliary structure) Structure details
Description: External planning tool: auxiliary structure
Structure field list including key, data, relationships and ABAP select examples
RCPFS 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 "External planning tool: auxiliary structure" 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_RCPFS TYPE RCPFS.
The RCPFS table consists of various fields, each holding specific information or linking keys about External planning tool: auxiliary structure data available in SAP. These include COB1_FLG (Indicator: start external planning tool with COB data), COB1 (Description of a new configuration), SOB1_FLG (Indicator: start external planning tool with SOB data), COB2 (Description of a PFS configuration).. 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)
SAP RCPFS 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 |
| COB1_FLG | Indicator: start external planning tool with COB data | FLG_COB1 | CHAR | 1 | FLAG | ||||
| COB1 | Description of a new configuration | PFS_COB1 | CHAR | 56 | PFS_56 | COB | |||
| SOB1_FLG | Indicator: start external planning tool with SOB data | FLG_SOB1 | CHAR | 1 | FLAG | ||||
| COB2 | Description of a PFS configuration | PFS_COB | CHAR | 56 | PFS_56 | CO1 | |||
| SOB1 | Description of a PFS simulation | PFS_SOB1 | CHAR | 56 | PFS_56 | CO2 | |||
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| WNAME1 | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
| SCHID | Planning tool | SCHID | CHAR | 10 | CHAR10 | PFS | |||
| PFSTXT | Text, 40 Characters Long | TEXT40 | CHAR | 40 | TEXT40 | ||||
| USER_DLNM | Last changed by | LUSER | CHAR | 12 | SYCHAR12 | ||||
| DATUM_DLNM | Last change date | LDATUM | DATS | 8 | SYDATS | ||||
| TIME_DLNM | Time of last master data download | TIME_DLNM | TIMS | 6 | UZEIT | ||||
| USER_DLNT | Last changed by | LUSER | CHAR | 12 | SYCHAR12 | ||||
| DATUM_DLNT | Last change date | LDATUM | DATS | 8 | SYDATS | ||||
| TIME_DLNT | Time of the last transaction data download | TIME_DLNT | TIMS | 6 | UZEIT | ||||
| USER_UPLD | Last changed by | LUSER | CHAR | 12 | SYCHAR12 | ||||
| DATUM_UPLD | Last change date | LDATUM | DATS | 8 | SYDATS | ||||
| RULE_DLNM | Frequency download in (days) | RULE_DLNM | NUMC | 2 | NUM2 | ||||
| RULE_DLNT | Frequency download in (days) | RULE_DLNM | NUMC | 2 | NUM2 | ||||
| DLNM_VAR | Selection variant for master data download | DLNM_VAR | CHAR | 14 | CHAR14 | ||||
| DLNT_VAR | Selection variant for transaction data download | DLNT_VAR | CHAR | 14 | CHAR14 | ||||
| UPLD_VAR | Selection variant for transaction data upload | UPLD_VAR | CHAR | 14 | CHAR14 | ||||
| TIME_UPLD | Time of the last transaction data upload | TIME_UPLD | TIMS | 6 | UZEIT | ||||
| JOBNAME_MD | Job name for master data download | JOBNAME_MD | CHAR | 18 | CHAR18 | ||||
| JOBNAME_TD | Job name for transaction data download | JOBNAME_TD | CHAR | 18 | CHAR18 | ||||
| PLN_HOR_FROM | External planning tool: planning horizon starting from | PLN_HOR_FROM | DATS | 8 | DATUM | ||||
| PLN_HOR_TO | External planning tool: planning horizon to | PLN_HOR_TO | DATS | 8 | DATUM | ||||
| PLN_HOR | Ext. planning tool: planning horizon (Gregorian calendar) | PLN_HOR | NUMC | 3 | NUMC3 | ||||
| L_UPLD_E | Last upload canceled with message type 'E' or 'A' | L_UPLD_E | CHAR | 1 | CHAR1 | ||||
| MD_START_DATE | IDoc Created On | EDI_CCRDAT | DATS | 8 | DATUM | ||||
| MD_START_TIME | IDoc Created at | EDI_CCRTIM | TIMS | 6 | UZEIT | ||||
| MD_END_DATE | End Date | ENDDA | DATS | 8 | DATUM | ||||
| MD_END_TIME | End Time | ENDZT | TIMS | 6 | TIMES | ||||
| TD_START_DATE | IDoc Created On | EDI_CCRDAT | DATS | 8 | DATUM | ||||
| TD_START_TIME | IDoc Created at | EDI_CCRTIM | TIMS | 6 | UZEIT | ||||
| TD_END_DATE | End Date | ENDDA | DATS | 8 | DATUM | ||||
| TD_END_TIME | End Time | ENDZT | TIMS | 6 | TIMES | ||||
| UP_DATE | last upload | UP_DATUM | DATS | 8 | DATS | ||||
| UP_TIME | Time of the last transaction data upload | TIME_UPLD | TIMS | 6 | UZEIT |
| Key field | Non-key field |
How do I retrieve data from SAP structure RCPFS using ABAP code?
As RCPFS 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 RCPFS as there is no data to select.How to access SAP table RCPFS
Within an ECC or HANA version of SAP you can also view further information about RCPFS 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