Versions Compared

Version Old Version 2 New Version Current
Changes made by

Matthew Garrett

Matthew Garrett

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
FWINT HEAD
FWINT HEAD
nopaneltrue

Return to MYOB Accounts Receivable Integration
Article Index

Table of Contents

Integrated Fields

The integration of MYOB Accounts Receivable to Framework ECM is of MYOB Accounts Receivable 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 and Framework Integration.Image Removed

...


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. ActionCreateInvoices

    1. Get eligible Framework jobs using v_FWINT_Invoices where

      1. cst_claim.s_invoice_num > 0 and its length < 8 characters

      2. cst_claim.s_link_accts <> ‘N/A’

      3. cst_claim.f_link_exported <> -1

      4. client.s_link_accts <> ‘N/A’

      5. Job. l_job_status_gl_id = -7 (Active) or -10 (On Hold) or l_job_status_gl_id = -946 (Pending Cancellation) or -8 (Cancelled) and d_cont_cancelled >= (today - 14 days)

      6. and apply Criteria Method criteria where CriteriaMethod is

      7. Single Region Division • job.l_context_id = ‘CriteriaMethodID’

      8. Single Job • job.s_job_num = ‘CriteriaMethodID’

      9. Single Team • job.l_team_id = ‘CriteriaMethodID’

      10. All Jobs • job.l_job_id <> 0

      11. Accounts Entity • job.l_accounts_e_id = ‘CriteriaMethodID’

    2. The MYOB table Jobs is checked for a matching Job Number where Jobs.JobNumber = ‘job.s_link_boq’, or if the s_link_boq field is empty then the match is done on Jobs.JobNumber = ‘job.s_job_num’

    3. If the job is found then a new record is added to the temporary Import_Service_Sales table, from where MYOB Sales, SaleLines and ServiceSaleLines tables are updated via an internal MYOB process

    4. The Framework cst_claim is updated so that…

      1. cstClaim.f_link_exported is set to true

      2. cstClaim.s_link_accts is set to Sales.SaleID

  3. ActionProcessReceipts

    1. Eligible receipts are read from MYOB Sales, SaleLines, CustomerPayments and CustomerPaymentLines tables where

      1. if profile key DepositRunEndDate is empty then CustomerPayments.TransactionDate > = ‘DepositRunStartDate’ and <= now, else if DepositRunEndDate has a date entered then

      2. CustomerPayments.TransactionDate > = ‘DepositRunStartDate’ and <= ‘DepositRunEndDate’

    2. Additionally, if Sales.TotalCredits > 0, then MYOB SettledCredits and SettledCreditLines tables are also read where

      1. if profile key DepositRunEndDate is empty then SettledCredits.TransactionDate > = ‘DepositRunStartDate’ and <= now, else if DepositRunEndDate has a date entered then

      2. SettledCredits.TransactionDate > = ‘DepositRunStartDate’ and <= ‘DepositRunEndDate’

    3. If MYOB record exists we

      1. Make sure the receipt does not exist in the cont_pay table where cont_pay.s_link_accts = CustomerPaymentLines. CustomerPaymentLineID (alternatively SettledCreditLines. SettledCreditLineID)

      2. if the payment does not exist then we can create it. First get the Framework job where job.s_job_num = SaleLines.JobID

      3. Then Insert the new cont_pay receipt record and update cst_claim.

    4. After processing receipts the profile key depositRunStartDate is updated.

  4. ActionCheckingConsistency

    1. Eligible Framework jobs for checking are retrieved from v_FWINT_ConsistencyByJob or v_FWINT_ConsistencyByInvoice, depending on profile setting, where

      1. If Check Consistency Level is claim by claim

        1. Job.l_wfl_stgMajor_id is checked against profile settings in the possible range of -5 to -2 (Pre-Administration, Administration, Construction, Maintenance)

        2. Job. l_job_status_gl_id = -7 (Active) or -10 (On Hold) or l_job_status_gl_id = -946 (Pending Cancellation)

        3. job.s_link_accts <> ‘N/A’

        4. Cst_claim.s_invoice_num is not empty

      2. If Check Consistency Level is job by job

        1. Job.l_wfl_stgMajor_id is checked against profile settings in the possible range of -5 to -2 (Pre-Administration, Administration, Construction, Maintenance)

        2. Job. l_job_status_gl_id = -7 (Active) or -10 (On Hold) ) or l_job_status_gl_id = -946 (Pending Cancellation)

        3. job.s_link_accts <> ‘N/A’

      1. apply Criteria Method criteria where CriteriaMethod is

        1. Single Region Division • job.l_context_id = ‘CriteriaMethodID’

        2. Single Job • job.s_job_num = ‘CriteriaMethodID’

        3. Single Team • job.l_team_id = ‘CriteriaMethodID’

        4. All Jobs • job.l_job_id <> 0

        5. Accounts Entity • job.l_accounts_e_id =‘CriteriaMethodID’

    2. Invoice Totals are compared between MYOB and Framework:

      1. If Check Consistency Level is Claim by Claim

        1. Cst_claims with the same invoice numbers have their cst_claim.c_total field values summed together

        2. The matching invoice is retrieved from transactions where Sales.SaleID = cst_claim.s_link_accts

        3. If the invoice record is found the Sales.(TotalLines + TotalTax) is compared with the total of the cst_claim.c_total fields we calculated previously, to determine if the invoice totals match.

      1. If Check Consistency Level is Job by Job

        1. All eligible claims for the job are read and the sum of cst_claim.c_total is determined

        2. The sum is compared to MYOB Sales.(TotalLines + TotalTax)

    3. Receipt Totals for each invoice or job are compared between MYOB and Framework

      1. If Check Consistency Level is Claim by Claim

        1. Cst_claims with the same invoice numbers have their cst_claim.c_paid_amt field values summed together

        2. The matching receipts are retrieved from transactions where Sales.SaleID = cst_claim.s_link_accts

        3. If there are receipts then the sum of Sales.(TotalPaid + TotalCredits) is calculated and compared with the total of the cst_claim.c_paid_amt fields we calculated previously, to determine if the receipts match.

      1. If Check Consistency Level is Job by Job

        1. The Framework Payments are summed together, the sum of c_pay from cont_pay is added up. Then because some cst_claims can indicate a refund we have to sum any cst_claims for the job where the c_paid_amt < 0 and remove this amount from the total payments.

        2. The matching receipts are retrieved from transactions where Sales.SaleID = cst_claim.s_link_accts

        3. If there are receipts then the sum of Sales.(TotalPaid + TotalCredits) is calculated and compared with the total of the Framework payments, to determine if the receipts match.