I'm trying to use electronic messages to execute an ER import configuration that will create general journals.
When I execute the configuration directly from the electronic reporting workspace, it's successful.
When I run a message processing action through which is configured to execute the same ER import configuration, I get the message, "Running electronic message processing Running action 'Import' Model mapping to appropriate destination does not exist."
There must be some checks and validations or conditions that are expected when importing via the electronic messages framework.
Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today!
I see this was posted a few days back and hopefully you've solved by now - incase not, here are a few ideas:
Specifically, the error indicates that the system cannot find a model mapping to the appropriate destination.
Validate the Model Mapping
Open the Electronic Reporting workspace and navigate to the Model Mappings section.
Ensure that the configuration you are trying to run has an associated Model Mapping that defines how data is mapped to the destination.
Validate the configuration to confirm that the mapping is complete and error-free.
Review the Message Processing Action
Go to Tax > Setup > Electronic messages > Message processing actions.
Check the Action settings and verify that it points to the correct ER configuration.
Confirm that the selected configuration is set up to use the appropriate model mapping.
Check Related ER Artifacts
Ensure that the Format Mapping and Format Configuration linked to the import configuration are correctly defined.
Double-check the Data Model hierarchy and its relationship to the format.
Link the Model Mapping
If the model mapping is not explicitly linked in the electronic messages framework, you’ll need to link it manually.
In the Electronic Reporting workspace, open the Advanced settings for your configuration and assign the appropriate model mapping.
Recheck Parameters
Ensure that all required parameters (e.g., source and target data structures) are set up in the Electronic Message and its Processing Action.
Missing or incorrectly defined parameters can cause the framework to fail validation.
Test by Running the Action
Test the action manually with a smaller dataset to ensure that the model mapping and configuration work seamlessly in the context of electronic messages.
Consult Documentation
Refer to the official documentation for electronic messages and ER templates. It provides additional details on configuring and linking model mappings.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
142
Share
Report
All responses (
Answers (
