Show TOC

 View Grouping: Multichannel Foundation Information

 

This view grouping provides the foundation for obtaining sales transactions data originating from different channels, including retail stores, the Web shop, and the interaction center (IC). The information is used for various purposes, such as segmentation, target group creation, and to make point-of-sale (POS) transactions from retail stores available for display in all channels.

Note Note

POS transaction data is only identified when customers use a loyalty membership card at the time of purchase. The card makes it possible to identify the customer.

End of the note.

Structure

Report Query Views

The following query views are included in this view grouping:

  • Multichannel sales items (CRMBpSlsItem)

    Provides multichannel sales items from sales orders in SAP ERP and SAP CRM, and from POS transactions. For each item, the amounts (such as subtotal and total) are provided at both the item and the transaction level. This view can be used to obtain sales orders that belong to specific business partners.

  • Business partner information (CRM_BUSINESS_PARTNER_INFO)

    Provides general information for SAP CRM business partners, such as the customer name and address, loyalty card details, and loyalty program membership data. This view combines information from the CRMBusinessPartnerAddress and CRMLoyaltyCardMembership views to expose data necessary to support the IC, and to use for customer segmentation.

  • POS transaction items and loyalty (CRMPosItmLoy)

    Provides information for POS sales items and corresponding loyalty membership points information for specific dates, stores, and transaction index. For each item, the amounts (such as subtotal and total) are provided at both the item and the transaction level.

  • POS transaction items (CRMPosItmSls)

    Provides information for POS sales items for specific dates, stores, and transaction index.

  • POS transaction information from business partner data (CRMPosLoySls)

    Provides POS transaction data based on the SAP ERP customer ID. While the view does not process or return loyalty membership data, loyalty membership information can be used to retrieve the SAP ERP customer ID, which in turn is used by the query view.

  • Multichannel sales repository with customer information (MULTICHANNEL_BUSINESS_PARTNER_SALES_ITEM)

    Provides all sales orders for which there is identifying business partner information. This makes it possible to obtain business partner information for segmentation purposes.

Reuse Views

The report query views are supported by the following reuse views:

  • Business type (BusinessType)

    Obtains data for the business type (categorization of POS transactions, such as sales transaction), as defined in SAP Customer Activity Repository Customizing.

  • Business partner address (CRMBusinessPartnerAddress)

    Uses business partner information obtained from SAP CRM to retrieve the corresponding SAP ERP customer number. The view then adds the business partner information, including city, postal code, and region (state, province, country). Note that only standard addresses are used, such as shipping and billing addresses.

  • Loyalty card and membership information for business partners (CRMLoyaltyCardMembership)

    Obtains a list of all loyalty cards that exist in SAP CRM, along with selected information related to each card, such as the card number and the ID of the business partner to which it belongs. The view then adds membership information, such as the membership ID and the loyalty tier level.

  • Data Status (DataStatus)

    Obtains the status of the quality of the POS transaction data, such as whether a master data check error is present.

  • Material (Material)

    Obtains master data related to the material from SAP ERP for Retail.

  • POS log header (POSLogHeader)

    Obtains transactional data from the transaction log header from the transaction log (TLOG).

  • POS log loyalty (POSLogLoyalty)

    Obtains the loyalty information on transaction level or item level from the TLOG.

  • POS segments classification (POSSegmentsClassification)

    Obtains data from the TLOG, providing the business classification of the categories and subcategories available for a POS transaction segment.

  • Sales document order channel (SalesDocumentOrderChannel)

    Obtains the origin of the sales document, and maps the sales order, document type, and distribution channel attributes of the sales order to an order channel as defined in Customizing in SAP Customer Activity Repository.

  • Sales order item (SalesOrderItem)

    Obtains the transactional data based the sales order item from SAP ERP, and information about the sold-to party.

There are reuse views that appear in most of the report query views for this view grouping. These reuse views are represented in the graphic as the Common Views, and they include the following:

  • CRM business partner (CRMBusinessPartner)

    Obtains the SAP CRM business partners, along with the mapping of each business partner to its corresponding SAP ERP customer number (if any). It exposes the data required to support SAP CRM processes (such as customer segmentation and the interaction center) and customer identification performed by SAP Customer Activity Repository.

  • Order channel (OrderChannel)

    Obtains Customizing data related to the order channel from SAP Customer Activity Repository.

  • Plant (Plant)

    Obtains master data related to the plant from SAP ERP for Retail.

  • POS Log Item Analytic (POSLogItemAnalytic)

    This view obtains the transaction item information from SAP Customer Activity Repository.

Note Note

If the information retrieved from the source system is called something other than what it is in the target system, the field name reflects the naming convention of the target system. For example, the information identified as Material in SAP ERP is displayed as Product in the IC in SAP CRM

End of the note.
Business Objects

These views are built on the following business objects:

  • POS transaction

  • Sales order

  • Business partner

  • Loyalty card

Measures and Attributes

Some important measures and attributes are as follows:

  • CRMPosItmSls

    This query view provides information about POS transactions at the item level, including calculated measures such as the subtotal, total, discounts, and taxes. These calculated measures are based on POS values such as sales amounts, included and excluded taxes, distributed and item discounts, and so on.

  • CRMPosLoySls

    This query view provides information about business partners, sales items, and related loyalty information. The loyalty points data used in the calculated measures originate from the POS transaction log

Filters

Several views use the same group of filters, but have different input parameters to extract specific data. These commonly used filters extract the following transaction data:

  • Business types that are sales or returns (BusinessType=1)

  • Valid sales and return transactions, by filtering out void and training transactions

  • Credit transactions, by filtering out debit transactions

  • POS retail line items that belong to the category “sales” (RetailItemCategory=A)

These filters are referred to throughout the rest of this document as the common filters.

The views use the following filters:

  • The multichannel sales items (CRMBpSlsItem) view uses the common filters and has the following input parameters:

    • SAP client (P_MANDT)

    • Business partner ID (P_BUSINESSPARTNER)

  • The POS transaction items and loyalty (CRMPosItmLoy) view uses the common filters and has the following input parameters:

    • SAP client (P_MANDT)

    • Retail store (P_RETAILSTOREID)

    • Posting date (P_BUSINESSDAYDATE)

    • Transaction index (P_TRANSINDEX)

  • The POS transaction items (CRMPosItmSls) view uses the common filters and has the following input parameters:

    • SAP client (P_MANDT)

    • Retail store range (P_MIN_RETAILSTOREID and P_MAX_RETAILSTOREID)

    • Posting date range (P_MIN_POSTING_DATE and P_MAX_POSTING_DATE)

    • Transaction index range (P_MIN_TRANSACTION_INDEX and P_MAX_TRANSACTION_INDEX)

  • The POS transaction information from business partner data (CRMPosLoySls) view uses the common filters and has the following input parameters:

    • SAP client (P_MANDT)

    • Number of results returned (P_MAXROWS)

    • SAP ERP customer number (P_CUSTOMERNUMBER)

  • The multichannel sales repository with customer information (MULTICHANNEL_BUSINESS_PARTNER_SALES_ITEM) view filters the following purchase data:

    • POS retail line item that belong to both the category and subcategory “sales” (RetailItemCategory=A and RetailSubcategory=A)

    • Sales documents that belong to the category “sales order” (SDDocumentCategory=C)

Used Tables and Views

The views select data from the following tables:

  • SAP_CAR./CAR/SALESDOCOC

  • SAP_CAR.DD07L

  • SAP_CAR.DD07T

  • SAP_CAR./DSMFD/ORDERC

  • SAP_CAR./DSMFD/ORDERCT

  • SAP_CAR./POSDW/ITMS

  • SAP_CAR./POSDW/ITMST

  • SAP_CRM.ADRC

  • SAP_CRM.BUT000

  • SAP_CRM.BUT021_FS

  • SAP_CRM.CRMM_BUT_CUSTNO

  • SAP_CRM.LOYD_MSH_MEMS

  • SAP_CRM.LOYD_MSH_MS_TIER

  • SAP_ECC.MAKT

  • SAP_ECC.MARA

  • SAP_ECC.T001W