Get one attachment

get

/fscmRestApi/resources/11.13.18.05/supplierProducts/{supplierProductsUniqID}/child/attachments/{attachmentsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Attachments resource and used to uniquely identify an instance of Attachments. The client should not generate the hash key value. Instead, the client should query on the Attachments collection resource in order to navigate to a specific instance of Attachments to get the hash key.
  • This is the hash key of the attributes which make up the composite key for the Supplier Products resource and used to uniquely identify an instance of Supplier Products. The client should not generate the hash key value. Instead, the client should query on the Supplier Products collection resource in order to navigate to a specific instance of Supplier Products 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 : supplierProducts-attachments-item-response
Type: object
Show Source
  • Title: Asynchronous Upload Tracker Id
    An identifier used for tracking the uploaded files.
  • Title: Attached Document Id
    Value that uniquely identifies the attached document.
  • Title: Category
    Maximum Length: 30
    Name of the product attachment category. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Attachment Categories task.
  • Title: Shared
    Contains one of the following values: true or false. If true then the attachment is shared. If false, then it is not shared. The default value is false.
  • Title: Created By
    Read Only: true
    Maximum Length: 255
    User who created the attachment.
  • Title: Created By User Name
    Read Only: true
    Login that the user used when creating the attachment.
  • Title: Creation Date
    Read Only: true
    Date and time when the user created the attachment.
  • Title: Type
    Maximum Length: 30
    Default Value: FILE
    Abbreviation that indicates the type of data. Valid values include WEB_PAGE, TEXT, or FILE.
  • Title: Description
    Maximum Length: 255
    Description of the product attachment.
  • Maximum Length: 255
    Value that uniquely identifies the document from which the attachment is created.
  • Title: Dm Folder Path
    Maximum Length: 1000
    Path to the folder in which the attachment file is uploaded.
  • Maximum Length: 255
    Version number that identifies the attachment in repository.
  • Title: DownloadInfo
    JSON object represented as a string containing information used to programmatically retrieve a file attachment.
  • Title: Error Status Code
    Abbreviation that identifies the error code, if any, for the attachment.
  • Title: Error Status Message
    Text of the error message, if any, for the attachment.
  • Title: Expiration Date
    Date when the contents of the attachment are no longer valid.
  • Title: File Contents
    Contents of the attachment.
  • Title: File Name
    Maximum Length: 2048
    Name of the file attached to the product.
  • Title: File Url
    Path of the document file.
  • Title: File Web Image
    Read Only: true
    The base64 encoded image of the file displayed in .png format if the source is a convertible image.
  • Title: Last Update Date
    Read Only: true
    Date and time when the product was most recently updated. For a list of attribute value interdependencies, refer to Interdependent Item Attributes: Explained at: https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FAPIM287169.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 255
    User who most recently updated the attachment.
  • Title: Last Updated By User
    Read Only: true
    Login that the user used when updating the attachment.
  • Links
  • Title: Title
    Title of the product attachment.
  • Title: Uploaded File Content Type
    Content type of the attached file.
  • Title: File Size
    Length of the attached file.
  • Title: Uploaded File Name
    Name of the attached file.
  • Title: Uploaded Text
    Contents of text file that is attached.
  • Title: Uri
    Maximum Length: 4000
    URI (Uniform Resource Identifier) appended to the base URI derived from the endpoint associated with application identified by the MODULE_ID.
  • Title: Url
    Maximum Length: 4000
    Uniform resource locator of the attachment.
  • Title: User Name
    Read Only: true
    Maximum Length: 255
    Display name of the attachment category. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage attachment categories task.
Back to Top