Integrated Fields

The integration of MYOB Purchase Orders to Framework ECM is fixed in the content that is exchanged between the systems. There are no user-configurable integrated fields available for this type of integration.

Database Models

The following database model(s) displays the manner in which data is integrated between the third party application and Framework Integration.

Integration Process

The following information is a low level account of the integration process including criteria, decisions, and outcomes. This information is technical in nature and is provided "as-is" for a detailed analysis of the integration process for system administrators.

1. Read profile keys to determine which actions to process.
2. Process Cost Centres
   1. Check “CostCentreCodeSource” profile key to decide if “CostCentres” or “Accounts” are used for Cost Centre integration
   2. Read all eligible records from Framework table int_cCentre where
      1. Int_cCentre.l_link_sys_gl_id = -2273 (MYOB)
      2. Int_cCentre.l_context_id = ‘Context’ (profile key)
      3. Int_cCentre.l_Int_cCentre_id <> 0
   3. or each record get matching MYOB record where, depending on what was established in item i,
      1. CostCentres.CostCentreID = Int_cCentre.s_link_cCentre or
      2. Accounts. AccountNumber = Int_cCentre.s_link_cCentre
   4. Update the Int_cCentre.s_link_name field
3. Process Suppliers
   1. Read all eligible records from Framework table int_entity where
   2. Int_entity.l_int_entity_id <> 0
   3. For each record get matching MYOB record in table Suppliers where Suppliers.CardRecordID = int_entity.s_link_entity
   4. Update int_entity.s_link_name and int_entity.s_link_reference fields
   5. If modified, update Entity/Address/Telephone details for the Supplier
4. Process Purchase Orders
   1. Get eligible Framework jobs from v_sched_dbJobOrders where
      1. Job.s_link_boq <> ‘N/A’
      2. Job.l_context_id = ‘Context’ (profile key, if 0 all contexts)
      3. Job.l_wfl_stgMajor_id = -4 (Construction) or job.l_wfl_stgMajor_id = -3 (Administration) and job.l_wfl_stgMinor_id = -18 (Maintenance) or job.l_wfl_stgMinor_id = -19 (Service)
      4. and apply order criteria where OrderCriteria is
         1. 2 – Construction Manager • Cst.l_mgr_e_id = ‘OrderCriteriaID’
         2. 3 – Supervisor • Cst.l_super_e_id = ‘OrderCriteriaID’
         3. 4 – Single Job • job.s_job_num = ‘OrderCriteriaID’
   2. For each job get orders and items from MYOB tables Purchases, PurchaseLines, Suppliers, CostCentres, Accounts, ItemPurchaseLines and Items where
      1. PurchaseLines.JobID = job.s_job_num (job.s_link_boq is used instead if not empty)
      2. Purchases.PurchaseStatusID = 'OR'
      3. Purchases.OrderStatusID <> 'T'
      4. Purchases.PurchaseDate >= ‘StartIntegrationDate’ – 7 days
      5. Purchases.PurchaseDate <= ‘EndIntegrationDate’ or now if endIntegrationDate is none.
   3. Once we have the MYOB Order, see if it exists in po_order table where
      1. Po_order.s_jobNo = PurchaseLines.JobID
      2. Po_order.CostCentreID = CostCentres.CostCentreID (or Accounts. AccountID)
   4. iv. And we check each MYOB Order Item, by seeing if it exists in po_item table where
      1. Po_item.l_link_item = PurchaseLines.PurchaseLineID
   5. Orders and items are updated or added.
   6. After all items have been processed, a list of unmatched purchase orders is produced, aimed at their manual deletion in MYOB. This mostly applies to potential superseded work orders, which do not exist in Framework any more.
   7. At the end of integration MYOB orders are checked to see if there are any missing (manually removed from MYOB), which need to be cancelled in Framework.