Recording Actual and Commitment Payment Data 
Recording Actual and Commitment Payment Data
Use
You can use this function to monitor payment obligations and actual payments in your project.
Features
As a project is processed, various business transactions give rise to payment obligations and payments in it. If Project Cash Management is active, the system automatically records the payment data in the following objects:
The system reduces the payment obligations in stages as payments are made.
The payment obligations are recorded under their own value type. You can evaluate them in the information system.
When recording this data, the system takes account of postings assigned to projects in respect of the following business transactions:
Payments made in FI are not automatically copied to Project Cash Management. You must post them there manually.
See
Payment transfers, however, are taken into consideration.
See
Payment TransfersRecording Payment Data
Each posting assigned to a project generates a Project Cash Management document. The coding block in the document includes information on the account assignment object and the commitment item.
The payment data is only recorded if the commitment item has financial transaction 30.
Determining the Commitment Item
When you post to the project, the system defaults the commitment item from the G/L account. You can change this in the coding block.
If there is no commitment item in the G/L account, you must enter one manually.
Recording Data from Purchase Requisitions and Purchase Orders
The purchase requisitions assigned to the project or orders appear as payment commitments in the information system. The payment commitment is reduced when you enter payment obligations in the form of purchase orders.
In the case of purchase requisitions entered before Project Cash Management was activated, you can use program RKANBU01 to post the payment obligations in the project.
Purchase requisitions generated by an MRP run do not generate payment commitments.
You can reference purchase orders to purchase requisitions. This reduces the assigned payment obligation from the purchase requisition, or clears it altogether.
You can maintain invoicing plans for purchase orders. You use the invoicing plan to add detail to payment data.
See:
Payment Plan Data from the Invoicing Plan for a Purchase OrderDown Payments
In the case of down payments referencing purchase orders and posted manually, the system always defaults the commitment item from the purchase order account assignment for recording the payment data.
In the case of down payments not referencing purchase orders, the system defaults the commitment item from the special general ledger account. The special general ledger does not contain any data on the purpose of the down payment. For this reason, it may be a good idea not to stipulate any commitment item in the special general ledger, but to enter one manually when posting.
Down payments are recorded under value type 61.
You must post the actual down payment allocation manually. Down payment clearing postings are recorded under value type 63.
Date Recorded
The dates as of which payment data is recorded are listed in the table below.
Business Transaction |
Date Recorded |
Purchase requisition |
Delivery date: |
Down payment from invoicing plan for purchase order |
Down payment date from invoicing plan |
Purchase order |
Delivery date + term of payment |
Down payment request |
Due date |
Down payment |
Posting date |
Invoice |
Baseline date for payment + term of payment |
Down payment clearing |
Posting date |
Payment |
Posting date |