<div>Hi </div>
<div> Regarding Condition Editor for a Trip expenses wrkflw .</div>
<div>Go to SWB_COND tx and specify Condition , what ever you required.</div>
<div>If you want to specify any User name . Use name Field(Consider L_usre_name) should be in Business object Attribute.</div>
<div>Balaji.T</div>
<div><br><br><br> </div>
<div class="gmail_quote">On Fri, Nov 21, 2008 at 9:31 PM, <span dir="ltr"><<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Send SAP-WUG mailing list submissions to<br> <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
<br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br><br>You can reach the person managing the list at<br> <a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a><br><br>When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of SAP-WUG digest..."<br><br><br>Today's Topics:<br><br> 1. RE: Condition Editor for a Trip expenses wrkflw (John A Haworth)<br> 2. SWCONT's limitations with long values... (Mike Gambier)<br>
3. RE: SWCONT's limitations with long values... (Mike Gambier)<br> 4. RE: SWCONT's limitations with long values... (Mike Gambier)<br><br><br>----------------------------------------------------------------------<br>
<br>Message: 1<br>Date: Fri, 21 Nov 2008 15:09:23 +0000<br>From: John A Haworth <<a href="mailto:jhoworth@csc.com">jhoworth@csc.com</a>><br>Subject: RE: Condition Editor for a Trip expenses wrkflw<br>To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
Message-ID:<br> <<a href="mailto:OF71C4E59B.E1132E6A-ON80257508.00535ACE-80257508.005364F0@csc.com">OF71C4E59B.E1132E6A-ON80257508.00535ACE-80257508.005364F0@csc.com</a>><br>Content-Type: text/plain; charset="utf-8"<br>
<br>Thanks for that.<br><br>Kind Regards<br><br>JOHN HAWORTH<br>CSC<br><br>Euxton House<br>Euxton Lane<br>Chorley<br>PR76FE<br>Office:01257236457<br>Mob: 07710917927<br><br><br><br><br>CSC ? This is a PRIVATE message. If you are not the intended recipient,<br>
please delete without copying and kindly advise us by e-mail of the<br>mistake in delivery. NOTE: Regardless of content, this e-mail shall not<br>operate to bind CSC to any order or other contract unless pursuant to<br>explicit written agreement or government initiative expressly permitting<br>
the use of e-mail for such purpose<br> ?<br>CSC Computer Sciences Limited ? Registered Office: Royal Pavilion,<br>Wellesley Road, Aldershot, Hampshire, GU11 1PZ, UK ? Registered in England<br>No: 0963578<br><br><br><br>"Sue Doughty" <<a href="mailto:Sue.Doughty@odfl.com">Sue.Doughty@odfl.com</a>><br>
Sent by: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><br>21/11/2008 14:33<br>Please respond to<br>"SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
<br><br>To<br>"SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>cc<br><br>Subject<br>RE: Condition Editor for a Trip expenses wrkflw<br><br><br><br><br><br><br>Hi John,<br>
<br>The Agents container in the condition editor is the user that triggered<br>the event.<br><br>In the Condition editor on the Start Events tab check that Agents =<br>Trip.Traveler?s User.<br><br>Regards,<br>Sue T. Doughty<br>
SAP Workflow Specialist<br>Old Dominion Freight Line, Inc.<br>500 Old Dominion Way<br>Thomasville, NC 27360<br>Phone: (336) 822-5189<br>Toll Free (800 ) 432-6335, ext. 5189<br>Email: <a href="mailto:sue.doughty@odfl.com">sue.doughty@odfl.com</a><br>
<br>From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>Of John A Haworth<br>Sent: Friday, November 21, 2008 7:57 AM<br>
To: SAP Workflow Users' Group<br>Subject: Condition Editor for a Trip expenses wrkflw<br><br><br>Hi<br><br>I need to use the condition editor to limit the triggering of a workflow<br>based on the person who initiates the workflow should be the same as the<br>
person identified in the Trip object.<br><br>In the editor I can see the Trip object and under the System Field I can<br>see the %User Name% Who is this User Name ? I really want the workflow<br>initiator, but cant see it ??<br>
<br>Kind Regards<br><br>JOHN HAWORTH<br>CSC<br><br>Euxton House<br>Euxton Lane<br>Chorley<br>PR76FE<br>Office:01257236457<br>Mob: 07710917927<br><br><br><br><br>CSC ? This is a PRIVATE message. If you are not the intended recipient,<br>
please delete without copying and kindly advise us by e-mail of the<br>mistake in delivery. NOTE: Regardless of content, this e-mail shall not<br>operate to bind CSC to any order or other contract unless pursuant to<br>explicit written agreement or government initiative expressly permitting<br>
the use of e-mail for such purpose<br>?<br>CSC Computer Sciences Limited ? Registered Office: Royal Pavilion,<br>Wellesley Road, Aldershot, Hampshire, GU11 1PZ, UK ? Registered in England<br>No: 0963578 _______________________________________________<br>
SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br><br><br>-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20081121/7bf764c0/attachment-0001.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20081121/7bf764c0/attachment-0001.htm</a><br>
<br>------------------------------<br><br>Message: 2<br>Date: Fri, 21 Nov 2008 15:30:31 +0000<br>From: Mike Gambier <<a href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</a>><br>Subject: SWCONT's limitations with long values...<br>
To: <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Message-ID: <BAY117-W27190EFD8167C1D5B2EB94D50F0@phx.gbl><br>Content-Type: text/plain; charset="iso-8859-1"<br><br><br><br>Hi,<br><br>I'm trying to convince SAP that using a really long structure-based single line importing parameter for a BApI, that might grow and grow, isn't a smart idea because SWCONT is limited to 255 chars. My fear is that we'll hit some sort of limit somewhere which will cause problems, whether that will be in BoR elsewhere like a BAdI.<br>
<br>They've come back and said that swc* macros can cope with longer strings at runtime and no truncation will result. Personally I'm not convinced and can only assume that the SAP code flicks into set/get table mode to cope somehwere, but I can't seem to find where..does anyone here know whether it can do this and how?<br>
<br>Regardless of their suggested approach, I want to try and impress upon them that a nested unstructured approach is more suitable to our needs and something more akin to SAP's Master Data Generator table EPRODA (which assigns a type definition to an element) has more of a future in our system.<br>
<br>But they're being a bit stubborn about this and any ammuntion from the WUG about pitfalls when using long parameter definitions like this would be useful.<br><br>Thanks in advance,<br><br>Mike GT<br>_________________________________________________________________<br>
See the most popular videos on the web<br><a href="http://clk.atdmt.com/GBL/go/115454061/direct/01/" target="_blank">http://clk.atdmt.com/GBL/go/115454061/direct/01/</a><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>
URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20081121/0a2a5770/attachment-0001.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20081121/0a2a5770/attachment-0001.htm</a><br><br>
------------------------------<br><br>Message: 3<br>Date: Fri, 21 Nov 2008 15:40:37 +0000<br>From: Mike Gambier <<a href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</a>><br>Subject: RE: SWCONT's limitations with long values...<br>
To: <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Message-ID: <BAY117-W38F6FC00758DAC008C0A5AD50F0@phx.gbl><br>Content-Type: text/plain; charset="iso-8859-1"<br><br><br>Hi again,<br><br>I forgot to mention that the example they provide where an importing parameter structure is already longer than 255 is BoR Object Method ISUCONTRCT.ChangeFromData where parameter ContractData is based on BAPIISUCONTRACT which is 386 chars long in our system.<br>
<br>So, it must be able to cope somehow...presumably if I could be bothered to debug it I'd find out how ;)<br><br>MGT<br><br><br><br>From: madgambler@hotmail.comTo: sap-wug@mit.eduSubject: SWCONT's limitations with long values...Date: Fri, 21 Nov 2008 15:30:31 +0000<br>
<br><br><br>Hi,<br><br>I'm trying to convince SAP that using a really long structure-based single line importing parameter for a BApI, that might grow and grow, isn't a smart idea because SWCONT is limited to 255 chars. My fear is that we'll hit some sort of limit somewhere which will cause problems, whether that will be in BoR elsewhere like a BAdI.<br>
<br>They've come back and said that swc* macros can cope with longer strings at runtime and no truncation will result. Personally I'm not convinced and can only assume that the SAP code flicks into set/get table mode to cope somehwere, but I can't seem to find where..does anyone here know whether it can do this and how?<br>
<br>Regardless of their suggested approach, I want to try and impress upon them that a nested unstructured approach is more suitable to our needs and something more akin to SAP's Master Data Generator table EPRODA (which assigns a type definition to an element) has more of a future in our system.<br>
<br>But they're being a bit stubborn about this and any ammuntion from the WUG about pitfalls when using long parameter definitions like this would be useful.<br><br>Thanks in advance,<br><br>Mike GT<br><br>BigSnapSearch.com - 24 prizes a day, every day. Search now<br>
_________________________________________________________________<br>See the most popular videos on the web<br><a href="http://clk.atdmt.com/GBL/go/115454061/direct/01/" target="_blank">http://clk.atdmt.com/GBL/go/115454061/direct/01/</a><br>
-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20081121/4a6e878d/attachment-0001.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20081121/4a6e878d/attachment-0001.htm</a><br>
<br>------------------------------<br><br>Message: 4<br>Date: Fri, 21 Nov 2008 16:01:07 +0000<br>From: Mike Gambier <<a href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</a>><br>Subject: RE: SWCONT's limitations with long values...<br>
To: <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Message-ID: <BAY117-W39916B7DE1E0D4963331EFD50F0@phx.gbl><br>Content-Type: text/plain; charset="iso-8859-1"<br><br><br>Apologies for the spam :P<br>
<br>So, OK it decomposes the structures element by element (but only up to 255 chars for each). Hence a container becomes quite full of 'sub' elements belonging to the parent element.<br><br>I think I knew this...been a while since I've neeeded to care about it XD<br>
<br>But...I still don't think this is ideal where the parameter will be extended a lot...<br><br>I know that I can pass a multi-line table based on SWCONT into an SWCONT-based container (so setting a container into a container as a table), so I'm leaning towards suggesting an unstructured 'table of elements + values' instead of a complex structure...<br>
Pity BoR can't cope with ABAP_PARMBIND though...<br><br>MGT<br><br><br><br>From: madgambler@hotmail.comTo: sap-wug@mit.eduSubject: RE: SWCONT's limitations with long values...Date: Fri, 21 Nov 2008 15:40:37 +0000<br>
<br>Hi again, I forgot to mention that the example they provide where an importing parameter structure is already longer than 255 is BoR Object Method ISUCONTRCT.ChangeFromData where parameter ContractData is based on BAPIISUCONTRACT which is 386 chars long in our system. So, it must be able to cope somehow...presumably if I could be bothered to debug it I'd find out how ;) MGT<br>
<br><br><br>From: madgambler@hotmail.comTo: sap-wug@mit.eduSubject: SWCONT's limitations with long values...Date: Fri, 21 Nov 2008 15:30:31 +0000<br><br><br><br>Hi,<br><br>I'm trying to convince SAP that using a really long structure-based single line importing parameter for a BApI, that might grow and grow, isn't a smart idea because SWCONT is limited to 255 chars. My fear is that we'll hit some sort of limit somewhere which will cause problems, whether that will be in BoR elsewhere like a BAdI.<br>
<br>They've come back and said that swc* macros can cope with longer strings at runtime and no truncation will result. Personally I'm not convinced and can only assume that the SAP code flicks into set/get table mode to cope somehwere, but I can't seem to find where..does anyone here know whether it can do this and how?<br>
<br>Regardless of their suggested approach, I want to try and impress upon them that a nested unstructured approach is more suitable to our needs and something more akin to SAP's Master Data Generator table EPRODA (which assigns a type definition to an element) has more of a future in our system.<br>
<br>But they're being a bit stubborn about this and any ammuntion from the WUG about pitfalls when using long parameter definitions like this would be useful.<br><br>Thanks in advance,<br><br>Mike GT<br><br>BigSnapSearch.com - 24 prizes a day, every day. Search now<br>
<br>Win ?1000 John Lewis shopping sprees with BigSnapSearch.com Search now<br>_________________________________________________________________<br>Win ?1000 John Lewis shopping sprees with BigSnapSearch.com<br><a href="http://clk.atdmt.com/UKM/go/117442309/direct/01/" target="_blank">http://clk.atdmt.com/UKM/go/117442309/direct/01/</a><br>
-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20081121/9706c3ae/attachment.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20081121/9706c3ae/attachment.htm</a><br>
<br>------------------------------<br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br><br>End of SAP-WUG Digest, Vol 48, Issue 47<br>***************************************<br></blockquote></div><br>