GRFN_S_API_ISSUE SAP (Issue Data for API) Structure details
Description: Issue Data for API
Related tables to GRFN_S_API_ISSUE
Access table GRFN_S_API_ISSUE
Structure field list including key, data, relationships and ABAP select examples
GRFN_S_API_ISSUE 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 "Issue Data for API" 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_GRFN_S_API_ISSUE TYPE GRFN_S_API_ISSUE.
The GRFN_S_API_ISSUE table consists of various fields, each holding specific information or linking keys about Issue Data for API data available in SAP. These include EXT_REF (External reference), ISSUE_NAME (Case Title), PROCESSOR (Processor), RESPONSIBLE (Person Responsible).. 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: Cannot Be Enhanced
SAP GRFN_S_API_ISSUE 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 |
| ISSUE_ID | GRPC ID of the individual object | GRPC_API_OBJECT_ID | CHAR | 50 | GRPC_API_OBJECT_ID | ||||
| EXT_REF | External reference | SCMG_EXT_REF | CHAR | 30 | CHAR30 | ||||
| ISSUE_NAME | Case Title | SCMG_CASE_TITLE | CHAR | 80 | TEXT80 | ||||
| PROCESSOR | Processor | SCMG_PROCESSOR | CHAR | 12 | Assigned to domain | XUBNAME | USER_ADDR | ||
| RESPONSIBLE | Person Responsible | SCMG_RESPONSIBLE | CHAR | 12 | Assigned to domain | XUBNAME | USER_ADDR | ||
| CATEGORY | Category | SCMG_CATEGORY | CHAR | 4 | CHAR4 | ||||
| ISSUE_PRIORITY | Issue Priority | GRPC_ISSUE_PRIORITY | CHAR | 1 | GRPC_ISSUE_PRIORITY | ||||
| DESCRIPTION | Issue description | 0 | |||||||
| COMPENSATING_CONTROLS | Compensation controls | 0 | |||||||
| POTENTIAL_IMPACT | Potential impact | 0 | |||||||
| REMEDIATION_COMMENT | Remediation comment | 0 | |||||||
| CASE_TYPE | Case Type | SCMGCASE_TYPE | CHAR | 4 | Assigned to domain | SCMGCASE_TYPE | |||
| STATUS_TEXT | Object status | J_TXT30 | CHAR | 30 | TEXT30 | ||||
| CATEGORY_TEXT | Text Field of Length 60 | TEXT60 | CHAR | 60 | TEXT60 | ||||
| STATUS | Object Status | CRM_J_STATUS | CHAR | 5 | CRM_J_STATUS | ||||
| PARENT_ID | GRPC ID of the individual object | GRPC_API_OBJECT_ID | CHAR | 50 | GRPC_API_OBJECT_ID | ||||
| CLOSED_ON | Field of type DATS | DATS | DATS | 8 | DATS | ||||
| VALIDATED_ON | Field of type DATS | DATS | DATS | 8 | DATS | ||||
| VALIDATED_BY | Person Validating | GRPC_VALIDATED_BY_UN | CHAR | 12 | UNAME | ||||
| WORKFLOW_TYPE | Issue Workflow Type | GRPC_ISSUE_WF_TYPE | CHAR | 1 | GRPC_ISSUE_WF_TYPE | ||||
| USE_CAPAPLAN | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| RESULT | String | GRFN_TEXT | STRG | 0 | |||||
| SERIOUS | Attribute Value | GRPC_ATTRVALUE | CHAR | 10 | GRPC_ATTRVALUE | ||||
| PRIORITY_RA | Issue Priority | GRPC_ISSUE_PRIORITY | CHAR | 1 | GRPC_ISSUE_PRIORITY | ||||
| COMMENT | String | GRFN_TEXT | STRG | 0 | |||||
| IMPACT | Attribute Value | GRPC_ATTRVALUE | CHAR | 10 | GRPC_ATTRVALUE | ||||
| OTHER_IMPACT | String | GRFN_TEXT | STRG | 0 | |||||
| OBJECT_ID | Object ID | GRFN_API_OBJECT_ID | CHAR | 50 | CHAR50 | ||||
| OBJECT_TYPE | Entity ID | GRFN_API_ENTITY_ID | CHAR | 20 | Assigned to domain | GRFN_API_ENTITY_ID | |||
| CREATE_DATE | Field of type DATS | DATS | DATS | 8 | DATS | ||||
| UPDATE_DATE | Time Stamp | GRFN_TIMESTAMP | DEC | 15 | TSTPS | GRFN_TIMESTAMP | |||
| REPORT_BY | Processor | SCMG_PROCESSOR | CHAR | 12 | Assigned to domain | XUBNAME | USER_ADDR | ||
| UPDATE_BY | Processor | SCMG_PROCESSOR | CHAR | 12 | Assigned to domain | XUBNAME | USER_ADDR | ||
| IS_ANONYMOUS | Boolean Variable (X=True, -=False, Space=Unknown) | BOOLEAN | CHAR | 1 | BOOLEAN | ||||
| ANONYMOUS_NAME | Text Field of Length 60 | TEXT60 | CHAR | 60 | TEXT60 | ||||
| DUE_DATE | End Date | ENDDATUM | DATS | 8 | DATUM | END | |||
| ISSUE_DATE | End Date | ENDDATUM | DATS | 8 | DATUM | END | |||
| ISSUE_SOURCE | issue type for GRC 2010 | GRFN_ISSUETYPE | CHAR | 20 | CHAR20 | ||||
| IS_NEW | Boolean Variable (X=True, -=False, Space=Unknown) | BOOLEAN | CHAR | 1 | BOOLEAN |
| Key field | Non-key field |
How do I retrieve data from SAP structure GRFN_S_API_ISSUE using ABAP code?
As GRFN_S_API_ISSUE 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 GRFN_S_API_ISSUE as there is no data to select.How to access SAP table GRFN_S_API_ISSUE
Within an ECC or HANA version of SAP you can also view further information about GRFN_S_API_ISSUE 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