J_3RT1_HEAD SAP (Goods issue-transportation note header) Structure details
Description: Goods issue-transportation note header
Structure field list including key, data, relationships and ABAP select examples
J_3RT1_HEAD 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 "Goods issue-transportation note header" 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_J_3RT1_HEAD TYPE J_3RT1_HEAD.
The J_3RT1_HEAD table consists of various fields, each holding specific information or linking keys about Goods issue-transportation note header data available in SAP. These include ERDAT (Date on Which Record Was Created), P_DAY (Version Number Component), P_MONTH (Version Number Component), P_GJAHR (Fiscal Year).. 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 J_3RT1_HEAD 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 |
TKNUM | Goods issue - transportation note number | J_3RTKNUM | CHAR | 20 | CHAR20 | ||||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
P_DAY | Version Number Component | CHAR2 | CHAR | 2 | CHAR2 | ||||
P_MONTH | Version Number Component | CHAR2 | CHAR | 2 | CHAR2 | ||||
P_GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
VKORG | Sales Organization | VKORG | CHAR | 4 | Assigned to domain | VKORG | VKO | C_VKORG | |
GONAM | Char255 | CHAR255 | CHAR | 255 | CHAR255 | ||||
GOBANK | Text field length 200 | CHAR200 | CHAR | 200 | CHAR200 | ||||
GOOKPO | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
GPNUM | Ship-to party | KUNWE | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
GPNAM | Char255 | CHAR255 | CHAR | 255 | CHAR255 | ||||
GPBANK | Text field length 200 | CHAR200 | CHAR | 200 | CHAR200 | ||||
GPOKPO | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
PLNAM | Char255 | CHAR255 | CHAR | 255 | CHAR255 | ||||
PLBANK | Text field length 200 | CHAR200 | CHAR | 200 | CHAR200 | ||||
PLOKPO | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
EKNAM | Char255 | CHAR255 | CHAR | 255 | CHAR255 | ||||
EKBANK | Text field length 200 | CHAR200 | CHAR | 200 | CHAR200 | ||||
PONAM | char120 | CHAR120 | CHAR | 120 | CHAR120 | ||||
PRNAM | char120 | CHAR120 | CHAR | 120 | CHAR120 | ||||
BRGEW | Gross Weight | BRGEW | QUAN | 13(3) | MENG13 | ||||
BRGEW_W | Character field length 50 | CHAR_50 | CHAR | 50 | |||||
NTGEW | Net Weight | NTGEW | QUAN | 13(3) | MENG13 | ||||
NTGEW_W | Character field length 50 | CHAR_50 | CHAR | 50 | |||||
GEWEI | Weight Unit | GEWEI | UNIT | 3 | T006 | CUNIT | MEINS | ||
TOTNAM | Character field length 50 | CHAR_50 | CHAR | 50 | |||||
TOTPLC | Character field length 50 | CHAR_50 | CHAR | 50 | |||||
TOTLIN | Character field length 50 | CHAR_50 | CHAR | 50 | |||||
TOTSUM | Character field, length 70 | CHAR70 | CHAR | 70 | CHAR70 | ||||
NETWR | Net Value in Document Currency | NETWR | CURR | 15(2) | WERTV8 | ||||
WAERS | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
NAME1 | Name of user within the company | XUNAME1 | CHAR | 30 | XUNAME1 | ||||
NAME2 | Name of user within the company | XUNAME1 | CHAR | 30 | XUNAME1 | ||||
TELNR | Telephone number (work) | XUTELNR | CHAR | 16 | XUTELNR | ||||
CHIEF_ACC | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 | ||||
REG_NUM | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
SERIA | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
NUM | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
SROK_DOCT | Date | DATUM | DATS | 8 | DATUM | ||||
CAR_MAKE | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
CAR_NUM | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
CUSTOMER | Char255 | CHAR255 | CHAR | 255 | CHAR255 | ||||
DRIVER | Character field length 50 | CHAR_50 | CHAR | 50 | |||||
CERTIF | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 | ||||
LICENSE_TYPE | Character field length 50 | CHAR_50 | CHAR | 50 | |||||
LICENSE_REGN | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
LICENSE_SER | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
LICENSE_NUM | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
TRANSP_TYPE | Character field length 50 | CHAR_50 | CHAR | 50 | |||||
TRANSP_CODE | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
ROUTE | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
READDR | char120 | CHAR120 | CHAR | 120 | CHAR120 | ||||
TRAILER_1 | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
TRAILER_NUM_1 | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
GARAGE_1 | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
TRAILER_2 | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
TRAILER_NUM_2 | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
GARAGE_2 | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
POGRN | Character String 60 | CHAR_60 | CHAR | 60 | CHAR_60 | ||||
DELIV_ALLOW_POS | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 | ||||
DELIV_ALLOW_NAME | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 | ||||
BRGEW_W_TO_DELIV | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 | ||||
PLCN_W_TO_DELIV | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 |
Key field | Non-key field |
How do I retrieve data from SAP structure J_3RT1_HEAD using ABAP code?
As J_3RT1_HEAD 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 J_3RT1_HEAD as there is no data to select.How to access SAP table J_3RT1_HEAD
Within an ECC or HANA version of SAP you can also view further information about J_3RT1_HEAD 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