cancel
Showing results for 
Search instead for 
Did you mean: 

Smartform is displayed in Print Preview but error "document saved but no accounting document generated" Routine not found in driver program in VF03

Former Member
0 Kudos

Hello Experts,

In VF03, when i add a custom output type (eg. ZAAA) and save it, i can display the smartform in print preview but when i enter go to Further Data (Goto->Header->Output->ZAAA->Further Data->Dispatch Time: Send Immediately (when saving the application)) i get the following error message in the processing log:

Green-> Object 999999999

Green-> Output type: Invoice

Green-> Processing log for program ZXXX routine ENTRY

Red   -> Processing routine ENTRY in program ZXXX does not exist

Actually the driver program used (ZXXX) is copy of the standard program RLB_INVOICE.

Can you please help/advise as to how to find the solution for this error?

Actions i took:

I have checked the configuration for this output type in NACE and its good.

I have inserted a break point in the custom driver program but debugging is only triggered when doing print preview and not when processing the output type in the transaction VF03/VF02

Yet, i do not find clues as to where the problem is arising.

Please help.

Thank you in advance

Regards,

Thyaga

Accepted Solutions (1)

Accepted Solutions (1)

Sijin_Chandran
Active Contributor
0 Kudos

Hi Thyagaraja ,

Click on ReleaseToAccounting button to check the error for Accounting Document not being generated.

Former Member
0 Kudos

Hello Sijin,

When i clicked on ReleaseToAccouting, i got the following error message:

"Cost center 999999 in controlling area AAAA is locked for revenue postings on 08.08.2012."

Should this be a program when processing the output in VF03?

Thank you

Regards,

Thyaga

Sijin_Chandran
Active Contributor
0 Kudos

Hi Thyaga ,

This issue can be solved by a Functional Guy.

Sijin_Chandran
Active Contributor
0 Kudos

Hi Thyaga ,

This issue can be solved by a Functional Guy.

Former Member
0 Kudos

Dear Thyagaraja Yenketeramdoo

Exactly....you are on the rite place, this error is not any routine, your posting  period is block for posting and hence you are not able to post the document and which result in error.

Kindly consult with your FI/CO Consultant  and ask him to open the period hence you can proceed further.

Thanking you!

Ashish Mishra

Answers (2)

Answers (2)

Former Member
0 Kudos

Dear Thyagaraja Yenketeramdoo

In VF03, when i add a custom output type (eg. ZAAA) and save it

I don't think you can insert output type manually in VF03.

As Sugested by Sijin Sij is the best way to get the details of the error and there you can check with the same why error is coming. There many be accounting or something else like cost centre error, please resolve the error and do the printing it will happen.

Try this ...will solve your issue.

Thanking you!

Ashish Mishra

Former Member
0 Kudos

Hello Ashish and Sijin,

Thank you for your prompt responses.

I will ask the function guy on this.

Thank you very much

Thyaga

vinoth_aruldass
Contributor
0 Kudos

check the form entry code in your driver program ,

i mean to say compare the form declaration with your standard program.

Because driver program will execute from form entry only.

for ex:

FORM entry USING return_code us_screen.



  CLEAR retcode.

  xscreen = us_screen.

  PERFORM processing USING us_screen.

  CASE retcode.

    WHEN 0.

      return_code = 0.

    WHEN 3.

      return_code = 3.

    WHEN OTHERS.

      return_code = 1.

  ENDCASE.



ENDFORM.                    "ENTRY

it should be presented in your driver program.

Former Member
0 Kudos

Hello Vinoth,

I compared the custom driver program with the standard one and the only place I see a difference is this:

CLEAR retcode.


  xscreen = us_screen.


  PERFORM processing USING us_screen.


  CASE retcode.


    WHEN 0.


      return_code = 0.


    WHEN 3.


      return_code = 3.


    WHEN OTHERS.


      return_code = 1.


  ENDCASE.

I commented the code above and added codes of my own.  Do you think this could be the problem?

Thanks

Thyaga