Create one special handling type

post

/fscmRestApi/resources/11.13.18.05/specialHandlingTypes

Request

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
  • Title: Automatically Create Receipt
    Maximum Length: 1
    Contains one of the following values: true or false. If true, then the application creates a receipt after the purchase order is implemented. If false, then the application doesn't create a receipt after the purchase order is implemented.
  • Title: Description
    Maximum Length: 240
    Description of the special handling type purchasing document.
  • Title: Enabled
    Maximum Length: 1
    Default Value: true
    Contains one of the following values: true or false. If true, then the special handling type will be available for document creation. If false, then you won't be able to create documents with that type.
  • Maximum Length: 30
    Descriptive flexfield context name for the special handling document header.
  • Maximum Length: 30
    Descriptive flexfield context name for the special handling document line.
  • Title: Negotiated
    Maximum Length: 1
    Contains one of the following values: true or false. If true, then when creating special handling purchasing documents, the Negotiated field on the line is enabled. If false, then the Negotiated field isn't enabled.
  • Title: Requires Buyer Review
    Maximum Length: 1
    Contains one of the following values: true or false. If true, then special handling orders created from requisitions require buyer review before submission. If false, then special handling orders created from requisitions are submitted automatically.
  • Title: Requires Single Supplier
    Maximum Length: 1
    Default Value: true
    Contains one of the following values: true or false. If true, then all lines on special handling requisitions must have the same supplier and supplier site. If false, then requisition lines can have a different supplier and supplier site.
  • Title: Special Handling Type
    Maximum Length: 30
    Type of purchasing document that indicates that the document needs to be handled in a special manner.
  • Title: Special Handling Type Code
    Maximum Length: 30
    Abbreviation that identifies the special handling type.
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 : specialHandlingTypes-item-response
Type: object
Show Source
  • Title: Automatically Create Receipt
    Maximum Length: 1
    Contains one of the following values: true or false. If true, then the application creates a receipt after the purchase order is implemented. If false, then the application doesn't create a receipt after the purchase order is implemented.
  • Read Only: true
    Maximum Length: 64
    User who created the special handing type.
  • Read Only: true
    Date and time when the special handling type was created.
  • Title: Description
    Maximum Length: 240
    Description of the special handling type purchasing document.
  • Title: Enabled
    Maximum Length: 1
    Default Value: true
    Contains one of the following values: true or false. If true, then the special handling type will be available for document creation. If false, then you won't be able to create documents with that type.
  • Title: Header Context
    Read Only: true
    Maximum Length: 80
    Descriptive flexfield context display value for the special handling document header.
  • Maximum Length: 30
    Descriptive flexfield context name for the special handling document header.
  • Read Only: true
    Date and time when the user last updated the special handling type.
  • Read Only: true
    Maximum Length: 64
    User who last updated the special handling type.
  • Title: Line Context
    Read Only: true
    Maximum Length: 80
    Descriptive flexfield context display value for the special handling document line.
  • Maximum Length: 30
    Descriptive flexfield context name for the special handling document line.
  • Links
  • Title: Negotiated
    Maximum Length: 1
    Contains one of the following values: true or false. If true, then when creating special handling purchasing documents, the Negotiated field on the line is enabled. If false, then the Negotiated field isn't enabled.
  • Title: Requires Buyer Review
    Maximum Length: 1
    Contains one of the following values: true or false. If true, then special handling orders created from requisitions require buyer review before submission. If false, then special handling orders created from requisitions are submitted automatically.
  • Title: Requires Single Supplier
    Maximum Length: 1
    Default Value: true
    Contains one of the following values: true or false. If true, then all lines on special handling requisitions must have the same supplier and supplier site. If false, then requisition lines can have a different supplier and supplier site.
  • Title: Special Handling Type
    Maximum Length: 30
    Type of purchasing document that indicates that the document needs to be handled in a special manner.
  • Title: Special Handling Type Code
    Maximum Length: 30
    Abbreviation that identifies the special handling type.
  • Read Only: true
    Value that uniquely identifies the special handling type.
Back to Top

Examples

This example describes how to create one special handling type.

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/specialHandlingTypes"

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/specialHandlingTypes"

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.

{          
            "SpecialHandlingType": "Bill Only",
            "SpecialHandlingTypeCode": "ORA_PO_BILL_ONLY",
            "Description": "Bill Only",
            "HeaderContextCode": "ORA_PO_BILL_ONLY_HEADERS",
            "LineContextCode": "ORA_PO_BILL_ONLY_LINES",
            "NegotiatedFlag": null,
            "EnabledFlag": true,
            "AutomaticallyCreateReceiptFlag": null,
            "RequiresSingleSupplierFlag": true,
            "RequiresBuyerReviewFlag": null
}

Example Response Body

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

{
    "SpecialHandlingTypeId": 300100650999688,
    "SpecialHandlingTypeCode": "ORA_PO_BILL_ONLY",
    "SpecialHandlingType": "Bill Only",
    "Description": "Bill Only",
    "HeaderContextCode": "ORA_PO_BILL_ONLY_HEADERS",
    "HeaderContext": null,
    "LineContextCode": "ORA_PO_BILL_ONLY_LINES",
    "LineContext": "Bill Only Context for Lines",
    "NegotiatedFlag": null,
    "EnabledFlag": true,
    "AutomaticallyCreateReceiptFlag": null,
    "RequiresSingleSupplierFlag": true,
    "RequiresBuyerReviewFlag": null,
    "CreatedBy": "CVBUYER01",
    "CreationDate": "2026-02-09T05:07:29.001+00:00",
    "LastUpdateDate": "2026-02-09T05:07:29.285+00:00",
    "LastUpdatedBy": "CVBUYER01",
    "links": [
        {
            "rel": "self",
            "href": "https://servername/fscmRestApi/resources/version/specialHandlingTypes/300100650999688",
            "name": "specialHandlingTypes",
            "kind": "item"
        },
        {
            "rel": "canonical",
            "href": "https://servername/fscmRestApi/resources/version/specialHandlingTypes/300100650999688",
            "name": "specialHandlingTypes",
            "kind": "item"
        }
    ]
}
Back to Top