Shulou(Shulou.com)05/31 Report--

This article mainly explains "what is the mapping logic of user status and system status". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what is the mapping logic of user status and system status".

Create a new Opportunity and set its status to E0001 (User status):

After I saved the Opportunity, in the DB, I can find both user status E0001-Open and system status I 1002 there.

After saving, not only the user status E0001-Open manually selected by the user is stored in the database for this Opportunity, but also the following system status I1002 is saved:

Second,How the mapping relationship between User status and System status maintained in One Order?

The mapping logic from user status to system status:

Step1. Under transaction type OPSM, we can find status profile.

Find the status profile corresponding to transaction type OPSM:

Step2. In the status profile, we can find the business transaction OPEN of user status.

Find the business transaction OPEN corresponding to the user status:

Step3.Based on the business transaction OPEN, we will select system status from TJ06

Where VRGNG = business transaction OPEN

And INACT not equal X

After getting the business transaction from step2, the system searches TJ06 for all the entry whose INACT is not X according to the logic of VRGNG = transaction. The result is all the system status corresponding to the user status.

Then,The configure point for table TJ06: tcode BS32

The entry in the TJ06 table is maintained through tcode BS32:

Finally,You can find below 3 steps in below function module.

The execution logic of the above three-step system can be learned through the following function module of debug:

Look at another example:

When you create a Task, the status you can choose is based on the status profile of the Task. Eventually, you will see that there are various user status corresponding to the task transaction in the Table TJ30, including released:

However, there is no such user status in the drop down list of WEB UI's new task:

This is because on Web UI, although the status in drop down list is from TJ30, there is also a status check for the new transaction during this period. In Table TJ07 or Tcode BS22, there is a mapping between user status and system status:

Where i1030 is system status, its corresponding releases this user status configuration is forbidden, which means that when there is an error on the transaction, changing the state of the transaction to released is prohibited. Therefore, when you create a new task on Web UI, because there are still many fields to be maintained, the system status of transaction is in the status of contains error-I1030. Every change operation on Page will trigger a status check. Once there is a status of I1030, the corresponding released user status will be removed from the drop down list.

If all required fields are maintained to ensure that transaction does not have error,released status, it will appear in drop down list:

Thank you for your reading, the above is the content of "what is the mapping logic of user status and system status". After the study of this article, I believe you have a deeper understanding of what the mapping logic of user status and system status is, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.