Bypass an optional operation

[former_member323997]

Hello,

We have a business scenario like, the router we defined is OP1->OP2->OP3, and the OP2 is an optional operation, which means, when the SFC is completed at OP1, and the operator (and only the operator) will decide it should go to OP2 or OP3. if operator decides to start at the OP3 then there is no need to do the start/complete at OP2 anymore.

Is there a solution like this in SAP ME? We are not using the POD to do the start and complete, but the customized client with PAPI to send the all requests.

Thanks & regards,

Leon

[sergiy_katerinich · Accepted solution]

Hi Leon,

Then you have a different routing rather than OP1->OP2->OP3. It looks like OP1->OP3 and OP1->OP2, and then OP2->OP3. Then I guess standard PAPI for Start and Complete should be enough to let you decide where go to OP3 or to OP2 after completion of OP1.

Regards,

Sergiy

[former_member323997 · Accepted solution]

Hi Sergiy,

Can you please advice more how the standard PAPI for start/complete know which operation should go, OP2 or OP3? e.g. the bellow routing. When I send the complete of OP_AOI_1, it throw exception because the system does not know what is the next possible operation?

And what we want is, if the operator takes the SFC on the OP_AOI_3 and send start/complete it works properly; if the operator takes it to the OP_AOI_2 and send the start/complete, it also works properly.

[sergiy_katerinich · Accepted solution]

In completeSfc, there is nextStep tag where you should specify either OP2 or OP3.

[former_member323997 · Accepted solution]

If you are referring to the completeSfc at OP1 then this is not what we want. Because at OP1, no one knows the SFC should go to the OP2 or OP3.

Thanks & regards,

Leon

[sergiy_katerinich · Accepted solution]

Then it means that OP1 should be configured with Queue Decision = Next Operator. And you do not need to specify nextStep value.

If this config fails, then it is a bug.

[Roman_Freidel · Accepted solution]

Leon,

1.) try to set the "Queue Desicion" to "Next Operator.

This determines which operator decides where the SFC number should be queued after it completes this routing step

• Completing Operator
  The operator completing the SFC number at this routing step determines where the SFC number is put in queue.
• Next Operator
  The operator at the next routing step determines where to start work on the SFC number. The SFC number is placed in queue at all the next routing steps and the first operator to start it controls where the SFC number is processed.
  

2. )As a second option you could check with a PAPI if the SFC is in queue at step e.g. Pack-RF and do a PlaceInQueueAtStep with a bypass and then you can run your regular things.

Roman

[former_member323997 · Accepted solution]

It works as expected. Thank you, Sergiy.

[former_member323997 · Accepted solution]

Thanks, Roman. The first option seems working as we wanted by our business.

thanks & regards,

Leon