Hello everyone,
I have a question about the archive company set-up in Baan IV.
Is it possible to create the archive companies so that no transactions can be made there once data is archived?
Is there some sort of parameter that can be set to make the maintain sessions read-only or something like that?

Thanks for any suggestions.
Sandy

Sandy,

The only way I am aware of to do this is to set table authorizations to be read only. I don't believe there is anything you can do to prevent super users from full access to the data.

Vince

Sandy,

Just to continue a bit further:

Archiving is the process of removing specific data from the operational
company. For each session, you will learn about the actual data that can be
archived. The Baan sessions let you decide whether to archive the data into
an archive company or just delete the data from the operational company.
Generally, when any of the Baan archiving sessions are executed, the system
runs through two sequential procedures. First, the master data is copied to
the archive company to keep the references to the archived data. Second, the actual data is copied to the archive company and deleted from the
operational company. Besides the general data, you also have the possibility
to archive any attached texts. There is usually a check box that you can select in order to archive texts.
After the archiving sessions have been executed, the archived data will not be available for analysis and reporting in the operational company. The data is
moved to the archive company. Users should only have “Read-only” rights
to prohibit modifying the archived data within the archive company.
Archiving is usually not reversible. For example, the archived data cannot be
brought back into the operational company

For super users it will not be possible and, also is not required in that u may always be required to turn off it at the time of archieving .

If however the intention is to prevent accidental data entry in archieve company , u can play with application para (like delete / reset all first free numbers , make all ledger/dim blocked for manual entry , enter signal code for all item to the effect that it is "ARCHIEVE COMPANY!!!" etc) .

Thanks for all your responses.

If you really really have to turn off the table level access to the Baan Super Users you can do it from the Oracle DB :eek:
Example, to revoke permissions of all company-200's tables:
select 'REVOKE select, update, delete, insert on baan.||TABLE_NAME|| from r_baan' from all_tables where owner = 'BAAN' and TABLE_NAME LIKE '%200';

If you really really have to turn off the table level access to the Baan Super Users you can do it from the Oracle DB :eek:
Example, to revoke permissions of all company-200's tables:


that WOULD be fun.. but that actually wacks everyone's permission to the database. (i.e., baan no workie anymore for anyone) =)

Dave