Get an expense miscellaneous policy line

get

/fscmRestApi/resources/11.13.18.05/expenseMiscPolicies/{MiscPolicyId}/child/expenseMiscPolicyLines/{PolicyLineId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
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 : expenseMiscPolicies-expenseMiscPolicyLines-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 64
    User who created the row.
  • Read Only: true
    Date and time when the row was created.
  • Title: Description
    Read Only: true
    Maximum Length: 240
    Currency of a miscellaneous expense policy line.
  • Title: Currency
    Maximum Length: 15
    Currency code of a miscellaneous expense policy line.
  • Title: Daily sum limit
    Daily reimbursement limit for miscellaneous expenses.
  • Title: End Date
    Date from which the miscellaneous expense policy rate is no longer applicable.
  • Title: Gender
    Maximum Length: 30
    Gender code for the miscellaneous expense policy.
  • The unique identifier of the geography for which the miscellaneous expense policy rate is applicable.
  • Title: Geographical Location
    Maximum Length: 240
    Geographical location for which the miscellaneous expense policy rate is applicable.
  • Maximum Length: 30
    Indicates why the miscellaneous expense policy line has the invalid status.
  • Read Only: true
    Date and time when the row was last updated
  • Read Only: true
    Maximum Length: 64
    User who last updated the row.
  • Read Only: true
    Maximum Length: 32
    Session login of user who last updated the row.
  • Links
  • The unique identifier of the miscellaneous expense policy.
  • The unique identifier of the miscellaneous expense policy line.
  • Title: City
    Maximum Length: 80
    City for which the miscellaneous expense policy rate is applicable.
  • Title: Country
    Maximum Length: 80
    Country for which the miscellaneous expense policy rate is applicable.
  • Title: County
    Maximum Length: 80
    County for which the miscellaneous expense policy rate is applicable.
  • Title: State
    Maximum Length: 80
    State for which the miscellaneous expense policy rate is applicable.
  • Title: Percentage Reimbursement
    Percentage of the expense amount that's reimbursed when the submitted expense amount exceeds the limit and the rate type is percentage reimbursement or percentage reimbursement with upper limit.
  • The unique identifier of the role for which the miscellaneous expense policy rate is applicable.
  • Title: Role
    Maximum Length: 80
    Role name for which the miscellaneous expense policy rate is applicable, such as Director or Engineer.
  • Title: Single instance limit
    Indicates whether miscellaneous expense policy limits are enforced by each submitted instance of a miscellaneous expense item.
  • Title: Start Date
    Date from which the miscellaneous expense policy rate is applicable.
  • Title: Meaning
    Read Only: true
    Maximum Length: 80
    Status of the miscellaneous expense policy line. Valid values are Draft, Valid, Invalid, and Active.
  • Title: Status
    Maximum Length: 30
    Indicates the status of the miscellaneous expense policy line. Values are from the lookup EXM_POLICY_STATUS.
  • Maximum Length: 30
    Type of rate line, such as base miscellaneous rate or catch all.
  • Title: Yearly limit
    Annual reimbursement limit for miscellaneous expenses.
  • Title: Zone
    Maximum Length: 30
    Zone code for which the miscellaneous expense policy rate is applicable, such as geographical locations or zones.
Back to Top