Create one allocation scenario
post
/fscmRestApi/resources/11.13.18.05/bmAllocationScenarios
Request
Header Parameters
-
Metadata-Context: string
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version: string
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
-
Upsert-Mode: string
Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object
-
AllocMeasures: string
Maximum Length:
4000
Value that uniquely identifies an allocation scenario. -
AttributeNamesList: string
Maximum Length:
255
List of attributes names in an allocation scenario. -
AttributeValueIds: string
Maximum Length:
4000
Unique identifier of attribute values in an allocation scenario. -
AttributeValueNamesList: string
Maximum Length:
255
List of value of the attributes used in an allocation scenario. -
DefaultCode: integer
(int32)
Value to indicate if the allocation scenario is default or not. The value 1 indicates that the allocation scenario is default and 2 or 0 indicate that the allocation scenario isn't a default scenario.
-
Description: string
Maximum Length:
240
Description of an allocation scenario. -
IncludeChildLevel: integer
(int32)
Value to indicate if the calculated demand metrics at a parent allocation node need to consider the demands at the child node also. The value 1 indicates that demand at the child nodes will be considered and the value 2 or 0 indicate that demand at the child nodes won't be considered.
-
InventoryItemId: number
Unique identifier of an inventory item specified in an allocation scenario.
-
ItemIds: string
Maximum Length:
4000
Unique identifier of the items specified in an allocation scenario. -
ItemNames: string
Maximum Length:
255
Names of the items specified in an allocation scenario. -
Message: string
Maximum Length:
255
Message that indicates if the allocation scenario was successfully created. -
MetricMeasures: string
Maximum Length:
4000
Measures that are part of the demand satisfaction metrics in an allocation. -
Name: string
Maximum Length:
80
Name of an allocation scenario. -
NumberOfBuckets: integer
(int32)
Number of buckets specified in an allocation scenario.
-
ObjectVersionNumber: integer
(int32)
Value to indicate the changed version of an allocation scenario for every edit and save made by the user.
-
OrganizationCodes: string
Maximum Length:
255
Code of the organizations specified in an allocation scenario. -
OrganizationIdList: string
Maximum Length:
4000
List of the organization identifier specified in an allocation scenario. -
OwnedBy: string
Maximum Length:
64
Name of the user who owns the allocation scenario. -
ScenarioId: integer
(int64)
Unique identifier of an allocation scenario.
-
StartDate: string
(date)
Date when an allocation scenario starts.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Root Schema : bmAllocationScenarios-item-response
Type:
Show Source
object
-
AllocMeasures: string
Maximum Length:
4000
Value that uniquely identifies an allocation scenario. -
AttributeNamesList: string
Maximum Length:
255
List of attributes names in an allocation scenario. -
AttributeValueIds: string
Maximum Length:
4000
Unique identifier of attribute values in an allocation scenario. -
AttributeValueNamesList: string
Maximum Length:
255
List of value of the attributes used in an allocation scenario. -
CreatedBy: string
Read Only:
true
Maximum Length:64
Name of the user who created the allocation scenario. -
CreationDate: string
(date-time)
Read Only:
true
Date when the user created the allocation scenario. -
DefaultCode: integer
(int32)
Value to indicate if the allocation scenario is default or not. The value 1 indicates that the allocation scenario is default and 2 or 0 indicate that the allocation scenario isn't a default scenario.
-
Description: string
Maximum Length:
240
Description of an allocation scenario. -
IncludeChildLevel: integer
(int32)
Value to indicate if the calculated demand metrics at a parent allocation node need to consider the demands at the child node also. The value 1 indicates that demand at the child nodes will be considered and the value 2 or 0 indicate that demand at the child nodes won't be considered.
-
InventoryItemId: number
Unique identifier of an inventory item specified in an allocation scenario.
-
ItemIds: string
Maximum Length:
4000
Unique identifier of the items specified in an allocation scenario. -
ItemNames: string
Maximum Length:
255
Names of the items specified in an allocation scenario. -
LastUpdateDate: string
(date-time)
Read Only:
true
Date when the user most recently updated the allocation scenario. -
LastUpdatedBy: string
Read Only:
true
Maximum Length:64
User who most recently updated an allocation scenario. -
LastUpdateLogin: string
Read Only:
true
Maximum Length:32
Sign in of the user who most recently updated an allocation scenario. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
Message: string
Maximum Length:
255
Message that indicates if the allocation scenario was successfully created. -
MetricMeasures: string
Maximum Length:
4000
Measures that are part of the demand satisfaction metrics in an allocation. -
Name: string
Maximum Length:
80
Name of an allocation scenario. -
NumberOfBuckets: integer
(int32)
Number of buckets specified in an allocation scenario.
-
ObjectVersionNumber: integer
(int32)
Value to indicate the changed version of an allocation scenario for every edit and save made by the user.
-
OrganizationCodes: string
Maximum Length:
255
Code of the organizations specified in an allocation scenario. -
OrganizationIdList: string
Maximum Length:
4000
List of the organization identifier specified in an allocation scenario. -
OwnedBy: string
Maximum Length:
64
Name of the user who owns the allocation scenario. -
ScenarioId: integer
(int64)
Unique identifier of an allocation scenario.
-
StartDate: string
(date)
Date when an allocation scenario starts.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]
The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Examples
This example describes how to create one allocation scenario.
Example cURL Command
Use the following cURL command to submit a request on the REST resource.
curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' "https://servername/fscmRestApi/resources/version/bmAllocationScenarios"
Example Request Body
The following example includes the contents of the request body in JSON format. You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it creates.
{ "Name" : "ABC2", "Description" : "ABC2Desc", "StartDate" : "2025-01-20", "NumberOfBuckets":10, "ItemNames": "BLM-ALLOC-JI-Quantity", "OrganizationCodes": "BLM:BLM_M1", "AllocMeasures":"ALLOC_SUP,CONSUM_SUP,AVAIL_SUP,CUML_AVAIL_SUP,GROSS_ALLOC,GROSS_CONSUM,GROSS_AVAIL,GROSS_CUML_AVAIL,ALLOC_STEAL,GROSS_ALLOC_STEAL,AVAIL_STEAL,NET_WEEK_SUP,ALLOC_USER_DEF,GROSS_SUP,CONSUM_HISTORY,GROSS_CONSUM_HISTORY", "MetricMeasures":"DMD_QTY,DMD_QTY_ON_TIME,PLN_FILL_PER,PLN_ONTIME_PER,SCH_FILL_PER,SCH_ONTIME_PER,REV,REV_PLN_ONTIME,REV_SCH_ONTIME", "IncludeChildLevel":1, "AttributeNamesList": "BLM-All", "AttributeValueNamesList": "ALL" }
Example Response Body
The following example includes the contents of the response body in JSON format:
{ "AllocMeasures": "ALLOC_SUP,CONSUM_SUP,AVAIL_SUP,CUML_AVAIL_SUP,GROSS_ALLOC,GROSS_CONSUM,GROSS_AVAIL,GROSS_CUML_AVAIL,ALLOC_STEAL,GROSS_ALLOC_STEAL,AVAIL_STEAL,NET_WEEK_SUP,ALLOC_USER_DEF,GROSS_SUP,CONSUM_HISTORY,GROSS_CONSUM_HISTORY", "AttributeValueIds": "300100544207360:8394830", "CreatedBy": "BLM_ALL", "CreationDate": "2025-05-08T08:57:00+00:00", "DefaultCode": 2, "Description": "ABC2Desc", "IncludeChildLevel": 1, "InventoryItemId": 26921883, "ItemIds": "26921883", "LastUpdateDate": "2025-05-08T08:57:00.696+00:00", "LastUpdateLogin": "3366CAA8B964E167E063C55B060A2DA8", "LastUpdatedBy": "BLM_ALL", "MetricMeasures": "DMD_QTY,DMD_QTY_ON_TIME,PLN_FILL_PER,PLN_ONTIME_PER,SCH_FILL_PER,SCH_ONTIME_PER,REV,REV_PLN_ONTIME,REV_SCH_ONTIME", "Name": "ABC2", "NumberOfBuckets": 10, "ObjectVersionNumber": 1, "OrganizationIdList": "45639", "OwnedBy": "BLM_ALL", "ScenarioId": 300100674234772, "StartDate": "2025-01-20", "AttributeNamesList": "BLM-All", "AttributeValueNamesList": "ALL", "Message": null, "ItemNames": "BLM-ALLOC-JI-Quantity", "OrganizationCodes": "BLM:BLM_M1", "links": [ { "rel": "self", "href": "https://servername/fscmRestApi/resources/version/bmAllocationScenarios/300100674234772", "name": "bmAllocationScenarios", "kind": "item", "properties": { "changeIndicator": "ACED0005737200136A6176612E7574696C2E41727261794C6973747881D21D99C7619D03000149000473697A65787000000001770400000001737200116A6176612E6C616E672E496E746567657212E2A0A4F781873802000149000576616C7565787200106A6176612E6C616E672E4E756D62657286AC951D0B94E08B02000078700000000178" } }, { "rel": "canonical", "href": "https://servername/fscmRestApi/resources/version/bmAllocationScenarios/300100674234772", "name": "bmAllocationScenarios", "kind": "item" } ] }