J_3R_M2_FSD SAP (Single data for M-2) Structure details
Description: Single data for M-2
Structure field list including key, data, relationships and ABAP select examples
J_3R_M2_FSD 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 "Single data for M-2" 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_3R_M2_FSD TYPE J_3R_M2_FSD.
The J_3R_M2_FSD table consists of various fields, each holding specific information or linking keys about Single data for M-2 data available in SAP. These include H02_OKPO (OKPO Code (Russia)), H03_DOCNUM (Document Number), H04_DOC_DATE (Document Date), H05_VALID_TILL (Document Date).. 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 J_3R_M2_FSD 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 |
| H01_COMPANY | Organization name | J_3RALCOMNAME | CHAR | 160 | CHAR160 | ||||
| H02_OKPO | OKPO Code (Russia) | J_3ROKPO | CHAR | 8 | CHAR08 | ||||
| H03_DOCNUM | Document Number | J_3R_DOCNUM | CHAR | 10 | CHAR10 | ||||
| H04_DOC_DATE | Document Date | J_3R_DOC_DATE | DATS | 8 | |||||
| H05_VALID_TILL | Document Date | J_3R_DOC_DATE | DATS | 8 | |||||
| H06_CONSUMER | Organization Name | J_3R_ORG_LONG_NAME | CHAR | 200 | TEXT200 | ||||
| H07_PAYER | Organization Name | J_3R_ORG_LONG_NAME | CHAR | 200 | TEXT200 | ||||
| H08_BANKN | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
| H09_BANKNAME | Char 80 | CHAR80 | CHAR | 80 | CHAR80 | ||||
| H10_POSITION | Description | BU_BEZ30 | CHAR | 30 | TEXT30 | ||||
| H11A_NAME | Text (80 Characters) | TEXT80 | CHAR | 80 | TEXT80UEB | ||||
| H11B_NAME_INIT | 'Middle Initial' or personal initials | AD_INITS | CHAR | 10 | CHAR10 | ||||
| H12_PASSP_SER | Text (20 Characters) | TEXT20 | CHAR | 20 | TEXT20 | ||||
| H13_PASSP_NUM | Identification Number | BU_ID_NUMBER | CHAR | 60 | CHAR60 | ||||
| H14_PASSP_ISS_BY | Character 100 | CHAR100 | CHAR | 100 | CHAR100 | ||||
| H15_PASSP_ISS_DAT | Date of Entry for ID Number | BU_ID_ENTRY_DATE | DATS | 8 | DATUM | ||||
| H16_VENDOR | CHAR140 | CHAR140 | CHAR | 140 | CHAR140 | ||||
| H17A_PO_NUM | Char 80 | CHAR80 | CHAR | 80 | CHAR80 | ||||
| H17B_PO_DATE | Purchasing Document Date | EBDAT | DATS | 8 | DATUM |
| Key field | Non-key field |
How do I retrieve data from SAP structure J_3R_M2_FSD using ABAP code?
As J_3R_M2_FSD 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_3R_M2_FSD as there is no data to select.How to access SAP table J_3R_M2_FSD
Within an ECC or HANA version of SAP you can also view further information about J_3R_M2_FSD 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