Microsoft Dynamics SL 6.5, EN, MVL, CD 271-01863 Leaflet
Product codes
271-01863
Flexible Approval Structure
Design a simple, one-person approval process or set up multiple layers of
approvals based on your company needs. Maximum amount approval levels can
be defined based on departments or projects. Additional approval policies can
be defined based on the type of items being ordered. The result is a tremendous
amount of flexibility to define the control and compliance structure you need
while at the same time streamlining the requisitioning process for your people.
approvals based on your company needs. Maximum amount approval levels can
be defined based on departments or projects. Additional approval policies can
be defined based on the type of items being ordered. The result is a tremendous
amount of flexibility to define the control and compliance structure you need
while at the same time streamlining the requisitioning process for your people.
Optimized Request Process
Many companies’ requisitioning processes span from paper forms to in-house
systems. Their request process often requires duplicate entry into multiple
systems. With Requisitions in Microsoft Dynamics SL there is one point of entry
for all requests: the Item Request function. This is accessible to users on the Web,
via the Business Portal in Microsoft Dynamics SL, or through the Microsoft
Dynamics SL application.
systems. Their request process often requires duplicate entry into multiple
systems. With Requisitions in Microsoft Dynamics SL there is one point of entry
for all requests: the Item Request function. This is accessible to users on the Web,
via the Business Portal in Microsoft Dynamics SL, or through the Microsoft
Dynamics SL application.
Encumbrance and Budget Validation
Item request budget, actual, and committed amounts are viewable to requesters
and approvers. Budgetary constraints will set off alerts or restrict requests from
being processed that are over budget. This helps to enforce the desired fiscal
responsibility. Upon submission for approval, the costs of the items on the
requests become committed to the account or project.
and approvers. Budgetary constraints will set off alerts or restrict requests from
being processed that are over budget. This helps to enforce the desired fiscal
responsibility. Upon submission for approval, the costs of the items on the
requests become committed to the account or project.
Request History Automatically
Maintained
Maintained
A complete history of each request, including the date, time and user is stored
for each request. This makes it easy to identify who requested an item and when
and also who approved it.
for each request. This makes it easy to identify who requested an item and when
and also who approved it.
Consolidation of Requests
Separate requests for the same vendor can be manually or automatically
consolidated onto a new requisition. Combining similar requests saves on
shipping and affords the opportunity of possible cost breaks through
negotiations on larger orders with vendors.
consolidated onto a new requisition. Combining similar requests saves on
shipping and affords the opportunity of possible cost breaks through
negotiations on larger orders with vendors.
FEATURES
BENEFITS
This document is for information purposes only.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS
DOCUMENT.
DOCUMENT.
© 2007 Microsoft Corporation. All rights reserved.
Microsoft and The Microsoft Dynamics Logo are either registered trademarks or trademarks of Microsoft Corporation or Microsoft
Business Solutions ApS in the United States and/or other countries. Microsoft Business Solutions ApS is a subsidiary of Microsoft
Corporation.
Microsoft and The Microsoft Dynamics Logo are either registered trademarks or trademarks of Microsoft Corporation or Microsoft
Business Solutions ApS in the United States and/or other countries. Microsoft Business Solutions ApS is a subsidiary of Microsoft
Corporation.
For more information about Microsoft Dynamics SL, visit: