Upgrading from XE \ ERP 8.0
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, DV920) 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. |
R8931CTSX |
To convert CTS1, CTS2, CTS3, and CTS9 (collectively referred to as CTSx) data item values from 2 display decimals to match the display decimals of the TRQT data item (4 decimals). |
You must run this program to increase the decimal precision of the CTSx data items if you use these data items to store unaccounted units. |
The R8931CTSX table conversion program retrieves the TRQT data dictionary display decimals and converts the values of the CTSx data items in all affected tables to match the TRQT display decimals. The R8931CTSX program calls the Data Decimal Conversion business function (B8900010) for each CTSx data item. The UBE locates all tables containing the data item and selects non-zero values for conversion. The program converts the CTSx value and updates the table. |
The default setting of the CTSx data items to 2 display decimals may cause rounding discrepancies. Therefore, Oracle recommends that you run this table conversion program to increase the decimal precision of the CTSx data items. After running the R8931CTSX program, change the display decimal setting of the CTSx data items in the E920 data dictionary to 4 to match the display decimal setting of the TRQT data item. For more information, refer to the Data Conversion Updates for Decimal Precision of Unaccounted Units document (2438553.1) on My Oracle Support:
|