J_1BDMEXH2 SAP (A/P: DME ITAU - LOT HEADER) Structure details
Description: A/P: DME ITAU - LOT HEADER
Structure field list including key, data, relationships and ABAP select examples
J_1BDMEXH2 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 "A/P: DME ITAU - LOT 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_1BDMEXH2 TYPE J_1BDMEXH2.
The J_1BDMEXH2 table consists of various fields, each holding specific information or linking keys about A/P: DME ITAU - LOT HEADER data available in SAP. These include H202 (Lot control (for header '0000', for trailer '9999')), H203 (record type, e.g. '0' for the header), H204 (operation type, fixed 'c'), H205 (Service type, fixed '20' for the time being).. 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_1BDMEXH2 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 |
| H201 | first three digits for house bank key, e.g. '341' for Itau | J_1BXH101 | CHAR | 3 | CHAR3 | ||||
| H202 | Lot control (for header '0000', for trailer '9999') | J_1BXH102 | NUMC | 4 | NUM4 | ||||
| H203 | record type, e.g. '0' for the header | J_1BXH103 | CHAR | 1 | CHAR1 | ||||
| H204 | operation type, fixed 'c' | J_1BXH204 | CHAR | 1 | CHAR1 | ||||
| H205 | Service type, fixed '20' for the time being | J_1BXH205 | NUMC | 2 | J_1BNUM2 | ||||
| H206 | Payment form, can be '1,2,3,10,30,31' | J_1BXH206 | NUMC | 2 | NUM2 | ||||
| H207 | 4 blanks | J_1BFILL4 | CHAR | 4 | CHAR4 | ||||
| H208 | Company: CPF ('1') or CNPJ ('2') ? | J_1BXH105 | CHAR | 1 | CHAR1 | ||||
| H209 | Company: CPF or CNPJ Number | J_1BXH106 | NUMC | 14 | NUM14 | ||||
| H210 | 20 blanks | J_1BXH107 | CHAR | 20 | J_1BCHAR20 | ||||
| H211 | Our bank key w/o control digit | J_1BXH108 | NUMC | 5 | NUM5 | ||||
| H212 | Bank key control digit | J_1BXH109 | CHAR | 1 | CHAR1 | ||||
| H213 | Our account number w/o control digit | J_1BXH110 | NUMC | 12 | NUM12 | ||||
| H214 | Account control digit | J_1BXH111 | CHAR | 1 | CHAR1 | ||||
| H215 | Account control digit | J_1BXH111 | CHAR | 1 | CHAR1 | ||||
| H216 | Our company name | J_1BXH113 | CHAR | 30 | CHAR30 | ||||
| H217 | Payment purpose, not filled | J_1BXH217 | CHAR | 30 | CHAR30 | ||||
| H218 | 10 blanks | J_1BFILL10 | CHAR | 10 | CHAR10 | ||||
| H219 | Our street | J_1BXH219 | CHAR | 30 | CHAR30 | ||||
| H220 | Our house number | J_1BXH220 | NUMC | 5 | NUM05 | ||||
| H221 | Our address - complement | J_1BXH221 | CHAR | 15 | CHAR15 | ||||
| H222 | Our city | J_1BXH222 | CHAR | 20 | CHAR20 | ||||
| H223 | Local code -main | J_1BXH223 | NUMC | 5 | NUM5 | ||||
| H224 | Local code -complement | J_1BXH224 | CHAR | 3 | CHAR3 | ||||
| H225 | Region | J_1BXH225 | CHAR | 2 | CHAR2 | ||||
| H226 | 2 blanks | J_1BFILL2 | CHAR | 2 | CHAR2 | ||||
| H227 | SIGMA system, not used for the time being | J_1BXH227 | CHAR | 6 | CHAR6 | ||||
| H228 | Accepted or rejected ? - 10 blanks when sending | J_1BXH228 | CHAR | 10 | CHAR10 |
| Key field | Non-key field |
How do I retrieve data from SAP structure J_1BDMEXH2 using ABAP code?
As J_1BDMEXH2 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_1BDMEXH2 as there is no data to select.How to access SAP table J_1BDMEXH2
Within an ECC or HANA version of SAP you can also view further information about J_1BDMEXH2 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