Leasing 

Purpose

As a lessor, you can use this integration scenario to order or commission leased objects from a dealer or manufacturer in accordance with the requirements of the lessee. According to the underlying lease quotation, you can create any number of purchase orders and order different materials or objects from various dealers or manufacturers. The purchase orders are created in accordance with agreements made with the business partners in question.

You can also verify invoices that you receive from a dealer or manufacturer and compare them with the lease quotation and created purchase order. If the information matches, the content of the invoice is transferred to the financing contract. The dealer or manufacturer is paid independently of the start of the lease.

The following business partners communicate with each other in the process:

●      E-selling system: SAP CRM

●      E-procurement system: SAP SRM

Prerequisites

The Leasing integration scenario is located in the Integration Repository in the SAP BBPCRM software component in namespace http://sap.com/xi/CRM/Global. You find the interface objects and mapping objects relevant for the integration scenario in the Integration Repository in the SAP BBPCRM software component in the namespace http://sap.com/xi/CRM and http://sap.com/xi/CRM/Global.

In the SRM system, you have activated the LAM scenario for leasing.

To do this, the CRM system and SRM system must use the same back-end system.

You need to make the following settings in Customizing:

●      Set initial status

If you want to use the automatic ordering system, you must set the initial status in object type LQ0 in transaction bs12.

You cannot set the initial status manually from the lease quotation.

●      Assign initial status

In Customizing for Customer Relationship Management → Transactions → Basic Settings → Define Item Categories, you must assign object type LQ0 to the item categories (for example, item category OBJA).

●      Activate XIF adapter

Customizing for CRM → CRM Middleware and Related Components → Exchanging Data with External Components → XIF Adapter Setup → Outbound Direction

●      Configure status management for XI adapter

Customizing for CRM → Financial Services → Basic Functions → Connection of External Systems → Asynchronous → Configure Status Management for XI Adapter

●      Replicate data

The following data must be distributed:

○       Vendors: The business partner data must be replicated from the CRM system to the back-end system and from there to the SRM system. For more information, see Distribution of Business Partner Data.

○       Product categories: Replication from the back-end system to the CRM system and from the back-end system to the SRM system.

Replication is not necessary for product data.

●      Business Add-Ins (BAdIs)

Customizing for CRM → Financial Services → Basic Functions → Connection of External Systems → Asynchronous → Connection to Purchasing

You can configure default account assignment, which is transferred by the system when you create a purchase order. To do so, make the following settings in Customizing for CRM:

Financial Services → Leasing → Incoming Invoice Verification → Assign Accounts to Account Assignment Groups.

Process Flow

...

       1.      Send Purchase Request Request

When the lease quotation has reached a certain status, the CRM system sends a purchase request to the purchasing system (mySAP SRM). You define in Customizing which quotation status (for example CTF and/or Released) triggers the purchase request.

You can also trigger the purchase request manually. You then determine when the ordering process is to be triggered by setting the status for the object item in the lease quotation.

The quotation item is assigned the status Requirement Requested.

Interface information

Message interface	PurchaseRequestRequest_Out (outbound, asynchronous)
Message types	Output: PurchaseRequestRequest
Fault message type	StandardMessageFault

 

       2.      Receive Purchase Request Request

The SRM system receives the purchase request and creates a purchase order. The system uses the purchase request to generate a shopping cart, from which it then creates one or more purchase orders.

Interface information

Message interface	PurchaseRequestRequest_In (inbound, asynchronous)
Message types	Output: PurchaseRequestRequest

 

       3.      Send Purchase Request Confirmation

When you save the purchase request (purchase order), the SRM system sends the message PurchaseRequestConfirmation to the CRM system as a confirmation asynchronously via the XI adapter.

As soon as the SRM system has saved the purchase order, it sends a confirmation to the CRM system that the purchase order has been created successfully.

Interface information

Message interface	PurchaseRequestConfirmation_Out (outbound, asynchronous)
Message types	PurchaseRequestConfirmation

 

       4.      Receive Purchase Request Confirmation

The CRM system receives the first confirmation. The quotation item is assigned the status Requirement Confirmed. As soon as the purchase order has gone through an approval process in the SRM system, the SRM system sends the message PurchaseRequestConfirmation a second time. On receipt of this message, the CRM system registers the PO number as a follow-on document in the document flow at header level in the lease quotation.

The quotation item is assigned the status Requirement Ordered.

Interface information

Message interface	PurchaseRequestConfirmation_In (inbound, asynchronous)
Message types	PurchaseRequestConfirmation
Fault message type	StandardMessageFault

 

       5.      Send Supplier Invoice Information

Invoice verification and invoice entry are performed in the SRM system.

○       Invoice entry with reference to a purchase order: Information is automatically transferred from the purchase order and written to the invoice. The quotation number and assignment number (GAID) are transferred.

○       Invoice entry without reference to a purchase order: The system creates only one invoice. For this, it requires a reference number (number of the lease quotation item), which must be entered manually. The reference number can be entered only using the input help.

As soon as the invoice has been posted, the message SupplierInvoiceInformation is sent to the CRM system. Here, the complete invoice is sent to the CRM system in the message.

Interface information

Message interface	SupplierInvoiceInformation_Out (outbound, asynchronous)
Message types	SupplierInvoiceInformation

 

       6.      Receive Supplier Invoice Information

The CRM system receives the invoice information. On receipt of the invoice, invoice information is stored in the lease quotation.

In the CRM system, the system makes the following changes in the quotation:

At header level, the invoice number is linked to the quotation number; at item level, the quotation item is linked with the invoice item. This is registered in the document flow as a follow-on document.

Quantities and the value of the invoice item are stored in the document flow of the object item.

The quotation item is assigned the status Supplier Invoice Posted Externally.

Interface information

Message interface	SupplierInvoiceInformation_In (inbound, asynchronous)
Message types	SupplierInvoiceInformation
Fault message type	StandardMessageFault

 

       7.      Send Supplier Invoice Settlement Release Request

On inception, the CRM system sends the message SupplierInvoiceSettlementReleaseRequestto the SRM system. This message triggers the release of the invoices used for contract creation.

Interface information

 

Message interface	SupplierInvoiceSettlementReleaseRequest_Out (outbound, asynchronous)
Message types	SupplierInvoiceInformation
Fault message type	StandardMessageFault

 

       8.      Receive Supplier Invoice Settlement Release Request

On receipt of the message InvoiceSettlementReleaseRequest, the invoice is released in the SRM system, if it was not already released. The invoice is therefore assigned the status Released and is posted in the connected FI system.

Interface information

Message interface	SupplierInvoiceSettlementReleaseRequest_In (inbound, asynchronous)
Message types	SupplierInvoiceInformation

 

       9.      Send Supplier Invoice Cancellation Execution Request

This interface is used if cancellations are made in the quotation or contract in the CRM system.

○       Cancellation of quotation: In the SRM system, the requirement is withdrawn and any invoices that exist are deleted or cancelled.

○       Cancellation of the certificate of acceptance:Invoices can be deleted/cancelled.

The invoices for the items to be cancelled are displayed on the screen. You can set indicators to determine whether the invoices are to be cancelled.

Purchase orders are not cancelled.

○       Cancellation of the contract: If a contract item is cancelled, the associated invoices are also cancelled. Purchase orders are not cancelled.

Interface information

Message interface	SupplierInvoiceCancellationExecutionRequest_Out (outbound, asynchronous)
Message types	SupplierInvoiceCancellationExecutionRequest
Fault message type	StandardMessageFault

 

   10.      Receive Supplier Invoice Cancellation Execution Request

On receipt of this message, the SRM system cancels or deletes the invoice.

If the invoice has already been posted in FI/CO, the SRM system cancels the invoice and creates a credit memo.

If the invoice has not been posted, the invoice is deleted (status: Deleted).

Interface information

 

Message interface	SupplierInvoiceCancellationExecutionRequest_In (inbound, asynchronous)
Message types	SupplierInvoiceCancellationExecutionRequest

 

   11.      Send Invoice Leasing Update Notification

On inception, the new contract number is sent to the SRM system. The contract number indicates the reference to the invoice item. The assignment number (GAID) is also sent and updated.

Only the leasing-specific fields of an invoice are updated. The other data can no longer be changed.

 

Interface information

Message interface	InvoiceLeasingUpdateNotification_Out (outbound, asynchronous)
Message types	InvoiceLeasingUpdateNotification
Fault message type	StandardMessageFault

 

   12.      Receive Invoice Leasing Update Notification

The SRM system updates the contract number and the assignment number (GAID).

Updating is only possible as long as the invoice has not been released. You cannot change an invoice once it has been released.

Interface information

Message interface	InvoiceLeasingUpdateNotification_In (inbound, asynchronous)
Message types	InvoiceLeasingUpdateNotification