By using this website, you agree to our Terms of Use (click here)
Hi Everyone,
I have 5 Import Scenarios that run to compile customer invoices from different sources. This is all working perfectly, however I have the imports running on schedules so they trigger one after the other in order (there is about 15 minutes separation). I was thinking, is there a generic inquiry that can pull out Import Scenario status, so I can attach this to a Business Event, to fire off the subsequent Import Scenarios?
So a BA to monitor Import Scenario 1, once it changes from Processing? to Complete? it then triggers Import Scenario 2, and so on. This way if one of the imports blows out in time, it won't break the subsequent imports, or waste time waiting for a schedule when it could be processing.
Or if someone has different approach to triggering Import Scenarios, I'm all ears. To save anyone asking, yes the 5 imports are required. No, I don't believe there would be anyway to condense them into 1 Import Scenario. Yes I'm happy with the process as it works well.
Cheers!
Any progress on this?
We have something similar importing files from an FTP site, then shortly after running the Import Scenario to load the data from those files.
I was looking for a business event that could monitor the Import Scenario log for an error and trigger a notification.
This is a brilliant idea! I've never tried using a Generic Inquiry to "daisy chain" Import Scenarios together, but that would be really cool if someone could figure it out. Business Events seem like a "light workflow engine", but this idea would make them more like a "workflow engine" if you could pull it off.
An idea I've been brainstorming and haven't yet tested is making a BE subscriber scenario that works on the Import By Scenario screen. All this workflow scenario would do is navigate to a specified scenario and take the <Prepare & Import> action. The BE itself would be triggered by a GI of PX.SM.UploadFileRevision which is looking for new versions of the data source file so as to trigger the related imports. What I don't know is, if you had multiple workflow scenarios, if they would wait for the triggered Import By Scenario to finish before moving on to start the next one.
Business Event subscribers execute in order, so daisy-chaining together import scenarios should be as easy as putting them in the proper order on the same BE. Flag them to 'Stop on Error' if you want the chain to stop if one of them fails. Then you can monitor that chain of scenarios by creating a GI of BPEventHistory to look for failed event runs, potentially filtered down to that specific Event ID.
My specific use case is simply Stock Item creation with additional import scenarios to populate various inter-record connections like the Vendor catalog, sale price, cross references, related products, etc. from a single master file.