Source Restrictions on Business Event Import Scenario

​@lairdtim This is generated with the help of AI hope its helpful for you 

Yes, the Source Restrictions tab in Import Scenarios is generally ignored when the scenario is triggered by a Business Event in Acumatica. This is because Business Events execute the import scenario as a process rather than performing a manual data import, which means the Source Restriction conditions are not enforced in the same way.

Why is this happening?
Import Scenarios with Source Restrictions are primarily designed for manual imports. When executed via a Business Event, the system does not evaluate these conditions before running the import.
The Business Event triggers the scenario regardless of whether the condition (Cost Difference ≠ 0) is met, leading to unnecessary $0 cost adjustments.
Possible Workarounds
1. Modify the Business Event Condition
Instead of relying on the Import Scenario's Source Restriction, adjust the Business Event conditions to prevent execution when Cost Difference = 0.

Navigate to System Management → Business Events.
Find your Business Event and edit it.
In the Conditions tab, add a condition like:
Cost Difference <> 0
This ensures that the event only triggers when a cost adjustment is actually required.
2. Adjust the Import Scenario with an IF Condition
If modifying the Business Event is not an option, you can adjust the Import Scenario to check for the cost difference before creating an adjustment:

Within your Import Scenario, add an action step that validates whether Cost Difference <> 0 before proceeding with the import.
If Acumatica's IF condition logic is available in your version, apply it to skip unnecessary records.
3. Use a Custom Automation or Workflow
If neither of the above methods works, you may need to implement a custom workflow or custom business logic to filter out unwanted adjustments.

Conclusion
Since Import Scenario restrictions do not work when fired by a Business Event, the best solution is to modify the Business Event conditions so it doesn’t trigger when the cost difference is zero. This should stop the creation of unnecessary cost adjustments.

Hi @lairdtim

Have you tried to run import scenario manually, is it still ignoring the source restriction?

If yes, Please attach your import scenario, so someone can find the root cause.

Hope, it helps!

Is there a way to run an import scenario driven by a business event manually?  I assume I’d have to make a copy of it and change the data provider to a static (or GI) source.

Yes, @lairdtim

you are right, do it manually by creating a copy of same import scenario with your GI as a data provider and run it from Import by Scenario and check.

​@lairdtim 

Yes, you can use both Source restriction and Target restriction. However, when processing this way, the system will attempt to trigger the business event but will fail if it cannot find the source document.

In the past, I tested restricting updates to certain PO orders using an import scenario.

Please share the business event and import scenario if you want more troubleshot.

ranjithduraisamy72 wrote:

​@lairdtim 

Yes, you can use both Source restriction and Target restriction. However, when processing this way, the system will attempt to trigger the business event but will fail if it cannot find the source document.

In the past, I tested restricting updates to certain PO orders using an import scenario.

Please share the business event and import scenario if you want more troubleshot.

 

You’ve done this with a Source Restriction as well?  The event erroring with a target restriction makes sense, since a regular import scenario will fail a line when a target restriction is in place.  But it seems to ignore my source restriction completely.