Processing Incoming SunSystems JournalEntry BODs
The BOD capabilities of SunSystems/SSC can consume incoming SunSystemsJournalEntry BODs. This covers the handling of these BODs from other systems as well as those coming in from another instance of SunSystems, using ION.
Configuring SunSystems
In Integration Configuration (INC), create a new configuration, and in the Integration System Name pane, check the Selected check box against SunSystems BODs Integration.
The following message types are available:
Incoming Process.SunSystemsJournalEntry
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.SunSystemsJournalEntry
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
SunSystemsJournalEntry BOD is a payload shaped custom BOD, so all the data fields within the ledger payload are supported for import.
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 SunSystemsJournalEntry 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.
SunSystemsJournalEntry is a SunSystems specified, payload shaped custom BOD, providing richer data than the ION standard SourceSystemsJournalEntry BOD. It must be enabled within ION before it can be used, as follows:
In ION Desk select , and select Import to import the SunSystemsJournal BOD schema definition.
All SunSystems custom BOD schema definitions can be downloaded via Infor Xtreme.
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):
| Field Name | Payload Tag Name | Allowable Values | Required | Example | Processing for incoming BOD |
|---|---|---|---|---|---|
| Name | N/A | Text name | Y | Journal BOD Import | Any name can be used. |
| Description | N/A | Text | N | Import profile for receiving ION based Journal BODs | N/A |
| Target Component | N/A | Valid option from drop down list | Y | Ledger | Ledger is the data object in SSC for journals. |
| Target Method | N/A | Create or Amend | Y | Create or Amend | Create or Amend is the only option. |
| Business Unit | <BusinessUnit> | Valid Business Unit code | N | Can be supplied but this will be ignored in favor of the business unit (Accounting Entity) supplied on the incoming journal BOD. | |
| Ledger | <BudgetCode> | Valid option from drop down list | Y | A | Value can be taken directly from the BOD. |
| Save Payload | N/A | Both, Input, None, Output | Y | None | No recommended value |
| Error Suspense Account Code | <SuspenseAccount> | Any valid account | Y | 9999 | Set by ledger import transfer profile |
| Transaction Amount Account Code | <TransactionAmountAccount> | Any valid account | Y | 9999 | Set by ledger import transfer profile |
| Reporting Amount Account Code | <ReportingAccount> | Any valid account | Y | 9999 | Set by ledger import transfer profile |
| Allow over-budget entries | <AllowOverBudget> | 'Y' or 'N' | Y | Y | Use as set on profile. Y is recommended. |
| Balancing options | <BalancingOptions> |
Blank Unused (No Options) 'JT' Journal Type 'TD' Transaction Date 'RF' Transaction Reference 'T0' to 'T9' Ledger Analysis 1 to 10 |
Y | T3 | Use as set on profile. Blank Unused (no options) is recommended. |
| Allow balancing transactions | <AllowBanTran> | 'Y' or 'N' | Y | Y | Use as set on profile. Y is recommended. |
| Posting options | <PostingType> |
'0' Validate only '1' Post '2' Post if no errors |
Y | 0 | Use as set on profile. Any of these options can be selected, but 2 Post if no errors, is recommended. |
| Journal type | <JournalType> | Valid SunSystems journal types | Y | FGJ |
If a journal type is not supplied in the BOD, use as set on profile. It is recommended that systems sending journals to SunSystems supply a valid journal type. If they do not, one can be set up to be used as the default in the import process. Note: This must be set up in
SunSystems
for the import to succeed.
|
| Default posting period | <DefaultPostingPeriod> | PPPYYY format | Y | 0052002 | Values for this field are calculated if supplied via the BOD. If the data is not provided in the BOD, normal ledger import period definition logic will be used to generate a valid period value. |
| Post provisional | <PostProvisional> | 'Y' or 'N' | Y | Y | Use as set on profile. N is recommended. |
| Post to hold | <PostToHold> | 'Y' or 'N' | Y | Y | Use as set on profile. N is recommended. |
| Allow posting to suspended accounts | <AllowPostToSuspend> | 'Y' or 'N' | Y | Y | Use as set on profile. Y is recommended. |
| Description | <Description> | Text description | N | Blank | Use as set on profile. Blank is recommended, or can be set to a generic value. For example, Imported via ION. |
| Consolidation | N/A | Valid option from consolidation setup function | N | Not specified | Default setting Not specified is recommended. |
| Credit debit scenario | N/A | Valid option from lookup | N | Default - Sum credits and debits separately | Default value is recommended. |
| Print transactions | N/A | 'Y' or 'N' | Y | N | Use as set on profile. N is recommended. |
| Report layout code | N/A | Valid SunSystems Layout Code | Y | Print01 | Use as set on profile. Print01 is recommended. |
| Report only errors | N/A | 'Y' or 'N' | Y | Y | Use as set on profile. Y is recommended. |
| Suppress messages for insignificant substitutions | N/A | 'Y' or 'N' | Y | N | Use as set on profile. Y is recommended. |
| Detailed output to transfer log | N/A | 'Y' or 'N' | Y | N | Use as set on profile. N is recommended. |
| Email Notification | N/A | Disabled or Enabled | N | Disabled | Default setting Disabled is recommended. |
| Email Address | N/A | Valid email address | N | Blank | Not set is recommended. |
| Email Content | N/A | Text | N | Blank | Not set is recommended. |
| Source Data Format | N/A | Valid option from drop down list | Y | Ledger | Use the setting from the profile. |
| Transformation | N/A | Valid option from drop down list | Y | Ledger-to-Ledger | Use the setting from the profile. |
| File basis | N/A | 'Client' or 'Server' | N | Client | Not relevant. Default setting Client is recommended. |
| File name | N/A | Valid file name | Y | ION | This is irrelevant for this particular journal import via a BOD but the profile will show as in error in Transfer Desk unless a value is supplied. Setting to ION is recommended. |
| File action | N/A | Option from the 'Source File Action' list | Y | None | Default setting None is recommended. This will not clear any incoming BOD from the inbox. |
Assign Import Profile
Each business unit which is set up to receive either a Sync.SunSystemsJournalEntry or Process.SunSystemsJournalEntry 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.