2014 Nov 25 9:48 AM
Hi All,
I had done BDC for updating excise invoice after GR using transactions J1IEX_C, J1I5 and J1IEX_P. The program is working fine when I execute it but the problem appears when the user executes. For him he is getting blocked by an information message' J_1IEXDYNPRO-EXYEAR' does not exist in screen SAPJ1IEX 0001'. I am confused when I execute why I am not getting this error and I am able to post the excise invoice. Because of this error he is not able to post the excise invoice. This error is appearing for him in transaction J1IEX_P. Somebody please help its very urgent.
Thanks in advance,
Priya
2014 Nov 25 10:40 AM
You can try and ask the user to record screenshots as he goes through the transaction then oyu can see what he is entering that is different to you.
Also, I would recommend doing the recording for your bdc again, but this time with the “simulate background” button checked.
2014 Nov 25 10:34 AM
hi priya,
try to execute by logging in with the user on the same same system (where recording done).
2014 Nov 25 10:54 AM
2014 Nov 25 10:38 AM
Hi,
That's a very common type of error to get in BDC. It means that the session has gone to an unexpected screen, and that EXYEAR field (therefore) does not exist there.
Sometimes different screen sequences occur when you execute in the background. For example, if a PID is not populated, or a user default is not filled in. You just have to step through the BDC execution to find the issue.
This is why hardly anyone uses BDC any more. (I wish ) Use BAPIs - they have none of these problems.
cheers
Paul
2014 Nov 25 10:54 AM
Hi Paul,
Thanks for your reply. I am also trying to avoid BDC's but there is no option for capturing and updating excise details after GR. There is no BAPi for updating excise data. Please do you know any other methods to update excise. Because if I am using BDC these kind of errors will always popup.
Thanks,
Priya
2014 Nov 25 10:40 AM
You can try and ask the user to record screenshots as he goes through the transaction then oyu can see what he is entering that is different to you.
Also, I would recommend doing the recording for your bdc again, but this time with the “simulate background” button checked.
2014 Nov 25 10:49 AM
Hi Priya,
In BDC you might be calling a transaction and you might have missed to skip the initial screen by passing all the mandatory values on the selection screen and In this kind of situation the bdc program might got stuck at the initial screen , one more important point to make a note that in background tasks you cannot call any screen or transactions which require user interaction, so make sure or modify the BDC program in such way that the initial screen is skipped . Also make sure the standard task in which you are calling this BDC program should be aasynchronous background task.
This is the reason why when you make it as a foreground task it might be working.
Hope this might help you!
2014 Nov 25 11:11 AM
Hi Bharani,
Thanks for your reply. Now I am using the BDC based on 'LOCAL' update mode. Will this cause any problem. I had recorded the BDC in 'LOCAL' update mode for transactions J1IEX_C and J1I5 and its working fine. Do I need to change to 'ASYNCHRONOUS' update mode.
Thanks,
Priya
2014 Nov 25 11:15 AM
better try for the condition to Asynchronous mode and check by login directly inside ur system using client details and check for the output
2014 Nov 25 10:50 AM
Hi,
As mentioned, check any specific configurations/settings in parameters, which can be varied depending on user.
2014 Nov 25 11:08 AM
2014 Nov 25 11:01 AM
Hi Priya,
Please use the follwing syntax if you are using call transaction method,
Data: wa_opt type CTU_PARAMS.
wa_opt-DEFSIZE = 'X'.
call transaction <tcode>
using <it_bdcdata>
option from wa_opt.
Regards,
Gurunath Kumar D
2014 Nov 25 11:07 AM
Hi Gurunath,
Yes I using like that. But I am recording the BDC in 'local' update Mode. Is this any problem?
Thanks,
Priya
2014 Nov 25 11:21 AM
Hi Priya,
The update of the database will not be processes in 'LOCAL' update mode. Please use always use either 'A' or 'S' mode.
Regards,
Gurunath Kumar D
2014 Nov 25 11:33 AM
Hi Gurunath,
For changing from local to asynchronous update should I do the BDC recording again or I can change in program:
f_option-updmode = 'L'. to f_option-updmode = 'A'.
Please confirm.
Thanks,
Priya
2014 Nov 25 11:38 AM
2014 Nov 25 12:24 PM
Hi Priya,
No need. just change the update mode = 'A' as Bharani said.
Regards,
Gurunath Kumar D
2014 Nov 25 8:03 PM
2014 Nov 25 8:04 PM
2014 Nov 25 8:17 PM
Hi Priya,
I am little circumspect of the approach.As you mention BDC is working perfectly fine for you only user is experiencing the same issue.
Action item.
1.Ensure user is following the same steps and not doing any other clicks on the screen.
2.Go to SU01d and compare the user profiles of both.
3.Check in Su53 if he have right authorizations/role assigned.
4.Check in SM12 for any locks and SM13 for any update process violation.
I am sure you will get some hints here.
Regards,
Kannan
2014 Nov 26 10:17 AM
Hi All,
I corrected this error in DEV. Its was a dynpro field name change. For me the BDC recording showed
PERFORM bdc_field USING 'J_1IEXDYNPRO-REFDOC'
'R07'.
but for the user the BDC recording showed:
PERFORM bdc_field USING 'J_1IEXDYNPRO-REFDOC'
'R08'.
But why its is so?? If this is the case then it will be really difficult to execute correctly this report.
But now another problem the user is having the same problem in Quality. How can I permanently fix this problem??
Please do anyone know any other methods other than BDC to update excise invoice???
Thanks,
Priya