Sage SUMMIT 2011 – Booth 205

We will see you all at Sage SUMMIT 2011, to be held at Washington DC.  Feel free to visit our booth #205. We have many exciting stuff including Add-On products and services for display.

There’s so much to do, see, ask, and learn:

• Visit our #205 booth and test-drive solutions with the latest technology.
• Learn ways to add power and functionality to your Sage solution
• Get hands-on with the tools and technologies
• Get exclusive discounts on products and services
• Win prizes and gifts

Looking forward to meet you there. Contact us for more information:  sales@ciindia.com

 

Sage Accpac – OE order to IC transfer

Order entry module in an ERP usually generates, schedules and maintains estimates, sales orders. Invoices are created automatically when linked to the appropriate modules. Inventory control module tracks inventory balances, serial numbers, product line information etc. The module is for tracking inventory costs and locations. Integration of order entry module with inventory control module makes complete sense.

As part of customizing Sage Accpac, CI worked on a project involving conversion of OE orders into IC transfers. Gap analysis and mapping was done to map the fields between the two modules. An interface was created to facilitate the user to enter the order details which needed to be transferred from OE to IC. Once the necessary details were processed, the sales order was converted into IC transfer and an IC transfer number was generated.

Contact us with your customization requests at sales@ciindia.com

 

Automated transfer during shipment – Sage Accpac 6.0 Customization

Sage Accpac 6.0 is the latest version of Accpac. As co-developers of Sage Accpac 6.0, CI possesses the skills required for customizing the product to suit the business needs. For one of our customers using Accpac, it was required for sales orders to be shipped and invoiced from sales locations. CI worked on the solution by creating two user interfaces and one Accpac view.

Configuration UI was created for selecting the item category that required automatic transfer from manufacturing location to sales location. OE Shipment Entry UI was created for IC transfer for the shipment item. IC transfer entry would have order number, reference fields, item from and to location, transfer quantity and UOM field values. The shipment entry was created only when transfer was successful.

Contact us with your customization requests at sales@ciindia.com

 

Sage SalesLogix: LAN to Web Upgrade

There is no question that web has taken over in the user arena. But the same cannot be said in the software products user arena. One can still see desktop or PC versions of products being used. Over the past few years we have been getting requests for LAN to web upgrades. Upgrading versions of software to a completely different delivery platform is a tough task. One cannot compare things between LAN and web client.

With SaaS/cloud gaining importance, there have been requests for LAN to web migration. We have been getting requests for upgrading from Sage SalesLogix LAN 7.2 to Sage SalesLogix web including all the customizations. We usually cover the following basic steps before upgrading:

• Gap analysis – to review the current functionality along with the customizations and compare the same with the features of the new version
• Form mapping – Form by form design outline and mapping
• Upgrade the database
• Complete the migration

Are you looking to migrate or upgrade to newer Sage SalesLogix versions? Contact us for a free quote at sales@ciindia.com

 

ERP Upgrade – Data Migration Utility

You have outgrown your existing ERP and want to move to another one which offers better functionality. Migration utilities pave the way for reducing the total effort required for migrating data from one system to other system. But how is a data migration utility built? One size does not fit all as the source and target systems are different in each case. Data migration involves data conversion, master records, historical data and transactional records migration.

Detailed analysis of source and target systems is done. Gap analysis is done to chart out the differences between the two systems. The migration tool should transfer data from source to target system irrespective of their versions without losing essential source system’s information to target system. The main business challenge in developing a migration tool was to match the data and the transactions from the basic accounting package to the comprehensive financial and operations system without losing track of business critical information and being user-friendly at the same time.

Data conversion will include the migration of master records, transactional data and historical data.

For example: In the migration of data from one accounting system to another:

• Master records will include key items such as account number, name, etc., as well as transaction masters that are used to create recurring transactions. For example: standard postings in the general ledger, recurring sales orders.
• Transactional data will include all types of open transactions. For example: unpaid AR invoices, partially paid AP invoices. Transactions completed or closed are assumed to be included in historical data.
• Conversion of historical data should be done where appropriate.

Mapping is done between both systems in terms of modules, features and data. The target system might already have features that aid in migration. Therefore it may not be necessary to reinvent the wheel. While standard features can be easily migrated, the challenge is in migrating customized features. CI has been involved in building Simply Accounting by Sage to Sage Accpac migration utility. To know more about our rapid product engineering capabilities with respect to Sage add-on product development contact us at sales@ciindia.com