...
The first entry in the Odometer Status History is created when the contract is activated (the Initial Mileage from the object is recordedwritten). Other records can then be created manually, from a service permit, from fuel card transactions, or by another import.
...
The Odometer Status History can be accessed opened from the Financed Object:
When entering the odometer status of on an object via the new button, the new system transfers the data from the object to the record in the history.
...
When entering a service permission, the user writes the odometer status mileage on the allowance card: which the system writes in the odometer status history after changing the allowance status to "Approved".
If the user enters a mileage so large that it would occur when calculating the predicted mileage, the system saves the record, but does not calculate the predicted mileage and writes 0:
...
There is also a record in the The Odometer Status History is also recorded from fuel card transactions. After importing fuel card transactions when creating an unposted , when a non-posted purchase invoice is created, the system records writes the odometer status from each fuel card transaction, provided that the Item Handover Date item handover date is filled in on the item.
An entry in the Odometer Status History is also from the Car Rental module, if the vehicle has the Leasing Object No. filled in on the car rental card. When entering or changing km on the rental card, the system will ask: "The mileage has been changed. Do you want to insert a new mileage into the Odometer Status History of the financed object OL170035_01 Financed Object?"
If the user clicks No, the mileage will not be saved in the odometer status historyOdometer Status History.
If the user clicks on Yes, the mileage will be saved in the odometer status history and the value in the Area = Car Rental field will be filled in the created row.
...
It is possible to open a card from a the record (or if the user wants to create a new record manually).
...
Financed Object No.
Object No. according to the contract for which the entry was made
Completes Fills in the system automatically when you create a record is created.
Licence Plate No.
From the financed object, the system will fill in add automatically when creating a the record is created
Chassis No. (VIN)
From the financed object, the system will fill in add automatically when creating a the record is created
BrandMake
From the financed object, the system will fill in add automatically when creating a the record is created
Model Line
From the financed object, the system will fill in add automatically when creating a the record is created
Model
From the financed object, the system will fill in add automatically when creating a the record is created
Financing Contract No.
Fills in the system automatically when a record is created
Customer No.
Completes Fills in the system automatically when creating a record from a financing contract
Customer Name
Completes Fills in the system automatically when creating a record from a financing contract
Customer Business Place No.
Completes Fills in the system automatically when creating a record from a financing contract
Customer Business Place Name
Completes Fills in the system automatically when creating a record from a financing contract
Contractual Mileage
It The system fills the system automatically when creating a record from the field of the same name from the last row of the Contractual Distance table (Contractual Distance+Initial Odometer Status).
Returned Object
Default N
Changes the system to Y on the line to Y automatically if Returned Odometer Status is entered on the item card.
Created
Row creation datetimeThe date and time the line was created
Created
Identification of the user who created the record
Mileage tab:
Area:
Specifies how the entry listing was created
Blank – for manual writing
Maintenance – the entry was created made from the maintenance permission
Tire service – the entry was created from the processing of the tire service data record
Fuel – the entry was made during the processing of fuel card transactions
Car Rental Company – the entry was made during the entry/change of when entering/changing the km on the issued rental rent in the Car Rental Company
Document No.
will be filled in according to the area of origin,
Maintenance permission number for the Service Maintenance area.
Entry No. Fuel Card Transaction Fuel Area
Approval No.
Approval number from the service permission. It is usually listed indicated on purchase invoices from
Mileage Date
The specific date to which the mileage relates.
Odometer Status (Mileage)
Mileage value as of the on a given date
After manual entry Values The values will be checked (the checks are on the page, not on the table. I.e. when entering e.g. fuel transactions, service allowances, no checks will be performed):
After entering, a check will be made to see if the Mileage Date is filled in:
If not, it displays you will receive an error that the field must be filled in
If it is, it can enter Mileage
After entering the Mileage value, the previous line is checked:
The system will find finds the record
Financed Object No.=sameSame
Mileage Date<= as on the created record
Entry No. = Highest
Note: We are looking for the nearest lower line, but according to Mileage Date
It then compares whether the Mileage (enteredspecified)>Mileage from the previous line is true
If it is true, it writes the value and continues
If it doesn't, it asks if the status is smaller less than the previous one and if it should be saved: "Mileage is lower than the last record in history. Save record?" or "The mileage is lower than the last record in history. Do you want to save the record?"
If the user confirms Yes, they write the value and continue.
If it confirms No, it doesn't save the Mileage value, and the user can enter a different value.
After entering a value and checking the previous value, the next row is also checked
The system finds the record:
Financed Object No.=sameSame
Mileage Date>= as on the created record
Entry No. = lowest
Note: We are looking for the next higher line according to Mileage Date
It then compares whether the Mileage (entered)<Mileage from the following next line is true
If it is true, it writes the value and continues
If it doesn't, it asks if the status is greater than the following and whether to save it:
ENG: Mileage is greater than the next record in history. Save record?
EN: The mileage is greater than the next record in history. Do you want to save the recording?
SK: Stav tahometra tachometer je väčší ako nasledujúci záznam v histórii. Chcete uložiť záznam?
If the user confirms Yes, they write the value and continue.
If it confirms No, it doesn't save the Mileage value, and the user can enter a different value.
Planned Mileage
Does the system calculate automatically after entering the Odometer Status Date
Planned Mileage = round(Initial Mileage (4026685) + (Contractual Distance) x Contract Duration Days; 0)
Total Days = Contractual End Date (10100)) – Handover Date
Number of Days = Mileage Date – Handover Date
When activated, fill Mileage without recalculation
If the user has entered a the mileage so large that the predicted mileage would overflow during the calculation, the system saves the record, but does not calculate the predicted states and writes 0
Km Under/Over Limit
The system calculates automatically after calculating the Planned Mileage field:
Km under/over Limit= Mileage (10) - Planned Mileage (60)
Ratio km- %
The Will the system automatically calculatescalculate:
Ratio km % = round(((Km Under/Over Limit*100)/(Planned Mileage-Initial Mileage (4026685)); 0)
Ration km (value)
The Will the system automatically calculatescalculate:
Ratio km (value) = round(((Km Under/Over Limit)/(Planned Mileage-Initial Mileage (4026685)); 2)
Lower Tolerance %
Taken from a financing contract
Lower Tolerance
Taken from a financing contract
Lower Tolerance Actual
Does the system calculate automatically when a row line is created:
Lower Tolerance Actual = round((Planned Mileage (60)-Initial Mileage (4026685)))*Lower Tolerance % (85)/100; 2)
Upper Tolerance %
Taken from a financing contract
Upper Tolerance
Taken from a financing contract
Upper Tolerance Actual
Does the system calculate automatically when a row line is created:
Upper Tolerance Actual = round((Planned Mileage (60)-Initial Mileage (4026685)))*Upper Tolerance % (75)/100; 2)
Predicted Mileage
Does the system automatically calculate:
Predicted Mileage = round((Mileage-Initial Mileage (4026685)) * Total number of days)/Number of days; 0)+Initial Mileage (4026685)
Total Number of Days = Contractual End Date – Handover Date
Number of Days = Mileage Date – Handover Date
Predicted Mileage Difference
Does the system automatically calculate:
Predicted Difference = Predicted Mileage - Initial Mileage (4026685)- Contractual Distance
Predicted Yearly Difference
Does the system automatically calculate:
Predicted Yearly Difference = round((Predicted Difference*12)/Financing Period (in Months); 0)
Predicted Contractual Distance
The system calculates automatically
Predicted Contractual Distance = Predicted Mileage (79500)-Initial Mileage (4026685) from API Financed Object (4026560)
Predicted Yearly Distance
Does the system automatically calculate:
Predicted Yearly Distance = round((Predicted Contractual Distance*12)/Financing Period (in Months); 0)
Predicted Financing Period (in months)
Does the system automatically calculate:
Predicted Financing Period (in Months) = round(Total number of days / 30.4; 0)
Total Days=Contractual Distance (10055) from API Financing Contract Header (4026397) / Km per day
km Km per day=(Mileage (10)-Initial Mileage (4026685) from API Financed Object (4026560)) / Number of days; 0)
Number of Days = Mileage Date – Handover Date