Customer name withheld · 2026 delivery

JDE kit costs did not update after a same-day rerun

What changed: A costing defect found with business users and corrected for production.

The problem behind the request

A consumer-products business needed to revise the way its JD Edwards custom processes calculated landed costs for kits. The work concerned freight and overhead components, the relationship between component costs and kit costs, and the rules used to select the correct values. For a delivery manager, the concern is whether a correction to source data will produce the expected result when the process runs again. The team was working toward reliable cost processing after corrections, so business users could move forward with figures they could check.

Understand the existing process before changing the calculation

Allari analyzed three existing custom applications: the landed-cost component process, work-file processing and kit-component rollup. The specialist reviewed behavior and dependencies, then defined kit-level calculations using lookup logic and hierarchy rules. The change had to fit the existing data writes and preserve the surrounding workflow.

Bring development and business testing together

The development work changed the processing logic to exclude selected components from component-level rollup and derive kit-level values according to the agreed rules. Unit testing included standard scenarios, different component structures and exceptions. The notes record issues found during testing, code corrections and further testing. Business users then joined an integration and acceptance-testing session to review freight and overhead behavior. Testing was part of delivering the change, rather than an assumption made after code was written.

Find the defect that the original request did not describe

Testing exposed a lookup issue when freight or overhead costs were not defined at the specific category level. Allari worked through successive code changes and tests to address it. The team also found an existing defect: after source-data corrections, rerunning a kit-cost rollup on the same day did not update landed costs. The specialist corrected the rerun behavior as part of the delivery.

What was delivered and validated

Allari completed the costing change, worked through lookup exceptions and corrected the same-day rerun defect. Unit and integration testing included business users, and the production package was built and deployed successfully.

What a delivery manager can take from this

The customer brought the costing rules, context and test scenarios. Allari brought application analysis and development, worked through the exceptions with users and carried the change into production. Correcting the rerun behavior addressed the underlying defect instead of leaving the team to repeat a manual correction. Allari’s Client Solutions Manager connects the required specialists, customer priorities and approved budget around that work.

Review the costing workflow your team cannot trust.

Bring the symptom, business consequence and current workaround. Together, we’ll review your priorities, process and budget, define the work and agree how your team will validate the result.

Discuss this kind of work →Explore the relevant service →
Coordinated expertise across business analysis, support, development, ERP operations, integrations, automation and ERP team mobilization.

Allari at Work

Your IT team.
Backed by an entire delivery organization.

Functional and technical specialists, coordinated around your priorities.

Discuss your next priority →

Explore another example of the challenges your team faces.

Search all delivery examples →