Objects in Leasing 

Definition

A unique instance of a product, such as a car, computer, or motorcycle. It identifies a specific object and contains data that is only true for that exact object.

Use

●      You can use objects in all leasing-relevant processes that require a unique reference to a specific object, such as a car with its vehicle identification number (VIN), model, construction year, and mileage.

●      Objects are quantity-based. This means they always have a quantity equal to one to ensure unique assignment. Moreover, objects can be identified uniquely in all contracts, which means they can be used beyond a single contract.

●      In leasing, you use objects to map the leased object, such as the car or computer. If you also use service cards in your leases, for example fuel cards, then you create these cards, which have a unique number, as objects.

For more information about objects in SAP Customer Relationship Management (SAP CRM), see Objects.

Integration

Pricing

You can create specific conditions for objects in pricing. If you want to use a specific pricing condition for an object, you have to adjust the modify sequence to have pricing check the specific condition for the object first and use this to calculate the price. This price has priority over the price of the reference product. The condition for the reference product is used only if no specific price can be determined for the object during pricing.

SAP ERP Accounting

In the ERP application, you have to create a reference product for the object and assign it to this object. The system uses the reference product to classify the lease and to create an asset. This is imperative because the ERP application cannot process objects from the CRM application. When the system transfers data to the ERP application, it replaces the object with the corresponding reference product.

Special Feature for Vehicles: Mileage Billing

A certain mileage value may be a component of the lease, depending on the term. SAP provides corresponding condition types for this in Customizing. You can assign all terminating change processes to a certain condition function group that contains the conditions for mileage billing. Starting from a defined amount (condition type 4K01), a starting value (4K02), an end value (4K03), and the resulting amount (4K04), the system calculates an additional, mileage-specific fee (4K05). These conditions are defined in the object item and copied to the corresponding items (4K11 to 4K15) in the billing request item, which contains the fee incurred for the terminating change process. The system adds the mileage fee to the regular fee and bills it.