J_1BDMEXG SAP (A/P: DME ITAU/FEBRABAN - Segment G - RETURN E-BOLETO) Structure details
Description: A/P: DME ITAU/FEBRABAN - Segment G - RETURN E-BOLETO
Structure field list including key, data, relationships and ABAP select examples
J_1BDMEXG 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/FEBRABAN - Segment G - RETURN E-BOLETO" 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_1BDMEXG TYPE J_1BDMEXG.
The J_1BDMEXG table consists of various fields, each holding specific information or linking keys about A/P: DME ITAU/FEBRABAN - Segment G - RETURN E-BOLETO data available in SAP. These include G02 (Lot control (for header '0000', for trailer '9999')), G03 (record type, e.g. '0' for the header), G04 (record number), G05 (Segment 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 J_1BDMEXG 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 |
G01 | first three digits for house bank key, e.g. '341' for Itau | J_1BXH101 | CHAR | 3 | CHAR3 | ||||
G02 | Lot control (for header '0000', for trailer '9999') | J_1BXH102 | NUMC | 4 | NUM4 | ||||
G03 | record type, e.g. '0' for the header | J_1BXH103 | CHAR | 1 | CHAR1 | ||||
G04 | record number | J_1BXA04 | NUMC | 5 | NUM5 | ||||
G05 | Segment type | J_1BXA05 | CHAR | 1 | CHAR1 | ||||
G06 | 1 blank | J_1BFILL1 | CHAR | 1 | CHAR1 | ||||
G07 | Movement code | J_1BXG07 | NUMC | 2 | J_1BXG07 | ||||
G08 | Vendor bank, first three digits | J_1BXA09 | NUMC | 3 | NUM3 | ||||
G09 | Currency code, should be always 9 | J_1BXJ8 | NUMC | 1 | NUM1 | ||||
G10 | Bar code control digit | J_1BXL24 | NUMC | 1 | NUM1 | ||||
G11 | Maturity Factor | J_1BXG11 | NUMC | 4 | J_1BXG11 | ||||
G12 | Value informed in barcode | J_1BXG12 | NUMC | 10 | J_1BXG12 | ||||
G13 | Mixture of several informations on bar code | J_1BXL23 | NUMC | 25 | J_1BNUMC25 | ||||
G14 | Vendor: CPF '1' or CNPJ '' ? | J_1BXB07 | CHAR | 1 | CHAR1 | ||||
G15 | Inscription number | J_1BXG15 | NUMC | 15 | J_1BXG15 | ||||
G16 | Partner name | J_1BXA15 | CHAR | 30 | CHAR30 | ||||
G17 | Due date, format DDMMYYYY | J_1BDUE2 | CHAR | 8 | CHAR8 | ||||
G18 | Nominal value | J_1BXL16 | NUMC | 15 | NUM15 | ||||
G19 | Amount in Reais | J_1BXA20 | NUMC | 15 | NUM15 | ||||
G20 | Currency code | J_1BXG20 | NUMC | 2 | J_1BXG20 | ||||
G21 | Document number | J_1BXG21 | NUMC | 15 | J_1BXG21 | ||||
G23 | Agency collector | J_1BXG23 | CHAR | 5 | J_1BXG23 | ||||
G24 | Verify digit of agency collector | J_1BXG24 | NUMC | 1 | J_1BXG24 | ||||
G25 | Agency Name | J_1BXG25 | CHAR | 10 | J_1BXG25 | ||||
G26 | Carteira Code | J_1BYA11 | CHAR | 1 | CHAR1 | ||||
G27 | Document type | J_1BXG27 | CHAR | 2 | J_1BXG27 | ||||
G28 | Document issue date | J_1BXG28 | CHAR | 8 | J_1BXG28 | ||||
G29 | Interest on arrears | J_1BXG29 | NUMC | 15 | J_1BXG29 | ||||
G30 | Code for 1st Discount | J_1BXG30 | CHAR | 1 | J_1BXG30 | ||||
G31 | 1st discount date | J_1BXG31 | CHAR | 8 | J_1BXG31 | ||||
G32 | Discount | J_1BXL18 | NUMC | 15 | NUM15 | ||||
G33 | Protest code | J_1BXG33 | NUMC | 1 | J_1BXG33 | ||||
G34 | Time for protest | J_1BXG34 | NUMC | 2 | J_1BXG34 | ||||
G35 | Limit date | J_1BXG35 | CHAR | 8 | J_1BXG35 | ||||
G36 | Interest code | J_1BXG36 | NUMC | 1 | J_1BXG36 |
Key field | Non-key field |
How do I retrieve data from SAP structure J_1BDMEXG using ABAP code?
As J_1BDMEXG 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_1BDMEXG as there is no data to select.How to access SAP table J_1BDMEXG
Within an ECC or HANA version of SAP you can also view further information about J_1BDMEXG 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