1. Procore To JDE
1.1. 4) Procore: Budget Account Balances
1.1.1. <-
1.1.1.1. JDE: Original Budget
1.2. 6) Procore: Budget Modifications/Budget Changes
1.2.1. <-
1.2.1.1. JDE: Budget Journals
1.3. Procore: Change Events
1.3.1. Not Needed
1.4. Procore: Forecast to complete
1.4.1. <-
1.4.1.1. Not Needed
1.5. 7) Procore: Prime Contract
1.5.1. <-
1.5.1.1. JDE: Contract
1.5.2. Approval
1.5.2.1. Executed Docusign Document
1.5.2.2. Workflow
1.5.2.2.1. CM Creates doc
1.5.2.2.2. Senior CM approves
1.5.2.2.3. Finalized document
1.5.2.2.4. Fields locked for integrated fields
1.5.3. Required Fields
1.5.3.1. JDE team to help define
1.5.4. Unique Key
1.5.4.1. JDE: BU
1.6. 8 ) Procore: Prime Change Orders
1.6.1. <-
1.6.1.1. JDE: Contract CO
1.6.2. Approval
1.6.2.1. Executed Docusign Document
1.6.2.2. Workflow
1.6.2.2.1. CM Creates doc
1.6.2.2.2. Senior CM approves
1.6.2.2.3. Finalized document
1.6.3. Required Fields
1.6.3.1. JDE team to help define
1.6.4. Unique Key
1.6.4.1. JDE BU
1.6.5. Budget is changing as a result of this action
1.7. 9) Procore: Commitments
1.7.1. <-
1.7.1.1. JDE: Purchase Orders
1.7.2. Approval
1.7.2.1. Executed Docusign Document
1.7.2.2. Workflow
1.7.2.2.1. CM Creates doc
1.7.2.2.2. Senior CM approves
1.7.2.2.3. Finalized document
1.7.3. Required Fields
1.7.3.1. JDE team to help define
1.7.4. Unique Key
1.7.4.1. Created by Endpoint
1.8. 10) Procore: Commitment Changes
1.8.1. <-
1.8.1.1. JDE: PO Changes
1.8.2. Approval
1.8.2.1. Executed Docusign Document
1.8.2.2. Workflow
1.8.2.2.1. CM Creates doc
1.8.2.2.2. Senior CM approves
1.8.2.2.3. Finalized document
1.8.3. Required Fields
1.8.3.1. JDE team to help define
1.8.4. Unique Key
1.8.4.1. Commitment number?
2. Takeaways
2.1. Working Groups
2.1.1. 0) Prime Contract, do we need this integration?
2.1.1.1. JDE Team
2.1.1.1.1. Brian
2.1.1.1.2. Kat
2.1.1.1.3. Harish
2.1.1.2. Topics
2.1.1.2.1. Can we associate Prime contract dataset just using JDE only the BU?
2.1.1.2.2. Do we need to develop an integration endpoint for the Prime Contracts?
2.1.2. 1) Direct Cost
2.1.2.1. JDE Team
2.1.2.1.1. Brian
2.1.2.1.2. Kat
2.1.2.1.3. Harish
2.1.2.2. Keith
2.1.2.3. Topics
2.1.2.3.1. Determine how we triage GL to three outcomes
2.1.3. 2) Modern Budget Change Planning Session
2.1.3.1. Modern
2.1.3.1.1. Keith
2.1.3.1.2. Clemente
2.1.3.2. Topics
2.1.3.2.1. Workflows
2.1.3.2.2. Cost Type Definitions
2.1.3.2.3. Change Order Reason Codes
2.1.3.2.4. JD Edwards Behavior
2.1.4. 3) Budget Change Business Rules Definition
2.1.4.1. Procore Consultant
2.1.4.2. GDSO
2.1.4.2.1. Janet
2.1.4.2.2. Akshay
2.1.4.2.3. John D.
2.1.4.2.4. Lucy
2.1.4.3. JDE
2.1.4.3.1. Brian
2.1.4.3.2. Harish
2.1.4.4. Modern
2.1.4.4.1. Keith
2.1.4.4.2. Clemente
2.1.4.5. Topics
2.1.4.5.1. Workflows
2.1.4.5.2. Cost Type Definitions
2.1.4.5.3. Change Order Reason Codes
2.1.5. 4) Budget Change JDE Discovery
2.1.5.1. Modern
2.1.5.1.1. Keith
2.1.5.1.2. Clemente
2.1.5.2. GDSO
2.1.5.2.1. Janet
2.1.5.2.2. Akshay
2.1.5.2.3. John D.
2.1.5.2.4. Lucy
2.1.5.3. JDE Team
2.1.5.3.1. Brian
2.1.5.3.2. Kat
2.1.5.3.3. Harish
3. Scoped Out
3.1. Owner Pay Applications
4. JDE To Procore
4.1. 1) JDE: Address Book
4.1.1. ->
4.1.1.1. Procore: Vendor
4.2. 2) JDE: Job
4.2.1. ->
4.2.1.1. Procore: Project
4.3. 3) JDE: Account Master
4.3.1. ->
4.3.1.1. Procore: Costcodes
4.4. 5) JDE: Non-Committed AP costs (Invoice)
4.4.1. ->
4.4.1.1. Procore: Direct Cost Invoices
4.4.2. Required Fields
4.4.2.1. Non contract invoice
4.4.2.2. Invoice number required
4.4.2.3. Vendor required
4.4.2.4. Can't be made the same day.
4.5. 5) JDE: Payroll (Aggregated)
4.5.1. ->
4.5.1.1. Procore: Direct Cost Payroll
4.5.1.2. Required Field
4.6. 5) JDE: Miscellaneous GL Costs (Expense)
4.6.1. ->
4.6.1.1. Procore: Direct Cost Expenses
4.6.2. Required Fields
4.7. (Dependent on Prime contract and commitment endpoints) JDE: AP Vouchers
4.7.1. ->
4.7.1.1. Payment Requisitions
4.7.2. (Creates invoice/default fields), select existing line item, to update record.
4.8. (Dependent on Prime contract and commitment endpoints) JDE: AP Payments
4.8.1. ->
4.8.1.1. Payments