Status management via transaction BSVW nottriggeringeventforsalesdelivery - post goods issue.

[Mike Pokraka]

Hans, Vijay,

I didn't know status management also handles deliveries, and here I
thought I was learning something new :-)

No, the VBUK/P fields have nothing to do with "status management" in the
BSVW sense. They are just indicator fields.

Vijay's suggestion about triggering it from an output type is a solution
I've used myself, though it is better to add a requirement in your output
determination (VBUK-STATV = B or C) instead of checking the status in the
workflow. This way the workflow is also only triggered once on the first
GR. Otherwise you'll trigger a WF every time the delivery is changed,
which is not really a necessary use of system resources.

My preferred alternative is to trigger an event from the material document
using BAdI MB_DOCUMENT_BADI, though you need to check one or two extra
bits like movement types.

Cheers
Mike

vijay srikanth wrote:
> Hi Hans,
>
> Statuses through BSVW did not help me either. Alternatively you can see
> this
> status for any object type via FM READ_STATUS (object key should be 'VB'
> and
> delivery number concatenated and if the status is set at header level, you
> should include 000000 (posnr for header). It would look something like
> this
> Object Key : VB004500605000000. I suggest you use this instead of BSVW.
> Trigger a workflow maybe through an output type, everytime a sales order
> or
> a delivery is saved, and then check in one of your workflow steps for this
> status using the above said FM. You also change status via FM
> CANGE_STATUS_EXTERN. I'm working on exactly something like this, as and
> when
> a sales order is created it goes into a status. Hope this helps.
>
>
> Regards,
> Vijay
>
>
>>From: "Brilleman,Hans " <hans.brilleman at tntpost.com>
>>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>>Subject: RE: Status management via transaction BSVW
>>nottriggeringevent	forsalesdelivery - post goods issue.
>>Date: Mon, 9 Jan 2006 10:32:58 +0100
>>
>>Hi Mike,
>>
>>Where can you see if this status (PSTD) was set. I am only aware of the
>>status tables (vbuk and vbup) where you can see a status indicator C -
>>for completed, set for goods issue, which has been set.
>>
>>Greetings,
>>
>>Hans.
>>
>>-----Oorspronkelijk bericht-----
>>Van: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Namens
>>Mike Pokraka
>>Verzonden: vrijdag 6 januari 2006 19:24
>>Aan: SAP Workflow Users' Group
>>Onderwerp: Re: Status management via transaction BSVW not
>>triggeringevent forsalesdelivery - post goods issue.
>>
>>Hi Hans,
>>Have you checked whether status PSTD is set when you Post Goods Issue?
>>Cheers
>>Mike
>>
>>Brilleman,Hans wrote:
>> > Hi Anna,
>> >
>> > thanks for the suggestions. I set up the status schema (SALES001) and
>> > raised the event on the supertype, but for some or other reason it is
>> > still ignoring the action on the post goods issue. Do you perhaps have
>>
>> > any more ideas?
>> >
>> > Greetings,
>> >
>> > Hans
>> >
>> > ----------------------------------------------------------------------
>> > --
>> > *Van:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
>> > *Namens *Hill, Anna
>> > *Verzonden:* donderdag 5 januari 2006 17:25
>> > *Aan:* SAP Workflow Users' Group
>> > *Onderwerp:* RE: Status management via transaction BSVW not triggering
>>
>> > event forsalesdelivery - post goods issue.
>> >
>> > Hi Hans
>> >
>> > I've not worked in this particular area before but you generally need
>> > a status schema when you create the entry in BSVW. It's also best
>> > practice to raise events on the supertype (i.e. LIKP) not the subtype
>> > (ZLIKP) - as you have delegated your subtype then you should still see
>>
>> > your custom event against the supertype. If there is no status schema
>> > available then check with your applications expert to ensure that the
>> > statuses have been set up.
>> >
>> > Hope this helps
>> > Cheers
>> > Anna
>> > SAP UK
>> >
>> > ----------------------------------------------------------------------
>> > --
>> > *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
>> > Behalf Of *Brilleman,Hans
>> > *Sent:* Thursday, January 05, 2006 12:56 PM
>> > *To:* Sap-Workflow user group
>> > *Subject:* Status management via transaction BSVW not triggering event
>>
>> > for salesdelivery - post goods issue.
>> >
>> > Hi all,
>> >
>> > I am currently working on 4.7.
>> >
>> > I created a sub type of LIKP and in there created a new event
>> > POSTGOODSISSUED (sub type has been delegated).
>> >
>> > With BSVW I created a entry with values as such:
>> >
>> > Status OT = VBK
>> > Business object = ZLIKP
>> > Event = POSTGOODSISSUED
>> >
>> > Status restriction = PSTD
>> >
>> > For some or other reason it does not trigger the event when the post
>> > goods issue button is executed. I have looked everywhere but cannot
>> > find an solution to my problem. I have a way around it via a check
>> > function module, but I want to know why it does not work via status
>>management.
>> >
>> > Any explanation will be highly appreciated.
>> >
>> > Greetings,
>> >
>> > Hans.
>> >
>> >
>> > ----------------------------------------------------------------------
>> > --
>> >
>> > _______________________________________________
>> > 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
>