Morpheus Integration between JDE & Prolog

Transcription

1 Morpheus Integration between JDE & Prolog

2 Data Bridge Projects JDE Prolog Companies/Addresses JDE Prolog Budget Codes JDE Prolog Original Budgets JDE Prolog Contracts / PO JDE Prolog Subcontract CO (SCO s) JDE Prolog Budget Revisions JDE Prolog UNIDIRECTIONAL 2

3 Synchronization Schedules Projects Companies/Addresses Budget Codes Original Budgets Contracts / PO Subcontract CO (SCO s) Budget Revisions Midnight Daily Midnight Daily Top of the hour Top of the hour Top of the hour Top of the hour Disabled 3

4 Projects 5

5 Projects Select Job Master Inquiry 6

6 Projects Enter the JDE job number in the QBE Line and click Find. The Prolog Integration Field can be found in the Inquiry. If it is not completed as it should be, send an to JDESETUP. 7

7 Projects The Integration requires that Category Code 21 (Prolog Integration) = Y and the Job Type = JB or JC. After the integration is complete, a post integration script will change the Y to a P in JDE. 8

8 Projects The Project is created in the Prolog Database of the Company on the Project/Job. Sub Jobs are created as part of the Account. Jobs are not separate records in Prolog (as they are in JDE). IT will grant access to users once the Project is setup. 9

9 Companies & Addresses 10

10 Companies & Addresses Select Job Address Information 11

11 Companies & Addresses Change the Search Type to C, O, V, or PO. Use an asterisk (*) to search all Types. Enter the JDE vendor number and search. After it s found, select it. 12

12 Companies & Addresses Make sure the company has the proper EIN Federal Tax Id from the W-9 13

13 Companies & Addresses The Integration requires that Category Code 10 (Prolog Vendor) = Y and the Search Type = C, O, V, PO. The Federal Tax ID also needs to be in the proper (XX-XXXXXXX) format. After the integration is complete, a post integration script will change the Y to a P in JDE. 14

14 Companies & Addresses After Integration, a script will auto-populate the Prolog Company ID in JDE. This will make the Prolog Company ID unique. You do not need to fill this out. 15

15 Companies & Addresses After Integration, the JDE Vendor No. and Fed Tax ID will show up in Prolog. Only Project Controllers or FOC s are able to modify the JDE Number field 16

16 Budget Codes and Original Budgets 17

17 Budget Codes and Original Budgets Select Set up Accounts on Job Master 18

18 Budget Codes and Original Budgets Enter job number in the Header and click Find. The Integration requires a Level of Detail > 7 and PE column is blank. Original Budgets will integrate in a separate transaction 19

19 Budget Codes and Original Budgets After synchronization the records can be displayed in the Prolog Budget module. Notice the integration concatenates the Level 7 trade description along with the Level 9 cost type. Confirm that all Budget Codes and Original Budgets transferred accurately. Failures can occur if the values are not available in the Prolog Budget list groups. Note: When modifying Original Budgets, please make changes in JDE and have them synchronized over to Prolog. Original Budgets in Prolog will be overwritten at the next synchronization cycle. 20

20 Segregation of Duties To comply with SOX, Segregation of Duties must exist. This means Operations can not push a record to JDE without Accounting performing their due diligence. Therefore, only Project Controllers or FOCs will have access to change the Posting Status field. This applies to all Subcontracts, Purchase Orders, and Change Orders. 21

21 Subcontracts and Purchase Orders Integration requires that the Approved for Budget box is checked. Type of Contract corresponds to the following JDE Order Types: SA = OS S2 = O2 P2 = OJ P3 = OM 22

22 Subcontracts and Purchase Orders The Remarks field in Prolog corresponds to the Payment Remark field in the JDE Order Header. This field prints on the check to the vendor when a voucher is entered through the Order. 23

23 Subcontracts and Purchase Orders Make sure the date Issued to Sub is in the current Accounting period. This will flow into the G/L Date of the Order Detail Lines & cause an error if in the wrong period. Retention Percentage is also integrated into JDE. 24

24 Subcontracts and Purchase Orders Confirm Schedule of Values and Budget Codes are correct prior to integration. Order will have the Project Number in the Order Header, but the Budget Code determines what Job & Account the Order Detail Line is coded to. Integration is Unidirectional, so changes after original synchronization will require manual modification in BOTH systems. 25

25 Subcontracts and Purchase Orders Make sure the Main Contact s Location has a valid JDE Number associated with it. 26

26 Subcontracts and Purchase Orders Project Controller marks Posting Status = Approved. Integration Status will confirm Success or Failed with an explanation and time stamp in the Integration Message. If the Integration fails, make necessary changes, clear the Integration Status, Integration Message, and Contract Reference fields. 27

27 Subcontracts and Purchase Orders Select the Doc Type associated with your Subcontract or Purchase Order 28

28 Subcontracts and Purchase Orders Enter your Order Number from the Prolog Contract Reference field in the QBE field and click Find. Once found select the Row Exit and Financial Status. Verify your Order integrated correctly. Notice the Reference Field is populated with the Prolog Contract Number and the Ordered By field is PROLOGMTG. 29

29 Subcontract Change Orders Integration requires the Approved for Budget box is checked on the PCO. Cost Allocation = Apprv Cmmt for the PCO line item. This status changes with the SCO is created. 30

30 Subcontract Change Orders Link the PCO line item to the SCO in Prolog. Ensure the Approved for Budget box is checked. Set NTP date in the current Accounting Period. 31

31 Subcontract Change Orders Quick Jump to the Subcontract to see the JDE Doc Type and Order Number for this SCO. 32

32 Subcontract Change Orders Make sure the Main Contact s Location has a valid JDE Number associated with it. 33

33 Subcontract Change Orders Project Controller marks Posting Status = Approved. Integration Status will confirm Success or Failed with an explanation and time stamp in the Integration Message. If the Integration fails, make necessary changes, clear the Integration Status and Integration Message fields. 34

34 Subcontract Change Orders Select the Doc Type associated with your Subcontract or Purchase Order 35

35 Subcontract Change Orders Enter your Order Number from the Prolog Contract Reference field in the QBE field and click Find. Once found select the Row Exit and Financial Status. Verify your Order integrated correctly. Notice the Reference Field is populated with the Prolog Contract Number and the Ordered By field is PROLOGMTG. 36

36 Common Errors All steps in the process must be successful for the later process in the integration to be successful. For example, Company needs to be integrated before it can be used in Orders. Orders must integrate before SCO s can be written. Integration Message errors usually mimic the associated JDE error for the same problem. ( PEC Does Not Allow Entry means the Posting Edit on the Account is not blank). Custom Integration Messages include Valid Supplier Number failed which means that the Supplier Number on the SCO is different than the Supplier Number on the Order. Disagreement or problems with the JDE Number field in the Company Setup versus the Location of the Main Contact on the Contract (see Slides #26 & 33). Dates in Current Accounting Period. JDE Fields not populated correctly. Manual completion of Integration Status or Integration Message fields. 37