The main purpose of this blog post is to explain how to create a status profile and how to configure the logic for an automatic status update.
The status profile is required when the system status does not provide/has the required statuses to meet the requirement. Using a status profile we can create our own status and use it in desired functionality. For Example, creating a status profile and using it in Quality Notification
Assuming that there is a requirement of the creation of a custom status profile and assigning it in the Stability Studies Quality Notification process so that a more detailed status of the quality notification can be displayed.
Status profile creation with multiple statuses displayed at the same time.
1. Create a status profile.
Here in this case status profile – ZQM_SS1 is created.
2. Define the statuses in the status profile
In this status profile, I have defined the following statuses with the description/ short text as per the requirement. Please make a point that at a time only 8 status can be displayed simultaneously.
Meaning of the fields
Ini. St- initial status.
This checkbox is used to make the selected status as the initial status, let us say when the notification is created the initial status will be CRIS in the user status section.
Priority and position
As you can see in the screenshot that each status has a position and a priority assigned to it. As stated in the standard documentation that only 8 status can be displayed at a time, so the position field decides which status will occupy which position starting from the left.
If 2 or more status is having the same position, then the priority field will decide which status is to be displayed in that position.
Example.
For the above table, we can see that C has a higher priority than A & B. if at a particular instance of time all the three statuses are active for position 1 then only status “c” will be displayed.
3. Assign Object type.
Go to the path in the menu bar as shown in the screenshot and select the object type from the list. the choice of the object type decides which business transaction can be assigned to individual statuses in status profile.
As per the requirement of stability study I have selected “Notification” as shown in the below screenshot.
4. Assign business transaction control to each status.
The business that can be assigned to the status depends on the object type assigned in the status profile
Meaning of the fields.
Allowed – This Radio Button allows the transaction to be executed when this Status is Set. i.e when status CRIS is set in the status profile. All the transaction mentioned in this status as allowed will only be allowed to be executed.
Warning – This Radio Button allows the transaction to be executed with warning when this Status is Set. i.e when status CRIS is set in the status profile. All the transaction mentioned in this status as “allowed” will only be allowed to be executed with a warning message
Forbidden – This Radio button does not the transaction to be executed if this particular user status is set.
No influence – The execution of the business transaction has no influence on this status.
Set – This radio button sets the user status after the execution of the transaction is completed.
Delete: – This Radio deletes this user status after executing the business transaction.
No Action – This radio ensures that the execution of the Transaction does not set/delete the user status.
The logic for an automatic Status update in status profile.
To allow the system to update from one status to other the previous status needs to be assigned in the
As seen from screenshot 1 that at position 1 two user Statuses are assigned having different priorities. The status. For the current use case, the status needs to be updated fro CRIS to ISCF without user intervention.
The status needs to updated to ISCF ( initial sample confirmed) after execution of CRIS ( create Initial sample ) Status. As shown in the above screenshot the above status ISCF has a reference to the previous transaction executed in previous status CRIS.
So as soon as Create initial sample business is executed in CRIS user status, the business transaction serves no purpose in the next user status. So in User Status ISCF the business transaction Create initial Sample is set to “FORBIDDEN” and in the next action Column the Set Radio Button is checked so that after the execution of this business the ISCF user status will be set.
Set Radio button in the next action is used to set the desired user Status after the execution of the transaction
NOTE: the Business transaction marked as allowed can only be executed when this User status is set.
So on a Similar basis, the automatic status update logic is recorded in the status profile giving the reference for previous business transactions executed in the current user status.
Status profile with Status Number
The Logic for automation status update remains the same, but there are slight differences in this method.
As you can see from the above screenshot all the user status have the same position and priority thus we can infer from the above screenshot that only 1 user status can be displayed at a time.
Also, have a look at the 1st column, the status number is mentioned as 1,2,….etc rather than 10,20,…etc because of the system limitation that the max status number can be 99.
Also, take a look at the column lowest and highest.
Lowest mean all the status below the status number specified in this column for a particular user status, cannot be executed.
The highest means all the user status below the number specified can be executed.
Lowest and Highest act as a range for the particular status execution.
Let us take an example for status 3 CRIL ( create a lot for Initial test ), here the lowest is specified as 3 and highest is specified as 11. this means status number 1 & 2 cannot be executed when this particular status is active, all the user status having status number 3 and above can be executed upto status number 11 ).
The rest process is same as that of user status profile with multiple statuses
______________________________________________________________________________
I hope this blog post is helpful for all. This blog post would reduce/eliminate the efforts of creating a custom development for an automatic status update in status profile depending on user action and also educate the use of the status profile and also a step by step guide to creating it.
Okumaya devam et...
The status profile is required when the system status does not provide/has the required statuses to meet the requirement. Using a status profile we can create our own status and use it in desired functionality. For Example, creating a status profile and using it in Quality Notification
Assuming that there is a requirement of the creation of a custom status profile and assigning it in the Stability Studies Quality Notification process so that a more detailed status of the quality notification can be displayed.
Status profile creation with multiple statuses displayed at the same time.
1. Create a status profile.
Here in this case status profile – ZQM_SS1 is created.
2. Define the statuses in the status profile
In this status profile, I have defined the following statuses with the description/ short text as per the requirement. Please make a point that at a time only 8 status can be displayed simultaneously.
Meaning of the fields
Ini. St- initial status.
This checkbox is used to make the selected status as the initial status, let us say when the notification is created the initial status will be CRIS in the user status section.
Priority and position
As you can see in the screenshot that each status has a position and a priority assigned to it. As stated in the standard documentation that only 8 status can be displayed at a time, so the position field decides which status will occupy which position starting from the left.
If 2 or more status is having the same position, then the priority field will decide which status is to be displayed in that position.
Example.
| Status | Priority | Position |
| A | 3 | 1 |
| B | 2 | 1 |
| C | 1 | 1 |
For the above table, we can see that C has a higher priority than A & B. if at a particular instance of time all the three statuses are active for position 1 then only status “c” will be displayed.
3. Assign Object type.
Go to the path in the menu bar as shown in the screenshot and select the object type from the list. the choice of the object type decides which business transaction can be assigned to individual statuses in status profile.
As per the requirement of stability study I have selected “Notification” as shown in the below screenshot.
4. Assign business transaction control to each status.
The business that can be assigned to the status depends on the object type assigned in the status profile
Meaning of the fields.
Allowed – This Radio Button allows the transaction to be executed when this Status is Set. i.e when status CRIS is set in the status profile. All the transaction mentioned in this status as allowed will only be allowed to be executed.
Warning – This Radio Button allows the transaction to be executed with warning when this Status is Set. i.e when status CRIS is set in the status profile. All the transaction mentioned in this status as “allowed” will only be allowed to be executed with a warning message
Forbidden – This Radio button does not the transaction to be executed if this particular user status is set.
No influence – The execution of the business transaction has no influence on this status.
Set – This radio button sets the user status after the execution of the transaction is completed.
Delete: – This Radio deletes this user status after executing the business transaction.
No Action – This radio ensures that the execution of the Transaction does not set/delete the user status.
The logic for an automatic Status update in status profile.
To allow the system to update from one status to other the previous status needs to be assigned in the
As seen from screenshot 1 that at position 1 two user Statuses are assigned having different priorities. The status. For the current use case, the status needs to be updated fro CRIS to ISCF without user intervention.
The status needs to updated to ISCF ( initial sample confirmed) after execution of CRIS ( create Initial sample ) Status. As shown in the above screenshot the above status ISCF has a reference to the previous transaction executed in previous status CRIS.
So as soon as Create initial sample business is executed in CRIS user status, the business transaction serves no purpose in the next user status. So in User Status ISCF the business transaction Create initial Sample is set to “FORBIDDEN” and in the next action Column the Set Radio Button is checked so that after the execution of this business the ISCF user status will be set.
Set Radio button in the next action is used to set the desired user Status after the execution of the transaction
NOTE: the Business transaction marked as allowed can only be executed when this User status is set.
So on a Similar basis, the automatic status update logic is recorded in the status profile giving the reference for previous business transactions executed in the current user status.
Status profile with Status Number
The Logic for automation status update remains the same, but there are slight differences in this method.
As you can see from the above screenshot all the user status have the same position and priority thus we can infer from the above screenshot that only 1 user status can be displayed at a time.
Also, have a look at the 1st column, the status number is mentioned as 1,2,….etc rather than 10,20,…etc because of the system limitation that the max status number can be 99.
Also, take a look at the column lowest and highest.
Lowest mean all the status below the status number specified in this column for a particular user status, cannot be executed.
The highest means all the user status below the number specified can be executed.
Lowest and Highest act as a range for the particular status execution.
Let us take an example for status 3 CRIL ( create a lot for Initial test ), here the lowest is specified as 3 and highest is specified as 11. this means status number 1 & 2 cannot be executed when this particular status is active, all the user status having status number 3 and above can be executed upto status number 11 ).
The rest process is same as that of user status profile with multiple statuses
______________________________________________________________________________
I hope this blog post is helpful for all. This blog post would reduce/eliminate the efforts of creating a custom development for an automatic status update in status profile depending on user action and also educate the use of the status profile and also a step by step guide to creating it.
Okumaya devam et...