1. REST API for Oracle Fusion Cloud SCMREST API for Oracle Fusion Cloud SCM
  2. Use Cases
  3. Supply Chain Planning
  4. Manage Production Schedule Setup Data

Manage Production Schedule Setup Data

You can manage production schedule setup data within an inventory organization by using the Production Scheduling Organizations REST resource. The setup data is required to drive the desired schedule behavior and a prerequisite to refreshing a production schedule.

Here's a typical application processing flow for the scenarios:

  1. Add a scheduling organization to create a schedule
  2. Refresh data for an organization
  3. Assign colors to attribute values
  4. Enable an attribute to be used for highlighting
  5. Create attribute-based changeover data
  6. Define user-defined attribute sequences
  7. Manage resource groups to group resources to aid in schedule analysis
  8. Add a resource to a resource group

Add an Organization to Create a Schedule

Let's say Richard Jones wants to add an organization to allow the creation of a schedule within an organization. A schedule organization is required to setup data common to an organization.

Example URL

Use this resource URL format.

POST

curl -u username:password POST 'https://servername/fscmRestApi/resources/version/ productionSchedulingOrganizations--header 'Content-Type: application/json' -d 'request payload'

Example Request

Here's an example of the request body in JSON format. You can get the organization identifier from the Inventory Organization REST resource.

{
	"OrganizationId": 100000011265067,
	"OrganizationCode": "ASW"
	
}

Example Response

Here's an example of the response body in JSON format.

{
	"OrganizationId": 100000011265067,
	"OrganizationCode": "ASW",
	"OrganizationName": null,
	"Timezone": null,
	"RequestInProcessFlag": null,
	"RefreshStatus": null,
	"RefreshStartDate": null,
	"RefreshEndDate": null,
	"RefreshRequestId": null,
	"RefreshErrorCode": null,
	"CreatedBy": "PRODUCTION_SCHEDULER",
	"CreationDate": "2020-10-19T14:13:42+00:00",
	"LastUpdatedBy": "PRODUCTION_SCHEDULER",
	"LastUpdateDate": "2020-10-19T14:13:42.086+00:00",
	"LastUpdateLogin": "B1152168B4BE6945E0534005F00A9B23",
	"links": [
		{
			"rel": "self",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067",
			"name": "productionSchedulingOrganizations",
			"kind": "item"
		},
		{
			"rel": "canonical",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067",
			"name": "productionSchedulingOrganizations",
			"kind": "item"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/attributes",
			"name": "attributes",
			"kind": "collection"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/changeoverRules",
			"name": "changeoverRules",
			"kind": "collection"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/itemClassAttributeGroups",
			"name": "itemClassAttributeGroups",
			"kind": "collection"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/itemParameters",
			"name": "itemParameters",
			"kind": "collection"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/manufacturingAttributeGroups",
			"name": "manufacturingAttributeGroups",
			"kind": "collection"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/resourceAttributeSequences",
			"name": "resourceAttributeSequences",
			"kind": "collection"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/resourceAttributes",
			"name": "resourceAttributes",
			"kind": "collection"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/resourceGroups",
			"name": "resourceGroups",
			"kind": "collection"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/resourceParameters",
			"name": "resourceParameters",
			"kind": "collection"
		},
		{
			"rel": "child",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/child/resourceRelationships",
			"name": "resourceRelationships",
			"kind": "collection"
		},
		{
			"rel": "action",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/100000011265067/action/refreshOrganizationData",
			"name": "refreshOrganizationData",
			"kind": "other"
		}
	]
}

Refresh Data for a Scheduling Organization

Richard can refresh data for an organization. This primarily includes the work order operation descriptive flexfields and item extensible flexfield that need to be referenced in changeovers, user defined sequences, and attribute value colors.

Example URL

Use this resource URL format.

POST

curl -u username:password POST 'https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209' --header 'Content-Type: application/vnd.oracle.adf.action+json' -d 'request payload'

Example Request

Here's an example of the request body in JSON format. You can get the catalog identifier and category identifier the Items Version 2 resource.

{
	"name": "refreshOrganizationData"
}

Example Response

Here's an example of the response body in JSON format.

{
	"result": "145054"
}

The response includes the scheduled processes request identifier.

Assign Color to Attribute Values

Example URL

Use this resource URL format.

POST

Note:

The AttributeId and AttributeValueId section of the URL can be obtained from the links section of the attributes and attribute values REST call respectively. 
curl -u username:password POST 'https://servername/fscmRestApi/resources/version/ productionSchedulingOrganizations/209/child/attributes/00020000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F18/child/attributeValues/00030000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F180000000EACED0005770800000000000824F2' --header 'Content-Type: application/vnd.oracle.adf.action+json' -d 'request payload'

Example Request

Here's an example of the request body in JSON format.

Note:

Color is specified using hexadecimal format. 
{
	"OrganizationId": 209,
	"AttributeId": 3008,
	"AttributeValueId": 441627,
	"Color": "#c0c0c0"

Example Response

Here's an example of the response body in JSON format.

{
	"OrganizationId": 209,
	"AttributeId": 100100214820632,
	"AttributeValueId": 533746,
	"AttributeValueCode": "White",
	"AttributeValueName": null,
	"Description": null,
	"Color": "#c0c0c0",
	"CreatedBy": "PRODUCTION_SCHEDULER",
	"CreationDate": "2020-10-19T15:16:05.173+00:00",
	"LastUpdatedBy": "PRODUCTION_SCHEDULER",
	"LastUpdateDate": "2020-10-20T16:22:28+00:00",
	"LastUpdateLogin": "B1153CFF789B6943E0534005F00AADA5",
	"links": [
	{
		"rel": "self",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/attributes/00020000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F18/child/attributeValues/00030000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F180000000EACED0005770800000000000824F2",
		"name": "attributeValues",
		"kind": "item"
	},
	{
		"rel": "canonical",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/attributes/00020000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F18/child/attributeValues/00030000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F180000000EACED0005770800000000000824F2",
		"name": "attributeValues",
		"kind": "item"
	},
	{
		"rel": "parent",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/attributes/00020000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F18",
		"name": "attributes",
		"kind": "item"
	}
	]
}

Enable Attribute to be Used for Highlighting

Richard can enable an attribute to be used for highlighting. While there may be many attributes in the model, Richard may only want to highlight the schedule with a few of them.

Example URL

Use this resource URL format.

Note:

The AttributeId and AttributeValueId section of the URL can be obtained from the links section of the attributes and attribute values REST call respectively.

POST

curl -u username:password PATCH 'https://servername/fscmRestApi/resources/version/ productionSchedulingOrganizations/209/child/attributes/00020000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F18' --header 'Content-Type: application/ json' -d 'request payload'

Example Request

Here's an example of the request body in JSON format.

Note:

Color is specified using the hexadecimal format. 
{
			"HighlightAttributeFlag": true
}

Example Response

Here's an example of the response body in JSON format.

{
	"OrganizationId": 209,
	"AttributeId": 100100214820632,
	"AttributeCode": "Process Color:Scheduling Extrusion Process(WIS_WD_OPERATIONS_B)",
	"Description": "Process Color",
	"DefaultAttributeValueId": null,
	"DefaultAttributeValueCode": null,
	"HighlightAttributeFlag": true,
	"DescriptiveFlexfieldCode": "WIS_WD_OPERATIONS_B",
	"FlexfieldContextCode": "Scheduling Extrusion Process",
	"SegmentCode": "Process Color",
	"ValueSetId": 193584,
	"CreatedBy": "PRODUCTION_SCHEDULER",
	"CreationDate": "2020-10-19T15:16:05.058+00:00",
	"LastUpdatedBy": "PRODUCTION_SCHEDULER",
	"LastUpdateDate": "2020-10-20T16:47:05+00:00",
	"LastUpdateLogin": "B11520F7D3826929E0534005F00A7953",
	"links": [
	{
		"rel": "self",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/attributes/00020000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F18",
		"name": "attributes",
		"kind": "item"
	},
	{
		"rel": "canonical",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/attributes/00020000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F18",
		"name": "attributes",
		"kind": "item"
	},
	{
		"rel": "parent",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209",
		"name": "productionSchedulingOrganizations",
		"kind": "item"
	},
	{
		"rel": "child",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/attributes/00020000000EACED0005770800000000000000D10000000EACED0005770800005B0A65BF0F18/child/attributeValues",
		"name": "attributeValues",
		"kind": "collection"
	}
	]
}

Create an Attribute-Based Changeover Records

Richard can create changeover records as part of the changeover matrix that is used by production scheduling when creating a schedule. This table lists the attributes for a changeover record along with the generic value, identifier, and the source REST resource. Typically, there are numerous records to define the different changeover rules by attribute and resource. The changeovers must be unique by organization and Changeover Sequence Number.

Attribute Value Identifier Resource
OrganizationId M1 207 inventoryOrganizations
WorkCenterId Painting 300100075230242 WorkCenters
ResourceId Paint Booth 300100075230242 WorkCenterResources
AttibuteId Color 3004 productionSchedulingOrganizations/{OrganizationId}/child/attributes
FromAttributeValueId Blue 437070 productionSchedulingOrganizations/{OrganizationId}/child/attributes/{attributesUniqId}/child/attributeValues
ToAttributeValueId Green 437071 productionSchedulingOrganizations/{OrganizationId}/child/attributes/{attributesUniqId}/child/attributeValues

Example URL

Use this resource URL format.

PATCH

curl -u username:password PATCH 'https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/changeoverRules' --header 'Content-Type: application/json' -d 'request payload'

Example Request

Here's an example of the request body in JSON format.

{
	"OrganizationId": 207,
	"ChangeoverSequenceNumber": 10,
	"WorkCenterId": 300100075230242,
	"ResourceId": 300100075230242,
	"AttributeId": 3004,
	"FromAttributeValueId": 437070,
	"ToAttributeValueId": 437071,
	"Duration": 60,
	"DurationUnit": "minutes"

}

Example Response

Here's an example of the response body in JSON format.

{
	"OrganizationId": 207,
	"ChangeoverId": 300100233885278,
	"ChangeoverSequenceNumber": 10,
	"WorkCenterId": 300100075230242,
	"ResourceId": 300100075230242,
	"WorkCenterCode": null,
	"ResourceCode": null,
	"WorkCenterName": null,
	"ResourceName": null,
	"GroupId": null,
	"GroupCode": null,
	"AttributeId": 3004,
	"AttributeCode": null,
	"FromAttributeValueId": 437070,
	"FromAttributeValueCode": null,
	"ToAttributeValueId": 437071,
	"ToAttributeValueCode": null,
	"Duration": 3,
	"DurationUnit": "hour",
	"Cost": 1,
	"CreatedBy": "PRODUCTION_SCHEDULER",
	"CreationDate": "2020-10-19T16:45:34+00:00",
	"LastUpdatedBy": "PRODUCTION_SCHEDULER",
	"LastUpdateDate": "2020-10-19T16:45:34.004+00:00",
	"LastUpdateLogin": "B11522D5CEE46939E0534005F00A36C7",
	"links": [
	{
		"rel": "self",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/606/child/changeoverRules/300100233885278",
		"name": "changeoverRules",
		"kind": "item"
	},
	{
		"rel": "canonical",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/606/child/changeoverRules/300100233885278",
		"name": "changeoverRules",
		"kind": "item"
	},
	{
		"rel": "parent",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/606",
		"name": "productionSchedulingOrganizations",
		"kind": "item"
	}
	]
}

Create a User-Defined Attribute Sequence

In this scenario, you can specify the attribute value order that is desired when generating the schedule. An example is attributes of Color and Size. You may want to schedule from light to dark for Color and Small to Large for Size such as (White, Small), (White, Medium), (White, Large), (Green, Small), (Green, Medium), (Green, Large), (Black, Small). In this case, the schedule sequence is respected within a schedule bucket as defined in your schedule options. The sequence is defined at two levels.

  • Attribute level. Define what order to sequence the attributes. For example, sequence by Color and then, within Color, sequence by Size.
  • Within an Attribute, define the sequence by attribute value. For example, for Color sequence from light to dark (White -> Green -> Black).

First, define the attribute sequence.

Example URL

Use this resource URL format.

POST

curl -u username:password POST 'https://servername:port/fscmRestApi/resources/version/ productionSchedulingOrganizations/209/child/attributeSequences --header 'Content-Type: application/ --header 'REST-Framework-Version: 8' json' -d 'request payload'

Example Request at the Attribute Level

Here's an example of the request body in JSON format. The Color is the first attribute to consider in the example hence Attribute Sequence Number of 10. Sequence are ordered numerically in ascending order. Size would be the next attribute where the Attribute Sequence Number should be greater than 10.

The Cycle Rule attribute can have the following values:

  • RestartSequence: Restart the sequence of attribute values at the start of a scheduling bucket. In the example, White work order operations would be scheduled at the start of the scheduling bucket since it is the first attribute value in the sequence.
  • ContinueSequence: Continue the sequence of attribute values from the prior scheduling bucket. In the example, if the prior week ended with Green then that would be the first Color to schedule in the subsequence week.
  • ReverseSequence: Reverse sequence allows the cycle to reverse in the subsequent schedule bucket. This allows you to cycle from light to dark Colors and than from dark to light. When using Reverse Sequence, the changeover times and cost in the changeover matrix should be defined.

The GenerateValueSequenceFlag defaults to false. When set to true, it automatically assigns sequence numbers to the attribute values to support the user interface. It is recommended to retain the default value. 

 {
            "OrganizationId": 209,
            "WorkCenterId": 300100209046811,
            "ResourceId": 300100209046817,
            "AttributeId": 100100240233675,
            "WorkCenterCode": "RBPS_EXTRU_WC1",
            "ResourceCode": "RBPS-INJMOLD2",
            "AttributeSequenceNumber": 10,
            "GenerateValueSequencesFlag": true,
            "CycleRule": "ReverseSequence"
        }
Field SCM REST
OrganizationId inventoryOrganizations
WorkCenterId WorkCenters
ResourceId WorkCenterResources
AttributeId productionSchedulingOrganizations/{OrganizationId}/child/attributes

Example Response

Here's an example of the response body in JSON format.

{
            "OrganizationId": 209,
            "WorkCenterId": 300100209046811,
            "ResourceId": 300100209046815,
            "AttributeId": 100100240233675,
            "WorkCenterCode": "RBPS_EXTRU_WC1",
            "ResourceCode": "RBPS-INJMOLD1",
            "WorkCenterName": "RBPS_EXTRU_WC1",
            "ResourceName": null,
            "AttributeSequenceNumber": 10,
            "AttributeCode": "Process Color:Scheduling Extrusion Process(WIS_WD_OPERATIONS_B)",
            "AttributeDescription": "Process Color",
            "DescriptiveFlexfieldCode": "WIS_WD_OPERATIONS_B",
            "FlexfieldContextCode": "Scheduling Extrusion Process",
            "SegmentCode": "Process Color",
            "GenerateValueSequencesFlag": null,
            "CycleRule": "RestartSequence",
            "CreatedBy": "PRODUCTION_SCHEDULER",
            "CreationDate": "2021-04-06T14:49:33+00:00",
            "LastUpdatedBy": "PRODUCTION_SCHEDULER",
            "LastUpdateDate": "2021-04-06T15:26:32+00:00",
            "LastUpdateLogin": "BE98288A63509B36E0535EBFF20A4F2B",
            "@context": {
                "key": "209,300100209046811,300100209046815,100100240233675",
                "links": [
                    {
                        "rel": "self",
                        "href": "https://servername:port/fscmRestApi/resources/11.13.18.05/productionSchedulingOrganizations/209/child/attributeSequences/209%2C300100209046811%2C300100209046815%2C100100240233675",
                        "name": "attributeSequences",
                        "kind": "item"
                    },
                    {
                        "rel": "canonical",
                        "href": "https://servername:port/fscmRestApi/resources/11.13.18.05/productionSchedulingOrganizations/209/child/attributeSequences/209%2C300100209046811%2C300100209046815%2C100100240233675",
                        "name": "attributeSequences",
                        "kind": "item"
                    },
                    {
                        "rel": "parent",
                        "href": "https://servername:port/fscmRestApi/resources/11.13.18.05/productionSchedulingOrganizations/209",
                        "name": "productionSchedulingOrganizations",
                        "kind": "item"
                    },
                    {
                        "rel": "child",
                        "href": "https://servername:port/fscmRestApi/resources/11.13.18.05/productionSchedulingOrganizations/209/child/attributeSequences/209%2C300100209046811%2C300100209046815%2C100100240233675/child/attributeValueSequences",
                        "name": "attributeValueSequences",
                        "kind": "collection"
                    }
                ]

Once the attribute sequence is defined, the attribute value sequences can be defined.

Example URL

Use this resource URL format.

curl -u username:password POST 'https://servername:port/fscmRestApi/resources/version/ productionSchedulingOrganizations/209/child/attributeSequences/ 209%2C300100209046811%2C300100209046817%2C100100240233675/child/attributeValueSequences --header 'Content-Type: application/ json' --header 'REST-Framework-Version: 8' -d 'request payload'

The attribute sequence object identifier is the URL encoded value of the key.

Example Request at the Attribute Value Level

Here's an example of the request body in JSON format. White is the first attribute value to be sequenced within a schedule bucket.

        {
            "OrganizationId": 209,
            "WorkCenterId": 300100209046811,
            "ResourceId": 300100209046817,
            "AttributeId": 100100240233675,
             "AttributeValueId": 533746,
            "AttributeValueSequenceNumber": 10

        }
Field SCM REST
OrganizationId inventoryOrganizations
WorkCenterId WorkCenters
ResourceId WorkCenterResources
AttributeId productionSchedulingOrganizations/{OrganizationId}/child/attributes
AttributeValueId productionSchedulingOrganizations/{OrganizationId}/child/attributes/{attributesUniqID} /child/attributeValues

Example Response

Here's an example of the response body in JSON format.

{
            "OrganizationId": 209,
            "WorkCenterId": 300100209046811,
            "ResourceId": 300100209046817,
            "AttributeId": 100100240233675,
            "AttributeValueId": 533746,
            "AttributeValueSequenceNumber": 10,
            "AttributeValueCode": "White",
            "AttributeValueName": null,
            "CreatedBy": "PRODUCTION_SCHEDULER",
            "CreationDate": "2021-04-08T13:59:09.132+00:00",
            "LastUpdatedBy": "PRODUCTION_SCHEDULER",
            "LastUpdateDate": "2021-04-08T13:59:09.192+00:00",
            "LastUpdateLogin": "BE9828DC87499B3CE0535EBFF20AEA5D",
            "@context": {
                "key": "209,300100209046811,300100209046817,100100240233675,533746",
                "links": [
                    {
                        "rel": "self",
                        "href": "https://servername:port/fscmRestApi/resources/11.13.18.05/productionSchedulingOrganizations/209/child/attributeSequences/209%2C300100209046811%2C300100209046817%2C100100240233675/child/attributeValueSequences/209%2C300100209046811%2C300100209046817%2C100100240233675%2C533746",
                        "name": "attributeValueSequences",
                        "kind": "item"
                    },
                    {
                        "rel": "canonical",
                        "href": "https://servername:port/fscmRestApi/resources/11.13.18.05/productionSchedulingOrganizations/209/child/attributeSequences/209%2C300100209046811%2C300100209046817%2C100100240233675/child/attributeValueSequences/209%2C300100209046811%2C300100209046817%2C100100240233675%2C533746",
                        "name": "attributeValueSequences",
                        "kind": "item"
                    },
                    {
                        "rel": "parent",
                        "href": "https://servername:port/fscmRestApi/resources/11.13.18.05/productionSchedulingOrganizations/209/child/attributeSequences/209%2C300100209046811%2C300100209046817%2C100100240233675",
                        "name": "attributeSequences",
                        "kind": "item"
                    }
                ]
            }
        }

Create a Resource Group to filter the Gantt Chart by resource

Richard can setup a resource group that is used to filter the Gantt Chart by only the resources defined within the group. This filters and orders the Gantt Chart to show the resources of interest and also can have significant performance implications because this limits the amount of data that is displayed in the application.

Example URL

Use this resource URL format.

Note:

The AttributeId and AttributeValueId section of the URL can be obtained from the links section of the attributes and attribute values REST call respectively.

POST

curl -u username:password POST 'https://servername/fscmRestApi/resources/version/ productionSchedulingOrganizations/209/child/resourceGroups' --header 'Content-Type: application/ json' -d 'request payload'

Example Request

Here's an example of the request body in JSON format.

{
	"OrganizationId": 209,
	"GroupCode": "Constrained Resources",
	"Description": "Show only Constrained Resources"
}

Example Response

Here's an example of the response body in JSON format.

{
	"OrganizationId": 209,
	"GroupId": 300100235053334,
	"GroupCode": "Constrained Resources",
	"Description": "Show only Constrained Resources",
	"CreatedBy": "PRODUCTION_SCHEDULER",
	"CreationDate": "2020-10-21T14:34:24+00:00",
	"LastUpdatedBy": "PRODUCTION_SCHEDULER",
	"LastUpdateDate": "2020-10-21T14:34:24.119+00:00",
	"LastUpdateLogin": "B1157A9032B0693BE0534005F00A4B2D",
	"links": [
	{
		"rel": "self",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/resourceGroups/300100235053334",
		"name": "resourceGroups",
		"kind": "item"
	},
	{
		"rel": "canonical",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/resourceGroups/300100235053334",
		"name": "resourceGroups",
		"kind": "item"
	},
	{
		"rel": "parent",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209",
		"name": "productionSchedulingOrganizations",
		"kind": "item"
	},
	{
		"rel": "child",
		"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/resourceGroups/300100235053334/child/groupMembers",
		"name": "groupMembers",
		"kind": "collection"
	}
	]
}

Add a Resource to a Resource Group

Richard can now add a resource to a resource group and define the order the resource should be displayed. The order is important because the order of display in the resource Gantt is typically desired by how the product flows through the factory.

Example URL

Use this resource URL format.

Note:

The AttributeId and AttributeValueId section of the URL can be obtained from the links section of the attributes and attribute values REST call respectively.

POST

curl -u username:password POST 'https://servername/fscmRestApi/resources/version/ productionSchedulingOrganizations/ 209/child/resourceGroups/300100235053334/child/groupMembers' --header 'Content-Type: application/ json' -d 'request payload'

Example Request

Here's an example of the request body in JSON format. In this example, the resource displays first in the Resource Gantt since the Member Sequence Number is 1.

{
	"OrganizationId": 209,
	"GroupId": 300100235053334,
	"WorkCenterId": 300100209046815,
	"ResourceId": 300100209046815,
	"MemberSequenceNumber": 1
}

Example Response

Here's an example of the response body in JSON format.

{
	"OrganizationId": 209,
	"MemberId": 300100235053712,
	"GroupId": 300100235053334,
	"WorkCenterId": 300100209046815,
	"ResourceId": 300100209046815,
	"WorkCenterCode": null,
	"ResourceCode": null,
	"WorkCenterName": null,
	"ResourceName": null,
	"MemberSequenceNumber": 1,
	"CreatedBy": "PRODUCTION_SCHEDULER",
	"CreationDate": "2020-10-21T14:37:52+00:00",
	"LastUpdatedBy": "PRODUCTION_SCHEDULER",
	"LastUpdateDate": "2020-10-21T14:37:52.098+00:00",
	"LastUpdateLogin": "B1157A9032B0693BE0534005F00A4B2D",
	"links": [
		{
			"rel": "self",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/resourceGroups/300100235053334/child/groupMembers/300100235053712",
			"name": "groupMembers",
			"kind": "item"
		},
		{
			"rel": "canonical",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/resourceGroups/300100235053334/child/groupMembers/300100235053712",
			"name": "groupMembers",
			"kind": "item"
		},
		{
			"rel": "parent",
			"href": "https://servername/fscmRestApi/resources/version/productionSchedulingOrganizations/209/child/resourceGroups/300100235053334",
			"name": "resourceGroups",
			"kind": "item"
		}
	]
}