Home  Embedded Analytics  Attributed Profitability Segments in S/4HANA 1610

Attributed Profitability Segments in S/4HANA 1610

by Ugur Hasdemir January 30, 2017 17 comments

In S/4HANA 1610 a new functionality called ‘Attributed Pro tability Segments’ is introduced. It is now possible t
a (statistical) pro tability segment when there is another real CO object with a settlement rule to COPA.

I was hoping that this would x some occurring issues with Account Based COPA in S/4HANA. Below, I will exp
scenario I have been dealing with in my example with a revenue bearing time & material service order which is b
with a debit memo. The debit memo request has an account assignment to the service order. The service order h
settlement rule to COPA. In this example I use an S/4HANA Finance 1503 environment.

In my second example I will show you how the Attributed Pro tability Segment in S/4HANA 1610 works. See th
difference yourself and decide if you can bene t from this new enhancement.

Current issues in Account Based Profitability Analysis 

Here I will show you a time & material service order scenario and the reporting issues in Account Based COPA w
having attributed pro tability segments.

As you can see in the settlement rule, the order will be settled to COPA:

The Debit Memo request is created with DP90:


In the account assignment in the sales order line items you can see the assignment to the service order and no
assignment to a Pro tability Segment.

This means that you cannot report on the Revenu in Pro tablity Analsyis untill the Service Order is settled. Even
will see the revenue on the settlement cost elements, not on the original revenue cost element.

Reporting
Let’s have a look on the data of this Invoice and service order in the ACDOCA table.

The top rows in the blue rectangular are the actual postings on the service order (e.g. Revenue Accounts). The ot
postings resulting from the settlement of service order (settlement cost elements). In this example I have my COP

characteristic Ship to Party and Ship to Country. As you can see these elds are not derived during the daily pos
They are only derived when the service order is settled to COPA.

The result is that I don’t have my COPA characteristics on my revenue GL accounts. Reporting in COPA with the
standard ACDOCA reports and KPI Fiori tiles will result in incomplete gures in these cases.

Have a look at the Actual Revenue KPI tiles in Fiori which come with SAP Smart Business as part of Embedded
Analytics. The Revenue KPI app is based on Account Based COPA, thus Cost Elements and corresponding pro t
characteristics. In this current scenario the pro tability characteristics are not assigned to the revenue accounts.
you will see is this:

The same issues applies on the new ACDOCA report ‘Market Segment Actuals’:


The only way to overcome this is building your own reports in HANA Live and making reports in one of the SAP
Object tools available (Lumira, Webi or Analysis for Of ce). Similar to what I have done for my T&M service orde
pro tability in Analysis for Of ce:

Using the attributed Profitability Segments in S/4HANA 1610 

As mentioned at the beginning of this post, the new functionality called ‘Attributed Pro tability Segments’ has b
introduced. If there is a real account assignment to one of the objects below, the system can derive “statistical” (
attributed) COPA segments for reporting purpose:

Cost Center

Internal Order

Project

Sales Order

 Production Order

Unfortunately the service order is not included in this list as object. Thus a direct solution for my scenario explain
above has not been provided yet by SAP. I hope the service order will be supported soon as receiving CO object

However let’s see how this new functionality works with a supported object, the internal order. Technically it’s th
issue we are solving, but instead of the service order we use an internal order as account assignment. In the
con guration I have activated the Attributed Pro tability Segment for internal Orders only for postings on P&L a
As mentioned at the beginning of my post, I will use a S/4HANA 1610 environment in this example.

The below internal order has an settlement rule to COPA.


I create a sales order with assignment to the above internal order in the line item. As you can see there is no ass
to COPA.

Final posting of the invoice:


 S/4HANA Blog
HOME CATEGORIES  ABOUT ME    

After posting the invoice you will see the attributed segment in the revenue line item in the ACDOCA table.

The real CO account assignment can be found in eld Object Type (ACCTASY) which is the Internal Order in this
you can see the COPA characteristics like the Material, Customer, Material Group, Customer Group and Ship to P
derived as well!

I see huge bene ts in this new functionality for reporting purposes since pro tability characteristics are derived
at the moment of posting even if there is another CO assignment. For me it was a long awaited functionality, ho
very disappointed that it isn’t working yet in scenarios were the service orders is the receiving cost object. I have
addressed this to SAP and waiting for a reply.

I hope you have enjoyed reading this and I wonder if you have experienced similar issues with CO objects as we
have other thoughts or questions related to this subject, please don’t hesitate to leave a comment. If there are an
S/4HANA related cases you would like to see, just let me know and perhaps I can write a future post on the topi

Update September 2017: SAP has released an OSS note to enable the attributed Pro tability Segment function
Service and Maintenance Orders. By default this is not enabled in the releases S/4 HANA Finance 1605, S/4 HAN
1610 and 1709.

After implementing the following OSS note this will be enabled:

2497666 – S/4 HANA Finance: Attributed pro tability segments for service and maintenance orders

Share this:

     
Related

Finance in S/4HANA 1610: the what, Realignments nally available in Embedded Analytics in S/4HA
why and how Account Based CO-PA with (with demo videos)
December 25, 2016 S/4HANA 1610 April 25, 2017
In "S4HANA" March 2, 2017 In "Embedded Analytics"
In "Pro tability Analysis"

COPA EMBEDDED ANALYTICS HANA MANAGEMENT ACCOUNTING PROFITABILITY PROFITABILITY ANALY

S4HANA

 17 comments 0    

UGUR HASDEMIR

With a nancial background combined with his passion for Information Technology, Uğur is a
advisor with experience in ERP implementation since 2010 in the area of Financial and Mana
accounting. Driven by his passion for new technologies, Uğur has focused on SAP S/4HANA s
introduction of Simple Finance in 2014. Read More: http://s4hanablog.com/about-me/

previous post
FINANCE IN S/4HANA 1610 THE WHAT, WHY THE SAP GUI MENU IS BACK IN F
AND HOW: PART 2


 YOU MAY ALSO LIKE

EVENT-BASED REVENUE REALIGNMENTS FINALLY FINANCE IN S/4HANA 161

RECOGNITION IN S/4HANA 1610 AVAILABLE IN ACCOUNT WHAT, WHY AND..
June 21, 2017 BASED CO-PA WITH... December 25, 2016
March 2, 2017

17 COMMENTS

PETER

 January 30, 2017 - 10:21

Hi Ugur,
Clear story!
Very unfortunate indeed that the service order is not included.
I would guess that it will be added in time…
Regards, Peter

UGUR HASDEMIR

 September 21, 2017 - 08:20

Hi Peter,
check this OSS note to enable the functionality for Service/Maintenance orders:
2497666 – S/4 HANA Finance: Attributed pro tability segments for service and maintenan
orders

 September 21, 2017 - 13:11

Hi Ugur,
Thanks! 
 Ga ik gelijk laten doen.
Gr. Peter

ZLATAN OSMANCEVIC

 February 2, 2017 - 20:34

Nice and clear explanation, very inconvenient issue as you can’t have real-time insight. Especially st
FI reporting isn’t a possibility. I blame my FICO consultant consultant.

REALIGNMENTS FINALLY AVAILABLE FOR ACCOUNT BASED CO-PA IN S/4HANA 1610 – S/4H
BLOG

 March 2, 2017 - 18:18

[…] you are new to Attributed Pro tability Segments you can read my blog on this newly released […

EMBEDDED ANALYTICS IN S/4HANA (WITH DEMO VIDEOS) – S/4HANA BLOG

 April 25, 2017 - 07:40

[…] you what you can achieve with HANA Live or tools like Analysis for Of ce. Speci cally in the Att
Pro tability Segments blog I did show some reporting possibilities in S/4HANA. In this blog I aim to
good overview […]

JOY KENNEDY

 June 27, 2017 - 05:23

I am unable to locate the Actual Revenue KPI tile in the Fiori Apps Library that is referred to in your
http://s4hanablog.com/tag/pro tability-analysis/.
Please could you con rm if this is a standard tile or one that you built? If it is standard, please could
me the name from the Apps Library as searching by Actual or Revenue returned no apps that seem
this one. If it’s a standard tile, please could you con rm which technical catalog it is in too?
I was able to nd the Market Segment Actuals easily.

UGUR HASDEMIR

 June 27, 2017 - 07:52

Hi Joy,
It is a standard tile and the link in the Fiori App Library is here:
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/#/detail/Apps('F0826‘)/
Ugur Hasdemir

SZYMON MASLOWSKI

 August 1, 2017 - 10:16

Hi Ugur,
Great job!
I wanted share with you an issue we identi ed in this area.
I was wondering if you had come across this issue as well (and might have a solution).
It’s about unit of measure recording for revenue postings on cost objects.
We are on 1710 FPS02.
In our design we use sales orders assigned to WBS elements. WBS elements are settled to account
CO-PA.
We’ve noticed that if we post billing document (to WBS element) unit of measure is not being updat
ACDOCA.
It’s only updated if unit of measure is maintained in revenue GL master (cost element category 11) a
of measure of material being sold is the same.
That would require separate revenue accounts for materials with different units of measure (not rea
practical).
Did you come across this issue?
We logged this issue with SAP and it’s with development now.
We’ll update you once we get a reply.
Regards,
Szymon

UGUR HASDEMIR

 August 1, 2017 - 11:00

Hi Szymon,
Thanks for contributing to the forum. I assume your system version 1710 fps02 was a typo
I’ve not come across this speci c issue, but I know that there are some customizing steps i
add additional quantity and UoM elds in ACDOCA. Perhaps this part is missing in your sy
I’m not sure.
You can nd this new customizing item in: IMG-Controlling-General Controlling-Additional
Quantities. There is also a BADI to ll the additional elds, which you can nd in this iMG p
I’m not sure if this is going to help you, but I’m anyhow very interested in the solution provi
SAP. So it would be very nice if you can post an update here.
thanks and regards,
Ugur

ALICE NG

 December 11, 2017 - 08:46


 Hi SZYMON,
I’m in a S/4HANA project now that is using Project System to manage the project. I follow
Practice to activate Account Based COPA only. Similarly, I assigned sales orders to WBS e
This WBS Element carries Revenue and Cost. I give Settlement rule receiver as PSG.
But I hit error when I try to settle WBS elements to PSG via CJ88 after running RA via KKA
system is asking for PA Transfer Structure for settlement. I understand that PA Transfer St
will transfer from Cost Element to COPA Value elds. But we don’t maintain Value elds fo
Account based COPA.
Really appreciate it if you can enlighten me on how to set settlement rule as PSG and settl
Account Based COPA.
Hi Ugur,
Appreciate your comments here too.
Thanks & regards,
-Alice-

SZYMON

 January 3, 2018 - 10:40

Hi Alice,
I hope our host Ugur has nothing against using his fantastic blog for resolving consulting issues :).
I can’t see any aw in your logic.
Our settlement pro le does not contain “PA transfer struct.” entry.
And we settled to account based CO-PA without any problems.
However we didn’t execute results analysis. That’s probably the only difference.
Please let me know once you resolve it.
Happy New Year.
Regards,
Szymon

UGUR HASDEMIR

 January 3, 2018 - 11:57

Hi Alice, Szymon, rst of all I wish you both all the best for 2018. It’s absolutely fantastic to
this blog turns into a collaboration/discussion platform :). Unfortunately due to lack of time
able to involve in all the discussions, but will try to contribute as soon as I have the chance
By the way, I recently gained access to a S/4HANA 1709 sandbox. Will try to write someth
you have any suggestions on speci c topics perhaps?

SZYMON

 January 4, 2018 - 02:01


Hi Ugur,
All the best in the New Year! I’ve been working with 1709 since November.
There are some nice new features in my area of expertise (Product Costing, Mate
Ledger). For example now it’s possible to report production costs on work centre
operation level. The maximum number of cost components is now 180 (used to b
But the quality of code is not that good. I had to log dozens and dozens of inciden
Hopefully upcoming SPs will sort it out.
Best regards,
Szymon

ALICE NG

 January 4, 2018 - 02:30

Hi Szymon,
Thanks for the reply. Happy New Year to you!.It works now after I removed the “P
transfer struct.” value. Really appreciate it.
I have another question. I’m working on S/4HANA 1709 now. Yesterday, I realised
that triggers from Network for a service material and converted to PO… WBS & P
de nition are not populated into ACDOCA table. Any clue?
Hi Ugur,
Happy New Year to you too. Appreciate it if you can shed some lights on Financia
reporting and Pro tabilty reporting creation that based on ACDOCA table. I nd
Of ce Analysis is more about pivot table reporting rather than reporting.
Best regards,
-Alice-

SZYMON MASLOWSKI

 January 4, 2018 - 08:30

Hi Alice,
I’m glad you managed to resolve the CO-PA settlement issue.
With regards to the second issue.
Can you please be more speci c: are you talking about goods receipt po
against a PO?
Thanks,
Szymon

ALICE NG

 January 4, 2018 - 08:38


 Hi Szymon,
Yes you are right. WBS & Project de nition are not populated i
ACDOCA table upon GRN of the service material. Only Netwo
number is populated.
Thanks,
-Alice-

LEAVE A COMMENT

Your Comment

Name* Email* Website

SUBMIT

NOTIFY ME OF FOLLOW-UP COMMENTS BY EMAIL.

 GOOGLE +  LINKEDIN  YOU

@2017 - PenciDesign. All Right Reserved. Designed and Devel