Hierarchy
⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷ VZ (Package) Application development R/3 RV central functions
Basic Data
Data Element | FPART |
Short Description | Billing plan/invoice plan type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FPART | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table | TFPLA |
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 | 10 | BillPlanTy |
Medium | 15 | BillingPlanType |
Long | 20 | Billing Plan Type |
Heading | 2 | EC |
Documentation
Use
Controls which fields are offered for processing. It also specifies how billing is performed for the billing dates in a billing plan of this type. The following options have been defined
- Periodic billing - the entire value to be billed is billed in full on each billing plan date
- Milestone billing - the total value to be billed is distributed between the individual billing plan dates (the value billed on each date can be fixed amount or a percentage)
Example
Periodic billing is used to bill rental or maintenance contracts.
Milestone billing is used to bill projects.
Supplementary Documentation - FPART 0001
Use
Controls which fields are available for processing and determines how calculation for the invoice dates in an invoice plan of this type is carried out . The options are:
- Periodic billing - a defined value to be billed is fully billed at every date
- Partial billing - the total value to be billed is split up among the various invoice plan dates (the value billed at every date can be an absolute amount or a percentage.
Procedure
Examples
The periodic invoice plan is well suited for billing rental or leasing payments.
The partial billing plan is well suited for step-by-step payments of a total amount, e.g. for a building devolopment scheme, 30% of the value is billed after production of the first stage of construction, another 30% after the completion of the second stage and the rest upon completion.
Dependencies
Supplementary Documentation - FPART 0002
Use
Checks which of the fields are provided for processing and determines how calculation of the invoice deadlines is carried out in an invoicing plan of this type.
The invoicing plan type PA is assigned to the invoicing plan for the transaction or component.
Procedure
Examples
Dependencies
History
Last changed by/on | SAP | 19991102 |
SAP Release Created in |