WORK ORDERS VALIDATION (JD EDWARDS)#

The system provides a Work Order Validation from Personality directly to the JD Edwards Financials data base. The JD Edwards Financials Database contains an Oracle Table F4801 that is used for editing from Personality to JD Edwards. The JD Edwards Work Order Validation will directly validate the Work Order Number from the JD Edwards Financials Data Base at the time the transactions are being entered to reduce errors. Personality invokes the JD Edwards Work Order Validation when the GL Company from IDGC screen is marked with a ‘Work Order Validation’ of ‘JD Edwards Financials’. The One Year previous rule is a rule that looks back 365 days prior to the leave line being evaluated to check the amount available for the employee to take in the current period. The accrual end date is the end of the pay period being evaluated and the accrual start date is 365 days prior to the end date. The system will look at all leave lines taken in the 365 day period and check to see what the hours are compared to the accrual defined in the Service levels tab if there is time available the employee will be able to take the time otherwise it will go to LWOP.

Connection to JD Edwards Financials Data Base#

A one time set up for the Database Link MUST be established by the DBA at the client site to the JD Edwards Financials data base from the current P2K database. If this Database Link is already set up for the GL Interface, then there is no need to repeat this set up.

In SQL+, the DBA will connect to the P2K database and then create the database link from the current P2K data base to the JD Edwards Financials data base as follows:

SQL> drop public database link jde_financials; SQL> create public database link jde_financials connect to USERNAME identified by USERPASSWORD using ‘DBALIAS’;

where USERNAME - is a database level user in the JD Edwards Financial system with proper permission , e.g. gluser USERPASSWORD - is the password for the above username, e.g. p2kpass DBALIAS - is the database alias for the JD Edwards financial system - the JD Edwards financials database alias must be in the TNSNAMES.ora file in the database’s ORACLE_HOME\NETWORK\ADMIN directory For example: In SQL+, the DBA will first connect to P2K database, then use the following command: > create public database link jde_financials connect to gluser identified by p2kpass using 'JDEFin' where ‘JDEFin’ is the jde_financials data base that contains Oracle Tables F4801

After the Database Link has been established, the DBA should test to ensure the JD Edwards Financials Tables are available for P2K as follows: In SQL+, connect to P2K database, check the following JD Edwards Financials Tables:

SQL>SELECT count(*) FROM F4801@jde_financials; This ‘SELECT’ statement should return the number of records in this F4801 Table.

Potential Errors to avoid#

1. On IDGC screen, the ‘Work Order Validation’ must be ‘JD Edwards Financials’ for the GL Company. 2. The user may encounter the following error: ‘ORA-00942 – table or view does not exist’ - this error occurs when the Database link is not established properly or the Table does not exist in the JD Edwards Financials data base, please check database link and the JD Edwards Financials database Tables to ensure all Tables exist - the actual name of the JD Edwards Financials Table may need to be referenced by the username, e.g. gluser.F4801, if this is the case, the DBA need to create a public synonym in the JD Edwards Financials Table for the Table.

JD Edwards Financials Data Base Work Order Table – F4801#

From F4801 Table, the following Column Names are used for validation:

WADOCO number - Work Order WASRST char(2) - Work Order Status

Personality GL Company Set up – IDGC Screen#

The Work Order Validation must be ‘JD Edwards Validation’ for the G/L Company.

How Personality validate Work Order in JD Edwards Database#

WADCTOWADOCOWALNIDWAPTWOWAPARSWATYPSWADL01WASRST
WO1300000000128RRebels Ticket Operations60
WO1310000000128RLounge Operations Rebels60
WO1320000000128RField Operations set up/down60
WO1330000000128Rper service pac2060
WO1340000000133Rrepair of waterline60
WO1350000000133Rrepair concrete sidewalk panel60
WO1290000000128RConcession Rebels Ftbl60
WO1190000000115RRepairs to Sidewalk60
WO1200000000120RParks TestWO – Turf Mowing60
WO1210000000121RParks TestWO – turf trimming60
WO1220000000107RRoadside60
WO1230000000123R5,000K LD PM90
WO1240000000124R10,000K LD PM 80
WO1250000000125RCHANGE ZAMBONI BLADE60
WO1260000000126R5,000K LD PM 80
WO1270000000127RRebels Football90
WO1280000000128RRebels Football60
WO1180000000115RReplacement of Traffic Control99
WO1080000000108RRoadside#260
WO1090000000109RPothole Patching 60
WO1100000000110RRepair Street Light - Glanford60
WO1110000000111RBudget Testing60
WO1120000000112RThird Party Work60
WO1130000000112RRepair of Waterline99
WO1140000000112RRepair of Concrete Sidewalk99

In order to validate between the 2 systems, P2K uses an Oracle SELECT statement to read the JD Edwards Financial F4801 table and do an exact match to the Work Order Number. The Work Order Number must be Active in order to be valid. Active Work Order Numbers are with WASRST = ‘60’.

Personality SELECT Statement to JD Edwards Database#

The following SELECT statement is used to retrieve Work Order Number from the JD Edwards Financials database:

SELECT * FROM F4801@jde_financials WHERE WADOCO = 130 AND WASRST IN (60);

The above SELECT statement validate the Work Order Number: 130. The user can replace the Work Order Number: 130 with other Work Order Number to test, e.g. 120.

Personality Programs that invoked JD Edwards Work Orders logic#

TRANSACTION ENTRY TIME At transaction entry time (IPTR, IPPH etc), whenever a Work Order Number is entered, the Work Order is validated from the JD Edwards Financials data base Table F4801.

Personality GL Interface File with JD Edwards Work Order Number#

The Work Order Number for each Transaction is required to be sent to the JD Edwards Financials system. To do this, the user need to set up IDIF screen Record 50 for the Work Order field.

Notes#

Click to create a new notes page