HRESS_S_CLAIM_PIN_FILE_IN SAP (Structure to Send Attachments to ESS Screen using BOL) Structure details
Description: Structure to Send Attachments to ESS Screen using BOL
Related tables to HRESS_S_CLAIM_PIN_FILE_IN
Access table HRESS_S_CLAIM_PIN_FILE_IN
Structure field list including key, data, relationships and ABAP select examples
HRESS_S_CLAIM_PIN_FILE_IN 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 "Structure to Send Attachments to ESS Screen using BOL" 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_HRESS_S_CLAIM_PIN_FILE_IN TYPE HRESS_S_CLAIM_PIN_FILE_IN.
The HRESS_S_CLAIM_PIN_FILE_IN table consists of various fields, each holding specific information or linking keys about Structure to Send Attachments to ESS Screen using BOL data available in SAP. These include LINUM (Line Number), FISTA (Status (Approved / Rejected)), FNAME (File Name), FTYPE (File Extension).. 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 (Deep)
SAP HRESS_S_CLAIM_PIN_FILE_IN 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 |
| LINUM | Line Number | PIN_LINUM | NUMC | 4 | NUMC4 | ||||
| FISTA | Status (Approved / Rejected) | PIN_LIREQ_STAT | CHAR | 1 | LIRST | ||||
| FNAME | File Name | PIN_FLNAM | CHAR | 255 | PIN_FLNAM | ||||
| FTYPE | File Extension | PIN_FTYPE | CHAR | 10 | PIN_FTYPE | ||||
| FLTXT | Description of the File Extention | PIN_FLTXT | CHAR | 40 | TEXT40 | ||||
| FSIZE | Attachment File Size (in KB) | PIN_FSIZK | CHAR | 12 | SO_DOC_SIZ | ||||
| INVAF | Invalid | PIN_VALID | CHAR | 1 | XFELD | ||||
| FDATA | Content of the Attachment File | PIN_FDATA | RSTR | 0 | |||||
| LNKTX | Text for Link on ESS screen | PIN_LNKTX | CHAR | 50 | TEXT50 | ||||
| POPHT | Numc3, internal use | NUMC3 | NUMC | 3 | NUMC3 | ||||
| POPWD | Numc3, internal use | NUMC3 | NUMC | 3 | NUMC3 | ||||
| ALUPL | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| ALDEL | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| ALVIE | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| ALDWL | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| ALVIB | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| MXFSZ | Attachment File Size (in KB) | PIN_FSIZK | CHAR | 12 | SO_DOC_SIZ | ||||
| MXTSZ | Attachment File Size (in KB) | PIN_FSIZK | CHAR | 12 | SO_DOC_SIZ | ||||
| MXNFM | Numc3, internal use | NUMC3 | NUMC | 3 | NUMC3 | ||||
| MXNFH | Numc3, internal use | NUMC3 | NUMC | 3 | NUMC3 | ||||
| MXNFT | Numc3, internal use | NUMC3 | NUMC | 3 | NUMC3 | ||||
| ALSOC | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| ALALL | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| FFFU1 | Flag For Future Use | PIN_FFFU | CHAR | 1 | XFELD | ||||
| FFFU2 | Flag For Future Use | PIN_FFFU | CHAR | 1 | XFELD | ||||
| FFFU3 | Flag For Future Use | PIN_FFFU | CHAR | 1 | XFELD | ||||
| VIEFL | Approver Privilege to View the Attachments of the Request | PIN_VIEFL | CHAR | 1 | XFELD | ||||
| VISIBLE_DOWNLOAD | Data element for domain BOOLE: TRUE (='X') and FALSE (=' ') | BOOLE_D | CHAR | 1 | BOOLE | ||||
| VISIBLE_DELETE | Data element for domain BOOLE: TRUE (='X') and FALSE (=' ') | BOOLE_D | CHAR | 1 | BOOLE | ||||
| VISIBLE_ATTACHMENT | Data element for domain BOOLE: TRUE (='X') and FALSE (=' ') | BOOLE_D | CHAR | 1 | BOOLE | ||||
| FILE_TITLE | Text (100 characters) | TEXT100 | CHAR | 100 | TEXT100 |
| Key field | Non-key field |
How do I retrieve data from SAP structure HRESS_S_CLAIM_PIN_FILE_IN using ABAP code?
As HRESS_S_CLAIM_PIN_FILE_IN 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 HRESS_S_CLAIM_PIN_FILE_IN as there is no data to select.How to access SAP table HRESS_S_CLAIM_PIN_FILE_IN
Within an ECC or HANA version of SAP you can also view further information about HRESS_S_CLAIM_PIN_FILE_IN 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