Integration with Procurement System

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 lease. The dealer or manufacturer is paid independently of the start of the lease.

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

  • E-selling system: SAPCRM

  • E-procurement system: SAPSRM

Prerequisites

You find the interface objects and mapping objects relevant for the integration scenario in the integration repository in the software component Start of the navigation pathSAP BBPCRM Next navigation step SAP CRM ABAP 7.0 in the namespaces http://sap.com/xi/CRM/FSEnd of the navigation path and http://sap.com/xi/CRM/FS/Global .

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

You need to make the following settings in Customizing:

  • Set initial status

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

  • Assign initial status

    In Customizing for SAP CRM under Start of the navigation pathTransactions Next navigation step Basic Settings Next navigation step Define Item CategoriesEnd of the navigation path , you must assign object type LQ0 to the item categories (for example, item category OBJA).

  • Activate XIF adapter

    Customizing for SAP CRM under Start of the navigation pathCRM Middleware and Related Components Next navigation step Exchanging Data with External Components Next navigation step XIF Adapter Setup Next navigation step Outbound DirectionEnd of the navigation path

  • Configure status management for XI adapter

    Customizing for SAP CRM under Start of the navigation pathFinancial Services Next navigation step Basic Functions Next navigation step Connection of External Systems Next navigation step Asynchronous Next navigation step Configure Status Management for XI AdapterEnd of the navigation path

  • 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.

  • Business Add-Ins (BAdIs)

    Customizing for SAP CRM Start of the navigation pathunderFinancial Services Next navigation step Basic Functions Next navigation step Connection of External Systems Next navigation step Asynchronous Next navigation step Connection to PurchasingEnd of the navigation path

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 (SAP SRM). You define in Customizing which quotation status (for example Commitment to Finance 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)

    Namespace

    http://sap.com/xi/CRM/FS/Global

    Message type

    PurchaseRequestRequest

  1. 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)

    Namespace

    http://sap.com/xi/SRM/SE/Global

    Message type

    Output: PurchaseRequestRequest

    Fault message type

    ExchangeFaultData

  2. 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.

    If the purchase order is rejected or deleted in the SRM system at a later date, the system also sends a Purchase Request Confirmation with the corresponding content (indicator for deletion).

    Interface Information

    Message interface

    PurchaseRequestConfirmation_Out (outbound, asynchronous)

    Namespace

    http://sap.com/xi/SRM/SE/Global

    Message type

    PurchaseRequestConfirmation

  3. 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)

    Namespace

    http://sap.com/xi/CRM/FS/Global

    Message type

    PurchaseRequestConfirmation

    Fault message type

    StandardMessageFault

  4. 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 (UIID) are transferred.

    • Invoice entry without reference to a purchase order: The invoice is manually created in the SRM system. When doing so, values such as units of measure (for example, PC for piece) must match the entries in the lease quotation in the CRM system otherwise the invoice cannot be processed in this system. So that the invoice in the CRM system can be assigned to the correct lease quotation, a reference number (number of the lease quotation item) is required. You can select this reference number using the search 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)

      Namespace

      http://sap.com/xi/SRM/Invoicing/Global

      Message type

      SupplierInvoiceInformation

  5. Receive Supplier Invoice Information

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

    The CRM system makes the following changes in the lease 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)

    Namespace

    http://sap.com/xi/CRM/FS/Global

    Message type

    SupplierInvoiceInformation

    Fault message type

    StandardMessageFault

  6. Send Supplier Invoice Settlement Release Request

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

    Interface Information

    Message interface

    SupplierInvoiceSettlementReleaseRequest_Out (outbound, asynchronous)

    Namespace

    http://sap.com/xi/CRM/FS/Global

    Message type

    SupplierInvoiceInformation

  7. 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)

    Namespace

    http://sap.com/xi/SRM/Invoicing/Global

    Message type

    SupplierInvoiceInformation

    Fault message type

    StandardMessageFault

  8. 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 existing invoices 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)

      Namespace

      http://sap.com/xi/CRM/FS/Global

      Message type

      SupplierInvoiceCancellationExecutionRequest

  9. 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)

    Namespace

    http://sap.com/xi/SRM/Invoicing/Global

    Message type

    SupplierInvoiceCancellationExecutionRequest

    Fault message type

    StandardMessageFault

  10. 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 (UIID) is also sent and updated.

    Interface Information

    Message interface

    InvoiceLeasingUpdateNotification_Out (outbound, asynchronous)

    Namespace

    http://sap.com/xi/CRM/FS

    Message type

    InvoiceLeasingUpdateNotification

  11. Receive Invoice Leasing Update Notification

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

    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)

    Namespace

    http://sap.com/xi/SRM/Leasing

    Message type

    InvoiceLeasingUpdateNotification

    Fault message type

    StandardMessageFault