Get all transaction payment schedules

get

/fscmRestApi/resources/11.13.18.05/receivablesCustomerAccountSiteActivities/{BillToSiteUseId}/child/transactionPaymentSchedules

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=
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
  • Used as a predefined finder to search the collection.

    Format ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables

    • PrimaryKey Finds transaction payment schedules using the finder attributes specified.
      Finder Variables
      • InstallmentId; integer; The unique identifier of the installment number of the transaction payment schedule for a REST service.
    • TransactionPaymentSchedulesFinder Finds transaction payment schedule details using the finder attributes specified.
      Finder Variables
      • InstallmentStatus; string; The status of transactions to consider for inclusion in the transaction payment schedules inquiry for a REST API. Valid values are Open and Closed.
      • TransactionLimitByDays; integer; The number of days past the transaction date to consider it for inclusion in the transaction payment schedules inquiry for a REST API. The default value is 90 days.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • 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
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • InstallmentId; integer; The identifier of the payment schedule installment for a REST service.
    • InstallmentStatus; string; The status of the payment schedule installment for a REST service.
    • TransactionId; integer; The transaction identifier of the payment schedule installment for a REST service.
    • TransactionNumber; string; The transaction number of the payment schedule installment for a REST service.
    • TransactionType; string; The transaction type of the payment schedule installment for a REST service.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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 : receivablesCustomerAccountSiteActivities-transactionPaymentSchedules
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : receivablesCustomerAccountSiteActivities-transactionPaymentSchedules-item-response
Type: object
Show Source
  • Title: Payment Schedule Accounting Date
    Read Only: true
    The payment schedule installment accounting date for a REST service.
  • Title: Site
    Read Only: true
    Maximum Length: 150
    The name of the customer bill-to site of the transaction payment schedule.
  • Read Only: true
    Maximum Length: 64
    The name of the user who created the payment schedule installment for a REST service.
  • Read Only: true
    The creation date of the payment schedule installment for a REST service.
  • Read Only: true
    Maximum Length: 15
    The currency code of the payment schedule installment for a REST service.
  • Read Only: true
    The identifier of the payment schedule installment for a REST service.
  • Read Only: true
    The number of the payment schedule installment for a REST service.
  • Read Only: true
    Maximum Length: 80
    The status of the payment schedule installment for a REST service.
  • Read Only: true
    The date the payment schedule installment was last updated for a REST service.
  • Read Only: true
    Maximum Length: 64
    The name of the user who last updated the payment schedule installment for a REST service.
  • Links
  • Read Only: true
    The number of days the payment schedule installment is past due for a REST service.
  • Title: Maturity Date
    Read Only: true
    The payment terms due date of the payment schedule installment for a REST service.
  • Title: PO Number
    Read Only: true
    Maximum Length: 50
    The purchase order number assigned to the payment schedule installment for a REST service.
  • Title: Receipt Method
    Read Only: true
    Maximum Length: 30
    The receipt method used for the receipt applied against the payment schedule installment for a REST service.
  • Read Only: true
    Maximum Length: 256
    The name of the structured payment reference assigned to the payment schedule transaction for a REST service.
  • Title: Payment Schedule Balance Due Amount
    Read Only: true
    The open balance amount on the payment schedule installment for a REST service.
  • Title: Payment Schedule Original Amount Due
    Read Only: true
    The original balance amount on the payment schedule installment for a REST service.
  • Read Only: true
    Maximum Length: 80
    The transaction class of the payment schedule installment for a REST service.
  • Title: Transaction Date
    Read Only: true
    The transaction date of the payment schedule installment for a REST service.
  • Read Only: true
    The transaction identifier of the payment schedule installment for a REST service.
  • Title: Transaction Number
    Read Only: true
    Maximum Length: 20
    The transaction number of the payment schedule installment for a REST service.
  • Read Only: true
    Maximum Length: 50
    The name of the transaction source assigned to the payment schedule transaction for a REST service.
  • Title: Transaction Type Name
    Read Only: true
    Maximum Length: 20
    The transaction type of the payment schedule installment for a REST service.
Back to Top