FDM_COLL_P2P_DETAIL SAP (Promise to Pay Detail) Structure details
Description: Promise to Pay Detail
Related tables to FDM_COLL_P2P_DETAIL
Access table FDM_COLL_P2P_DETAIL
Structure field list including key, data, relationships and ABAP select examples
FDM_COLL_P2P_DETAIL 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 "Promise to Pay Detail" 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_P2P_DETAIL TYPE FDM_COLL_P2P_DETAIL.
The FDM_COLL_P2P_DETAIL table consists of various fields, each holding specific information or linking keys about Promise to Pay Detail data available in SAP. These include CASE_GUID (FSCM-DM: GUID (Internal Key of Dispute Case)), PROMISED_AMT (Amount Promised for Payment), MAX_P2P_AMOUNT (Maximum Amount for Promise to Pay), P2P_AMT_BEFORE (Amount Promised for Payment).. 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 FDM_COLL_P2P_DETAIL 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_TYPE | FSCM-DM: Case Type | BDM_CASE_TYPE | CHAR | 4 | CHAR04 | ||||
CASE_GUID | FSCM-DM: GUID (Internal Key of Dispute Case) | BDM_CASE_GUID | CHAR | 32 | SYSUUID_C | ||||
PROMISED_AMT | Amount Promised for Payment | BDM_PROMISED_AMOUNT | CURR | 15(2) | WERT8 | ||||
MAX_P2P_AMOUNT | Maximum Amount for Promise to Pay | FDM_MAX_P2P_AMOUNT | CURR | 15(2) | WERT8 | ||||
P2P_AMT_BEFORE | Amount Promised for Payment | BDM_PROMISED_AMOUNT | CURR | 15(2) | WERT8 | ||||
P2P_CURR | Currency of Promise to Pay | BDM_PROMISE_CURR | CUKY | 5 | Assigned to domain | WAERS | |||
P2P_DUE_DATE | Date for Which Payment Is Promised | BDM_PROMISE_DUE_DATE | DATS | 8 | DATUM | ||||
P2P_DATE | Date on Which Promise to Pay Was Given | BDM_PROMISE_DATE | DATS | 8 | DATUM | ||||
PROMISED_BY | Clerk That Gave the Promise to Pay | BDM_PROMISED_BY | CHAR | 40 | TEXT40 | ||||
P2P_STATE | State of Promise to Pay | BDM_PROMISE_STATE | CHAR | 1 | BDM_PROMISE_STATE | ||||
P2P_REF | Promise to Pay Reference | FDM_P2P_REF | CHAR | 30 | CHAR30 | ||||
CONTACT_MAIL | e-mail Address of Contact Person at Business Partner | FDM_CONTACT_EMAIL | CHAR | 128 | TEXT128 | ||||
CONTACT_TEL | Telephone Number of Contact Person at Business Partner | FDM_CONTACT_PHONE | CHAR | 30 | CHAR30 | ||||
CONTACT_FAX | Fax Number of Contact Person at Business Partner | FDM_CONTACT_FAX | CHAR | 30 | CHAR30 | ||||
CONTACT_FAXC | Country of Fax Number of Contact Person | FDM_CONTACT_FAXC | CHAR | 3 | Assigned to domain | LAND1 | |||
CONTACT_KEY | Number of contact person | PARNR | NUMC | 10 | PARNR | VPA | |||
NO_OF_INST_BEFORE | Number of Installments in the Promise to Pay in Installments | BDM_NO_OF_INSTMNTS | INT4 | 10 | INT4 | ||||
MULT_INV_CONTEXT | UUID in character form | SYSUUID_C | CHAR | 32 | SYSUUID_C | ||||
EDIT_MODE | Data element for domain BOOLE: TRUE (='X') and FALSE (=' ') | BOOLE_D | CHAR | 1 | BOOLE |
Key field | Non-key field |
How do I retrieve data from SAP structure FDM_COLL_P2P_DETAIL using ABAP code?
As FDM_COLL_P2P_DETAIL 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_P2P_DETAIL as there is no data to select.How to access SAP table FDM_COLL_P2P_DETAIL
Within an ECC or HANA version of SAP you can also view further information about FDM_COLL_P2P_DETAIL 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