Adhoc reporting and IDM out

Hi!

Does anyone know if you can print Adhoc reports via IDM output management in Cloud? If possible, how do you configure it? I need an ad hoc report in Excel format, and in 13,4 you used report manager for that - but I would assume that is done via IDM output management in Cloud or am I wrong?

//Gunilla

Find more posts tagged with

Accepted answers

All comments

Legacy Contributor

Yes, it is possible to setup with IDM in a few steps.

Create a document type in IDM to hold your template. Upload the template file to it.

Then configure M3 in MNS060, MNS216 and AHS010, AHS110 to point to it and use it.

I would advise uploading the template with blank division attribute (if you set it up with division as attribute in IDM) and then map division to blank value in MNS060 - so you don't need the same template uploaded for every division.

[View:/cfs-file/__key/communityserver-discussions-components-files/100/AdHoc-Report-Template-Setup.docx:320:240]

[View:/cfs-file/__key/communityserver-discussions-components-files/100/M3AdhocTemplate.xlsx:320:240]

Maxime Richard

Hi,

Interesting post.

Did as you suggest but the file seems to be stucked somewhere. Report has MDS_DistributionJobs as document type!

You cannot see because it's too small but the base64 content is indeed the addhoc i am expecting to receive. The report is a basic one on OOHEAD with a filter on OACUNO.

Checking jobs in IDM, it's ok :

I am lost.

Legacy Contributor

I would not be able to tell where it goes wrong in your case, or why you are not getting output. Perhaps you can submit screenshots on your relevant MNS060, MNS216 and AHS010, AHS110 panel settings

It may also be that you have not given a proper email to send it to, or if there is not a proper sending email then IDM may have processed it but the mailserver is just ignoring it. IN AHS110 you'll need to select the adhoc email to current user, and then select the user it should be emailed to, and make sure that is in MNS205 properly, and also you will need to set a valid sender email there as well (which is selcted from crs111 and type 19 I believe)

MDS_DistributionJobs is just where IDM stores all jobs coming through, and cleans it out eventually as things are processed, Think of that kind of like MNS206 but on the IDM side.

Maxime Richard

It seems that we need to request a restart of IDM print from the CSP (Cloud Suite Portal). Just like you said, jobs are stucked and printout is not completely finished. Only the customer has admin role to do such a request... a bit complicated taken into account the current situation. Thanks for your reply !

Denis MARETTE

Hi @henrik-refsnes

I have not seen anything described in the Infor documentation about this.
so your contribution is very much appreciated.

If there is a need to improve the XLS file you proposed as a template, what would you recommend as documentation to understand what is possible?

Thank you

Legacy Contributor

From the Adhoc reporting point of view there isn't much you can do, the template is populated dynamically based on the report you configure in M3.

Denis MARETTE

Hi @henrik-refsnes

Just for my understanding:

Does the mechanism you described work because the adhoc report was not designed with the new editor (Option 1 of ASH100) or is it unrelated?

I admit that it is a bit confusing for me at this level.

Because I was trying to understand how the mapping works between the XML data generated by the execution of an adhoc report (whatever the content of the report is) and the Excel template file which has almost no structure? It's this "somewhat" magical side that escapes me.

Denis MARETTE

Hello,

I would like to know if some of you are using in a Multi-tenant Cloud environment M3 Ad Hoc Report other than generating XLS files distributed by email ? For example, by distributing the XLS files on a file server.

What would be the additional setup steps to implement this approach for example and yourarecommandations ?

Thanks

Denis MARETTE

Hi @henrik-refsnes

If I understood correctly this method allows to have a default XLS template by division for all Ad Hoc reports.

What should be adapted to this approach if we want for example to have a default template per report?

In MNS060, somewhere we would need to have the pendant attribute corresponding to Printer File but for an Ad Hoc report.
I don't know if anyone has tried to set up something that would come close to what I am expressing?

Thanks

Copyright © 2025 Infor. All rights reserved.