Jump to

• Request
• Response
• Examples

Create attributes for a demand or supply

post

/fscmRestApi/resources/11.13.18.05/demandAndSupplyPlans/{PlanId}/child/PlanningDemands/{TransactionId}/child/PlanningAttributes

Request

Path Parameters

• PlanId(required): integer
  The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
• TransactionId(required): integer(int64)
  The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=

Header Parameters

• 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.
• Upsert-Mode:
  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

Request Body - application/json ()

Root Schema : schema

Type: object

Show Source

• OrderNumber: string
  Title: Order Number

  Maximum Length: 4000

  Number that identifies the order associated with the demand or supply.
• PlanningAttributeNumber10: string
  Maximum Length: 4000

  Value for the planning attribute number 10 in attribute-based planning.
• PlanningAttributeNumber11: string
  Maximum Length: 4000

  Value for the planning attribute number 11 in attribute-based planning.
• PlanningAttributeNumber12: string
  Maximum Length: 4000

  Value for the planning attribute number 12 in attribute-based planning.
• PlanningAttributeNumber13: string
  Maximum Length: 4000

  Value for the planning attribute number 13 in attribute-based planning.
• PlanningAttributeNumber14: string
  Maximum Length: 4000

  Value for the planning attribute number 14 in attribute-based planning.
• PlanningAttributeNumber15: string
  Maximum Length: 4000

  Value for the planning attribute number 15 in attribute-based planning.
• PlanningAttributeNumber3: string
  Maximum Length: 4000

  Value for the planning attribute number 3 in attribute-based planning.
• PlanningAttributeNumber4: string
  Maximum Length: 4000

  Value for the planning attribute number 4 in attribute-based planning.
• PlanningAttributeNumber5: string
  Maximum Length: 4000

  Value for the planning attribute number 5 in attribute-based planning.
• PlanningAttributeNumber6: string
  Maximum Length: 4000

  Value for the planning attribute number 6 in attribute-based planning.
• PlanningAttributeNumber7: string
  Maximum Length: 4000

  Value for the planning attribute number 7 in attribute-based planning.
• PlanningAttributeNumber8: string
  Maximum Length: 4000

  Value for the planning attribute number 8 in attribute-based planning.
• PlanningAttributeNumber9: string
  Maximum Length: 4000

  Value for the planning attribute number 9 in attribute-based planning.
• TransactionId: integer (int64)
  Value that uniquely identifies the demand or supply. This value is internally generated by the application.

{
    "type":"object",
    "properties":{
        "PlanningAttributeNumber10":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 10 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber14":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 14 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber13":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 13 in attribute-based planning.",
            "nullable":true
        },
        "OrderNumber":{
            "title":"Order Number",
            "maxLength":4000,
            "type":"string",
            "description":"Number that identifies the order associated with the demand or supply.",
            "nullable":true
        },
        "PlanningAttributeNumber12":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 12 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber11":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 11 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber8":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 8 in attribute-based planning.",
            "nullable":true
        },
        "TransactionId":{
            "type":"integer",
            "description":"Value that uniquely identifies the demand or supply. This value is internally generated by the application.",
            "format":"int64",
            "nullable":true,
            "x-hints":{
                "precision":18
            }
        },
        "PlanningAttributeNumber9":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 9 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber15":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 15 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber6":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 6 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber7":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 7 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber4":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 4 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber5":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 5 in attribute-based planning.",
            "nullable":true
        },
        "PlanningAttributeNumber3":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 3 in attribute-based planning.",
            "nullable":true
        }
    }
}

Back to Top

Response

Supported Media Types

• application/json

Default Response

The following table describes the default response for this task.

Headers

• Metadata-Context(required):
  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(required):
  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.

Body ()

Root Schema : demandAndSupplyPlans-PlanningDemands-PlanningAttributes-item-response

Type: object

Show Source

• links: array Links
  Title: Links

  The link relations associated with the resource instance.
• OrderNumber: string
  Title: Order Number

  Maximum Length: 4000

  Number that identifies the order associated with the demand or supply.
• PlanningAttributeNumber10: string
  Maximum Length: 4000

  Value for the planning attribute number 10 in attribute-based planning.
• PlanningAttributeNumber11: string
  Maximum Length: 4000

  Value for the planning attribute number 11 in attribute-based planning.
• PlanningAttributeNumber12: string
  Maximum Length: 4000

  Value for the planning attribute number 12 in attribute-based planning.
• PlanningAttributeNumber13: string
  Maximum Length: 4000

  Value for the planning attribute number 13 in attribute-based planning.
• PlanningAttributeNumber14: string
  Maximum Length: 4000

  Value for the planning attribute number 14 in attribute-based planning.
• PlanningAttributeNumber15: string
  Maximum Length: 4000

  Value for the planning attribute number 15 in attribute-based planning.
• PlanningAttributeNumber3: string
  Maximum Length: 4000

  Value for the planning attribute number 3 in attribute-based planning.
• PlanningAttributeNumber4: string
  Maximum Length: 4000

  Value for the planning attribute number 4 in attribute-based planning.
• PlanningAttributeNumber5: string
  Maximum Length: 4000

  Value for the planning attribute number 5 in attribute-based planning.
• PlanningAttributeNumber6: string
  Maximum Length: 4000

  Value for the planning attribute number 6 in attribute-based planning.
• PlanningAttributeNumber7: string
  Maximum Length: 4000

  Value for the planning attribute number 7 in attribute-based planning.
• PlanningAttributeNumber8: string
  Maximum Length: 4000

  Value for the planning attribute number 8 in attribute-based planning.
• PlanningAttributeNumber9: string
  Maximum Length: 4000

  Value for the planning attribute number 9 in attribute-based planning.
• TransactionId: integer (int64)
  Value that uniquely identifies the demand or supply. This value is internally generated by the application.

{
    "type":"object",
    "properties":{
        "PlanningAttributeNumber10":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 10 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber14":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 14 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber13":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 13 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "OrderNumber":{
            "title":"Order Number",
            "maxLength":4000,
            "type":"string",
            "description":"Number that identifies the order associated with the demand or supply.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber12":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 12 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber11":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 11 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber8":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 8 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "TransactionId":{
            "type":"integer",
            "description":"Value that uniquely identifies the demand or supply. This value is internally generated by the application.",
            "format":"int64",
            "nullable":true,
            "x-hints":{
                "precision":18
            },
            "x-queryable":true
        },
        "PlanningAttributeNumber9":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 9 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber15":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 15 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber6":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 6 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber7":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 7 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber4":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 4 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber5":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 5 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "PlanningAttributeNumber3":{
            "maxLength":4000,
            "type":"string",
            "description":"Value for the planning attribute number 3 in attribute-based planning.",
            "nullable":true,
            "x-queryable":true
        },
        "links":{
            "title":"Links",
            "type":"array",
            "description":"The link relations associated with the resource instance.",
            "items":{
                "$ref":"#/components/schemas/link"
            }
        }
    }
}

Nested Schema : Links

Type: array

Title: Links

The link relations associated with the resource instance.

Show Source

• Array of: object link

{
    "title":"Links",
    "type":"array",
    "description":"The link relations associated with the resource instance.",
    "items":{
        "$ref":"#/components/schemas/link"
    }
}

Nested Schema : link

Type: object

Show Source

• 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.

{
    "type":"object",
    "properties":{
        "kind":{
            "title":"kind",
            "type":"string",
            "description":"The kind of the related resource.",
            "enum":[
                "collection",
                "item",
                "describe",
                "other"
            ]
        },
        "rel":{
            "title":"relation",
            "type":"string",
            "description":"The name of the relation to the resource instance.  Example: self.",
            "enum":[
                "self",
                "lov",
                "parent",
                "canonical",
                "child",
                "enclosure",
                "action",
                "custom"
            ]
        },
        "name":{
            "title":"name",
            "type":"string",
            "description":"The name of the link to the related resource."
        },
        "href":{
            "title":"hyperlink reference",
            "type":"string",
            "description":"The URI to the related resource."
        },
        "properties":{
            "type":"object",
            "properties":{
                "changeIndicator":{
                    "type":"string",
                    "description":"Change indicator or the ETag value of the resource instance."
                }
            }
        }
    }
}

Nested Schema : properties

Type: object

Show Source

• changeIndicator: string
  Change indicator or the ETag value of the resource instance.

{
    "type":"object",
    "properties":{
        "changeIndicator":{
            "type":"string",
            "description":"Change indicator or the ETag value of the resource instance."
        }
    }
}

Back to Top

Examples

Planning attributes can only be created when creating the parent (planning demand or planning supply). Once the planning demand or planning supply has been created, then planning attributes can only be updated.

Back to Top