User status as object attribute

Mike Pokraka asap at workflowconnections.com
Tue Aug 8 09:36:20 EDT 2006


Hi Anna,

Thanks for the info, I suspect this is where I'm missing something. But
this is at definition time - i.e. defining the object attribute. There are
no status profiles in sight when defining attributes (rightly so).

Debugging SWO1, I found it checks table TJ30 for possible user statuses
but passes no profile variable - thus looking for a blank. If I very
manually create an entry with a blank profile everything works fine -
though customizing doesn't allow this. hmmm.... Checked this on a 46c and
a 4.7 system also - same result.

Thanks for your input.
Have fun,
Mike


> Hi Mike
>
> Are you using the correct status profile to find the users statuses?
> Users statuses are configured against profiles so you'll only find the
> users status if you're searching against the right profile. You'll see
> the profile to use if you try and change the status manually in the
> transaction.
>
> Good luck!
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Tuesday, August 08, 2006 8:51 AM
> To: SAP Workflow Users' Group
> Subject: Re: User status as object attribute
>
> Hi Thomas,
>
> I'm working with a delegated QMSM subtype. It is starting to look like
> an
> OSS problem, though I can't find any notes by searching for any of the
> obvious terms (User status, ifstatus). When debugging a manual entry it
> looks for the status with a blank status profile, so I suspect it's got
> to
> do with that.
>
> I've even hardcoded values into the other Statusxxxxx attributes, no
> joy.
>
> Thanks for the feedback.
> Cheers,
> Mike
>
>>
>> Mike,
>>
>> I remember having a problem with statuses where the StatusObjNumber
>> attribute caused problems - will have to research.  Thought an OSS
> note
>> corrected.
>>
>> User statuses are definitely possible.
>>
>> Which BO are you working with?  That might help me find it.
>>
>> Regards,
>> Thomas Maue
>>
>>
>>
>>
>>              "Mike Pokraka"
>>              <asap at workflowcon
>>              nections.com>
> To
>>              Sent by:                  sap-wug at mit.edu
>>              sap-wug-bounces at m
> cc
>>              it.edu
>>
> Subject
>>                                        User status as object attribute
>>              08/07/2006 07:25
>>              AM
>>
>>
>>              Please respond to
>>                "SAP Workflow
>>                Users' Group"
>>              <sap-wug at mit.edu>
>>
>>
>>
>>
>>
>>
>> Hello all,
>> Simple question: How do I enable user statuses as attributes in a BO?
>>
>> I've done this before but for some reason it's not happening here or
> I'm
>> missing something blindingly obvious. When I select a status in the
>> attributes all I see are system statuses. If I enter it directly I get
>> "Status E0001 from the object status management is not defined".
>>
>> IFSTATUS, StatusObjNumber, StatusObjType, StatusProfile are all
>> implemented and functioning correctly, the object tests ok, searched
> the
>> archives, read the saphelp, still no user status. I can define an
>> attribute, when I hit the dropdown all I see are system statuses.
>>
>> Maybe it's not possible? It's been a while since I worked with it...
>>
>> Any input appreciated.
>> Cheers,
>> Mike
>>
>> _______________________________________________
>> 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
>





More information about the SAP-WUG mailing list