Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-AB-IFW (Application Component) Invoice Forecasting⤷
CIWB (Package) Invoice Forecasting Worklist: Core objects
Basic Data
| Data Element | IFW_DE_PAYDD_DET |
| Short Description | Payment Due Date Control |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | IFW_DO_PAYDD_DET | |
| 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 | 0 | |
| Heading | 0 |
Documentation
Definition
Payment due date of invoice or billing document that appears in the invoice forecasting worklist (IFW).
Use
If no (real or forecast) invoice or billing document exists, the payment due date is a planned date that may come from the pricing and payment events (PPE). This kind of payment due date serves business processes where the expected payment due date controls the invoice or billing document creation date rather than the other way round (typical commodity business process).
As soon as a real invoice or billing document exists, the payment due date is always the one that is evaluated from the payment terms, regardless of any PPE events.
If an invoice or billing document is forecast, the payment due date is also filled by means of the payment terms, provided no PPE event exists.
Dependencies
If the payment due date is intended to come from PPE events, PPE must first be activated place. As a prerequisite, you have activated business function ISR_GLT_COMMODITY_5.
Example
History
| Last changed by/on | SAP | 20110901 |
| SAP Release Created in | 606 |
