Update one component

patch

/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub/{OrderKey}/child/lines/{linesUniqID}/child/charges/{OrderChargeId}/child/chargeComponents/{OrderChargeComponentId}

Request

Path Parameters
  • Value that uniquely identifies the transaction.
  • Value that uniquely identifies the transaction.
  • Value that uniquely identifies the sales order. It can have the following formats.

    - Concatenation of SourceOrderSystem, a colon, and the value of SourceTransactionId. For orders created through the Oracle Fusion Cloud Order Management work area, the SourceTransactionId is same as the HeaderId. For example, if SourceOrderSystem is LEG and SourceTransactionId is R13_Sample_Order, the value of this attribute is LEG:R13_Sample_Order. This format of the OrderKey in the URL always returns the latest version of the sales order. When a draft exists, that becomes the latest version of the sales order. When invoking GET sales order using this OrderKey format, the URLs in the "links" section point to the latest version of the sales order and the corresponding child objects.
    Example: /salesOrdersForOrderHub/LEG:R13_Sample_Order points to the latest version of the order with SourceTransactionId "R13_Sample_Order" in the SourceOrderSystem "LEG".

    - Primary key of the sales order, which is HeaderId. This format of the OrderKey is useful when the order has multiple revisions because it helps in accessing either the older version or the latest version of the order. When there's a draft revision then HeaderId can be used to access the processing order. When invoking GET sales order using this OrderKey format, the URLs in the "links" section also point to that specific version of the sales order and the corresponding child objects. Only the Get operation is supported on older revisions of the order.
    Example: /salesOrdersForOrderHub/12345 points to an order with HeaderId 12345.

    When a q parameter or query finder is used to GET an order that has multiple versions then the latest version has the OrderKey in the format <sourceOrderSystem>:<SourceTransactionId> whereas reference orders have OrderKey in the format of HeaderId.
  • This is the hash key of the attributes which make up the composite key for the Order Lines resource and used to uniquely identify an instance of Order Lines. The client should not generate the hash key value. Instead, the client should query on the Order Lines collection resource in order to navigate to a specific instance of Order Lines 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.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Maximum Length: 255
    Name of the currency that the charge component uses.
  • Maximum Length: 15
    Abbreviation that identifies the currency that the charge component uses.
  • Extended amount for the duration displayed in the currency that the charge uses.
  • Extended amount displayed in the currency that the charge uses. Extended amount equals the unit price multiplied by the quantity on the order line. For a configured item, the extended amount equals the unit price multiplied by the extended quantity on the order line.
  • Price or adjustment for each unit displayed in the charge currency that the order line uses.
  • Maximum Length: 1000
    Explanation of the charge component.
  • Maximum Length: 30
    Message name of the explanation that displays in the price break down dialog.
  • Maximum Length: 255
    Name of the currency that the order header uses.
  • Maximum Length: 15
    Abbreviation that identifies the currency that the order header uses.
  • Extended amount for the duration, displayed in the currency that the order header uses.
  • Extended amount, displayed in the currency that the order header uses.
  • Price or adjustment for each unit of the item, displayed in the currency that the order header uses.
  • Percent that the unit price constitutes of the basis charge component. The default value for the basis is List Price. This attribute stores the margin percent, the percent that net price constitutes of the list price, and so on.
  • Maximum Length: 255
    Name of the price element, such as list price, net price, and so on.
  • Maximum Length: 30
    Abbreviation that identifies the price element.
  • Maximum Length: 255
    Name that describes charge component usage.
  • Maximum Length: 30
    Abbreviation that identifies the charge component usage.
  • Maximum Length: 30
    Value that identifies the source of the lowest level pricing. For example, it contains the Id that identifies a line on the price list, a tier rule, a shipping line, and so on.
  • Maximum Length: 255
    Type of the price source.
  • Maximum Length: 30
    Type of the price source, such as the charge of a segment price list. A list of accepted values is defined in the lookup type ORA_QP_SOURCE_TYPES.
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then the value is a rollup value for the charge component. If false, then the value is not a rollup value. For Oracle Fusion application priced orders, the default value is set based on the pricing setup. For pre-priced orders, the default value is false.
  • Sequence number for the charge component.
  • Maximum Length: 50
    Value that identifies the source of a manual price adjustment.
  • Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then the price for the charge component includes tax. If false, then the price for the charge component does not include tax. For Oracle Fusion application priced orders, the default value is set based on the pricing setup. For pre-priced orders, the default value is false.
  • Total Components
    Title: Total Components
    The Total Components resource retrieves the components that determine the total price of a sales order.
Nested Schema : Total Components
Type: array
Title: Total Components
The Total Components resource retrieves the components that determine the total price of a sales order.
Show Source
Nested Schema : salesOrdersForOrderHub-lines-charges-chargeComponents-totalComponents-item-patch-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 : salesOrdersForOrderHub-lines-charges-chargeComponents-item-response
Type: object
Show Source
Nested Schema : Total Components
Type: array
Title: Total Components
The Total Components resource retrieves the components that determine the total price of a sales order.
Show Source
Nested Schema : salesOrdersForOrderHub-lines-charges-chargeComponents-totalComponents-item-response
Type: object
Show Source
Back to Top