1. REST API for Oracle Supply Chain Management Cloud
  2. Tasks
  3. Maintenance
  4. Part Requirement Lines

Create lines

post

/fscmRestApi/resources/11.13.18.05/partRequirementLines

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
Nested Schema : Part Requirement Line Details
Type: array
Title: Part Requirement Line Details
Records that contain additional details of a particular part or component. They help you view, create, or update sourcing information for a part requirement line.
Show Source
Nested Schema : Flexfields for Part Requirement Lines
Type: array
Title: Flexfields for Part Requirement Lines
Data used to manage the flexfields for a part requirement line.
Show Source
Nested Schema : Pricing Headers
Type: array
Title: Pricing Headers
Pricing-related information regarding a pricing segment, strategy, and currency applied to a part requirement line.
Show Source
Nested Schema : Service Charges
Type: array
Title: Service Charges
Charges levied for the components of a part requirement line, for example, for a party site or a customer.
Show Source
Nested Schema : partRequirementLines-lineDetails-item-post-request
Type: object
Show Source
Nested Schema : partRequirementLines-partRequirementLinesDFF-item-post-request
Type: object
Show Source
Nested Schema : partRequirementLines-pricingHeaders-item-post-request
Type: object
Show Source
Nested Schema : partRequirementLines-serviceCharges-item-post-request
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 : partRequirementLines-item-response
Type: object
Show Source
Nested Schema : Part Requirement Line Details
Type: array
Title: Part Requirement Line Details
Records that contain additional details of a particular part or component. They help you view, create, or update sourcing information for a part requirement line.
Show Source
Nested Schema : Flexfields for Part Requirement Lines
Type: array
Title: Flexfields for Part Requirement Lines
Data used to manage the flexfields for a part requirement line.
Show Source
Nested Schema : Pricing Headers
Type: array
Title: Pricing Headers
Pricing-related information regarding a pricing segment, strategy, and currency applied to a part requirement line.
Show Source
Nested Schema : Service Charges
Type: array
Title: Service Charges
Charges levied for the components of a part requirement line, for example, for a party site or a customer.
Show Source
Nested Schema : partRequirementLines-lineDetails-item-response
Type: object
Show Source
Nested Schema : partRequirementLines-partRequirementLinesDFF-item-response
Type: object
Show Source
Nested Schema : partRequirementLines-pricingHeaders-item-response
Type: object
Show Source
Nested Schema : partRequirementLines-serviceCharges-item-response
Type: object
Show Source
Links
calculateSourceAndPrice
Parameters:
  • RequirementLineId: $request.path.RequirementLineId
Finds the source for the requirement line and prices it. In the case of depot repair logistics and parts exchange flow, it creates the shipment line as well.
getAvailableParts
Parameters:
  • RequirementLineId: $request.path.RequirementLineId
Finds all the sources where the part can be sourced based on the preferences for the requirement line.
getPreferredSource
Parameters:
  • RequirementLineId: $request.path.RequirementLineId
Provides the suitable sourcing details for the requirement line.
lineDetails
Parameters:
  • RequirementLineId: $request.path.RequirementLineId
Records that contain additional details of a particular part or component. They help you view, create, or update sourcing information for a part requirement line.
partRequirementLinesDFF
Parameters:
  • RequirementLineId: $request.path.RequirementLineId
Data used to manage the flexfields for a part requirement line.
pricingHeaders
Parameters:
  • RequirementLineId: $request.path.RequirementLineId
Pricing-related information regarding a pricing segment, strategy, and currency applied to a part requirement line.
serviceCharges
Parameters:
  • RequirementLineId: $request.path.RequirementLineId
Charges levied for the components of a part requirement line, for example, for a party site or a customer.
Back to Top

Examples

This example describes how to create one transit time.

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

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. 

{
    "DestinationOrganizationCode": "FST",
    "DestinationSubinventory": "FS_Truck1",
    "InventoryItemId": 8980,
    "NeedByDate": "2019-03-01T02:17:00+00:00",
    "ParentEntityCode": "WO",
    "ParentEntityId": 300100186608532,
    "Quantity": 1,
    "ItemRevision": null,
    "ServiceActivityId": null,
    "ShipToAddressType": "CUSTOMER",
    "ShipToLocationId": 300100126721683,
    "UOMCode": "Ea"
}

Example Response Body

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

{
    "DestinationOrganizationId": 5702,
    "DestinationSubinventory": "FS_Truck1",
    "InventoryItemId": 8980,
    "NeedByDate": "2019-03-01T02:17:00+00:00",
    "ParentEntityCode": "WO",
    "ParentEntityId": 300100186608532,
    "Quantity": 1,
    "RequirementHeaderId": null,
    "RequirementLineId": 300100187398476,
    "ReturnReasonCode": null,
    "ItemRevision": null,
    "ServiceActivityId": null,
    "ShipToAddressType": "CUSTOMER",
    "ShipToContactId": null,
    "ShipToLocationId": 300100126721683,
    "UOMCode": "Ea",
    "DestinationOrganizationCode": "FST",
    "UnitOfMeasure": null
}
Back to Top