FKK_P2P_PROPOSAL_CONF SAP (Propose Promise to Pay) Structure details
Description: Propose Promise to Pay
Related tables to FKK_P2P_PROPOSAL_CONF
Access table FKK_P2P_PROPOSAL_CONF
Structure field list including key, data, relationships and ABAP select examples
FKK_P2P_PROPOSAL_CONF 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 "Propose Promise to Pay" 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_FKK_P2P_PROPOSAL_CONF TYPE FKK_P2P_PROPOSAL_CONF.
The FKK_P2P_PROPOSAL_CONF table consists of various fields, each holding specific information or linking keys about Propose Promise to Pay data available in SAP. These include GPART (Business Partner Number), GPTXT (Short name of business partner), VKONT (Contract Account Number), BUKRS (Company Code).. 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 FKK_P2P_PROPOSAL_CONF 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 |
TICKET | Ticket Number Used to Store a Proposal | TICKET_KK | CHAR | 22 | SYCHAR22 | ||||
GPART | Business Partner Number | GPART_KK | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | |
GPTXT | Short name of business partner | BU_DESCRIP | CHAR | 50 | BU_TEXT50 | ||||
VKONT | Contract Account Number | VKONT_KK | CHAR | 12 | Assigned to domain | ALPHA | VKONT_KK | KTO | FKKVKP_F4 |
BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
BUTXT | Name of Company Code or Company | BUTXT | CHAR | 25 | TEXT25 | ||||
PPRSC | Reason for Promise to Pay | PPRSC_KK | CHAR | 2 | Assigned to domain | PPRSC_KK | |||
PPRSCT | Text 50 Characters | TXT50_KK | CHAR | 50 | TEXT50 | ||||
PPCAT | Category of Promise to Pay | PPCAT_KK | CHAR | 2 | Assigned to domain | PPCAT_KK | |||
PPCATT | Text 50 Characters | TXT50_KK | CHAR | 50 | TEXT50 | ||||
FPAYD | First Payment Date | FPAYD_KK | DATS | 8 | DATUM | ||||
DISMO | Payment Dates (Monthly, Every 2 Months, ...) | DISMO_KK | NUMC | 2 | DISMO_KK | ||||
DISMOT | Explanatory Text for Application Object | TXT60_KK | CHAR | 60 | CHAR60 | ||||
NOPDT | Number of Payment Dates | NOPDT_KK | NUMC | 2 | NUM02 | ||||
PRCUR | Currency for Payment | PRCUR_KK | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
MXPAM | Maximum Amount per Payment | MXPAM_KK | CURR | 13(2) | WERT7 | ||||
MXPAM_TOT | Maximum Amount per Payment | MXPAM_KK | CURR | 13(2) | WERT7 | ||||
PRAMT_TOT | Total Amount Including Charges and Interest | PRAMT_TOT_KK | CURR | 13(2) | WRTV7 | ||||
PRAMT_CHR | Charges for Promise to Pay | PRAMT_CHR_KK | CURR | 13(2) | WRTV7 | ||||
PRAMT_INT | Interest for Promise to Pay | PRAMT_INT_KK | CURR | 13(2) | WRTV7 | ||||
FAEDN_TO | Due date for net payment | FAEDN_KK | DATS | 8 | DATUM | ||||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
ERTIM | Time at which the object was created | ERTIM_KK | TIMS | 6 | UZEIT | ||||
PRRAT | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure FKK_P2P_PROPOSAL_CONF using ABAP code?
As FKK_P2P_PROPOSAL_CONF 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 FKK_P2P_PROPOSAL_CONF as there is no data to select.How to access SAP table FKK_P2P_PROPOSAL_CONF
Within an ECC or HANA version of SAP you can also view further information about FKK_P2P_PROPOSAL_CONF 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