Hierarchy
⤷ FI-CA (Application Component) Contract Accounts Receivable and Payable
⤷ FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
Data Element | STUDT_KK |
Short Description | Deferral to |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATUM | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | DEFERRAL | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Deferral |
Medium | 15 | Deferral to |
Long | 20 | Deferral to |
Heading | 10 | Deferral |
Documentation
Definition
Date to which an open item is deferred beyond the actual due date.
Use
The date is used as the basis for the automatic creation of dunning notices or debit memos instead of the due date specification.
Note for the industry component Insurance
The control elements of the contract account also contain incoming and outgoing payment agreements. Here you can also define periodic dunning frequencies. These are stored in the individual posting in the deferral field. The values determined by the frequencies are considered by the dunning run and the payment run.
Incoming payment agreements
Periodic incoming payment agreements are possible for each contract account. Incoming payment agreements only apply for receivables, that is, amounts larger than zero. As well as the frequency, incoming payment agreements also contain a base date to which the frequency applies. On posting, the deferral field is always determined if a base date is given for the contract account and receivables are posted. In the determination, the base date is increased by the frequency until a date is reached that is after or equal to the maximum of the due date of the individual posting to be created and the system date. The date thus determined is placed in the deferral field.
Outgoing payment agreements
Outgoing payments are possible for every business partner of a contract account. Outgoing payment agreements are only valid for payables. Payables are the amounts whose value is smaller than zero. As well as the frequency, outgoing payment agreements also contain a base date to which the frequency applies. On posting, the deferral field is always determined if a base date is given for the account partner and payables are posted. In the determination, the base date is increased by the frequency of the account partner until a date is reached that is after or equal to the maximum of the due date of the individual posting to be created and the system date. The date thus determined is placed in the deferral field.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |