Ledger Analysis Update

The input payload is divided into four sections:

  • <User> identifies the user.
  • <SunSystemsContext> identifies the business unit, budget or ledger code.
  • <LedgerUpdate> contains the selection values used to select the transactions to be updated and are described in detail later in this topic.
  • <Actions> contains the action(s) that are applied to all transactions that meet the specified selection values. It also contains the controls that must be satisfied before the update is allowed; these are described in detail later in this topic.

LedgerUpdate

If you want to update specific transactions, use the fields in this section to specify the selection values that you need. At least one value must be supplied from the list below.

  • Allocation Marker
  • Analysis Code (ten values - 1 to 10)
  • Base Amount
  • Debit/Credit
  • Due Date
  • Journal Line Number
  • Journal Number
  • Journal Type
  • Transaction Amount
  • Transaction Reference
  • Account Range

Before executing the payload, you should ensure that you have correctly identified which Ledger transactions are to be selected for update. Failure to do so may result in the wrong transactions being updated. You may wish to run a journal query payload using the same filter values as those you have defined in the <LedgerUpdate> section. This list of transactions returned from the journal query allows you to confirm that you have selected the correct transactions for update.

Actions

This section is where you specify the new value for the analysis code(s) and the transaction description. You may also specify a batch total (referred to as a control total within the component) value, with a debit or credit indicator.