Due to the new naming convention in ERP are all multi occ sessions called like aabbbxxxmxxx single occ sessions aabbbxxxsxxx.
But what about print sessions? I checked some print sessions in "wh" and found they're all named with an "m". But the form of a print session ist normaly a single occurence.

How is the offical way to name a printsession?


Thanks
Spartacus

Dear spartacus

The naming convention follows the pattern ppmmmxxxxlyyy
pp denotes the package
mmm denotes the module
xxxx denotes the session number. Now print sessions will have the number 4 as the second digit of this part, eg. 0400, 1400, 2400, 2434, etc
l denotes the level; m means main session (can be executed independently), while s means subsession (can only be executed from other sessions
yyy additional session number

Rgds,
Paul

Hi Paul,

the problem exists esp. for the level "l". Because since ERP "m" stands for "multi occ session" and "s" for a "single occ session", no more for "main" and "sub".

But as I wrote already, IMHO Baan doesn't follow this convention in case of "print sessions"

regards
Spartacus

The m for multi and the s for single only exists for type I, II and III forms. The type IV forms (print sessions etc) do not have this rule. In that case only a main session exists.

Hope this helps,
Dick

Hi all,

The reasoning behind the 'm' in the code for print sessions is:
most of the time when you print data, you print multiple records. So an 'm' is more appropriate than an 's'.

But technically, the classification of multi/single occ is incorrect for print sessions. These are 'no occurrence' screens.

Andre de Vrij

Having the naming pattern ppmmmxxxxlyyy please clarify the yyy additional session number. I was told to use 000, 100, 200, etc.
Is it this the rule to use with Infor LN 10.7 ? Or, it could be 000, 001, 002, etc.
Is there a rule to say if session is Print type give yyy 000, 001, etc. AND in case the session is Maintenance the yyy is to be 100, 200, 300, 400 etc. ?
Well, I understand it is a naming CONvention but a complete clarification would be useful.