The Loyalty Member is a copy of Business Partner with minimum information from the Business Partner tables.
NOTE: 1178046 (This note is the Loyalty installation Guide)
> The customer is already using the CRM and newly installing the Loyalty, he has to update/activate few BAdI’s in order to copy the BP from CRM to the Loyalty Member table.
> If the customer is installing the CRM and LOY for the first time, then he just needs to activate few BAdI’s, so that whenever the BP is created, Member table is also updated with member ID.
The two-box approach tells that the data must be replicated from one system to another system with standard data transfer structure. Here we transfer data from BP tables of CRM system to the Member table of Loyalty box. The member able is only used for search purpose, no updates can be made on the member table, therefore the data transfer from Member table to BP tables is not required, and hence it is not supported.
In our system, data are technically exchanged with SAP CRM System and SAP LOY System.
Here, we use the CRM Middleware for initial copy of BP’s to Member Tables as in the case of Two Box approach. The customer shall use the CRM middleware for only performing an Initial Load of BP into the LOY system.
The implementation “LOY_MEMBER_UPDATE” of the interface “IF_EX_PARTNER_UPDATE” will copy any changes to BP header data on BP save to the member table.
The implementation “LOY_MEM_ADDR_UPDATE” of the interface “IF_EX_ADDRESS_UPDATE” will copy any changes to BP address data on BP save to the member table.
The three important packages are:
- LOY_MEM_DB – Package for member tables.
- LOY_MEM_RFC – Package for the RFC Function Modules to access, create, modify the member tables.
- CRM_LOY_MEM_SYNC – Package for the Function modules, classes and BAdI implementations used for keeping the BP and the Member tables in sync.
This package holds the two important member tables which is used throughout the Loyalty member and its respective table types, structures, data elements and domains.
The two tables are: LOYD_MEM_MEMBER and LOYD_MEM_ADDR
- LOY_APPL_MODEL => Loyalty Application Model. Transaction for developing Loyalty application models
- CRM_LOYIL_MODEL => Loyalty Interaction Layer. Transaction for developing loyalty GenIL layer.
Few Important Function Groups
- LOY_MEM_RFC => This function group has all the RFC FMs related to member object.
- LOY_MEM_MEMBER_UPDATE => The FM’s of this function group are “LOY_MEM_MEMBER_UPDATE” & “LOY_MEM_MEMB_ADDR_UPDATE”. These are the FM’s which are used to actually update/modify the database tables. These FM’s are called by the whitefield framework.
- CRM_LOY_MEM_API => This function group has all the API’s needed for member and its child object address.
The member search can be objects can be found by using LOY_APPL_MODEL.
The membership is a relation between a person or organization (business partner/member) and a loyalty program. Membership covers details about the member, status, program, tier level, point account balance, preferences, etc.
A Membership page consists of the following Views.
The Membership View consists of General Details of the Membership like loyalty program, purpose of use and origin, employee responsible, start and end date, status, and point account set ID.
These details are stored in the table: LOYD_MSH_MEMS
Function Module: LOY_MSH_MEMS_UPDATE_FM (it has the membership insert, delete and update operations)
The above table is also responsible for holding the Administration Data like created by,at and changed by,at.
The Member Guid is linked with the Tables: LOYD_MEM_MEMBER, LOYD_MSH_MS_MEMB, BUT000, LOYD_MEM_MEMBER
Using the membership guid, you can get the point accounts and the point transaction details from the tables like: LOYD_PT_ACCT and LOYD_PT_TXN
For more loyalty tables, refer: http://scn.sap.com/docs/DOC-62189