Update a joint venture subledger transaction

patch

/fscmRestApi/resources/11.13.18.05/jointVentureSLATransactions/{jointVentureSLATransactionsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Joint Venture Subledger Transactions resource and used to uniquely identify an instance of Joint Venture Subledger Transactions. The client should not generate the hash key value. Instead, the client should query on the Joint Venture Subledger Transactions collection resource in order to navigate to a specific instance of Joint Venture Subledger Transactions to get the hash key.
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.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : Account Key Flexfields
Type: array
Title: Account Key Flexfields
The code identifying the general ledger account against which amounts are recorded. These represent assets, liabilities, revenues, expenses, and fund balances.
Show Source
Nested Schema : Joint Venture Transaction Changes
Type: array
Title: Joint Venture Transaction Changes
The joint venture transaction changes resource is used to view the history of manual changes to joint venture transactions.
Show Source
Nested Schema : transactionDFF
Type: array
Show Source
Nested Schema : jointVentureSLATransactions-transactionAccount-item-patch-request
Type: object
Show Source
Nested Schema : jointVentureSLATransactions-transactionChanges-item-patch-request
Type: object
Show Source
Nested Schema : schema
Type: object
Show Source
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 : jointVentureSLATransactions-item-response
Type: object
Show Source
Nested Schema : Account Key Flexfields
Type: array
Title: Account Key Flexfields
The code identifying the general ledger account against which amounts are recorded. These represent assets, liabilities, revenues, expenses, and fund balances.
Show Source
Nested Schema : Joint Venture Transaction Changes
Type: array
Title: Joint Venture Transaction Changes
The joint venture transaction changes resource is used to view the history of manual changes to joint venture transactions.
Show Source
Nested Schema : transactionDFF
Type: array
Show Source
Nested Schema : jointVentureSLATransactions-transactionAccount-item-response
Type: object
Show Source
Nested Schema : jointVentureSLATransactions-transactionChanges-item-response
Type: object
Show Source
  • Title: After Assignment Rule
    Read Only: true
    Maximum Length: 30
    The new ownership definition assignment rule assigned to the transaction.
  • Title: After Distribution Only
    Read Only: true
    Maximum Length: 1
    The new distribution only value assigned to the transaction.
  • Title: After Ownership Definition
    Read Only: true
    Maximum Length: 30
    The new ownership definition assigned to the transaction.
  • Title: After Direct Billed Stakeholder
    Read Only: true
    Maximum Length: 30
    The new name of the direct billed stakeholder assigned to the transaction.
  • Title: After Direct Billed Stakeholder Description
    Read Only: true
    Maximum Length: 240
    The new description of the direct billed stakeholder assigned to the transaction.
  • Title: After Status
    Read Only: true
    Maximum Length: 80
    The new status assigned to the transaction.
  • Title: After Transaction Date
    Read Only: true
    The new transaction date assigned to the transaction.
  • Title: Before Assignment Rule
    Read Only: true
    Maximum Length: 30
    The previous ownership definition assignment rule assigned to the transaction.
  • Title: Before Distribution Only
    Read Only: true
    Maximum Length: 1
    The previous distribution only value assigned to the transaction.
  • Title: Before Ownership Definition
    Read Only: true
    Maximum Length: 30
    The previous ownership definition assigned to the transaction.
  • Title: Before Direct Billed Stakeholder
    Read Only: true
    Maximum Length: 30
    The previous name of the direct billed stakeholder assigned to the transaction.
  • Title: Before Direct Billed Stakeholder Description
    Read Only: true
    Maximum Length: 240
    The previous description of the direct billed stakeholder assigned to the transaction.
  • Title: Before Status
    Read Only: true
    Maximum Length: 80
    The previous status assigned to the transaction.
  • Title: Before Transaction Date
    Read Only: true
    The previous transaction date assigned to the transaction.
  • Title: Change Reason
    Read Only: true
    Maximum Length: 80
    The reason for the manual change to the joint venture transaction.
  • Title: Change Reason Details
    Read Only: true
    Maximum Length: 240
    Additional text to describe the reason the joint venture transaction was manually changed.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the joint venture transaction change.
  • Title: Creation Date
    Read Only: true
    The date and time when the joint venture transaction change was created.
  • Links
  • Title: Transaction Change ID
    Read Only: true
    The unique identifier of the joint venture transaction change.
Nested Schema : jointVentureSLATransactions-transactionDFF-item-response
Type: object
Show Source
Back to Top