About Wisdom of Solomon

Wisdom of Solomon is a blog by Jeff Trotman.  The name comes from the fact that many of the posts contain technical information about Microsoft Dynamics SL, an accounting system formerly known (and still commonly referred to as) Solomon.

Jeff does business as Westglenn Software, and can help with just about any project involving Dynamics SL.

Update: Jeff/Westglenn is no longer working with Dynamics SL. The articles have been left up in case they help anyone but aren’t being updated any more.

Jeff is a Microsoft Certified Professional (MCP) with over 30 certifications, a Microsoft Certified Trainer (MCT) and has lots of experience with:

  • Installing and Configuring SL
  • SQL Server and how it needs to be configured to work with SQL
  • Customization Manager
  • Crystal Reports
  • SQL Server Reporting Services (SSRS)
  • FRx
  • SL Financial modules
  • SL Project modules
  • SL Distribution modules
  • Business Portal (and SharePoint)
  • SL SDK (formerly known as VB Tools, the SDK allows you to write new screens that look and act just like other SL screens, as opposed to Customization Manager which lets you make changes to existing screens)

Here are some examples of things Jeff has done with Dynamics SL:

  • Alternative for Order Management written using VB Tools. When version 4 of Solomon was released, the old order entry module (Order Processing) was discontinued and replaced with the current Order Management module, which had many more features, but was much more complicated. For people that just wanted the old feature set to run in the new (at the time) 32-bit environment, Jeff wrote a new module that worked just like the old one.
  • Industry specific light manufacturing module. A client in the lumber business had specific manufacturing issues related to cutting boards into tongue-and-groove flooring.  Jeff wrote a custom module that handled the inventory transactions and gave them the custom yield reporting they needed.
  • Custom Business Portal entities. To use Business Portal’s querying capability, an “entity” must be written to connect to the table in the database.  For standard SL tables, the entities come with Business Portal, but if you have custom tables in your SL database and want to query them through BP, custom entities must be written.
  • Customized Business Portal’s Reporting Interface. Client wanted users to have a different interface for entering report parameters so the existing webpage was changed using VBScript and custom Web Services.  Also created custom SharePoint webpart to let users see just their own report requests.
  • Automated imports into SL using Object Model. The Object Model is COM-wrapper around the SL screens that lets programmers “drive” data entry into SL similar to how an Excel macro can automate steps in Excel.  Using the Object Model (as opposed to importing directly into SQL tables) guarantees that all SL business logic is enforced.
  • Custom billing programs. Clients have had need for specific ways to feed billing (both using Flexible Billings in the Project series, and straight into AR) so custom screens and processes were written using the SDK.
  • Integrating Dynamics SL to Dynamics CRM. Automated synchronization of SL customers to CRM accounts and SL Projects/Tasks to CRM cases.

Advertisements
  1. jslim180
    June 16, 2011 at 3:13 pm

    Hi Jeff, I have a write-up of something my company needs to do in Solomon. I hope you don’t mind if I present this here, I did not see a related post about this. If you would have a look, maybe something will jump out. This would really complete the next piece to this puzzle. This is really just a simple question, I included all of the details.

    -Thanks,
    Jimmy


    Our Solomon company represents a Health Center. The health center
    contracts with one or more pharmacies to dispense drugs owned by the
    center. The pharmacy receives a dispensing fee, and collects a payment
    from the patient and possibly from third-party insurance.

    We are wondering how to classify the pharmacy. Is it a Vendor or a
    Customer?

    Normally a pharmacy would collect all payments and send the Net of the
    Sales Collections less the dispensing fee to the center. The problem is
    that some patients may be subsidized by the center. If a patient has no
    insurance and their payment is less than the dispensing fee, then the
    net for that transaction is negative. In any period we don’t know if
    the center going to collect or pay money, as it depends on the mix of
    patients that go to the pharmacy during that time.

    AS A VENDOR

    The pharmacy may be a Vendor because they are providing a service to the
    Health Center. We will use Credit Vouchers and Debit Vouchers. Some vendors are sending us checks to pay those Debit Vouchers.

    When sending the Debit Voucher, we run the Payment Selection which creates Zero Check entries leaving just a balance of what is owed by the pharmacy. Next, how do we apply the check when it is received? The voucher is paid and the GL will not tie the entry to a specific vendor.

    AS A CUSTOMER

    What is the best way to handle a customer with a surplus of
    credit memos? If any one of these would work, we would be in good shape:

    Print Checks – Not an option because Solomon checks require payment to a
    Vendor in the payables module. This is a Customer in the Receivables
    module. Making a second entity, a vendor, will fragment the account and mess up all reports.

    Adjustment – What about issuing the check from outside of Solomon then
    make a GL entry? The problem here is that we would have un-applied
    credit memos. Also, there is no way to apply the GL entry to the correct customer. It is a account/company wide adjustment.

    Credit Write-off – We are not actually needing a ‘write it off’ … So, Brace yourself, this sounds like nails on a chalk board. Instead, this function would use the Small Balance/Credit Write Off to move the credit memo into Cash (pharmacies check arrives). I guess this would apply the credit memos update the customer’s balance, it sounds all wrong though.

    Something Else – …

    • June 16, 2011 at 4:02 pm

      Jimmy,

      I feel your pain. As you are already aware, SL just isn’t very good at receiving payments and cutting checks to the same entity and keeping a good running balance between the vendor and customer records.

      Just to make things worse, if they are using Cash Manager – there’s yet another complication. If you do any AR/AP documents that hit the GL acct/sub combination that has been deemed a “Cash Account”, Cash Manager only considers AR Payments and AP Checks in calculating the Cash Manager account balance, so your Cash Manager module’s opinion of the account balance won’t match GL’s opinion of the account balance.

      I don’t think you are going to be able to handle this situation without having a customer and a vendor record for each pharmacy and doing some custom reporting to tie them together. (I know that’s not the answer you’re looking for.) I’ve had to do something like this for a client and after the fact, I wondered if setting up a Project in Project Controller would have helped. I haven’t really thought that through, but the fact that AP and AR can hit Project made me think maybe there was something there.

      Also – I’d take a look at this – http://www.isissoftware.com/enha/isis_sl_apar_refunds.aspx. I don’t know anything about it and have never used it (so this isn’t an endorsement), but I remembered seeing it at a Convergence exhibit or something like that.

      Good luck.
      JT

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: