Create multiple change order relationship rules

post

/fscmRestApi/resources/11.13.18.05/productChangeOrdersV2/{productChangeOrdersV2UniqID}/child/changeOrderRelationships/{changeOrderRelationshipsUniqID}/child/relationshipRules

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Change Order Relationships resource and used to uniquely identify an instance of Change Order Relationships. The client should not generate the hash key value. Instead, the client should query on the Change Order Relationships collection resource in order to navigate to a specific instance of Change Order Relationships to get the hash key.
  • This is the hash key of the attributes which make up the composite key for the Product Change Orders Version 2 resource and used to uniquely identify an instance of Product Change Orders Version 2. The client should not generate the hash key value. Instead, the client should query on the Product Change Orders Version 2 collection resource in order to navigate to a specific instance of Product Change Orders Version 2 to get the hash key.
Header Parameters
  • 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".
  • 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.
  • 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
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • 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".
  • 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 : productChangeOrdersV2-changeOrderRelationships-relationshipRules-item-response
Type: object
Show Source
Back to Top

Examples

This example describes how to how to add a relationship rule.

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/productChangeOrdersV2/productChangeOrdersV2UniqID/child/changeOrderRelationships/changeOrderRelationshipsUniqID/child/relationshipRules"

For example:

curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' 
"https://servername/fscmRestApi/resources/version/productChangeOrdersV2/300100618383864/child/changeOrderRelationships/300100618384476/child/relationshipRules"

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

{
"SourceRuleStatus": "Open",
"DestinationRuleStatus": "Approval"
}

Example Response Body

The following example includes the contents of the response body in JSON format:

{
    "RelationshipId": 300100618384476,
    "RelationshipRuleId": 300100618389345,
    "SourceObjectId": 300100618383864,
    "SourceObjectNumber": "ECO12345",
    "SourceObjectType": "CHANGE",
    "SourceRuleStatus": "Open",
    "DestinationObjectID": 300100618384461,
    "DestinationObjectNumber": "PR1234",
    "DestinationObjectType": "PROBLEM_REPORT",
    "DestinationRuleStatus": "Approval",
    "CreatedBy": "PLM_AUTO",
    "CreationDate": "2023-10-25T17:42:14+00:00",
    "LastUpdateDate": "2023-10-25T17:42:14.200+00:00",
    "LastUpdatedBy": "PLM_AUTO",
    "links": [
        {
            "rel": "self",
            "href": "https://servername/fscmRestApi/resources/version/productChangeOrdersV2/300100618383864/child/changeOrderRelationships/300100618384476/child/relationshipRules/300100618389345",
            "name": "relationshipRules",
            "kind": "item",
            "properties": {
                "changeIndicator": "ACED0005737200136A6176612E7574696C2E41727261794C6973747881D21D99C7619D03000149000473697A65787000000001770400000001737200116A6176612E6C616E672E496E746567657212E2A0A4F781873802000149000576616C7565787200106A6176612E6C616E672E4E756D62657286AC951D0B94E08B02000078700000000178"
            }
        },
        {
            "rel": "canonical",
            "href": "https://servername/fscmRestApi/resources/version/productChangeOrdersV2/300100618383864/child/changeOrderRelationships/300100618384476/child/relationshipRules/300100618389345",
            "name": "relationshipRules",
            "kind": "item"
        },
        {
            "rel": "parent",
            "href": "https://servername/fscmRestApi/resources/version/productChangeOrdersV2/300100618383864/child/changeOrderRelationships/300100618384476",
            "name": "changeOrderRelationships",
            "kind": "item"
        }
    ]
}
Back to Top