At 03:09 PM 1/12/2001 , you wrote:
>I was wondering if someone could walk me through adding a Report Builder
>report to the menu in Vantage. We are currently running version 3.00.630.
Sarah already gave some good steps, and it's all in the online help,
too. So I'm gonna skip the little details and throw in the not-as-obvious
stuff:
* Create a directory on the server for your report files. I created
\Vantage\Usaero for all our things, with a .\ReportLink under that for the
.PRLs Epicor suggests \Vantage\UD, but I figure it's best to keep my
things as far away from their's as possible (I think custom programming
expects to use .\UD for their things?)
* Add an entry in Custom Report Link (under all the Master File
menus.) The help file erroneously states the report ID must use a "UD"
prefix if it will be added to the menus. This is not true; don't do
it. (10 chars is too short as is, without throwing away the 1st two!)
* Use a consistent naming scheme for all your reports and menu items. I
use the standard Vantage prefixes, like JC for Job Mgt, AP for Accts
Payable, etc.
* Try to use consistent naming, abbreviations, capitalization, punctuation,
etc. in your report descriptions. Sounds kinda uptight, but, hey, I think
it makes 'em look a lot nicer, and more legible. The description you use
in the Report Link will be pulled into the menu item by default.
* When you enter the path to the library in Report Link, BE SURE to use a
relative pathname to the \Vantage directory,
like: usaero\reportlink\om_open_sos.prl
If you use an absolute path, like
V:\Vantage\usaero\reportlink\om_open_sos.prl you will have to change every
dang one of them if you upgrade Vantage and the drive letter changes (BTDT!)
* I create a Custom Reports menu under each of the standard menus (eg:
Purchase Mgt / Custom Reports) rather than mix them with the regular
Reports items. The IDs for the sub-menus and items do demand the UD
prefix. I use the standard prefix with UDppCR01 for the menu ID, eg:
UDPMCR01 in purchasing. (this is in System Utilities / Menu Structure
Maintenance if you haven't found it yet.)
* You will need a security code for the menu and each item. There are a
few different strategies on setting up security. I have all my menus open
to everyone, and then assign allowed groups to each item. So I create a
security entry for my Custom Reports menu, titled something like "Job Mgt
Custom Report Menu" open to <everyone> Then one security entry that I use
on ALL my report items under it, titled "Job Mgt Custom Repos - All" that
handles group access. Re-using one security code on all the reports keeps
things a lot more simple, and provides adequate security control for
us. The security IDs are auto-generated.
* You need a menu item ID for each report you add; they must start with
"UD" I assign mine like UDppnnnn where pp is the module prefix (JC, PM,
AP) and nnnn is a unique number (I increment it for each report I add.) So
a new purchasing report might be UDPM5073
Here's a summary:
submenu UDPMCR01 Custom Reports
security UDC001 Purchasing Custom Reports Menu
menu item UDPM5033 Matl PO Suggestions - by Due Date
security UDC002 Purchasing Custom Reports - All
report link PMMSUG1 Matl PO Suggestions - by Due Date
PRL file usaero\reportlink\PM_mat_suggest.prl
-Wayne Cox