1099 Vendor Backup Withholdings in SL 2015 features

• In SL 2011, 1099 Vendor Backup Withholding have manual process. Now In SL 2015, having new functionality to make it less manual and more of an automated process.

• How we set this up. Open the AP setup screen under the financial module in 1099 Tab there are a few additional features added to the 1099 screen to specify backup withholding options

1.       Calculate backup withholding

2.       Backup withholding Pct

3.       Disable backup withholding

4.       Backup withholding

a.       Account

b.       Subaccount

• Turn on YES to “Calculate Back Withholding” and click YES to proceed then automatically turn on backup withholding.
• Enter the percent in “Back Withholding Pct” and we define exactly which accounts up count we should be using when we’re doing our backup withholding and when we initially turn it on and sole it.

• Open the vendor maintenance screen and choose the vendor. In the Vendor maintenance screen under 1099 tab will notice is that the “1099 vendor field” set as YES.

• “TaxID Nbr” it is mixing tax ID number which is for holding a backup withholding so that’s a reason to turn on.

• And in the existing field “TIN incorrect Notice” field have you notify vendor that ability and in the new field to calculate backup withholding in its been turned on YES

• Open the voucher & adjustment screen and choose the particular vendor. The system message popup “Vendor ID selected is subject to backup withholding” click YES as we continue on & enter the line amounts control totals & total amounts then save it and Release the batch.  \

                                                    Create Voucher for $1000

• For payment, so we look into the Payment selection screen. In the Payment selection screen select the vendor ID in “payment selection field” and set the specific vendor in the detail grid then click Begin Processing Button. Click Preview Button to view the details.    

• Now have the information in there check printing process. Choose the Created batch and click View Selection Button to view the selections will notice. 

          Note:

 If remember made voucher for a $1000 but we’re only cut the check for $800 because of  backup withholding amount $200.

• So we have automated this process no longer do you have to keep track of it on information. As well we store the vendor backup withholding information into vendor maintenance screen under “1099 info tab” and also view history in Show History button under vendor tab.                                                

Multi-Company Features in SL2015

In Dynamics SL 2011, were limited to running for one company such as “Allocations” and the “Indirect Rate Calculator”.

In Dynamics SL 2015, you can run allocations and other processes for a specific company or all companies, without having to change companies as shown below.

In Dynamics SL 2015, Switching between companies requires just one touch. Now that there are sign-on enhancements, you will only see the companies to which you have access to. Just click and switch! This is done through a simple dropdown menu as shown below. 

                                

In Dynamics SL 2015, Project reports now support the Company Selection sorting criteria. You can also run project reports for a selected companies or current companies. 

In Dynamics SL 2011, had no information on the company they were associated with projects. Now In Dynamics SL 2015, the company related to the project is listed and users only see projects for the company that they have access rights.

Non-admin access user has Using Transaction Import

User who is not in the Microsoft Dynamics SL ADMINISTRATORS group. But users like to use Transaction Import (TI):

   1. Logged in Administrator user, grant them full rights to the TI screens (98.500.00 and 98.510.00). 

   2. Log out Microsoft Dynamics SL then log back in (this will regenerate their menu)

   3. Have them click "All Modules" then expand "Administration".  They can then right-click each of these                          screens and choose "Add to Favorites"

Moving forward, these users can now operate Transaction Import without having to be in the Administrators group.

Goods for Project VS Goods for Project Inventory

In Dynamics SL 2011 one of these new features was addition of a new ‘Purchase For’ type in the Purchase Order Maintenance screen to improve the integration between the Project and Distribution modules.

In previous versions of Dynamics SL there were two ‘Purchase For’ types that were related to projects: “Goods for Project” and “Services for Project”. 

However, the “Goods for Projects” type is not fully supporting to update the inventory balance; No inventory impact during GRN though the items are physically available in warehouse till issuing to project. It would only create a project commitment; Project commitments created during the purchase is getting relieved during the AP Voucher itself. Supposedly, the commitment should be relieved only after issuing to project which is not the case with GP type. In Dynamics SL 7 and earlier you could either update inventory or create a project commitment, you couldn’t do both.

But now, with Dynamics SL 2011, any inventory purchased with the new “Goods for Project Inventory” ‘Purchased For’ type will create a project commitment and inventory will now be allocated for the designated project and task and consumed only by the designated project in the Sales Order Entry (40.100.00), Shippers (40.110.00), or Issues (10.020.00) screens.

In addition, any regular, non-committed inventory that is already in stock can be allocated to a project and then only consumed by that project in the previously mentioned Order Management screens.  This can be done with a new screen in the Inventory module called Project Inventory Allocation.  Allocating inventory in this screen will increase the “Inventory Allocated to Projects” quantity and reduce the “Quantity Available” quantity.  You can also unallocated inventory from projects with this screen.

The timing of the commitments and relieving of the commitments is also different between the two ‘Purchase For’ types.  With the “Goods for Project” ‘Purchase For’ type a project commitment was created when the Purchase Order was entered and the commitment was relieved when the voucher for the related receipt on the purchase order was entered.  In addition, the voucher also posted the ‘actual’ costs to the project.

With the “Goods for Project Inventory” ‘Purchase For’ type a project commitment is also created when the Purchase Order is entered, but the commitment is not relieved when the voucher is released.  Instead, it is not until the allocated inventory is entered on a Sales Order and the Inventory Issue batch that is created from the Order Management Sales Journal is released.  The Inventory Issue batch will not only relieve the commitment, but it will also create the actual costs that post to the project.

Dynamics SL 2015 features

Here’s a few of the new In SL 2015:

Web Apps: Web Apps will play a big role in SL 2015, replacing the Business Portal. Introduced in Dynamics SL 2011, these apps provide a new way to access and enter data into Dynamics SL. Web Apps allow you to access Dynamics SL screens and information via your smartphone or tablet. The apps include Project Time Entry, Project Expense, Project T&E Approval, and Project Analyst

Here are a few features in Dynamics 2011 that use web apps:

    ·   Project Correcting Timecards

    ·   Project Time & Expense Approval

    ·   Project Expense Reports GP

    ·   Project Time Entry with Support for Project Flex Time

    ·   Project Analyst

    ·   Project T-type Timecard Support

In addition to the features that were included in the 2011 release, Microsoft Dynamics SL 2015 web apps are scheduled to be released every 6 months. Web apps will include the following:

·  Project Timesheet Entry – Enter time for a group of employees all at once.

·  Project Communicator - View and read communicator messages.

·  Project Maintenance & Inquiry – Setup project general and billing information, assign resources, set maximums, etc.

·  Billing Information Maintenance

·  Project Maximums Maintenance

·  Percent Complete and Revenue Recognition Setup

·  Address Maintenance

· Contract Value and Revenue Information

·  Budget Maintenance and Inquiry – Set up and review budgets, and make edits and revisions to your budgets.

·  Budget Revision Maintenance, Approval, Inquiry, and Analysis

·  Project Invoice Approval – Approve invoices while out of the office.

·  Project Delegations Approval - Delegate approval for Project based items to others while you are out of the office.

·  Item Request Entry & Approval - Enter Item Requests and approve them

Basic Resource Planning: An incredible new dashboard will allow you to assign resources to projects and tasks.  You can see availability of resources and projects all in one single view. This helps you to manage project coordination and use your resources efficiently without overburdening them.

ROI/ROIS SRS Email: Added email capability is back! You can now email reports directly from Crystal reports with a click of a button.

Report (ROI) Enhancements: Remember those 8 report formats that you could choose from for your reports, well, now you can use an unlimited number of report formats. Also, if you have a customized report that you use frequently, you can set that report as your default format for future reports. 

  1.   Unlimited report formats per report

       

  2.    Company default report format

  3.    Descriptive captions for ROI selection (Metadata)

     

Quick Query Enhancements:  Easily connect your data to Excel and use powerful tools like Pivot Tables to analyze your data.

Sign on enhancement

1.       Building on the removal of all modules

2.       Limit access to only those company ID’s user has rights

3.       If you don't have access to accompany you won't see it 

·      

Dynamics SL 2011 Customization Upgrade

DB upgrade from SL 7 to SL 2011SP2:

1.  If you upgrade the DB from SL 7 to SL 2011 SP2, some alignment issues will be face. After fix the alignments issues and export the latest customizations.
2.  For testing purpose, delete the customization level for the particular screen ID in Customvba table and Re-import the CST file.

             In this scenario’s face problems:

                  a.  Customizations have “versions”. The newest version is 6.

                  b.  The export customizations that haven’t been updated to version 6, you can’t be able to re-                                            import the CST file you just created. You will get an event log like this:

                             “System Message 5016: Operation aborted, data is not formatted correctly. Data

                                                  Row contents: Source: 0”.

                  To get around this:

                   As always, have a good backup of your environment before making any changes

                         *  Export the customization, but don’t check the “export VBA as source” checkbox

                         *  Edit the file and remove the “Source: 0” line(s)

       3.  Then you can re-import. But in this scenario doesn’t not work for DB upgrade

Export the Customization from SL 7 and Import to SL 2011 SP2:

1.  Export the Customization from SL 7 environment with level like (All user, One group, One user, Supplemental, Self) and  import the customization to SL 2011 SP2 environment
2.  Launch the particular screen and customize the screen, then fix the alignment issues automatically version has been updated to 6  and export the latest customizations.
3.  Then delete the customization level for the particular screen ID in Customvba table
4. Then you can re-import customization. Its working fine

SQL Force SL to upgrade it to version 6 first:

   1.   Run the following in SQL:

Ø  Update CustomVBA set Version=Version+1000 where Version<1000

   2.  Open each customize screen and close

Ø  At this point, the version should update to 6.

  3.  Now export the customization. 

Automate Data Entry manner in Dynamics SL

 Data import into Dynamics SL can be attained through any of the below techniques.

  Transaction import (TI):

All Dynamics SL users have the standard import capabilities through the transaction import tool. When using the transaction import screen, the process is powerfully enhanced by use of the Control Macro Generator, which dynamically adjusts for any customization's for field names, and layout.

·         Integration tool of Dynamics SL to transfer data from an external file into any Dynamics SL window

·         Existing Dynamics SL business logic will validate the imported data ensuring the Transaction integrity is an advantage.

·         Can be launched as a batch script file or can be scheduled to run automatically using the “Application Server” tool of Dynamics SL.

·         The data source could be the data file in the comma or tab delimited format.

·         TI processing works only with the Active Desktop connection. If the machine is locked, TI won’t work and will resume only after the machine is unlocked which is a major disadvantage for data import automations.

   Solomon Object Model:

Solomon object model (SOM) is an automatic process for invoking the SL Standard (r) custom screen. The set of all members (properties, events, and methods) of a COM component, In the Microsoft Dynamics SL Object Model, this includes information about the SIVApplication and SIVToolbar objects and their members.

     More detail about Solomon object Module link beneath

     http://ajitkannan-erp.blogspot.in/2013/04/automatically-invoking-sl-standard-r.html

·         Any Dynamics SL window can be accessed as an object and pass data directly into the window.

·         Any COM-compliant application or programming tool can use Solomon Object model

Eg: VB.Net/ C# by adding the Microsoft.Dynamics.SL.ObjectModel.dll as the reference.

·         Best for Dynamics SL Data import Automations as it strictly follows the SL rules and validations ensuring the SL data integrity.

·         The data source could be the databases of home grown/legacy application or the CSV file.

      SQL injection:

·         Injecting the data into the SQL tables of Dynamics SL directly.

·         Need to replicate the table impacts and the validations of Dynamics SL while importing the data into SL.

·         Not highly recommended as there is always a threat of not replicating all the business rules of Dynamics SL.

Big Big thank you to Perumalsamy, else for all the tremendous effort that they put into these blog...