swc_create_object & swc_get_property Macro Commands

[vijay srikanth]

ah There's a fine line of difference. There are two scenarios here, the BAPI 
itself causing the error, or the BAPI working fine, but the custom program 
not working properly after the BAPI  call. The former cause would be 
supported by SAP. But not the later.

In your case, since the BUS object doesn't populate the FIRSTNAME properly, 
I guess SAP should be able to provide a solution. One other easy way, 
inherit the object and create an attribute called FIRSTNAME_NEW, and try to 
write code such that your data is correctly populated in the new variable. 
and then start using the new attribute. Will that solve your problem?

Regards,
Vijay


>From: jerry martinek <jerry.martinek at shawbiz.ca>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: Re: RE: swc_create_object & swc_get_property Macro Commands
>Date: Fri, 18 Aug 2006 08:23:29 -0700
>
>
>
>
>
>Hi Vijay,
>
>That doesn't seem correct because if that is the case SAP wouldn't support 
>BAPI's or code that's available for customer use that is included in the 
>customers own code.
>
>If I open another message with a different subject and get the same SAP SRM 
>Support Consultant then what?
>
>Thanks,
>
>Jerry
>
>----- Original Message -----
>
>From: vijay srikanth <vijay_d15 at hotmail.com>
>
>Date: Friday, August 18, 2006 7:53 am
>
>Subject: RE: swc_create_object & swc_get_property Macro Commands
>
>
>
> >
> > ah ok, I Get it now. That's always SAP's standard answer. When you
> > raised
> > this note, they would have given you a link to a document which
> > tells
> > differnce between consulting and support. They won't touch the SAP
> > code if
> > it appears in a Z FM or a user exit. What Jocelyn told earlier
> > would be a
> > good idea, to tell SAP that BUS4101 has a problem with its
> > attributes, and
> > remove the custom environment from the note.
> >
> > Regards,
> > Vijay
> >
> > >From: "jerry.martinek" <jerry.martinek at shawbiz.ca>
> > >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> > >To: "'SAP Workflow Users' Group'" <sap-wug at mit.edu>
> > >Subject: RE: swc_create_object & swc_get_property Macro Commands
> > >Date: Fri, 18 Aug 2006 06:47:06 -0700
> > >
> > >Hi Vijay,
> > >
>
> > >The use of the custom function module comes into the picture when
> > you write
> > >your own function module that uses/calls the workflow macros to
> > instantiate>an instance of BUS4101 and then use the object
> > attributes for some evil
> > >deed
> > >which in my case is to figure the shopping cart approvers.
> > >
> > >For additional information refer to Appendix E "Workflow Macros"
> > in the
> > >book.
> > >
> > >Regards,
> > >Jerry Martinek
> > >
> > >-----Original Message-----
> > >From: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] On Behalf Of
> > >vijay srikanth
> > >Sent: August 17, 2006 9:14 PM
> > >To: sap-wug at mit.edu
> > >Subject: RE: swc_create_object & swc_get_property Macro Commands
> > >
> > >
> > >Hi Jerry,
> > >
>
> > >If you're talking about standard business object BUS4101, where
> > does use of
> > >custom function modules come in to the picture?
> > >
> > >Regards,
> > >Vijay
> > >
> > > >From: jerry martinek <jerry.martinek at shawbiz.ca>
> > > >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> > > >To: sap-wug at mit.edu
> > > >Subject: swc_create_object & swc_get_property Macro Commands
> > > >Date: Thu, 17 Aug 2006 10:55:06 -0700
> > > >
> > > >
> > > >
> > > >Hi,
> > > >
> > > >I've hit a wall with OSS regarding the usage of the above
> > workflow macro
> > > >commands.
> > > >
> > > >I reported a problem to OSS with the BUS4101 business object in
> > SRM 5.0
> > >in
>
> > > >that when you instantiate the object, the 'Firstname' attribute
> > isn't> >populated. I even managed to get the person who is
> > assigned the message
> > >to
> > > >agree that there is a problem. I provided screen samples of
> > where the
> > > >problem is occurring in the SAP code and etc ... Then this
> > person tells
> > >me
> > > >that since I'm using the workflow macros in a custom function
> > module that
> > > >SAP will not fix the problem as this person's position is that
> > this is a
> > > >remote consulting issue and there is no problem with the SAP
> > code .....
> > > >
> > > >I've always been under the impression that these macros are
> > released for
> > > >customer use so if I run into a problem using them and if its SAP's
> > > >problem, that they should fix the code.
>
> > > >
> > > >If you run SWO1 and execute a test for BUS4101 the first name
> > is not
> > > >returned.
> > > >
> > > >Can someone please confirm that if that code isn't working
> > properly that
> > > >it's part of the regular SAP support agreement and not remote
> > consulting.> >
> > > >Sample:
> > > >
> > > >swc_create_object lo_bus4101_chief 'BUS4101' l_chiefwfid.
> > > >.......
> > > >swc_get_property lo_bus4101_chief 'FirstName' l_firstname.
> > > >swc_get_property lo_bus4101_chief 'LastName' l_lastname.
> > > >.....
> > > >
> > > >The LastName and other attributes work fine.
> > > >
> > > >Regards,
> > > >
> > > >Jerry Martinek
> > > >
> > >
> > >
> > > >_______________________________________________
>
> > > >SAP-WUG mailing list
> > > >SAP-WUG at mit.edu
> > > >http://mailman.mit.edu/mailman/listinfo/sap-wug
> > >
> > >
> > >
> > >_______________________________________________
> > >SAP-WUG mailing list
> > >SAP-WUG at mit.edu
> > >http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
>


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