Table of Contents

Item Journal Import Feature - Setup & Processing Guide

Overview

The Item Journal Import feature in the Linc Third Party Transactions extension enables automatic creation of Business Central Item Journal Lines from imported transaction data. This system supports inventory adjustments, stock movements between locations, and comprehensive item tracking with validation capabilities for inventory management processes.

Key Components

  • Application Area: Inventory
  • Transaction Types: Item Journal
  • Supported Entry Types: Positive Adjustment, Negative Adjustment
  • Supported Line Types: Items only
  • Output: Business Central Item Journal Lines

Prerequisites

1. Basic Business Central Setup

  • Inventory Setup configured
  • Items properly set up in Item table
  • Locations configured (if using location-based adjustments)
  • Unit of Measure codes defined
  • Dimensions configured (if using dimension tracking)
  • Item Journal Templates and Batches configured

2. Extension Setup

  • Linc Third Party Transactions extension installed
  • Appropriate user permissions configured
  • Item Journal Templates and Batches ready for processing

Step-by-Step Setup Instructions

Step 1: Configure Third Party Setup for Item Journals

  1. Navigate to Third Party Setup List (Page 71112700)
  2. Create or modify setup record with the following configuration:

General Settings

  • Third Party Code: Unique identifier for your item journal setup
  • Application Area: Set to Inventory
  • XMLPort ID: Select appropriate import XMLPort for file imports
  • No. of Header Rows: Number of header rows to skip in import files

Journal Configuration

  • Item Journal Template: Default template for item journal processing
  • Item Journal Batch: Default batch for item journal processing

Processing Options

  • Use Mapping: Enable Third Party Mappings for value translation
  • Attempt Direct Mapping: Try direct value resolution when mapping not found
  • Use Default Journal Dimensions: Use BC default journal dimensions vs imported dimensions
  • Use Import Journal Description: Use imported description vs item description
  • Use Import Amount: Apply imported amounts to journal lines
  • Ignore Zero Value Lines: Automatically archive zero-quantity lines

Step 2: Configure Item Journal Templates & Batches

  1. Navigate to Item Journal Templates

  2. Set up or verify existing templates:

    • Template Type: Must be "Item"
    • Name: Template code to use in Third Party Setup
    • Description: Descriptive name
    • Source Code: Appropriate source code for tracking
    • Reason Code: Optional reason code for adjustments

  3. Navigate to Item Journal Batches

  4. Set up or verify batches for your template:

    • Journal Template Name: Link to your item journal template
    • Name: Batch code to use in Third Party Setup
    • Description: Descriptive name
    • No. Series: Number series for document numbers (optional)

Step 3: Configure Item Mappings (if using mappings)

If Use Mapping is enabled:

  1. Navigate to Third Party Mappings (Page 71112706)
  2. Create item mapping records:

Item Mappings

  • Third Party Code: Same as setup record
  • Mapping Type: Item
  • Third Party Reference No.: External item identifier
  • Mapping No.: Internal BC Item No.
  • Variant Code: (Optional) Specific item variant
  • Unit of Measure Code: (Optional) Specific UoM

Location Mappings (if using locations)

  • Mapping Type: Location
  • Third Party Reference No.: External location code
  • Mapping No.: Internal BC Location Code

Dimension Mappings (if using dimensions)

  • Mapping Type: Shortcut Dimension 1 Code through Shortcut Dimension 8 Code
  • Third Party Reference No.: External dimension value
  • Mapping No.: Internal BC Dimension Value Code

Step 4: Configure Excel Import Mapping (For Excel Files)

If importing from Excel files:

  1. Navigate to Third Party Excel Import Mapping (Page 71112709)
  2. Create field mappings:
    • Third Party Code: Same as setup record
    • Mapping Type: Field (column reference) or Fixed Value
    • Third Party Reference No.: Column name or fixed value
    • Third Party Trans. Field ID: Target field in transaction table

Required Data Fields for Item Journals

Mandatory Fields

  • Application Area: Must be "Inventory"
  • Transaction Type: Must be "Item Journal"
  • Line Type: Must be "Item" (only items supported)
  • Line Type No.: Item number (external or BC format)
  • Line Quantity: Item quantity (positive for increases, negative for decreases)
  • Transaction Date: Will be used as posting date
  • Document No.: External document reference
  • Ext. Document No.: External document number
  • Location Code: Source location for adjustment
  • To Location Code: Destination location (creates transfer between locations)
  • Variant Code: Item variant
  • Unit of Measure: Unit of measure code
  • Line Amount: Transaction amount (if using imported amounts)
  • Description: Line description
  • Journal Template: Specific journal template (overrides setup default)
  • Journal Batch: Specific journal batch (overrides setup default)
  • Shortcut Dimension 1-8 Code: Dimension values

Processing Workflow

Step 1: Import Transaction Data

Choose your import method:

Method A: File Import (XML/Excel)

  1. Navigate to Third Party Transactions (Page 71112707)
  2. Filter to Inventory application area
  3. Click Import Transactions
  4. Select your configured Third Party Setup
  5. Choose file to import

Method B: Direct API/Integration

  • Use Business Central APIs to insert records into ThirdPartyTransact_THI_LINC table

Step 2: Validate Imported Data

  1. In Third Party Transactions page
  2. Select transactions to validate (or use Ctrl+A for all)
  3. Click Validate action

Validation Process

The system validates:

  • Setup Existence: Third Party Setup record exists
  • Transaction Type: Must be "Item Journal"
  • Item Resolution: Via mapping or direct lookup
  • Location Validation: Location codes exist if specified
  • Dimension Validation: All dimension values exist if specified
  • Unit of Measure: Valid UoM for the item
  • Variant Validation: Item variant exists if specified

Validation Results

  • Status = Checked: Transaction passed all validations
  • Status = Error: Issues found (check Error Message field)
  • Status = Ignore: Manually ignored transactions

Step 3: Create Item Journal Lines

  1. Filter to show validated transactions (Validation Status = "Checked")
  2. Select transactions to process
  3. Click Create Item Journal Lines action
  4. Confirm creation dialog

Journal Line Creation Logic

The system creates different types of journal lines based on location setup:

Single Location Adjustments
  • Location Code specified, To Location Code blank:
    • Creates one journal line with Entry Type based on quantity sign
    • Positive Quantity → Positive Adjustment
    • Negative Quantity → Negative Adjustment
Location-to-Location Transfers
  • Both Location Code and To Location Code specified:
    • Creates two journal lines:
      1. Negative Adjustment: From source location (removes inventory)
      2. Positive Adjustment: To destination location (adds inventory)
    • Both lines use absolute quantity value
Zero Location Processing
  • Neither location specified: No journal lines created for location-based items

Line Details Applied

  • Posting Date: From transaction date
  • Document No.: From import data or batch number series
  • Item No.: From validation/mapping
  • Description: From import (if enabled) or item description
  • Quantity: Absolute value of transaction quantity
  • Amount: From import (if enabled)
  • Unit of Measure: From validation/mapping
  • Variant Code: From validation/mapping
  • Location Code: As determined by logic above
  • Dimensions: Applied per setup configuration
  • External Document No.: From import data

Step 4: Review and Post Journal Lines

  1. Navigate to Item Journals
  2. Select appropriate Journal Template and Batch
  3. Review created journal lines:
    • Verify quantities and amounts
    • Check location assignments
    • Validate dimension assignments
    • Confirm posting dates
  4. Post journal when ready

Advanced Features

Flexible Journal Assignment

  • Transaction-Level Override: Specify different journal template/batch per transaction
  • Setup-Level Default: Use setup defaults when transaction fields are blank
  • Validation: System ensures journal template and batch exist

Location Transfer Processing

  • Automatic Dual-Line Creation: Creates both negative and positive adjustments
  • Quantity Sign Handling: Always uses positive quantities for both lines
  • Location Validation: Validates both source and destination locations

Dimension Handling

  • Comprehensive Support: All 8 shortcut dimensions supported
  • Import vs Default: Choose between imported dimensions or BC defaults
  • Mapping Integration: Full mapping support for dimension values

Amount Processing

  • Optional Amount Import: Enable "Use Import Amount" to apply transaction amounts
  • Automatic Amount Handling: Uses absolute values for proper journal processing
  • Cost Integration: Integrates with BC's standard item costing

Batch Processing

  • Line Cleanup: Automatically removes blank journal lines before processing
  • Sequential Line Numbers: Maintains proper line numbering (10000 increments)
  • Document Number Management: Uses batch number series or imported document numbers

Validation Rules & Error Messages

Critical Errors (Will prevent processing)

  • "Third Party Setup for %1 was not found"
  • "No Mapped Item Found"
  • "Item Journal Template and Batch must have a default value in Third Party Setup, if Journal Template and Journal Batch is empty"

Validation Failures

  • Item existence verification
  • Location code validation
  • Dimension value existence
  • Unit of measure compatibility
  • Variant code validation
  • Journal template/batch existence

Troubleshooting Guide

Common Issues & Solutions

1. "No Mapped Item Found"

Solutions:

  • Create item mapping in Third Party Mappings
  • Enable "Attempt Direct Mapping" if item codes match BC
  • Verify items exist in BC Item table
  • Check item number format and length

2. Journal Template/Batch errors

Solutions:

  • Configure Item Journal Template and Batch in Third Party Setup
  • Ensure journal template type is "Item"
  • Verify journal batch exists and is linked to correct template
  • Check journal template and batch names match exactly

3. Location validation failures

Solutions:

  • Verify location codes exist in BC Location table
  • Check location mapping if using mapped values
  • Ensure location codes are active and not blocked

4. Dimension validation errors

Solutions:

  • Check dimension values exist in BC
  • Verify dimension mapping configuration
  • Consider enabling "Use Default Journal Dimensions"
  • Check dimension value restrictions

5. Zero journal lines created

Solutions:

  • Verify transactions have "Checked" validation status
  • Check transaction type filter (must be "Item Journal")
  • Ensure Line Quantity is not zero
  • Review error messages on failed transactions

6. Duplicate document numbers

Solutions:

  • Configure number series on journal batch
  • Ensure imported document numbers are unique
  • Check document number format and length limits

7. Posting failures

Solutions:

  • Verify all required fields are populated
  • Check item availability and setup
  • Ensure posting date is in open period
  • Validate dimension combinations

Best Practices

  1. Test with Small Batches: Start with a few transactions to verify setup
  2. Use Consistent Templates: Standardize on specific journal templates and batches
  3. Configure Mappings: Better control than direct mapping alone
  4. Validate Before Processing: Run validation immediately after import
  5. Monitor Error Messages: Address validation errors before processing
  6. Backup Before Processing: Take database backup before large imports
  7. Review Journal Lines: Always review before posting
  8. Use Number Series: Configure number series for automatic document numbering
  9. Handle Zero Quantities: Enable "Ignore Zero Value Lines" for clean processing
  10. Test Location Logic: Verify location transfer logic with sample data

Performance Considerations

  • Batch Size: Process large imports in smaller batches for better performance
  • Journal Cleanup: System automatically removes blank lines before processing
  • Validation Timing: Run validation during off-peak hours for large datasets
  • Archive Management: System automatically archives processed transactions
  • Line Numbering: Uses standard 10000 increments for proper sequencing

Integration Events

The system provides integration events for customization:

  • Custom validation logic can be added through integration events
  • Journal line creation can be extended with custom processing

Security & Permissions

Required permissions for users:

  • Read/Write access to Third Party Transaction tables
  • Insert/Modify access to Item Journal tables
  • Execute permissions on processing codeunits
  • Access to setup and mapping pages
  • Item journal posting permissions