Hi Ahmad,
Are you sure system has posted entry in the GL? Check any changes have been done in account determination and also let me know have you maintained account determination based on CO.transaction? However, you can also check the accounting document from the controlling document, check in this way to identify correct posting for it.
Regards,
Mukthar
Sir,
Please see the screen shot it is ksv5
Hi Ahmad,
Yes, it is CO-FI integration document. Here I want to correct that the system will post with the same cost element, if you done distribution to primary cost element in CO-FI posting. If you done with secondary cost element posting i.e.assessment,confirmation etc., it will post with GL account which you defined in OK17 account determination .
Regards,
Mukthar
SIr,
Why the entries in FI are posted in primary cost element. Can we stop these entries to post in FI and restrict them to co only .
Hi Ahmad,
You cannot restrict it. Because the CO-FI integration activation to all applicable for all CO transactions.
Regards,
Mukthar
Hi everyone,
I really would like to thanks everyone that waste your time trying help me in this issue.. How I have said, I open an incidente to SAP and the program error was fixed by this note that SAP delivered last week:
Note: 2153853
This note solved the problem!
I hope it help other that face this same issue!!!
Thanks again!
Hi Srinivas,
Please refer the OSS note that explains the cause and possible solution http://service.sap.com/sap/support/notes/1521506
This detailed explanation note released yesterday only :-). hope this address your issue.
Thank you,
Srinath
If a customer is using CBCOPA today in EHP7 and has agreed to start using ABCOPA in SFin/SCORE. Is it possible to migrate the historical CBCOPA data to new ABCOPA or ABCOPA will start afresh in SFIN/SCORE ? This means customer loses the comparison with previous year
Dear Friends,
Our clients getting the error while running a variance calculation for the previous period process order.
Costing have been run for the currently date only before that they done the couple of order have been cleated for the last period without costing run.
Now we can run variance calculation for the order system display the error as below.
“Cannot calculate the scrap variance “” only remaining var in version &no target cost for order.”
Kindly suggest me how to solve the issue.
Thanks &Regards,
Sabhapathy R
Hi, if you are getting this error only for previous period order, it is related to missing standard cost issue only. You can perform a small quantity of GR in current period (use the posting date from when the released cost is available) and recalculate the variances with the correct status of the order (DLV or Teco). That would fix your issue.
The other option is, you can also reverse all your GR and repost them in current period with the released standards.That way also you will not see any missing target costs errors that might be also resulting "cannot calculate variances" error.
If this error is wide open for all the order, then you need to check if the scrap variance is flagged for variance variant in OKVG.
Thank you,
Srinath
HI Srinath ! Thanks for quick response and appreciate your immediate update . I dont have access to OSS . Actually I am using IDES . Can you please elaborate about the note. Tq
Yes, price is maintained 460 EUR.
For 453, in OMJJ, account grouping is set to GBB - VAX acct modif hence posting to COGS acct.
Reason for this, I do not know.
Can you suggest correct settings for mvt 453?
Hi Experts,
We are facing one issue of Total Actual Cost becoming zero for Production Order containing work centers for which cost centers were changed.
Can anybody explain what is the reason for this and how to eliminate this issue?
Hi friends,
WhenI am uploading the MT940 file I am facing the issue
Error :- Account SBIXXX SBIXXXX
USD: Statement XXXXXXXXX is not in the bank data storage
Thank & Regard
Ravi
Hello
Thanks for the reply.
I already go through with the note. This is for the order Category 30 (Maintenance order) .
And I hope this is not applicable for the order category 10 (PP order).
Any suggestion please.
Regards
SS
Thats right!!
Please close the thread, if resolved
Hi Suhas
Did you maintain activity price in KP26?
Try to cancel your confirmations and do again
Ajay M
HI ,
THisis means your External Transaction N495 is not configured for EBS posting . go to OT83 and to the mapping of N495 .
THis is transportable configure . you need to in your development client and transport through LIve after testing in each client ,
