ecc6 701 editor lock for SWO1 ( MOSTLY RESOLVED )

Evangelos Pournaras pourne at otenet.gr
Thu Jul 26 17:25:47 EDT 2012


Hello Rick,

 

The ‘released’ status allows the method to be published for use in external systems; I recall the .NET Connector showing only released methods as available for use while on a C# portal application development project.

In this context, it sounds useful to lock the interface of methods that are ready to be used externally; you need well-defined interfaces, and a guarantee that they are not subject to change.

 

 

 

Best regards,

Pournaras Evangelos

 

SAP Technical Expert – HR/Payroll Coordinator

TEKA SYSTEMS S.A.

252, Piraeus St. - 177 78 - Tavros

Athens - Greece

Tel: +30 210 489 8493

Mob: +30 6974 400525

Fax: +30 210 482 1474

E-mail: epournaras at teka.vionet.gr

 <http://www.tekasystems.com/> www.tekasystems.com

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Sample, Rick
Sent: Thursday, July 26, 2012 11:59 PM
To: SAP Workflow Users' Group
Subject: RE: ecc6 701 editor lock for SWO1 ( MOSTLY RESOLVED )

 

Somehow, all the methods got set to “Released”. Humph! No idea why. 

Did SAP change how this works with SAP ECC 6.0  / SAP GUI 7.20? Yes, we are finally of 4.6c. 

 

Honestly, I always just set and leave the methods to Implemented and never change it. 

I don’t recall ‘Released’ state ever stopping me from changes in the dialog box. It certainly does not stop me from changing the code. Kinda useless function me thinks. Was this always like this, or did it in fact change?

 

Whatever the case, that’s the problem. I set it back to Implemented and allows me to change the settings. I need to float this around to my other developers and see what they recall. 

 

Thanks,

Rick

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Gambier
Sent: Thursday, July 26, 2012 3:08 PM
To: SAP Workflow Users' Group
Cc: SAP Workflow Users' Group
Subject: Re: ecc6 701 editor lock for SWO1

 

Rick,

 

Have you checked SM12 to see if there's a generic lock left on anywhere, e.g. the ABAP report for the BOR Object itself?

 

I think just by displaying a WF definition SWDD can locks it without you realising it. 

 

Also worthwhile checking to see if you're still editing the current active version of the WF or whether the WF is in a weird state with no active version. 

 

Mike GT


Sent from my iPhone


On 26 Jul 2012, at 19:59, "Sample, Rick" <Rick.Sample at graybar.com> wrote:

Hi all, 

 

I have an issue that I never seen before. I was in SWO1 was making a code change. Then I got bumped out of SAP do to VPN going down in flames. I logged back in, screen came up with the ‘clear old sessions’ or ‘continue new’ (whatever verbiage). I choose to close old sessions and start over. I was in middle of a SAVE when it crashed. 

 

When I got back in SAP, I noticed it lost my change. Was saving but not Generating the code. No biggie, was one line. 

After more changes I tried opening the attributes on a method in the BOR to switch it background and all options for all methods are greyed out. Just for this object! I just set the method and task to foreground yesterday to test so I know it was working for me, but now, I can not get to the attributes to change them. And this is just for this BOR’s methods->attributes. Weird!

 

I checked SM12 and find nothing. 

Thanks,

Rick

 

<image001.png>

 

 

 

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20120727/8844dbe4/attachment.htm


More information about the SAP-WUG mailing list