Control Business Transactions for your Process Orders & Operations
With the 2208 release of SAP S/4HANA Cloud, public edition, a new feature named Business Transaction Control was released, in the area of production operations for process orders.
With this feature, you can now control what business transactions are possible for a process order, depending on other business transactions. More specifically, the system will allow or forbid certain transactions from being performed, based on the statuses that exist on the process order.
This Business Transaction Control feature will influence the allowed business transactions at the order header level or order operation level.
To illustrate this capability, we will look at the use case where you may want to block Goods Movements to a process order after it has been technically completed – i.e after the TECO status has been assigned to a process order.
Before we look at the functional process, let’s head on over to the configuration environment to make the settings relevant to our scenario.
For that we need to access the configuration settings named ‘Define Business Transaction Control’, in the area of Manufacturing.
The configuration presents as below:
- We will first define a profile
- Then define the business transaction controls
First, we create a profile. Note that we opted for the node type ‘Process Order Header’. We could also have chosen the node type ‘Process Order Operation’. In fact, you could maintain both entries – one for the header node, and one for the operation node.
Also note, that the naming convention of profiles has to begin with ZPP.
We then select the newly created profile and navigate to the ‘Define Business Transaction Controls’ folder. Here we define the Business Transactions Controls we wish to setup.
As a reminder, we want to setup the system so as to prevent Goods Movements once the order is technically completed.
We have here named, i.e given a code and description to the Business Transaction Control. Note that the Activate check box has not been set to ‘active’, meaning it is not active by default.
Next, we select the newly created Business Control and drill down to the Define Activating/Deactivating BTs folder.
Here we have defined 2 steps, meaning:
- The first line defines that we want to activate the blocking of the transaction we will define in the next step if the order is ‘Technically Completed’
- The second line defines that we should de-activate the blocking of the transaction we will define in the next step if the technical completion of the order is reversed.
In plain English, this means that when the process order is TECO (Technically Completed), this will activate the business transaction control we defined in the previous step. Similarly, if we revoke the ‘TECO’ Status of the process order, then this will deactivate the business transaction control previously defined.
As the last step, we need to define the transactions that we want to block per se, once the order is ‘Technically Completed’. For that, we go to the next folder, named ‘Define Business Transactions to Be Blocked’.
As seen below, we will have added three entries, that will in effect block all goods movements against orders that have the TECO status – whether the goods movement is an issue or receipt. Note that you could have only chosen issues or receipts.
At this point, we have finished the creation of our profile, but in order to use it, we need to assign it to the order type, that we want to leverage this profile. This will ensure that your profile is always applied to your process orders.
For that, we go to the configuration setting ‘Define Process Order Type’. Here, for your chosen process order type(s) add the name of your profile, under the ‘Status Management’ section, as shown below.
Now that the settings have been made, we can make use of them.
To see it in action, we will first assign the TECO (Technically Complete) status on a process order (that we created after the above settings were made !)
As soon as we Technically Complete the order, we note in the header, that the Business Transaction Control – NMTE – we defined earlier has been automatically applied to the order.
To check that this status will indeed block goods movements on this process order, let’s try to perform a goods issue against it.
As soon as we enter the process order, we get an error message advising us that the order status forbids the processing of goods movement.
We now go back to the process order and revoke the Technical Completion status. This, if you recall should also de-activate the blocking of the goods movements against our order.
As you can see, once we revoke the TECO status, the user status NMTE is also removed.
Now that we have made this change, let’s once again try to process a goods movement on our order.
This time, we are able to process the goods movement. The error message is no longer displayed and the planned goods movements are proposed.
I hope this example has enabled your understanding of how this feature works and maybe given you ideas on it can fulfill requirements you may have.
You may also want to read more on this capability: