Docstoc

Toolkit Instructions

Document Sample
Toolkit Instructions Powered By Docstoc
					                                    Baan A&D 22b Data Correction
                                         Toolkit Instructions
      DRAFT                     DRAFT    DRAFT       DRAFT     DRAFT                                                                    DRAFT
This document includes general instructions associated with executing the Data Correction Toolkit.

Table of Content
Revision History ............................................................................................................................................. 1
Required Prerequisite Activities ..................................................................................................................... 2
  Patch Configuration .................................................................................................................................... 2
  Unique Toolkit User ID .............................................................................................................................. 2
  Output File Naming Convention ................................................................................................................ 2
  General Ledger Account Mapping Changes ............................................................................................... 2
  Application Access Restriction .................................................................................................................. 2
  Permanent Transfer Processing .................................................................................................................. 2
  TCL Processing .......................................................................................................................................... 2
2.2b Data Recovery Programs and Sequences................................................................................................ 2
Toolkit Program Dependency Flow Diagram ................................................................................................. 4
MAUC Sequence ............................................................................................................................................ 5
  tucor9000 - Temporary Transfers Negative Quantities .............................................................................. 5
  tucor9008 - Sync INV and PGC Inventories .............................................................................................. 5
  tucor9007 – Purchase Order Validation ..................................................................................................... 5
  tucor9004 - Purchase Item Re-costing (restate current MAUC)................................................................. 6
  tucor9001 - Production Order Validation ................................................................................................... 6
  tucor9011 – Make MAUC based on Actual Costs ..................................................................................... 7
  tucor9010 - Make Item Re-costing ............................................................................................................. 7
Logistics Sequence ......................................................................................................................................... 7
  tucor9003 - Production Order Re-costing ................................................................................................... 8
  tucor9005 - Temporary Transfer Re-costing .............................................................................................. 8
  tucor9006 - Inventory Adjustment.............................................................................................................. 8
  tucor9009 - Permanent Transfer Re-costing ............................................................................................... 8
  RPL Corrections – tucor9013, tucor9014, tucor9012, tucor9015 ............................................................... 8
Wrap-up Sequence.........................................................................................................................................10
  tucor9002 - MDD & CLIN Correction .....................................................................................................10
  tucor9008 – Sync INV and PGC Inventories (2nd run) ..............................................................................11
  tdinv0250m000 – Rebuild Planned Inventory Transactions ......................................................................11
  tipgc0250m00b – Rebuild Planned Inventory Transactions ......................................................................11
  tipgc0252m00b – Update Pegging and Group Item Data ..........................................................................11
  tipgc0255m00b – Update Group Items......................................................................................................11
Toolkit Implementation Instructions .............................................................................................................11
Program Execution Instructions (how to use ASCII) ....................................................................................13


Revision History
Version         Release DateChanges
1.1                         
                July 13, 2001  Modified run order to place tucor9001 prior to calculation of MAUC
                               values for make items (tucor9011 and tucor9010). This was done to
                               ensure that delivered quantities on production orders was correct prior to
                               using this information to calculate actual operation costs in tucor9011.
1.3         Aug. 24, 2001  Reorganized most of document.
                              Added Required Prerequisite Activities section and new topics of Patch
                               Configuration, TCL Processing, and Application Access Restriction.
                              Introduced run-order for MAUC and LOGISTIC and WRAP-UP
                               sequences
                              Added instructions for use of standard Baan utility program that may
                               assist in synchronizing inventory.
                              Added instructions for running INV and PGC rebuilds after completion
Toolkit Instructions                                                                           Page 1 of 14
Version 1.4       Aug 25, 2001
      DRAFT                     DRAFT                     DRAFT                     DRAFT                     DRAFT                     DRAFT
                         Baan A&D 22b Data Correction
                              Toolkit Instructions
      DRAFT          DRAFT    DRAFT       DRAFT     DRAFT                                   DRAFT
                                  of Toolkit.
                                 Added toolkit installation instructions.
1.4        Aug 25, 2001          Baseline Release

Required Prerequisite Activities
Patch Configuration
Sync Patch 12 must be installed at the customer site. All correction programs delivered in SP12 and called
out in the SP12 installation instructions must be executed and all data dictionary updates performed.
Unique Toolkit User ID
To simplify identification of the transactions created by the Toolkit programs in update mode, a unique user
ID must be created and used specifically for running the programs.
Output File Naming Convention
To further assist in providing audit trail documentation throughout your system, it is strongly recommended
that users retain all output report from update runs of correction programs in the toolkit. It is strongly
recommended that all output reports from update runs be printed to files. It is further recommended that
users develop a naming convention for these files to allow easy retrieval of the data.
General Ledger Account Mapping Changes
Many of these Toolkit programs create project and integration transactions when running in update mode.
Customers running the Toolkit programs in update mode should consider temporarily changing the account
mappings on these transactions to point to different ledger accounts established specifically for this data
clean up effort. Such ledger account changes must be made before the programs are run in update mode.
The functional specification documentation for each Toolkit program describes the transactions that may be
created.
Application Access Restriction
All Baan application users must be out of the system during Toolkit program execution. Login to the Baan
test/production company in which the recovery is being executed must be disabled. Only the Baan user ID
established exclusively for running the Toolkit programs can be in the Baan test/production company while
the recovery is being executed.
Permanent Transfer Processing
All pending permanent transactions residing in tipgc020 must be processed using Process Permanent
Transfers (tipgc0221m00b) prior to running the Toolkit programs.
TCL Processing
All transactions residing in the TCL (tpppc210, tpppc211, tpppc231, tpppc251, tpppc271, and tpppc291)
must be processed to the PCL leaving the TCL empty.

2.2b Data Recovery Programs and Sequences
The correction programs included in the 22b Data Recovery Toolkit include:
1. Tucor9000.3gl          Temporary Transfers Negative Quantities & Borrow/Loans
2. Tucor9001.3gl          Production Order Validation
3. Tucor9002.3gl          MDD & CLIN Correction
4. Tucor9003.3gl          Production Order Re-costing
5. Tucor9004.3gl          Purchase Item Re-costing (restate current MAUC)
6. Tucor9005.3gl          Temporary Transfers Re-costing
7. Tucor9006.3gl          Inventory Adjustments
8. Tucor9007.3gl          Purchase Order Validation
9. Tucor9008.3gl          Sync INV and PGC Inventories
10. Tucor9009.3gl         Permanent Transfers
11. Tucor9010.3gl         Make Item Re-costing (restate current MAUC)
12. Tucor9011.3gl         Make MAUC based on Actual Costs
Toolkit Instructions                                                                           Page 2 of 14
Version 1.4       Aug 25, 2001
      DRAFT          DRAFT             DRAFT              DRAFT              DRAFT          DRAFT
                          Baan A&D 22b Data Correction
                               Toolkit Instructions
      DRAFT           DRAFT    DRAFT       DRAFT     DRAFT                                   DRAFT
13.   Tucor9012.3gl        RPL Financial Data
14.   Tucor9013.3gl        RPL Transfer Cross Reference
15.   Tucor9014.3gl        RPL Distribution
16.   Tucor9015.3gl        RPL Updates

Programs tucor9000.3gl “ Temporary Transfers Negative Quantities” and tucor9008 “Sync INV and PGC
Inventories” must be run at every site. These are the foundation programs that establish data integrity in
the reference A&D tables for the subsequent programs. Execution of the other programs within the Toolkit
is optional. Decision on applicability or requirement of each of the optional programs will be site-specific
and will be made jointly by the Baan and customer data recovery teams. Once it is decided which
programs will be executed, there will be run-order dependencies that must be observed. To facilitate
understanding of these run-order dependencies, the Toolkit programs can be divided into three sequences.
These sequences are known as MAUC, LOGISTICS, and WRAP-UP.

MAUC SEQUENCE
The MAUC sequence includes the first two required programs (tucor9000 and tucor9008). In addition, this
sequence includes the programs used to recalculate MAUC values (tucor9004, tucor9010, and tucor9011).
This sequence also includes the programs that validate/correct delivered quantities on production orders
(tucor9001) and purchase orders (tucor9007) which are prerequisite steps to recalculating MAUC values.

The Toolkit has provided programs to recalculate “buy” MAUCs and “make” MAUCs. Each site has the
option to use these programs or come up with their own routines to recalculate MAUC values.

Furthermore, sites could declare that the current MAUCs are accurate, in which case no recalculation
would be required.

LOGISTICS SEQUENCE
The logistics sequence is devoted primarily to validating costs (and quantities in some cases) associated
with different types of orders. In order for any benefits to be achieved in this sequence, current MAUC
values must be accurate. All of the programs in the Logistics sequence are optional. The programs within
the Logistics Sequence are independent of each other and can be run in any order within the Logistics
sequence. The only exception to this is the RPL programs (tucor9012, 9013, 9014, and 9015). The RPL
programs have a prescribed sequence within themselves but can run before or after any of the other
programs in the Logistics Sequence.

WRAP-UP SEQUENCE
Included in this sequence is the validation/correction of MDDs (tucor9002). This is an optional program.
If the site chooses to run this program, it should not run until all desired programs from the Logistics
sequence have successfully completed in update mode.

Also included in this sequence is a final run of the inventory-synchronizing program (tucor9008). If any
Toolkit program other than the two required programs (tucor9000 and tucor9008) have been run in update
mode, the inventory-synchronizing program (tucor9008) must be run again as one the final step of the
recovery effort to ensure that inventories are still in sync.

Lastly, this sequence includes execution of some of the standard Baan and A&D specific utility programs.
If any of the optional Toolkit programs were run in update mode (programs other than tucor9000 and
tucor9008), these utility programs must be run. These programs will ensure that the on-order and
allocated/required quantities recorded throughout the system are correct. These programs will also ensure
that planned receipt and material requirement quantities are correct.




Toolkit Instructions                                                                            Page 3 of 14
Version 1.4       Aug 25, 2001
      DRAFT           DRAFT            DRAFT             DRAFT             DRAFT             DRAFT
                        Baan A&D 22b Data Correction
                             Toolkit Instructions
    DRAFT           DRAFT    DRAFT       DRAFT     DRAFT        DRAFT

Toolkit Program Dependency Flow Diagram
                                       tucor9000


 MAUC Sequence                         tucor9008




                    tucor9007                      tucor9001

                                                                      Optional

                    tucor9004                                   tucor9011




                                      tucor9010



Logistics Sequence

      tucor9003           tucor9005   tucor9009     tucor9006   tucor9013



                                                                tucor9014



                                                                tucor9012



                                                                tucor9015




Wrap-up Sequence                      tucor9002

Toolkit Instructions                                              Page 4 of 14
Version 1.4       Aug 25, 2001        tucor9008
    DRAFT           DRAFT        DRAFT      DRAFT      DRAFT    DRAFT
                          Baan A&D 22b Data Correction
                               Toolkit Instructions
    DRAFT             DRAFT    DRAFT       DRAFT     DRAFT                                    DRAFT
MAUC Sequence
tucor9000 - Temporary Transfers Negative Quantities & Borrow/Loans
tucor9008 - Sync INV and PGC Inventories
tucor9007 - Purchase Order Validation
tucor9004 - Purchase Item Re-costing (restate current „buy‟ MAUC)
tucor9001 - Production Order Validation
tucor9011 - Make MAUC based on Actual Costs
tucor9010 - Make Item Re-costing (restate current „make‟ MAUC)
Programs tucor9000 and tucor9008 MUST be run at all sites. These two programs will ensure that on-hand
and owned balances are consistent throughout the system – a state required to ensure proper system
performance. Beyond these first two programs, the team responsible for each site will determine the
applicability or requirement of each of the remaining programs in the MAUC sequence.

The first two programs, tucor9000 and tucor9008 must be run in that order, one after the other, for the same
range of items. These two programs can be run against small item number ranges as long as both run
against the same item range and both complete successfully before allowing production operations to
resume. DO NOT attempt to run any other program in the Toolkit until these two programs have been run
and successfully completed for ALL items.

If MAUC values (ticpr952) are incorrect, the Purchase Item Re-costing (tucor9004) and Make Item Re-
costing (tucor9010) routines are used to recalculate MAUC values (ticpr952). Optionally, customers may
choose to write their own algorithm to recalculate MAUC values or they may manually perform the task by
using Maintain MAUC Value (ticpr9152m00b) or MAUC Correction (ticpr9252m00b). In any event,
MAUC value corrections for all make and buy items must be completed prior to moving on to any of the
correction programs in the Logistics sequence or Wrap-up sequence.
tucor9000 - Temporary Transfers Negative Quantities
This program will change any pending temporary transfers (tipgc020) stated in negative quantities to
positive quantities. Once all pending temporary transfers for an item have been stated in positive values,
this program will ensure that all borrow and loan quantities in pegging data (tipgc010), project inventory
(tipgc040), and accountability records (ticpr951) match pending temporary transfers (tipgc020). All
discrepancies in these tables will be modified to reflect actual pending temporary transfers found in
tipgc020. Accurate recording of loan quantities is a prerequisite to synchronizing inventory values in
tucor9008.
tucor9008 - Sync INV and PGC Inventories
The inventory sync program, tucor9008, ensures that on-hand quantities in the standard inventory tables
match those values in the project inventory/ownership tables. If any discrepancies are found among the
standard inventory tables (tiitm001, tdinv001, and tdilc101), the error message
“TIITM001/TDINV001/TDILC101 not in sync, no correction” will notify the user of this problem. This
problem MUST be corrected before tucor9008 can attempt to synchronize the project inventory/ownership
tables with the standard inventory tables. In this situation, the standard Baan error recovery utility program
Check Inventory Data (tdinv0252m000) may be able to assist in the correction. Refer to the Baan CS&S
document titled “Commonly Run TD Error Recovery Sessions” for detailed information on this program.

If any discrepancies are found between these standard inventory tables and the project inventory/ownership
tables (tipgc001, tipgc010, and tipgc040), program tucor9008 will make all tables match the tdilc101 table.
Having inventory levels synchronized between all inventory tables is a prerequisite to running any other
program in the Toolkit with the exception of tucor9000.
tucor9007 – Purchase Order Validation
This program can not be run until inventory balances are in sync. As a result, this program can not run in
non-update or update mode until tucor9008 completes successfully in update mode for all item ranges.


Toolkit Instructions                                                                             Page 5 of 14
Version 1.4       Aug 25, 2001
    DRAFT             DRAFT             DRAFT             DRAFT             DRAFT             DRAFT
                          Baan A&D 22b Data Correction
                               Toolkit Instructions
    DRAFT             DRAFT    DRAFT       DRAFT     DRAFT                                     DRAFT
Although this program is optional, all sites should run this program in non-update mode against all items
and purchase orders to determine if any problems exist. If none are found, the update portion could be
skipped. If problems are found, each site will need to determine if this program should be run in update
mode.

For pegged purchase orders, this program will ensure that all quantities received on purchase orders are
properly stated in the PCL with regard to quantities and amounts. Accurate recording of purchase receipt
quantities and amounts in the PCL is a prerequisite for recalculating „buy‟ MAUCs (tucor9004). If
tucor9004 is going to be used to recalculate „buy‟ MAUC values and purchase receipt problems are
identified by tucor9007, tucor9007 must be run in update mode for all items before attempting to run
tucor9004.

For pegged purchase orders, this program will ensure that the distribution of each purchase receipt is
accurate. Accurate recording of purchase receipt distribution quantities is a prerequisite for validating
MDD completion quantities (tucor9002). If tucor9002 is going to be used to validate MDD quantities and
purchase receipt problems are identified by tucor9007, tucor9007 must be run in update mode for all items
before attempting to run tucor9002.

It is possible to run this program for ranges of purchase orders thus allowing this program to be run over a
series of days if desired.
tucor9004 - Purchase Item Re-costing (restate current MAUC)
This correction program will update IMAUCs of purchased items and PMAUCs with MBCS = BUY.
Having accurate MAUCs of purchased items is an essential prerequisite to validating the MAUCs of
manufactured items and validating costs associated with all type of orders (SFC, RPL, transfers, inventory
adjustments).

This program is considered optional in the sense that each site has the option to choose how they want to
recalculate MAUC values for purchased items. A site can choose to use the logic provided by this
correction program or develop their own routine (including the use of existing sessions) to update MAUC
values that may be incorrect. However this is accomplished, MAUC values of ALL purchased items must
be accurate before attempting to validate MAUCs of manufactured items or attempting to validate costs of
orders.

It is possible to run this program for ranges of items thus allowing this program to be run over a series of
days if desired.
tucor9001 - Production Order Validation
This program can not be run until inventory balances are in sync. As a result, this program can not run in
non-update or update mode until tucor9008 completes successfully in update mode for all item ranges.

Although this program is optional, all sites should run this program in non-update mode against all items
and production orders to determine if any problems exist. If none are found, the update portion could be
skipped. If problems are found, each site will need to determine if this program should be run in update
mode.

This program will ensure consistent recording of production order completion quantities, component issue
quantities, and labor and machine hours distribution on production orders. Accurate recording of these
quantities is a prerequisite for validating costs associated with production orders (tucor9003). If tucor9003
is going to be used to validate production order costs and production order quantity problems are identified
by tucor9001, tucor9001 must be run in update mode for all items before attempting to run tucor9003.

For pegged production orders, this program will ensure that the distribution of each production receipt and
production issue is accurate. Accurate recording of production receipt and issue distribution quantities is a

Toolkit Instructions                                                                              Page 6 of 14
Version 1.4       Aug 25, 2001
    DRAFT             DRAFT             DRAFT             DRAFT              DRAFT             DRAFT
                          Baan A&D 22b Data Correction
                               Toolkit Instructions
    DRAFT             DRAFT    DRAFT       DRAFT     DRAFT                                     DRAFT
prerequisite for validating MDD completion quantities (tucor9002). If tucor9002 is going to be used to
validate MDD quantities and production receipt or issue problems are identified by tucor9001, tucor9001
must be run in update mode for all items before attempting to run tucor9002.

It is possible to run this program for ranges of purchase orders thus allowing this program to be run over a
series of days if desired.
tucor9011 – Make MAUC based on Actual Costs
If problems were found with production order completion quantities in tucor9001, this program can not run
until tucor9001 has been run in update mode and all erroneous production order quantities have been
corrected.

This program will attempt to calculate operation values (labor, machine, and subcontracting) based on
actual production orders to be used later when recalculating MAUC values for manufactured items.

The Toolkit provides two different methods for calculating operation values that should be included in the
MAUC of a manufactured item. One method is based on actual closed or completed production orders
while the other method is based on routines. If a site chooses to use the programs in the Toolkit to correct
MAUC values of manufactured items, the site will need to run tucor9010. Furthermore, if a site chooses to
have operation values in MAUCs based on actual production orders, the site will need to run tucor9011
prior to running tucor9010.
tucor9010 - Make Item Re-costing
Prior to running this program, MAUCs of purchased items must be correctly stated in the MAUC table
(ticpr951). This can be accomplished by tucor9004 or a site can create it‟s own method for recalculating
MAUC values. Additionally, if a site is choosing to use the programs provided in the Toolkit to update
MAUCs of manufactured items and the site desires to have operation costs in manufactured items based on
actual production orders rather than routines, program tucor9011 must be run in update mode before
running tucor9010.

This correction program will update IMAUCs of manufactured items and PMAUCs with MBCS = MAKE.
Having accurate MAUCs of manufactured items is an essential prerequisite to validating costs associated
with all type of orders (SFC, RPL, transfers, inventory adjustments).

This program is considered optional in the sense that each site has the option to choose how they want to
recalculate MAUC values for manufactured items. A site can choose to use the logic provided by the
Toolkit (tucor9011 and/or tucor9010) or develop their own routine (including the use of existing sessions)
to update MAUC values that may be incorrect. However this is accomplished, MAUC values of ALL
manufactured items must be accurate before attempting to validate costs of orders.

It is possible to run this program for ranges of items thus allowing this program to be run over a series of
days if desired.

Logistics Sequence
tucor9003 - Production Order Re-costing
tucor9005 - Temporary Transfers Re-costing
tucor9006 – Inventory Adjustments
tucor9009 - Permanent Transfers
RPL - tucor9013, tucor9014, tucor9012, tucor9015

Prior to running any of the programs in the Logistics sequence, MAUC values of all items must be accurate
(ticpr951) and inventory balances must be in sync.


Toolkit Instructions                                                                              Page 7 of 14
Version 1.4       Aug 25, 2001
    DRAFT             DRAFT             DRAFT             DRAFT              DRAFT             DRAFT
                          Baan A&D 22b Data Correction
                               Toolkit Instructions
    DRAFT             DRAFT    DRAFT       DRAFT     DRAFT                                     DRAFT
The programs in the Logistics sequence are independent of each other and can be run in any order with the
exception of the RPL programs. The RPL programs must be run in order of tucor9013 followed by
tucor9014 followed by tucor9012 and finished off with tucor9015. However, the RPL programs can be run
before or after any of the other programs in the Logistics sequence.
tucor9003 - Production Order Re-costing
Prior to running this program, MAUC values of all items must be accurate and inventory balances must be
in sync. Furthermore, all production order receipt quantities, production order issue quantities, and hours
changed to production orders must be correct. These production order quantities/hours can be
validated/corrected by tucor9001.

Although this program is optional, all sites should run this program in non-update mode against all items
and orders to determine if any problems exist. If none are found, the update portion could be skipped. If
problems are found, each site will need to determine if this program should be run in update mode.

It is possible to run this program for ranges of production orders thus allowing this program to be run over
a series of days if desired.
tucor9005 - Temporary Transfer Re-costing
Prior to running this program, MAUC values of all items must be accurate and inventory balances must be
in sync. Furthermore, all temporary transfer quantities must be correct. These temporary transfer
quantities can be validated/corrected by tucor9000.

Although this program is optional, all sites should run this program in non-update mode against all items
and transfers to determine if any problems exist. If none are found, the update portion could be skipped. If
problems are found, each site will need to determine if this program should be run in update mode.

It is possible to run this program for ranges of items thus allowing this program to be run over a series of
days if desired.
tucor9006 - Inventory Adjustment
Prior to running this program, MAUC values of all items must be accurate and inventory balances must be
in sync.

Although this program is optional, all sites should run this program in non-update mode against all items
and warehouse orders to determine if any problems exist. If none are found, the update portion could be
skipped. If problems are found, each site will need to determine if this program should be run in update
mode.

It is possible to run this program for ranges of warehouse orders and items thus allowing this program to be
run over a series of days if desired.
tucor9009 - Permanent Transfer Re-costing
Prior to running this program, MAUC values of all items must be accurate and inventory balances must be
in sync.

Although this program is optional, all sites should run this program in non-update mode against all items
and transfers to determine if any problems exist. If none are found, the update portion could be skipped. If
problems are found, each site will need to determine if this program should be run in update mode.

It is possible to run this program for ranges of items, transfer numbers, and/or “from” projects thus
allowing this program to be run over a series of days if desired.
RPL Corrections – tucor9013, tucor9014, tucor9012, tucor9015
Prior to running these programs, MAUC values of all items must be accurate and inventory balances must
be in sync.
Toolkit Instructions                                                                              Page 8 of 14
Version 1.4       Aug 25, 2001
    DRAFT             DRAFT             DRAFT             DRAFT             DRAFT              DRAFT
                          Baan A&D 22b Data Correction
                               Toolkit Instructions
    DRAFT             DRAFT    DRAFT       DRAFT     DRAFT                                   DRAFT

Although these programs are optional, all sites should run this program in non-update mode against all
items and RPL orders to determine if any problems exist. If none are found, the update portion could be
skipped. If problems are found, each site will need to determine if these programs should be run in update
mode.

For RPL orders moving items into or out of a pegged warehouse, this program will ensure that the
distribution of each movement is accurate. Accurate recording of RPL distribution quantities is a
prerequisite for validating MDD completion quantities (tucor9002). If tucor9002 is going to be used to
validate MDD quantities and RPL distribution quantity problems are identified by the RPL correction
programs, the RPL correction programs must be run in update mode for all items before attempting to run
tucor9002.

The RPL correction programs must start with tucor9013 – RPL Transfer Cross Reference, followed by
tucor9014 – RPL Distribution, followed by tucor9012 – RPL Financial Data, and ending with tucor9015 –
RPL Updates.

tucor9013 - RPL Transfer Cross Reference
Prior to running this program, MAUC values of all items must be accurate and inventory balances must be
in sync.

This program creates a temporary table establishing a cross-reference between RPL order deliveries and the
transfers that were executed to accomplish the delivery. Establishing an accurate link between RPL
deliveries and transfers is a prerequisite for validating RPL distribution quantities (tucor9014). If
tucor9014 is going to be used to validate RPL distribution quantities, tucor9013 must be run first and the
temporary table validated prior to running tucor9014.

It is NOT possible to run this program for ranges of RPL orders or items. Therefore, enough time must be
allowed for this program to run in its entirety before normal production operations continue.

tucor9014 - RPL Distribution
Prior to running this program, a temporary table must be loaded with the cross-reference between RPL
order deliveries and the transfers that were executed to accomplish the delivery. This can be accomplished
by running program tucor9013.

This program creates a temporary table of the desired distribution quantities for each RPL delivery that is
moving inventory into or out of a pegged warehouse. Establishing accurate RPL distribution quantities is a
prerequisite for validating RPL financial data (tucor9012). If tucor9012 is going to be used to validate RPL
financial data, tucor9014 must be run first and the temporary table validated prior to running tucor9012.

For RPL deliveries moving items into or out of a pegged warehouse, this program will ensure that the
quantity recorded on the transfers that were executed to accomplish the delivery are accurate. Accurate
recording of quantities on transfers associated with RPL deliveries is a prerequisite for validating MDD
completion quantities (tucor9002). If tucor9002 is going to be used to validate MDD quantities, tucor9014
should be run first to identify any problems with quantities on transfers linked to RPL orders. If any
problems with quantities on transfers linked to RPL orders, tucor9015 (RPL Updates) must be run in update
mode for all items before attempting to run tucor9002.

It is possible to run tucor9014 for ranges of RPL orders thus allowing this program to be run over a series
of days if desired.

tucor9012 - RPL Financial Data routine


Toolkit Instructions                                                                            Page 9 of 14
Version 1.4       Aug 25, 2001
    DRAFT             DRAFT             DRAFT            DRAFT             DRAFT             DRAFT
                          Baan A&D 22b Data Correction
                               Toolkit Instructions
    DRAFT             DRAFT    DRAFT       DRAFT     DRAFT                                   DRAFT
Prior to running this program, a temporary table must be loaded with desired distribution quantities for each
RPL delivery that is moving inventory into or out of a pegged warehouse. This can be accomplished by
running program tucor9014.

This program creates a temporary table of estimated and actual financial transactions created for each RPL
delivery.

It is possible to run program tucor9012 for ranges of RPL orders or item numbers thus allowing this
program to be run over a series of days if desired.

tucor9015 - RPL Updates
Prior to running this program, numerous temporary tables must be loaded. A table must be loaded with the
cross-reference between RPL order deliveries and the transfers that were executed to accomplish the
delivery. This can be accomplished by running program tucor9013. A table must be loaded with desired
distribution quantities for each RPL delivery that is moving inventory into or out of a pegged warehouse.
This can be accomplished by running program tucor9014. A table must be loaded with estimated and
actual financial transactions created for each RPL delivery. This can be accomplished by running program
tucor9012. Furthermore, all of these temporary tables must be verified prior to running this program.

For RPL deliveries moving items into or out of a pegged warehouse, this program will ensure that the
quantity recorded on the transfers that were executed to accomplish the delivery are accurate. Accurate
recording of quantities on transfers associated with RPL deliveries is a prerequisite for validating MDD
completion quantities (tucor9002). If tucor9002 is going to be used to validate MDD quantities, tucor9014
should be run first to identify any problems with quantities on transfers linked to RPL orders. If any
problems with quantities on transfers linked to RPL orders, tucor9015 (RPL Updates) must be run in update
mode for all items before attempting to run tucor9002.

Wrap-up Sequence
tucor9002 - MDD & CLIN Correction
tucor9008 - Sync INV and PGC Inventories
tdinv0250m000 – Rebuild Planned Inventory Transactions
tipgc0250m00b – Rebuild Planned Inventory Transactions
tipgc0252m00b – Update Pegging and Group Item Data
tipgc0255m00b – Update Group Items

The programs in the Wrap-up sequence may or may not be run at a site, depending on what programs from
the MAUC and Logistics sequences were run. If programs in the Wrap-up sequence are run, they do have a
prescribed order of execution. That order is the same order as they appear listed above.

tucor9002 - MDD & CLIN Correction
Prior to using tucor9002 to validate/correct completion quantities for MDDs, quantities available from
other types of orders must be correct. Running Toolkit programs tucor9007, tucor9001, tucor9006,
tucor9009, and tucor9015 in update mode prior to running tucor9002 can ensure correctness of quantities
available from other orders.

Although this program is optional, all sites should run this program in non-update mode against all items
and contracts to determine if any problems exist. If none are found, the update portion could be skipped. If
problems are found, each site will need to determine if this program should be run in update mode.

It is possible to run tucor9002 for ranges of contracts and items thus allowing this program to be run over a
series of days if desired.


Toolkit Instructions                                                                           Page 10 of 14
Version 1.4       Aug 25, 2001
    DRAFT             DRAFT             DRAFT             DRAFT             DRAFT            DRAFT
                           Baan A&D 22b Data Correction
                                Toolkit Instructions
    DRAFT              DRAFT    DRAFT       DRAFT     DRAFT                                     DRAFT
tucor9008 – Sync INV and PGC Inventories (2nd run)
If any programs from the Toolkit beyond the first two required programs (tucor9000 and tucor9008) were
run in update mode, tucor9008 must be run again to validate that on-hand balances are still in sync. This
final run insures accurate inventory balances to facilitate return to normal production activities. If any
problems are discovered in this final run of tucor9008 that were previously correct, contact Baan Support
immediately.
tdinv0250m000 – Rebuild Planned Inventory Transactions
This standard Baan error recovery utility program will perform two functions. First, it completely rebuilds
table tdinv150 with planned inventory movement data from purchase orders, production orders, RPL
orders, etc. Secondly, this program will ensure that inventory allocations and on-order quantities are
correct. After executing the Toolkit programs in update mode, it is necessary to run tdinv0250m000 prior
to returning to normal production activities to ensure the accuracy of the data from which the planning
engines will operate. Refer to the Baan CS&S document titled “Commonly Run TD Error Recovery
Sessions” for detailed information on this program.
tipgc0250m00b – Rebuild Planned Inventory Transactions
This A&D error recovery utility program will completely rebuild table tipgc500 with planned inventory
movement data from different types of pegged orders and transfers. After executing the Toolkit programs
in update mode, it is necessary to run tipgc0250m00b prior to returning to normal production activities to
ensure the accuracy of the data from which the GRP planning engine will operate. Refer to the Baan CS&S
document titled “PGC Rebuild Sessions” for detailed information on this program.
tipgc0252m00b – Update Pegging and Group Item Data
This A&D error recovery utility program will update on-order and required quantities in table tipgc010
based on different types of pegged orders and transfers. After executing the Toolkit programs in update
mode, it is necessary to run tipgc0252m00b prior to returning to normal production activities to ensure the
accuracy of the data from which the GRP planning engine will operate. Refer to the Baan CS&S document
titled “PGC Rebuild Sessions” for detailed information on this program.
tipgc0255m00b – Update Group Items
This A&D error recovery utility program will update on-order and required quantities in table tipgc001
based on different types of pegged orders and transfers. After executing the Toolkit programs in update
mode, it is necessary to run tipgc0255m00b prior to returning to normal production activities to ensure the
accuracy of this data. Refer to the Baan CS&S document titled “PGC Rebuild Sessions” for detailed
information on this program.

Toolkit Implementation Instructions
You‟ll receive a toolkit.tar file containing the objects, source, and tables required to run the 2.2b Data
Recovery Toolkit. Those will be available for download from the support ftp site when complete.

Download the toolkit.tar from the ftp site. Use an FTP utility, in binary mode, to place the toolkit.tar in
your Baan server. Store the file in a temporary directory initially; that temp directory need not be in your
$BSE. For this example we show a temp directory called junk.

Run this command:

From /junk, run:
bshell6.1> tar -xvf toolkit.tar

To extract the following files from toolkit.tar:
Objects.tar
Source.tar
Tables.tar

Toolkit Instructions                                                                              Page 11 of 14
Version 1.4       Aug 25, 2001
    DRAFT              DRAFT             DRAFT             DRAFT             DRAFT              DRAFT
                           Baan A&D 22b Data Correction
                                Toolkit Instructions
    DRAFT              DRAFT    DRAFT       DRAFT     DRAFT                                       DRAFT
Extract each of those *.tar files as shown below:

bshell6.1> tar -xvf objects.tar
To extract the objects shown below (note, object sizes will be different at release date):
x objects/ocor9000.3gl, 22144 bytes, 44 tape blocks
x objects/ocor9001.3gl, 69480 bytes, 136 tape blocks
x objects/ocor9002.3gl, 69480 bytes, 136 tape blocks
x objects/ocor9003.3gl, 70031 bytes, 137 tape blocks
x objects/ocor9004.3gl, 20341 bytes, 40 tape blocks
x objects/ocor9005.3gl, 21346 bytes, 42 tape blocks
x objects/ocor9006.3gl, 35103 bytes, 69 tape blocks
x objects/ocor9007.3gl, 55083 bytes, 108 tape blocks
x objects/ocor9008.3gl, 33409 bytes, 66 tape blocks
x objects/ocor9009.3gl, 31449 bytes, 62 tape blocks
x objects/ocor9010.3gl, 38704 bytes, 76 tape blocks
x objects/ocor9011.3gl, 28377 bytes, 56 tape blocks
x objects/ocor9012.3gl, 19957 bytes, 39 tape blocks
x objects/ocor9013.3gl, 22770 bytes, 45 tape blocks
x objects/ocor9014.3gl, 18991 bytes, 38 tape blocks
x objects/ocor9015.3gl, 57525 bytes, 113 tape blocks

Similarly, extract the table definitions from tables.tar:
bshell6.1> tar -xvf tables.tar
x tables/components, 49 bytes, 1 tape blocks
x tables/dumpt01.Z, 3 bytes, 1 tape blocks
x tables/dumpo01.Z, 3 bytes, 1 tape blocks
x tables/dump.l, 958 bytes, 2 tape blocks
x tables/dumpd01.Z, 9836 bytes, 20 tape blocks
x tables/dump.e, 259 bytes, 1 tape blocks

The following table definitions are delivered:
ttucor908                 B40Cc3haz9
ttucor952                 B40Cc3haz9
ttucor961                 B40Cc3haz9
ttucor962                  B40Cc3haz9
ttucor963                 B40Cc3haz9
ttucor964                 B40Cc3haz9
ttucor992                 B40Cc3haz9
ttucor993                 B40Cc3haz9
ttucor994                  B40Cc3haz9
ttucor995                 B40Cc3haz9

Finally, extract the source files (files will be zero byte, but are required for installation):

bshell6.1> tar -xvf source.tar
x source/components, 65 bytes, 1 tape blocks
x source/dumpt01.Z, 3 bytes, 1 tape blocks
x source/dumpr01.Z, 8 bytes, 1 tape blocks
x source/dumps01.Z, 378129 bytes, 739 tape blocks
x source/dumpo01.Z, 324167 bytes, 634 tape blocks
x source/dump.l, 2749 bytes, 6 tape blocks
x source/dumpd01.Z, 13793 bytes, 27 tape blocks
x source/dump.e, 259 bytes, 1 tape blocks

Toolkit Instructions                                                                              Page 12 of 14
Version 1.4       Aug 25, 2001
    DRAFT              DRAFT              DRAFT              DRAFT              DRAFT             DRAFT
                          Baan A&D 22b Data Correction
                               Toolkit Instructions
    DRAFT             DRAFT    DRAFT       DRAFT     DRAFT                                  DRAFT
You‟ll see new subdirectories for objects, tables, and source result from the extracts.

drwxrwx--x 2 kpinckne bsp             512 Aug 8 13:18 objects
drwxrwx--x 2 kpinckne bsp             512 Aug 8 13:21 tables
drwxrwx--x 2 kpinckne bsp             512 Aug 8 13:24 source

Once extracted, the Toolkit components must be installed in the “tu” directories in your system‟s
$BSE/application directory. Use session ttiex1285m000 (Import Data Dictionary) for that installation. See
the example below:




That installation populates the application directories shown below:
/baan22/bse/application/tuB40B_c3_22b2/otucor
/baan22/bse/application/tuB40B_c3_22b2/ptucor

And installs the table definitions in /baan22/dict/ddad22b2/dtucor.

See the section titled “Program Execution Instructions (how to use ASCII)” to learn how to run the Tookit
programs.

Program Execution Instructions (how to use ASCII)
The programs in the toolkit are written in a third generation language (3gl). This means they will look and
feel like ASCII screens rather than the GUI screens to which you are accustomed. The following
instructions will help your teams setup and execute these Toolkit programs.


Toolkit Instructions                                                                          Page 13 of 14
Version 1.4       Aug 25, 2001
    DRAFT             DRAFT             DRAFT             DRAFT             DRAFT           DRAFT
                          Baan A&D 22b Data Correction
                               Toolkit Instructions
    DRAFT             DRAFT    DRAFT       DRAFT     DRAFT                                     DRAFT
The programs will not appear on any menu. Therefore to start any Toolkit program from Baan, go to the
“File” option from the main menu. Under “File”, choose “Run Program”. This will pop up a window
asking for the program/session name. In this field, enter the name of the program you want to run using the
following format “otucor90XX.3gl”. Do not include the quotes and ensure everything is in lower case.
Leave the other fields in this window blank (i.e., Program Argument and Run External Program). Press
OK.

This will bring up a screen with the program title and the selection criteria required to run the program.
The cursor will likely be sitting at the bottom right hand corner of the screen on the Choice prompt. From
the Choice field, enter a “C” for change (without the quotes). This will move the cursor to the first field on
the screen and allow the entry of desired selection criteria.

On this screen, use the “enter” key to move to the next field. The arrow keys can be used to move back and
for between the selection criteria fields.

Hitting the “Esc” key from the beginning of any field will eliminate any changes made to the selection
criteria and move the cursor to the Choice prompt.

If the selection criteria has a predefined set of options (existing order number, order status values, etc), the
list of available options can be viewed by hitting “Cntr” + “z” or by hitting the space bar while sitting at the
beginning of the field. Using the space bar or the Cntr-z depends how the set of options is defined. If one
method doesn‟t work, try the other. If no predefined set of options exists, the Cntr-z will do nothing and
the space bar will put a space at the start of the field.

Once the desired selection criterion is entered, move the cursor to the Choice field. Enter a “y” to start
processing the data. As soon as the process is started, a standard “Select Device” screen will be displayed.
Entered the desired device for the program output on this screen. Select the “continue” button to allow the
program to process after an output device has been specified.




Toolkit Instructions                                                                              Page 14 of 14
Version 1.4       Aug 25, 2001
    DRAFT             DRAFT              DRAFT             DRAFT             DRAFT              DRAFT

				
DOCUMENT INFO