SAP ABAP IMG Activity OLMEOME6 (Set Up Procedure Without Classification)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ ME0C (Package) Customizing R/3 Purchasing
IMG Activity
ID OLMEOME6 Set Up Procedure Without Classification  
Transaction Code S_ALR_87002165   IMG Activity: OLMEOME6 
Created on 19981222    
Customizing Attributes OLMEOME6   Set Up Procedure Without Classification 
Customizing Activity OLMEOME6   Set Up Procedure Without Classification 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLMEOME6    

In this step, you can set up release procedures for purchase requisitions.

For release purposes, you must define strategies, which the SAP System sets up taking the following into consideration:

Note
If you define a release strategy dependent on the account assignment
category, you must maintain all possible combinations of plant and
material group for each account assignment category.

Standard settings

The release procedure without classification is predefined in the standard SAP System.

Activities

  1. Decide whether you wish to make use of the automatic release option.
  2. If you do not wish to work with automatic release, you must delete all table entries.

For requisitions, you can use either the release procedure WITHOUT classification (procedure 1) or the one WITH classification (procedure 2). Procedure 2 gives you considerably more flexibility in determining the strategy.

If you have previously worked with procedure 1, for example, but now wish to switch to procedure 2, you must at least define the release group for procedure 2. As soon as you have saved this, procedure 2 is active. If you wish to work with procedure 1 again, it is enough to delete the release group.

If you wish to work with procedure 1, define the following:

  • Release codes
  • Release indicators
  • Assignment of release indicators
  • Release prerequisites
  • Determination of release strategy

  1. Release codes

    Create the release codes.

  2. Release indicators

    Define release indicators and branch to the detail screen. Here you define whether fixed purchase requisitions may be changed by Materials Planning, for example, and whether an RFQ or a purchase order may be created from the requisition.

    You can also determine the field selection here.

    In the area "Changes after the start of the release procedure", you specify whether a requisition may be changed after the release procedure has begun. You specify whether the strategy has to be redetermined after changes, or whether the release procedure has to start all over again from the beginning.

    This parameter bears a relation to the parameter "Value change". For example, previous releases are not cancelled if the value of the requisition item after the change does not exceed plus 10% of its original value.

    Attention:
    Be sure to create a release indicator (e.g. B for "blocked") that serves as the starting point for subsequent indicators. Do not set the indicators for release for the issue of RFQs and PO on the detail screen for this indicator.
    Also create a release indicator characterizing the released status. Set the indicators for release for the issue of RFQs and PO on the detail screen.

  3. Assignment of release indicators

    Assign a release indicator in dependence on the status of the release.

    Example:

    You create a release strategy S1 consisting of two release codes 01 and 02. Release with 01 is a prerequisite for release with 02. If release has been effected with 01, the requisition has been given the "all clear" for the issue of RFQs.

    You have created the release indicators B (blocked), 1 (cleared for issue of RFQs) and 2 (cleared for RFQs and PO).

    Now enter the following as assignment:

    Strategy C1 C2 C3 ...
    S1 B (blocked)
    S1 X 1 (RFQ)
    S1 X X 2 (RFQ/PO)

  4. Release prerequisites

    Define which release codes are involved in a release strategy. Specify whether a code is set for a release status following release, and whether one release status is a prerequisite for another (+).

    Example:

    Strategy Code C1 C2 C3 ...
    S1 01 X
    S1 02 + X

  5. Determination of the release strategy

    Determine the conditions under which each release strategy is assigned. The criteria are account assignment category, material group, plant, and value of the requisition item.

Note

For more information, refer to the MM Purchasing documentation, section "Release Procedure".

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OLMEOME6 0 HLA0001529 Release of Requisitions 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_161E V - View SM30 FREIGABE01 Release Codes 
V_161S V - View SM30 FREIGABE02 Release indicator 
V_161G V - View SM30 FREIGABE03 Assign Release Indicators 
V_161F_SIM V - View SM30 FREIGABE04 Release Points: Prerequisites 
V_161I V - View SM30 FREIGABE05 Determination of Release Strategy 
History
Last changed by/on SAP  20000525 
SAP Release Created in