Extension ledger not posting in Margin account in COPA v2022

[gustavo_hermozaazaldegui]

Dear SAP

We have a strange behaviour in our new version 2022 s4hana against the expect result that we have checked in varius forums.

https://blogs.sap.com/2020/04/02/sap-s-4hana-extension-ledger-use-cases/

Regarding point 12:

We have this configuration

in spro :Financial Accounting/Check Prediction Ledger

we have done this posting in ledger L6 and fill the characteristic in PA

fill characteristics:

We have checked the table acdoca, the following value => XPAOBJNR_CO_REL=X.

But, if we check transacction KE24 or KE24N, It does not create anything line or registers in Margin Account in COPA.

Only, We have checked that the system create one registers of characteristics

On the other hand, we can observed that our posting are reflected in ledger 6 using s_ebs_44000137 transaction (Reporting for Table FAGLFLEXT from REPORT PAINTER FGI6 TCODE) It is correct but if we check our PROFITABILITY ANALYSIS then it is a big difference. We undertand that for this reason we are creating an extension ledger for profitability analysis

Could SAP comment or recommend which points to check?

Other possible point that we can observed that some tables missing as the following:

are these tables necessary?

CE5: Logical sement level

CE7: Internal Help structure for assessments

CE8: Internal Structure for assessment

Then, We were wondering, How the Margin account in COPA gets the line or posting of ke24 or ke24n or ke30 transactions?

Could you recommend us what is missing or any note oss for clarifity this topic, please? Should we regenerate the COPA again?

for example ,we found this note oss: 2866321 Predective Accounting Display settings and the expect result is correct. Then what is missing for the entry to appear in COPA using the margin accounting model?

Welcome all recommendations

Gustavo

[gustavo_hermozaazaldegui]

Dear SAP,

I have checked this behavior from S_AL0_19000001 - Transaction S_AL0_19000001.

If ledger Group is different than Ledger principal, then the system create document COPA otherwise not create anything if we put the same extension ledger.

I was wondering if this is the expected result because it does not make sense. In the ledger group we should put the extension ledger. In fact when we run the P&L and balance sheet report for extension ledger L6, We should see both postings from leading ledger 0L and extension ledger L6 but this is not the expected result in our 2022 version.

Let us explain with one illustration. we have put the following here:

With this, we will have this result: We have created our COPA document.

continue..

[gustavo_hermozaazaldegui]

If we have checked the tables: This is no longer correct because we should have L6 as an extension ledger, and not 0L in table ACDOCA.

in BKPF table.

[gustavo_hermozaazaldegui]

I have checked the options from this blogs:

https://blogs.sap.com/2020/04/02/sap-s-4hana-extension-ledger-use-cases/

Based on what kind of journal entries you want to post to the extension ledger, you can define 3 extension ledger types:

• Standard Journal Entries– stores journal entries with real document numbers. These journal entries cannot be deleted and have to be reversed when required. Use cases – management adjustments, tax adjustments, realignments
• P – Line items with technical numbers /no deletion possible (former Prediction) – stores journal entries with technical numbers only, without document numbers. They cannot be deleted and have to be reversed when required. Use cases – predictions, commitments, statistical sales conditions.
• S – Line items with technical numbers/deletion possible (former Simulation) – stores journal entries with technical numbers only, without document numbers. They can be deleted. Use cases – simulation, posting

I have changed the ledger L6, the following:

The same behavior using Ledger type Extension ledger type as "Standard journal" It does not create values document in COPA

To sum up: if we are using anything options , the result is not expect result.

We are understand that when you run a P&L and balance sheet report for leading ledger 0L, we will only see documents that are posted in leading ledger 0L; however, when we run a P&L and balance sheet report for extension ledger L6, we ’ll see both postings from leading ledger 0L and extension ledger L6 , but this behaviour is not what we get. à Any suggestions? Could you tell us if this is possible, we will need to use any extension etc.

I have found these oss notes but we understand that this should be a standard solution in version 2022.

804753 - FlexGL: Data transfer to CO from parallel ledger

932045 - FlexGL: Data transfer to CO from parallel ledger (part II)

Do we have to open an Incidencit to SAP to review this behaviour ? All suggestions are welcome!!!

Gustavo

[gianluca_taccone · Accepted solution]

Ok,

please read OSS 2868965 , specially the part where it says "reading data from an Extension ledger is not supported using transactions KE24 nor KE30".

SAP is developing many new functionalities in S/4 it is essential that you understand that sometimes the way of benefit of this new functionalities is FIORI.

If you are not happy with my replies you can open an incident.

Best

Gianluca

[gustavo_hermozaazaldegui · Accepted solution]

Dear GIANLUCA,

I agree with you recommendations and i truly believe that we have clarified with you help this doubts.

Without a doubt whatsoever the note oss will help to us the follow the right way.

I cannot help but say as commented Martin in his blog and as it was published in SAP Press that we can use a extension ledger for

profitability analysis. This due that we had looked a solution to manual posting only in PA and we have founded that SAP recommends considering the possibility of using the "extension" option of general ledger or main ledger.

We understand that this is possible as we have observed in the journal ACDOCA and done the testing.

Yet, not everything is black and white and, in a way, it also has to do with the content we have reviewed in depth with your help.

That is why , this is vital give the green light, if the way to benefit from these new functionalities is using FIORI to use this functionality, instead of reading data from an extension ledger that it no longer supports the use of KE24 or KE30 transactions so Welcome the many new functionalities in S/4!

One last recommendation, Is there any other query CDS similar to "2CCFIMARKSEGMQ2501,2CCFIPNLPLNACTCMT, 2CCFIPROFLOSSQ2901" in which I can show the results by ledger in Fiori, than use KE24 and KE30 ?

Thank you very much in advance

Best regards

[gianluca_taccone · Accepted solution]

Hello Gustavo,

Martin never mentioned anything about COPA and extension ledger, but in his blog he talked about predictive ledger for incoming sales orders. The same is done in the SAP PRESS blog post.

Now you can object that a Predictive Ledger is still an extension ledger, but In my view you are doing something completely different from the prediction ledger concept. You are trying to post manual FI document on an extension ledger and see the result in KE30/KE24 in COPA. MArgin Analysis is based on ACDOCA while KE30 and KE24 are clearly not aligned with it. So you will be able to see these Extension Ledger manual postings in ACDOCA and in FIORI apps, try the Market Segment app F0943 for example or other apps in FIORI.

As said FIORI is a very important part of these new S/4HANA functionalities.

THanks
Best

Gianluca

[gustavo_hermozaazaldegui · Accepted solution]

Thank you very much for your valuable information Gianluca,

We must clarify that we relate the valuable information in the Extension Ledger that Martin commented on to the publication of SAP-PRESS as well as the title "Creating an Extensión Ledger for Profitability Analysis with SAP s4hana" and these have helped us to clarify doubts and with their valuable information we have been aligning

Yes, you are right, These are different topics. In fact, As you said, we were looking for a solution for the manual postings we do in COPA with ke21n , to move to the "Margin Analysis" approach and we thought it would be good to consider the possibility of using the "extension" option of the general ledger or general ledger 0L".

then, as we have checked in our evidences. MArgin Analysis is based on ACDOCA while KE30 and KE24 are clearly not aligned with it. That is, in our evidence for both cases it is not possible to show in ke24/ke30 these lines.

Accordingly, as you have indicated. We need to go the way you recommend.

Thank you very much for the clarification on these functionalities and for the information on FIORI where we have to go.

Best regards

Gustavo

[gianluca_taccone]

If you want to play with the ledger concept, I strongly suggest that you check reporting in FIORI or in ACDOCA directly, please be aware that some new margin analysis functionalities (e.g. Predictive accounting or other cases described here ) keep the ledger as a basic concept. Per my knowledge reading data from extension ledger is not supported by KE30.

[gustavo_hermozaazaldegui]

Thank you very much Gianluca for responding to my evidences.

we sincerely believe that your answer is giving green light to some doubts and it appears to be that both of us have coincided with the same post that you share with us.

Let us dive deeper into it and pin down the way forward:

I have checked the 3 extension ledger types and none create the document in profitability analysis account (KE24). At least with the Standard Journal Entries option it should create document in Profitability analysis account (KE24 or KE30) .

On another hand, we have ckeck this scope and for this reason from our humble opinion, we believe that it should working in v2022, ie, The system must display the document of the ke24 or ke30 transactions, for the following:

ie, ==> This should work in Classical SAP GUI reports as well

Account Based CO-PA I understand that it is based on the following points:

Ø Data is transferred when accounting document is posted to Financial Accounting

Ø Account based COPA Stores data in general CO tables, as below:

· Line item actual data in ACDOCA

· Line item plan data in ACDOCP

· Actual line item in COEP value type, not equal to 4 and not equal to 11

· Plan line item in COSP & COEJ specific value types

Ø Account based COPA will be innovation path always in S/4HANA. Since ACDOCA is the primary table in S/4HANA and account based COPA only update ACDOCA tables

In In fact, if we see the table acdoca or I_JOURNALENTRYITEMCUBE , in both of them, we can see the same lines. and this CDS is used in the fiori app according to the information in the following : Note OSS 2956071 Customer guide s4hana Margin Analysis.

[gustavo_hermozaazaldegui]

2

We must make clear that the lines in acdoca are correct but the system not shows this information in ke24 or ke30. It does not make sense and Martin in his post specifies that it is possible that the system use the classical way.

From our point of view and as Martin points out, the extension ledger should work in the classical way, because if not, How would it be explained to the customers that a part of the Profitability Analysis account (ke24 or ke30) would be displayed in s4hana in ke24 but the rest of the other lines would be displayed in fiori, this does not make sense.

[gustavo_hermozaazaldegui]

3

We have check your recommendations with regarding this option “Check and Define Default Values for Postings in Controlling”.

We have put 0L for our checking, the following:

Initial photo

[gustavo_hermozaazaldegui]

4

We have do a posting in L6: OK, the behavior is correct.

The system created object PA but in ke24 we don’t find anything.

[gustavo_hermozaazaldegui]

5

Now, we have done a posting in 0L, and this impact in all ledgers. it is a standard behavior.

We think you will agree with us from the evidence attached and as Martin points out it is needless to say that it should work in clasical way. We have also reviewed the information in the SAP PRESS Community and the expected result is that it will work for the ledger extension in profitability Analysis.

https://blog.sap-press.com/creating-an-extension-ledger-for-profitability-analysis-with-sap-s4hana-f...

We look forward to your recommendations as this is of the utmost importance to us.

Best regards

Gustavo

[gianluca_taccone]

Hello Gustavo,

with regards to the problem of writing from FI to COPA margin Analysis on different ledgers please read the help and reflect on this customizing

So I strongly suggest to analyze this customizing and then execute your tests again.

Moreover Margin Analysis writes in ACDOCA, so postings may be analyzed in FIORI for example the market segment app. In alternative you can check ACDOCA .

Please also reflect on the difference between ledger and ledger group cause they are not the same concept if your Ledger Group Contains only Ledger 0L why are you expecting to have postings on Ledger L6?

If you open an incident on these questions, the reply you will receive is that this is a consulting issue.

[gustavo_hermozaazaldegui]

1

Dear SAP Expert, Gianluca.

Yes, we have checked this behavior before that we have created an “extension ledger” for profitability analysis as we have commented above. This is the behaviour that we are reporting that is not working, i.e. what we are posting to the L6 ledger defined as an extension ledger does not create a document in margin analysis with its values.

We must make clear that this confirm to us ==> If you do not enter a default ledger group, all CO postings will be done to all G/L ledgers.

On the other hand, in response to your comment, according to the information reviewed and the requested business requirements so we expect that in our s4hana version 2022, the system should create in our COPA(Margin Analysis) the documents with their values. ¿Is it possible or not?

Regarding your difference between ledger and ledger group, yes you are right, they are not the same concept but we don't want our L6 to contain the 0L. In fact, if we look at the thread of information reported sequentially, we can see that we did it to show that the linking of the extension ledger with the 0L as representative, is when the system has been able to generate the CO document and the COPA document, and obviously this result is not what we expect. We believe that you agree with us.

Let us dive deeper into it and let us know if we something missing on this issue.

We have the following ledger.

Next

[gustavo_hermozaazaldegui]

As Ledger group we have the following:

In 0L we have the following.

next

[gustavo_hermozaazaldegui]

next 3

In L6 We have the following:

Then,

1. if the L6 ledger is not created as L6 group, when you will do a posting the system shows you the message “Ledger group L6 does not contain any ledgers - Message No. FAGL_LEDGER_CUST004” Therefore: the system does not generate a co document and COPA document, same behaviour if it is created as a ledger group.

2. let's go to the recommended option that you commented to us. Please don’t forget that our L6 is an extension ledger and “Underluning ledger is 0L”. Why do we need to include the 0L ledger to the L6 extension ledger? It does not make sense.

3. As you have been able to observe the ledger "0L" as a group you have the same as "0L", es decir, when you will do a posting in ledger 0L, thas mean that all post reflect in all ledger.

4. as we understand without a doubt whatsoever, this is not a consulting issue, this is an incorrect behavior.

Furthermore, we want any company code to be able to use all --> 0L, L1, L2, L3, L6 ledgers. Obviously what was posted in each ledger l1, l2, l3 defined as a standard ledger will remain in its ledger and the Extension ledger L6 ( that system create the document in COPA (Margin analysis) but this is not working. Do you have any notes that solve this behavior regarding the extension ledger for profitability analysis?
All suggestions are welcome!!!
Best regardsGustavo

[gustavo_hermozaazaldegui]

1.

Dear Sap Expert, Gianluca,

Additionality i would like to add more think with regarding the behavior about "Extension Ledger"

We understand if we post a document in leading ledger 0L, it won’t be posted in extension ledger L6. Likewise, if we post a document in extension ledger L6, it won’t be posted in leading ledger 0L.

Obviously an extension ledger can’t live on its own; it always references a standard ledger because The extension ledger inherits the basic settings of the underlying ledger from 0L.

We believe that you are agree with this behavior commented above because it is a "Extension ledger".

Let me share with you the following results:

Transaction : s_ebs_44000137.

We have the following initial photo:

We posted a document in L6 “Extension ledger” with 100,00 €. This behavior is perfect as we have commented above., ie: if we post a document in extension ledger L6, it won’t be posted in leading ledger 0L.

Let me share the result from 0L transaction F.01. This behavior is correct because if we run a “P&L” and “balance sheet” reports for leading ledger 0L, we ’ll only see documents that are posted in leading ledger 0L.

next..

[gustavo_hermozaazaldegui]

2

F.01 Transaction. This is correct.

Profitability Analysis from KE24 transaction . This is correct

Let me share the result from L6 Extension ledger transaction F.01.

However, when we run a “P&L” and “balance sheet” reports for extension ledger “L6”. We only see postings from our extension ledger L6. This is strange because I believe that a Extension ledger is different than a Standard Ledger

next..

[gustavo_hermozaazaldegui]

3

but we have nothing in Profitability Analysis (KE24). We need to see the 8.630,00 €.

next

[gustavo_hermozaazaldegui]

4

Now, let me share the following result when we have done a post in 0L à 50€

Following the approach of the “Extended ledger”, we have understood that if we post a document in leading ledger 0L, it won’t be posted in extension ledger L6.

It appears to be that the amount is added to both ledger, ie: be it an “extension ledger” or a “standard ledger”.

Let me share the result from 0L transaction F.01. This behavior is correct.

next

[gustavo_hermozaazaldegui]

5

KE24 transaction. This behavior is correct.

Let me share the result from L6 transaction F.01. However, it has also posted in extension ledger L6.

next

[gustavo_hermozaazaldegui]

7

But, in the profit and loss account - transaction KE24. We have an unbalance of € 8.680,00.

From my point of view, I think, when we run a "P&L" and "balance sheet" reports for extension ledger L6, we should see both postings from leading ledger 0L and extension ledger L6.

In consequence, we have checked different blogs about this topic and the behavior when we post a document in our extension ledger "L6" for "Profitability Analysis". In our system s4hana v2022, we have observed that in COPA it is not working.

For this reason we believe that this is a correct incidence.

Could you recommend any suggestions on how to correct this behavior?

Thank you very much in advance for your answer, it has sincerely helped me to go deeper into the subject, but now we need your collaboration on this solution

I hope that the evidence will help to find the light and find out where the challenge is.

Best regards

Gustavo

[gustavo_hermozaazaldegui]

Dear Sap

Do we have to open an Incidencit to SAP to review this behaviour the above commented ? All suggestions are welcome!!!

Gustavo