AW: AW: getting an attribute

Tue Oct 1 02:00:53 EDT 2002

Hello Jose,

try the following: change the data type of your variable MATNR! This is
not an object reference!

>   DATA: material TYPE swc_object OCCURS 0,
>         matobj TYPE swc_object,
>         matnr like vbap-matnr.    "instead of TYPE swc_object.
<=3D=3D=3D!!!!!
>   =20
>   swc_get_table ac_container 'Material' material. =3D=3D=3D=3D=3D>=20
> material filled with table
>   READ TABLE material INDEX 1 INTO matobj. =3D=3D=3D=3D=3D=3D> matobj =
filled
>   swc_get_property matobj 'Material' matnr.  =3D=3D=3D=3D=3D> matnr =
not=20

Regards
    Matthias

> -----Urspr=FCngliche Nachricht-----
> Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] Im=20
> Auftrag von Jose Burgman [AST]
> Gesendet: Montag, 30. September 2002 18:21
> An: SAP-WUG at MITVMA.MIT.EDU
> Betreff: Re: AW: getting an attribute
>=20
>=20
> The key gets passed across to VBAP OK during=20
> swc_get_property. When VBAP calls the method to get the=20
> material, the key for material seems to get scrambled - the=20
> sales document no and item no don't go across OK - the item=20
> contains the value VBAP (!) and sales doc no is a space.=20
> Obviously when looking up on the table it doesn't find the=20
> information.=20
>=20
> I tested the object VBAP in swo1, there it does it correctly.=20
> I looked on OSS and didn't find any references. So....I'm a=20
> bit stumped.
>=20
> Jose=20
>=20
> -----Original Message-----
>> From: Zmudzin,Tomasz,VEVEY,GL-DS/DM [mailto:Tomasz.Zmudzin at nestle.com]
> Sent: Monday, September 30, 2002 5:56 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: AW: getting an attribute
>=20
>=20
> Where exactly does this thing fail?=20
>=20
> Cheers, T.
>=20
> -----Original Message-----
>> From: Jose Burgman [AST] [mailto:jose.burgman at ast.co.za]
> Sent: Monday,30. September 2002 17:05
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: AW: getting an attribute
>=20
>=20
> Hi there
>=20
> I tried this and it did not work. The key does not seem to=20
> get passed across when i try and get the attribute. It's=20
> probably something simple that I'm doing wrong, but blow me=20
> over if I can pick it up!
>=20
> Thanks.
>=20
> Jose
>=20
> -----Original Message-----
>> From: Zmudzin,Tomasz,VEVEY,GL-DS/DM [mailto:Tomasz.Zmudzin at nestle.com]
> Sent: Monday, September 30, 2002 3:13 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: AW: getting an attribute
>=20
>=20
> Actually I think the name of the container element misled=20
> Heinz -- you need an instance of VBAP to query its properties:
>=20
> SWC_CREATE_OBJECT VBAPOBJ 'VBAP' matobj.   " or its part that=20
> contains the
> key
> SWC_GET_PROPERTY VBAPOBJ 'MATERIAL' matnr.
>=20
> Tomasz
>=20
>=20
> -----Original Message-----
>> From: Jose Burgman [AST] [mailto:jose.burgman at ast.co.za]
> Sent: Monday,30. September 2002 14:59
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: AW: getting an attribute
>=20
>=20
> Material is an attribute of the object VBAP so an instance=20
> should exist - I think the problem is that the key from VBAP=20
> is not being passed across to the get property macro - these=20
> fields contain no value when I'm in debug mode in the macro itself.=20
>=20
> Jose
>=20
> -----Original Message-----
>> From: Schmidinger, Heinz (Unaxis IT BZ)=20
> [mailto:heinz.schmidinger at unaxis.com]
> Sent: Monday, September 30, 2002 2:43 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: AW: getting an attribute
>=20
>=20
> is an instance of object 'BUS1001' avaiable at this time ?=20
> Otherwise maybe you shoud do swc_create_object 'BUS1001' mat_key
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: Jose Burgman [AST] [mailto:jose.burgman at ast.co.za]=20
> Gesendet am: Montag, 30. September 2002 14:11
> An: SAP-WUG at MITVMA.MIT.EDU
> Betreff: getting an attribute
>=20
> Hi every-one
>=20
> Well, I've got to a point where I'm not sure how to proceed.=20
> I'm in the process of creating a standard role. The position=20
> is determined by the material number - I'm using BUS2030=20
> (Customer Inquiry)as a starting point. In BUS2030 the items=20
> are a multiline element (of type VBAP) - I pass this to my=20
> standard role and extract the table (of type VBAP, called=20
> material). I read the first line of the table and I seem to=20
> get a key. When I try and get the material property (also an=20
> object BUS1001), no information is returned. In debug mode it=20
> seems the key is not passed across and I get nothing back for=20
> my material, although the key shows in my extracted object.=20
>=20
> ie
>   DATA: material TYPE swc_object OCCURS 0,
>         matobj TYPE swc_object,
>         matnr TYPE swc_object.
>   =20
>   swc_get_table ac_container 'Material' material. =3D=3D=3D=3D=3D>=20
> material filled with table
>   READ TABLE material INDEX 1 INTO matobj. =3D=3D=3D=3D=3D=3D> matobj =
filled
>   swc_get_property matobj 'Material' matnr.  =3D=3D=3D=3D=3D> matnr =
not=20
> filled. In debug mode, the key in matobj is not passed across=20
> to the implementation program.
>=20
> Can any-one tell me what I'm doing wrong?
>=20
> Thanks
>=20
> Jose.
> ______________________________________________
>=20
> "This information is intended only for the person or entity=20
> to which it is addressed and may contain private,=20
> confidential, proprietary and/or privileged material and may=20
> be subject to confidentiality agreements.
>=20
> Any review, retransmission, dissemination, or any other use=20
> of or taking of any action in reliance upon this information,=20
> by persons or entities other than the intended recipient, is=20
> prohibited.
>=20
> If you received this in error, please contact the sender and=20
> delete the material from all storage media.
>=20
> The company is neither liable for proper, complete=20
> transmission of the information contained in this=20
> communication, any delay in its receipt or that the mail is=20
> virus-free" ______________________________________________
>=20
> "This information is intended only for the person or entity=20
> to which it is addressed and may contain private,=20
> confidential, proprietary and/or privileged material and may=20
> be subject to confidentiality agreements.
>=20
> Any review, retransmission, dissemination, or any other use=20
> of or taking of any action in reliance upon this information,=20
> by persons or entities other than the intended recipient, is=20
> prohibited.
>=20
> If you received this in error, please contact the sender and=20
> delete the material from all storage media.
>=20
> The company is neither liable for proper, complete=20
> transmission of the information contained in this=20
> communication, any delay in its receipt or that the mail is=20
> virus-free" ______________________________________________
>=20
> "This information is intended only for the person or entity=20
> to which it is addressed and may contain private,=20
> confidential, proprietary and/or privileged material and may=20
> be subject to confidentiality agreements.
>=20
> Any review, retransmission, dissemination, or any other use=20
> of or taking of any action in reliance upon this information,=20
> by persons or entities other than the intended recipient, is=20
> prohibited.
>=20
> If you received this in error, please contact the sender and=20
> delete the material from all storage media.
>=20
> The company is neither liable for proper, complete=20
> transmission of the information contained in this=20
> communication, any delay in its receipt or that the mail is=20
> virus-free" ______________________________________________
>=20
> "This information is intended only for the person or entity=20
> to which it is addressed and may contain private,=20
> confidential, proprietary and/or privileged material and may=20
> be subject to confidentiality agreements.
>=20
> Any review, retransmission, dissemination, or any other use=20
> of or taking of any action in reliance upon this information,=20
> by persons or entities other than the intended recipient, is=20
> prohibited.
>=20
> If you received this in error, please contact the sender and=20
> delete the material from all storage media.
>=20
> The company is neither liable for proper, complete=20
> transmission of the information contained in this=20
> communication, any delay in its receipt or that the mail is=20
> virus-free"
>=20