Skip to Content
author's profile photo Former Member
Former Member

Release strategy- best practise document

Is there a document available that identifies the "Best practise" and/or "Leading practise" for PR release strategy when the business requirements are complex and working with standard/ vanila release strategy would be very difficult to create and would be a maintenance nightmare?

Thanks

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 02, 2007 at 04:30 PM

    Hi Rajendra,

    Regarding the release Strategy customization please go through this link which is very useful for understanding the Release strategy.

    http://www.sap123.com/showthread.php?t=59

    rgds

    Chidanand

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 02, 2007 at 03:37 PM

    Please refer to SAP HELP which is easy to understand, If you have any problems related to this Please feel free to ask.

    Releasing Purchase Requisitions

    Prerequisites

    Before releasing a requisition, you need to know:

    Your release code (contact your system administrator)

    (If you wish to release an individual purchase requisition) the release status of the requisition (see Displaying Release Information)

    Release Options

    There are two ways of releasing purchase requisitions:

    Individual release

    You release items of an individual purchase requisition or - if the requisition has to be released in total - by releasing one item you simultaneously release all the others.

    Collective release

    You release all requisition items or complete requisitions that are awaiting processing by your release code. This is the preferred method if you frequently have to effect release.

    Release Conditions

    Definition

    The release conditions determine the release strategy in accordance with which a requisition or an external purchasing document is to be released.

    If a requisition or an external purchasing document does not meet the conditions for a release strategy, it is automatically released for further processing.

    Procedure Without Classification (Requisition Items Only)

    The conditions can be based on one of the following item characteristics or a combination of these:

    Account assignment category

    Material group

    Plant

    Total value

    Procedure with Classification (Requisitions and External Purchasing Documents)

    The conditions are formulated via characteristic values and are stored in the Purchasing Customizing facility (under the release strategy).

    A precondition for this is that the characteristics are first created and then assigned to classes. For information on classification, refer to the Cross-Application Components documentation under CA - Characteristics and CA - The Classification System and the Implementation Guide (IMG) for Purchasing (under Release Procedures).

    To enable a release strategy to be assigned to it, a requisition or an external purchasing document must have one of the possible values for each characteristic.

    Release Strategy

    Definition

    The release strategy defines the approval process for purchase requisitions or external purchasing documents. The strategy specifies the release codes necessary and the sequence in which releases have to be effected. You can define a maximum of eight release codes.

    The assignment of the release strategy to a requisition or a purchasing document is based on the release conditions.

    Release Code

    Definition

    The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. Who may work with which release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).

    In addition, the assignment of release code to individual processor (processing staff member) is defined according to organizational requirements - that is to say, the various departments specify which users will be working with which release codes.

    In the case of the release procedure with classification for purchase requisitions, the assignment of release code to processor can also be made via Customizing for Purchasing. In this case, there must be a linkage with SAP Business Workflow. The release codes are assigned to an Organization Management object in each case (e.g. a position). The system then determines the responsible processor (processing staff member) in each concrete case.

    Release Prerequisites

    Definition

    The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).

    The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.

    Release Indicator

    Definition

    When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.

    When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).

    What does the release indicator determine?

    Requisitions...

    External purchasing documents....

    Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure

    Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes

    Whether an RFQ or a PO may be created with reference to the item

    Whether the document may be changed by Purchasing after the start of the release procedure

    Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes

    Whether the purchasing document is released for transmission

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.