Processing Incoming SourceSystemJournalEntry BODs

Configuring SunSystems

In Integration Configuration (INC), create a new configuration, and in the Integration System Name pane, check the Selected check box against Non-system specific.

The following message types are available:

Incoming Process.SourceSystemsJournalEntry

In this scenario, SunSystems will be the system of record (SOR) for journals. A process message is a request for an object to be created, and SunSystems should Sync out the record onto downstream systems if it has been set up in INC to do so. Journals in SunSystems are stored at the Accounting Entity level (Business Unit) so inbound journals must also include the target AE. Any data referenced within the journal (Analysis, Accounts etc) must exist in the system for the journal to be imported successfully. Any failure in data integrity results in a ConfirmBOD and an appropriate error message inside to state what the issue was, or an entry is made into Ledger Import (LIM).

Incoming Sync.SourceSystemJournalEntry

SunSystems in this scenario is not the SOR for journals. SunSystems will be listening to journals only and is not responsible for synching them on.

Supported Fields

The BOD fields supported for import are documented in the Inbound BOD mapping guide.

Variation ID

The normal protocol for handling incoming BODs supports Variation ID, which is the mechanism used to ensure that earlier updates do not wrongly overwrite later ones. If variation 7 of, say, a master data record is obtained before variation 6, then variation 6 is ignored when it is received.

In the case of journals, however, the consumption of multiple versions of a specific SourceSystemJournalEntry with the same Document ID, but different Variation ID, is not supported. If a later variation of a journal arrives, it is not processed. Instead, a Rejection message is sent.

Additional Setup Information

There is an additional set up step which is a recommendation for reconciliation purposes, for getting source journal IDs from the sending system into SunSystems.

General Description 25 must be specified as an additional field to contain Source Journal ID, via Additional Field Setup (AFS).

SunSystems Ledger Import options

When you configure your system to bring journals into SunSystems via ION, you still have the full range of options which SunSystems currently provides. In the default profile for running Ledger Import, this includes the following choices:

• Post if no errors
• Post
• Validation only

You are advised to use Post if no errors when bringing Journal data in using ION, but you are not prohibited from selecting the other options.

In the case of the Validation only option being selected, the incoming data is validated to see whether it would post, but will not be posted. An Acknowledge BOD indicating success is returned in such a case.

Therefore, you must understand the implications of using the other valid SunSystems options. In this example, the receiving system will receive an Acknowledge BOD, but (because of the option chosen in SunSystems), no Journal was posted.

Ledger Import SSC Component Transfer Profile

The following table details the recommended value for each attribute on the Ledger Import SSC Component Transfer Profile, set in Transfer Desk (TRD):

Assign Import Profile

Each business unit which is set up to receive either a Sync.SSJE or Process.SSJE can be associated with an Import Transfer Profile. This is required in order for the correct import default values to be applied, such as Error Suspense Account Code, Transaction Amount Account Code, and Reporting Amount Account Code.