We are creating two new tables for BaaN, of which there will be the relevant sessions generated.

I have a question about thye naming conventions for both the tables and sessions.

The tables are to be for the service module under service and maintanence.

I have had a look at the tables and established in my mind that the names for the tables should be tssma330b40oliv0 and tssma331b40oliv0.

Will naming them this cause any problems and are there any issues I need to consider for naming the sessions? Should I name the sessions the same as the tables?

The naming convention that I have used is the standard BaaN naming convention but I would like to have this confirmed before I go ahead with creating the table definitions.

Cheers guys

I have always used the following naming convention for tables:

tt xxx 000

tt = the package such as tc or ts
xxx = the module such as com or sma
000 = a sequential number

I have alway set my table numbering starting from 900 eg. tssma900 so that it will not interfere with any tables baan may introduce.

As for session naming, this works as follows:

tt xxx 9y99m000

tt = package
xxx = module
y = session type = 4 for print session, 5 for display session
999 = the table number
000 = sequence number

if your table is tssma905 and you are creating a display session the your session code will be tssma9505m000. Another display session for the same table will be tssma9505m001

A good way to distinguish customised session from standard baan sessions is to do add a c in the first character of the sequnce number in the session code eg.

tssma9505mc00
tssma9505mc01

If have also seen this done:

tssmac505m000

I hope this helps

This is great, however we have a table under sma numbered 999 I should still be able to number my table 905 though shouldn't i?

That should be fine, you could maybe try using the 800 range instead if you like. It's up to you

i have tried to use the domain tt yeno but it has given me an error saying no integration with package tt!!

Help!! any ideas...

Cheers

Excerpt from the Baan IV Development 1 Training manual:

Coding of tables:
[...]

Ranges for customization types:
c (customization by dealer) 901-935
l (localization) 936-950
b (business-specific version) 951-965
d (dealier-specific version) 966-980
j (junior compact version) 981-985
o (own development by customer) 986-995

So if you're developing customizations for your own company, it's recommended to use the 986-995 range, if possible. Also, Baan is not violating their own recommended standard by ending a table in 999, since only 901-995 are reserved for other parties.

You can't use components from package tt. Use domain tcyesno instead of ttyeno.

In your original post you table names are to long. I can only assume that this was either the package VRC or session name that you were trying to create.

If it is the vrc you should really have the release in the middle like B40Oc3liv0.

If it is sessions that you are creating for a NEW table it should be as stated in the Software Coding STandards.

pp = package code

mmm = module code

s = submodule code. This is the first character of the table. It is called submodule to group like tables/functions together. Like all sales order tables could start with 4 and all commision tables/sessions start with 1. So when you go to move objects they can be grouped.

f = function code.
1 = maintenance (and display baan v)
2 = processing
3 = reserved
4 = print
5 = display only
6 = reserved
7 = graph
8 = auxilary
9 = conversion

o = type of process
m = main baan iv, multi line baan v
s = sub baan iv, single baan v

y = session session number; if more than one session is present for the same main table, this sequence number can be used to define the different sessions, starting with 0. Usually baan assigned.

cc = customixation type. This would be used when you are customizing a standard baan session, that you were going to use along with baan standard sessions. IE if you were going to split some functionality out from the standard, or were going to add a new session for additional functionality, that following standards would be named the same as a standard baan program. If you are customizing a standard program, and would not need to run the standard. you would not have to rename it. After all that is what VRC's are for, to store your customizations.