Book Image

Implementing Order to Cash Process in SAP

By : Chandrakant Agarwal
Book Image

Implementing Order to Cash Process in SAP

By: Chandrakant Agarwal

Overview of this book

Using different SAP systems in an integrated way to gain maximum benefits while running your business is made possible by this book, which covers how to effectively implement SAP Order to Cash Process with SAP Customer Relationship Management (CRM), SAP Advanced Planning and Optimization (APO), SAP Transportation Management System (TMS), SAP Logistics Execution System (LES), and SAP Enterprise Central Component (ECC). You’ll understand the integration of different systems and how to optimize the complete Order to Cash Process with mySAP Business Suite. With the help of this book, you'll learn to implement mySAP Business Suite and understand the shortcomings in your existing SAP ECC environment. As you advance through the chapters, you'll get to grips with master data attributes in different SAP environments and then shift focus to the Order to Cash cycle, including order management in SAP CRM, order fulfillment in SAP APO, transportation planning in SAP TMS, logistics execution in SAP LES, and billing in SAP ECC. By the end of this SAP book, you'll have gained a thorough understanding of how different SAP systems work together with the Order to Cash process.
Table of Contents (15 chapters)

Vendors

Vendors are created in ECC and can be loaded to CRM based on your business requirements. Vendors are an integral part of the order to cash transaction when it comes to third-party sales orders. When products are not available in the organization's warehouse, then the sourcing is executed via a third-party vendor. In typical CRM sales order scenarios, a customer service representative might need vendor information if it is a third-party sales order and therefore it becomes imperative to determine the correct vendor on the CRM sales order. For vendor determination, you need to load vendors into the CRM system. In CRM, these vendors are created as a business partner in the BBP000- Vendor role when downloaded from ECC.

Downloading vendors

Downloading vendors from ECC to CRM requires some pre-requisite steps, which are stated as follows.

CRM settings

The following steps are performed in CRM settings:

  1. Activate the VEND_MWX_CREATE_MAIN_BDOC function. In transaction SM31, the CRMC_BUT_CALL_FU table for the business partner outbound of business partner objects and the VEND_MWX_CREATE_MAIN_BDOC function must be active.
  2. Activate the VEND_MAIN and VENDOR_MAIN adaptor objects. In transaction R3AC1, the VEND_MAIN and VENDOR_MAIN adapter objects must be active. A filter for each role of role category vendor must be set for the VEND_MAIN object.
  3. Create a subscription for vendors in SMOEAC. In transaction SMOEAC (admin console), there will be a subscription for the All Vendors publication to the ECC system (site). For example, you can specify All Vendors (MESG) as the subscription's name:
    Figure 2.37 – Vendor subscription in SMOEAC

    Figure 2.37 – Vendor subscription in SMOEAC

  4. Creation of Business Partner Grouping for Vendors: In this step the business partner grouping for vendors is created by activating the external grouping and assigning the Number range to the grouping. The Number range should be same as the ECC vendor number range.

    Figure 2.38 shows the activation of external grouping and the Number range getting assigned to grouping:

Figure 2.38 – Vendor business partner grouping

Figure 2.38 – Vendor business partner grouping

SAP ECC settings

Like the settings and the steps executed in SAP CRM to set up vendors, you need to execute the settings in the SAP ECC system. These are as follows:

  1. Activate PI_BP_PROXY_BAPI_VENDOR: Within transaction SM31, the COM_BUPA_CALL_FU table for R/3 object inbound processing (time R3OBI) of vendor records (object VEND), the PI_BP_PROXY_BAPI_VENDOR function must be active, and the PI_BP_PROXY_BAPI_CUST_VEND function must not be active.
  2. Settings in the CRMSUBTAB table: In transaction SM31, the CRMSUBTAB table for user CRM, the COM_VEND_MAIN_INBOUND function should be active for the VEND_MAIN object of the BUPA class for upload. The PI_BP_VENDOR_MAIN_EXTRACT function should be active for the VENDOR_MAIN object of the VEND class for download.
  3. Settings in the PIDV table: In the PIDV transaction, maintain the mapping between the CRM role categories for vendors (usually role category BBP000) and the corresponding ECC account group as shown in Figure 2.39 and Figure 2.40.

    The next screenshot shows the mapping of the account group to the business partner role category from R/3 to CRM, that is, the data flow from SAP ECC to SAP CRM:

Figure 2.39 – Assignment of the account group to the business partner role category

Figure 2.39 – Assignment of the account group to the business partner role category

The next screenshot shows the mapping of the business partner role category to the account group from CRM to R/3, that is, the data flow from SAP CRM to SAP ECC:

Figure 2.40 – Assignment of the business partner role category to the account group

Figure 2.40 – Assignment of the business partner role category to the account group

By default, Business Documents (BDOCS) of the VEND_MAIN type are sent in the SAP CRM system for all CRM business partners as soon as you activate the distribution function in the CRM_BUT_CALL_FU table for VEND_MWX_CREATE_MAIN_BDOC. This is a mandatory step to load the vendors in CRM.

Vendor download in CRM – R3AS

After all the previous activities, vendors are downloaded using the R3AS transaction in CRM:

Figure 2.41 – Vendor initial load via R3AS

Figure 2.41 – Vendor initial load via R3AS

Now that we have covered the concept of the vendor master and understood the exact settings required to download the vendor from SAP ECC to SAP CRM, our next topic is plant settings and the concept of how to utilize a plant as a business partner in SAP CRM.