Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-PCT (Application Component) Product Catalog⤷
FF (Package) Cash Management
Basic Data
| Data Element | FF70ZTBE |
| Short Description | Include payment dates in the liquidity forecast |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 0 | |
| Long | 35 | Include payment dates |
| Heading | 0 |
Documentation
Definition
If you select this statement, the payment date determinations and assignments defined in Customizing (view V_T035Z) are included in the liquidity forecast.
If you want to use payment dates other than those in Customizing, you can enter them using the selection option in the liquidity forecast. However, you still need the customizing settings, so that you can identify for which groups and levels these payment dates are relevant.
For information on how to stipulate and periodically determine payment dates, read the F1 help for "Customer Payment Dates" and "Vendor Payment Dates".
Example
The following examples illustrate how assignment works in the liquidity forecast:
Suppositions:
- Today is September 10.
- Tolerance days for vendor payables: zero to two days (per view V_T042)
- Payment run made weekly
- Next date for customers: September 12
- Next date for vendors: September 14
Assignments for customers (dates in MM.YY format):
From planning date To planning date Summarized to payment date
0 12.09. 12.09.
13.09. 19.09. 19.09.
20.09. 26.09. 26.09.
27.09. 03.10. 03.10.
04.10 10.10 10.10.
11.10. 17.10. 17.10.
and so on
Assignment for vendors with no tolerance days:
From planning date To planning date Summarized to payment date
0 20.09. 14.09.
21.09. 27.09. 21.09.
28.09. 04.10. 28.09.
05.10. 11.10. 05.10.
12.10. 18.10. 12.10.
19.10. 25.10. 19.10.
and so on
Assignment for vendors with two tolerance days:
From planning date To planning date Summarized to payment date
0 17.09. 14.09.
18.09. 24.09. 21.09.
25.09. 01.10. 28.09.
02.10. 08.10. 05.10.
09.10. 15.10. 12.10.
16.10. 22.10. 19.10.
and so on
('From Planning Date' and 'To Planning Date' shift back 2 days due to tolerance days)
The starting point for assignment to a payment date is the planning date determined at the time the document was created or last changed (for more details, see Note 24883).
However, assignment to the correct payment date cannot always be guaranteed, because:
- the liquidity forecast cannot execute the complicated item selection logic the payment program carries out, because the liquidity forecast does not know the individual items, but works only with summary records.
- The liquidity forecast does not know the interim account used for the items.
- The planning date may have taken account of the expected check cashing time or bill of exchange term (at the time the document was created) and thereby the payment date assignment may not be correctly completed.
- The liquidity forecast cannot distinguish between genuine and parked documents, so that it may assign parked documents to payment dates.
- The system bases the planning date calculation on either cash discount terms 1 or the due date for net payment. If you are paying with cash discount terms 2, the payment date assignment in the liquidity forecast will be wrong.
- When making the assignment, the liquidity forecast cannot distinguish between invoice-related credits, those by value dates, and others. All credits are treated as if the payment program must pay them.
The "Include Payment Date" function can deliver good results if you use Customizing to restrict processing to customers who pay by automatic debits and to vendors (and customers managed as vendors) with bank transfers.
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in |
