Use ConfirmRework workflow/activity

To be able to use ConfirmRework workflow/activity from Rework, it is needed to use the activity IncrementCounter provided by Ordermanagement.

The ConfirmRework workflow is used in the following scenarios:

ArnP/ScrapWorkflow
HDEV6/RunWorkflowAction
HDEV6/ScrapWorkflow

The following arguments must be passed to the workflow. The workflow returns true or false as the result.

Table 1. ConfirmRework input parameters with example
Name	Direction	Argument type	Example
inCostCenter	In	String	123
inReason	In	String	456
inLocationId	In	String	022200400001100010001
inSerialNumber	In	String	019fe2e4-b53e-4708-9126-3f21644bc9cb
inCounterType	In	Int64	1
inTypeNo	In	String	F005V01834_R2

Configuration of MES Orchestration:

It was tested with the following orchestration version on fe0bci-int-19.de.bosch.com.

<version released="false">4.3.1</version>
<buildVersion>Orchestration_4.3.23082.01</buildVersion>

The ConfirmRework workflow is located in the D:\Opcon\Data\Orchestration_IAS\ directory. Then restart the service.

The function can be tested by making an HTTP POST request to the URL of the Orchestration service (e.g. http://fe0bci-int-19.de.bosch.com:59208/api/workflow/ias). The service should then respond with true or false.

Listing 1. HTTP Body, to test the execution of the ConfirmRework workflow

{
    "identifier": "c258cebb-0144-474a-b38a-ceb2d38d0b6b",
    "action": "ConfirmRework",
    "parameters": {
        "inCostCenter": "123",
        "inReason": "123123",
        "inLocationId": "022200400001100010001",
        "inSerialNumber": "019fe2e4-b53e-4708-9126-3f21644bc9cb",
        "inCounterType": 1,
        "inTypeNo": "F005V01834_R2"
    }
}

Configuration of Order Management

The configuration was done with the Desktop Client. This can be installed via a ClickOnce package. For example http://fe0bci-int-19/ClickOnce/OrderManagement_SRSClient/OrderManagement_SRSClient.application

The setting for creating station orders must be set.

Figure 1. OrderManagement settings

In addition, the use of SerialNumbers must be active in the line, then you can create and release an order in the line (so that the SerialNumbers are created). And the station for the location Id must exist in the line.

Configuration of MACMA

During configuration, it must be noted that the orchestration instance installed on fe0bci-int-19.de.bosch.com uses MACMA on PREP12 - a different instance than Rework. (Rework may have to be configured again here).

Configuration of OSS (ReworkDataSet)

The controls for CostCenter and ScrapReason must be configured in the OSS. These can then be filled after selecting the RootCause and the configured action in the OSS. The values serve as input for the ConfirmRework orkflow.

Figure 2. OSS[] Rework configuration cost center

Figure 3. OSS[] Rework configuration scrap reason

The exported data set ReworkDataSet.xml[] from the OSS (Toolbar function Export) must be made known to the Rework service by uploading it via the portal.