cancel
Showing results for 
Search instead for 
Did you mean: 

No CO document is created after proceeding down payments

Former Member
0 Kudos

Hello, we faced this kind of problem.

After creating the down payment (F-48) no CO document is created. However FI document is created succesfully in BSEG table. Although if we delete default cost element in OKEP it shows a mistake. The problem occured recently, month ago everything was ok, so as we think the reason is recent changes in CO area or BASIS.

Already did these steps

  • New support packages haven't been installed recently;
  • We tried to procced down payments with exactly the same steps that were succesfull month ago;
  • In Okep default cost element is defined;
  • Cost element is type 1 and avaliable till 9999 year;
  • These note is implemented 388843 and many others also checked.

Did any one had such problem before? Any reply would be helpful.

Accepted Solutions (0)

Answers (2)

Answers (2)

varshal_kachole3
Active Contributor
0 Kudos

Hi,

Recommendation would to raise it with SAP via an Incident. Please let us all know the findings by SAP.

Thanks and Regards,

Varshal Kachole

kamalkumar_biswas2
Active Contributor
0 Kudos

Hi

Have you checked your CE defined OKEP...is there any change in CE level ...because generally CE is not assigned for down payment if not required to capture in CO...down payment is a purely financial transaction..

In think the link of error is CE

Former Member
0 Kudos

May be. Can i ask you to be more specific. Which settings in OKKP can affect this?

former_member198650
Active Contributor
0 Kudos

Hi Kir,

Earlier you might be not implemented project system. Due to this it was not throwing any error message. Now the PS has implemented and due to this it is asking for cost element. So assign a cost element in OKEP.

Regards,

Mukthar

Former Member
0 Kudos

PS was implemented long long ago, nothing to do with that. As i already said

  • In Okep default cost element is defined;

We redifened it several times. No use.

Paulo_Vitoriano
Active Contributor
0 Kudos

Just debug it with a good ABAPer to find out the reason.

Check number range for KAZO, but should be ok, otherwise you would get an error message.

Check that GL account in CoA has all account assignments open, but not defined for Company Code.

Also you can debug from a breakpoint where there is an error message once you remove OKEP definition, to make sure you are closer to CO document posting subprogram.