on 12-18-2012 5:29 AM
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.