Table of Contents

Assembly Order Import Feature - Setup & Processing Guide

Overview

The Assembly Order Import feature in the Linc Third Party Transactions extension enables automatic creation of Business Central Assembly Orders from imported transaction data. This system supports manufacturing and assembly processes with comprehensive item validation, location management, and production scheduling capabilities for assembly operations.

Key Components

  • Application Area: Manufacturing
  • Transaction Types: Assembly
  • Supported Line Types: Items only
  • Document Types: Assembly Order
  • Output: Business Central Assembly Orders/Headers

Prerequisites

1. Basic Business Central Setup

  • Manufacturing Setup configured
  • Assembly items properly set up in Item table
  • Assembly BOMs configured for assembly items
  • Locations configured (if using location-based assembly)
  • Unit of Measure codes defined
  • Dimensions configured (if using dimension tracking)
  • Assembly Management functionality enabled

2. Extension Setup

  • Linc Third Party Transactions extension installed
  • Appropriate user permissions configured
  • Assembly item master data ready for processing

Step-by-Step Setup Instructions

Step 1: Configure Third Party Setup for Assembly Orders

  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 assembly order setup
  • Application Area: Set to Manufacturing
  • XMLPort ID: Select appropriate import XMLPort for file imports
  • No. of Header Rows: Number of header rows to skip in import files

Processing Options

  • Use Mapping: Enable Third Party Mappings for value translation
  • Attempt Direct Mapping: Try direct value resolution when mapping not found
  • Use Default Dimensions: Use BC default dimensions vs imported dimensions
  • Exclude Dimensions from Header: Don't apply dimensions to assembly order header
  • Use Import Description: Use imported description vs item description
  • Use Due Date from Import: Apply imported due dates to assembly orders
  • Ignore Zero Value Lines: Automatically archive zero-quantity lines

Step 2: Configure Assembly Item Mappings (if using mappings)

If Use Mapping is enabled:

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

Item Mappings

  • Third Party Code: Same as setup record
  • Mapping Type: Item
  • Third Party Reference No.: External assembly item identifier
  • Mapping No.: Internal BC Assembly Item No.
  • Variant Code: (Optional) Specific item variant
  • Unit of Measure Code: (Optional) Specific UoM
  • Split: (Optional) Percentage split for multi-item assembly mapping

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 3: 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 Assembly Orders

Mandatory Fields

  • Application Area: Must be "Manufacturing"
  • Transaction Type: Must be "Assembly"
  • Line Type: Must be "Item" (only assembly items supported)
  • Line Type No.: Assembly item number (external or BC format)
  • Line Quantity: Assembly quantity (must be greater than zero)
  • Transaction Date: Will be used as posting date
  • Transaction Due Date: Assembly completion due date
  • Document No.: External document reference
  • Ext. Document No.: External assembly order number
  • Location Code: Assembly location
  • Variant Code: Assembly item variant
  • Unit of Measure: Unit of measure code
  • Line Amount: Assembly unit cost (applied to Unit Cost field)
  • Description: Assembly order description
  • 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 Manufacturing 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 "Assembly"
  • Line Type: Must be "Item" for assembly orders
  • Assembly 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 assembly item
  • Variant Validation: Assembly item variant exists if specified
  • BOM Existence: Assembly BOM exists for the assembly item (if applicable)

Split Processing Support

The system supports splitting single imported transactions into multiple assembly orders:

  • Multi-Item Mapping: Create multiple assembly orders from one transaction
  • Split Percentage Validation: Split percentages must total 100%
  • SPLIT Indicator: System marks multi-split transactions appropriately

Validation Results

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

Step 3: Create Assembly Orders

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

Assembly Order Creation Logic

The system creates assembly orders with comprehensive manufacturing support:

Basic Assembly Header Creation
  • Document Type: Assembly Order
  • Item No.: From validation/mapping (assembly item)
  • Quantity: From transaction quantity
  • Location Code: Assembly location (if specified)
  • Variant Code: From validation/mapping
  • Unit of Measure: From validation/mapping
  • Posting Date: From transaction date
  • Due Date: From transaction due date (if enabled in setup)
  • Creation Date: System work date
Cost and Pricing Application
  • Unit Cost: Applied from Line Amount field (if provided)
  • Cost Calculation: Integrates with BC assembly costing
Dimension Processing
Default Dimensions Option:
  • Use Default Dimensions = True: Uses item/location default dimensions
  • Exclude Dimensions from Header = True: No dimensions on assembly header
  • Use Default Dimensions = False: Uses imported dimension values
Mapping-Based Creation

When mappings are used:

  • Mapping Resolution: Uses item mapping for assembly item
  • Variant Assignment: From mapping variant code
  • UoM Assignment: From mapping unit of measure
  • Direct Mapping Fallback: Attempts direct resolution if mapping fails
Split Assembly Processing

For multi-item splits:

  • Multiple Orders: Creates separate assembly orders for each split
  • Quantity Distribution: Distributes quantity based on split percentages
  • Cost Allocation: Allocates costs proportionally across split orders

Step 4: Review and Release Assembly Orders

  1. Navigate to Assembly Orders
  2. Filter by Third Party Code field to see imported orders
  3. Review created assembly orders:
    • Verify assembly items and quantities
    • Check location assignments
    • Validate dimension assignments
    • Confirm due dates and scheduling
    • Review assembly BOM components
  4. Release assembly orders when ready for production

Advanced Features

Assembly BOM Integration

  • Automatic BOM Explosion: System validates assembly items have proper BOMs
  • Component Validation: Ensures all BOM components are available
  • Location Consistency: Validates component availability at assembly location

Production Scheduling

  • Due Date Management: Uses imported due dates for production scheduling
  • Creation Date Tracking: Maintains audit trail of assembly order creation
  • Priority Management: Supports production priority through dimension handling

Flexible Assembly Assignment

  • Item Validation: Ensures only genuine assembly items are processed
  • Variant Support: Full variant code support for assembly items
  • UoM Flexibility: Supports different units of measure for assembly quantities

Cost Processing

  • Unit Cost Integration: Applies imported costs to assembly unit cost
  • Standard Cost Override: Allows override of standard assembly costs
  • Cost Validation: Integrates with BC standard costing methods

Multi-Assembly Support

  • Split Processing: Creates multiple assembly orders from single transaction
  • Percentage Allocation: Distributes quantities and costs by percentage splits
  • Individual Tracking: Maintains separate tracking for each split assembly

Validation Rules & Error Messages

Critical Errors (Will prevent processing)

  • "Third Party Setup for %1 was not found"
  • "No Mapped Item Found"
  • "Assembly items must have Line Type = Item"
  • "Split field is [value]" (when split percentages don't total 100%)

Assembly-Specific Validation

  • Assembly item must exist in Item table
  • Assembly item must be set up for assembly (Assembly Policy configured)
  • Location code validation (if assembly location required)
  • BOM existence validation (if using assembly BOMs)
  • Dimension value existence and date validity

Troubleshooting Guide

Common Issues & Solutions

1. "No Mapped Item Found"

Solutions:

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

2. Assembly item validation failures

Solutions:

  • Verify items are configured for assembly in Item table
  • Check Assembly Policy field on assembly items
  • Ensure Assembly BOM exists for assembly items
  • Validate item assembly setup completeness

3. Split percentage errors

Solutions:

  • Ensure split percentages total exactly 100%
  • Verify all split mappings are configured correctly
  • Check for rounding issues in split percentages
  • Review multi-item split mapping setup

4. Location validation failures

Solutions:

  • Verify location codes exist in BC Location table
  • Check location mapping if using mapped values
  • Ensure locations allow assembly operations
  • Validate location assembly configuration

Solutions:

  • Verify Assembly BOM exists for assembly items
  • Check BOM component availability
  • Validate BOM version and date ranges
  • Ensure BOM components are properly configured

6. Due date calculation issues

Solutions:

  • Enable "Use Due Date from Import" in setup
  • Verify imported due dates are valid
  • Check calendar setup for production scheduling
  • Validate work center capacity calendars

7. Zero assembly orders created

Solutions:

  • Verify transactions have "Checked" validation status
  • Check transaction type filter (must be "Assembly")
  • Ensure Line Quantity is greater than zero
  • Review error messages on failed transactions
  • Verify assembly item configuration

8. Cost application failures

Solutions:

  • Verify Line Amount field has valid cost data
  • Check assembly item costing method
  • Validate cost calculation setup
  • Review standard cost configuration

Best Practices

  1. Test with Small Batches: Start with a few assembly transactions to verify setup
  2. Configure Assembly Items: Ensure proper assembly item and BOM setup
  3. Use Consistent Mappings: Standardize assembly item mappings
  4. Monitor BOM Dependencies: Validate component availability before assembly
  5. Validate Before Processing: Run validation immediately after import
  6. Review Assembly Orders: Always review before release for production
  7. Handle Split Mappings Carefully: Test multi-item split scenarios thoroughly
  8. Backup Before Processing: Take database backup before large imports
  9. Location Coordination: Ensure assembly locations are properly configured
  10. Production Scheduling: Coordinate with production planning processes

Performance Considerations

  • Batch Size: Process large assembly imports in smaller batches for better performance
  • BOM Validation: System validates assembly BOMs during processing
  • Component Checking: Performance may be impacted by complex BOMs
  • Validation Timing: Run validation during off-peak hours for large datasets
  • Archive Management: System automatically archives processed transactions
  • Assembly Explosion: Consider BOM complexity impact on processing time

Integration Events

The system provides integration events for customization:

  • OnAfterCreateAssemblyHeaderBeforeModifyTransact: Custom assembly header processing
  • OnAfterUpdateThirdPartyTransactionAfterDocumentCreatedTransact: Post-creation updates
  • Custom validation logic can be added through integration events

Security & Permissions

Required permissions for users:

  • Read/Write access to Third Party Transaction tables
  • Insert/Modify access to Assembly Header and Assembly Line tables
  • Execute permissions on assembly processing codeunits
  • Access to setup and mapping pages
  • Assembly order management permissions
  • Manufacturing module access rights