Source Codes in Inter-Entity

Why use Source Codes?

When using Inter-Entity Transactions across multiple databases, it is helpful to use Source Types to monitor and identify transactions created by Inter-Entity Transactions in both the source company and in the target companies.

Source Types in source company

The source types required for the source company are defined in IET Options, on the Processing Tab.  The source types needed are for:

  • IET loan account journal entries (IY)

  • IET reversal journal entries (IR)

  • IET trigger journal entries and (IT)

  • IET G/L substitutions journal entries (IS)

The source types configured in IET Options should all be set to different codes.

Target Company Source Types

The source types required for the target company are defined in IET Entity database mappings.  The source types used in Database Mappings should never be the same as the ones specified in IET Options.

Important! You must not use IY, IR, IT or IS if Inter-Entity Transactions is activated in the target database and these source types are used in IET Options on the processing tab in the target database.

Example:

In the example below, “IE” has been used as a source code – for Inter Entity Transactions coming from Entity 1 (ORCLTD).  Using “JE” would also be fine if you do not want to track the inter-entity Transactions in the target databases via a source type.

Reserved GL Source Types

Some source types (JE, CL, CO, CV, IC) are reserved for Sage 300 modules. Do not use them in Inter-Entity configuration.

  1. Do not use the pre-defined source type "IC".  This is reserved for the Sage 300 Inter-Company module.  If you use this source code in company which is not your "Inter-Company Database", GL will automatically delete any GL Journal Entry Detail with the source type "IC" prior to posting the batch.

  2. 4. RT is reserved for GL Auto-allocation transactions.