Alternative Release Code for PR or PO Without Workflow

Introduction to SAP Release Strategies

What Are Release Codes and Levels?

  • Release Code: A key that identifies an individual or group authorized to release documents.
  • Release Level: The stage in the release process; documents must pass through these levels before being finalized.

Purpose of Alternative Release Codes

Alternative release codes allow flexibility, enabling more than one person to approve documents at the same level. This is essential when the primary approver is unavailable.

Scenario: Setting Alternative Release Code at Level 2

Typical 3-Level Release Strategy Explained

Level Role Action
1 Junior Buyer Initial Review
2 Senior Buyer/Backup Approval by Either Employee
3 Procurement Head Final Authorization

Requirement: Either Employee Can Release at Level 2

To meet this requirement:
  • Both employees must be authorized for the same release code.
  • The system should proceed to level 3 if either releases the document.

How to Configure Alternative Release Code for Purchase Orders (PO)

Using Classifications in PO

Step 1: Define Release Strategy in SPRO

Go to SPRO → Materials Management → Purchasing → Purchase Order → Release Procedure → Define Release Strategy.

Step 2: Assign Classifications

Use characteristics such as:

Step 3: Set Up Release Group and Codes

  • Create release group (e.g., G1).
  • Define release codes (e.g., 03 for level 2).
  • Assign these codes to the desired strategy.

Step 4: Assign Authorization to Multiple Users

Use transaction PFCG or ask the authorization admin to assign the same release code to both users. Either can now release the PO using ME28.

How to Configure Alternative Release Code for Purchase Requisitions (PR)

Handling PRs Without Classifications

Assigning Multiple Employees to One Position

1. Use PPOMA to assign both users to the same position.
2. In OMGS, assign object type “S” with the position ID in the Agent ID field.

Managing Release Without Workflow

If workflow isn't implemented, ensure:
  • Employees access PRs via ME54N.
  • Authorizations allow either user to perform the release.

Workflow-Based vs Non-Workflow-Based Release Process

Workflow Configuration Overview (OMGS, PPOMA)

  • OMGS is used to map release codes to positions.
  • PPOMA allows you to assign users to those positions.
  • This lets either employee execute the release.

Direct Release Using Transaction Codes (ME28, ME29N)

If workflow isn’t in place:
  • Assign release code authorization directly.
  • Users can release documents using ME28 (for PO) or ME54N (for PR).

Best Practices to Minimize Release Codes

Example Configuration with G1 and Release Code 03

Assign release group G1 and code 03 to both users:
  • Only one release code needed for both.
  • The system continues automatically upon release by either.

Temporary Authorization Assignment with Validity Period

In cases of absence:
  • Temporarily assign release codes with an end date.
  • Use transaction PFCG to configure validity.
  • The system disables access automatically when the date expires.

Common Issues and Troubleshooting Tips

Conflicts in Authorization

  • Ensure both employees have M_BEST_BSA and M_EINK_FRG authorizations.
  • Check for missing roles or validity dates.

Validity Expiration and Its Impact

  • If a user’s authorization expires, they’ll be unable to release.
  • Always check validity when users report access issues.

FAQs on Alternative Release Code for PR or PO

Q1: Can I assign multiple release codes at one level?

No, but you can assign the same code to multiple users.

Q2: Is workflow necessary for this setup?

No. You can manage releases without workflow using transaction codes and proper authorization.

Q3: What transaction is used to release a PO without workflow?

Use ME28 for mass release or ME29N for individual release.

Q4: How do I assign a release code to multiple users?

Use transaction PFCG and assign the same role with release authorizations to both.

Q5: Can I temporarily assign release rights?

Yes, through validity settings in PFCG.

Q6: What happens if no one releases at level 2?

The document remains unreleased and cannot proceed to the next level.

Conclusion: Efficiently Managing SAP Release Strategies Without Workflow

Using an alternative release code for PR or PO is a smart way to streamline approvals and build redundancy into your procurement process. Whether you use classifications or not, configuring SAP to allow either of two users to approve documents without workflow is entirely possible—and practical. Stick to best practices, maintain clear authorizations, and your process will remain seamless even during staff absences.

Fast links:
Get help for your SAP MM problems
SAP MM Forums - Do you have a SAP MM Question?

SAP MM Books
SAP Materials Management Reference Books

SAP Material Management Tips
SAP MM Configuration Tips and Materials Management

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.