Promises to Pay 
DataSource Transactional Data: 0CLM_P2P
This DataSource is used to extract all information about the promise to pay that was saved in Collections Management. It can be used together with the DataSource Invoice Status (0CLM_INVOICE) to evaluate the following data per customer, for example:
Number of Promises to Pay
Number of invoices
Details about the promise to pay
Amount billed, promised, and paid
The DataSource is loaded to the DataStore Object Promise to Pay (0CLM_DS04) and you can use this as InfoProvider.
Technical Data
Application Component | Collections Management (0FSCM-CLM) |
|---|---|
Available as of Release | Financial Basis 6.0, SP05 / SAP ECC 6.0, SP05 |
Shipment | SAP NetWeaver 2004s BI Content Add-On 3 SP02 |
Content Versions | There are no content versions. |
RemoteCube-Capable | No |
Delta-Capable | Yes |
Extraction from Archives | No |
Verifiable | No |
Data Modeling
Delta Update
The DataSource permits delta update with the delta procedureAIE (After-Images via Extractor).
Fields in the Extract Structure | Description of the Field in the Extract Structure | Table of Origin | Field in the Table of Origin |
|---|---|---|---|
CASE_GUID | FSCM-DM: GUID (Internal Key of Dispute Case) (GUID of promise to pay) | UDM_P2P_ATTR | CASE_GUID |
FIN_COMP_CODE | Company Code | UDM_P2P_ATTR | FIN_COMP_CODE |
FIN_CUSTOMER | Key of Customer in Accounts Receivable | UDM_P2P_ATTR | FIN_CUSTOMER |
INVOICE_NO | Accounting Document Number | ||
DOC_ITEM | Number of Posting Item within Accounting Document | ||
FISCAL_YEAR | Fiscal Year | ||
FIN_PROMISED_AMT | Amount Promised for Payment | UDM_P2P_ATTR | FIN_PROMISED_AMT |
FIN_PAID_AMOUNT | Amount Paid | UDM_P2P_ATTR | FIN_PAID_AMOUNT |
FIN_P2P_CURR | Currency of Promise to Pay | UDM_P2P_ATTR | FIN_P2P_CURR |
FIN_P2P_DUE_DATE | Due Date of Promise to Pay | UDM_P2P_ATTR | FIN_P2P_DUE_DATE |
FIN_P2P_DATE | Date on Which Promise to Pay Was Given | UDM_P2P_ATTR | FIN_P2P_DATE |
FIN_P2P_STATE | Promise to Pay State | UDM_P2P_ATTR | FIN_P2P_STATE |
FIN_P2P_LEVEL | Level of Promise to Pay | UDM_P2P_ATTR | FIN_P2P_LEVEL |
FIN_PROMISED_BY | Clerk that Gave the Promise to Pay | UDM_P2P_ATTR | FIN_PROMISED_BY |
FIN_LAST_PAYMENT | Date of Last Payment (last payment for a promise to pay) | UDM_P2P_ATTR | FIN_LAST_PAYMENT |
STAT_PARA | Case: System Status (system status of promise to pay) | SCMG_CASE_T_ATTR | STAT_PARA |
FIN_LOG_SYSTEM | Logical System (logical FI system) | UDM_P2P_ATTR | FIN_LOGICAL_SYSTEM |
LOGSYS | Logical System (logical system of Collections Management) | ||
P2P_COUNT | Numeric, 2-digit value (counter for promises to pay) | ||
CHANGE_TIME | Last Changed On | SCMG_CASE_T_ATTR | CHANGE_TIME |
Extractor Logic
The extractor extracts the data of the customer contact as separate data records. The basis for the extraction is the promise to pay (UDM_P2P_ATTR) table.
The extractor considers the time of the change to extract the data records of the customer contact that have been created or changed since the last upload.
For the aggregation in the BI system, the counters for the promises to pay are systematically set to the constant value 1: The other key figures are transferred on a one-to-one basis.
Verification of Key Figures
If necessary, you can check the key figures of the individual worklist items as follows:
In the source system, call up a worklist by choosing one of the following functions from the SAP Easy Access screen:
Accounting 
Financial Supply Chain Management Collections Management Worklists My Worklist 
- Accounting Financial Supply Chain Management Collections Management Worklists All Worklists
Choose
Edit Process Receivables Other Business Partner .In the dialog box, enter the relevant data.
The Process Receivables screen appears.
On the tab page Promises to Pay, select the required promise to pay to compare the following key figures:
Original Amount Promised
Amount Paid
Number of Promises to Pay
Unsychronized Backup Recovery in BI System
This DataSource uses its own time stamp for the delta update. If you import backup copies asynchronously, you therefore have to initialize the delta procedure for the DataSource again.