trade promotion integration to condition contract

Integration GuideSAP Customer Relationship ManagementDocument Version: 1.2 – 2018-09-14

CUSTOMER

Trade Promotion Integration to Condition ContractSettlement Management

2CUSTOMER© 2018 SAP SE or an SAP affiliate company. All rights reserved.

Trade Promotion Integration to Condition Contract Settlement ManagementTypographic Conventions

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,pushbuttons labels, menu names, menu paths, and menu options.Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, table names, and key concepts of a programming language when theyare surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,names of variables and parameters, source text, and names of installation, upgrade anddatabase tools.

Example Exact user entry. These are words or characters that you enter in the system exactly asthey appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characterswith appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

Trade Promotion Integration to Condition Contract Settlement ManagementDocument History

CUSTOMER© 2018 SAP SE or an SAP affiliate company. All rights reserved. 3

Document History

NoteYou can find the most current version of this document on SAP Help Portal. We strongly recommend thatyou use the documents provided there as they are updated regularly.

Version Date Comment

1.2 2018-9-12 Added information on taxation.See chapter 3, Configuration for CCS Integration

1.1 2017-09-19 Added chapter 9, Delivered Condition Types

1.0 2016-06-09 Released for SAP Enhancement Package 4 for SAP CRM 7.0


Trade Promotion Integration to Condition Contract Settlement ManagementContents

Contents

1 Overview .................................................................................................................................. 61.1 Big Picture .............................................................................................................................................. 6

2 Business Function ....................................................................................................................8

3 Configuration for CCS Integration......................................................................................... 9

4 Accrual Pull and Sales Volume Pull ...................................................................................... 13

5 CRM Settlement Integration to Manual Settlement of CCS ............................................... 15

6 Middleware Related Information ........................................................................................... 176.1 Trade Promotion to Condition Contract Integration ......................................................................... 176.2 Funds Management to Condition Contract Integration .................................................................... 17

7 Pricing Procedure in SAP S/4HANA ..................................................................................... 18

8 Condition Contract Configuration in SAP S/4HANA .......................................................... 19

9 Delivered Condition Types ....................................................................................................23



Table of Figures

Figure 1: Component Diagram Depicting Rebate Trade Spends Integration Scenario with Condition ContractSettlement .............................................................................................................................................................................7Figure 2: Business Function Activation .............................................................................................................................. 8Figure 3: Definition of Campaign Types ............................................................................................................................. 9Figure 4: Campaign Types .................................................................................................................................................. 9Figure 5: Customizing for Condition Generation of Trade Spends ................................................................................10Figure 6: View to Maintain Condition Generation Type ...................................................................................................10Figure 7: Customizing to Assign Condition Trade Spend Combinations to Contract Types ....................................... 11Figure 8: View to Maintain Trade Spend Relation to Condition Contract Type/Condition Type................................. 11Figure 9: Customizing to Assign Condition Generation Type to Campaign Type ......................................................... 12Figure 10: View to Assign Condition Generation Type to Campaign Type .................................................................... 12Figure 11: Customizing to Maintain Job Types ................................................................................................................. 13Figure 12: View to Maintain Job Types .............................................................................................................................. 13Figure 13: Summary of New Created Job Types .............................................................................................................. 13Figure 14: Accrual Profile .................................................................................................................................................... 14Figure 15: Billing Application Configuration ...................................................................................................................... 15Figure 16: Integration to SD Billing .................................................................................................................................... 15Figure 17: Billing Type Customizing................................................................................................................................... 16Figure 18: Customization to Define Condition Contract Types ...................................................................................... 19Figure 19: View to Maintain Condition Contract Types .................................................................................................. 20Figure 20: Customizing to Assign Condition Types to Condition Type Groups ........................................................... 20Figure 21: Assign Condition Types to Condition Type Groups........................................................................................ 21Figure 22: Customizing to Maintain Condition Type Relevance for CCS ....................................................................... 21Figure 23: View to Maintain CCS Relevance for Pricing Conditions .............................................................................. 22

https://wiki.wdf.sap.corp/wiki/x/YbQxY



1 Overview

This document explains the enhancements done on the CRM Trade Promotion object with regards to integrationwith SAP S/4HANA®. Rebate agreement and the related settlement functionality shall be quarantined thendeprecated in SAP S/4HANA. Going forward the rebate agreement and subsequent settlement processing shallbe handled by condition contract and Condition Contract Settlement Management (CCS). This document providesa high-level view of the new integration approach with all the necessary steps required to enable the new process.There are no fundamental changes in the CRM architecture with regards to integration with SAP S/4HANA. Theintegration of trade spends to condition contracts is done in a non-disruptive manner by introducing a businessfunction and Customizing. For a certain period, rebates and condition contracts can co-exist until the decision ismade to move the process completely over to Condition Contract Settlement Management. This means that themove to the condition contract shall be done in a phased manner.The integration is supported from SP05 of SAP CRM 7.0 EHP4 and FPS01 of SAP S/4HANA 1610 releases.

NoteThe discount and the free goods based trade spends are not affected by the new integration and thoseareas are not described in this document.

1.1 Big Picture

A Trade Promotion created in CRM generated a rebate agreement object in ERP for certain category of tradespends. Rebate object was generated and persisted in CRM and this was replicated to ERP via middleware. WithCCS integration, there shall be no new business object created in CRM. The trade promotions that are set to beintegrated to the condition contract shall have trade spends that shall just hold a reference to the ID of the relatedcondition contract in SAP S/4HANA.The corresponding condition contract shall hold the condition record with the trade spend value and the productdimension information with all the required information. When a trade promotion is released, based on mappinglogic, an RFC is invoked on the SAP S/4HANA side to create the condition contract via middleware queue.The integration to condition contracts can be turned on via Business Function CRM_TPM_CCS_1. Thecorresponding switch CRM_TPM_CCS_1 is attached to repository objects so that by default the old behavior is notdisrupted. There are new Customizing settings to map trade spends to condition contracts. Additionally, newsettings are delivered that allow you to distinguish a trade spend mapped to a condition contract vis-à-vis arebate.Each trade spend in the trade promotion is mapped to a single condition contract. This carries over the samebehavior with the rebates agreement that each trade spend was mapped to an individual rebate agreement. Thisleads to better transactional consistency between the objects in both the systems. The trade spends with spendcombinations that are mapped to a condition contract type and condition type shall skip the rebate processingand go with the condition contract creation in SAP S/4HANA.



NoteIt shall not be possible to mix the current rebate agreement based trade spends and the conditioncontract based trade spends in the same trade promotion. The recommendation is to create newpromotion types and the corresponding condition generation types to integrate with the conditioncontracts thus providing a separation between the two objects.Also, the recommendation for claims processing is not to add trade promotions where some go to therebate agreement object and some go to the condition contract object. This shall lead to issues whilecreating CRM settlement documents.

The transaction WCOCO is used in SAP S/4HANA to view the condition contracts.The following figure provides an overview of the integration landscape.

Figure 1: Component Diagram Depicting Rebate Trade Spends Integration Scenario with Condition Contract Settlement



2 Business Function

A new business function CRM_TPM_CCS_1 and the corresponding switch CRM_TPM_CCS_1 shall be the enabler oftrade spend integration to the condition contract object. The following is a screen shot from transactionSFW_BROWSER.

Figure 2: Business Function Activation

The switch BC sets that are assigned to the switch CRM_TPM_CCS_1 contain some delivered Customizing entries.Some of the switch BC sets are templates for creating other entries.



3 Configuration for CCS Integration

Business Context

When the switch BC sets are activated, new promotion types and condition generation types appear in thesystem.Following is an example of one such promotion type:1. In Customizing for Customer Relationship Management choose Marketingà Marketing Planning and

Campaign Managementà Basic Dataà Define Types/Objectives/Tactics.

Figure 3: Definition of Campaign Types

Figure 4: Campaign Types



2. In Customizing for Customer Relationship Management choose Trade Promotion Managementà TradePromotionsà Condition Maintenanceà Define Condition Generation.

Figure 5: Customizing for Condition Generation of Trade Spends

Figure 6: View to Maintain Condition Generation Type

As can be seen in the generation type 1001 there are no trade spends mapped to Rebate BO. But thiscondition generation type is indeed mapped to condition contract types. The following figure depicts thismapping.

3. In Customizing for Customer Relationship Management choose Trade Promotion Managementà TradePromotionsà Condition Maintenanceà Condition Contract Mapping for S4 HANAà Assign Trade SpendCombination to Condition Contract Type.



Figure 7: Customizing to Assign Condition Trade Spend Combinations to Contract Types

Figure 8: View to Maintain Trade Spend Relation to Condition Contract Type/Condition Type

With this approach, it is possible to segregate trade promotions that work with rebate agreements and thosethat work with condition contract settlement.

4. In Customizing for Customer Relationship Management choose Trade Promotion Managementà TradePromotionsà Condition Maintenanceà Assign Condition Generation Types.



Figure 9: Customizing to Assign Condition Generation Type to Campaign Type

Figure 10: View to Assign Condition Generation Type to Campaign Type

In the assignment area, the decision is made to decide which sales areas need to be activated with the newpromotion type and the relevant condition generation type. Again, recommendation from SAP is to not mixthe rebate related trade spends with the condition contract relevant trade spends. Assign only theappropriate condition generation type to the promotion type. This means, do not assign condition generationtypes having rebate trade spends and condition generation types having CCS relevant mapping to the samepromotion type. This will ensure a clean cut over to the new world.

As is evident from the above screen shots, there can be rebate agreement-based trade promotions and CCSbased trade promotions co-existing in the system.

NoteTaxation is not supported in SAP CRM when using condition contracts. No taxation information flowsbetween SAP CRM and SAP S/4HANA. For example, the tax direction field and tax difference report willnot work when using condition contracts. Taxation should be handled entirely on the SAP S/4HANA side.



4 Accrual Pull and Sales Volume Pull

There are new reports for pulling the accruals and sales volumes from the condition contract to CRM. To enablethe new data pull, it is required to configure the new job types:In Customizing for Customer Relationship Management choose Basic Functionsà Batch Processing FrameworkàDefine Job Types.

Figure 11: Customizing to Maintain Job Types

Figure 12: View to Maintain Job Types

Figure 13: Summary of New Created Job Types

Reports:



· RCRM_MKTPL_TPM_EXT_CCS_ACRUALS: enables pull of accruals from the condition contract and update fundusages with financials.

· RCRM_FM_ACL_CCS_SALES_VOLUMES: enables pull of business volume base from the condition contract.· RCRM_FM_ACL_CCS_ACCRUAL_RUN: enables the calculation of accruals based on the business volume

fetched from the above report.· RCRM_FM_ACL_CCS_ACR_POSTING_FM: posts accruals to Funds Management based on the above report.

A new accrual profile S4_CC_SV is available to be assigned to expense types in the Funds Integration area of TradeManagement.

Figure 14: Accrual Profile

There could be funds plans in the system that have funds associated to rebates and others to condition contracts.This does not affect any accrual calculations. The rebate-based reports and the CCS-based reports must be run toensure that the right updates reach the fund usages. The reports do not cause a conflict between rebate basedaccrual and CCS-based accrual. The aggregation works correctly in the fund usages.



5 CRM Settlement Integration to ManualSettlement of CCS

In Customizing for Customer Relationship Management choose Billingà Configure Application.

Figure 15: Billing Application Configuration

Figure 16: Integration to SD Billing

Select the Integration to SD Billing option.The billing type used should be set up to work against manual settlement of the condition contract. This is done asfollows:In Customizing for Customer Relationship Management choose Billingà Define Billing Types.



Figure 17: Billing Type Customizing

The Integration Type as shown in the figure enables manual settlement of CCS.



6 Middleware Related Information

The CRM middleware is used to communicate between CRM and SAP S/4HANA. Here are two examples:

6.1 Trade Promotion to Condition Contract Integration

BDoc CRM_MKTPL_MKTELEM and the corresponding adapter CRM_MKTPL_R3INT hold the flow of information fromCRM to SAP S/4HANA and back.Inbound Queue TPM_CCS_(TPM ID) is triggered in the SAP S/4HANA system, which then invokes the RFCWB2_REBATES_TPM_INBOUND_RFC.Inbound Queue S4INT_CCS_(TPM_ID) is used to trigger inbound processing of acknowledgement messages inCRM. The placeholder (TPM_ID) represents the Trade Promotion ID without the 'T-'. The application log withobject CRM_TPM_CCS and sub-object TRANS_STATUS holds messages regarding transfer.

6.2 Funds Management to Condition Contract Integration

BDoc CRM_FM_CCS and the corresponding adapter CRM_FM_CCS hold the flow of information from CRM to SAPS/4HANA and back.Inbound Queue R3AU_FUND_(FUND_PLAN_ID) is triggered in the SAP S/4HANA system, which then invokes theRFC CRM_FM_CCSDATA_R3_IN.Inbound Queue R3AD_FUND_(FUND_PLAN_ID) is used to trigger inbound processing of accrual data in CRM. Theplaceholder (FUND_PLAN_ID) represents the Fund Plan ID.The application log with object CRM_FM_ACL and sub-object MONITOR hold messages regarding transfer.



7 Pricing Procedure in SAP S/4HANA

New access sequence TPCC is available in the SAP S/4HANA system to work with the condition tables holdingCCS-based rebates. Pricing condition types that are marked for CCS consumption should be assigned this newaccess sequence. Then the SD pricing procedure relevant for documents relevant for rebate processing shouldhave this new condition type assigned.Alternatively, you can use the delta accrual batch processing where the accruals are calculated outside of SDpricing for a condition contract. These condition types can be transferred to CRM via the existing conditionCustomizing download. They are treated as ‘PR’ condition types. They can also be created in Customizing forCustomer Relationship Management by choosing Basic Functionsà Pricingà Create Condition Types.



8 Condition Contract Configuration in SAPS/4HANA

1. In SAP S/4HANA, in Customizing choose WLFAà Settlement Managementà Condition ContractManagementà Condition Contract Maintenanceà Define Condition Contract Types.

Figure 18: Customization to Define Condition Contract Types

The following is a screen shot of a delivered contract type with a highlighted sales condition type group.



Figure 19: View to Maintain Condition Contract Types

The relevant condition type which maps to the trade spend is assigned to the condition type group in thefollowing configuration:

2. In Customizing, choose WLFAà Settlement Managementà Condition Contract Managementà ConditionContract Maintenanceà Condition Contract Conditionsà Salesà Assign Condition Types to Condition TypeGroups.

Figure 20: Customizing to Assign Condition Types to Condition Type Groups



Figure 21: Assign Condition Types to Condition Type Groups

The pricing condition types should be marked for condition contract consumption, as shown in the figure.3. In Customizing, choose WLFAà Settlement Managementà Condition Contract Managementà Condition

Contract Maintenanceà Condition Contract Conditionsà Salesà Specify CC-Relevance and Copy Controlfor Condition Types.

Figure 22: Customizing to Maintain Condition Type Relevance for CCS



Figure 23: View to Maintain CCS Relevance for Pricing Conditions

In the figure, pricing condition type REA3 is marked as condition contract relevant. This condition type would needto be assigned to the SD Pricing Procedure relevant for those sales orders for which accrual posting is desired.

Trade Promotion Integration to Condition Contract Settlement ManagementDelivered Condition Types


9 Delivered Condition Types

Table 1: Condition Types Used in SAP Trade Management

ConditionType

Description

Usage Corresponding TPMConditionType

ReferenceConditionType

Maintainedin Contract

PricingProcedureBilling

PricingProcedureManualSettlement

Pricing ProcedureAutomaticSettlement

PricingProcedureDeltaAccruals

REA1 RebateAccruals

Accruals Rate REA3 X X

REA2 RebateAccrualsRev

Reversal of Accrualsin Settlement

REA4 X

REA5 RebateAccrualsSettl

Accruals Adjustmentin Settlement

optional optional

RED1 RebateAccruals

Accruals Rate forUsage in DeltaAccruals Calculation

RED3 REA1 X

RED2 RebateAccrTotal

Total of ExistingAccruals for DeltaAccruals Calculation

RED4 X

RES1 Rebate Rebate Rate RES3 X X

RES2 RebatePartSettlRev

Reversal of ExistingSettlements inSettlement and for

RES4 X X


Trade Promotion Integration to Condition Contract Settlement ManagementDelivered Condition Types

ConditionType

Description

Usage Corresponding TPMConditionType

ReferenceConditionType

Maintainedin Contract

PricingProcedureBilling

PricingProcedureManualSettlement

Pricing ProcedureAutomaticSettlement

PricingProcedureDeltaAccruals

Delta AccrualsCalculation

RENT RebateNetAmount

Net Amount inManual Settlement

X

REU1 RebateUnlikelihood

Set accruals to bedone to zero(because rebatetarget achievement isunlikely and,therefore, thereshould be no accrualsfor this customer)

X optional X

REBV RebateBusinessVol.

Business Volume forSettlement

X X

RETT RebateTaxTrigger

X X (goods relatedtax, based on taxcode frombusiness volume)

RETX RebateTax

X (taxdetermination insettlement)

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP SEor an SAP affiliate company.SAP and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks ofSAP SE (or an SAP affiliate company) in Germany and othercountries. All other product and service names mentioned are thetrademarks of their respective companies. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark foradditional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

trade promotion integration to condition contract

Documents