swc_create_object & swc_get_property Macro Commands

[jerry.martinek]

Hi Jocelyn,

The subject line is Error in program RBUS4101when returing FIRSTNAME
Attribute ( 0000795160/2006 ) 

The reason I started down the macro path was that the person admitted there
was a problem with the attribute but they wanted to know where and how this
was being used in the SAP application. 

But based on your reply, this is a problem that should be fixed by SAP so I
will continue exchanging messages with the OSS person.

Regards,
Jerry Martinek   

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Dart, Jocelyn
Sent: August 17, 2006 9:25 PM
To: SAP Workflow Users' Group
Subject: RE: swc_create_object & swc_get_property Macro Commands

Hi Jerry, 

I don't think its the macros its more likely to be the coding sequence in
the business object. Remember that we must not assume any particular order
in which attributes are determined. That's the usual cause of the symptoms
you describe, i.e. value missing first time around. 

So provided you have not changed the standard code under BUS4101 or created
a delegated subtype look for notes and/or report the problem as a problem
with the standard business object BUS4101 - ****NOT**** as a problem with
the macros.  And if I were you I would create it as a new message - don't
confuse it with the old one if that talks about macros. 



Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney 
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission is
confidential and may be legally privileged. It is intended only for the
person or entity to which it is addressed. If you are not the intended
recipient, you are hereby notified that any distribution, copying, review,
retransmission, dissemination or other use of this electronic transmission
or the information contained in it is strictly prohibited. If you have
received this electronic transmission in error, please immediately contact
the sender to arrange for the return of the original documents. 
Electronic transmission cannot be guaranteed to be secure and accordingly,
the sender does not accept liability for any such data corruption,
interception, unauthorized amendment, viruses, delays or the consequences
thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the sender
is authorized to state them to be the views of SAP AG or any of its
subsidiaries. SAP AG, its subsidiaries, and their directors, officers and
employees make no representation nor accept any liability for the accuracy
or completeness of the views or information contained herein. Please be
aware that the furnishing of any pricing information/ business proposal
herein is indicative only, is subject to change and shall not be construed
as an offer or as constituting a binding agreement on the part of SAP AG or
any of its subsidiaries to enter into any relationship, unless otherwise
expressly stated. 


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
vijay srikanth
Sent: Friday, 18 August 2006 2: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