Then specify the task IDs that are relevant for the Purchase Order Approval scenario.
It is good to have someone who knows the Workflow settings for Approving POs. In our case the customer had implemented a custom workflow for Approving POs. In our case the Task ID was “WS91000003”, but if your customer is using the standard workflow template, the Task ID is “WS20000075”.
Follow a part of the application help that gives some hints on how to get the Task ID:
To find the workflow tasks you need to enter in this Customizing activity, proceed as follows:
Start transaction SWETYPV.
Find a line to which the following applies:
The ObjectType is BUS2012 (purchase order).
The Event is RELEASESTEPCREATED.
The checkbox Type linkage active is selected.
Copy the entry for Receiver Type in the same line to your clipboard.
Start the Workflow Builder (transaction SWDD).
Enter the content of the clipboard into the Workflow field and press ENTER.
In the Navigation Area, you see a list of steps.
For those steps that you want to use in the app, navigate to the Control tab and find out the ID of the task.
A5. Fiori Configuration Cockpit
Now it is time to Add a Tile in Fiori Cloud for the FrontEnd component of the App. You also have to use the destination you created in step S3.
Follow the screenshots.
Getting into the administration area.
Under “Content Management”
Create New App.
Create a Catalog.
Define a Group.
Define the Visualization of your tile.
Now check the catalog.
Important: Change the Fiori App to use the customer’s destination.
Choose the name of your destination.
In our case, the Approval Process didn’t work at the beginning.
Customer had a custom implementation of the Purchase Order Approval Workflow.
The App was getting the list of Orders to be approved, but when pushing the “Approve” button we were getting the error “No Release Code maintained for Purchase Order xxxx”
List of Purchase Orders:
Error when clicking Approve button.
We had to adjust the context elements of the approval task.
We followed the Chapter 3 of the below blog (from @Masayuki Sekihara) to fix it: