UDM_BI_COLL_P2P SAP (Extract Structure for Promise to Pays) Structure details
Description: Extract Structure for Promise to Pays
Related tables to UDM_BI_COLL_P2P
Access table UDM_BI_COLL_P2P
Structure field list including key, data, relationships and ABAP select examples
UDM_BI_COLL_P2P 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 "Extract Structure for Promise to Pays" 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_UDM_BI_COLL_P2P TYPE UDM_BI_COLL_P2P.
The UDM_BI_COLL_P2P table consists of various fields, each holding specific information or linking keys about Extract Structure for Promise to Pays data available in SAP. These include FIN_COMP_CODE (Company Code), FIN_CUSTOMER (Key of Customer in Accounts Receivable Accounting), INVOICE_NO (Accounting Document Number), DOC_ITEM (Number of Line Item Within Accounting Document).. 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 UDM_BI_COLL_P2P 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 |
| CASE_GUID | FSCM-DM: GUID (Internal Key of Dispute Case) | BDM_CASE_GUID | CHAR | 32 | SYSUUID_C | ||||
| FIN_COMP_CODE | Company Code | BDM_COMP_CODE | CHAR | 4 | CHAR4 | ||||
| FIN_CUSTOMER | Key of Customer in Accounts Receivable Accounting | UDM_KUNNR | CHAR | 10 | ALPHA | UDM_KUNNR | |||
| 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 | ||
| FIN_PROMISED_AMT | Amount Promised for Payment | BDM_PROMISED_AMOUNT | CURR | 15(2) | WERT8 | ||||
| FIN_PAID_AMOUNT | Amount Paid | BDM_PAID_AMOUNT | CURR | 15(2) | WERT8 | ||||
| FIN_P2P_CURR | Currency of Promise to Pay | BDM_PROMISE_CURR | CUKY | 5 | Assigned to domain | WAERS | |||
| FIN_P2P_DUE_DATE | Date for Which Payment Is Promised | BDM_PROMISE_DUE_DATE | DATS | 8 | DATUM | ||||
| FIN_P2P_DATE | Date on Which Promise to Pay Was Given | BDM_PROMISE_DATE | DATS | 8 | DATUM | ||||
| FIN_LAST_PAYMENT | Date of Last Payment | BDM_LAST_PAYMENT_DATE | DATS | 8 | DATUM | ||||
| FIN_P2P_STATE | State of Promise to Pay | BDM_PROMISE_STATE | CHAR | 1 | BDM_PROMISE_STATE | ||||
| FIN_P2P_LEVEL | Level of Promise to Pay | BDM_PROMISE_LEVEL | INT1 | 3 | INT1 | ||||
| FIN_PROMISED_BY | Clerk That Gave the Promise to Pay | BDM_PROMISED_BY | CHAR | 40 | TEXT40 | ||||
| LOGSYS | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| FIN_LOG_SYSTEM | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| STAT_PARA | Case: System Status | SCMGSTATPARA | CHAR | 3 | CHAR03 | ||||
| P2P_COUNT | 2-Digit Numeric Value | NUM2 | NUMC | 2 | NUM2 | ||||
| CHANGE_TIME | Last Changed On | SCMG_CHANGE_TIME | DEC | 15 | TSTPS | SCMG_TIMESTAMP |
| Key field | Non-key field |
How do I retrieve data from SAP structure UDM_BI_COLL_P2P using ABAP code?
As UDM_BI_COLL_P2P 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 UDM_BI_COLL_P2P as there is no data to select.How to access SAP table UDM_BI_COLL_P2P
Within an ECC or HANA version of SAP you can also view further information about UDM_BI_COLL_P2P 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