One order里user status和system status的mapping逻辑

版权声明：本文为博主汪子熙原创文章，未经博主允许不得转载。 https://blog.csdn.net/i042416/article/details/89704092

Below example show: How the mapping relationship between User status and System status maintained in One Order.
APP: My Opportunity
Transaction type: OPSM
First,I create an new Opportunity in WebClientUI, I set the status with E0001( User status).
新建一个Opportunity，将其status 设置成E0001( User status)：

After I saved the Opportunity, in the DB, I can find both user status E0001 - Open and system status I1002 there.
保存之后，在数据库里针对该Opportunity不仅仅存储了用户手动选择的user status E0001 - Open，还保存了如下的system status I1002：

Second,How the mapping relationship between User status and System status maintained in One Order?
这个user status到system status的mapping 逻辑：
Step1. Under transaction type OPSM, we can find status profile.
找到transaction type OPSM 对应的status profile：

Step2. In the status profile, we can find the business transaction OPEN of user status.
找到该 user status对应的business transaction OPEN:

Step3.Based on the business transaction OPEN, we will
select system status
from TJ06
where VRGNG = business transaction OPEN
and INACT not equal X
系统从step2里取得business transaction之后，根据VRGNG = transaction的逻辑到TJ06里去查找所有结果INACT不为X的entry，结果即为该user status对应的所有
system status

Then,The configure point for table TJ06: tcode BS32
TJ06 表里的entry通过tcode BS32维护：

Finally,You can find below 3 steps in below function module.
上述三步系统的执行逻辑可以通过debug如下的function module来学习：

要获取更多Jerry的原创文章，请关注公众号"汪子熙":