Sage 500 ERP v7.4 Invoice Overpayments – Continued


It was not my original intention to have a continuation on the original blog which you can see at  http://joenoll.rklesolutions.com/2012/01/04/sage-500-erp-v7-4-invoice-overpayments, however my good friend Richard Sisk at Sage provided some follow-up on the original post that provide additional insight into this new process. I thought I needed to follow-up on this new found information to complete my prior posting. This is great information. Thank you Rick!

In the original post I closed out by saying it would be nice to be able to post a second payment against the same invoice even though the balance was already < 0. It turns out this does exist it just did not work as I thought it would so I missed it. I apologize for the oversight but in this post I detail this newfound information for you.

I have entered another payment from Aldebrn for $150. I am applying this payment to against an invoice that has a current balance of $0. This brings the new balance to –$150.

image

Now I register and post this batch. This makes this record permanent. My next step is to create another batch with a another payment for Aldebrn of $135, as shown below. As you can see by entering in the Invoice No 1113 and then pressing the Tab key key it retrieves the invoice information showing the current balance of –$150. I then key in the Payment Applied of $135 as mentioned by Richard Sisk and it now brings the value of the new balance to –$285.

image

So I stand corrected in my comment in my original post. It appears that Sage has accommodated for this possibility!

How is this being treated in the database is quite interesting and simplistic. You can see this with some simple selects as shown below. The TranNo and the corresponding keys are based on the values from my demonstration and would most likely be different in your system.

   1: -- Invoice Header information

   2: SELECT InvcKey, TranID, TranDate, CompanyID,

   3:        TranAmt, Balance

   4: FROM tarInvoice

   5: WHERE tranno like '%1113%';

   6:  

   7: -- Invoice Header Application information

   8: SELECT ApplyToInvcKey, PostDate, PmtAmt, ApplyFromPmtKey, ApplyFromTranID

   9: FROM tarInvoiceAppl

  10: WHERE ApplyToInvcKey = 1307;

  11:  

  12: -- Customer Payment Header

  13: SELECT CustPmtKey, BatchKey, PmtRcptDate, 

  14:     PostDate, TranID, TranAmt, UnappliedAmt

  15: FROM tarCustPmt

  16: WHERE CustPmtKey IN (515, 516, 517);

  17:  

  18: -- Customer Payment Application

  19: SELECT CustPmtKey, ApplyToInvcKey, ApplyToTranDate, ApplyToTranID,

  20:         PmtAmt

  21: FROM tarCustPmtAppl

  22: WHERE CustPmtKey IN (515, 516, 517);

 

 

 

Results of above Select statements in order of the selects.

image

I recommend that you read up on this functionality in more detail and experiment with it in a test environment of your own. It is a very useful enhancement. Thank you Sage!

Advertisements

New Folder Compare Utility in Sage 500 ERP


Let me start by saying I am quite pleased with the new brand name for what was previously referred to as Sage ERP MAS 500, or Sage MAS 500 or Best Enterprise or Acuity depending on how long you have been around. I would say that we were faired quite well in the rebranding process in maintaining our prior identity.

Sorry, I digress now let me get back to the topic of this blog post. In version Sage 500 ERP 7.40.1, which is the August 2011 PU, I found a nice surprise. A new utility called Folder Compare. After much poking and prodding around the Folder Compare I reached out to my friend Linda Cade for a little clarification on a few things. She quickly provided me with the missing component. I knew she was the right person for the question. If you do not know Linda you can check her blog out at http://sageerpmas500users.wordpress.com/.

So why was I so excited about this Folder Compare utility you might ask. It may seem strange since we have been using WinDiff and Beyond Compare for so many years to do this very thing. However it is quite nice to just have this functionality built right in and available at the client site.

The Sage 500 ERP Folder Compare utility can be found in the following folder “C:\Program Files (x86)\Sage Software\Sage MAS 500 Client\Managed Applications”. This folder may vary based on where you installed the Sage 500 ERP Client. The Application is Accounting.Application.CS.FolderCompare. There are 2 files with this name: one is the XML application.config file, the other one is the actual application EXE.

Today I downloaded Sage 500 ERP v7.4.2 the December 2011 PU. Before I installed this PU I ran the Folder Compare utility to Create Comparison File. This process will create an XML file of the current Sage 500 ERP Client folder.

I created a folder structure to preserve these files for future use. You can see my structure below. This is not necessary just personal preference.

In a network scenario you may wish to create a folder share similar to what you might do with your shared reports as described in the Sage KB article called “How to configure reports to run from a shared location.” It is Resolution ID 2562. This will allow you to compare your clients from one central source.

When you open the Folder Compare utility it defaults to the Client folder. You can simply click the Create Comparison File button which will ask you where to save the file and what to call it. I just used the default name it generated and placed it in my v741 folder that I created above.

Now that you have created the base file you can exit Folder Compare and install the 7.40.2 product update. Once that is completed you once again run the Folder Compare utility. Now create another comparison file of the Client folder. This file I am not placing in my v742 folder.

Now we select the Base file, in this case is the first one I created in the v741 folder and the Comparison file found in the v742 folder. Once you have your files selected click on the Comparison tab and click on the Compare files button.

The results of the comparison will return. I have changed my View Settings below to only show the modified items. You can compare this to the accompanying PDF Sage provides with each update if you wish to dig into the components for further understanding.

In the Options menu you can also put your name, email address and the sage support email address. This information will be the defaults if you decide email the comparison file to support for any reason. As you can see this will require a Case Number. Beware though it appears to email it in the background so it assumes you have the correct information in the Options settings.

I hope you found this useful. I know Sage has some documentation on this but I have not seen it anywhere in the client folder.

How do I verify that Sage ERP MAS 500 v7.3 is Compliant?


You can go to the https://www.pcisecuritystandards.org/approved_companies_providers/vpa_agreement.php web page and find that Sage ERP MAS 500 version 7.3 is PA-DSS compliant.  

You then need to prove to the auditors that Sage ERP MAS 500 was implemented in accordance with our PA-DSS Implementation Guide: http://community.sagemas.com/t5/Installation-and-Technical/PA-DSS-Implementation-Guide-for-v7-3-Credit-Card-Processing/td-p/16235

This is all the proof the auditors require as far as Sage ERP MAS 500 is concerned.

There is only one level of certification in PA-DSS, the application and implementation is either compliant or not. PCI-DSS has different levels of certification and Sage ERP MAS 500 is compliant with any of the different PCI-DSS compliance levels.

Once Sage ERP MAS 500 is at version 7.5 and utilizing Sage Exchange, MAS500 will no longer touch card holder information. The card holder data is gathered by Sage Exchange in a totally independent memory space and sent to the Sage Vault. Sage ERP MAS 500 then deals with an opaque pointer to the information stored in the vault. Sage Exchange is PA-DSS compliant. Sage ERP MAS 500 will no longer require PA-DSS certification because it no longer touches card holder data.

The customer will still be required to be PCI-DSS compliant, so it doesn’t change the customer’s procedures. It only moves the PA-DSS compliance requirement from Sage ERP MAS 500 to Sage Exchange. You can learn more about Sage Exchange at http://www.sagepayments.com/Products-Services.

I would like to thank Richard Sisk for input on this topic.

The creation of ePortal for MAS 500


I have been asked several hundred times over the last 3 years, in various ways, as to what was the background of ePortal for MAS 500. It’s initial intent was to serve as a much more dynamic and robust B2B and salesperson interface than the legacy eCustomer and eSalesforce modules for Sage ERP MAS 500. This was accomplished rather easily and it has morphed into quite a bit more.

The ePortal for MAS 500 framework is built using the Microsoft .NET 3.5 SP1 tool set. It consists of 3 components. They include the following.
ePortal for MAS 500 – This is the user interface. This is ASP.NET and JavaScript.
MAS 500 WS – This layer is comprised of Web Services and WCF Services. This layer is serves as the interface with the MAS 500 database and the UI (ePortal for MAS 500). For those wishing to create their own or just use their existing UI they can just purchase the MAS 500 WS without the ePortal for MAS 500.
SQL Components – The application does not alter any base tables, views or stored procedures of the base Sage ERP MAS 500 solution, but it does have some objects of its own.

The first year we spent finding our way with the product. The initial installations were solely to our customer base to meet their unique requirements that were just no longer possible with the legacy modules. We have continued to add functionality, expand our install based and tweak the functionality based on your feedback.

This has proven to be a success for both RKL and our clients. It is always nice to create something that is extremely flexible but it always creates some anxiety at times while everyone gets acclimated to the product. Thank you to the RKL Team for all the effort spent working on this product vision and to the Sage Partners and Customers who have been adopters of this new interface. We appreciate your business.

%d bloggers like this: