Accept/Reject Operations in SAM while EAM_PHASE_MODEL" enabled

[S_K1]

Hello MDK Experts,

We are have requirements to perform accept/reject operations in SAM App while Phase model enabled, But it's giving sync error that "mobile status not supported" but locally it's works fine, Here i'm trying with accept and reject operation only without changing MobileStatus.

Is accept/reject possible in EAM Phase model ?

[Pathik]

Hi, please provide some more information about your use case. Is the user logged in as a Technician or a Supervisor? Are the Accept and Reject mobile statuses been configured in the Config panel in the Mobile Status State machine?

[S_K1]

Yes Prathik, User login as technician. And the Accept/Reject mobile status has been configured in Backend system as well as Syclo configuration.

[S_K1]

Below are the requirement - 

Requirement is to have two additional buttons for accept and reject in operation details screen. In case technician rejects, an additional screen should appear to select reason of rejection. 

Actions in SSAM should trigger operation user status update in S/4 and FSM. For this a new operation user status profile is created 

Requirement for both Accept/Reject buttons 

Accept  

Whenever technician accepts the order operation in SSAM User status “Accept” should be updated against the operation in S/4, This user status should be sent to FSM,.Dispatcher can view “Accept” against the operation in FSM.  Phase and Sub phase should remain as it is i.e. Execution and Ready for Execution. 

Development Approach: 

We are currently working on updating the User Status in the PMMobileStatus entity while keeping the Mobile status unchanged. Here are the results: 

In MDK development for accept and reject we are referring “PMMobileStatus” entity and “UserStatus” property. And below details we are trying to update. 

When User accept operation – ACPD 

In mdk debugging we are getting initial value of UserStatus property (“PMMobileStatus” entity) in assigned operation, whatever available in backend. 

We are performing update entity action, in local (before sync) it’s updating the userstatus accept/reject properly. But while sync we are facing below issues. 

1. Update UserStatus only from SAM - Sync Failed and transaction error is “Mobile Status is mandatory”.
2. Update existing Mobile Status (Ready) & UserStatus from SAM App - Sync failed, and transaction error is “Mobile Status ‘Ready’ not supported”. 
3.  Update Mobile Status & User Status from SAM App - Sync Successful, In backend Only Mobile status updating but not user status. And in trace we can see the record of UserStatus as well as MobileStatus as mentioned in below snapshot.  

[Pathik]

Hi, see my response in Red regarding your issues:

But while sync we are facing below issues. 

1. Update UserStatus only from SAM - Sync Failed and transaction error is “Mobile Status is mandatory”. You should only be updating the Mobile Status from the app. The backend logic will update the user status accordingly.
2. Update existing Mobile Status (Ready) & UserStatus from SAM App - Sync failed, and transaction error is “Mobile Status ‘Ready’ not supported”. Why are you updating the mobile status as Ready? As per your earlier comments you are trying to Accept or Reject.
3.  Update Mobile Status & User Status from SAM App - Sync Successful, In backend Only Mobile status updating but not user status. And in trace we can see the record of UserStatus as well as MobileStatus as mentioned in below snapshot. You should only update the mobile status. What user status is the STARTED mobile status mapped to in the Configuration Panel?