<BODY><P></P>
<P>Hi,</P>
<P>Based on the following response, changing the subject isn't going to get the message past the current OSS person:</P>
<P>
<TABLE class=urMatrixLayout style="WIDTH: 100%" cellSpacing=0 cellPadding=0 border=0 ct="MatrixLayout">
<TBODY class=urLinStd>
<TR>
<TD class=urLayoutDefault><LABEL class="urLblStdBar urVt1" style="WHITE-SPACE: nowrap" onclick="sapUrMapi_Label_clickLabeledElement('','note2sap',event);" ct="Label" f="note2sap"><SPAN>Info to SAP</SPAN></LABEL> </TD></TR>
<TR>
<TD class=urLayoutDefault> </TD></TR>
<TR>
<TD class=urLayoutDefault><SPAN class="urTxtEmph urVt1" id=timestamp style="WHITE-SPACE: nowrap" ct="TextView">17.08.2006 - 14:02:41 CET SAP Reply</SPAN> </TD></TR>
<TR>
<TD class=urLayoutDefault>
<P class=urTxtStd id=timestamp ct="TextView">Hello Jerry,<BR><BR>I can see that the FIRSTNAME does not appear in the BUS1401 object,<BR>however after much analysis I cannot see where this is causing<BR>and issue in any standard programs or transactions.<BR><BR>Can you please provide details of where this causes an error in the<BR>standard workflow or causes errors in any SAP delivered transactions.<BR>As I said, if you can identify any such errors that a correction will beprovided.<BR></P></TD></TR></TBODY></TABLE></P>
<P>Pushing water uphill!</P>
<P>Thanks,</P>
<P>Jerry</P>
<P>----<STRONG> Original Message -----</STRONG></P>
<P></P><B>From</B>: "jerry.martinek" <jerry.martinek@shawbiz.ca>
<P></P><B>Date</B>: Friday, August 18, 2006 6:40 am
<P></P><B>Subject</B>: RE: swc_create_object & swc_get_property Macro Commands
<P></P>
<P></P>> Hi Jocelyn, <BR>> <BR>> The subject line is Error in program RBUS4101when returing FIRSTNAME <BR>> Attribute ( 0000795160/2006 ) <BR>> <BR>> The reason I started down the macro path was that the person <BR>> admitted there <BR>> was a problem with the attribute but they wanted to know where and <BR>> how this <BR>> was being used in the SAP application. <BR>> <BR>> But based on your reply, this is a problem that should be fixed by <BR>> SAP so I <BR>> will continue exchanging messages with the OSS person. <BR>> <BR>> Regards, <BR>> Jerry Martinek <BR>> <BR>> -----Original Message----- <BR>> From: sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] On Behalf Of <BR>> Dart, Jocelyn <BR>> Sent: August 17, 2006 9:25 PM <BR>> To: SAP Workflow Users' Group <BR>> Subject: RE: swc_create_object & swc_get_property Macro Commands <BR>> <BR>> Hi Jerry, <BR>> <BR>
> I don't think its the macros its more likely to be the coding <BR>> sequence in <BR>> the business object. Remember that we must not assume any <BR>> particular order <BR>> in which attributes are determined. That's the usual cause of the <BR>> symptomsyou describe, i.e. value missing first time around. <BR>> <BR>> So provided you have not changed the standard code under BUS4101 <BR>> or created <BR>> a delegated subtype look for notes and/or report the problem as a <BR>> problemwith the standard business object BUS4101 - ****NOT**** as <BR>> a problem with <BR>> the macros. And if I were you I would create it as a new message - <BR>> don't <BR>> confuse it with the old one if that talks about macros. <BR>> <BR>> <BR>> <BR>> Regards, <BR>> Jocelyn Dart <BR>> Senior Consultant <BR>> SAP Australia Pty Ltd. <BR>> Level 1/168 Walker St. <BR>> North Sydney <BR>> NSW, 2060 <BR>> Australia <BR>
> T +61 412 390 267 <BR>> M + 61 412 390 267 <BR>> E jocelyn.dart@sap.com <BR>> http://www.sap.com <BR>> <BR>> The information contained in or attached to this electronic <BR>> transmission is <BR>> confidential and may be legally privileged. It is intended only <BR>> for the <BR>> person or entity to which it is addressed. If you are not the intended <BR>> recipient, you are hereby notified that any distribution, copying, <BR>> review,retransmission, dissemination or other use of this <BR>> electronic transmission <BR>> or the information contained in it is strictly prohibited. If you have <BR>> received this electronic transmission in error, please immediately <BR>> contactthe sender to arrange for the return of the original <BR>> documents. <BR>> Electronic transmission cannot be guaranteed to be secure and <BR>> accordingly,the sender does not accept liability for any such data <BR>
> corruption,interception, unauthorized amendment, viruses, delays <BR>> or the consequences <BR>> thereof. <BR>> Any views expressed in this electronic transmission are those of the <BR>> individual sender, except where the message states otherwise and <BR>> the sender <BR>> is authorized to state them to be the views of SAP AG or any of its <BR>> subsidiaries. SAP AG, its subsidiaries, and their directors, <BR>> officers and <BR>> employees make no representation nor accept any liability for the <BR>> accuracyor completeness of the views or information contained <BR>> herein. Please be <BR>> aware that the furnishing of any pricing information/ business <BR>> proposalherein is indicative only, is subject to change and shall <BR>> not be construed <BR>> as an offer or as constituting a binding agreement on the part of <BR>> SAP AG or <BR>> any of its subsidiaries to enter into any relationship, unless <BR>
> otherwiseexpressly stated. <BR>> <BR>> <BR>> -----Original Message----- <BR>> From: sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] On Behalf Of <BR>> vijay srikanth <BR>> Sent: Friday, 18 August 2006 2:14 PM <BR>> To: sap-wug@mit.edu <BR>> Subject: RE: swc_create_object & swc_get_property Macro Commands <BR>> <BR>> <BR>> Hi Jerry, <BR>> <BR>> If you're talking about standard business object BUS4101, where <BR>> does use of <BR>> custom function modules come in to the picture? <BR>> <BR>> Regards, <BR>> Vijay <BR>> <BR>> >From: jerry martinek <jerry.martinek@shawbiz.ca> <BR>> >Reply-To: "SAP Workflow Users' Group" <sap-wug@mit.edu> <BR>> >To: sap-wug@mit.edu <BR>> >Subject: swc_create_object & swc_get_property Macro Commands <BR>> >Date: Thu, 17 Aug 2006 10:55:06 -0700 <BR>> > <BR>> > <BR>> > <BR>> >Hi, <BR>> > <BR>
> >I've hit a wall with OSS regarding the usage of the <BR>> above workflow macro <BR>> >commands. <BR>> > <BR>> >I reported a problem to OSS with the BUS4101 business object in <BR>> SRM 5.0 in <BR>> >that when you instantiate the object, the 'Firstname' attribute <BR>> isn't <BR>> >populated. I even managed to get the person who is assigned the <BR>> message to <BR>> >agree that there is a problem. I provided screen samples of where <BR>> the <BR>> >problem is occurring in the SAP code and etc ... Then <BR>> this person tells me <BR>> >that since I'm using the workflow macros in a custom function <BR>> module that <BR>> >SAP will not fix the problem as this person's position is that <BR>> this is a <BR>> >remote consulting issue and there is no problem with the SAP code <BR>> .....> <BR>
> >I've always been under the impression that these macros are <BR>> released for <BR>> >customer use so if I run into a problem using them and if its <BR>> SAP's <BR>> >problem, that they should fix the code. <BR>> > <BR>> >If you run SWO1 and execute a test for BUS4101 the first name is <BR>> not <BR>> >returned. <BR>> > <BR>> >Can someone please confirm that if that code isn't working <BR>> properly that <BR>> >it's part of the regular SAP support agreement and not remote <BR>> consulting.> <BR>> >Sample: <BR>> > <BR>> >swc_create_object lo_bus4101_chief 'BUS4101' l_chiefwfid. <BR>> >....... <BR>> >swc_get_property lo_bus4101_chief 'FirstName' l_firstname. <BR>> >swc_get_property lo_bus4101_chief 'LastName' l_lastname. <BR>> >..... <BR>> > <BR>> >The LastName and other attributes work fine. <BR>> > <BR>> >Regards, <BR>
> > <BR>> >Jerry Martinek <BR>> > <BR>> <BR>> <BR>> >_______________________________________________ <BR>> >SAP-WUG mailing list <BR>> >SAP-WUG@mit.edu <BR>> >http://mailman.mit.edu/mailman/listinfo/sap-wug <BR>> <BR>> <BR>> <BR>> _______________________________________________ <BR>> SAP-WUG mailing list <BR>> SAP-WUG@mit.edu <BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug <BR>> <BR>> <BR>> _______________________________________________ <BR>> SAP-WUG mailing list <BR>> SAP-WUG@mit.edu <BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug <BR>> </BODY>