FDM_COLL_INVOICE_ALV SAP (ALV Output Structure for Collections Management) Structure details
Description: ALV Output Structure for Collections Management
Related tables to FDM_COLL_INVOICE_ALV
Access table FDM_COLL_INVOICE_ALV
Structure field list including key, data, relationships and ABAP select examples
FDM_COLL_INVOICE_ALV 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 "ALV Output Structure for Collections Management" 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_FDM_COLL_INVOICE_ALV TYPE FDM_COLL_INVOICE_ALV.
The FDM_COLL_INVOICE_ALV table consists of various fields, each holding specific information or linking keys about ALV Output Structure for Collections Management data available in SAP. These include CUSTOMER (Customer Numbers), COLL_DEBITOR (Customer Numbers), COMP_CODE (Company Code), INVOICE_NO (Accounting Document Number).. 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 FDM_COLL_INVOICE_ALV 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 |
ITEM_STATE_ICON | Symbol: Status of Item | FDM_ITEM_STATE_ICON | CHAR | 132 | SYCHAR132 | ||||
CUSTOMER | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
COLL_DEBITOR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
COMP_CODE | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
INVOICE_NO | Accounting Document Number | BELNR_D | CHAR | 10 | ALPHA | BELNR | BLN | ||
DOC_ITEM | Number of Line Item Within Accounting Document | BUZEI | NUMC | 3 | BUZEI | BUZ | |||
FISCAL_YEAR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
BILLING_DOC | Billing Document | VBELN_VF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | VF | |
POSTING_DATE | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
INV_DATE | Document Date in Document | BLDAT | DATS | 8 | DATUM | ||||
DUE_DATE | Net Due Date | FAEDT_FPOS | DATS | 8 | DATUM | ||||
OVERDUE_BY | Days in Arrears by Net Due Date | VERZN | DEC | 5 | WRTV3 | ||||
PAYMENT_DATE | Date of Last Incoming Payment for Invoice | FDM_LAST_PAYMENT_DATE | DATS | 8 | DATUM | ||||
CURRENCY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
INVOICE_AMOUNT | Original Amount of Invoice or Credit | FDM_INVOICE_AMOUNT | CURR | 15(2) | WERTV8 | ||||
PAID_AMOUNT | Amount Paid | BDM_PAID_AMOUNT | CURR | 15(2) | WERT8 | ||||
OPEN_AMOUNT | Open Amount | FDM_OPEN_AMOUNT | CURR | 15(2) | WERTV8 | ||||
CREDITED_AMOUNT | Total of All Credits for Selected Invoice | FDM_CREDIT_AMOUNT | CURR | 13(2) | WERT7 | ||||
DISPUTED_AMOUNT | Disputed Amount | FDM_DISPUTED_AMOUNT | CURR | 13(2) | WERT7 | ||||
DUNNING_AMOUNT | Dunned Amount | FDM_DUNNING_AMOUNT | CURR | 15(2) | WERTV8 | ||||
DUNNING_LEVEL | Dunning level | MAHNS_D | NUMC | 1 | MAHNS | ||||
DUNNING_DATE | Date of Last Dunning Notice for Invoice | FDM_LAST_DUNNING_DATE | DATS | 8 | DATUM | ||||
PROMISED_AMOUNT | Outstanding Amount Promised | FDM_CURRENT_P2P_AMOUNT | CURR | 15(2) | WERT8 | ||||
P2P_LEVEL | Level of Promise to Pay | BDM_PROMISE_LEVEL | INT1 | 3 | INT1 | ||||
P2P_STATE | State of Promise to Pay | BDM_PROMISE_STATE | CHAR | 1 | BDM_PROMISE_STATE | ||||
P2P_DUE_DATE | Date for Which Payment Is Promised | BDM_PROMISE_DUE_DATE | DATS | 8 | DATUM | ||||
INST_IS_OVERDUE | Data element for domain BOOLE: TRUE (='X') and FALSE (=' ') | BOOLE_D | CHAR | 1 | BOOLE | ||||
PAYMENT_ARRANGED | Amount Arranged for Payment | FDM_PAYMENT_ARRANGED | CURR | 13(2) | WERT7 | ||||
DISCOUNT_AMOUNT | Cash discount amount in document currency | WSKTO | CURR | 13(2) | WERT7 | ||||
XBLNR | Reference Document Number | XBLNR1 | CHAR | 16 | XBLNR1 | ||||
.INCLU--AP | 0 | ||||||||
BSCHL | Posting Key | BSCHL | CHAR | 2 | Assigned to domain | BSCHL | |||
EXT_KEY | Case ID | FDM_EXT_KEY | CHAR | 12 | ALPHA | FDM_EXT_KEY | |||
STATUS_DESCRIPTION | Status of Dispute Case | FDM_STATUS_DESCRIPTION | CHAR | 30 | TEXT30 | ||||
REASON_CODE_DESCRIPTION | Description of Reason | FDM_REASON_CODE_DESCRIPTION | CHAR | 40 | TEXT40 | ||||
CREATE_TIME | Time of Creation of Dispute Case | FDM_CREATE_TIME | DEC | 15 | TSTPS | FDM_TIMESTAMP | |||
NO_OF_RSM | Number of Resubmissions | FDM_INV_NO_OF_RSM | INT4 | 10 | INT4 | ||||
NO_OF_NTS | Number of Notes | FDM_INV_NO_OF_NTS | INT4 | 10 | INT4 | ||||
SPGL_IND | Special G/L Indicator | UMSKZ | CHAR | 1 | Assigned to domain | UMSKZ | |||
.INCLU--AP | 0 | ||||||||
MANST | Dunning level | MAHNS_D | NUMC | 1 | MAHNS | ||||
MADAT | Last dunned on | MADAT | DATS | 8 | DATUM | ||||
MANSP | Dunning block | MANSP | CHAR | 1 | Assigned to domain | MANSP | |||
COLOR | Data Type 4 Characters | CHAR04 | CHAR | 4 | CHAR4 | MOD | |||
STATE_ICON | Icon: State of Promise to Pay | FDM_PROMISE_STATE_ICON | CHAR | 132 | SYCHAR132 | ||||
P2P_STATE_TXT | State of Promise to Pay: Text | FDM_PROMISE_STATE_TXT | CHAR | 60 | TEXT60 |
Key field | Non-key field |
How do I retrieve data from SAP structure FDM_COLL_INVOICE_ALV using ABAP code?
As FDM_COLL_INVOICE_ALV 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 FDM_COLL_INVOICE_ALV as there is no data to select.How to access SAP table FDM_COLL_INVOICE_ALV
Within an ECC or HANA version of SAP you can also view further information about FDM_COLL_INVOICE_ALV 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