RNCFILE0 SAP (IS-H: Structure for File Name Composition in HCM/EDI Area) Structure details
Description: IS-H: Structure for File Name Composition in HCM/EDI Area
Structure field list including key, data, relationships and ABAP select examples
RNCFILE0 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 "IS-H: Structure for File Name Composition in HCM/EDI Area" 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_RNCFILE0 TYPE RNCFILE0.
The RNCFILE0 table consists of various fields, each holding specific information or linking keys about IS-H: Structure for File Name Composition in HCM/EDI Area data available in SAP. These include MANDT (Client), EINRI (Institution), EDIPROC (IS-HCM: EDI Procedure), DAS301 (Data Collection Point for EDI Message Transmission).. 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 RNCFILE0 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 | |||
EINRI | Institution | EINRI | CHAR | 4 | TN01 | ALPHA | EINRI | EIN | |
EDIPROC | IS-HCM: EDI Procedure | N_EDIPROC | CHAR | 5 | TNC301G0 | N_EDIPROC | |||
DAS301 | Data Collection Point for EDI Message Transmission | ISH_DAS301 | CHAR | 10 | NC301B | N301DEST | |||
NINOUTSIGN | IS-HCM: Outbound - Inbound Message(s) Indicator | NINOUTSIGN | CHAR | 1 | NINOUTSIGN | ||||
NTNR | IS-HCM: Message Type Number | NTNR | CHAR | 3 | TNCT0 | NTNR | |||
CONST1 | IS-H EDI: Constant in File Name | ISH_FILEFIX | CHAR | 10 | VAL_TEXT | ||||
CONST2 | IS-H EDI: Constant in File Name | ISH_FILEFIX | CHAR | 10 | VAL_TEXT | ||||
CONST3 | IS-H EDI: Constant in File Name | ISH_FILEFIX | CHAR | 10 | VAL_TEXT | ||||
SEQ_CONST1 | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
SEQ_CONST2 | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
SEQ_CONST3 | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
SEQ_LF301M | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
SEQ_YEAR | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
SEQ_MONTH | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
SEQ_COUNT | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
QNT_LF301M | IS-H: Number of Digits of DCP-Specific Sequence Number | ISH_QNTLF301M | NUMC | 2 | NUM02 | ||||
QNT_YEAR | IS-H: EDI Number of Digits in Year Specification Used | ISH_QNTYEAR | NUMC | 2 | NUM02 | ||||
QNT_COUNT | IS-H: EDI Number of Digits for Counter | ISH_QNTCOUNT | NUMC | 2 | NUM02 | ||||
CNT_MONTH | IS-H: Counter Incremented on Monthly Basis | ISH_IND_MONTH | CHAR | 1 | XFELD | ||||
CNT_YEAR | IS-H: Counter Incremented on Yearly Basis | ISH_IND_YEAR | CHAR | 1 | XFELD | ||||
CNT_NUM | IS-H: Numerical Counter Used | ISH_IND_NUM | CHAR | 1 | XFELD | ||||
CNT_ALPHA | IS-H: Counter Contains Letters Only | ISH_IND_ALPHA | CHAR | 1 | XFELD | ||||
CNT_NUMAL | IS-H: Counter Numeric, then Alphabetical | ISH_IND_NUMAL | CHAR | 1 | XFELD | ||||
CNT_ALNUM | IS-H: Counter Alphabetical, then Numeric | ISH_IND_ALNUM | CHAR | 1 | XFELD | ||||
LF301C | IS-H: EDI Sequence Counter for File Name Logic | ISH_LF301C | CHAR | 10 | ISH_LF301C | ||||
LAST_DATE | IS-H: EDI Date when Counter Last Incremented | ISH_LASTDATE | DATS | 8 | RI_DATUM | ||||
UPDAT | IS-H: Date of Last Change | RI_UPDAT | DATS | 8 | RI_DATUM | ||||
UPTIM | IS-H: Time Data Record was Last Changed | ISH_UPTIM | TIMS | 6 | UHRZT | ||||
UPUSR | IS-H: Name of Person who Last Changed Data | RI_UPNAM | CHAR | 12 | USNAM | ||||
ERDAT | IS-H: Date when Record Created | RI_ERDAT | DATS | 8 | RI_DATUM | ||||
ERTIM | IS-H: Time when Data Record Created | ISH_ERTIM | TIMS | 6 | UHRZT | ||||
ERUSR | IS-H: Name of Employee who Created Record | RI_ERNAM | CHAR | 12 | USNAM | ||||
SEQ_FALNR | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
SEQ_PATNR | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
SEQ_EINRI | IS-H: Sequence | ISH_SEQ | NUMC | 2 | NUM02 | ||||
FALNR | IS-H: Case Number | FALNR | CHAR | 10 | Assigned to domain | ALPHA | FALNR | FAL | |
PATNR | IS-H: Patient Number | PATNR | CHAR | 10 | Assigned to domain | ALPHA | PATNR | PAT | |
LF301M | IS-HCM: Seq. File Number (Data Cllct. Point-Specific) | ISH_LF301M | NUMC | 5 | NUM05 | ||||
QNT_FALNR | IS-H: Number of Digits from Case Number | ISH_QNTFALNR | NUMC | 2 | NUM02 | ||||
DEL_ZEROS | IS-H: Suppress Leading Zeros | ISH_DELZEROS | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure RNCFILE0 using ABAP code?
As RNCFILE0 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 RNCFILE0 as there is no data to select.How to access SAP table RNCFILE0
Within an ECC or HANA version of SAP you can also view further information about RNCFILE0 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