The following archive solutions were developed with the objective to fit into
the existing Baan
archiving concept, and to avoid customizations
of standard
Baan archiving sessions. Archive
sessions are
frequently updated with new patches by Baan and
customizations should be
avoided.
Sessions are offered at fixed prices. Pricing Info
Preparation and Planning
o
Archive Planner
This is a tool for data assessment, planning of archive procedures and checking archived
data.
Please click here for more information.
Purchase
o
Archive Purchase Order Data (Baan 5)
In Baan 5 it is only possible to archive purchase order data related
to PCS-projects.
This session will archive the purchase order data for standard
purchase orders (includes related
data - like receipts).
o Archive Purchase Requisitions (Baan 5)
In Baan standard it is currently not possible to archive purchase requisitions. Purchase requisitions
can only be deleted. This session archives the purchase requisitions.
o Archive Purchase Requisition History (Baan 5)
In Baan standard it is currently not possible to archive purchase requisition history. Purchase
requisition history can only be deleted. This session archives the purchase requisition history.
Sales
o
Archive Sales Order Data (Baan 5)
In other Baan 5 it is only possible to archive
sales order data related to PCS-projects.
This session
will archive the sales
order data for standard sales orders (includes related data -
like deliveries).
Service
o Archive Service Orders and Service Order History (Baan 5)
In Baan standard it is not possible to archive service orders and the service order history.
Only functionality for deleting this data is available. This session
will archive service orders and
service order history (incl. related costing data).
Other helpful sessions
o Utility session to generate batch jobs (Baan 4, Baan 5)
This session generates Baan batch jobs by reading job variable data for Baan standard sessions
from a
file.
Usually archive companies are defined by year
(please see FAQ). In Baan standard, it's not always
possible to archive and delete data by
date.
For example, PCS budget numbers can only be archived by budget number range. This session
will read the budget numbers from a file and create a batch job with the standard Baan session.
This eliminates the need to enter the numbers manually and helps solving many problems without
customizations.
The session is also useful for other
purposes than archiving. It works with most of the standard
Baan sessions in Baan 4 and Baan 5.
o Utility session to check for duplicate records in the archive and production company (Baan 4)
This session produces a report of records, which
exists in both companies – the archive company
and the production company.
This
is useful if archive companies are not set up by year and numbers have been
reused in the
production company. If for example a sales order with a reused number is
archived into the same
archive company as the previous sales order with the same number, then the new
record will
overwrite the old record.
This session can be used to make sure that data that will be archived doesn't
overwrite previously
archived data.
o Utility sessions to check for obsolete items (Baan 4)
Many companies want to clean up obsolete
master data after archiving is done. After
dynamic data
(orders, order history) has been archived and removed from the
original company, it is possible to
delete old items, customers, suppliers, etc.
This session produces a report and/or a sequential file
with the items that are not used any longer and could be deleted. The sequential file can be
reviewed/corrected and than be fed to the batch job generator utility
described above.
The utility session
will build a batch job for the session “Delete items” (tiitm0203m000).
Similar sessions, to identify master data ready for
deletion, can be developed easily.
Back to overview
Copyright © 2002 Max S.C. LLC