how to configure bus2012 for release strategy in SAp?

Answer 1

check the sap help portal:

http://help.sap.com/saphelp_erp2005vp/helpdata/en/04/92777c46f311d189470000e829fbbd/frameset.htm

Tasks: Release (MM-PUR-GF) Locate the document in its SAP Library structure

In these tasks, a purchasing document is released with a release code.

Request for Quotation (RFQ)

Task: TS20000175

Identifier: mm_qr_rel

Description: Release of RFQ

Referenced Object Method, Attributes

Object type: BUS2010 ( RFQ)

Method: SingleRelease ( individual release)

Attributes: None

Purchase Order (PO)

Task: TS20000166

Identifier: mm_po_rel

Description: Release of PO

Referenced Object Method, Attributes

Object type: BUS2012 ( PO)

Method: SingleRelease ( individual release)

Attributes: None

Scheduling Agreement

Task: TS20000169

Identifier: mm_pa_rel

Description: Release of scheduling agreement

Referenced Object Method, Attributes

Object type: BUS2013 ( Scheduling agreement)

Method: SingleRelease ( individual release)

Attributes: None

Contract

Task: TS20000172

Identifier: mm_pc_rel

Description: Release of contract

Referenced Object Method, Attributes

Object type: BUS2014 ( Contract)

Method: SingleRelease ( individual release)

Attributes: None

Maintaining Processor Assignment

At runtime, the relevant task is addressed to the processor(s) (processing staff member(s)) to whom the release code has been assigned via a role resolution. You must make the following settings in Customizing for this:

* In Task-Specific Customizing for SAP Business Workflow you must list all organization management objects that are generally permitted to work with workflow-relevant release codes (e.g. jobs or positions).
Prior to this, the organizational plan (defining the organizational structure) must be finalized.

* By assigning a release code to a processor in Customizing for Purchasing, you specify who in concrete terms may process a document (i.e. effect releases) using this code. Take care that this assignment is compatible with the processor assignment in Task-Specific Customizing. If you enter a user, for example, the latter must also be the holder of a position in Task-Specific Customizing. If you enter a position, precisely this position must also be defined in Task-Specific Customizing and have users assigned to it.

It is also necessary for the release codes to be marked as "relevant to Workflow".

See also:

Preparation and Customizing (MM-PUR-GF)

Determining the Processor

In determining the processor (the person who is to process the document), the system searches the Purchasing Customizing facility for the processor ID for a release code. This is achieved via role resolution.

For this purpose, the following roles are defined for the relevant task:

* Request for Quotation (RFQ)

Role 20000030 ( Person responsible for releasing RFQ)

* Purchase Order (PO)

Role 20000027 ( Person responsible for releasing PO)

* Scheduling Agreement

Role 20000028 ( Person responsible for releasing scheduling agreement)

* Contract

Role 20000029 ( Person responsible for releasing contract)

Input for the role comprises the release code and the relevant document. These were passed on to the role container from the task container.

Role Container Task container

<- _WI_OBJECT_ID
ReleaseC ode <- ReleaseCode

Then, using this data, the Customizing settings for Purchasing containing the linkage between release code and processor ID are read. After this, the system checks whether these settings agree with those of Task-Specific Customizing. If they do not, the workflow terminates and the system administrator responsible for workflow is informed by mail accordingly.

Terminating Events

The standard task Release is terminated by the events Release effected, or significantly changed.

See also:

Steps in a Workflow (MM-PUR-GF)




Leaving content frame