Retirement Notice
|
|
User login
|
|
Frontpage Sponsor
|
|
Poll
|
What do you expect from your SI Implementation partner for the success of ERP implementation. Bring best practices - Not to offer more CR's Leveraging standard functions 20% Need more honesty to work with the Users until their processes are fully mapped & Users are trained 40% Focus on process automation/ integrations/ Real time data/ BI analytics 13% Stick to basics 27% Total votes: 15 |
|
|
 |

13th January 2003, 11:42
|
 |
Guru
|
|
Join Date: Dec 2001
Location: Germany
Posts: 773
|
|
Baan: BaanERP 5.0c -
DB: Oracle 8 -
OS: SunOS 5.9
|
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
|

13th January 2003, 12:54
|
 |
Guru
|
|
Join Date: Jul 2002
Location: Jakarta, Indonesia
Posts: 794
|
|
Baan: BaanIV, BaanERP -
DB: SQL Server, Informix, Oracle -
OS: Windows, HP-UX
|
ppmmmxxxxlyyy
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
|

9th February 2023, 09:31
|
Member
|
|
Join Date: Jan 2023
Posts: 39
|
|
Baan: 4,5,6,10 -
DB: sql -
OS: windows
|
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.
|

13th January 2003, 14:20
|
 |
Guru
|
|
Join Date: Dec 2001
Location: Germany
Posts: 773
|
|
Baan: BaanERP 5.0c -
DB: Oracle 8 -
OS: SunOS 5.9
|
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
|

14th January 2003, 10:19
|
 |
Guru
|
|
Join Date: Sep 2002
Location: Netherlands
Posts: 585
|
|
Baan: Triton 3.0 and higher -
DB: All -
OS: All
|
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
__________________
BTW: this post has been made on my personal view. My employer might not share my point of view.
|

15th January 2003, 11:35
|
Junior Member
|
|
Join Date: Oct 2002
Posts: 12
|
|
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
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
|
|
Thread Tools |
|
Display Modes |
Hybrid Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|