Dimesional Restrictions in DM Package

Question

I have a DM Package that calls script logic. Currenty I use a requestor to select dimensional members. I want to hard code one of my dimensions but I do not want to do it in the script logic. Is there a was to combine prompted and hard coded dimensional selections in a DM Package?
Thanks
Cliff

Answer 1

I'm not aware of a way to do this in the package (the MODIFYSCRIPT) itself -- in a manner of speaking, you want an xdim_memberset instruction in the pacakge, that's passed on to the LGF. But the package syntax only allows for member selection defined by the user at run-time. (I'm 95% certain of this, but there may be some way to configure the SelectionFile that's never been documented, and which I haven't discovered.)
What I've done in this situation is to create a core logic file, with no dimension scoping. This can then be referenced from a number of other packages via an *INCLUDE. I find this useful for currency conversion, which I often want to call as the last step of various other packages, scoped on a specific set of accounts or datasrc's or something else.
One of those wrapper LGF files only has two lines, the *xdim_memberset where you can fix the dimension members, and the *include. This wrapper is called from your package.
I think the end-result at run-time is the same as what you want, the only difference being that the administration of those hard-coded members is in the LGF wrapper file (admin console), rather than in the MODIFYSCRIPT (eData -> organize package list).