cancel
Showing results for 
Search instead for 
Did you mean: 

Release procedure

Former Member
0 Kudos

For PR the release conditions are

if net value < 1000, person 1 will approve

if net value > 1000 < 50000, person 1 & 2 will approve

if net value >50000, person 1,2,3 will approve.

But due to some reasons Person 3 is rejecting PR. Example instead of 100 pcs person 3 wants end user to request for only 90 pcs.

1. How this will be communicated( i hope person 3 will reject by going to transaction ME54n but he cant communicate to user to change qty to 90 pcs correct?)

2. If person 2 changes some value or qty even less than actual, then once again new strategy has to be triggered from person 1, 2,3.

Pls hlp me how to solve

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

To communicate between the Release effecting Users you can use SAP Business Workflow. When you set up the release procedure with classification for purchase requisitions or purchase orders, you can define a link to the SAP Business Workflow. This is particularly advisable if employees whose daily duties include tasks other than the approval of requisitions or purchase orders are involved in the release procedure.

The employee is automatically advised when a release is to be effected. A work item appears in his or her inbox, which he or she can process directly. When the item is processed, the SAP release transaction is automatically invoked with the relevant release code.

For more information, please refer to MM - Materials Management: Workflow Scenarios in SAP Library.

To trigger the new Release Strategy, please follow the Case2/ Case 3 mentioned below:

Changes After the Start of the Release Procedure -The following cases can arise when a purchase requisition or external purchasing document for which the release procedure has already started is changed:

Case 1: Insignificant change that does not necessitate a different release strategy.

Case 2: Relevant change that does not necessitate a different release strategy.

Case 3: Relevant change that necessitates a different release strategy

In each case, the system issues a message to the user after the change has been made.

Case 1

Instead of 10 tons of Steel 1 at a total price of $100, only 8 tons are needed, at a total price of $80.

This subsequent change to the document is possible. The release procedure continues uninterrupted.

Case 2

A user has the authorization for purchase orders valued between $1,000 and $120,000. Release strategy FS is assigned in this case.

The user has ordered 10 cameras at a price of $1000 each. The release procedure has already started and the release indicator 01 (free for issue of RFQ) has been set.

The settings made in Customizing for Purchasing for release indicator 01 are such that the system will issue a warning message if the original PO value is exceeded by more than 50%.

The user then changes the PO to 100 cameras, causing the PO value to increase by more than 50%. The system reassigns release strategy FS and issues the warning message.

The user has the following options:

Correct the PO, so that the percentage is not exceeded. The release procedure then continues.

No correction to PO. The system then cancels the previous releases and the release procedure starts all over again from the beginning.

Case 3

An electron beam welding machine assigned to project A is to be subsequently reassigned to cost center 3. Again, it is not possible to simply go ahead and make this change. The system will issue an error message. Either the change must be cancelled, or the release strategy redetermined and the approval procedure restarted.

Regards,

Narayana.

Edited by: Narayana Ghanta on Sep 17, 2008 4:21 PM

Former Member
0 Kudos

Hi,

You can achieve this by WOrkflow.

I have no idea how configure workflows. But you can send a message to the user inbox regarding the change to be done purch doc.

Try the link provided below

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf

Thanks

Anand K

Edited by: anand k on Sep 17, 2008 12:35 PM