In this article

MEM Sample Data

This topic outlines the types of records that are installed with the MEM sample data.

In the assisted setup you have the option to install MEM sample data which is installed on top of the default Business Central sample data.

By default, MEM sample data is installed with the Global Dimension 1 Code as a Global Dimension Entity. The sample data uses descriptive intercompany accounts marked as false.

Note icon. Note: If you are creating a new company through the Create New Company setup wizard, you have the option to install the MEM sample data. In the Create New Company setup wizard, you must select either Evaluation - Sample Data or Advanced Evaluation - Complete Sample Data if you want to install the MEM sample data. For more information on creating a company, see Create New Companies in Business Central.

Installing Sample Data Multiple Times

You can install the MEM Sample Data multiple times.

To install the sample data again, after the initial assisted setup, do the following:

  1. Go to Search and enter MEM Install Sample Data.
  2. Select Global Dimension for Entity from the drop-down.
    1. If MEM sample data is installed already then the Global Dimension for Entity remains the same value when MEM sample data was installed initially. Otherwise it is MEM Entity Dimension.
  3. Select Actions > Process.

Fields

The following field boxes are available: 

Field Description
Use Descriptive Intercompany Accounts Turn on to create descriptive G/L accounts for each entity combination for intercompany setup while installing MEM sample data. For more information on intercompany accounts, see Intercompany Setup Records (GL Accounts Record for intercompany).
Global Dimension for Entity Allow users to select the Global Dimension code where they want to install the MEM sample data. By default, the value of this field is the value of the Entity Dimension from the MEM Multi-Entity Management Setup window. When you change the value of this field while installing the MEM sample data, previous MEM settings will be removed and new settings for the changed Dimension will be created.

Actions

The following actions are available: 

Action Description
Process Installs the MEM sample data with your selected settings

Records Created and Updated with the MEM Sample Data

The following records are created or updated when you install the MEM sample data.

MEM Entity Setup Records

If you select the Global Dimension 1 Code while installing the sample data, the Company - Dimension record appears as:

000, 100, 200, 300, 999 - entity (Dimension Values) records

If you select the Global Dimension 2 Code while installing the sample data, the Entity - Dimension record appears as:

A01, B01, B02, C01, C02 - entity (Dimension Values) records

In the MEM Entity Setup window, the following tabs and all of the fields in them are updated:

  • General
    • For example, Legal Name, Email, and Home Page are all updated.
    • The Tax Registration Number field is not updated.
  • Billing information
    • For example, the Billing Address, Billing City, and Billing Country are all updated.
  • Shipping Information
    • For example, the Shipping Address, Shipping City, and Shipping Country are all updated.
  • Sales Number Series and Purchase Number Series
    • For example, the Invoice Numbers and Order Numbers are updated.
  • Payments: The Bank Account Number is updated.
  • Intercompany information: New customer and vendor records are created and GL accounts are also created if they are required.
    • The Intercompany Customer, Intercompany Vendor, and Intercompany Location fields are all updated.

Intercompany Setup Records (GL Accounts Record for intercompany)

Note that GL Accounts will be consistent with regions.

Descriptive Intercompany Accounts turned off

If you turn off Use Descriptive Intercompany Accounts while installing the sample data, Payable, Liabilities, Receivable, Assets, and General Ledger accounts are created.

An Intercompany Setup record is created for all entity combinations with the following accounts.

For the United States (US) region:

  • Account No: 21999, Name: Intercompany Payable, Category: Liabilities
  • Account No: 10980, Name: Intercompany Receivable, Category: Assets
  • Account No: 22990 (Evaluation Setup), Name: Intercompany Payable, Category: Liabilities
  • Account No: 22490 (Extended Setup), Name: Intercompany Payable, Category: Liabilities
  • Account No: 15190 (Evaluation Setup), Name: Intercompany Receivable, Category: Assets
  • Account No: 13390 (Extended Setup), Name: Intercompany Receivable, Category: Assets

For the European (EU) region,

  • Account No: 57999, Name: Intercompany Payable, Category: Liabilities
  • Account No: 47999, Name: Intercompany Receivable, Category: Assets
  • Account No: 82990 (Evaluation Setup), Name: Intercompany Payable, Category: Liabilities
  • Account No: 5480 (Extended Setup), Name: Intercompany Payable, Category: Liabilities
  • Account No: 75190 (Evaluation Setup), Name: Intercompany Receivable, Category: Assets
  • Account No: 2380 (Extended Setup), Name: Intercompany Receivable, Category: Assets

For the Australian (AU) region,

  • Account No: 57999, Name: Intercompany Payable, Category: Liabilities
  • Account No: 47999, Name: Intercompany Receivable, Category: Assets
  • Account No: 2271 (Evaluation Setup), Name: Intercompany Payable, Category: Liabilities
  • Account No: XXXX (Extended Setup), Name: Intercompany Payable, Category: Liabilities
  • Account No: 1280 (Evaluation Setup), Name: Intercompany Receivable, Category: Assets
  • Account No: XXXX (Extended Setup), Name: Intercompany Receivable, Category: Assets

Descriptive Intercompany Accounts turned on

If you turn on Use Descriptive Intercompany Accounts while installing the sample data, GL accounts for each of the entity combinations are created. An Intercompany Setup record is created for all entity combinations with accounts created for each of the following entity combinations. The entity combinations are:

  • IC (Originating Entity)- DT- (Destination Entity) (Originating Due To account)
  • IC (Originating Entity)- DF- (Destination Entity) (Originating Due From account)
  • IC (Destination Entity)- DT- (Originating Entity) (Destination Due To account)
  • IC (Destination Entity)- DF- (Originating Entity) (Destination Due From account)

For example, for entity 000 to 100 combination:

  • IC 000-DT-100 (Originating Due To account)
  • IC 000-DF-100 (Originating Due From account)
  • IC 100-DT-000 (Destination Due To account)
  • IC 100-DF-000 (Destination Due From account)

Allocation Templates Records

Allocation Template Record Description
70/20/10

70, 20, and 10 represent the percentages.

70% is allocated to the first entity in the entity list.

20% is allocated to the second entity

10% is allocated to the third entity
50/30/20

50, 30, and 20 represent the percentages.

50% is allocated to the first entity in the entity list

30% is allocated to the second entity

20% is allocated to the third entity
50/50 50% is allocated to the first and second entity.
20/20/20/20/20 20% is allocated to each entity available in the list.
12/33/17/38

12% is allocated to the first entity in the entity list

33% is allocated to the second entity

17% is allocated to the third entity

38% is allocated to the fourth entity

If the total of the percentage values does not equal 100, the remaining percentage will be allocated to a line entity.

Bank Account Posting Group Records

If the G/L account is not available, it is also created.

  • Code=CHECKING (AU: CHEQUING), G/L Account No.= (US:10100, EU: 40100, AU:2920)
  • Code=SAVINGS, G/L Account No.= (US: 10200, EU: 40200, AU:2940)
  • Code=CASH, G/L Account No.= (US: 10300, EU: 40300, AU:2910)

Evaluated Setup

  • Code= CHECKING, G/L Account No.= (US: 18200, EU: 78200)
  • Code=CASH, G/L Account No.= (US: 18100, EU: 78100, AU: 1005)
  • Code= OPERATING, G/L Account No.= (US: 18200, EU: 78100, AU: 2102)
  • Code=SAVINGS, G/L Account No.= (US: 18400, EU: 78400)
  • Code= FCY, G/L Account No.= (AU: 1015)
  • Code= LCY, G/L Account No.= (AU: 1010)

Extended Setup

  • Code= CURRENCIES, G/L Account No.= (US: 11500, EU/AU: 2930)
  • Code= USD, G/L Account No.= (US: 11400)
  • Code= OPERATING, G/L Account No.= (US: 22100, EU/AU: 5310)
  • Code= (AU: LCY, EU: GBP), G/L Account No. = (AU/EU: 2920)
  • Code= (AU/US: LCY2, EU: GBP2), G/L Account No.= (US: 11600, AU/EU: 2940)

Bank Account Records

Bank account records are created and entities are assigned to each bank account created by the MEM sample data or bank accounts which already exist.

If any of the bank account records from the following list already exist on the database, an entity is assigned to those bank accounts. If bank account records do not already exist on the database, then records are created and an entity is assigned to the bank account.

  • CHECKING
  • SAVINGS
  • GIRO
  • NBL
  • WWB-OPERATING
  • FIRST BANK
  • UPTOWN TRUST

Inventory Posting Group Records

  • FINISHED
  • RAW MAT
  • RESALE

Location Records

Location records are created and entities are assigned to each location.

If any of the location records from the following list already exist on the database, an entity will be assigned to those locations. Otherwise, location records are created by the MEM sample data and an entity is assigned to the location.

  • EAST
  • MAIN
  • NORTH
  • WEST
  • BLUE
  • GREEN

For each of these locations and Inventory Posting Group, Inventory Posting Setup will be created. For example, for the location East record, the following setups are created.

  • EAST-FINISHED
  • EAST-RAW MAT
  • EAST-RESALE

Existing Transaction Records

All unposted and posted transactions are assigned an entity. This only applies to the Cronus data. The following existing transaction records are updated with the MEM sample data:

  • Unposted transactions, including:
    • Sales and purchase orders, sales quotes, and sales and purchase invoices
    • For sales orders and purchase orders, each transaction is assigned a different entity. In some cases transactions might have the same entity depending on the number of transactions.
    • For one transaction each (orders, quotes, invoices), the header and line entity is different to make intercompany impact. Remaining transactions are assigned the same header and line entity. This is applied to both sales and purchase transaction records.
    • Journals and item journals
      • Bank account lines are assigned an entity depending on the bank account owner.
      • To create intercompany impact, the G/L Account line is assigned a different entity from the balancing bank account entity.
      • To avoid intercompany impact, the G/L Account line is assigned same entity as balancing bank account entity.
      • For item journals, an entity is assigned based on the location used in the journal line.
    • Fixed assets
  • Posted transactions, including:
    • Posted sales (shipments and invoices, for example)
    • Posted purchases (receipts and invoices, for example)
    • For posted transactions, all related entries are assigned the same entity.
    • The balancing line and actual line are assigned the same entity for whole transactions because the transaction is already posted and assigning different entities causes imbalance in the entries.
    • Journals
    • All related documents, including invoices, orders, and receipts, are assigned the same entity.
    • Transfer receipts (assigned based on entity of location)

New Transaction Records

New transaction records are created with MEM sample data if your company has Cronus data available.

All transactions are created and posted with the intercompany impact and some are posted with the Intercompany Customer (sales) and Intercompany Vendor (purchase). If you have modified or deleted the Customer/Vendor record in your Cronus data, then transactions for those Customer/Vendor records are skipped.

With the Intercompany Customer and Intercompany Vendor, the case is different. Even if you delete the Intercompany Customer and Intercompany Vendor records, the transactions are still created and posted. This is because the MEM sample data creates those missing records for the MEM Entity Setup. When any transaction is posted with an Intercompany Customer or Intercompany Vendor then additional transactions are created as expected.

For example, if you install the MEM sample data with the Global Dimension 1 Code, and sales invoices are created and posted with Entity 000, and have the Intercompany Customer related to Entity 100. Then, purchase orders with Entity 100 and the Intercompany Vendor related to Entity 000 are created as well.

New transaction records that are created with MEM sample data include the following:

  • New sales, purchase, and General Journal transactions
  • Five orders and five invoices are created and posted
  • Ten General Journal transactions are created and posted
    • Some of General Journal transactions have intercompany impact and some do not have intercompany impact.