|
Http Verb |
GET |
|---|---|
|
Url |
/integration/territory/organizational-structures/r1/work-centers/{workCenterCode}/operation-centers |
|
Permissions required |
Core Additional Parameters: Edit (fsm.core.additionalparameter.edit) WO Configuration: View (fsm.core.workorder.configuration.view) or WO Configuration: Edit (fsm.core.workorder.configuration.edit) |
|
Last Modified Version |
r1 |
|
Tech Tags |
MULTILANGUAGE-FIELDS |
|
Available Async |
No |
BPMN Diagram
Business Logic
This Integration API retrieves the value of Operation Center starting from Work Center.
System verifies Permission Required and starts the elaboration that is organized in steps.
STEP 1 - External System Validation
System takes Input fields and checks their existence in internal configuration.
API Verb: GET
Resource: External Systems
Input: externalSystemCode, active=true
Output: externalSystemId
If System can obtain the Output fields → continue to next step.
If System can’t obtain the Output fields → responds with error. Elaboration is stopped.
STEP 2 - Work Center Validation
System takes Input fields and checks their existence in internal configuration.
API Verb: GET
Resource: Work Centers
Input: workCenterCode
Output: workCenterId, description, active
If System can obtain the Output fields → continue to the next step
If System can’t obtain the Output fields → responds with error. Elaboration is stopped.
STEP 3 - Operation Center Validation
System takes Input fields and checks their existence in internal configuration.
API Verb: GET
Resource: /{workCenterId}/operation-centers
Input: workCenterId
Output: operationCenterId
If System can obtain the Output fields → continue to next step.
If System can’t obtain the Output fields → responds with error. Elaboration is stopped.
STEP 4 - Operation Center Retrieve
API Verb: GET
Resource: Operation Centers
Input: operationCenterId
Output: operationCenterCode, operationCenterDescription, active
If System can obtain the Output fields → continue to next step.
If System can’t obtain the Output fields → responds with error. Elaboration is stopped.
Error Type:
-
Others - see link in Resource
Path Parameters
As their name suggests, they are included in the URL path of the endpoint.
Not applicable.
Query String Parameters
Start with a ? and includes parameters listed one after the another separated by &.
Filter
|
Field |
Description |
Mandatory |
Constraint |
|
|---|---|---|---|---|
|
1 |
externalSystemCode |
External system code |
Y |
Not Blank |
Fields
The parameter _fields allows to choose output fields. More info here How to use APIs: Output fields selection.
Header Parameters
Parameters included in the request headers. Generally, request headers are used to keep authorization parameters.
Default.
Request example
{baseUrl}/integration/territory/organizational-structures/r1/work-centers/OPE_CEN_001/operation-centers?externalSystemCode=SAP
Response documentation
Response payload fields
|
Field |
Field Type |
Description |
|
|---|---|---|---|
|
1 |
operationCenters |
|
operationCenterObject
|
Field |
Description |
|
|---|---|---|
|
1 |
id |
Operation Center Id |
|
2 |
code |
Operation Center Code |
|
3 |
description |
Operation Center Description |
|
4 |
active |
Flag Active |
Compliant with RFC Standard https://www.rfc-editor.org/rfc/rfc9457.html
Extension fields:
|
Field |
Description |
Note |
|---|---|---|
|
code |
Extension member of a Problem Details Object that contains the error code |
Only for ERROR |
Response example
{
"operationCenters": [
{
"id": 1581,
"code": "WC_MECH_01",
"description": "XXX",
"active": true
},
{
"id": 1581,
"code": "WC_MECH_01",
"description": "XXX",
"active": false
}
]
}
Error example
{
"type": "about:blank",
"title": "Not Found",
"status": 404,
"detail": "External system string does not exist",
"instance": "/integration/workforce/r1/resource-skills",
"code": "IA001_001"
}