2012 Jan 31 2:32 PM
HI everybody,
I am uploading the data and creating the PO through BAPI, and the PO is getting created. when i logged into ME23N and checking the PO it is everything fine without any error.
But when i click on the message button and checking the display PO output is giving an error message over as Incorrectly processed and when i check the processing log i am seeing the msg text as error in the address output.
and i checked the NACE transaction the output type is configured with program name, form routine name, form name and smartform name.
here in the form name and the smartform name which is present is having the different name and both are the smartforms only.
Can any one help me out in this issue how to resolve the error.
Thanks in advance
2012 Jan 31 3:24 PM
Hi,
Please check for condition records for the respective Output type which gets determined as soon as the PO get created
Thanks & Regards
Suresh Krishnan
2012 Jan 31 3:24 PM
Hi,
Please check for condition records for the respective Output type which gets determined as soon as the PO get created
Thanks & Regards
Suresh Krishnan
2012 Jan 31 5:10 PM
Hi Suresh,
we have checked those thing and everything is customized, and also if possible can you let me how can i debug the smartform while i am uploading the data from the Z prog so that if der is any problem in the smartform that might be fixed for this issue or still there is any other setting to over come this issue.
Thanks in advance
2012 Jan 31 5:14 PM
The error is im the smartform window. You can manually go into po and create new message with option sending data via job option. After that go to rsnast00 and process it. Before that pls put your breakpoint in the driver program sub routine
Nabheet
2012 Feb 02 8:27 AM
Hi,
Check the TNAPR Table by putting the Form Name / Program Name to find out the output type it is attached to.
Debug
The other method of checking is by setting up a break-point at smartform and manually entering a PO using the same upload data and try to save it. But this would not help you much. Because the root cause is the Determination of output type.
Thanks & Regards
Suresh Nair
2012 Jan 31 9:18 PM
keep a break point in the driver program and come tome23n, open the PO, and click print preview. debugger will trigger. now check whats going wrong.