Viki - You're really getting way out of MM territory and into Dev topics now. I'm going to go ahead and answer here, and I beg the indulgence of all of the MM readers who (rightfully) think we should be in the other forum - if the dialog has to continue, I would suggest opening a new thread over there. What you're attempting to do with your VB code is very similar to the BDC programming technique in SAP - stepping through screens, pressing buttons and filling fields. Your challenge is, you're trying to do it from outside, without access to SAP's secret sauce and all of the internal information that's available in the SAP memory. To compound it, you're trying to automate what they call an 'Enjoy' transaction - and SAP has pretty clearly said that they don't intend to support automating those transactions. I'm not sure what the best advice is for you, since I don't know the process flow you're trying to create. If you want your VB code to step in and automate just part of an interactive session, where the user does most of the work and then lets your code do the menial stuff, then you might investigate having them use ME22 instead of ME22N. The downside is that you lose access to several years of additions and enhancements to the process that aren't available in the old transaction. On the other hand, if you're trying to automate the whole thing, and the user is not contributing to the PO editing process, then you should switch your approach entirely. My first choice would be to move the code into SAP - even if your situation requires that some remaining VB stub triggers it. My second choice would be that the VB code should ditch the SAPGUI automation, and directly call functions via RFC like BAPI_PO_CHANGE, and in this case READ_TEXT and SAVE_TEXT. My third choice (actually, that implies I like this choice, which I don't) would be to have the VB automate a SAPGUI session against ME22, and pray that you don't need to "hold" a PO, or deal with versions, or any of several other improvements that you won't be able to use. Dave
| | | ---------------Original Message--------------- From: Viktor Drizga Sent: Thursday, September 15, 2011 6:59 AM Subject: SAPLMEGUI number differs every time when SAP is launched Thanks for reply Dave. Do you know any button combination which gets me to "Item Detail Texts tab - Revise Delivery Note field"? It is in the last third of PO screen - Item Detail. Than Texts tab and Revise Delivery Note. I have also tried before running the script to do one item by hand and sometimes it changes anyway. It keeps changing between SAPLMEGUI:0010 and SAPLMEGUI:0015. Or it there any other how to eliminate this issue? Thanks a lot Viki Pua Esejpee | | __.____._ Copyright © 2011 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | Dave Thornburgh SAP Logistics Material Management Enthusiast
Contributed 100 posts in a group to earn a Bronze Achievement Popular White Papers In the Spotlight View the "Managing the Application Life Cycle" webinar and learn how organizations optimize their SAP applications. _.____.__ |
0 Response to "RE: [sap-log-mm] SAPLMEGUI number differs every time when SAP is launched"
Post a Comment