Trade Promotion Integration to Condition Contract Settlement Management

Transcription

1 I Integration Guide SAP Customer Relationship Management Document Version: Trade Promotion Integration to Condition Contract Settlement Management

2 Typographic Conventions Type Style Example Example EXAMPLE Example Example <Example> EXAMPLE Description 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. Emphasized words or expressions. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. 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 and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions

3 Document History Note You can find the most current version of this document on SAP Help Portal. We strongly recommend that you use the documents provided there as they are updated regularly. Version Date Comment Released for SAP Enhancement Package 4 for SAP CRM Added chapter 9, Delivered Condition Types Document History 2017 SAP SE or an SAP affiliate company. All rights reserved. 3

4 1 Overview Big Picture Business Function Configuration for CCS Integration Business Context Accrual Pull and Sales Volume Pull CRM Settlement Integration to Manual Settlement of CCS Middleware Related Information Trade Promotion to Condition Contract Integration Funds Management to Condition Contract Integration Pricing Procedure in SAP S/4HANA Condition Contract Configuration in SAP S/4HANA Delivered Condition Types SAP SE or an SAP affiliate company. All rights reserved.

5 Table of Figures Figure 1: Component Diagram Depicting Rebate Trade Spends Integration Scenario with Condition Contract Settlement...7 Figure 2: Business Function Activation... 8 Figure 3: Definition of Campaign Types... 9 Figure 4: Campaign Types... 9 Figure 5: Customizing for Condition Generation of Trade Spends...10 Figure 6: View to Maintain Condition Generation Type...10 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 Figure 9: Customizing to Assign Condition Generation Type to Campaign Type Figure 10: View to Assign Condition Generation Type to Campaign Type Figure 11: Customizing to Maintain Job Types Figure 12: View to Maintain Job Types Figure 13: Summary of New Created Job Types Figure 14: Accrual Profile Figure 15: Billing Application Configuration Figure 16: Integration to SD Billing Figure 17: Billing Type Customizing Figure 18: Customization to Define Condition Contract Types Figure 19: View to Maintain Condition Contract Types Figure 21: Customizing to Assign Condition Types to Condition Type Groups Figure 22: Assign Condition Types to Condition Type Groups Figure 23: Customizing to Maintain Condition Type Relevance for CCS Figure 24: View to Maintain CCS Relevance for Pricing Conditions SAP SE or an SAP affiliate company. All rights reserved. 5

6 1 Overview This document explains the enhancements done on the CRM Trade Promotion object with regards to integration with SAP S/4HANA. Rebate agreement and the related settlement functionality shall be quarantined then deprecated in SAP S/4HANA. Going forward the rebate agreement and subsequent settlement processing shall be handled by condition contract and Condition Contract Settlement Management (CCS). This document provides a 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. The integration of trade spends to condition contracts is done in a non-disruptive manner by introducing a business function and Customizing. For a certain period, rebates and condition contracts can co-exist until the decision is made to move the process completely over to Condition Contract Settlement Management. This means that the move 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. Note The discount and the free goods based trade spends are not affected by the new integration and those areas 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 trade spends. Rebate object was generated and persisted in CRM and this was replicated to ERP via middleware. With CCS integration, there shall be no new business object created in CRM. The trade promotions that are set to be integrated to the condition contract shall have trade spends that shall just hold a reference to the ID of the related condition contract in SAP S/4HANA. The corresponding condition contract shall hold the condition record with the trade spend value and the product dimension information with all the required information. When a trade promotion is released, based on mapping logic, 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 FunctionCRM_TPM_CCS_1. The corresponding switchcrm_tpm_ccs_1 is attached to repository objects so that by default the old behavior is not disrupted. There are new Customizing settings to map trade spends to condition contracts. Additionally, new settings are delivered that allow you to distinguish a trade spend mapped to a condition contract vis-à-vis a rebate. Each trade spend in the trade promotion is mapped to a single condition contract. This carries over the same behavior with the rebates agreement that each trade spend was mapped to an individual rebate agreement. This leads to better transactional consistency between the objects in both the systems. The trade spends with spend combinations that are mapped to a condition contract type and condition type shall skip the rebate processing and go with the condition contract creation in SAP S/4HANA SAP SE or an SAP affiliate company. All rights reserved.

7 Note It shall not be possible to mix the current rebate agreement based trade spends and the condition contract based trade spends in the same trade promotion. The recommendation is to create new promotion types and the corresponding condition generation types to integrate with the condition contracts thus providing a separation between the two objects. Also, the recommendation for claims processing is not to add trade promotions where some go to the rebate agreement object and some go to the condition contract object. This shall lead to issues while creating CRM settlement documents. The transactionwcoco 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 2017 SAP SE or an SAP affiliate company. All rights reserved. 7

8 2 Business Function A new business functioncrm_tpm_ccs_1 and the corresponding switchcrm_tpm_ccs_1 shall be the enabler of trade spend integration to the condition contract object. The following is a screen shot from transaction SFW_BROWSER. Figure 2: Business Function Activation The switch BC sets that are assigned to the switchcrm_tpm_ccs_1 contain some delivered Customizing entries. Some of the switch BC sets are templates for creating other entries SAP SE or an SAP affiliate company. All rights reserved.

9 3 Configuration for CCS Integration 3.1 Business Context When the switch BC sets are activated, new promotion types and condition generation types appear in the system. 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 2017 SAP SE or an SAP affiliate company. All rights reserved. 9

10 2. In Customizing for Customer Relationship Management choose Trade Promotion Management Trade Promotions 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 type1001 there are no trade spends mapped to Rebate BO. But this condition generation type is indeed mapped to condition contract types. The following figure depicts this mapping. 3. In Customizing for Customer Relationship Management choose Trade Promotion Management Trade Promotions Condition Maintenance Condition Contract Mapping for S4 HANA Assign Trade Spend Combination to Condition Contract Type SAP SE or an SAP affiliate company. All rights reserved.

11 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 those that work with condition contract settlement. 4. In Customizing for Customer Relationship Management choose Trade Promotion Management Trade Promotions Condition Maintenance Assign Condition Generation Types SAP SE or an SAP affiliate company. All rights reserved. 11

12 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 new promotion type and the relevant condition generation type. Again, recommendation from SAP is to not mix the rebate related trade spends with the condition contract relevant trade spends. Assign only the appropriate condition generation type to the promotion type. This means, do not assign condition generation types having rebate trade spends and condition generation types having CCS relevant mapping to the same promotion 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 CCS based trade promotions co-existing in the system SAP SE or an SAP affiliate company. All rights reserved.

13 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 enable the 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: 2017 SAP SE or an SAP affiliate company. All rights reserved. 13

14 RCRM_MKTPL_TPM_EXT_CCS_ACRUALS: enables pull of accruals from the condition contract and update fund usages 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 profiles4_cc_sv is available to be assigned to expense types in the Funds Integration area of Trade Management. 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 to ensure that the right updates reach the fund usages. The reports do not cause a conflict between rebate based accrual and CCS-based accrual. The aggregation works correctly in the fund usages SAP SE or an SAP affiliate company. All rights reserved.

15 5 CRM Settlement Integration to Manual Settlement 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 as follows: In Customizing for Customer Relationship Management choose Billing Define Billing Types SAP SE or an SAP affiliate company. All rights reserved. 15

16 Figure 17: Billing Type Customizing The Integration Type as shown in the figure enables manual settlement of CCS SAP SE or an SAP affiliate company. All rights reserved.

17 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 BDocCRM_MKTPL_MKTELEM and the corresponding adaptercrm_mktpl_r3int hold the flow of information from CRM to SAP S/4HANA and back. Inbound QueueTPM_CCS_(TPM ID) is triggered in the SAP S/4HANA system, which then invokes the RFC WB2_REBATES_TPM_INBOUND_RFC. Inbound QueueS4INT_CCS_(TPM_ID) is used to trigger inbound processing of acknowledgement messages in CRM. The placeholder(tpm_id) represents the Trade Promotion ID without the 'T-'. The application log with objectcrm_tpm_ccs and sub-objecttrans_status holds messages regarding transfer. 6.2 Funds Management to Condition Contract Integration BDocCRM_FM_CCS and the corresponding adaptercrm_fm_ccs hold the flow of information from CRM to SAP S/4HANA and back. Inbound QueueR3AU_FUND_(FUND_PLAN_ID) is triggered in the SAP S/4HANA system, which then invokes the RFCCRM_FM_CCSDATA_R3_IN. Inbound QueueR3AD_FUND_(FUND_PLAN_ID) is used to trigger inbound processing of accrual data in CRM. The placeholder(fund_plan_id) represents the Fund Plan ID. The application log with objectcrm_fm_acl and sub-objectmonitor hold messages regarding transfer SAP SE or an SAP affiliate company. All rights reserved. 17

18 7 Pricing Procedure in SAP S/4HANA New access sequencetpcc is available in the SAP S/4HANA system to work with the condition tables holding CCS-based rebates. Pricing condition types that are marked for CCS consumption should be assigned this new access sequence. Then the SD pricing procedure relevant for documents relevant for rebate processing should have this new condition type assigned. Alternatively, you can use the delta accrual batch processing where the accruals are calculated outside of SD pricing for a condition contract. These condition types can be transferred to CRM via the existing condition Customizing download. They are treated as PR condition types. They can also be created in Customizing for Customer Relationship Management by choosing Basic Functions Pricing Create Condition Types SAP SE or an SAP affiliate company. All rights reserved.

19 8 Condition Contract Configuration in SAP S/4HANA 1. In SAP S/4HANA, in Customizing choose WLFA Settlement Management Condition Contract Management 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 SAP SE or an SAP affiliate company. All rights reserved. 19

20 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 the following configuration: 2. In Customizing, choose WLFA Settlement Management Condition Contract Management Condition Contract Maintenance Condition Contract Conditions Sales Assign Condition Types to Condition Type Groups. Figure 20: Customizing to Assign Condition Types to Condition Type Groups SAP SE or an SAP affiliate company. All rights reserved.

21 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 Control for Condition Types. Figure 22: Customizing to Maintain Condition Type Relevance for CCS 2017 SAP SE or an SAP affiliate company. All rights reserved. 21

22 Figure 23: View to Maintain CCS Relevance for Pricing Conditions In the figure, pricing condition typerea3 is marked as condition contract relevant. This condition type would need to be assigned to the SD Pricing Procedure relevant for those sales orders for which accrual posting is desired SAP SE or an SAP affiliate company. All rights reserved.

23 9 Delivered Condition Types Table 1: Condition Types Used in SAP Trade Management Conditi on Type Descripti on Usage Correspon ding TPM Condition Type Reference Condition Type Maintained in Contract Pricing Procedure Billing Pricing Procedure Manual Settlement Pricing Procedure Automatic Settlement Pricing Procedure Delta Accruals REA1 Rebate Accruals Accruals Rate REA3 X X REA2 Rebate Accruals Rev Reversal of Accruals in Settlement REA4 X REA5 Rebate Accruals Settl Accruals Adjustment in Settlement optional optional RED1 Rebate Accruals Accruals Rate for Usage in Delta Accruals Calculation RED3 REA1 X RED2 Rebate Accr Total Total of Existing Accruals for Delta Accruals Calculation RED4 X RES1 Rebate Rebate Rate RES3 X X RES2 Rebate PartSettl Rev Reversal of Existing Settlements in Settlement and for RES4 X X Delivered Condition Types 2017 SAP SE or an SAP affiliate company. All rights reserved. 23

24 Conditi on Type Descripti on Usage Correspon ding TPM Condition Type Reference Condition Type Maintained in Contract Pricing Procedure Billing Pricing Procedure Manual Settlement Pricing Procedure Automatic Settlement Pricing Procedure Delta Accruals Delta Accruals Calculation RENT Rebate Net Amount Net Amount in Manual Settlement X REU1 Rebate Unlikelih ood Set accruals to be done to zero (because rebate target achievement is unlikely and, therefore, there should be no accruals for this customer) X optional X REBV Rebate Business Vol. Business Volume for Settlement X X RETT Rebate Tax Trigger X X (goods related tax, based on tax code from business volume) RETX Rebate Tax X (tax determination in settlement) SAP SE or an SAP affiliate company. All rights reserved. Delivered Condition Types

25

26 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.