Allocation Markers - Input Payload Overview

The input payload is divided into four sections:

  • <User> identifies the user.
  • <SunSystemsContext> identifies the business unit, budget or ledger code.
  • <AllocationMarkers> contains the search values used to identify the transactions to be updated. These are described in detail later in this topic.
  • <Actions>identifies the controls that must be satisfied before the update is allowed and specifies the value of the updated Allocation Marker. These are described in detail later in this topic.

Allocation Markers

The fields that can be queried on to identify the transactions to be updated are listed below. A range of account codes plus one other criteria must be supplied as a minimum.

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

You should ensure that you have correctly identified which Ledger transactions are to be updated before running the update payload. Failure to do this may result in the wrong transactions being updated. You may wish to run the Journal Query component as a validation, using the same filter values as those you have defined in the <AllocationMarkers> section. This allows you to confirm that the correct transactions are being selected, before updating the Allocation Marker values.

Actions

This is where you specify the new value for the Allocation Marker. You may also specify a Batch Total (referred to as a Control Total within the component) value, with a Debit or Credit Indicator. This is the expected base currency value total of the selected transactions.