SCHEDMAN_SPECIFIC_COPCPCP SAP (Allowed CO-PC-PCP-Specific Fields for Monitor) Structure details
Description: Allowed CO-PC-PCP-Specific Fields for Monitor
Related tables to SCHEDMAN_SPECIFIC_COPCPCP
Access table SCHEDMAN_SPECIFIC_COPCPCP
Structure field list including key, data, relationships and ABAP select examples
SCHEDMAN_SPECIFIC_COPCPCP 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 "Allowed CO-PC-PCP-Specific Fields for Monitor" 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_SCHEDMAN_SPECIFIC_COPCPCP TYPE SCHEDMAN_SPECIFIC_COPCPCP.
The SCHEDMAN_SPECIFIC_COPCPCP table consists of various fields, each holding specific information or linking keys about Allowed CO-PC-PCP-Specific Fields for Monitor data available in SAP. These include KALADAT (Costing Run Date), ERFNM (Entered by), KOKRS (Controlling Area), BUKRS (Company Code).. 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 SCHEDMAN_SPECIFIC_COPCPCP 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 |
| KALAID | Name of Costing Run | CK_KALAID | CHAR | 8 | CHAR8 | KKF | CKKAT | ||
| KALADAT | Costing Run Date | CK_KALADAT | DATS | 8 | DATUM | KK1 | |||
| ERFNM | Entered by | ERFNM | CHAR | 12 | USNAM | ||||
| KOKRS | Controlling Area | KOKRS | CHAR | 4 | Assigned to domain | CACCD | CAC | ||
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| KLVAR | Costing Variant | CK_KLVAR | CHAR | 4 | Assigned to domain | KLVAR | KRT | ||
| TVERS | Costing Version | CK_TVERS | NUMC | 2 | CK_VERSION | VSN | |||
| KADAT | Costing Date From | CK_ABDAT | DATS | 8 | CK_KADAT | KDA | |||
| UEBID | Transfer Control | CK_UEBID | CHAR | 4 | Assigned to domain | CK_UEBER | |||
| RFC_GROUP | Name of Server Group for Parallel Processing | CKRFCGROUP | CHAR | 20 | SPTA_RFCGR | SPTA_SERVER_GROUP |
| Key field | Non-key field |
How do I retrieve data from SAP structure SCHEDMAN_SPECIFIC_COPCPCP using ABAP code?
As SCHEDMAN_SPECIFIC_COPCPCP 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 SCHEDMAN_SPECIFIC_COPCPCP as there is no data to select.How to access SAP table SCHEDMAN_SPECIFIC_COPCPCP
Within an ECC or HANA version of SAP you can also view further information about SCHEDMAN_SPECIFIC_COPCPCP 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