Overview for Implementing Custom Logic in SAP Marketing Cloud

• What is Custom Logic?
• An introduction in ABAP for Key Users 
• How to Implement Custom Logic
• Which Enhancements are Available to Implement in SAP Marketing Cloud?
• Implementation Examples
• Conclusion

What is Custom Logic?

Custom logic is logic that you create to enhance SAP standard delivery implementations. To accommodate customers requirements, SAP provides predefined points to extend the solutions. This enhancement implementation is also known as Business Add-Ins (BAdI).

In SAP Marketing Cloud, it is possible to extend the logic of the following business contexts:

In general, this is the process to implement custom logic:

SAP Documentation: Creating Custom Logic:

• Create your own enhancement implementations by using ABAP for Key Users.
• Publish enhancement implementations to your test system.
• Edit enhancement implementations or delete enhancement implementations that have already been published.
• Export custom logic implementation as software collections to the production system.

Creating custom logic is one of the options available to extend and enhance the SAP Marketing Cloud standard delivery. You can find more information in our Extensibility Guide

An introduction in ABAP for Key Users

ABAP for Key Users is a subset of the ABAP programming language. You can use this ABAP variant to implement business logic extensions using a web-based editor provided in SAP Marketing Cloud.

You can find more information on how to develop using ABAP for Key Users in our SAP Documentation: Introduction to ABAP for Key Users. Note: restricted ABAP syntax exists. For example, any database operation except selects from released views, tweaking new tasks, dynamic programming, obsolete ABAP statements, and code generation. Additionally, only whitelisted (released) APIs can be used.

SAP Marketing Cloud provides the following classes that can be used in custom logic:

ABAP Class Name	Description
CL_CUAN_CE_IC_QUERY	Search for Interaction Contact
CL_CUAN_CE_IA_HELPER	Interaction Helper
CL_CUAN_CE_IC_HELPER	Interaction Contact Helper
CL_CUAN_CE_MKT_ATTR_CAT_HELPER	Helper Class for Marketing Attributes Categories
CL_CUAN_CE_MKT_PERM_HELPER	Helper Class for Marketing Permission
CL_CUAN_COMMON_HELPER	Common Helper
CL_CUAN_INTERACTION_HELPER	Helper Methods for Interactions
CL_CUAN_INTEREST_HELPER	Interest Helper
CL_CUAN_LOC_HELPER	Helper Class for Marketing Location
CL_CUAN_MKT_EXEC_HELPER	Marketing Execution: Helper Class
CL_CUAN_PRODUCT_HELPER	Helper Class for Product
CL_ABAP_CONTEXT_INFO	Helper Class for System Info
CL_CUAN_INTERACT_CNTCT_HELPER	Helper Class for Get Additional Contact Fields
CL_CUAN_CAMPAIGN_HELPER_API	Helper Class for Campaign Data

Example 1: Use case implementation using CL_CUAN_CE_IC_QUERY class to search for an existing interaction contact.

The ABAP class returns the matching interaction contact.

DATA:
   lt_contact 	TYPE cuan_t_qr_ce_ic_root_ext,
   ls_query 	TYPE cuan_s_q_ce_ic_root_ext,
   lt_query 	TYPE cuan_t_q_ce_ic_root_ext.
* Create Query internal table to search for existing contacts
   CLEAR ls_query.
   ls_query-name_last = 'Doe'. 		"last name
   ls_query-name_first = 'John'. 	"first name
*  ls_query-name_text = . 			"full name
*  ls_query-country = . 			"country code
*  ls_query-country_ft = . 			"country free text
*  ls_query-region = . 				"region code
*  ls_query-region_ft = . 			"region free text
*  ls_query-postcode1 = . 			"postal code
*  ls_query-city1 = . 				"city
*  ls_query-street = . 				"street
*  ls_query-house_num1 = . 			"house number
*  ls_query-title = . 				"title code
*  ls_query-title_ft = . 			"title free text
*  ls_query-search_text = 			"search text
   APPEND ls_query TO lt_query.
* search for interaction contacts
  cl_cuan_ce_ic_query=>search(
	EXPORTING
		query = lt_query " Interaction Contact Query
	IMPORTING
		contact = lt_contact " Interaction Contact Root Result
  ).

Example 2: How to use SY-DATUM?

For ABAP developers, it is common to use SYST structure (sy-datum, sy-uzeit, sy-uname and others). As you can only use whitelisted APIs, you cannot use SYST in ABAP for Key user. Instead, you call the appropriate method of the class CL_ABAP_CONTEXT_INFO.

Example 3: You can select data from standard Core Data Services (CDS) views like I_Mkt_Initiative (campaign data), I_Mkt_Interaction (interactions), I_Mkt_Contact (contacts) and others.

How to Implement Custom Logic

In SAP Marketing Cloud, you access the Custom Fields and Logic app to implement custom logic.

Create an enhancement implementation by choosing a business context and BAdI. After, add an implementation description and ID and the Web-Development Editor will be enabled for ABAP custom logic implementation.

In the Editor, there are code examples to help you implement your custom code as well as detailed BAdI documentation.

Custom Logic Tracing

SAP Marketing Cloud enables you to trace BAdI implementations after publishing by the Custom Logic Tracing app. You can trace the values of the input, the actions, as well as check the execution processing time of your custom logic. You can also see which exceptions are raised and where they occur.

It is a powerful troubleshooting app to find implementation issues. It can also help you to identify performance tuning points in your custom code.

Which Enhancements are Available to Implement in SAP Marketing Cloud?

SAP Marketing Cloud offers several points to enhance the standard solution. You can find a list of available BAdIs in SAP Help.

Digital Account

Customize the access token request for digital account services.

Export Definition

For campaigns using Export Files Definition, you can implement custom logic to modify files structure, add columns, hide columns by checking user authorization, filter the list of File Export Definitions in campaigns, and to modify the header, attributes or target group members during file exportation.

Campaign

You can adapt and enhance campaign execution procedure based on your requirements, update attributes, change hyperlinks or filter campaigns during replication to SAP Cloud for Customer.

Open Channel

Enhancements to implement open channel for Custom Action during Campaign Executions. Find more information in Open Channel documentation.

Campaign Performance

Enhance the data checks during import of campaigns performance data.

Interaction

You can modify interaction data before import or adapt interaction data displayed in the interaction history list (Contacts and Profiles app in SAP Marketing Cloud, Interaction tab).

Contact and Corporate Account

You can modify interaction contacts or golden record when importing a contact, modify a contact when importing an interaction, or modify finding-matching logic enhancing the contact merge process.

Landing Page

You can change the data on the landing page files before publishing them during automated landing page publication, create custom logic to determine which contacts should be updated during the landing page input data and also prefill data in the landing page with data that SAP Marketing has already collected about your contacts.

Marketing Area

You can allow additional marketing areas for target groups or switch to a different marketing area during the Campaign Execution.

You can find more information regarding Marketing Area custom logic in the Help SAP documentation.

Marketing Permission

Implement your own logic to handle marketing permissions, newsletter subscriptions and suppression rules.

Marketing Plan

Enhancements to check and update attributes for marketing plan before saving it.

Marketing Program

Enhancements to check and update attributes for marketing program before saving it.

Recommendations

Implement custom logic to modify recommendations parameters before the Recommendation Scenario is calculated, and also to modify the impressions of (mass) recommendations.

Implementation Examples

In this section, you will find some BAdI implementation examples to handle different customer requirements.

Use-Case example 1: Customer requirement: to add new validation status to a specific ID_ORIGIN for a contact by using the BAdI CUAN_UPDATE_IC_ROOT.

******************************************************
* Sample logic setting the IC ROOT validation status *
******************************************************
*  c_anonymous         =  '  '
*  c_self_identified   =  '10'
*  c_qualified         =  '20'
*  c_business_partner  =  '30'
    LOOP AT lt_ia_facet REFERENCE INTO lr_ia_facet.
      CASE lr_ia_facet->id_origin.
        WHEN cl_cuan_ce_ic_helper=>gc_crm_bupa           OR  "SAP CRM Business Partner
             cl_cuan_ce_ic_helper=>gc_erp_bupa           OR  "SAP ERP Business Partner
             cl_cuan_ce_ic_helper=>gc_erp_contact        OR  "SAP ERP Contact
             cl_cuan_ce_ic_helper=>gc_erp_customer       OR  "SAP ERP Customer
             if_cuan_ce_c=>co_origin_sap_erp_company     OR  "SAP ERP Company
             if_cuan_ce_c=>co_origin_sap_c4c_indiv_cust.     "SAP C4C Individual Customer
                 es_ic_new-validation_status = c_business_partner.
          EXIT.
     ENDLOOP.

Use-Case example 2: Customer requirement: to define an Interaction, use the same Marketing Area from a Contact assigned to the interaction during Import Interaction by using the BAdI CUAN_IA_REVISE_FOR_IMPORT.

DATA: lv_marketing_area type c length 40.

IF interaction_data-mkt_area_id is initial 
OR interaction_data-mkt_area_id EQ 'GLOBAL'.
SELECT SINGLE InteractionContactMktgArea FROM I_MKT_IntactnCntctMktgArea
WHERE InteractionContactOrigin EQ @interaction_data-id_origin
AND InteractionContactId EQ @interaction_data-id
AND InteractionContactUUID EQ @interaction_data-contact_key
INTO @lv_marketing_area.
*   Set Marketing Area into Interaction
interaction_data-mkt_area_id = lv_marketing_area.
ENDIF.

Use-Case example 3: Customer requirement: to add custom attributes to the Open Channel Campaign when sending data to the external system by using the BAdI CUAN_CPG_OPN_CHNL_PARAMETER.

  DATA: v_campaign_id        TYPE cuan_initiative_id,
        s_header_Attributes  LIKE LINE OF header_attibutes,
        s_campaign_root      TYPE cuan_s_campaign_root_api.
    package_size = 100. " change the number of target group members processed in one package and transferred in the odata payload
    CHECK_PERMISSION = abap_false.
    read table HEADER_ATTRIBUTES assigning FIELD-SYMBOL(<fs_head>) WITH KEY param_name = 'CAMPAIGN'.
    if sy-subrc eq 0.
       v_campaign_id = <fs_head>-param_value.
    endif.
   s_campaign_root = cl_cuan_campaign_helper_api=>campaign_root_read( EXPORTING iv_id = v_campaign_id ).
    clear s_header_attributes.
    s_header_attributes-param_name = 'Z_NEW_FIELD'.
    s_header_attributes-param_value = s_campaign_root_api-yy1_new_field.
    append s_header_attributes to HEADER_ATTRIBUTES.
    endif.

Conclusion

This article introduced you to an overview for implementing custom logic in SAP Marketing Cloud. Now, you know what to consider to extend the standard solution, the steps to start your implementation code, and which options are available for enhancement.

To find out more about extensibility, go to: Extensibility Overview for SAP Marketing Cloud