07-08-2010 5:30 PM
Hello Experts,
I am creating an ECATT to upload very basic data via PA40. I am new to ECATTu2019s but in the past I have clicked the back button to end my script.
Now when the script runs through it works fine but doesnu2019t end properly. If I execute it in the foreground, and I manually click the back button it works great but it wonu2019t automatically end.
Are there any suggestions to fixing this issue?
Regards,
Kevin
07-10-2010 4:02 PM
After doing some more research, I have found that creating ECATT's on PA40 has caused some problems for others.
I'm still curious why the ECATT wouldn't end (loop).
07-10-2010 4:02 PM
After doing some more research, I have found that creating ECATT's on PA40 has caused some problems for others.
I'm still curious why the ECATT wouldn't end (loop).
07-12-2010 4:36 AM
Hello, Kevin:
can you please give more information about the eCATT log? if possible, please attach the log in the message.
Normally, if the process goes well, the script will be executed as the way it was recored.
Best Regards, Lawrence
07-12-2010 1:35 PM
Thanks for investigating my error. I have sent you an email with the log messages.
Thanks,
Kevin
09-20-2010 10:49 AM
Hi Kevin,
I would need some details before I answer your question.
-> Is the recording done on TCD or SAPGUI?
-> If on TCD, then you should have pressed the Back button to get the position back to eCATT editor, check the last or last but one DYNPRO, if the OKCODE is correct.
-> If done on SAPGUI, make sure that you check the check box "close session" during your execution of the ecatt, that also closes the sessions once the execution finishes.
Let me know if u are still facing the problem.
Best regards,
Harsha
09-28-2010 1:28 AM
A great way to exit is to use the command in the command box: /eend
Cheers
09-28-2010 2:13 PM
Hi,
The best way to end eCATT recording either by TCD or SAPGUI is by pressing the yellow exit button(shift+F3).
Since this action will also be recorded as part of the script, this will never end in an error.
Thanks
Seema
10-15-2010 4:12 PM
Hi Harsha,
I'm sorry it has taken such a long time to respond. While working on this requirement I recorded the transaction via TCD. I have limited knowledge in the eCATT world, but I do understand typically how to back out of the recording by clicking the back button or the exit button.
I'm curious what you mean by the OKCODE being correct?
Thanks for the help!
Kevin
10-18-2010 8:25 AM
Dear Kevin,
TCD is a recording technique, which works like a BDC or LSMW's.. All the buttons that you click and the actions that you perform on a transaction is recorded in terms of fields and OKCODE.
Each DYNPRO of the Command interface of a TCD recording, would have an OKCODE in each DYNPRO step.
OKCODE in technical terms is the action that the TCD should perform while working with each DYNPRO's of the command interface.
If you observe the last 3 DYNPRO's of your interface, (The last one is for messages, which you can ignore) The third from last would have an OKCODE of '=ENDE' and the last but one should have '/EENDE'.
3rd from Last would look like this:
'S' 'BDC_OKCODE' '=ENDE'
2nd from last would look like this:
'S' 'BDC_OKCODE' '/EENDE'
If you have all these OK Codes intact in your interface, any TCD should close the session properly.
Check your interface and come back to me if you still have any questions.
Best regards,
Harsha
11-03-2010 8:37 PM
Hi Harsha,
I still have questions for you!
Quick recap... After hiring the initial employee via PA40, the eCATT script stops running once it returns back to the PA40 screen. If I manually hit the back button, the eCATT picks back up and continues perfectly (in the foreground).
When running in the background, I receive: Error in eCATT command TCD PA40 (S00344 No batch input data for screen SAPMP50A 2000)
Looking at the OK Codes I can see the 2nd to last looking like: 'S' 'BDC_OKCODE' '/EENDE' (Just as you said)
I don't have 3rd from last one that looks like '=ENDE' this though. My 3rd from last reads 'S' 'BDC_SUBSCR' 'MP000100' Is this where the problem is? If so, how can this be fixed?
Thanks so much!
11-08-2010 4:03 AM
Hi Kevin,
Apologies for the delay in responding. It was a very long weekend for us here in India.
There are 2 options that I can think of in your case:
Case 1 - As per your post above, you said that you have the DYNPRO in the TCD recording, but there is no ok_code in it except bdc_cursor. To quickly do it, go to the change mode of the eCATT, double click on the interface of the recording.
Double click on the 3rd from last DYNPRO, Click on the the New Entries button and then add a line: 'S' 'BDC_OKCODE' '=ENDE' . You can either add a new line or modify the existing BDC_CUrsor line with that information. That should work (provided you have the DYNPRO with the screen name and number recorded in your TCD)
Case 2 - If you do not have that third DYNPRO itself, then all I can ask you to do is to rerecord the process using TCD, copy and paste the 3rd from last DYNPRO from the new TCD recording to the old TCD recording. If you are about to do this, you need make sure that you not only copy the screen name, but also need to copy the okcode inside the screen name.
I hope this helps. Let me know if you need any additional info on this?
Best regards,
Harsha
11-12-2010 2:26 PM
Harsha,
Thank you for all the help! You have solved my long lasting query.
Sincerely,
Kevin
10-20-2010 5:14 PM
Hello Kevin,
It depends on which driver you are using, if you are using SAPGUI then we can stop the recording in the pop-up window and the recording ends automatically.
If you are recording using TCD , then the better way is to perform the operation intended then click on the exit button of the screen and then the recording ends with the popup asking if you want to transfer the data.
Hope this helps you out.
Thanks,
Ajay