Show TOC

Request Loyalty Membership Activity Journal as Bulk Locate this document in the navigation structure

Definition

To send a mass request from SAP POS DM to loyalty membership activity.

Technical Data

Software Component Version

RTLPOSDM 1.0

Release State

released

Technical Name

LoyaltyMembershipActivityJournalCRMBulkRequest_Out_V1

Namespace

http://sap.com/xi/RTLPOSDM/Global2

Application Component

BW-BCT-ISR-PIP

Related Web Service Definition

/POSDW/CO_LylMbrshpActJrBkReq

Category

SAP A2A

Direction

outbound

Mode

asynchronous

Idempotency

no

P2P Communication Enabled

no

Notes on Release State (Technical Data)

This operation is the successor to operation of the same name under namespace http://sap.com/xi/BICONTENT/Global2.

The change to the XML namespace allows for optional P2P communication.

Business Context

The operation sends loyalty information from SAP POS DM to SAP CRM. Loyalty information can be included at the header level or at the retail line item level of the POS transaction. Customizing settings determine how the service is filled.

Features

Initially, a transaction log (TLOG) containing loyalty information is sent to the SAP POS DM. Once data is in SAP POS DM, loyalty information within the TLOG must be sent to SAP CRM using the operation Request Loyalty Membership Activity Journal as Bulk. Loyalty points/amounts are aggregated based on the customer card number.

Different options are as follows:

  • Send loyalty amount at header level

  • Send loyalty points at header level

  • Send loyalty amount at retail line item level

  • Send loyalty points at retail line item level

Main nodes of the operation are as follows:

  • MemberParty: Contains the customer loyalty card number

  • SalesDocumentReference: Contains the transaction number, the store ID, and the loyalty amount

  • Point: Contains loyalty points

Prerequisites

The system must call Maintain Loyalty Membership Activity Journal before using the Request Loyalty Membership Activity Journal as Bulk operation. This operation is not available in SAP POS DM but is available in a system that uses the operation to create loyalty membership activity with the POS transaction details.

Integration

This operation may be optionally referenced within the following software component(s):

  • Store Connectivity

  • ESM BI CONT

  • ESM Integration

Error Handling

Forward error handling (FEH) is not available in SAP NetWeaver BW.

As a result, any message that cannot get processed within the service implementation (for example, due to a mapping error) is rejected and a corresponding fault message is raised using cl_proxy_fault=>raise.

Typical errors are as follows:

  • Customizing is missing for loyalty data transfer

  • A duplicate customer card number is found, which means no aggregation is done

  • An empty customer card number is detected

Constraints and Integrity Conditions

The operation cannot currently support inventory or summary transactions.

Notes on SAP Implementation

The Supply CRM Loyalty Interface task in SAP POS DM sends loyalty information to CRM component using the service interface. This task must be set up for the retail store that is being used.

Inside PIPE customizing:   POS Data Management   POS Inbound Processing   Integration with Other SAP Components   CRM Integration   settings determine which fields are mapped in the operation. Different options are as follows:

  • Points from TLOG header level mapped to CRM

  • Amount from TLOG header level mapped to CRM

  • Points from TLOG line item level summed up mapped to CRM

  • Amount from TLOG line item level summed up mapped to CRM

B2B And A2A Related Information

SAP NetWeaver BW and SAP CRM are the back-end components that are involved. The corresponding inbound service of this operation resides in the SAP CRM component.

Processing

LoyaltyMembershipActivityProfileCode determines if points are redeemed or awarded. The redeemed scenario is not supported for the communication between SAP POS DM to SAP CRM (offline scenario). Therefore the value is always 13 (POS ACCURAL). In the offline scenario, the 'TypeCode' under SalesDocumentReference is set to 903, which is related to POS transactions.

Asynchronous outbound operations only

POS Workbench (transaction /POSDW/MON0) can be used to send out the service interface.

Enhancements

The /POSDW/SE_LOYALTY_OUTBOUND Business Add-In (BAdI) is available for this operation under Enhancement Spot /POSDW/SPOT_SE_LOYALTY.