AVAG Full Service Leasing (SGF)

The Fullservice Contract is a special Contract provided by the AVAG Holding where – depending on what the Business Partners desires - several packages can be included.

This Fullservice Contract Offer can only be created/adjusted during within the Sales Process (Sales Lead/Opportunity) and is always in combination with a Vehicle Sales Offer.

The creation of such an Offer is optionally possible

Entity

3 new entities were created:

IDMS_FullServiceContract: Stores the header details of the Fullservice Contract
IDMS_FullServiceContractItem: Stores the selected services of the Fullservice Contract
IDMS_FullContractService: Stores combinations of specific service types (Storage, Changing Wheels, Service Replacement Vehicle) that can be added at the Fullservice Contract

The equivalent tables are the following:

@IDMS_FULLSRVCON
@IDMS_FULLSRVCONITM
@IDMS_FULLCONTRACSRV

@IDMS_FULLSRVCONITM works as a sub-collection of @IDMS_FULLSRVCON (similar to @IDMS_DOCUMENT and @IDMS_DOCUMENTITEM) but without using SL

Setup

A new setup page was created which is used to manage the specific service types that can be added at the Fullservice Contract. The URL and Business Case are the following:

~/SetupEntities/List/SalesAndLeads/IDMS_FullContractService
BC: 1973

The service types that can be configured at the setup page are the following:

Storage
WheelChanging
ServiceReplacementVehicle

The following fields at the form are required:

Product Type
Running Time
Valid From
Monthly Net Rate

The field Total Net Amount is automatically calculated based on the following formula:

round({MonthlyNetRate} * {RunningTime})

The Time Period (Valid from/Valid until) must be unique per Product Type and Running Time.

Process

In order to support this functionality, new workflow steps (transitions) need to be created to fulfill those needs:

Create/Update Fullservice Contract Offer
Accept Fullservice Contract Offer
Decline Fullservice Contract Offer

Along with these transitions, new external functions were created in order to support these steps:

CreateOrUpdateFullserviceContractOffer
AcceptFullserviceContractOffer
DeclineFullserviceContractOffer

Also, a new transition required view was created in order to handle Fullservice Contract Offer create or update process:

FullserviceContractOfferView

For more information on the workflow setup, check here

Transition required view sections

Here the first 6 fields represent the "header" of the Fullservice Contract document. The first 4 fields are required:

Manufacturer Key. No.
Type Key No.
Mileage per Year
Running Time in Months

If the "Framework Agreement Manufacturer" checkbox is checked, when printing the main document which is the Fullservice Contract Offer, an extra document is also printed and "merged" to the final document.

If the “Send offer via email” checkbox is checked, the fullservice contract document is sent via email notification when saving the transition at the “Activities” tab.

Services

Below of the above fields, a table with all the available services appears, only if the user has filled the required fields.

The services can be separated in 3 categories:

Setup services: Data for these services are retrieved via the setup page that was described above
- Storage
- Wheel Changing
- Service Replacement Vehicle
  - The filter that is applied for these services is the following:
    - Product Type = <Type of the selected service> AND
    - Running Time = <Running time in months (from the header)> AND
    - Valid from / until = valid Date Period (Current Date must be between "Valid from" and "Valid until")
Manual services: The total amount for those services is entered manually from the user
- Wheel Package Winter
- Tyre package Winter
- Tyre Package Summer
- Tyre Package All Weather
- Manufacturer Grant
Technical Maintenance services: Data for these services are provided via the TecAlliance web services
- Technical Maintenance
- Technical Maintenance + Consumption

There are also 2 hybrid-services. They are filled from the data of the "Technical Maintenance" and "Technical Maintenance + Consumption" services according to the following formulas:

Cost per km (additional km driven)
- ((Technical Maintenance + Technical Maintenance + Consumption) * 12) / (Mileage per Year * 2)
Refund per km (viewer km driven)
- ((Technical Maintenance + Technical Maintenance + Consumption) * 12) / (Mileage per Year * 0.75)

The "Manufacturer Grant" service acts as a discount (flat value, not percentage)

The "Cost per km" and "Refund per km" services are not part of the Total monthly Amount of the contract.

Regarding the columns of the table:

The second column represents the total amount of the service (for the whole running time)
The third column contains a checkbox "Include in Contract" which when clicked adds the selected service to the offer
The last 2 columns show the Net Amount per Month and Gross Amount per Month, respectively

The VAT used at the last column of the services' table is coming from the Business Partner

Finally, there are 4 buttons at the view:

Create Insurance Offer: Starts a communication with the AVS portal by opening a new tab at the user's browser. No data from this communication are retrieved back to OD. It is an one-way communication
Print: Prints the offer document using one of the configured providers
Cancel: Redirects the user back to the activities tab in order to select again the desired transition
Apply: Saves any changes at the offer and redirects the user back to the activities tab in order to save the transition

AVS portal setup

For the AVS communication, we created 4 setup keys that need to be configured properly:

AVSInterfacingManagerUrl
AVSGrantType
AVSClientId
AVSClientSecret
AVSApplicationID_{CompanyName} (value is company ID)

Then, for username and password temporarily we used the following 2 setup keys

AVSUsername
AVSPassword

TecAlliance interface setup

The communication with the TecAlliance interface is done via the Interfaces team. Thus, the following setup keys need to be configured properly:

ODExchangeAPIUrl
ODExchangeAPIUnm
ODExchangeAPIPwd
ODExchangeAPICId
ODExchangeAPIDId

From TecAlliance we receive values for the following 2 services:

Technical Maintenance
Technical Maintenance + Consumption

For more information on the defined AVAG setup keys check here

Printing

1 new Printing Business Type was created:

Fullservice Contract Document

Currently supports only the internal print provider

Setup

First you need to select which printing service will be used. Look here for more info about this setup
The setup key for the Fullservice Contract Document printout's Template name is called FullserviceContractPrintoutTemplateName
The setup key for the Fullservice Contract Framework Agreement printout's Template name is called FullserviceContractFrameworkAgreementTemplateName
If you use the internal OD printing system then you have to create an RTF following these instructions

Fullservice Contract Document printout fields

Property

Type

Comments

Header

{FullserviceContractId}

string

Unique ID (unique over the whole AVAG Group – AVAG Area ID as Prefix)

{SalesLeadCode}

string

Code from the Lead/Opportunity (DocEntry)

{VehicleCode}

string

Vehicle ID from the Vehicle

{Status}

string

Possible Values:

Empty (will be set when new Offer is being created via external function)
Accepted (will be set when Offer is being accepted (WF-Step via external function)
Declined (will be set when Offer is being declined (WF-Step via external function)

{ManufacturerKeyNo}

string

{TypeKeyNo}

string

{MileagePerYear}

string

{RunningTimeMonths}

string

{ContractDate}

date

{BankAccountInformation}

string

{FrameworkAgreementManufacturer}

bool

If 'true', then an additional template must be printed on the Service Contract

Customer

{CustomerName}

string

Full name of customer

{CustomerZipCode}

string

Zip-Code of the customer's address

{CustomerCity}

string

Customer's city

{CustomerStreet}

string

Customer's street

{CompanyStreetNo}

string

Company's street Number

{CustomerEmail}

string

Customer's email

{CustomerTelephone1}

string

Customer's phone number

{CustomerPhone}

string

Customer's mobile phone number

{CustomerCode}

string

Customer's code (Business Partner code)

{BusinessPartnerName}

string

Business partner's name

{CompanyName}

string

Company name (where the user is logged in)

{CompanyZipCode}

string

Zip-Code of teh company's address

{CompanyCity}

string

City where the company is located

{CompanyStreet}

string

Company's street address

{CustomerStreetNo}

string

Company's street address number

{CompanyEmail}

string

Company's email

{CompanyPhone}

string

Company's phone number

{CompanyMobile1}

string

Company's mobile phone number

{CompanyCode}

string

Company's code

Employee

{EmployeeOfficePhone}

string

Office phone number of the sales person

{EmployeeMobilePhone}

string

Office mobile phone number of the sales person

Services

{TechnicalMaintenance}

bool

Checkbox in the column Include in Contract

{TechnicalMaintenanceTotalAmount}

string

Net Total Amount (whole running time)

{TechnicalMaintenancePrice}

string

Net Amount per Month

{TechnicalMaintenancePriceGross}

string

Gross Amount per Month

{TechnicalMaintenanceAndConsumption}

bool

Checkbox in the column Include in Contract

{TechnicalMaintenanceAndConsumptionTotalAmount}

string

Net Total Amount (whole running time)

{TechnicalMaintenanceAndConsumptionPrice}

string

Net Amount per Month

{TechnicalMaintenanceAndConsumptionPriceGross}

string

Gross Amount per Month

{WheelPackageWinter}

bool

Checkbox in the column Include in Contract

{WheelPackageWinterTotalAmount}

string

Net Total Amount (whole running time)

{WheelPackageWinterPrice}

string

Net Amount per Month

{WheelPackageWinterPriceGross}

string

Gross Amount per Month

{TyrePackageWinter}

bool

Checkbox in the column Include in Contract

{TyrePackageWinterTotalAmount}

string

Net Total Amount (whole running time)

{TyrePackageWinterPrice}

string

Net Amount per Month

{TyrePackageWinterPriceGross}

string

Gross Amount per Month

{TyrePackageSummer}

bool

Checkbox in the column Include in Contract

{TyrePackageSummerTotalAmount}

string

Net Total Amount (whole running time)

{TyrePackageSummerPrice}

string

Net Amount per Month

{TyrePackageSummerPriceGross}

string

Gross Amount per Month

{TyrePackageAllWeather}

bool

Checkbox in the column Include in Contract

{TyrePackageAllWeatherTotalAmount}

string

Net Total Amount (whole running time)

{TyrePackageAllWeatherPrice}

string

Net Amount per Month

{TyrePackageAllWeatherPriceGross}

string

Gross Amount per Month

{Storage}

bool

Checkbox in the column Include in Contract

{StorageTotalAmount}

string

Net Total Amount (whole running time)

{StoragePrice}

string

Net Amount per Month

{StoragePriceGross}

string

Gross Amount per Month

{WheelChanging}

bool

Checkbox in the column Include in Contract

{WheelChangingTotalAmount}

string

Net Total Amount (whole running time)

{WheelChangingPrice}

string

Net Amount per Month

{WheelChangingPriceGross}

string

Gross Amount per Month

{ManufacturerGrant}

bool

Checkbox in the column Include in Contract. Acts as a flat discount

{ManufacturerGrantTotalAmount}

string

Net Total Amount (whole running time)

{ManufacturerGrantPrice}

string

Net Amount per Month

{ManufacturerGrantPriceGross}

string

Gross Amount per Month

{ServiceReplacementVehicle}

bool

Checkbox in the column Include in Contract

{ServiceReplacementVehicleTotalAmount}

string

Net Total Amount (whole running time)

{ServiceReplacementVehiclePrice}

string

Net Amount per Month

{ServiceReplacementVehiclePriceGross}

string

Gross Amount per Month

{CostPerKm}

string

Net Amount per Month

{RefundPerKm}

string

Net Amount per Month

{CostPerKmGross}

string

Gross Amount per Month

{RefundPerKmGross}

string

Gross Amount per Month

{NetTotalAmount}

string

Sum of Net Total Amounts of services

"CostPerKm" and "RefundPerKm" are not included
"ManufacturerGrantTotalAmount" is deducted from the totals

{NetTotalAmountPerMonth}

string

Sum of Net Total Amounts per month

{GrossTotalAmountPerMonth}

string

Sum of Gross Total Amounts per month

Other properties

{Lead}

To get to any of the following values, for example

Lead.Title to use Lead's title

Vaue	Description
Title	Lead title
Make	Vehicle’s Make
SalesPersonName	Sales Person’s code
SalesPersonEmail	Sales Person’s Name (First name and Last name)
NextActivityDate	Lead’s next activity date
CreateDate	Lead’s creation date
LastUpdateDate	Lead’s update date
NextActivityTime	Lead’s next activity time
CreateTime	Lead’s creation time
LastUpdateTime	Lead’s update time
LeadImage	Photo of Vehicle
VehicleVIN	Vehicle’s VIN
LightHouseInquiryBaseUrl	LightHouse Inquiry base URL
InquiryCodeMD5	OD Inquiry code MD5-encrypted

Vehicle

{VehicleManufacturer}

string

The Make of the vehicle

{VehicleModel}

string

The Model of the vehicle

{VehicleFamily}

string

The Family of the vehicle

{VehiclePowerPS}

string

The amount of Power PS

{VehiclePowerKW}

string

The amount of Power KW

{VehicleKbaKey}

string

The vehicle's KBA key.
This the HSN and TSN values separated by a '/'. (HSN/TSN)

Sales Offer

{LastOfferDocNumber}

string

The document entry of the last created sales offer (if exists)

Data Privacy

{DataPrivacy}

Header

To get to any of the following values, you use the header property (in this case the 'DataPrivacy') followed by any of the values bellow, separated by fullstop.

For example: To use the data privacy phone channel state:

DataPrivacy.PhoneChannelStateto

Vaue	Type	Description
{PhoneChannelState}	bool	Contact by Phone is allowed
{PostChannelState}	bool	Contact by Mail is allowed
{EmailChannelState}	bool	Contact by E-Mail is allowed
{SMSChannelState}	bool	Contact by SMS is allowed

Lines

To get to any of the following values, you use the line's header property (in this case the 'DataPrivacyLines') followed by any of the values bellow, separated by fullstop.

For example: To use the data privacy make description:

DataPrivacy.DataPrivacyLines.MakeDescription

Data Privacy Lines

{DataPrivacyLines}

Value	Type	Description
{MakeDescription}	string	The name of the Manufacturer in One Dealer
{PhoneChannelState}	bool	Contact by Phone is allowed
{PostChannelState}	bool	Contact by Mail is allowed
{EmailChannelState}	bool	Contact by E-Mail is allowed
{SMSChannelState}	bool	Contact by SMS is allowed

To get to any of the following values, you use the line's header property (in this case the 'DealerDataPrivacyLines') followed by any of the values bellow, separated by fullstop.

For example: To use the dealer data privacy phone channel:

DataPrivacy.DealerDataPrivacyLines.PhoneChannelState

DealerDataPrivacyLines

{DealerDataPrivacyLines}

Value	Type	Description
{PhoneChannelState}	bool	Contact by Phone is allowed
{PostChannelState}	bool	Contact by Mail is allowed
{EmailChannelState}	bool	Contact by E-Mail is allowed
{SMSChannelState}	boll	Contact by SMS is allowed

Related tab section

A new section was created at the Related tab which stores the related fullservice contract document that is created or updated. By clicking on the title, if the "Print Status" is "Failed" then the system will try to print the document again and then load it, otherwise the document is just loaded.

Regarding the contract statuses, there are 3 statuses:

Empty: Only when the contract offer is created or updated
Accepted: When the contract offer is accepted via the necessary transition
Declined: When the contract offer is declined via the necessary transition

Fullservice Contract offer restrictions

1 Fullservice Contract offer for each VOI
1. There is no historic data for created offers of the same VOI, similar to the Sales Offer where the user can view and select past offers
The "Create Order" transition should not be available, if a Fullservice Contract offer is of status "Empty". The user have to accept or decline the Fullservice Contract offer first in order to proceed with a Sales Order
A Fullservice Contract Document has to be created in order to accept it or decline it.

2 new validations were created which can be found here (among other information regarding the workflow setup of the Fullservice Contract process).

Activity Type Group

A new UI Group Code was created:

FSC (Fullservice Contract Offer - OD0007764)

This code can be used at the @IDMS_WF_ACTTYPE.U_IDMS_UI_GroupCode field.

This code is used to group activities at the Calendar

Extra Vehicle Card Page fields

2 new fields were added at the vehicle card page, for AVAG only:

Manufacturer Key No.: linked to @XIS_CARS.U_XIS_KBAKey
Type Key No.: linked to @XIS_CARS.U_XIS_TypeKey

Related Issues

AVGA-99 - Getting issue details... STATUS

AVGA-695 - Getting issue details... STATUS

Page tree

Entity

Setup

Process

Transition required view sections

Header

Services

AVS portal setup

TecAlliance interface setup

Printing

Setup

Fullservice Contract Document printout fields

Related tab section

Fullservice Contract offer restrictions

Activity Type Group

Extra Vehicle Card Page fields

Related Issues

0 Comments