PIN_TRANSD_HEADER SAP (Structure to store the cumulated header record) Structure details
Description: Structure to store the cumulated header record
Related tables to PIN_TRANSD_HEADER
Access table PIN_TRANSD_HEADER
Structure field list including key, data, relationships and ABAP select examples
PIN_TRANSD_HEADER 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 store the cumulated header record" 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_PIN_TRANSD_HEADER TYPE PIN_TRANSD_HEADER.
The PIN_TRANSD_HEADER table consists of various fields, each holding specific information or linking keys about Structure to store the cumulated header record data available in SAP. These include PERNR (Personnel number), REFNR (Request Reference Number), RETYP (Reimbursement Type), RQTYP (Request Type).. 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 or numeric)
SAP PIN_TRANSD_HEADER 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 |
PERNR | Personnel number | PERSNO | NUMC | 8 | Assigned to domain | PERSNO | PER | ||
REFNR | Request Reference Number | PIN_REFNR | CHAR | 13 | CHAR13 | ||||
RETYP | Reimbursement Type | PIN_REIMB_TYP | CHAR | 4 | Assigned to domain | CHAR4 | |||
RQTYP | Request Type | PIN_REQ_TYP | CHAR | 2 | PIN_REQ_TYP | ||||
CREFM | Request Created Source | PIN_CL_REQ_SOURCE | CHAR | 2 | PIN_CL_REQ_SOURCE | ||||
RQCID | Request Created By | PIN_RQCID | CHAR | 12 | UNAME | ||||
RQCDT | Request Creation Date | PIN_RQCDT | DATS | 8 | DATUM | ||||
RQCTM | Request Creation Time | PIN_RQCTM | TIMS | 6 | TIME | ||||
RQCAN | Request Creation Solution Type | PIN_RQCAN | NUMC | 5 | NUMC5 | ||||
RSNCD | Reason Code for Reject / Delete | PIN_RSNCD | CHAR | 3 | CHAR3 | ||||
ARDDT | Approve / Reject / Delete Date | PIN_ARDDT | DATS | 8 | DATUM | ||||
ITUDT | Infotype Update Date | PIN_ITUDT | DATS | 8 | DATUM | ||||
PAYDT | Payment Date | PIN_PMTDT | DATS | 8 | DATUM | ||||
CODAT | Completed Date | PIN_CODAT | DATS | 8 | DATUM | ||||
ITBDT | Infotype Begin Date | PIN_ITBDT | DATS | 8 | DATUM | ||||
PHASE | Phase Of the Request | PIN_PHASE | CHAR | 1 | PIN_CPHAS | ||||
CSTAT | Status Of the Request | PIN_REQSTATUS | CHAR | 1 | PIN_REQSTATUS | ||||
ASREF | Request Reference Number | PIN_REFNR | CHAR | 13 | CHAR13 | ||||
TSR01 | Trigger Screen Rendering Field | PIN_TRSCR | CHAR | 4 | CHAR4 | ||||
TSR02 | Trigger Screen Rendering Field | PIN_TRSCR | CHAR | 4 | CHAR4 | ||||
OCFLG | Offcycle Requested | PIN_OCREQ | CHAR | 1 | FLAG | ||||
TEXRQ | Tax Exemption Requested | PIN_TEXRQ | CHAR | 1 | FLAG | ||||
WRKID | Work item ID | SWW_WIID | NUMC | 12 | Assigned to domain | SWW_WIID | WID | ||
OCPVD | Offcycle Provided | PIN_OCPVD | CHAR | 1 | FLAG | ||||
DCLAG | Declaration Agreement | PIN_DCLAG | CHAR | 1 | FLAG | ||||
ERRFG | Error Flag | PIN_ERRFG | CHAR | 1 | FLAG | ||||
ERRNO | Message number | MSGNR | CHAR | 3 | Assigned to domain | MSGNR | |||
APUID | Last / Latest Approver User ID | PIN_USRID | CHAR | 12 | UNAME | ||||
APLVL | Approver Level | PIN_APLVL | CHAR | 2 | PIN_APLVL | ||||
APGRP | Approver Group | PIN_APRVR_GRP | CHAR | 15 | CHAR15 | ||||
LCUID | Last Change By User ID | PIN_LCUID | CHAR | 12 | USRID | ||||
LCHDT | Last Change Date | PIN_LCHDT | DATS | 8 | DATUM | ||||
LCHTM | Last Change Time | PIN_LCHTM | TIMS | 6 | TIME | ||||
ISMST | Mail Sent | PIN_ISMST | CHAR | 1 | FLAG | ||||
EEMOB | SAPoffice: ID of a SAPoffice object | SO_OBJ_ID | CHAR | 17 | SO_OBJ_ID | ||||
APMOB | SAPoffice: ID of a SAPoffice object | SO_OBJ_ID | CHAR | 17 | SO_OBJ_ID | ||||
ADMOB | SAPoffice: ID of a SAPoffice object | SO_OBJ_ID | CHAR | 17 | SO_OBJ_ID | ||||
SCMCD | LTC Scheme Code | PIN_LTC_SCHEME_CODE | CHAR | 4 | CHAR4 | ||||
PCLMD | Partial Claim | PIN_PARTIALLY_CLAIM | CHAR | 1 | FLAG | ||||
ISCMP | Trip Completed | PIN_IS_COMPLETED | CHAR | 1 | FLAG | ||||
PRTNO | Part Number | PIN_PART_NUMBER | NUMC | 2 | NUMC2 | ||||
TRPNO | Object Identification | OBJPS | CHAR | 2 | OBJPS | OPS | |||
BEGDA | LTC Block Begin Date | PIN_LTC_BEGDA | DATS | 8 | DATUM | ||||
ENNDA | LTC Block End Date | PIN_LTC_ENDDA | DATS | 8 | DATUM | ||||
RQAMT | Requested Amount | PIN_RQAMT | CURR | 15(2) | PRBETRG | ||||
APAMT | Approved Amount | PIN_APAMT | CURR | 15(2) | PRBETRG | ||||
RQNUM | Requested Number | PIN_RQNUM | DEC | 15(2) | PRANZHL | ||||
APNUM | Approved Number | PIN_APNUM | DEC | 15(2) | PRANZHL | ||||
RQTEX | Requested Tax Exemption Amount | PIN_RQTEX | CURR | 15(2) | PRBETRG | ||||
APTEX | Approved Tax Exemption Amount | PIN_APTEX | CURR | 15(2) | PRBETRG | ||||
UNIT | Unit Key | PIN_CLM_UNIT | CHAR | 3 | Assigned to domain | RPMSH | |||
WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
SDAT1 | General Amount Field | PIN_GENAM | CURR | 15(2) | PRBETRG | ||||
SDAT2 | General Amount Field | PIN_GENAM | CURR | 15(2) | PRBETRG | ||||
SDAT3 | General Amount Field | PIN_GENAM | CURR | 15(2) | PRBETRG | ||||
SDAT4 | General Amount Field | PIN_GENAM | CURR | 15(2) | PRBETRG | ||||
SNUM1 | General Number Field | PIN_GENNM | DEC | 15(2) | PRANZHL | ||||
SNUM2 | General Number Field | PIN_GENNM | DEC | 15(2) | PRANZHL | ||||
SNUM3 | General Number Field | PIN_GENNM | DEC | 15(2) | PRANZHL | ||||
SNUM4 | General Number Field | PIN_GENNM | DEC | 15(2) | PRANZHL |
Key field | Non-key field |
How do I retrieve data from SAP structure PIN_TRANSD_HEADER using ABAP code?
As PIN_TRANSD_HEADER 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 PIN_TRANSD_HEADER as there is no data to select.How to access SAP table PIN_TRANSD_HEADER
Within an ECC or HANA version of SAP you can also view further information about PIN_TRANSD_HEADER 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