Epicor Functions (EFx) Implementation Guide

Overview

Epicor Functions (EFx) are a major architectural improvement introduced in recent ERP versions. They allow developers to bundle C# business logic into discrete libraries that can be reused across BPMs, reports, and REST APIs. For library scope guidelines, visit the EpiUsers Epicor Functions threads

Exposing custom calculations as Epicor Functions prevents code duplication. If a pricing algorithm changes, developers can modify a single EFx library instead of rewriting scripts across 15 separate Method Directives.

Technical Implementation Details

To implement this solution in your Epicor environment, utilize the following code block. Ensure you replace the standard configurations with your company database names, server URLs, and keys.

// Epicor Function (EFx) Library: CalculateBulkDiscount
// Input parameters: double orderTotal, string customerGrp
// Output parameter: out double discountPct
discountPct = 0.0;

if (customerGrp == "DIST")
{
    if (orderTotal > 10000) discountPct = 0.15;
    else if (orderTotal > 5000) discountPct = 0.10;
}
else if (customerGrp == "RETAIL" && orderTotal > 15000)
{
    discountPct = 0.05;
}

// Return message via output parameter or write to system logs
// (Note: UI direct dialogs like PublishInfoMessage are unsupported in isolated Functions context)
Ice.Diagnostics.Log.WriteEntry("Discount calculated: " + discountPct.ToString("P"));

Process Verification and Flow

Additionally, Epicor Functions run in an isolated execution sandbox, making migrations easier. Custom library methods can be exported and imported into new systems without breaking standard UI hooks.