Get one adjustment

get

/fscmRestApi/resources/11.13.18.05/salesOrderActionRequests/{ActionRequestId}/child/manualPriceAdjustments/{manualPriceAdjustmentsUniqID}

Request

Path Parameters
  • Unique identifier for the master action request.
  • This is the hash key of the attributes which make up the composite key for the Manual Price Adjustments resource and used to uniquely identify an instance of Manual Price Adjustments. The client should not generate the hash key value. Instead, the client should query on the Manual Price Adjustments collection resource in order to navigate to a specific instance of Manual Price Adjustments to get the hash key.
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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 : salesOrderActionRequests-manualPriceAdjustments-item-response
Type: object
Show Source
  • Amount of the manual price adjustment for a charge, which can be specified as either a fixed amount or a percentage.
  • Maximum Length: 255
    Basis used by pricing to calculate the manual price adjustment, which can be either QP_NET_PRICE or QP_LIST_PRICE.
  • Maximum Length: 255
    Name of the basis used by pricing to calculate the manual price adjustment, which can be either Your Price or List Price.
  • Maximum Length: 255
    Method that pricing uses to calculate the manual price adjustment for the item. A list of accepted values is defined in the lookup type ORA_QP_LINE_ADJ_TYPES.
  • Maximum Length: 255
    Abbreviation that identifies the type of manual price adjustment. A list of accepted values is defined in the lookup type ORA_QP_LINE_ADJ_TYPES.
  • Maximum Length: 255
    Definition of the charge that pricing uses to apply a manual price adjustment.
  • Maximum Length: 255
    Abbreviation that identifies the definition of the charge that pricing uses to apply a manual price adjustment.
  • Maximum Length: 255
    Comments that describe the manual price adjustment.
  • Number of periods to use for the price adjustment. This is available for use with the Integrate Order Management with Subscription Management to Process Subscriptions or Coverages features.
  • Number that identifies the period when the price adjustment starts. This is available for use with the Integrate Order Management with Subscription Management to Process Subscriptions or Coverages features.
  • Number that identifies the period when the price adjustment ends. This is available for use with the Integrate Order Management with Subscription Management to Process Subscriptions or Coverages features.
  • Maximum Length: 255
    Type of effectiveness for the price adjustment, available for use with the Integrate Order Management with Subscription Management to Process Subscriptions or Coverages feature.
  • Maximum Length: 255
    Abbreviation that identifies the type of effectiveness to be used for the price adjustment. A list of accepted values is defined in the lookup type ORA_OSS_PRICE_ADJ_EFFECTIVITY. This abbreviation is available for use with the Integrate Order Management with Subscription Management to Process Subscriptions or Coverages feature.
  • Links
  • Maximum Length: 255
    Price periodicity of the recurring charge where pricing applies the manual price adjustment.
  • Maximum Length: 255
    Abbreviation that identifies the price periodicity of the recurring charge, where pricing applies the manual price adjustment.
  • Maximum Length: 255
    Reason for the manual price adjustment.
  • Maximum Length: 255
    Abbreviation that identifies the reason for the manual price adjustment.
  • Sequence that pricing uses to apply the manual price adjustment to other manual price adjustments.
  • Maximum Length: 255
    Value that uniquely identifies the manual price adjustment. The source application assigns this value.
  • Maximum Length: 255
    Usage UOM of the usage charge where pricing applies, the manual price adjustment.
  • Maximum Length: 255
    Abbreviation that identifies the usage UOM of the usage charge, where pricing applies the manual price adjustment.
Back to Top