Get one action, not supported

get

/fscmRestApi/resources/11.13.18.05/validateReceivingTransactionDates/{validateReceivingTransactionDatesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Validate Receiving Transaction Dates resource and used to uniquely identify an instance of Validate Receiving Transaction Dates. The client should not generate the hash key value. Instead, the client should query on the Validate Receiving Transaction Dates collection resource in order to navigate to a specific instance of Validate Receiving Transaction Dates 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 : validateReceivingTransactionDates-item-response
Type: object
Show Source
  • Abbreviation that identifies the message that describes the error that occurred when validating the transaction date. If the Return Status attribute contains a value of SUCCESS, then the Error Code attribute is empty.
  • Message that describes the error that occurred when validating the transaction date. If the Return Status attribute contains a value of SUCCESS, then the Error Explanation attribute is empty.
  • Value that uniquely identifies the item.
  • Links
  • Value that uniquely identifies the parent transaction.
  • Value that uniquely identifies the purchase order schedule.
  • Value that uniquely identifies the RMA receipt advice line.
  • Status returned by the application when validating the date. Valid values are SUCCESS, ERROR, and WARNING. SUCCESS: the application successfully validated the date for the transaction. ERROR: the validation failed. WARNING: the validation found a potential problem but allowed the transaction to continue.
  • Value that uniquely identifies the shipment line.
  • Document type of the shipment. Valid values are PO, RMA, TRANSFER ORDER and INVENTORY.
  • Value that uniquely identifies the receiving organization.
  • Title: Receipt Date
    Date for the current receiving transaction.
  • Default Value: RECEIVE
    Type of transaction being validated. Valid values are ACCEPT, REJECT, TRANSFER, DELIVER, CORRECT, RETURN TO VENDOR, RETURN TO RECEIVING, RETURN TO CUSTOMER, and RETURN TO ORGANIZATION.
  • Value that uniquely identifies the transfer order line.
Back to Top