Need clarification on Reconcilation Key

[Former Member]

Hi exports,

We have closed the Recon Key and tried to transport the same to GL through FPG1. While transporting the same we are facing the error. Then we identify that one customization was missed. So we did that customizations and transported the TR into production. After transported the TR again we tried to transport the Recon key through FPG1 and it is giving the same error,.

After doing the customization changes, for testing we have created a same scenario and posted the document and closed the R.Key and transported successfully. But we are not able to transport the old R.key.

Please guide me why i am not able to transport the old Recon key and why it is giving same error after making changes also.

Thanks in advance

Regards,

Srinivas

[kandarpa_anand]

Srinivas..

What is the Error? can you please copy the error message in the forum....

Cheers,

Anand.Kandarpa

[Former Member]

Please fid the attached document....

Thanks in advance.

[kandarpa_anand]

Srinivas.

Please check the Note 159850 - Settlement within a project.

Looks like an issue with your WBS element

http://scn.sap.com/message/7542878#7542878

Hope this helps your issue.

Thanks

Anand

[Former Member]

Hello Anand,

i have checked the above link, that is different issue for PS i think.

Regards

Srinivas

[kandarpa_anand]

Srinivas,

Please check WBS element o/5d12r00018-01 using the Tcode CJ30. it looks like the WBS elements which is in the line items 002 has exceed the budget.

looks lie an issue with availability control

Anand

Message was edited by: Kandarpa Anand

[AmlanBanerjee · Accepted solution]

Hi Srinivas,

The fix that you have sent will ensure that the error does not come going forward.

However, since the reconciliation key contains the transaction data which has already been posted before the fix went in, so this backlog entry will not get changed automatically.

To fix the issue, you have the following options-

(a) Take a note of all the documents that you have posted in the reconciliation key.

     Now reverse the reconciliation key through transaction code FP08M.

      Once you have reversed that, try to post the documents again.

      This time you will see that the new WBS element is coming in the transactions.

     Close it and post it to GL.

(b) Technically, you need to correct the entries in table DFKKSUM for each of the line items for the reconciliation key and the company code.

     So you can develop a custom program which would update the WBS element with the new entry in table DFKKSUM for the particular reconciliation            key.Once done, then try to post it to GL.

Hope it helps

Thanks,

Amlan

[Former Member]

Hi Amlan,

Let me say thanks 1^st for your golden solution.

I have checked the scenario in DEV server by changing the DFKKSUM Changing the standard table manually and I got the solution also. But as per my knowledge changing the S.table manually is not suggestible as per SAP policy.

So please confirm whether we can change the table or not. If we change there will be no problem in future right.

Many many Thanks

Regards,

Srinivas

[AmlanBanerjee]

Hi Srinivas,

Option (b) only comes into play,  if the entries are huge and if your only concern is sending it to ECC and you will not perform any activity on the reconciliation key (like reversal etc.) once its transferred to GL, then you can develop a custom program which would update the WBS element field against the particular reconciliation key in DFKKSUM table.

This would only ensure that the reconciliation key will be transferred to FI-GL.

I would go for option (a) to reverse the recon. key and re-post the entries in a standard way

Hope it clarifies.

Thanks,

Amlan

[Former Member]

Hello Amlan,

Thanks for your valuable inputs.

Thank you very very much….

And i have a another Issue, if you have round kindly go with below link.

http://scn.sap.com/thread/3361272

Thanks in advance

Regards,

Srinivas