This section contains the manual table conversions that are required to finish the upgrade process if you are upgrading from previous releases.
Note:
Whenever you submit a Manual Table Conversion from Batch Versions, check on the Properties box to ensure you specify the correct Source and Target environments. You must also override the location to Local as the Previous Release environment is not defined on the Enterprise Server.This chapter describes these tasks:
You must run post installation Universal Batch Engine (UBE) reports to successfully use your previous data. Unless noted otherwise, you should run these conversions from a client workstation in the environment that you are upgrading. When running against SQL Server, Oracle, or DB2\UDB, sign on as the data source owner if any of the post installation jobs are TCs which create temp tables.
Run these post installation UBEs after the automatic table conversion programs have completed successfully.
See Also
JD Edwards EnterpriseOne Programmer's Guide and theJD Edwards EnterpriseOne Database Changes Guide for detailed information on additional information, notes, and verification procedures regarding the following UBEs.
You must use the Fast Path field to navigate to the Post Install Menu (GH9619) where you run the UBEs listed in this table.
Note:
If you do not use the Fast Path field to navigate to the Post Install Menu (GH9619), the menu selections may not display properly.All Conversion Programs marked with * must be run on the Deployment Server.
This section contains a list of all the Table Conversions required when upgrading from XE \ ERP 8.0.
| Upgrading from XE \ ERP 8.0 | ||||
|---|---|---|---|---|
| Conversion Program | Run this Job | Requirements | Purpose | Notes |
| R890030B | Only if you have taken the ESU in XE/ERP8.0 and are using F0031 Bank Transit Master Tag Table. | None | To merge the F0031 Bank Transit Master Tag Table into the F0030 Bank Transit Master. The conversion will copy the data from the bank address number AN8BK in F0031 to the bank address number AN8BK in F0031. | None |
| R8903B11P1 | To convert F03B11 from XE\ERP 8.0. | This is to be run after the A\R ledger has been successfully upgraded in the automatic Upgrade Plan. The basic F03B11 table conversion must have successfully run in your plan prior to running this Post Install job. Suspend all Invoicing and Sales Update activity from the time of the upgrade through the successful completion of this job. | Critical A\R features in invoicing will malfunction if this job is not run. | Over a dozen new fields were introduced to the F03B11 table. The standard table conversion, which is run through the Table Conversion Scheduler application (P98430), initializes all of the new fields to default or blank values. Limitations in the table conversion tool prevent it from calculating values for some of the new fields in the F03B11 table. This post-install conversion supplements R8903B11. |
| R890411P1 | To convert F0411from XE\ERP 8.0. | This is to be run after the A\P Ledger has been successfully upgraded in the automatic Upgrade Plan. Suspend all Vouchering and Voucher Match activity from the time of the upgrade through successful completion of this job. | Critical A\P features in invoicing will malfunction if this job is not run. | New fields have been added to F0411. This updates the domestic amount to distribute (ATAD), foreign amount to distribute (CTAD), domestic non recoverable tax amount (NRTA), foreign non recoverable tax amount (FNRT) and base company currency code (BCRC). The Purchase Order number (RPPO) is left padded with zeros. |
| R89069116 | To convert F069116 from XE | None. | This table conversion populates the new field PHISH. | The following fields were added to F069116: LVPT and PHISH. After this program is run, PHISH will contain "1 ". LVPT will remain blank. |
| R8908601C | To convert F08601 from XE\ERP 8.0. | The processing option of this job should be set based on whether only JD Edwards World was used to enter Health and Safety information from the source environment. A processing option value of 1 indicates that JD Edwards World was used, while a processing option value of 0 or Blank indicates that JD Edwards World was not used exclusively for information entry and JD Edwards EnterpriseOne applications may have been used to enter Health and Safety information. | This table conversion checks for and handles the following scenarios:
1. Processing option is set to 1 (indicates that yes, only JD Edwards World was used to enter Health and Safety information). 2. Processing option is set to 0 or Blank (indicates that no, JD Edwards World was not used exclusively to enter Health and Safety Information). |
Country (CTR) and Incident Occurred on Employer's Premises (ONPRM) columns were added to F08601. |
| R890015B | To convert F0015 from XE\ERP 8.0 for Triangulation Exchange Rates. | This program must run after R891015A - F0015\F00151 Exchange Rate table conversion has completed successfully and the F0015 Currency Exchange Rate table has been upgraded successfully in the automatic Upgrade Plan. Suspend any processes requiring exchange rates from the time of the upgrade through the successful completion of the job. The following objects are required:
F0015 R891015B R891015B\XJDE0001 |
Triangulation exchange rates have values of zero if this job is not run. | After running the R891015A - F0015\F00151 Exchange Rate table conversion the triangulation records have rates that are blank or zero. This selects records from the converted F0015 table where the calculation method is triangulation (CLMETH=3). The rates for the triangulation records are retrieved from the corresponding rates in the F0015 table for both multiplier (CRR) and divisor (CRRD) rates and updated to the triangulation records. |
| R891216 | To convert F1216 when upgrading from XE\ERP 8.0 and requires special attention for whether or not SAR 5685791 has been applied to JD Edwards EnterpriseOne Xe. If this SAR has been applied to Xe before upgrading, then there is no need for F1216 data conversion because the data has already been corrected when the SAR was applied. Otherwise, the F1216 data needs to be corrected to fix the data that has been entered from JD Edwards EnterpriseOne before.
Migrating from JD Edwards World does not require the F1216 data conversion because the data entered from JD Edwards World is in the correct format. |
None | This conversion program corrects existing data in the F1216 table that has been entered using JD Edwards EnterpriseOne Xe. The conversion program only modifies data that is stored incorrectly in the table. The conversion program reformats data in the F1216 table and corrects the mapping. | When upgrading from Xe/ERP 8.0, the F1216 table may need a data conversion to correct the data that has previously been entered from JD Edwards EnterpriseOne. Please, also refer to the Breaking News message that has been published with regard to these issues and the data conversion for JD Edwards EnterpriseOne Xe. |
| R894801P | To convert F4801 \ F4801T \ F4817 from XE\ERP 8.0 when working with configured items, serialized components, or generating orders through Customer Service and Warranty or Equipment and Maintenance. | Two processing options exist for this report:
Convert URCD Convert PARS If the client does not use serialized components or work with configured items, these processing options should be set as blank. |
This report must run to consolidate the F4817 table records into the F4801T tables, set the SRCN field, and reset the configured work order's parent number to the immediate higher related work order in the configured item's construction. | This report consolidates the F4801T and F4817 tables, properly sets the new serialized component field in F4801T, and reassigns the parent work order numbers for the configured item work orders. |
| R8948164A | To convert F48164 Media Objects from XE\ERP 8.0 for old Knowledge Base. | Requires that table conversions for F00165 and F48164 completed successfully. | To properly convert old Knowledge Base media objects. If this is not run, that information is not available for use by the new Failure Analysis applications. | The media object structure for Failure Analysis has changed. Previously, the media objects were stored in one structure. Now, the media object structure is split into three separate structures. |
| R8930006D | To convert F30006 Work Center Master from XE\ERP 8.0. | R8930006C must have completed successfully | Blank values in the work center branch plant field are no longer supported because application P3003 and P3112 validate the work center and the branch plant being used. | The primary key of the F30006 table was changed from Work Center (MCU) to Branch/Plant (MMCU) and Work Center in order to support the concept of the work center branch plant. R8930006C is responsible for placing each work center into the respective branch plants based on records found in the F3003 table. However, in the event that the work center is not used in F3003, the branch plant remains blank in the F30006 table. R8930006D assigns these work centers with a default branch plant value, and selects all records with a Branch/Plant of blank and sets the field equal to the default Branch/Plant in the processing option. |
| R3365 | To regenerate the Resource Profile in Capacity Planning. | Run the batch application R3365 to populate F3303 Capacity Resource Profile. Make sure F4101, F4102, F3002, F3003, F30006, F3007 and F0007 tables have converted for existing data. Data for F3460 is already available since the table has not been changed. | Populates the F3303 Capacity Resource Profile table. | A new field was introduced to the F3303 table. A table conversion was not created for this table due to the complexities of the logic in conversion and the existing solution of running this batch application to create the Resource Profile. |
| R3380 | To convert F3311 \ F3312 \ F3313 from XE\ERP 8.0 for Resource Requirement Planning. | Run the batch application R3380 to populate F3311, F3312, F3313. Make sure F4101, F4102, F3002, F3003, F30006, F3007, F0007, F3411 and F33133 tables have converted for existing data. Data for F3460 is already available since the table has not been changed. | Populates the F3311, F3312, and F3313 tables. | A new field was introduced to the F3311, F3312, and F3313 tables. Table conversions were not created for these tables because of the complexities of the logic in conversion and the existing solution of running batch applications to create Capacity Message, Capacity Peggins and Capacity Load. The R3380 or R3382 programs are the existing batch applications. User has to select either Resource Requirements Planning (R3380) or Rough Cut Capacity Planning\Capacity Requirements Planning (R3382) depending on whether they are using Resource Requirements Planning (RRP) or Rough Cut Capacity Planning\Capacity Requirements Planning (RCCP\CRP). |
| R3382 | To convert F3311 \ F3312 \ F3313 from XE\ERP 8.0 for Rough Cut Capacity Planning\Capacity Requirements Planning. | Run the batch application R3382 to populate F3311, F3312, F3313. Make sure F4101, F4102, F3002, F3003, F30006, F3007, F0007, F3411 and F33133 tables have converted for existing data. Data for F3460 is already available since the table has not been changed. | Populates the F3311, F3312, and 3313 tables. | A new field was introduced to the F331, F3312, and F3313 tables. Table conversions were not created for these tables because of the complexities of the logic in conversion and the existing solution of running batch applications to create Capacity Message, Capacity Peggins and Capacity Load. R3380 or R3382 is the existing batch application. User has to select either Resource Requirements Planning (R3380) or Rough Cut Capacity Planning\Capacity Requirements Planning (R3382) depending on whether they are using Resource Requirements Planning (RRP) or Rough Cut Capacity Planning\Capacity Requirements Planning (RCCP\CRP). |
| R31P40039 | To convert F40039 when upgrading from XE\ERP 8.0.
If you have chosen a new document type for some work orders, which is different from the document type you used in the past for those work orders, you must run R48803 in order to correct that document type in your tables. See the Setup instructions in the Enterprise Asset Management, Shop Floor and the Engineering Project Management Guides for more details. Note: See the table below for information regarding the values to enter for the processing options. |
This is to be run immediately after upgrading to validate all programs using F4801\F4801T Order Type prior to database output. Make sure all order types in the 00\DT have been set up in the Document Type Revisions (P40040) before running R31P40039 to convert work orders. | If different types of work orders have been mixed in a single Order Type value, they must convert the F4801 work orders to separate the records by order type. If this job is not run, none of the programs that enter data into F4801\F4801T (for example, Manufacturing Work Order Entry, Equipment Order Entry, Service Order Entry, etc.) are able to function. | It is necessary that all Work Order Types be unique, which is set up in the Document Type Master. For example, an order type of "WO" needs to be set equal to "02" (Manufacturing Work Order). This is set up manually using Document Type Revisions (P40040), or by running F40039 Conversion from Xe (R31P40039). If there are a large number of order types to set up, the UBE may be more efficient. This should be set up once, prior to the following steps. |
| R8903B571A | To set next unique key id for F03B571 when upgrading from XE\ERP 8.0. | The table upgrade plan should be successfully completed. Suspend all Automatic Debit processing until this UBE completes successfully. | This job must be run for Autodebit processing to function correctly. | This report adds\updates an entry in the F00022 table for the F03B571 table and sets the next unique key ID equal to the next auto debit batch control number. |
| R8900165K | To change GT0411S Key to use KCO when upgrading from XE\ERP 8.0 and have not yet taken SAR 5848035. Also this UBE is only required for users using Media Object Attachments for vouchers. | This is to be run after the F00165 table has been successfully upgraded in the automatic Upgrade Plan. Objects required: Change GT0411S Key to use KCO not CO | After running this job existing Media Objects Attachments for Vouchers are accessible from the Voucher Entry Program (P0411) and Speed Status Change (P0411S). | This conversion program takes records from the F00165 with object name (OBNM) equal to GT0411S and ensures that the Generic Text Key (TXKY) is written in the format KCO|DCT|DOC|SFX. Where records are written with TXKY format equal to CO|DCT|DOC|SFX it replaces the generic text key field with KCO instead of CO and preserves the rest of the key. |
| R8900165JA | To convert F00165 JEDTLGT to GT0911A when upgrading from XE\ERP 8.0. | This is to be run after the F00165 table has been successfully upgraded in the automatic Upgrade Plan. Requires objects: F00165 Convert JEDTLGT to GT0911A | After running this job, existing Media Objects attachments for voucher G\L distributions are accessible from the Voucher G\L Distribution form (P0411 | W0411K). | This process converts all voucher G\L distribution attachment records in the F00165 table to be coexistent with JD Edwards World and with JD Edwards EnterpriseOne A\R and G\L systems. Attachments entered for voucher G\L distribution records were written to F00165 with Object Name (OBNM) equal to JEDTLGT. Instead, these should have been written with Object Name equal to GT0911A. For each record in F00165 with Object Name (OBNM) equal to JEDTLGT, this conversion changes the Object Name to GT0911A and modifies the Generic Text Key (TXKY) to match the structure of GT0911A. |
| R8900165JB | To convert JEDOCGT to GT0911 when upgrading from XE\ERP 8.0. | This is to be run after the F00165 table has been successfully upgraded in the automatic Upgrade Plan. Requires objects:F00165 Convert JEDOCGT to GT0911A. | After running this job, existing Media Objects attachments for Journal Entry document levels are accessible from the Account Ledger Inquiry form (P09200 | W09200A). | This process converts all journal entry document level attachment records in the F00165 table to be coexistent with JD Edwards World and with JD Edwards EnterpriseOne A\R and G\L systems. Attachments entered for journal entry document levels were written to F00165 with Object Name (OBNM) equal to JEDOCGT. Instead, these should have been written with Object Name equal to GT0911A. For each record in F00165 with Object Name (OBNM) equal to JEDOCGT, this conversion changes the Object Name to GT0911A and modifies the Generic Text Key (TXKY) to match GT0911A's structure. |
| R89060117A | To populate F060117A when upgrading from XE\ERP 8.0 and this job has not been run previously in an ESU. | None | Transfers any values that were stored in the F060117 table to the replacement field ALRN15 in the F060117A. | The original F060117 table contains a field to store the Alien Registration Number (ALRN). However, this field is not long enough to store an Admissions Number, which is an acceptable value for this field. The F060117A tag table was created with an appropriate length field (ALRN15) that replaces the one in the original table. |
| R89060117 | To populate Employee Master Tag Tables when upgrading from XE\ERP 8.0. | None. | This TC populates the F060117 record for every existing F060116 record. | Prior to 8.9 the F060117 table was treated as a tag to F060116, in that it may or may not have a corresponding record in F060117 if a record existed in F060116. After 8.9 the application was changed so that if there was no F060117 record an error would be issued. This TC populates the F060117 record for every F060116 record, so that the application will not error automatically. |
| R890912 | To format OBJ and SUB in F0912 when upgrading from XE\ERP 8.0. | F0912, R890912 and R890912|XJDE0001 are required. The data stored in F0912 from a prior release is required. Suspend activity during the conversion. | Programs and applications requiring access to RJFROM and RJTHRU will not perform properly if the data has not been concatenated. | In JD Edwards World, application P0912 Recurring Journal Entry stored data for object and sub in separate fields. In EnterpriseOne, RJFROM and RJTHRU are used to store a combined object and sub. The table conversion concatenates OBJF and FSUB to form RJFROM, and OBJT and SUBT to form RJTHRU. This prevents the trouble of combining object and sub every time the fields are read and displayed. The table conversion retrieves the account separator from the General Accounting Constants for use when combining the two fields. |
| R891201A | To update WOYN in F1201 when upgrading from XE\ERP 8.0 to create Work Orders against equipment records. | Run after the table conversions have completed. | Work Orders cannot be created against any equipment record that does not have this flag turned on. | Logic was added to reference the Work Order Allowed Flag (WOYN) located in the F1201 table. This flag indicates whether a piece of equipment is allowed to have a Work Order entered against it. Previously WOYN existed in F1201 but was not referenced in the Work Order creation logic. |
| R8948SINVF | To convert INVF to Uppercase when upgrading from XE\ERP 8.0. | None. | This job should be run to ensure all Invoice Format Codes within Service and Contract Billing are uppercase and consistent across all tables that store this code. | The Data Item is modified for Invoice Format Code(INVF) to be uppercase only. |
| R8908601 | To update HH05 in F08601 when upgrading from XE\ERP 8.0. | None. | The table conversion R8908601 changes the data for HH05 in F08601 (Injury\Illness Case Master) from 1-7 to 01-05. | The OSHA 300 is now consistent with the one on the OSHA website. The number of injury\illness types has been reduced to 5 from 7. This is a legislative change. |
| R080101 | To set Address Book AT3 and synchronize ALPH and SSN for HR related Address Book records. | None. | This job should be run to ensure synchronization of the ALPH and SSN fields between the F0101 and the F060116, F08401 and F08901. | Many tables used in the workforce management suite have ALPH and SSN fields. The address book table also has these two fields. In an effort to keep the duplicate data consistent across the database a flag in the F0101 (AT3) is set to a Y to indicate that changes should be updated to these additional tables. Previously the synchronization was based solely on search type, this method was deemed in adequate because search type is somewhat user defined and hard coding is not appropriate. This UBE takes existing records in the F0101 and if a matching record exists in one of three tables (F060116, F08401 and F08901) the AT3 flag is updated to a Y. If either the ALPH or SSN is out of sync the F0101 values are updated to the corresponding table. |
| R7611B | To update BSTT in F7611B when upgrading from XE\ERP8.0, and have not taken ESU #4937298. | Requires clear understanding of the Brazil process on how to populate the F7611B table correctly. | The ICMS Tax Situation Code (BSTT) contains incorrect values if this job is not run. | This is a data conversion UBE that converts the ICMS Tax Situation Code (BSTT) field based on an algorithm.
Do not execute for a World A9.2 migration. Do not re-run from the Xe/E80 Post Install menu for World A7.3 migration. |
| R897611B | To populate BST1 in F7611B when upgrading from XE\ERP 8.0, and have run the pre-requisite R7611B once. | Requires clear understanding of the Brazil process on how to populate the F7611B table correctly. | The new ICMS Tax Situation Code (BST1) has incorrect values if this job is not run. | Populates a new ICMS Tax Situation code field (BST1) in table F7611B with the concatenated value of Item Origin (BORI) and old ICMS Tax Situation Code (BSTT). This new BST1 field is now of size=3 as compared to size=2 for prior releases.
Do not execute for a World A9.2 migration. Do not re-run from the Xe/E80 Post Install menu for World A7.3 migration |
| R98403A |XJDE0001
* Must Run on the Deployment Server |
All customers | Run after all table conversions have been completed. Do not alter the Data Selection for this table conversion. Set processing options to copy the tables from Source Environment JDEPLAN to the Target Environment you are upgrading to, for example, DV9. | Errors due to missing vital data occur if this job is not run. For example, writing to certain accounts could generate an error. | Copies the data contained in demo data on the installation image to the customer's database. |
| R9500165 | To remove RTF formatting. Run if you cannot see any customized dictionary glossaries when viewing them through the application. | Run after table conversion process. Most customers do not need to run the UBE. Check your customized data dictionary glossaries. If they appear to have disappeared, schedule this UBE to run at a convenient time. There is no loss of data. Once the UBE has run, the glossaries are visible. It runs for several hours. | Rerun if glossary items are missing (most likely for Korean and Japanese glossary items). | |
| R8991300 | To upgrade Scheduler Job Master when upgrading from Xe\ERP8. | This conversion must be run before the F0092 series of conversions is complete. That series includes R89959212, R89959211, and R8995921. | Run from the JDEPLAN environment. | The conversion reads over the F91300 table row by row. Except for the *Scheduler record it fetches the user group out of F0092 based on the user id stored in SCHUSER in F91300. The user group from F0092 is then stored in SCHROLE.
It is important that customers designate the Properties of the table conversion to input the source environment (for example, DV7333) and the target environment (for example, DV910) so that the records are properly located and updated. If you do not check the Properties box in the Table Conversion Prompting screen, the UBE is submitted with whatever has been previously designated in the options (if anything). Also, because no PDF is created, you should check the TC log in the Print Queue directory to determine if there were errors or any problems during the execution. |
| R8991320 | To upgrade Job Schedule when upgrading from Xe\ERP8. | This conversion must be run before the F0092 series of conversions is complete. That series includes R89959212, R89959211, and R8995921. | Run from the JDEPLAN environment. | The conversion reads over the F91320 table row by row. It fetches the user group out of F0092 based on the user id stored in SCHUSER in F91320. The user group from F0092 is then stored in SCHROLE. |
| R89959212 | This UBE populates the F0092 (User Profiles) table and the F00926 (Role Descriptions) from the Roles and Descriptions that may have been previously set up in the UDC H95\RL. This UDC was used for Phase I and is now being removed. | Only required if the customer is upgrading from a release prior to 8.9.
If applicable to your upgrade, this UBE should be run as the first in this 3-part sequence: R89959212 R89959211 R8995921 |
The UBE uses each Role from the UDC H95\RL (the role is stored in the data item column KY in the F0005 table). The UBE populates the UGRP field in the F0092 table with this Role. It also populates the F00926 table with the Role Description, previously in the DL01 and DL02 columns of the F0005 table, the values in these columns are concatenated and inserted into the F00926 table, column ROLEDESC. If the insert to the F0092 table is successful, the F0005D table is then fetched upon to retrieve all of the possible language descriptions for the Role Descriptions. Those, as well, are populated in the F00926 table. Each Domestic Language Record in the F00926 table contains a Sequence Number. When running this UBE, the sequence numbers begin at 500 and increase by 5. | The 8.9 release introduces Roles. If upgrading from a release prior to 8.9, you must run a sequence of UBEs to convert Groups (as listed in the F0092) table to Roles. This creates a sequence number for each role and inserts role relationships based upon users\group records in the F0092 table.If you are running ERP 8.9 or later and wish to upgrade, you do not need to run these UBEs as the F0092, F00926 and F95921 tables already contain the necessary records. |
| R89959211 | This TC takes all current Groups in the UGRP field in the F0092 table and adds a Description record for them in the F00926 table. The Role is the Group name (Ex: OWTOOL), the description is also the Group Name as a description is required. A sequence Number is added to the F00926 record as well. This sequence number begins at 1000 and increments by 5 with each record written. | Only required if the customer is upgrading from a release prior to 8.9.
If applicable to your upgrade, this UBE should be run as the second in this 3-part sequence: R89959212 R89959211 R8995921 |
The UBE retrieves each Group from the F0092 table. It populates the USER field in the F00926 table with this Role. It also populates the F00926 table with the Role Description which is also the Group value from the F0092 table. This value is inserted into the F00926 table, column ROLEDESC. Each Domestic Language Record in the F00926 table contains a Sequence Number. When running this UBE, the sequence numbers begin at 1500 and increase by 5. | Refer to Notes in R89959212 above. |
| R8995921 | This TC takes all current User Profiles records in the F0092 table and inserts a User\Role Relationship Record based on the F0092.USER and F0092.UGRP tables. The record that is added to the F95921 table contains the User, Role (formerly the Group for this user in the F0092 table), Effective and Expiration Dates. Some of these values are based upon the values in the processing option. | Only required if the customer is upgrading from a release prior to 8.9.
If applicable to your upgrade, this UBE should be run as the third in this 3-part sequence: R89959212 R89959211 R8995921 Values in the records inserted into the F95921 table are based upon those inserted into the processing option at submission time. |
The UBE retrieves each User Record from the F0092 (User Profiles) table. It populates the following output fields: F95921.RLFRROLE - F0092.USERF95921.RLTOROLE - F0092.UGRPF95921.RLEFFDATE - PO EffectiveDateF95921.RLEXPIRDATE - PO ExpirationDateF95921.RLFUROLE1 - PO cIncludedInAllF95921.RLROLETYP - "0" And Audit Info. The F95921 table is inserted with the information above. One Record per user in the F0092 table. If the Mode of the version is Final, the F0092.UGRP field is left blank for all users in the F0092 table. | Refer to Notes in R89959212 above. |
This section contains a list of all the Table Conversions required when upgrading from 8.9 or below.
| Upgrading from 8.9 or Below | ||||
|---|---|---|---|---|
| Conversion Program | Run this Job | Requirements | Purpose | Notes |
| R48803 | Convert Document Type for existing orders by running the post install JD Edwards EnterpriseOne UBE R48803. Before running this UBE, see the Programmer's Guide for more information. | Before running the UBE, see the Programmer's guide about more information regarding who should run the UBE, requirements of the UBE, and the purpose of this UBE. | Not applicable. | This is not a Table conversion for converting data from prior release. This is a post install UBE that needs to be run one time to convert Order Types for existing records. This conversion is necessary because of changes made to Document Types, based on EPM requirements. The new document type is defined in the processing options. For the orders selected in the data selection, the document type is converted. |
| R891207B | To update PDFG in F1207 when upgrading from 8.9 or below. | The TC should be run over the entire F1207 table. | This post-install job reads through existing maintenance schedules in the F1207 and updates the schedule type (PDFG) field with a "1" for those schedules that have no service intervals defined. | As part of the Condition-Based Maintenance enhancement, the schedule type (PDFG) field is now utilized on the Equipment PM Schedule (F1207) record to identify the type of maintenance. A value of blanks is for Interval Based Maintenance. A value of "1" is for Unschedule Maintenance. A value of "2" is for Condition-Based Maintenance. |
| R8912071B | To update PDFG in F12071 when upgrading from 8.9 or below. | The TC should be run over the entire F12071 table. | This post-install job reads through existing model maintenance schedules in the F12071 and updates the schedule type (PDFG) field with a "1" for those schedules that have no service intervals defined. | As part of the Condition-Based Maintenance enhancement, the schedule type (PDFG) field is now utilized on the Equipment PM Schedule Model (F12071) record to identify the type of maintenance. A value of blank is for Interval Based Maintenance. A value of "1" is for Unscheduled Maintenance. A value of "2" is for Condition-Based Maintenance. |
| R3210CFGID | To convert Config ID when upgrading from 8.9 or below. | None. | This UBE determines the highest seed from F3201 and writes it to Bucket 2 of Next Numbers System 32. | The Configuration ID (which is the primary key field of Configurator F3201 Master File) will now be retrieved from Next Number instead of using the "seed" record in F3201 Configurator Master Table. |
This section contains a list of all the Table Conversions required when upgrading from 8.10 or below.
| Upgrading from 8.10 or Below | ||||
|---|---|---|---|---|
| Conversion Program | Run this Job | Requirements | Purpose | Notes |
| R8901151 | To move Email Address from F0111 to F01151 when upgrading from 8.10 or below. | Four processing Options exist for this conversion:
1 - Run in Proof or Final Mode. 2 - Do you want to reset the remark field in F0101 to blank or not. 3 - Enter the default value of the Email Hierarchy field. 4 - Process all records or only records with an associated User ID. |
This conversion moves Email addresses from the Who's Who table (F0111) to the Electronic Address table (F01151). If this is not run, Email addresses will not be accessible. | The UBE prints out a pdf listing the records processed and displays how the F01151 columns were updated. |
| R891755B | To convert F1755 for Case when upgrading from 8.10 or below. | Three Processing Options exist for this TC:
1 - Enter the time zone of the system date and time. 2 - Enter the daylight savings rule of the system date and time. 3 - Do you want to update the work order table with the case number of the record being converted? "0" - Do Not Update. "1" Update. |
To convert the existing dates and times in F1755 to UTC time. To blank out the work order number in F1755 and to populate case number in F4801. | |
| R3210CFGID | To convert Config ID when upgrading from 8.10 or below. | None. | This UBE determines the highest seed from F3201 and writes it to Bucket 2 of Next Numbers System 32. | The Configuration ID (which is the primary key field of Configurator F3201 Master File) will now be retrieved from Next Number instead of using the "seed" record in F3201 Configurator Master Table. |
| R01302 | To convert F0101 Compressed Description when upgrading from 8.10 or below. | Run this UBE when UDC H95|SC has changed. The values shipped with the software are:
~!@#^&*()_+`-={}|[]\:";'<>?,.\ |
This UBE strips off special characters from the DC field in F0101 as a result of changing the UDC H95|SC (Word Search Special Characters). | If the UDC H95|SC values are changed and an address book record is added, this will cause inconsistencies in the DC fields. An example of this would be the blank value. If blank is part of the list, the "Digger Corporation" will be stripped to be "DIGGERCORPORATION" in the DC field else it would be "DIGGER CORPORATION". |
| R890911CA | To populate F0911 Foreign Amount when upgrading from 8.10 or below. | Run after the table conversions have completed. | A new foreign amount field (GLACR) is added to the Account Ledger table. The TC will populate the new foreign amount field based on the existing CA ledger records. | A new foreign amount field (GLACR) is added to the Account Ledger table so all of the currency information is available in one F0911 record and the extra CA record is no longer needed. The system continues to write the CA ledger records during this first phase. |
| R890911PCA | To populate F0911P Foreign Amount when upgrading from 8.10 or below. | Run after the table conversions have completed. | A new foreign amount field (GLACR) is added to the Account Ledger Purge table. The TC will populate the new foreign amount field based on the existing CA ledger records. | A new foreign amount field (GLACR) is added to the Account Ledger Purge table so all of the currency information is available in one F0911 record and the extra CA record is no longer needed. The system continues to write the CA ledger records during this first phase. |
This section contains a list of all the Table Conversions required when upgrading from 8.11 or below.
| Upgrading from 8.11 or Below | ||||
|---|---|---|---|---|
| Conversion Program | Run this Job | Requirements | Purpose | Notes |
| R8908771A | To populate F08771A when upgrading from 8.11 or below. | The Processing Option of this job sets the value for the new field MSEB in the table F08771A. | This TC populates the F08771A tag table with the MSEB value from the processing option value selected. | The tag table F08771A was added with the MSEB column to allow managers to signoff on the final performance appraisal on behalf of the employee. A value of "1" means Yes, managers can approve or contest the final appraisal on the employee's behalf. A value of "0" means No, employees access the appraisal system through Employee Self Service and approve or contest the appraisal themselves. |
| R8908772A | To populate F08772A when upgrading from 8.11 or below. | The Processing Option of this job sets the value for the new field MSEB in the table F08772A. | This TC populates the F08772A tag table with the MSEB value from the processing option value selected. | The tag table F08772A was added with the MSEB column to allow managers to signoff on the final performance appraisal on behalf of the employee. A value of "1" means Yes, managers can approve or contest the final appraisal on the employee's behalf. A value of "0" means No, employees access the appraisal system through Employee Self Service and approve or contest the appraisal themselves. |
| R8908773A | To populate F08773A when upgrading from 8.11 or below. | The Processing Option of this job sets the value for the new field MSEB in the table F08773A. | This TC populates the F08773A tag table with the MSEB value from the processing option value selected. | The tag table F08773A was added with the MSEB column to allow managers to signoff on the final performance appraisal on behalf of the employee. A value of "1" means Yes, managers can approve or contest the final appraisal on the employee's behalf. A value of "0" means No, employees access the appraisal system through Employee Self Service and approve or contest the appraisal themselves. |
| R89087711A | XJDE0001 | To populate F087711A Current when upgrading from 8.11 or below. | The Processing Option of this job sets the value for the new field MSEB in the table F087711A. | This TC populates the F087711A tag table with the MSEB value from the processing option value selected. | The tag table F087711A was added with the MSEB column to allow managers to sign off on the final performance appraisal on behalf of the employee. A value of "1" means Yes, managers can approve or contest the final appraisal on the employee's behalf. A value of "0" means No, employees access the appraisal system through Employee Self Service and approve or contest the appraisal themselves. |
| R89087711A | XJDE0002 | To populate F087711A Historic when upgrading from 8.11 or below. | The Processing Option of this job sets the value for the new field MSEB in the table F087711A. | This TC populates the F087711A tag table with the MSEB value from the processing option value selected. | The tag table F087711A was added with the MSEB column to allow managers to sign off on the final performance appraisal on behalf of the employee. A value of "1" means Yes, managers can approve or contest the final appraisal on the employee's behalf. A value of "0" means No, employees access the appraisal system through Employee Self Service and approve or contest the appraisal themselves. |
| R890411B | To generate F76C4011 from F0411 when upgrading from 8.11 or below. | |||
| R8913907A | To convert F13907 SWO (Separate Work Order) field from 8.11 or below. | Run after the table conversions have completed. | Any data in the SWO field that used to be a Y will be changed to a 1. Any data in the SWO field that used to be an N will be changed to a 2. | Prior to 8.11 SP1, there was no editing for the Separate Work Order (SWO) field in the Associative Service Types (P13907) application. The existing application allowed entries of Y, N, 1, or 2, however the UDC attached to the SWO data dictionary only listed values of 1 and 2.
To keep things simple, editing was turned on for the DD item so new entries into that fields would be validated against the UDC. Since clients could have existing data that used a Y or N, this post-install was created to correct that data. |
| R8976V01 | To generate F76C4015 from F0411 when upgrading from 8.11 and SAR 7668978 has not been previously applied. Do not run if upgrading from 8.10 or below. | Requires use of Venezuela's localization. | For each Credit\Debit Note in table F0411 related to a Voucher in table F0411, the TC generates a record into table F76V4015 to relate the Credit\Debit Note and the Voucher. | |
| R8976V02 | To generate F76V4011 from F76V0401 when upgrading from 8.11 and SAR 7668978 has not been previously applied. Do not run if upgrading from 8.10 or below. | Requires use of Venezuela's localization. | For each record in table F76V401, the TC generates a record into table F76V4011 to store the localized voucher information. | |
| R893016 | To populate F3016T from F3016 when upgrading from 8.11 or below. | None. | This TC creates a corresponding F3016T tag record for every existing F3016 record. | |
| R893283F | To fix CTKID in F3283 when upgrading from 8.11 or below. | None. | This TC cleans up the data in F3283 for the entire table. | This report should fix all the records. If there are any problems, the records shall be listed on the report. These problematic records can be re-run using R893283L UBE, which uses data selection. Run the records that had issues. If problems persist, these records may need to be manually removed from the database and re-added. |
| R893283L | To fix CTKID in select F3283 records when upgrading from 8.11 or below. | R893283F | This TC cleans up the data in F3283 for select records. | Run this TC only if there were problematic records reported in R893283F. |
| R893215F | To fix CFGSID in F32xx when upgrading from 8.11 or below. | None. | This TC cleans up the data in F3215, F3211, F32119, F32159 and F41021 for the entire table. | This report should fix all the records. If there are any problems, the records shall be listed on the report. These problematic records can be re-run using R893215L UBE, which uses data selection. Run the records that had issues. If problems persist, these records may need to be manually removed from the database and re-added. |
| R893215L | To fix CFGSID in select F32xx records when upgrading from 8.11 or below. | R893215F | This TC cleans up the data in F3215, F3211, F32119, F32159 and F41021 for select records. | Run this TC only if there were problematic records reported in R893215F. |
| R099102 | To populate the new Debit Amounts AND01-14 in F0902 when upgrading from 8.11 or below. | Run after the table conversions have completed. | The Repost on menu G09316 updates the F0902 table with the Debit Amounts. | Debit fields AND01-14 that were formerly located in tag table F0902A were added to the F0902.
Many applications require data for total debits or total credits. Prior to the change, the data was obtained from the F0911, causing performance issues. With this change the data is retrieved from the F0902 resulting in improved performance. |
| R8900165JC | XJDE0001 | To convert media object data from GT0901 to ACCGT for Job Status Inquiry. | None. | This conversion copies the data in F00165 for GT0901 to ACCGT so Job Status Inquiry can access the media object. | Prior to 8.11 SP1, Job Status Inquiry was using the media object for GT0901 but all of the other job cost applications were using ACCGT. In order to make the media object data consistent across all of job cost, Job Status Inquiry was changed to use ACCGT instead of GT0901.
You only need to run this conversion if you are using Job Status Inquiry with media object data in GT0901. |
This section contains a list of all the Table Conversions required when upgrading from 8.11 SP1 or below.
| Upgrading from 8.11 SP1 or Below | ||||
|---|---|---|---|---|
| Conversion Program | Run this Job | Requirements | Purpose | Notes |
| R8908495 | To convert GT08495 Media Object from 8.11 SP1 or below. | This is to be run after the F00165 table has been successfully upgraded in the automatic Upgrade Plan. | N\A | This media object supported resumes and cover letters in the eRecruit module. Changes were made to allow the resume and cover letter to be searched with Verity text search. |
| R8908490I | To save Internal Applicant Address Info when upgrading from 8.11 SP1 or below. | None. | N\A | |
| R89069116A | To convert F069116 from 8.11 SP1 or below. | The processing option on this job prompts the user for a value to update the new field DEFR in F069116. | To update the new column DEFR in F069116. It is updated with a value of "1", "2", or "3" based on the processing option value. | This TC simply calls a BSFN (B8902023) that will do a mass update to DEFR based on the processing option value. |
| R8901301D | To convert Activities from 8.11 SP1. | Prior to running this post upgrade UBE, all users of activity system should already have universal time (time zone) and daylight savings rule set in their user profiles.
The processing option on this job prompts the user to enter the maximum number of occurrences for never ending activities. |
To populate new and changed fields in F01301.
To populate new field in F01331 and create new exclusion records for assignees. To write activity details in F01301D. For recurring activity with no end date: To update F01321 with a calculated end date based on the maximum number of occurrences specified in the Processing Option. To update F01321 with the combination of the originator's time zone and daylight saving rules (separated by |). |
F01301 (Activity Header): The owner parent record is assigned a new GUID for the group activity ID. All assignee's activity records are reassigned the same GUID as the parent owner. "All Day" events and tasks are now stored with time starting 00:00:00 and ending 23:59:59 local time of the orignator's time zone from the user profile.
F01331 (Exclusion): The existing exclusion record is updated with the Activity id of the Owner Master record. New exclusion records are created for the excluded assignee's series. The activity id updated for the new exclusion records is the activity id of the assignee's master record. F01321 (Recurrence Master): For recurring activities that have no end date, a finite end date is calculated based on the max number of occurrences specified in the UBE processing option. In addition, the combination of the activity's originator's time zone and daylight saving rule (fields separated by |) is updated in URCH. F01301D (Activity Details): Physical activity records for every instance of a recurring activity rescind in the new activity detail table F01301D. Activity search applications are changed to search over this new table, which allows for faster and easier search capabilities. |
| R4801T1 | To populate F4801T1 from F4801T when upgrading from 8.11 SP1 or below. Only customers that have data for ETO in F4801 need to run this TC. Do not run this TC if the ESU was applied prior to upgrade. | None. | This post-install UBE will populate table F4801T1 with data from F4801T. If there are records in F4801T with PRJM (project number) field populated corresponding records would be created in F4801T1. The only field that gets populated from F4801T into F4801T1 is DOCO. | |
This section contains a list of all the Table Conversions required when upgrading from 8.12 or below.
| Upgrading from 8.12 or Below | ||||
|---|---|---|---|---|
| Conversion Program | Run this Job | Requirements | Purpose | Notes |
| R09E115 | To update Expense Location UDC Codes when upgrading from 8.12 or below. | None. | To reformat the values in UDC 09E|EL. | The size of the UDC Code 09E|EL has been increased to 10 characters. This caused the values to be left padded with spaces to make up the difference in size. This UBE will remove that left padding. |
| R05041 | To add data items to Future Data \ History Tracking when upgrading from 8.12 or below. | None. | To create a record in F06041 and F08041 for each new data item added to the F060116. For records added, set respective flags in tables (ICDE, XCOD) = "N" | F06041 - Future Data FieldsF08041 - History Tracking Fields. These tables are pre-populated with records that the client may toggle to "on" or "off" for tracking history. In 90, 2 new fields were added, that will be shipped with the data set. For customers upgrading, from say 812 to 90, the ube would be run to add the two new records, but maintain the existing data set that the customer may have changed. This UBE should ensure that the client's preferences are not lost, while gaining the ability to modify the two new records. |
| R98305V | When upgrading from 8.12. | None | To convert all existing Web Only versions to full versions. | None |
| R8915L101A | To change GT15L101 Key when upgrading from 8.12 or below. | This post-install UBE, must be run AFTER the R8915L101 TC has completed successfully. | The purpose of this Table Conversion is to enable customers to convert existing media objects in the F00165 that match the GT15L101 media object structure. Since the F15L101 table was changed to include UKID in the primary key, the resulting media objects attached to the unit master were also changed to match this key. As a result, a conversion was written to "re-key" those media objects to utilize the updated key structure. This conversion was required as a result of changes made to support inclusion of multiple leases (i.e. future leases and speculative leases). | This conversion program does not need to be run unless the Media Objects Storage (F00165) table contains very specific data. If the OBNM field of any record contains GT15L101, the table conversion is necessary. Although it is not harmful to run the procedure anyway, you can determine if the table conversion is necessary by performing the following SQL statement (with the appropriate syntax, against the appropriate database).
Select count (*) from F00165 where GDOBNM = 'GT15L101' If the returned count is greater than zero, the conversion program must be run. This count is the number of records that are candidates to be analyzed by this UBE. |
| R89I100B | When upgrading from previous releases and running India Localizations. | Apply ESU for SAR 8868437 to add R89I100B to the menu. If the ESU has not been applied and the conversion needs to be run, you must do it manually from Batch Versions. | To combine the information from F75I100 and F75I101A into one table and add new fields for TDS Certificate functionality. | This table was modified to save information that was in the F75I100 table and F75I101A table. Also, some new fields were added to this table. The conversion program copies the old F75I100 records, completes the new fields with blank or zero, and moves information from F75I101A to F75I100 record. |
| R8940G00 | To convert all Grower Area fields to the correct format based on the new display decimals when upgrading from 8.12 or below. | Four processing Options exist for this conversion:
1 - Data Item Class. 2 - New Data Display Decimals. 3 - Enter 1 to Update the Display Decimals in the Data Dictionary. 4 - Enter 1 to convert the data and update the tables. |
Display decimal changes in the Data Dictionary are not updated through the upgrade process. A new data class is created for the grower area fields (GROWERAREA). This post install UBE will update the display decimals (specified in the UBE processing options) for the new data class. The UBE will also convert the data to the correct format for the new display decimals for the following tables:
F40G03 - Harvest Master F40G0300 - Update Harvest Profile F40G02 - Block Master F40G0200 - Update Block Profile F40G65 - Farming Operation Header F31B70 - Vessel Assignment Table |
The following DB items were created with varying lengths and no display decimals. In 9.0, they are modified to have display decimals with a length of 4. The DD items are: PLTAREA, GRSAREA, TRTAREA, PAREA1, PAREA2, PAREA3. |
| R48S84A | When upgrading from 8.11 SP1 or 8.12 and you have existing Pool Grouping Code records in the F48S84 table. | Run this batch application after the F48S84 table has been converted. | This batch application will update the ending date if applicable on records in the Pool Grouping Code Table (F48S84). | An Ending Effective Date has been added to the F48S84 table. This job should be run to ensure there is no overlapping pool grouping code records. If there is a pool grouping code with different begin dates, the batch application R48S84A will update the ending date of the earlier record with an ending date one day prior to the begin date of the next record.
Note: This Post Install UBE is only needed when upgrading from 8.11 SP1 and 8.12 |
This section contains a list of all the Table Conversions required when upgrading from 9.0 or below.
| Upgrading from 9.0 or Below | ||||
|---|---|---|---|---|
| Conversion Program | Run this Job | Requirements | Purpose | Notes |
| R43S001 | When upgrading from 9.0 or below and ESU has not already been installed in prior release. | F43S001, UDC 43S|AL | This TC will populate the F43S001 table with the list of supported alerts from the UDC 43S|AL. | If ESU was installed in From Release, then this conversion does not need to be run again. |
| R41B100 | To update data in tables that contain the VCF data item; it does not modify the table structure.
It should be run in Final mode only once. It can be run in Proof mode multiple times. Proof mode does not perform any updates. |
Users should verify that this report has not already been run. It was required if the user took the ESU for SARs 8567415 (Xe), 8757032 (8.12) or 8820775 (9.0). | This report converts the data in the Volume Correction Factor (VCF) field of the tables listed below from 4 decimals to 5 decimals.
Tables containing VCF: F38111 - Agreements Transaction Ledger F41511 - Bulk Product Transaction File F41515 - Multi-Meter Readings F49211- Sales Order Detail File - Tag F49211Z1- Sales Order Detail Tag Unedited F49219- Sales Order Detail - Tag History F4963 - Load In-transit F49631- Load In-transit Ledger F49632 - Load In-transit Left on Board F49299 - S.O. Detail Tag Ledger File |
The report should be run in Proof mode first. If the processing option to display the records is set to 1, the report will display all the records that will be updated and what the volume correction factor will be updated to. If the processing option is not set to display records, the total number of records in each table that will be updated is displayed.
Run the report in Final mode only one time, regardless of the value of the processing option to display records. If the report is run in Final mode more than once, the data will be incorrect. |
| R8940G34 | To populate item and harvest pattern information that was previously stored in the Grower Block table (F40G02) into the Harvest Item Master (F40G034). | This TC is dependent upon the *ALTER record being processed successfully for the Grower Block table (F40G02) and the Grower Harvest table (F40G03). The *ALTER conversions will convert the tables to the new 9.1 format. Then R8940G34 can be run to process the records and populate the F40G034 columns. | F40G034 table was added to support crop rotation functionality in which item is an attribute of the harvest rather than of the block.
A record is inserted into F40G034 for every Grower Harvest record (F40G03) for each Block record (F40G02). F40G034 will be populated with the Vessel ID from F40G03 and with Short Item Number, 2nd Item Number, 3rd Item Number, and Harvest Pattern from F40G02. |
This TC is also being released in an ESU for 9.0. Users upgrading from release 9.0 to 9.1 that have taken the ESU will not be required to run the Post Install table conversion.
R8940G34 deletes existing records found in F40G034 before creating new records so it may be run more than once without errors. |
| R41806 | To automatically mark all item and item branch records as country of origin required. | None | The TC should be run as a post install only if the Country of Origin functionality is desired after an upgrade to 9.1. | The user should set up data selection only for those items and branches for which they wish to activate the country of origin required functionality. Users will need to specify proof or final mode, and decide whether to activate the country of origin at the item master level. The user can also specify a default country of origin value to give to the item branch records. |
| R41807 | After the country of origin required flag has been activated for the first time on an existing item branch you will use this TC to update all existing lots to the correct country of origin. | Should be run after the R41806. | This TC is run once the required flag has been activated and if this is being run as part of the post install process it should be run after the R41806 is run. | User should restrict any lots that already have a country of origin from the data selection. There is a proof and final mode processing option, and there is a default value for the country of origin for the lot. |
| R31B8505 | This TC will update all data currently residing in the weigh tag master file which currently contains lot information to now contain lot and country of origin information. | Should be run after the R41806 and R41807. | This TC should be run as a post install and only if the client utilizes the grower weigh tag functionality. | There is a proof and final mode processing option, and there is a default value for the country of origin for the lot. |
| R8976A08 | This process copies current Country of Origin data at Item/Lot level used by Argentina Localization (field LRP9 of F4108) to the new ORIG field into table F4108. | The process has to be executed only when the customer is using Argentina Localization and selling Imported Items by Sales Order module. | This UBE has to be executed as a Post Install from any 9.1 prior releases to 9.1 or higher releases. | In case the country codes in UDC 41/L9 are not the same than UDC 00/CN, the user has to define the mapping between values using the special handling code of UDC 41/L9. That means special handling code of UDC 41/L9 should contains the corresponding country code of UDC 00/CN.
Execute R8976A08 selecting the correct Lots from F4108 by user data selection. For a given record, the value into ORIG field of F4108 has to contain the same country than the value of LRP9 field. |
| R95SQAQ | To convert old saved queries to new enhanced queries. | This is to be run if you use Saved Query. To verify, please check if you have records in F98950 table with field UOTY = "SQ" | Enhanced Query uses a different format than Saved Query to store the queries. This conversion program provides users a way to convert your old saved queries to the new format that Enhanced Query uses. | User can use the PO Template D95SQAQPO to specify any combination of 3 attributes (User ID and/or Application Name and/or Form Name) to filter the old queries to be converted to the new format. Records in F98950 and F98950D are converted during the process. The old SQ records are NOT deleted during the conversion. |
This table lists all the processing options required for the R31P40039 program.
| Processing Options for R31P40039 | |
|---|---|
| Mode | Blank = Final (can be rerun).
1 = Proof. Does not change anything in the database. |
| Manufacturing | |
| Order Type value 01 for Manufacturing Orders | The user-defined code that the user wants to replace Order Type value 01 in the manufacturing orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Manufacturing Orders | The user-defined code that the user wants to replace Order Type value 02 in the manufacturing orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Manufacturing Orders | The user-defined code that the user wants to replace Order Type value 03 in the manufacturing orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Manufacturing Orders | The user-defined code that the user wants to replace Order Type value 04 in the manufacturing orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Manufacturing Orders | The user-defined code that the user wants to replace Order Type value 05 in the manufacturing orders. If no value is entered, the default order type assigned is 01. |
| Manufacturing Rework | |
| Order Type value 01 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 01 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 02 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 03 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 04 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 05 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Equipment | |
| Order Type value 01 for Equipment Orders | The user-defined code that the user wants to replace Order Type value 01 in the equipment orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Equipment Orders | The user-defined code that the user wants to replace Order Type value 02 in the equipment orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Equipment Orders | The user-defined code that the user wants to replace Order Type value 03 in the equipment orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Equipment Orders | The user-defined code that the user wants to replace Order Type value 04 in the equipment orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Equipment Orders | The user-defined code that the user wants to replace Order Type value 05 in the equipment orders. If no value is entered, the default order type assigned is 01. |
| S\WM | |
| Order Type value 01 for Service Orders | The user-defined code that the user wants to replace Order Type value 01 in the service orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Service Orders | The user-defined code that the user wants to replace Order Type value 02 in the service orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Service Orders | The user-defined code that the user wants to replace Order Type value 03 in the service orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Service Orders | The user-defined code that the user wants to replace Order Type value 04 in the service orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Service Orders | The user-defined code that the user wants to replace Order Type value 05 in the service orders. If no value is entered, the default order type assigned is 01. |
| Warranty Claim | |
| Order Type value 01 for Warranty Claim Orders. | The user-defined code that the user wants to replace Order Type value 01 in the warranty claim orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Warranty Claim Orders. | The user-defined code that the user wants to replace Order Type value 02 in the warranty claim orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Warranty Claim Orders. | The user-defined code that the user wants to replace Order Type value 03 in the warranty claim orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Warranty Claim Orders. | The user-defined code that the user wants to replace Order Type value 04 in the warranty claim orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Warranty Claim Orders. | The user-defined code that the user wants to replace Order Type value 05 in the warranty claim orders. If no value is entered, the default order type assigned is 01. |
| Supplier Recovery | |
| Order Type value 01 for Supplier Recovery Orders | The user-defined code that the user wants to replace Order Type value 01 in the supplier recovery orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Supplier Recovery Orders | The user-defined code that the user wants to replace Order Type value 02 in the supplier recovery orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Supplier Recovery Orders | The user-defined code that the user wants to replace Order Type value 03 in the supplier recovery orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Supplier Recovery Orders | The user-defined code that the user wants to replace Order Type value 04 in the supplier recovery orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Supplier Recovery Orders | The user-defined code that the user wants to replace Order Type value 05 in the supplier recovery orders. If no value is entered, the default order type assigned is 01. |
| ECO | |
| Order Type value 01 for Engineering Change Orders | The user-defined code that the user wants to replace Order Type value 01 in the engineering change orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Engineering Change Orders | The user-defined code that the user wants to replace Order Type value 02 in the engineering change orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Engineering Change Orders | The user-defined code that the user wants to replace Order Type value 03 in the engineering change orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Engineering Change Orders | The user-defined code that the user wants to replace Order Type value 04 in the engineering change orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Engineering Change Orders | The user-defined code that the user wants to replace Order Type value 05 in the engineering change orders. If no value is entered, the default order type assigned is 01. |
| ECO Request | |
| Order Type value 01 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 01 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 02 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 03 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 04 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Engineering Change Request Orders | The user-defined code that the user wants to replace Order Type value 05 in the engineering change request orders. If no value is entered, the default order type assigned is 01. |
| Real Estate Management | |
| Order Type value 01 for Real Estate Management Orders | The user-defined code that the user wants to replace Order Type value 01 in the real estate management orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Real Estate Management Orders | The user-defined code that the user wants to replace Order Type value 02 in the real estate management orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Real Estate Management Orders | The user-defined code that the user wants to replace Order Type value 03 in the real estate management orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Real Estate Management Orders | The user-defined code that the user wants to replace Order Type value 04 in the real estate management orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Real Estate Management Orders | The user-defined code that the user wants to replace Order Type value 05 in the real estate management orders. If no value is entered, the default order type assigned is 01. |
| Rate Schedules | |
| Order Type value 01 for Rate Schedule Orders | The user-defined code that the user wants to replace Order Type value 01 in the rate schedule orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for Rate Schedule Orders | The user-defined code that the user wants to replace Order Type value 02 in the rate schedule orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for Rate Schedule Orders | The user-defined code that the user wants to replace Order Type value 03 in the rate schedule orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for Rate Schedule Orders | The user-defined code that the user wants to replace Order Type value 04 in the rate schedule orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for Rate Schedule Orders | The user-defined code that the user wants to replace Order Type value 05 in the rate schedule orders. If no value is entered, the default order type assigned is 01. |
| EPM Order Summary | |
| Order Type value 01 for EPM SummaryOrders | The user-defined code that the user wants to replace Order Type value 01 in the EPM summary orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 02 for EPM Summary Orders | The user-defined code that the user wants to replace Order Type value 02 in the EPM summary orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 03 for EPM Summary Orders | The user-defined code that the user wants to replace Order Type value 03 in the EPM summary orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 04 for EPM Summary Orders | The user-defined code that the user wants to replace Order Type value 04 in the EPM summary orders. If no value is entered, the default order type assigned is 01. |
| Order Type value 05 for EPM Summary Orders | The user-defined code that the user wants to replace Order Type value 05 in the EPM summary orders. If no value is entered, the default order type assigned is 01. |
These section describes these tasks to upgrade E1PAGE from Release 9.0 to Release 9.1:
Section 13.10.3, "Working With Upgrade UGC Objects Using W98E1UGCA"
Section 13.10.4, "Working With Detail Upgrade Using W98E1UGCB"
To upgrade your E1PAGE, you should execute the R98E1UGC post upgrade. This function of this UBE is to move data from previous release to the upgraded release for F952400 table. The list of affected tables affected includes:
F952411
This is the history table for the record moved.
F982400
This table tracks the record as LCM process.
F982402 and F982405
These tables track the upgrade process.
This section describes these tasks:
Below is a list of the required processing options and an example of each:
From Environment
For example, DV900.
From Release
For example: E900.
To Environment
For example, DV910.
To Release
For example, E910.
Object Type
For example, E1PAGE.
Below is a list of the optional processing options and an example of each:
Job Number
For example, the default value is.
UP:USER_ID,Date and time (UP:USERDATETIME)
Report View Mode
Valid values are:
1 - View Only Errors
0 - View All Records
Update Mode
Valid values are:
1 - Proof Mode (Edit Mode for E1PAGE)
0 - Final Mode (APPROVE mode)
Below lists the logic flow for each section of the processing for R98E1UGC.
Processing Section 1
The logic flow of Processing Section 1 is based on Path Code Master table (F00942) with these considerations:
If *ALL is set for all environment in the processing option, the UBE processes all environments but only executes one path code. The F952400 table is a Central Objects table and should only be mapped by path code.
If a specific environment is used, the UBE can determine the path code.
The B98E1UGC business function processes all records in F952400 for the specified path code.
If the target environment F952400 table exists with JDE E1PAGE objects, the BSFN will not overwrite those records from those that exist in the source F952400 table. Therefore, any JDE delivered E1PAGE objects in a previous release are not carried over.
The BSFN creates records in the F952411, F982403, and F982400 tables. In the F982402 table, the header information for the Job Number maps back to the upgrade records in F982403 table.
Processing Section 2
This processing section is based on F982403 table. It reports any records that fail to update.
You can use P98E1UGC to upgrade F952400 objects. Using this program allows users to:
View records that have been successfully upgraded correctly and also to view any records that have issues.
View any errors and their suspected reasons.
Redo the upgrade after the UGC an identified issue has been fixed.
You can use W98E1UGCA to view the header information for the UGC by Job Number.
You can use W98E1UGCB to work with detail upgrades. Using this program allows users to:
View all the records that have been upgraded.
View additional detail on the errors.
After any errors on the objects are fixed, the user can select Upgrade from this form. This allows the upgrade process to execute without re-running the R98E1UGC.