Displaying prior approved PRs post Flexible

workflow activation fails

Contents
Issue: .............................................................................................................................................................. 1
Requested change: ........................................................................................................................................ 2
Fiori Approval app reference: ........................................................................................................................ 3

Issue:
A custom Epiq error message is being triggered. Need to determine:

- if this user exit in general still needs to be active

- and/or if the message needs to be changed to stop aborting the transaction.
- If the error message is skipped, does the PR still display any approvers in the ME53n.

1. In transaction Me53n, display PR 10051358. Navigate to the “Release Strategy group” tab. The
below popup/message appears. The user is then kicked out of the display transaction of me53n
which is not ok.
Include: ZXM06U12

Requested change:

Release Strategy approvers should no longer be retrieved or displayed to users. Rather, a warning
message should present to the user when SAP tries to fetch the Release Strategy approvers.

Short Message: Approval history for this Purch Req can be found in the line item change history.

Long Message: Purchase Requisitions created before XX/XX/XXXX utilized a retired approval mechanism
titled “Release Strategy”. The approval history can be found in the line item history changes.

To see the approval history, select line item 1. Then, using the top menu, navigate to Environment ->
Item Changes. The line where the “New Value” is 05 for Requisition Processing State shows the final
approval.
The entirety of the user exit needs to commented out. The only remaining ite

Fiori Approval app reference:

Test: approving PR 10052447 via Fiori. Does it appear as changes in S4?

Me53n:

1. Approval Details Tab:

a. Step 1.

b. Step 2 (doubleclick comment)

2. Environment - > Line Item changes shows no changes.

a.

Why does 10050305 support both workflows and no errors?

Note: this PR does show a change history of the “old” release strategy approach:
What field to use for finding un-released PR’s?

FRGDT Release Date. A: No. this is a supply chain esque field rather than PR approval status field.

BANPR Requisition Processing State

BANPR = 05 equal released; 03 = not released.