FIBL_OPAY_DOC_IF SAP (Interface: Post Online Payment) Structure details
Description: Interface: Post Online Payment
Related tables to FIBL_OPAY_DOC_IF
Access table FIBL_OPAY_DOC_IF
Structure field list including key, data, relationships and ABAP select examples
FIBL_OPAY_DOC_IF 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 "Interface: Post Online Payment" 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_FIBL_OPAY_DOC_IF TYPE FIBL_OPAY_DOC_IF.
The FIBL_OPAY_DOC_IF table consists of various fields, each holding specific information or linking keys about Interface: Post Online Payment data available in SAP. These include DOC_TYPE (Document Type), PSTNG_DATE (Posting Date in the Document), PAYM_CURR (Payment Request Currency Key), PAYM_AMOUNT (Payment Request Amount in Payment Currency).. 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 FIBL_OPAY_DOC_IF 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 |
| COMP_CODE | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| DOC_TYPE | Document Type | BLART | CHAR | 2 | Assigned to domain | BLART | BAR | ||
| PSTNG_DATE | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
| PAYM_CURR | Payment Request Currency Key | PRQ_PACUR | CUKY | 5 | Assigned to domain | WAERS | |||
| PAYM_AMOUNT | Payment Request Amount in Payment Currency | PRQ_AMTFC | CURR | 13(2) | WERT7 | ||||
| LOC_CURRCY | Local Currency | HWAER | CUKY | 5 | Assigned to domain | WAERS | |||
| LOC_AMOUNT | Amount in Local Currency | DMBTR | CURR | 13(2) | WERT7 | ||||
| EXCH_RATE | Exchange rate | KURSF | DEC | 9(5) | EXCRT | KURSF | |||
| XINCOMING_PMNT | Indicator: Payment Method Used for Incoming Payments? | XEINZ | CHAR | 1 | XFELD | ||||
| PARTNER_ACCOUNT | Business Partner | PRQ_PARNO | CHAR | 10 | ALPHA | PRQ_PARNO | |||
| ITEM_TEXT | Reference type text | REFTXT | CHAR | 50 | TEXT50 | ||||
| BUS_AREA_BANK | Business Area: Offsetting Posting | PRQ_ZGSBR | CHAR | 4 | Assigned to domain | GSBER | GSB | ||
| DEBITED_ACCT | Account to be Debited: G/L Account/Customer/Vendor | DEBITED_ACCT | CHAR | 10 | Assigned to domain | ALPHA | MUSTR | ||
| ACCT_TYPE | Account type payment advices | BF_KOARTAV | CHAR | 1 | BF_KOARTAV | ||||
| POST_KEY | Posting Key | BSCHL | CHAR | 2 | Assigned to domain | BSCHL | |||
| DOC_REF_TXT | Internal Reference: Item Text | INTREF | CHAR | 50 | TEXT50 | ||||
| BUS_AREA | Business Area | GSBER | CHAR | 4 | Assigned to domain | GSBER | GSB | ||
| VALUE_DATE_SENDER | Value Date for the Sending Bank | PRQ_VALDT | DATS | 8 | DATUM | ||||
| TRADE_ID | Company ID of trading partner | RASSC | CHAR | 6 | Assigned to domain | ALPHA | RCOMP | PGS | |
| PMTMTHSUPL | Payment Method Supplement | UZAWE | CHAR | 2 | Assigned to domain | UZAWE | |||
| PAYMT_REF | Payment Reference | KIDNO | CHAR | 30 | CHAR30 |
| Key field | Non-key field |
How do I retrieve data from SAP structure FIBL_OPAY_DOC_IF using ABAP code?
As FIBL_OPAY_DOC_IF 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 FIBL_OPAY_DOC_IF as there is no data to select.How to access SAP table FIBL_OPAY_DOC_IF
Within an ECC or HANA version of SAP you can also view further information about FIBL_OPAY_DOC_IF 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