Get a contract line internal attribute

get

/fscmRestApi/resources/11.13.18.05/contracts/{contractsUniqID}/child/ContractLine/{LineId}/child/ProjectContractLineInternalAttributes/{ProjectContractLineInternalAttributesUniqID}

Request

Path Parameters
  • The unique identifier of the contract line.
  • This is the hash key of the attributes which make up the composite key--- ContractId, ContractLineId and MajorVersion ---for the Contract Line Internal Attributes resource and used to uniquely identify an instance of Contract Line Internal Attributes. The client should not generate the hash key value. Instead, the client should query on the Contract Line Internal Attributes collection resource with a filter on the primary key values in order to navigate to a specific instance of Contract Line Internal Attributes.

    For example: ProjectContractLineInternalAttributes?q=ContractId=<value1>;ContractLineId=<value2>;MajorVersion=<value3>
  • This is the hash key of the attributes which make up the composite key for the Contracts resource and used to uniquely identify an instance of Contracts. The client should not generate the hash key value. Instead, the client should query on the Contracts collection resource in order to navigate to a specific instance of Contracts 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
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • 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 : contracts-ContractLine-ProjectContractLineInternalAttributes-item-response
Type: object
Show Source
  • Unique identifier of the contract.
  • Unique identifier of the contract line.
  • Maximum Length: 1
    Indicates whether project managers can change the planned finish date of a milestone once created in the project plan. The default value is Y, which allows project managers to manage planned finish dates for milestones in the project plan.
  • Unique identifier for the expenditure type which is recorded on the internal invoices of the receiver in Oracle Fusion Payables for the contract line.
  • Title: Expenditure Type Name
    Maximum Length: 240
    Name of the expenditure type that is recorded on the internal invoices of the receiver in Oracle Fusion Payables for the contract line.
  • Title: Use original task owning organization
    Maximum Length: 20
    Indicates whether the expenditure organization populated on the intercompany invoice line sent to payables comes from the task owning organization on the original expenditure item or the expenditure organization on the intercompany contract line.
  • Title: Use original expenditure type
    Maximum Length: 1
    Indicates whether the expenditure type populated on the internal invoice line sent to payables comes from the expenditure type on the original expenditure item or the expenditure type on the internal contract line..
  • Maximum Length: 150
    The external reference key.
  • Maximum Length: 150
    The external source key.
  • Links
  • Identification of the version of the contract, created by amending the contract, used to generate the revenue distribution.
  • Unique identifier for the expenditure organization which is recorded on the internal invoices of the receiver in Oracle Fusion Payables for the contract line.
  • Title: Expenditure Organization Name
    Maximum Length: 240
    Name of the organization that is recorded on the internal invoices of the receiver in Oracle Fusion Payables for the contract line.
  • Title: Provider Business Unit ID
    Unique identifier for the business unit that provides goods or services which are charged using the internal contract line.
  • Title: Provider Business Unit Name
    Maximum Length: 240
    Name of the business unit that provides goods or services which are charged using the internal contract line.
  • The unique identifier of the receiver business unit.
  • Title: Receiver Business Unit
    Maximum Length: 240
    The receiver business unit name.
  • Unique identifier for the project which is recorded on the internal invoices of the receiver in Oracle Fusion Payables for the contract line.
  • Title: Receiver Project Name
    Maximum Length: 240
    Name of the project that is recorded on the internal invoices of the receiver in Oracle Fusion Payables for the contract line.
  • Unique identifier for the task which is recorded on the internal invoices of the receiver in Oracle Fusion Payables for the contract line.
  • Title: Receiver Task Name
    Maximum Length: 255
    Name of the task that is recorded on the internal invoices of the receiver in Oracle Fusion Payables for the contract line.
Back to Top