Purchase Requisition Item - Custom Release Procedures

[David G Cooper]

Hi Fellow Developers,

 

This is just a quick note/warning for workflow developers using the BUS2009
(Purchase Requisition Item) object with a custom release procedure.

1)   The following events all have a standard parameter "ReleaseCode" which
is checked against table T161E

a.   Released

b.   Reset

c.   Rejected

d.   ReleaseStepCreated

e.   SignificantlyChanged

2)   ReleaseCodes are maintained as part of configuration in TWO areas, only
the first option below updates table T161E

a.   Materials Management -> Purchasing -> Purchase Requisition -> Release
Procedure -> Set Up Procedure Without Classification

b.   Materials Management -> Purchasing -> Purchase Requisition -> Release
Procedure -> Procedure with Classification -> Set Up Procedure with
Classification

3)   If the Release Codes are not entered into table T161E, the raised event
will

a.   Fail, and

b.   Deactivate the event binding on the workflow

4)   The workflow cannot be restarted as the standard workflows all have a
mandatory parameter for the Release Code

 

While having a custom release procedure within a custom Z Table is common,
as businesses like to centralize the management of financial authority.
Please keep in mind that the release codes used need to be entered in BOTH
configuration areas.

 

Just a friendly reminder for the future.

** Note: a Check function on the raise event could prevent the deactivation
of the event binding, but still cannot start the workflow.

 

Kind Regards

David Cooper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130313/5e827e76/attachment.htm