Hierarchy
BBPCRM (Software Component) BBPCRM⤷
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 | FPFIX |
| Short Description | ID for adopting billing/invoice date |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FPFIX | |
| 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 | 10 | Fixed date |
| Medium | 15 | Fixed date |
| Long | 20 | Fixed date |
| Heading | 3 | Fix |
Documentation
Procedure
Enter a code which controls whether the billing date in the billing plan is a fixed date or whether it is based on an actual or planned milestone date.
Use
A milestone from an event in the corresponding network is assigned toeach billing date in the billing plan. If you enter a value other than 0 in this field, the planned or actual date from the milestone is adopted as the billing date. Changes made to the planned or actual date are automatically made to the billing date.
If you enter 0 here, the billing date is fixed.
Example
Project: Installation of turbine at customer location
Planned delivery date in the milestone - 06.30.95
First billing date in the billing plan: Delivery of turbine
Fixed date indicator: 1 (Planned/actual date from milestone)
The planned delivery date is changed to 07.01.95. However, the customer still wants to pay on the original billing date. Therefore, you would change the fixed date ID for the date to 0 (fixed date).
Note
You must enter a value in this field if you are using milestone billing.
Supplementary Documentation - FPFIX 0001
Procedure
This is where you enter a code that controls whether the billing date is a fixed date or the planned or actual dates are copied from the milestone.
Use
A network milestone for a project is assigned to every billing plan date. If you enter a value other than 0 in this field, then the planned or actual date is copied from the milestone as the billing date. Changes to the milestone are automatically copied to the billing date.
If you enter a 0 here, the billing date is a fixed date.
Example
Project: Installation of a turbine
Planned delivery date in the milestone: 06.30.95
First billing date in the billing plan: Delivery of turbine
Fixed date indicator: 1 (Planned/actual date from milestone)
The planned delivery date is changed to 07.01.95. The customer, however, wants to pay on the original billing date. In this case, you would set the fixed date indicator to 0.
Note
If you are using milestone billing, you must enter a value in this field.
Use
Procedure
Examples
Dependencies
Supplementary Documentation - FPFIX 0002
WHAT_TO_DO&
This is where you enter a code that controls whether the billing date as a fixed date or the planned or actual dates are copied from the milestone.
USE&
A network milestone for a project is assigned to every billing plan date. If you enter a value other than 0 in this field, then the planned or actual date is copied from the milestone as the billing date. Changes to the milestone are automatically copied to the billing date.
If you enter a 0 here, the billing date is a fixed date.
EXAMPLE&
Project: Installation of a turbine
Planned delivery date in the milestone: 06.30.95
First billing date in the billing plan: Delivery of turbine
Fixed date indicator: 1 (Planned/actual date from milestone)
The planned delivery date is changed to 07.01.95. The customer, however, wants to pay on the original billing date. In this case, you could set the fixed date indicator to 0.
NOTE&
If you are using milestone billing, you must enter a value in this field.
Use
Procedure
Examples
Dependencies
Supplementary Documentation - FPFIX 0003
Use
For milestone billing the system includes the invoicing or billing plan data from the milestones when creating items.
You can determine whether the invoicing or planning data is automatically adapted to the milestone deadlines or not.
Procedure
- " " - no assignment to milestones possible
- 0 - fixed deadline, no transfer from milestones
When creating the item the system takes the deadline from the milestone. If the milestone deadline changes, the deadline will not fit in the invoicing or billing plan.
- 1 - Planned/actual deadline from milestones
When creating the item, the system transfers the deadline from the milestone. If the milestone deadline changes, the changed deadline is automatically transferred into the billing or invoicing plan.
Dependencies
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19991102 |
| SAP Release Created in |
