CRM status management framework supports the authorization concept as below. Customer can choose that only specific user group (with dedicated PFCG role) contains the authorization to change the status of transaction/activity to specific status, e.g. “Completed” and “Cancelled”. Other user group (with different PFCG role) can only change status to status like “In Process”. This feature is implemented via so called Authorization Code in IMG activity “Define Status Profile”.
If the respective user status is configured with an authorization code, in the runtime, authorization check will be executed accordingly. But in CRM, there are two different use cases. (1) If end changes the user status directly in Fiori UI (edit page), authorization object “B_USERSTAT” will be used for check.
(2) If user clicks the check box in Fiori search page, authorization object “B_USERST_T” will be used for check.
In my previous blog Build Chart and Table representation via Analytics Path Fram...
简单来说, 仓库模式就是一种存放数据访问逻辑的容器, 它向业务层屏蔽了数据访问逻辑的细节, 在不清楚数据层设计结构的情况下, 我们也能按照业务逻辑来访问数据层。