Friday, March 24, 2017

ERA22A41 - CO-PA Derivations

ERA22A41 - CO-PA Derivations - Enhancement

Business Process and System Design - CO-PA Derivations . This article outlines the end to process flow and system design for SAP CO-PA Derivation - Enhancement.

Process Attributes

SAP Profitability Analysis module also called as "CO-PA" or "PA" is used for analyzing

Business Process
CO-PA Characteristics Derivation
SAP Module
CO-PA Module
SAP Core Area
Finance
Business Process Code
ERA22A15
SAP Version
1610 
Cloud and On-premise Versions
Presented by
www.simplefinancesupport.com
Description:
SAP COPA module provides functionality to analyze Profitability by multiple market Segments through Characteristics. Transactional data captures Characteristics based on the available Customer Master, Product Master attributes as referenced. All customer related attributes such as Customer Country, Customer Region are populated into COPA tables for analysis. These are called automatic derivation. SAP also provides a mechanism to build derivation based on specific requirements

Transaction
KEDR
Business Roles
Financial Analyst
Inputs / Triggers:
1.       Sales Transaction – Goods Issue and Invoicing
2.       COPA Planning Functions
3.       SAP Journal Entry
Outputs:
1.       Characteristics are derived as per derivation rules
2.       Data is posted with derived characteristics
3.       Data is available for analysis

Flow:
Sales à Finance à Analysis
Remote Consulting


Business Training
Requirements:
1.       Ability to derive COPA characteristics based on certain other attributes
2.       Derive characteristics in all Data Flow options for COPA
Test Scenarios
1.       Perform Data flow transactions and check the derivation


Introduction

SAP Profitability Analysis module also called as "CO-PA" or "PA" is used for analyzing Profitability by different dimensions/segments. Profitability by Customer, Product or combination of Customer, Product and Region etc., Characteristics are defined from fields from Customer, Material/Product and derived from Master Data and Transactional data at the time of transaction processing.

Derivations

Characteristics values are filled at the time of transactional processing based on available attributes. For example,
Realignment is performed with Realignment Run and one run can combine multiple Requests. The job execution is at Run level and system update the status of Run - New, Scheduled, Running , Cancelled or Successful. The Run can be scheduled as background job with immediate or with specific date




Realignment Request

Requests are created within a Run. Every request combines set of selection conditions for selecting specific data for conversion.  Logical set of data change is combined within a specific Request


Business Case - Demo

Following example shows the step by step execution of Realignment. Two characteristics -Material Group 1  and Material Group2 . Material Group1 is realigned based on Derivation rule after changing the Material Master Data and Material Group 2 is changed directly without subjected to Derivation

End to End Process

Check Line Item Data in COPA (KE24)



Summary

Realignment Tool provides to adjust COPA line item data in SAP for Profitability Analysis based on current structure of Characteristics. In S4 version of SAP, Data in GL table - ACDOCA also updated to have reporting adjusted automatically

Please contact us for SAP Consulting Services -

Business Partner - Central Maintenance

Business Partner Design Considerations – Combining BP Roles. This article outlines the end to process flow and system design for SAP Business Partner linking different Roles.

Introduction
SAP provides default roles for majority of Business Processes. Every BP role comes with certain default maintenance functionality. Following different roles are available for Business Partner who is involved in in Sales and Purchasing
  • BP 00000 – General Address Details
  • BP FLVN00 – Vendor Company Code Details
  • BP VLVN01 – Vendor Purchasing Details
  • BP FLCU00 – Customer Company Code Details
  • BP FLCU01 – Customer Sales Area Details
There are many other Business Partners come with different other functions such as Credit Management Details, Agency Details and sol.
There is way of combining these Business Partner Roles to help users maintain these details with single transaction. This functionality was in SAP previous versions was partially achieved through having Central Maintenance Transactions, for example
  • XK01 – Maintain Vendor Centrally (General, Company Code and Purchasing)
  • XD01 – Maintain Customer Centrally (General, Company Code and Sales)
However, there was no way to combine ONE place Vendor and Customer together. With SAP BP functionality, this can be achieved easily.
General Data
BP Role General -000000 General Data for Customer such as basic address details. This role is mandatory role for any business partner.
BP Roles - Vendor
Vendor is maintained at two levels apart from General Address Role. Company Code View and Purchasing View.
Company Code View Company Code details are maintained for vendor to make Financial postings. This was part of SAP old transaction – FK01 and now part of FLVN000 – Business Partner Role
Purchasing View Purchasing Details such as Order Currency and other details for performing Purchase Functions – SAP old transaction MK01 and part of SAP Business Partner – FLVN01
BP Roles - Customer
Customer is maintained at multiple levels depending on the functions performed. For sales activity Company Code and Sales Area view is maintained.
Company Code View Company Code details are maintained for Customer to make Financial postings. This was part of SAP old transaction – FD01 and now part of FLCU00 – Business Partner Role
Sales Area View Customer is extended to a Sales Area – Sales Organization, Division and Distribution Channel. All attributes maintained at these levels are required for performing Sales Activity. This was part of SAP old transaction – XD01 and now part of FLCU01 – Business Partner Role
BP Roles – Central Maintenance
In previous versions of SAP, it was possible to maintain Customers and Vendors centrally with SAP given transactions such as XK01 and XD01. However, there was no way to maintain the entire business partner centrally. Following Screen Shows Business Partner Centrally maintained
This provides easy and single level role for achieving this functionality
Summary
With SAP S4/Hana – Simplification at Core - SAP Business Partner provides a single source of Partner information and eliminates many different transactions. With this special configuration it is possible to combine different standard roles