sap assignment to a profitability segment

Attributed Profitability Segments in S/4HANA 1610

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

I was hoping that this would fix some occurring issues with Account Based COPA in S/4HANA. Below, I will explain the scenario I have been dealing with in my example with a revenue bearing time & material service order which is billed with a debit memo. The debit memo request has an account assignment to the service order. The service order has an 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 Profitability Segment in S/4HANA 1610 works. See the difference yourself and decide if you can benefit 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 without having attributed profitability 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 Profitability Segment.

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

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 others are postings resulting from the settlement of service order (settlement cost elements). In this example I have my COPA characteristic Ship to Party and Ship to Country. As you can see these fields are not derived during the daily postings. 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 use of standard ACDOCA reports and KPI Fiori tiles will result in incomplete figures 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 profitability characteristics. In this current scenario the profitability characteristics are not assigned to the revenue accounts. What 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 Business Object tools available (Lumira, Webi or Analysis for Office). Similar to what I have done for my T&M service order profitability in Analysis for Office:

Using the attributed Profitability Segments in S/4HANA 1610 

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

• Cost Center
• Internal Order
• Sales Order
• Production Order

Unfortunately the service order is not included in this list as object. Thus a direct solution for my scenario explained 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 the same issue we are solving, but instead of the service order we use an internal order as account assignment. In the configuration I have activated the Attributed Profitability Segment for internal Orders only for postings on P&L accounts. 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 assignment to COPA.

Final posting of the invoice:

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 field Object Type (ACCTASY) which is the Internal Order in this case. As you can see the COPA characteristics like the Material, Customer, Material Group, Customer Group and Ship to Party are derived as well!

I see huge benefits in this new functionality for reporting purposes since profitability characteristics are derived directly at the moment of posting even if there is another CO assignment. For me it was a long awaited functionality, however I’m 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 well? If you have other thoughts or questions related to this subject, please don’t hesitate to leave a comment. If there are any other S/4HANA related cases you would like to see, just let me know and perhaps I can write a future post on the topic.

Update September 2017:  SAP has released an OSS note to enable the attributed Profitability Segment functionality for Service and Maintenance Orders. By default this is not enabled in the releases S/4 HANA Finance 1605, S/4 HANA OP 1610 and 1709.

After implementing the following OSS note this will be enabled:

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

Share this:

• Click to email a link to a friend (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Twitter (Opens in new window)
• Click to share on WhatsApp (Opens in new window)

Ugur Hasdemir

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

Finance in S/4HANA 1610 the what, why and how: Part 2

The sap gui menu is back in fiori 2.0, you may also like, optimizing your financial close: the power of sap..., understanding intercompany matching and reconciliation with sap s/4hana, leveraging proof of delivery (pod) in sap s/4hana..., embracing the past, envisioning the future: sap gui..., s/4hana mastery: 10 crucial skills for the modern..., from parallel to universal parallel: the evolution of..., the roadmap to success: leveraging best practices and..., how to perform mass material price change (mr21)..., my favorite innovations in s/4hana 2020, ready for brexit with s/4hana, 26 comments.

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

check this OSS note to enable the functionality for Service/Maintenance orders:

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

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

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

I am unable to locate the Actual Revenue KPI tile in the Fiori Apps Library that is referred to in your blog https://s4hanablog.com/tag/profitability-analysis/ . Please could you confirm if this is a standard tile or one that you built? If it is standard, please could you give me the name from the Apps Library as searching by Actual or Revenue returned no apps that seemed like this one. If it’s a standard tile, please could you confirm which technical catalog it is in too?

I was able to find the Market Segment Actuals easily.

It is a standard tile and the link in the Fiori App Library is here: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F0826 ‘)/W12

Great job! I wanted share with you an issue we identified 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 based CO-PA. We’ve noticed that if we post billing document (to WBS element) unit of measure is not being updated in ACDOCA. It’s only updated if unit of measure is maintained in revenue GL master (cost element category 11) and unit of measure of material being sold is the same. That would require separate revenue accounts for materials with different units of measure (not really 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

Thanks for contributing to the forum. I assume your system version 1710 fps02 was a typo :).

I’ve not come across this specific issue, but I know that there are some customizing steps in CO to add additional quantity and UoM fields in ACDOCA. Perhaps this part is missing in your system? I’m not sure.

You can find this new customizing item in: IMG-Controlling-General Controlling-Additional Quantities. There is also a BADI to fill the additional fields, which you can find in this iMG path.

I’m not sure if this is going to help you, but I’m anyhow very interested in the solution provided by SAP. So it would be very nice if you can post an update here.

thanks and regards, Ugur

Hi SZYMON, I’m in a S/4HANA project now that is using Project System to manage the project. I follow Best Practice to activate Account Based COPA only. Similarly, I assigned sales orders to WBS element. 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 KKA2 . The system is asking for PA Transfer Structure for settlement. I understand that PA Transfer Structure will transfer from Cost Element to COPA Value fields. But we don’t maintain Value fields for Account based COPA.

Really appreciate it if you can enlighten me on how to set settlement rule as PSG and settle to Account Based COPA.

Hi Ugur, Appreciate your comments here too.

Thanks & regards, -Alice-

I hope our host Ugur has nothing against using his fantastic blog for resolving consulting issues :). I can’t see any flaw in your logic. Our settlement profile 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.

Hi Alice, Szymon, first of all I wish you both all the best for 2018. It’s absolutely fantastic to see that this blog turns into a collaboration/discussion platform :). Unfortunately due to lack of time I’m not 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 something. Do you have any suggestions on specific topics perhaps?

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, Material 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 be 40). But the quality of code is not that good. I had to log dozens and dozens of incidents. Hopefully upcoming SPs will sort it out.

Best regards, Szymon

Hi Szymon, Thanks for the reply. Happy New Year to you!.It works now after I removed the “PA transfer struct.” value. Really appreciate it. I have another question. I’m working on S/4HANA 1709 now. Yesterday, I realised that PR that triggers from Network for a service material and converted to PO… WBS & Project definition 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 Financial reporting and Profitabilty reporting creation that based on ACDOCA table. I find that Office Analysis is more about pivot table reporting rather than reporting.

Best regards, -Alice-

I’m glad you managed to resolve the CO-PA settlement issue. With regards to the second issue. Can you please be more specific: are you talking about goods receipt posting against a PO?

Thanks, Szymon

Hi Szymon, Yes you are right. WBS & Project definition are not populated into ACDOCA table upon GRN of the service material. Only Network number is populated.

Thanks, -Alice-

Thanks for detail document.

we have activates account based COPA. now attributed profitability segment feature is here. but when i am trying to use and analysis this feature. I am not getting expected result. as per my understanding if we use Attributed PA seg, in that case if we are posting FI entry on Cost center as real object and same time cost will post to COPA as statistical posting as we do not need to wait period end closing to see margin or profitability against my revenue posted copa on real time. i have done setting attributed PSG and marked Cost center category F and P/L account marked yes. and did one derivation rule KEDR as source i have selected 1) controlling are and 2) ACCASTY- Account Assignment Category and as target ia have selected Sales org updated derivation rules values as Controlling Area A000 and Account Assignment Category as CTR and Sale org 1010.

but when i posted document with some fi entry it posted to cost center as real but no posting on COPA as statistical.

i think i am missing something here or i am doing correct.

is there anything more needed to get desired output.

Can you please help me here.

thanks Akesh

I really did my best, but I don’t understand your requirement. You post actuals on a cost center and expect that the postings should appear on the attributed profitability segment? I don’t see the relation between your sales organization and the cost center. The attributed profitability segments works only when you have an account assignment to one of the below objects and these objects are assigned to a Profitability Segment:

• Cost Center • Internal Order • Project • Sales Order • Production Order • CS / PM Order

In your case, you are already directly posting to a cost center. There is no other object which is assigned to the cost center. You can already fill your PSG on the P&L account while doing the posting.

Perhaps it will help when you describe your requirement first?

Hi Ugur, Thanks for detail document, now we are implementing 1709, KE27 (Revolution of COGS) functionality is available in 1709?

Thanks, Chandrasekhar

NO 1709 account based copa Does not support ke27, If needed ke27 go to Costing based copa

Hi Ugur, Thanks for your blog, very interesting. Small question to you or any members: did you made something special to have the customer / bill-to/ship-to to the Profitability Segment? We have setup a WBS with a settlement rule. Then we do a billing via SD on this WBS. The attributed probiltability segment works but it is unable to retrieve characteristics from the Sales Order (e.g. Sales Order number, bill-to…). do you have any idea? thank you

Best regards,

Hi Walter, do you work with a multi level WBS or just 1 level? Attributed profitability segment functionally does not work with multi level WBS by default.

Attributed profitability segment (APS) solution only works where, sender object (like Cost Center, WBSe, Internal order etc) should have one to one relationship with receiver object (Statistical PSG) means characteristics (like Division, Sales org, or any characteristics. means one cost center X should be posted only one division not more than one. then only it will post the data. if we have 2 or more received characteristics values then APS will not work. so SAP has to work on the provide further solution to APS work in multiple entries as receiver. also data posted using APS will not available for Top-Down Distribution. if we want execute the TDD then first you need to post data as real PSG using CO-PA Assessment then we can do the TDD.

Great blog and the follow on comments and responses are extremely beneficial. I especially want to thank Alice for her comments. I’m working on a 1709 implementation now where Attributed Segments is turned on trying to generate the settlement rule for the WBS assigned to the SOLI has been a departure from what I did in 1610. In that scenario I was able to do CJB2 for the SO and bring over all the PSG characteristics into the WBS settlement rule. Then run KKA2, then CJ88. I will try the set up listed here to see if it works. Also I’m setting up the configuration for Event Based Rev Recognition.

Uger or others, will there be a problem using both methods? APS for Single Site projects and KKA2/CJ8G for Multi-site projects where billing is done for each individual site? (plus Material/Labor needs to be split out in COPA. In 1610 I did that through the Settlement profile).

Hello Ugur, NIce Blog, i have tried same internal order example, but its not working for me. i don’t understand what i am missing. I have activated that internal order in customization.

I created an internal order with psg settlement rule and internal order linked to sales order. After PGI and invoice, in ACDOCA Table i am getting psg number but not the other characteristics like sales order and other derivation characteristics.

Can you please give light or hint, what could i miss.

Thanks, Ashok

Leave a Comment Cancel Reply

Save my name, email, and website in this browser for the next time I comment.

Notify me of follow-up comments by email.

This site uses Akismet to reduce spam. Learn how your comment data is processed .

• March 25, 2017
• by Sachin Patil

“Attributed Profitability Segments”

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

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

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 without having attributed profitability 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 Profitability Segment.

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

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 others are postings resulting from the settlement of service order (settlement cost elements). In this example I have my COPA characteristic Ship to Party and Ship to Country. As you can see these fields are not derived during the daily postings. 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 use of standard ACDOCA reports and KPI Fiori tiles will result in incomplete figures 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 profitability characteristics. In this current scenario the profitability characteristics are not assigned to the revenue accounts. What 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 Business Object tools available (Lumira, Webi or Analysis for Office). Similar to what I have done for my T&M service order profitability in Analysis for Office:

Using the attributed Profitability Segments in S/4HANA 1610 

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

• Cost Center
• Internal Order
• Sales Order
• Production Order

However let’s see how this new functionality works with a supported object, the internal order. Technically it’s the same issue we are solving, but instead of the service order we use an internal order as account assignment. In the configuration I have activated the Attributed Profitability Segment for internal Orders only for postings on P&L accounts. 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 assignment to COPA.

Final posting of the invoice:

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 field Object Type (ACCTASY) which is the Internal Order in this case. As you can see the COPA characteristics like the Material, Customer, Material Group, Customer Group and Ship to Party are derived as well!

I see huge benefits in this new functionality for reporting purposes since profitability characteristics are derived directly at the moment of posting even if there is another CO assignment.

Post comment

Cancel reply.

You must be logged in to post a comment.

I share experience and observations knowledge about the SAP and peripheral systems. 

Copyright © 2022 Sachin H Patil . All Rights Reserved.

• ERPCorp FI/CO Books
• Access SAP Modules
• SAP Webinars
• Client Roster
• BECOME A MEMBER

ERPCorp SAP FICO Blog

Attributed profitability segment - sap s/4hana.

By Anand Seetharaju

Characteristics from a profitability segment can be read and posted to income statement line items based on the best guess principle. This feature was introduced in account-based CO-PA (now Margin Analysis) in S/4HANA 1610. You can use drill-down reporting on posted data. Without attributed profitability segments, you must wait until month-end activities such as settlement, allocation and top-down distribution. With the new feature, you can achieve real-time profitability reporting during the month.

With S/4HANA, you can perform contribution margin reporting in CO-PA using both costing-based and Margin Analysis. SAP recommends Margin Analysis as the default solution, however both can co-exist. Only Margin Analysis updates the universal journal (ACDOCA), and all future innovations will happen with Margin Analysis. Customers considering both approaches may find it difficult to justify costing-based COPA in S/4HANA since most costing-based functionality is now available with Margin Analysis.

The following new features are introduced with Margin Analysis in S/4HANA 1610

•     Cost of goods splits using cost splitting profile
•     Price splitting per variance category using price difference splitting profile
•     Attributed profitability segment – characteristics update without settlement
•     Event-based revenue recognition without settlement
•     Prediction ledger with statistical sales conditions

Let's explore attributed profitability segments

With Margin Analysis, revenue and cost are always reconciled with the profit and loss statement since the data is stored in the universal journal. You do not need to reconcile Margin Analysis with GL. In addition, you can drill-down on any characteristic such as brand, sales group, product group, or customer group using data stored in the universal journal.

These characteristics are typically derived and posted to the universal journal at the time of logistical billing documents or at period end with settlement, allocation, or top-down distribution. Figure 1 displays how the universal journal enables single source of truth for reporting by storing all information from various components in one place  –  single source of truth.

Figure 1 : Universal Journal Integration

Attributed Profitability Segment vs. Real Account Assignment Derivation

With attributed profitability, you can derive characteristics early in the process with the best-guess principle, rather than wait until period-end settlement activity. For example, let's assume, in project-based billing, you have WBS costs not yet billed to the customer. A settlement rule is created with brand or customer group in the profitability segment account assignment.

When a document is posted to WBS, the characteristics are derived from the settlement rule and updated in the universal journal. Another example is to derive characteristics with expense postings to a cost center. The attributes derivation helps you perform profitability analysis reporting before the month-end closing settlement process. These attributes are statistical in nature rather than real account assignments and used primarily for reporting.

Meet Anand Seetharaju in-person at SAP Controlling Financials 2023 Conference, Sept 17-19 San Diego, CA   Use coupon code: JJ100 for $100 off: Click here now  

  At the time of document posting, the system determines whether a real account assignment or attributed assignment is involved. In the case of a real account assignment object identified by the sending application such as settlement of cost object to CO-PA or billing document in a sales order scenario, profitability segment number is transferred to G/L along with the combination of characteristics exists in CO-PA segment.

With an attributed profitability segment identified (activation in IMG), the system determines whether a settlement rule exists along with the corresponding profitability segment data and then populates characteristics on the income statement line item on the document to enable drill-down reporting for supported account assignment objects. If no settlement rule exists, but a sales order item exists in income statement line item and sales order carries a profitability segment, the G/L line item is populated with characteristics from profitability segment from the sales order. If sales order does not carry a profitability segment either, certain characteristics are read from sales order header.  

To derive attributed profitability segments, GL accounts must be setup as either Primary costs/Revenue or Secondary costs.

The characteristics apply for both P&L and some balance sheet accounts.

The following account assignment objects are supported when G/L line items post:

• Cost Center
• Internal Order
• Sales Order
• Production Order
• Service and Maintenance Order with SAP Note 2497666

To use attributed account assignments, activate the derivation in CO-PA configuration shown in Figure 2.

Controlling>Profitability Analysis>Master Data>Activate Derivation for Items without profitability segment

Figure 2 : Configuring Attributed Profitability Segment

First create a WBS and assign PSG settlement rule with 100% as shown in Figure 3. I added brand as one of the characteristics among others to be derived.

Figure 3 : Settlement Rule Added to a WBS

To learn more about Profitability Segments, and other SAP FICO topics  become a member  Click here now :

Next, post a general ledger document to the WBS. The universal journal shows brand derived as shown in Figure 4. The CO-PA reports do not show these characteristics until settlement is performed. You may have to write a new ad-hoc ACDOCA report using a CDS view and/or analysis for office query to view the characteristics.

Figure 4 : Universal Journal display with Brand Derivation

As of writing this blog (tested in 1809), the logic works only with settlement rules with 100% assignment to profitability segment. If you want to split profitability segments, the settlement rules are not considered unless the split is assigned to an identical profitability segment.

Refer to the example in Figure 5. This is documented in SAP Note 2439201 – S/4HANA Finance: Derivation logic when determination “attributed profitability segments”.  The below example depicts such a scenario. Refer to Note 11 for future release on this functionality.

Figure 5 : Settlement Rule Splits

The universal journal in Figure 6 shows brand not derived when multiple settlement rule exists with a split criterion.

Figure 6 : Universal Journal Shows Brand Not Derived

Attributed profitability segments help you perform multi-dimensional reporting on CO-PA characteristics such as product, customer, brand, product group before month-end closing. You can further refine the characteristics at closing.

You accomplish this by setting up a settlement rule on account assignment objects. Documents posted based on the settlement rule and information available at that point in time (best guess). The prerequisite for this is account-based CO-PA.

When working on SAP Margin Analysis we recommend you work with our ERPCorp SAP experts:

Learn about ERPCorp Coaching & Consulting

For the latest updates

About the author

Anand Seetharaju

Anand Seetharaju is a certified SAP S/4HANA financial and management accounting consultant. He holds active CPA and CMA licenses and has more than 25 years of experience in business process design, consulting, and implementation of accounting systems. He has led several SAP S/4HANA Finance and Central Finance transformation projects and has presented several topics at SAP conferences. Additionally, he has extensive implementation experience with the SAP classic general ledger, new general ledger, and SAP S/4HANA general ledger, including the conversion from a classic general ledger. Anand’s experience includes global SAP finance and controlling implementations and rollouts with an emphasis on Central Finance, receivables management, revenue accounting and reporting, cash and liquidity management, profitability analysis, project systems, product costing, material ledger, capital asset management, leasing, global tax, and legal reporting.

Author's recent posts

Captcha Image

PO account assignment to a Profitability segment

SAP Guru’s > We are designing a third party sales process that will be using standard > third party functionality within SAP 3.1I. Basically, a sales order will > be created with line items using the TAS item category. The purchase > requisition created via the sales order will be converted to a purchase > order using automatic creation of purchase orders from requisitions, tran > code ME59. > > My question relates to the account assignment for the purchase order. The > client would like to use a G/L account that has been set up as a revenue > element. Using tran code ME59, we get an error that the G/L account > requires an assignment to a CO object. I know that the revenue element > needs an assignment and the client would like the assignment to go to a > profitability segment. > > I tried using tran code ME58, creating a purchase order via a purchase > requisition, and saw that the fields are visible, just grayed out. If I > create a purchase order using the purchase order create menu path (tran > code ME21) with the same item category and account assignment group, I do > not have this problem. I can create the profitability segment within the > coding block when I update the account assignment and my purchase order is > good to go. > > Is anyone aware of config that will allow a profitability segment to > automatically create using ME59? Or is it just not possible? > Thanks, Greg Muchler SAP Sales & Distribution EDS/Rolls-Royce Account Phone 317-230-2190, pager 317-235-2963 Email [email protected] also [email protected] Mail loc 29A > > > This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipients, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.

I would be surprised that the error message was popped up when you ran ME59 transaction. The fact is that the related sales order has already been defaulted as the cost object for your account assigned PR.

In account assignement settings you can unhide the profit segment

Related Topics

3300714 - Profitability Segment serving as true Account Assignment

You receive the error "Enter only one true account assignment" when trying to post journal entry, since you have WBS element and Market Segment in Profitability Analysis acting as true account assignments. 

Environment

SAP S/4HANA Cloud

Profitability Segment always serves as true CO account assignment, although, it's possible to have a statistical WBS element.

If a true CO account assignment to WBS element is not required, you could alternatively make profitability segment the true CO account assignment and add WBS element on the account assignment screen of the profitability segment as attribute.

The other option would be to have WBS element as true account assignment and then use Profitability Analysis Substitution / Validation to derive the additional PA characteristics.

Substitution for Market Segments

Sales Accounting: FAQ

Profitability Analysis, Market Segment, True Account Assignment, PA Characteristics, Substitution, Validation, WBS Element, Account Assignment  , KBA , CO-PA-MD , Master Data , How To

Privacy | Terms of use | Legal Disclosure | Copyright | Trademark