Inversions at posting level 20

Hi Greg,
i like the look of your blog and I will read it when I get some more time (probably after my current project).
At first glance I have a question for you, why would the following impact the I/S?
Dr intercompany payable                110
Cr intercompany receivable            100
Cr intercompany netting                  10
(I assume that yourfor a payables/receviables elimination your IC difference account (intercompany netting) would be in the Balance Sheet).
However, I accept that the same example with IC Income v IC expense would cause the impact on Retained earnigns prior year at year end.
This is a good reason make sure that IC is reviewed at year end, especially where the amounts are considered "material".
I haven't read the whole example yet but surely regardless of whether the IC is matched before year end or after year end, the net reserves (prior year + current year) will be correct?

Hi Greg,
I have the same question as TheScotsman: why you consider impact on I/S of such entries (and their reversals) as A/R - A/P?
Impact (during posting and during inversion) may be considered in my example from the other recent discussion:
Depreciation accrual (B/S) - Depreciation expense (I/S)
i'm not sure how my eliminations from prior year "disappear" and don't get inverted with the the new FY.
May happen if you used (or configured and do not use) special periods (13-16 for K4 FYV). Inversion might be scheduled in one of this special periods in which you didin't run period inizialization.
i also have doubts on netting as it may contain more than actual float. e.g. foreign exchange translation difference.
This C/T difference is a part of the real difference in GC.

Similar Messages

Document type with posting level 12 not being carryforward

Hi gurus,
We are now implementing SEM-BCS 6.0 in the BI 7.0 server.
We have a document type u201CMIu201D which properties are:
Posting level: 12
Balance check: 0 error when balance note equal to zero
Application: Other
Posting: Manual posting
Inversion: No automatic inversion
The problem is that when we execute the Balance Carryforward in the subsequent year this is the only document type that is not being carryforward.
Why is this happening?
Thanks for your help.
Best regards.

This is by design
http://help.sap.com/saphelp_erp60_sp/helpdata/en/0c/ab0240536fe369e10000000a155106/content.htm
"Data records for preparatory postings for consolidation group changes are neither translated nor carried forward."
I'll try an example...
Company A is sold from company 1 to company 2 in June (EoP)
For periods 0 - 6:
BCS reports company A's balance sheet under company 1
BCS reports company A's income statement under company 1
starting period 7
BCS reports company A's balance sheet under company 2
BCS reports company A's 0 - 6 income statement under company 1
BCS reports company A's 7 income statement under company 2
this is managed through the posting level 02 12 and 22 document types, as well as PL30 if using CoI.
Assuming the period of first consolidation and period of divestiture were set correctly in the groups for company 1 and company 2, BCS wants to read all 0 - 6 data under group 1 and all 7 + data under group 2. This is obviously incorrect from an accounting standpoint and the PCC postings correct that.
So BCS books a PL02/12/22 in group 1 to zero out the balance sheet. It then books another set of entries in group 2 to write up the entire balance sheet in the new group.
However, once you get to the end of the year and run your BCF, the entire balance sheet is now sitting in period 0. The system is able to report company A's balance sheet under group 2 withou the aid of the PCC documents. Therefore, the system does not roll these documents forward into the new year.
The PCC documents were only required because of the periodic nature of the BCS data storage vs. the LTD nature of the balance sheet for reporting. Once the full LTD balance is available in a single period, as is the case just after a BCF, the PCC documents are no longer required.
Anyway, hope that made some sense. If not, I'd encourange you to create an Excel sheet replicating how BCS stores the data in the cube, perfrom a divestiture, and see why the system is not carrying forward the documents. This is how I came to understand it.
Now, if you're doing something "non-standard" with the PL12, all bets are off
Good luck,
Chris

Error when select posting level in document type

Hi,
Did anyone have an experience to face the Abab run time error when select "posting level" in document type?
The Error is : GETWA_NOT_ASSIGNED
Short text
Field symbol has not yet been assigned.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_UC_ITKEY_FACTORY===========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.

If you searched the notes, as Dan proposed (and didn't find anything relevant), and the answer to the Greg's question is positive, then I would suggest regeneration data basis and ConsArea due to data model inconsistency.
If it doesn't not help - open customer message to SAP.
Edited by: Eugene Khusainov on Jan 26, 2010 10:26 AM

Copy data posting level 20 - 30 is not allowed SEM BCS

Hi expert,
We need to copy data from a version to another version, is very
important for us to import documents with posting level 20/30. Copy
task is only used for documents with posting level 01 - 10. But, in EC - CS we could to execute the copy program for this kind of documents,
and we are migrating from Ec-cs to SEM BCS so, we need to keep the same
funcionality.
Any idea in order to solve it? Badi´s? user exits?
Thanks in advance,
Beatriz Bernardos

Hi
It is not possible to copy data at posting level 20 and 30 as they are group entries.
Logically, it should not allow one to copy the entry at posting level 20 and 30.
SAP doesnt support copying data at posting level 20 and 30.
I had same kind of requirement in all of my BCS project but I believe logically it is not correct to copy group level entry.
Alterntively, what you can do is,
create export datasource to load the data back into BCS integration cube from BCS total records virtual cube by changing posting level 20/30 to 01 or 10 in the update rule.
It still believe it will give you the wrong result in the report.
Please have a common understanding with customer that it is not possible copy posting level 20/30
Regards,
Manish

Reclasification in the posting level 00

Dear All,
I have 4 Item for cash pooling, one of theme is asset and one of the is liabilities, depands on balance.
Item_A and Item_AT - technical item as triger.
Item_L and item_LT - technical item as triger.
I have used reclasification with layout condition and steps. This metod is periodic not cumulative.
This reclasifiaction is use without a document in posting level 00.
In the first period there is a balance for item Item_AT: 500 EUR.
I have used a reclasification:
Triger: Item_AT
Source item: Item_AT
Targer item: Item_A.
Result in my databasis:
Item_AT: DT: 500
               CT: -500
Item_A: 500.
In the second period there is balance for item Item_AT: 1600 EUR.
Triger: 1600 EUR.
Source item: item_AT
Target item: item_A.
Result in my databasis:
Item                               I period                                          II period
Item_AT                          0                                                       0
Item_A                            500                                                   1600.
When I call up my report, there is 2100 EUR balance for item Item_A.
I would likt to what is wrong? Why does the system displays wrong balance in II period?
Thank you in advance for your help.
Best reagrds,
anka

Questions which have no feedback from the topic starter, not even simple thanks, regardless of answers given, right? Systematically?
This forum works not for the sake of such mute questioners. It's mainly for education of another contributors who would want to know if the answer given was useful. With no feedback such a topic has no good for a community. So, I prefer to ignore such questions and questioners.
Edited by: Eugene Khusainov on Aug 24, 2010 11:48 PM

Reclassification of MI at posting level 30

Hi Experts
I need some help to clarify the behaviour of a stantard reclasification at posting level 30, we have the following group hierarchy (G1-G3
are groups and C1-C6 are companies)
G1
u2514u2500u2500C1 <---Parent Unit
u2514u2500u2500C2
u2514u2500u2500G2
     u2514u2500u2500C3 <---Parent Unit
     u2514u2500u2500C4
     u2514u2500u2500G3
         u2514u2500u2500C5 <---Parent Unit
      u2514u2500u2500C6
C1 has investments in C2 and C3
C3 has investments in C4 and C5
C5 has investments in C6
We use consolidation of investments and make additional reclasifications reading the posting level 30 information generated from the COI
task for the following purpose:
Most of the Minority Interest that comes from the Equity Accounts needs to be generated with group shares, but only 2 equity accounts need
to generate MI with direct shares, but the accounting technique can only be assigned only per method and per company, not for each account.
For that we created a standard reclasification that cancels the postings that affect those two equity accounts against the MI account and
Example:
C1 has 90% share in C3
C2 has 80% share in C5
C5 has 100% share in C6
At G1 level the group share for C6 is 72%
C6's equity is composed of
Common stock (CS)           5000.00 <----direct share (this according to local GAAP)
Reserve     (RS)               2000.00 <----group share
Retained Earnings (RE)           3000.00 <----group share
The postings for MI for each group are:
Document Type: I1
Group     Company          Account          Amount
G2     C6          CS          -1000.00
G2     C6          RS           -400.00
G2     C6          RE           -600.00
G2     C6          MI           2000.00
G1     C6          CS           -400.00
G1     C6          RS           -160.00
G1     C6          RE           -240.00
G1     C6          MI            800.00
The reclassification we want is for canceling the postings for the CS account to the MI account considering that the postings that generate
the MI with group share are those that are located at upper level groups (in this example there is no MI at G3 group):
Group     Company          Account          Amount
G2     C6          CS           1000.00 <---Step 1 in method
G2     C6          MI          -1000.00 <---Step 1 in method
G1     C6          CS            400.00 <---Step 2 in method
G1     C6          MI           -400.00 <---Step 2 in method
The configuration for each step in the Reclassification method is the following
Step 1:
               Trigger               Source               Target
Item               CS               CS               MI
Company               C6               ---               ---
Cons Group          G2               G2               G2
Document Type          I1               ---               ---
Step 2:
               Trigger               Source               Target
Item               CS               CS               MI
Company               C6               ---               ---
Cons Group          G1               G1               G1
Document Type          I1               ---               ---
The group is important in the postings because we want to check in the consolidated financial statement the effects of MI in different
groups but when we do a reclassification the log show us that for the same step 1 the task generated a reclassification for group G1 and G2
first generating the correct reclassification in G2 but cancelling it in G1, so the postings look like this:
Group     Company          Account          Amount
G2     C6          CS           1000.00 <---Correct (Step 1)
G2     C6          MI          -1000.00 <---Correct (Step 1)
G1     C6          CS          -1000.00 <---Unexpected (Step 1)
G1     C6          MI           1000.00 <---Unexpected (Step 1)
G1     C6          CS            400.00 <---Correct (Step 2)
G1     C6          MI           -400.00 <---Correct (Step 2)
From G1 perspective the total MI is without the adjustment we want but from G2 perspective the MI is correct.
We decided to change step 1 to the following configuration for the purpose of correcting at least G1:
Step 1:
               Trigger               Source               Target
Item               CS               CS               MI
Company               C6               ---               ---
Cons Group          G2               G1               G1
Document Type          I1               ---               ---
It generates the following postings:
Group     Company          Account          Amount
G1     C6          CS           1000.00 <---Step 1 in method (not the group we expect)
G1     C6          MI          -1000.00 <---Step 1 in method (not the group we expect)
G1     C6          CS            400.00 <---Step 2 in method
G1     C6          MI           -400.00 <---Step 2 in method
This at least solves the problem from G1 perspective but for G2 we don't have a posting
Any lead on how to solve this problem is highly appreciated
Best Regards
Paul
Edited by: Paul Heredia on Oct 28, 2011 2:31 PM

Hi
I'm using this same thread to ask an important related question with the expectation of closing this thread, about the behaviour of a reclassification with a Posting Level 30, and Consolidation of investments application in the document type, why the reclassification task behaves like this when executing it at G1 level, if this is an unexpected behaviour I could send an OSS note to SAP, if this is expected, please explain why
Group
Company
Account
Amount
Comments
G2
C6
CS
1000.00
Expected from Step 1
G2
C6
MI
-1000.00
Expected from Step 1
G1
C6
CS
-1000.00
Unexpected and it is cancelling Step 1 at G1
G1
C6
MI
1000.00
Unexpected and it is cancelling Step 1 at G1
G1
C6
CS
400.00
Expected from Step 2
G1
C6
MI
-400.00
Expected from Step
One remark, for the unexpected postings there is no trigger value but strangely it generates a document...
We don't want to do this manually because it would require too much analysis and manual postings
Thanks in advance
Message was edited by: Paul Heredia (Just adding an important remark after the example)

Copy data of posting level greater 10 in EHP2

Dear all,
   We install EHP2 ( enhancement package 2 ) to our BCS.
   According to the document , we should be able to copy data with posting level >10.
   We are trying to copy data(all data types) from one group currency to another one.
   First ,we create a copy method with data type = All data types and with one currency translation method.
   We also create a copy task with that method.
   When we run the task, the system keep showing that :
=====================================================
Data stream for activity numbers is incomplete
Message no. UCF6884
Diagnosis
The data stream for activity numbers does not contain the Source System and Referenced Activity fields. Therefore, the system cannot store the link between the new activity number to be assigned and the activity number of the source.
System Response
The data cannot be copied or loaded.
Procedure
Add the missing fields to the data stream for activity numbers.
======================================================
There are two fields missing Source System and Referenced Activity.
But, I don't know where or which data model we should assign those two fields.
We try to add 0BCS_COINRR & 0LOGSYS to activity number DSO.
The system still shows that message.
Anyone knows how to make the copy work with posting level > 10?
Please advise .
Thx,
Jeff
Edited by: Jeff Huang on Sep 16, 2008 3:25 AM

Jeff, are you still havnig this problem?
- after we have implemented EHP2, I hope to copy PL20 and 30 too.
Please let me know if you have succeeded or have found a workaround

Upload functionality for Posting level 30

HI,
I have a situation where I need to post around 800 entries at every period at posting level 30.
Is there any options to upload the documnets, as it is very difficult and time consuming for posting manually.
Can any one suggest how to develop an upload method for posting level 30?
Thanks in Advance,
Richard

our basis team did it, once in each system, during a weekend/night when everyone else was locked out/inactive.
As you would expect, they activated function FIN_ACC_GROUP_CLOSE in Dev, then we tested it
Then when happy, we went to QA, user testing then Production
We had a transport freeze during this period but it did not take us long (eg under 1 week)
There is no requirement to perform any further activations, unless you want the next functionality (we did not need the next 2 functions yet)
If you want to activate the later functions, you must first activate the earlier functions
You can activate all of the functions at the same time (in the correct order) but you must perform testing and remember that you cannot undo the activation
NB for BCS there are only 3 functions for BCS (NB I don't know about EHP5 yet):
FIN_ACC_GROUP_CLOSE (available in EHP2)
FIN_ACC_GROUPCLOSE_2 (available in EHP3)
FIN_ACC_GC_TAXRATECHG (EHP4)
- So you would have a maximum of 3 activations per system, or you could activate all at once.
Once activated, all of the new configuration options in that function are available in the workbench

Posting level 01 and 10

Dear All,
How can I change automaticule posting level 01 into 10. I have a lof of documents with posting level 01 and when I execute task: balance forrward this posting level is changed in posting level 00. I cannot load data from SAP correctly to new period.
Is it possible to change posting level from 01 into 10 automaticle?
Please help me.
Thank you in advance for your help.
Regards,
anka

How can I change automaticule posting level 01 into 10. I have a lof of documents with posting level 01 and when I execute task: balance forrward this posting level is changed in posting level 00.
- PL 01 is dedicated mainly to correcting errors, especially by manual JE.It's a feature of the system that after BCF PL01 goes to PL00. Automatic postings (not eliminations and consolidations) usually use PL10.
I cannot load data from SAP correctly to new period.
- Why?
Is it possible to change posting level from 01 into 10 automaticle?
- AFAIK, only manually. By reassigning the doctype to another PL.

Reclassification - Posting Logic with Different Posting Levels

Hi *,
we've a reclassification task on posting level 30.
In SAP online help I've found the statement "The system includes all values of the triggering object(s) entered or posted with a posting level less than or equal to 30.". So I assume that also PL 12 and 22 is covered by our reclassification task. However, I've realized that the task doesn't consider postings on PL 12 or PL22. Within the SAP help I couldn't find a remark that cons group changes are exluded.
Does anyone know whether cons group changes have to be considered by the system?
Thanks in advance!
Daniel

Hi Daniel,
AFAIK, 00, 01, 10, 20 and 30 PLs are considered by the system in case of reclass on the PL 30.
PLs of cons groups changes ( 02, 12 and 22) are not considered.

Posting Level, Doc Type n Mvmt Type

Hi Gurus,
Many thanks for my earlier querry on TP. I have few more things to ask from you experts.
1. What is purpose of Posting Level and Document Type ? How they are different and where we can
create them ?
2. What is the function of Movement Type ? Where can we create the movement type ?
Best regards and many thanks to you in advance.
os

To Anurag Tambe.
A little hint: when you want to provide some links in help.sap.com, then just click on the little red left arrow that you see in the first, topic description. You'll arrive to the proper topis'c link. Instead of giving the link to the whole module, you'll have the precise link, like here:
http://help.sap.com/saphelp_sem60ep1/helpdata/en/3d/c77b3bf7975a03e10000000a114084/frameset.htm
To OS.
Additions to what Anurag Tambe said.
1). Posting levels allow the BCS' user to have information in the system segregated by its origin:
PL 00 - reported data, RFD (plus some changes entered by means of reclasses without document assigned).
PL 01 - some corection to RFD.
PL 10 - some transformation data (very often it's a transformation from a local legislation to GAAP ot IAS).
PL 20 - eliminations between pairs of companies.
PL 30 - entries related to Consolidation of Investments and elimination of unrealised profits in supply chain operations.
It's very useful. At any moment you may see the original (almost) RFD and all corrections/transformations/eliminations etc.
- Document types determine many features, like the PL, currency of the entry etc. etc. They also allow to assign special items to them. In this case you may overwrite the settings set on the system level and allow the system generating specific for the document entries.
2). Movement types is an additional analytic to the items that helps to recognise different types of data. Like Begining balance, increase, decrease etc. In general, interpretaion of the MoveTypes depends on you. You may introduce different types you need. They are to be created in the workbench.

Posting Level 01 documents allow cross company postings - unexpected

hi,
Previously users could not enter a PL01 document that crossed companies.
Now they can.
I had previously thought that this was not possible for PL01 but what is happening is
when they enter cross-company postings (2 lines, one each to a different cons unit)
the system creates 2 documents,
with 2 balancing entry lines (one to each unit) to the clearing item
- just as can happen when a PL20 or PL30 manual posting is to the same company but cross-profit centres.
So my question;
is this normal behaviour in BCS?
was this always possible but the users just hadn't achieved it until now
NB they are adamant that this was not possible previously, until the Support Packs were implemented sometime last year
Finally, is there a way to stop it from happening?

Concur with Dan.
Most likely, that you've met the 2nd case: the DocType with configured clearing ConsUnit was attached to manual entry task. It might be not easily seen. Just check it out and remove if find.
Edited by: Eugene Khusainov on Jan 28, 2010 11:13 PM

Issue Tracking Posting Level

The HCM team has approximately 650 issues logged for our 4.6C system (over a 3 year period). Our potential usage of the Solution Mgr issue logging will be quite extensive. We would like to have our issues logged at the Project level as well as the Solution level. The system allows for this type of logging. However, the available Issue report does not report in this fashion.
The HCM group would like to report and record issues at the Solution level based on the need to not always remember which project the issue is filed under. We then experimented with the Solution Reporting to test how issues would be picked using the selection screen provided.
Our results show that if an issue is reported at the Solution level it does not get displayed if a project is selected thru Solution reporting selection variant. The report selection criteria seems to be an "either or" meaning by project or by Solution but not both which we would see using.
We were wondering what the intent is or best practice recommendation for filing issues is. Solution level or Project level
Thanks in advance
Ron Taylor
TCDSB

Hi Benjamin,
The error can be caused by many reasons, so you need to check the ULS log for detailed error message.
For SharePoint 2010, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS.
In the meanwhile, you can clear the configuration cache for SharePoint to see if the issue still occurs.
To clear the configuration cache, please follow the link below:
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
Please also check if the issue is caused by the KB2844286 Security Update on SharePoint 2010 as Cameron suggested.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Inversion of postings at level 10

hi,
maybe itu2019s a simple question, but Iu2019m a bit confused about the inversion of document types at posting level 10. We do the following posting in period 12:
p/l-acc 100
balance-acc -100
Now I have the problem whether to use the inversion for the next year or not.
If I do, the result in period 1 of the following year is the following:
balance-acc -100 (carryforward)
balance-acc 100 (inversion)
p/l-acc 0 (carryforward)
p/l-acc 100 (inversion)
If I donu2019t invert the posting document, the result in period 1 of the following year is the following:
balance-acc -100 (carryforward)
p/l-acc 0 (carryforward)
No matter which setting I use, I only see three possible solutions:
1.     Carrying forward all p/l-accounts and inverting the posting document
2.     Not using the inversion and doing a new (balance- or p/l-)manual posting in period 1 of the new year
3.     Not mixing up balance and p/l-accounts in one posting
All three options are not really satisfying u2013 maybe you have some other suggestions? It would be really great!
Thanks,
B

Hi BickBee and welcome to SDN.
Actually mixing up with B/S and P&L items is a usual thing in accounting and SEM-BCS. In order to balance FS reports (B/S and P&L) the system the system uses special (clearing) items.
Journal entries in your case will look like follows:
P&L -> 100
P&L Clearing -> -100
B/S -> -100
B/S Clearing (= CY R/E) -> 100
After BCF we have:
P&L -> 0
P&L Clearing -> 0
B/S -> -100
B/S Clearing goes to Prev Year R/E -> 100
And, finally, after inversion:
P&L -> -100
P&L Clearing -> 100
B/S -> 100
B/S Clearing -> -100 (will appear during inversion)
Prev Year R/E -> 100
Taking into account that P&L Clearing is an artificial (not accounting) item we got additional income in P&L, right? However, from accounting point of view we also got additional CY R/E in B/S. Which is right.
Considering also that P&L items are usually not BCFed, the situation you faced looks for me like a methodological problem.
Proposed solution: do not invert these J/Es. Actually, shouldn't be such entries. Could you give us more info, what kind of entries you have?
P.S. Your proposed slution #2 will not work at all. - You'll not be able to break consistensy between R/E in B/S and NI in P&L (if not to do it by 1-sided reclass without DocType).

Manual posting at level 20 - number of lines available in cons monitor

Hello,
I have a question concerning manual postings. We have created a document type and a task for manual postings connected to intercompany eliminations (posting level 20). In the monitor, the users only have 10 lines available for the manual posting and I have not been able to figure out how to increase the number of lines. Has anyone else been able to get more than 10 lines, or is that a limit?
Thanks in advance!
Kerstin

Well, that would be great - but I tested it and I couldn´t make it work? I will try this with my customer again tomorrow, if we can´t make it work I hope it´s OK if I get back to with a follow-up question?
Kind Regards,
Kerstin

Inversions at posting level 20

Similar Messages

Maybe you are looking for