When we enter information "package,module, table, company" and click "y", what is the system doing background?

Could anybody list the operations?

Though I don't know the answer in detail , but by stretch of imagination , I can tell you following things.

1. check the company and it's package combination
2. Check the DD of that table in the current package combination.
3. whether DD in current package combination matches with that of company's package combination adn it's RDD . If not through error 512.
4. Load the table in memory and initialize the file pointer to the first record in that table.

Hi Amy,

Be careful with GTM! It works directly with Baan tables and you may accidentally damage or delete some data thru option "Modify record" or "delete".

GTM is the Table Editor for Baan. It allows you to modify records without using the session logic. So where in the session "Maintain Sales Order Lines" (tdsls4102s000) you can only edit lines for orders that also do have an order header "Maintain Sales Orders" (tdsls4101m000), due to data model constraints, you can change the order number field tdsls041.orno in table tdsls041 ("Sales Order Lines") into a non existing order number in tdsls040 ("Sales Orders").

If you need to know exactly what happens when you start it, you can use all kind of tracings and loggings. But that is not what you want to know, I suppose.

Just in case someone shouldn't know:

GTM (ttaad4100) has a smart sister/brother:
ttaad4500.
With this session you cannot modify/delete/insert, just look.
Try to get get acustomed to only using this one and restrain the use of ttaad4100 to the rare occasions when you have to use it.

regards

Norbert

But in case you will need more information (like table field input help) you will still need to go to GTM itself. When viewing is smart enough, you are absolutely right.

And also when users make mistakes which are difficult to correct via baan sessions it is no way to make the situation stable but to do corrections manually (but always keeping in mind that trespassing baan sessions logic may do harm).

A view of GTM and its usage from a different angle

We only allow Baan support to use GTM on our Live installation
and issue a seperate password for each case we raise which requires GTM. We also keep a log of all these.

Our reasons are

1 If users are able to screw up the data then the software should be robust enough to prevent this and therefore it is an issue for Baan ( it is accepted that PC failures can detract from our rationale but we may be fortunate but have few of these)

2 We will not allow any "in house" user access to GTM based on past experiences we had which caused the company much grief.
This also means that the responsibility for GTM is only with Baan

Also worth noting that there is a log of GTM transactions. If something in the tables appears to be messed up, it doesn't hurt to run Print General Table Maintenance Log (ttaad4400m000) to see if anything was altered by GTM.

Scott

Sorry , yes I missed that out

We actually print these to excel and merge them with the Baan case on a monthly basis

As I said we did have a large problem

Are you saying that you are logging a case each month just to post the ttaad4100 log to Baan? Does that prove anything? Since it is a printout of an editable logfile...

Or do you only post the ttaad4100 log to demonstrate that Baan is the only party that could have messed up the data and thus cause the problem you are registering in that particular case?

For each case that requires GTM we print the appropriate log entries to excel and attach relevant case number for reference

Currently running at 6 a month which has reduced from 12+ a month early in year due to implementation of increased number of solutions which have addressed the finance area

If GTM is needed, I think it indeed should be done by persons that know the datamodel and make *all* appropriate changes in *all* tables. Even not all support analysts do have that knowledge alas... :( Not even myself.

That brings me to the next point: Having a log of ttaad4100 is only part of the story. The log does tell you which kind of action is done on which table, but it does not give you the old and new values...

Do you also track the changes themselves (for example: create a dump before and after, then save the diff output)?

In response to your first point that is the reason we only allow Baan support to make changes via GTM

As far as the "before" state is concerned the details are logged on the case itself but as for the post update state this is a matter for the relevant internal business analyst to record and be satisfied .

BTW, how to get the log of ttaad4100?

Something puzzling me:
1.When I log in with user of "Baan" (the default user), and open ttaad4100, set information of "tt, aad,200(User Data),000', the click "y", system directly goes in
2.Log in with another super user except of "Baan", and open ttaad4100, set information of "tt, aad,200(User Data),000', the click "y", system pops up input box for Password!

So what's the mechanism of this GTM? And which password is the wanted passward, the one set in "ttadv0144m000" or one set in somewhere else?

To get the log of ttaad4100 -

open the session, ttstperrlog and then find the option - log.ttaad4100 then print it to a display browser to see the GTM log.

The one set in ttadv0144m000

Ayoobi

Use the session ttaad4400m000 (Print GTM log ) in Tools==> Database management ==> Reports.

And both sessions do use the log.aad4100 in $BSE/log

Administration tasks within your Baan system are done by a special administrator account named baan. This user should not be used for normal tasks, but for administration tasks only.

User baan has special privileges within the system (comparable with Administator on NT), among which the use of ttaad4100.

For other users there is a special autorisation required in the form of knowing the password (see session ttadv0144m000).

As layed out in this trhead: using ttaad4100 may violate the datamodel restrictions and is risky to use. Do not log in as baan for normal operations (do not allow yourself to get accustomed to mending datacurruption with this session: leave that part to professionals). Change the password on ttaad4100 (login as baan and then set a new password) and keep it save.

Hi OmeLuuk,

Your comments are very clear and making sense

Run session ttaad4400m000

Edit

Apologies this response was obviously meant for another thread
which I will try to find !

Run the session ttaad4400m000

Hey all,

I see that this very old thread was reactivated today by Siripuram for some odd non-understood reason. However, I looked through it, and saw OmeLuuk's comment about the ttaad4100 logfile which only shows you the tables changed, the date and the user, but do not show the old and new values. Ome Luuk opts for running a dump before ttaad4100 is started, and one on exit or so, and print the diff to a log (or maybe integrate it into the same Baan-log...?). Has OmeLuuk (are you back with us???) or anyone else ever done this? Anyone has better, more detailed logging of GTM??

Yes, have done that (before/after dumps) on a case by case basis. But more often I've used a "mini-dump" approach.

Say, for example, something is messed up in a gld batch. I will dump or print the before change and after change version of any records that are to be altered. Not as fail-safe as full table dump but often more workable.

All the other earlier advice in this thread is still valid and important.
Unless you really know what you're doing, and are willing/able to take responsibility for it, leave GTM to Baan or your support provider.
Try the solution in your test company before even thinking about touching the live company.
Document what you did. If the problem recurrs, there is a roadmap for the next fix. If the "fix" impacts something that seems unrelated, you or someone else can more easily trace why.
GTM is an emergency fix. Seek permanent solution through Baan to prevent future recurrences.

Scott

Scott, I agree fully with all the precautions to be taken related to usage of GTM. I however use GTM often at my company (I'm the Baan administrator), and would like to automate this additional logging; i.e. automatically when ttaad4100 is started, take dump/log, and on exit a new one, compare, and log the difference. How is this to be achieved?

Wish I could help you on that one. I'm a just [dis]functional guy -- not a techie -- and I have to go with common sense solutions. But I 've had to use GTM more frequently than my previous reply suggests. If someone out there can suggest a more fail-safe solution, we'll all be grateful!

Scott

I haven't yet had time to look in to it, but shouldn't this be easy via AFS? If I'm not mistaking I saw a thread recently (maybe even last week?) discussing a problem applying AFS for session like GTM ttiex1280m000 and others..?