J_3RFCLRDOC SAP (Vendor/Customer open item autoclearing report structure) Structure details
Dictionary Type: Structure
Description: Vendor/Customer open item autoclearing report structure
Description: Vendor/Customer open item autoclearing report structure
Structure field list including key, data, relationships and ABAP select examples
J_3RFCLRDOC 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 "Vendor/Customer open item autoclearing report structure" 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_3RFCLRDOC TYPE J_3RFCLRDOC.
The J_3RFCLRDOC table consists of various fields, each holding specific information or linking keys about Vendor/Customer open item autoclearing report structure data available in SAP. These include LIFNR (Account Number of Vendor or Creditor), BUKRS (Company Code), BEDG1 (Criterion 1), BEDG2 (Criterion 2).. 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: Cannot Be Enhanced
SAP J_3RFCLRDOC 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 |
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| BEDG1 | Criterion 1 | BED1_F123 | CHAR | 30 | Assigned to domain | FDNAME | |||
| BEDG2 | Criterion 2 | BED2_F123 | CHAR | 30 | Assigned to domain | FDNAME | |||
| BEDG3 | Criterion 3 | BED3_F123 | CHAR | 30 | Assigned to domain | FDNAME | |||
| BEDG4 | Criterion 4 | BED4_F123 | CHAR | 30 | Assigned to domain | FDNAME | |||
| BEDG5 | Criterion 5 | BED5_F123 | CHAR | 30 | Assigned to domain | FDNAME | |||
| SRTPR | Individual, User-Defined Character | CHAR0001 | CHAR | 1 | CHAR0001 | ||||
| QUANT | Iteration quantity | J_3RFCHAR3 | CHAR | 3 | J_3RFCHAR3 | ||||
| NUCLR | Clearing document sequence number | J_3RFCLRNUM | CHAR | 10 | J_3RFCLRNUM | ||||
| BELNR | Accounting Document Number | BELNR_D | CHAR | 10 | ALPHA | BELNR | BLN | ||
| BUZEI | Number of Line Item Within Accounting Document | BUZEI | NUMC | 3 | BUZEI | BUZ | |||
| BUDAT | System Date | SYDATUM | DATS | 8 | SYDATS | ||||
| BLDAT | Document Date in Document | BLDAT | DATS | 8 | DATUM | ||||
| USTXT | Document Header Text | BKTXT | CHAR | 25 | TEXT25 | ||||
| DE_CR | Individual, User-Defined Character | CHAR0001 | CHAR | 1 | CHAR0001 | ||||
| CLRPS | Individual, User-Defined Character | CHAR0001 | CHAR | 1 | CHAR0001 | ||||
| DSBLE | Individual, User-Defined Character | CHAR0001 | CHAR | 1 | CHAR0001 | ||||
| DSBBT | Individual, User-Defined Character | CHAR0001 | CHAR | 1 | CHAR0001 | ||||
| UMSKZ | Special G/L Indicator | UMSKZ | CHAR | 1 | Assigned to domain | UMSKZ | |||
| UMSKS | Special G/L Transaction Type | UMSKS | CHAR | 1 | UMSKS | ||||
| GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| SHKZG | Debit/Credit Indicator | SHKZG | CHAR | 1 | SHKZG | ||||
| WRBTR | Amount in document currency | WRBTR | CURR | 13(2) | WERT7 | ||||
| DMBTR | Amount in Local Currency | DMBTR | CURR | 13(2) | WERT7 | ||||
| CLRNG | Amount in document currency | WRBTR | CURR | 13(2) | WERT7 | ||||
| KOART | Account Type | KOART | CHAR | 1 | KOART | ||||
| XZAHL | Indicator: Is the posting key used in a payment transaction? | XZAHL | CHAR | 1 | XFELD | ||||
| XZAHR | Indicator: Is the posting key used in a payment transaction? | XZAHL | CHAR | 1 | XFELD | ||||
| XZAHM | Indicator: Is the posting key used in a payment transaction? | XZAHL | CHAR | 1 | XFELD | ||||
| BILDVAL | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
| DIFSUMMA | Amount in Local Currency | DMBTR | CURR | 13(2) | WERT7 | ||||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| HWAER | Local Currency | HWAER | CUKY | 5 | Assigned to domain | WAERS | |||
| CLWRS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| KURSF | Exchange rate | KURSF | DEC | 9(5) | EXCRT | KURSF | |||
| WWERT | Translation Date | WWERT_D | DATS | 8 | DATUM | ||||
| KURSR | Exchange rate | KURSF | DEC | 9(5) | EXCRT | KURSF | |||
| KURSC | Exchange rate | KURSF | DEC | 9(5) | EXCRT | KURSF | |||
| REBZG | Number of the Invoice the Transaction Belongs to | REBZG | CHAR | 10 | ALPHA | BELNR | |||
| REBZZ | Line Item in the Relevant Invoice | REBZZ | NUMC | 3 | BUZEI | ||||
| REBZJ | Fiscal Year of the Relevant Invoice (for Credit Memo) | REBZJ | NUMC | 4 | GJAHR | GJAHR | |||
| REBZT | Follow-On Document Type | REBZT | CHAR | 1 | REBZT | ||||
| NAME1 | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
| NAMEOLD | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
| FLAG_FILL | Individual, User-Defined Character | CHAR0001 | CHAR | 1 | CHAR0001 | ||||
| HKONT | General Ledger Account | HKONT | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | ||
| XPROC | Indicator | FLAG_X | CHAR | 1 | CHAR1_X |
| Key field | Non-key field |
How do I retrieve data from SAP structure J_3RFCLRDOC using ABAP code?
As J_3RFCLRDOC 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_3RFCLRDOC as there is no data to select.How to access SAP table J_3RFCLRDOC
Within an ECC or HANA version of SAP you can also view further information about J_3RFCLRDOC 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