How To Use The New Version Of The Powerpoint V

Transcription

1 Infor10 ERP Express (VISUAL) Release Notes

2 Copyright 2012 Infor All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor. By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor pursuant to a separate agreement ("Purpose"). In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above. Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause. Trademark Acknowledgements All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners. Publication Information Release: Infor10 ERP Express (VISUAL) Publication date: July 12, 2012

3 Contents Compatibility... 6 Compatibility with other VISUAL products... 6 Unify 5.2 runtime requirements... 7 Licensing... 8 Upgrading from previous versions... 9 Macros, Workflow, and custom applications Audit Triggers Overview of major new features Multi-entity and multi-site Other enhancements Multi-entity and Multi-site overview About the tenant level About accounting entities About sites Sample multi-entity, multi-site structure Setting up the multi-entity, multi-site environment Application Global Maintenance Report Format Overrides Accounting Entity Maintenance Site Maintenance Assigning parts, shop resources, services and employees Users and Groups Setting up financial information... 20

4 Contents Chart of Accounts Currency Financial Calendars GL Interface Using the interface in a multi-site, multi-entity environment Viewable sites Browse tables Accounting ID Browse Tables Setting up auto-numbering Setting up master data in a multi-entity, multi-site environment Warehouse Maintenance Part Maintenance Outside Service Maintenance Shop Resource Maintenance Employee Maintenance Customers Banks Manufacturing Transactions in a multi-entity, multi-site environment Buying and selling between accounting entities Financial Transactions in a Multi-entity, Multi-site environment Other functions in a multi-site, multi-entity environment Reporting Financial Reporting Calendars Other Enhancements Cost Centers Customer Groups Vendor Groups Contact Maintenance Buyer Maintenance Single Sign On (SSO) Infor10 ERP Express (VISUAL) Release Notes

5 Contents Landed Cost User ID and Password Length Password in Command Line Export Attendance Transactions EIS Infor10 ERP Express (VISUAL) Release Notes 5

6 Compatibility Compatibility As of the publication date of this document, Infor10 ERP Express (VISUAL) is compatible with the products described in this section. Consult the Infor 10 ERP Express (VISUAL) Compatibility Matrix and the VISUAL Supported Platforms document for up-to-date compatibility information. ERP Express (VISUAL) is compatible with these database engines: SQLServer 2008 R2 SP3 Oracle 11g ERP Express (VISUAL) is not compatible with SQLBase. ERP Express (VISUAL) is compatible with this client operating system: Windows 7 64 bit ERP Express (VISUAL) is compatible with these server operating systems: Windows bit and 64 bit Windows 2008 R2 64 bit ERP Express (VISUAL) is compatible with these third-party applications: Office 2010 Loftware 9.8 MPC Compatibility with other VISUAL products ERP Express (VISUAL) is compatible with these products: Infor ERP VISUAL Human Resources Infor ERP VISUAL Payroll Compatibility with other VISUAL products is pending. When other VISUAL products have been updated to be compatible with Infor10 ERP Express (VISUAL) 7.1.0, Infor will send notifications. VISUAL databases that have CRM tables cannot be upgraded at this time. 6 Infor10 ERP Express (VISUAL) Release Notes

7 Compatibility Unify 5.2 runtime requirements ERP Express (VISUAL) requires the use of the Unify 5.2 service pack 2 runtime. Previous versions of the Unify runtime are not compatible with ERP Express (VISUAL) Infor strongly recommends removing all previous versions of the Unify runtime before installing ERP Express (VISUAL) Infor strongly recommends that you do not use multiple versions of the Unify runtimes on the same client. Infor10 ERP Express (VISUAL) Release Notes 7

8 Licensing Licensing A new license key is required to use multi-entity functionality in version The number of sites you are allowed to use is determined by the license key. If you are currently using a single entity with no additional financial entities, you do not need a new license to continue using a single entity. Version does not support financial entities as they behaved in versions prior to Customers who were actively using financial entities in version and earlier will have to decide whether they want to go to full multi-site or if what they are trying to achieve can be done some other way in the system (transactional reporting, etc). We rely on the expertise of our partners to determine the best path forward for the goals of each customer. If you are currently using multiple financial entities, contact your salesperson or Infor consulting to ensure you have the correct key. Adding sites may be chargeable. 8 Infor10 ERP Express (VISUAL) Release Notes

9 Upgrading from previous versions Upgrading from previous versions Note: If you currently use multiple financial entities, consult the Upgrade Considerations for Databases with Multiple Financial Entities document for more detailed information on upgrading your database. In previous versions of VISUAL, you could create multiple entities. One of these entities was the default manufacturing entity. All manufacturing activity and associated inventory transactions took place in the default manufacturing entity. All other entities were financial entities. You could attach these financial entities to certain transactions such as customer orders and accounts payable invoices, and each financial entity could have its own general ledger interface. The financial entities could not be associated with inventory and manufacturing activity. In ERP Express (VISUAL) 7.1.0, the default manufacturing entity and financial entity concepts do not exist. Most activity occurs at the site level, and most of the areas in the system that used to include an Entity ID field (such as customer orders and accounts payable invoices) now include the Site ID field instead. When you upgrade to ERP Express (VISUAL) 7.1.0, you have the opportunity to rename your existing financial entities to new accounting entities. You must create a new accounting entity for each of your previous financial entities. You cannot specify the same value in more than one line in the New ID column Infor10 ERP Express (VISUAL) Release Notes 9

10 Upgrading from previous versions After the conversion is complete, the IDs you specified in the New ID column are used as the Accounting Entity IDs. The IDs in the Old ID column are used as the Site IDs. For example, site MMC belongs to accounting entity USEAST, site MMC-2 belongs to accounting entity USWEST, and so on. If you would like to continue to use financial entities that have no associated manufacturing data, it will not be possible to convert your database into an environment that will be useful in the multi-site version of ERP Express (VISUAL). We recommend you consult with your channel partner or Infor Consulting Services for the best implementation plan for your environment. If you upgrade a database that has more than one financial entity, then your system is considered to be a multi-site system. You will be required to use a license that supports multiple sites. 10 Infor10 ERP Express (VISUAL) Release Notes

11 Macros, Workflow, and custom applications Macros, Workflow, and custom applications If you use macros, workflows, or custom applications, you may need to make modifications to these items to handle site-specific information. Infor10 ERP Express (VISUAL) Release Notes 11

12 Audit Triggers Audit Triggers During upgrade, all existing Audit triggers are deleted. If you currently use Audit Maintenance, make a note of all audits you have currently set up before you upgrade your database. You will need to recreate your audits after you upgrade your database. 12 Infor10 ERP Express (VISUAL) Release Notes

13 Overview of major new features Overview of major new features Multi-entity and multi-site ERP Express (VISUAL) introduces new multi-entity and multi-site functionality. Multi-entity and multi-site features use three levels of organization: the tenant level, the accounting entity level, and the site level. Your sites report to accounting entities; your accounting entities report to the tenant. Each of your accounting entities is an independent financial entity. Each entity can have its own financial calendar, currency exchange rates, and costing method. The settings specified at the accounting entity level apply to each site assigned to the accounting entity. Each of your sites can manufacture goods independently of one another. Each site has its own production schedule and warehouses. Before you can use a part, shop resource, outside service, or employee in a site, you must assign the item to the site. You can define site-specific information for your parts, shop resources, outside services, and employees. After you set up your site-specific data, you can use the data in transactions. Most transactions take place at the site level. The system administrator can control which of your database users can access site information. The system administrator assigns sites to user IDs. The sites the system administrator assigns are the user s allowable sites. Users can tailor the interface by deciding which of their allowable sites they would like to view in the system. See Multi-entity and Multi-site overview and the subsequent sections for more detailed information about this major new feature. Other enhancements The other enhancements in ERP Express (VISUAL) help you to analyze costs, streamline data entry, and streamline access to ERP Express (VISUAL) itself. These new enhancements include: Cost Centers Use cost centers, or dimensional reporting, to associate costs with particular records in your database, such as warehouse IDs, customer IDs, and vendor IDs. Dimensional reporting provides granularity to your general ledger transactions. Customer Groups and Vendor Groups Use Customer Groups to group multiple Customer IDs under one parent group. You can use Customer Groups to centralize payment receipts. You can receive payment from the parent group and apply the payment to invoices for individual customer Infor10 ERP Express (VISUAL) Release Notes 13

14 Overview of major new features IDs. Similarly, use Vendor Groups to group multiple Vendor IDs under one parent group. You can use Vendor Groups to centralize payments you make. You can make a payment to the parent group and apply the payment to invoices for individual vendor IDs. Contact Maintenance Use Contact Maintenance to create and maintain all contacts in a centralized location. Buyer Maintenance Use Buyer Maintenance to specify which users act as buyers. You can then browse for a buyer ID in transactions that use buyers. Single Sign On (SSO) When you enable Single Sign On, users do not need to specify separate log in information for ERP Express (VISUAL) After they log into their work station, they can open ERP Express (VISUAL) without specifying any additional credentials. In conjunction with this feature, user IDs and passwords can be up to 20 characters. See Other Enhancements for more detailed information. 14 Infor10 ERP Express (VISUAL) Release Notes

15 Multi-entity and Multi-site overview Multi-entity and Multi-site overview Multi-entity and multi-site features use three levels of organization: the tenant level, the accounting entity level, and the site level. About the tenant level A tenant is the corporate parent or top level of the organizational structure. Each database can have only one tenant. Information you define at the tenant level applies to all accounting entities and sites in your database. Information defined at the tenant level includes, but is not limited to: Certain application-wide information, such as purchase quote type, the default directory for documents, and interface theme Common codes, such as Honorifics, Packaging Types, Carriers, Workflow Codes, Commodity Codes, and Units of Measure For some records, such as parts, you define certain information at the tenant level and certain information at the site level. You can also choose to override some of the tenant information for the part with site-specific information. For example, in Part Maintenance you can define the Part Description at the tenant level only. The Eng Master ID can only be defined at the Site level. Product code can be defined at either the Tenant or Site level. About accounting entities An accounting entity is an independent financial entity within your company. An accounting entity is a person, partnership, organization, or business unit that has a legal existence, for which accounting records are kept, and about which financial statements are prepared. The accounting entity is the middle level of the organizational structure. Each accounting entity is summarized to the Tenant level. Information defined at the accounting entity level includes, but is not limited to: Costing information, such as the costing method, POC revenue recognition method, and burden basis Default VAT information Default Intrastat information Payment information, such as Next Payment Batch Sequence # and withholding information Infor10 ERP Express (VISUAL) Release Notes 15

16 Multi-entity and Multi-site overview Default Order Management information, such as whether WIP/VAS is enabled and allocation information In addition, each accounting entity can use a different financial calendar and functional currency. About sites Typically, a site is a specific, physical location capable of manufacturing goods of all sizes in large quantities to be sold by a business. Sites can also be a building, a part of a building, or a collection of buildings that uses independent planning and costing processes whether or not goods are manufactured at the site. Sites are assigned to accounting entities. Each site can be assigned to only one accounting entity, but each accounting entity can have multiple sites. Most activity occurs at the site level. Information defined at the site level includes, but is not limited to: Scheduling information Shipment tracking information Default ECN information Default inventory, labor, inspections, and project information Engineering masters, quotes, and work orders You assign parts, services, shop resources, and employees to sites. The system administrator assigns database users to particular sites. Users can only view and create information in the sites to which they are assigned. 16 Infor10 ERP Express (VISUAL) Release Notes

17 Multi-entity and Multi-site overview Sample multi-entity, multi-site structure A multi-entity, multi-site environment may have this structure: Parent Company XYZ Company/Entity A Company/Entity B Company/Entity C Site A1 Site A2 Site A3 Site B1 Site C1 Site C2 In a multi-entity environment, a parent company has separate business units or divisions that are separate legal entities, each with their own tax ID and independent financial statements and reporting. In a multi-site environment, multiple sites belong to one accounting entity. Financial statements and reporting is at the accounting entity level, but inventory control, WIP, planning and other data is separated by site. Infor10 ERP Express (VISUAL) Release Notes 17

18 Setting up the multi-entity, multi-site environment Setting up the multi-entity, multi-site environment To set up your tenant, accounting entities, and sites, use the appropriate ERP Express (VISUAL) application. You use Application Global Maintenance to set up the tenant. You use Accounting Entity Maintenance to set up accounting entities. You use Site Maintenance to set up sites. To set up financial information, use Financials Application Global Maintenance. In addition, you must assign sites to your database users before they can enter information in the database. If you are upgrading from a previous version of VISUAL, all existing users are assigned to the site that was the default manufacturing entity before upgrade. Application Global Maintenance Use Application Global Maintenance to define basic information about the tenant level. The information you define in Application Global Maintenance applies to all of your accounting entities and sites. Application Global Maintenance is divided into several tabs. The tabs are: General Use the General tab to define the corporate address, barcode transaction system time limit, number of recently used files to display in the File menu of certain windows, default oldest open invoice setting, purchase quote type, and Synchronizer records setting. Schedule Use the Scheduling tab to define the standard workday and shift information for your enterprise. If you are licensed to use multiple sites, you can define scheduling information specific to the sites in Site Maintenance. If you choose not to define calendars specific to your sites, the schedule you specify here is used instead. If you are licensed to use a single site, the scheduling information you define in Application Global Maintenance is used. Any scheduling information defined in Site Maintenance is ignored. Defaults Use the Defaults tab to specify certain application-wide information, including Trace ID information, how to use customer pricing in shipping entry, default document maintenance options, and password requirements in Workflow. In addition, you use Application Global Maintenance to specify system-wide information, such as common codes, address layouts, service charge defaults, and report format overrides. 18 Infor10 ERP Express (VISUAL) Release Notes

19 Setting up the multi-entity, multi-site environment If you used a previous version of VISUAL, all other information that you formerly maintained in Application Global Maintenance is now maintained in either Accounting Entity Maintenance or Site Maintenance. Report Format Overrides Report format overrides are maintained at the tenant level, but you can create overrides at the entity or the site level. You can use this feature to include site- or entity-specific information, such as a logo, on your reports. Accounting Entity Maintenance Use Accounting Entity Maintenance to define basic information about your accounting entities. The information you define for an accounting entity in Accounting Entity Maintenance applies to each site that belongs to that accounting entity. Accounting Entity Maintenance is divided into several tabs. The tabs are: General Use the General tab to specify the entity s address, the entity s tax ID number, the entity s financial calendar, the entity s functional currency, the default language ID for menus, and the effective exchange rate date. Costing Use the Costing tab to specify how transactions are costed. Each accounting entity can have a different costing method. VAT Use the VAT tab to activate VAT for the accounting entity and to set up all related codes. Intrastat Use the Intrastat tab to set up Intrastat and ESL information. Payment Use the Payment tab to set up default payment information such as batch number information, withholding information, cash variance information, and source of commission payments. Order Mgt Use the Order Mgt tab to set up order management such as WIP/VAS settings, allocation behavior, default shipping weight unit of measure, default back order fill rate, and order management codes. Defaults Use the Defaults tab to specify requisition approval group names, how purchase requisition approval tasks are generated, requisition rejection codes, and default cash receipt and cash payment bank accounts. Site Maintenance Use Site Maintenance to define basic information about your site. You can also assign parts, shop resources, services and employees to your sites in Site Maintenance. Site Maintenance is divided into several tabs. The tabs are: Infor10 ERP Express (VISUAL) Release Notes 19

20 Setting up the multi-entity, multi-site environment General Use the General tab to define the site s address, default pack list status, demand fences for the Advanced Material Planning window, part location and warehouse on the fly settings, and issue negative settings. Schedule Use the Schedule tab to define the site s production schedule. If you are licensed to use multiple sites, the schedule you define in Site Maintenance overrides the schedule defined in Application Global Maintenance. If you are licensed to use a single site, the schedule defined in Application Global Maintenance overrides the schedule you define in Site Maintenance. Shipment Trk Use the Shipment Trk tab to activate shipment tracking, define the default shipping label, and specify how to handle partial shipments with pre-invoiced orders. ECN Use the ECN tab to define default ECN settings and to set up ECN codes. Defaults Use the Defaults tab to specify default inventory and labor settings, inspection settings, and project warehouse settings (requires Project/A&D licensed). You can also set up service charge defaults. Assigning parts, shop resources, services and employees Parts, resources, services and employees must be assigned to a site before they can be used in transactions for that site. You can assign parts, resources, services, and employees to a site in Site Maintenance. Use the options available on the Maintain menu to assign parts, resources, services, and employees to your sites. Users and Groups Before a database user can enter information and conduct transactions in a site, the system administrator must assign the site to the user. In addition, the system administrator must set up approval groups by site. Use the Allowable Sites tab in Security Maintenance to assign sites to users. The sites that are assigned to users are referred to as allowable sites. Use the Groups tab to set up approval groups for your sites. Before a user can be added to a group for a particular site, the system administrator must first assign the site to the user. If users are not allowed to use a particular site, they cannot be added to approval groups for that site. Setting up financial information Set up this financial information before entering transactions. Chart of Accounts Set up your chart of accounts at the tenant level. 20 Infor10 ERP Express (VISUAL) Release Notes

21 Setting up the multi-entity, multi-site environment Currency Each entity has a functional currency. The concept of functional currency replaces the concept of system currency in previous versions of VISUAL. Use Currency Maintenance to define each entity s functional currency. In addition, entities can use only those currencies that you assign to them. Assign currencies to entities in Currency Maintenance. When you enter a transaction for a site, the currency you use must be assigned to that site s accounting entity. Financial Calendars Assign financial calendars to accounting entities. Each accounting entity can use a different financial calendar. If you are upgrading from a previous version, the financial calendar you used is included in the upgraded database. The ID of your previous financial calendar is the same as the ID you had used for your default manufacturing entity. Set up financial calendars in Financial Calendar Maintenance. Financial Calendar Maintenance is available from the Maintain menu in Financial Application Global Maintenance. After you set up the financial calendar, use Accounting Entity Maintenance to assign the financial calendars to your entities. GL Interface Set up the default GL interface on a site-by-site basis. You can copy the GL Interface you set up in one site to another site. Several new accounts have been added to the GL interface. Use these accounts in transactions between sites. The new accounts are: A/P Intercompany Cash A/R Intercompany Cash Intransit Burden Intransit Material Intransit Services Intransit - Labor Infor10 ERP Express (VISUAL) Release Notes 21

22 Using the interface in a multi-site, multi-entity environment Using the interface in a multi-site, multi-entity environment Viewable sites After the system administrator sets up a user s allowable sites, the user can choose which of the allowable sites are viewable. The user can also specify a default site. When a user selects viewable sites, only those sites are available for selection when the user clicks the Site ID drop-down button in a window. The default site is inserted in the Site ID field when the user accesses a window. Users can set up their viewable sites on a system-wide basis and on a window-specific basis. To set up viewable sites on a system-wide basis, use the Set Viewable Sites dialog box available on the Sites menu. Use this dialog box to specify the default site. To set up viewable sites in a window, use the Set Viewable Sites dialog available on the View menu in windows where this feature is supported. Browse tables When you specify a site ID in a window, browse tables are filtered by site ID if the data in the table are maintained by site ID. For example, purchase order IDs are maintained at the site level. If you browse for a purchase order ID in the Purchase Order Entry window, the purchase order IDs in the browse are filtered by the site you selected. If the browse table is an advanced browse table, you can choose to view information from your viewable sites or your allowable sites. Accounting ID Browse Tables While you maintain the chart of accounts at the tenant level, you can display only selected accounts when users browse for an Account ID. To display only certain accounts when you browse for an account in a particular site, use the Filter Account by Site function. You can access this function from the Maintain menu in the Accounting Window. After you set up which accounts are displayed for a 22 Infor10 ERP Express (VISUAL) Release Notes

23 Using the interface in a multi-site, multi-entity environment particular site, users see only those accounts when they browse for an account ID in a transaction for that particular site. Users can still manually type in any account ID. Infor10 ERP Express (VISUAL) Release Notes 23

24 Setting up auto-numbering Setting up auto-numbering We strongly recommend using different numbering schemes for each site in multi-site implementations. Setting up schemes for each of your sites helps you to easily identify which site generated the transaction. It also ensures that transactions within a site are sequential. Set up auto-numbering schemes in these windows: Accounts Payable Invoice Accounts Receivable Invoice Cash Application ECNs Equipment Maintenance Estimating Window Inter-branch Transfer Entry Inter-branch Transfer Receipt Entry Inter-branch Transfer Shipping Entry Planned Maintenance - Sales Order ID Planned Maintenance - Schedule Planned Maintenance - Work Order ID Purchase Order Entry Purchase Receipt Entry Purchase Requisition Entry RMA Entry Sales Orders Entry Shipping Entry - Advanced Shipping Notices Shipping Entry - Bills of Lading Shipping Entry - Customs Doc IDs Shipping Entry - Packlists Unplanned Maintenance Unplanned Maintenance - Sales Order ID Unplanned Maintenance - Work Order ID Vendor RFQ Entry Work Orders 24 Infor10 ERP Express (VISUAL) Release Notes

25 Setting up master data in a multi-entity, multi-site environment Setting up master data in a multi-entity, multi-site environment Warehouse Maintenance Create warehouses at the Site level. Warehouse IDs must be unique at the tenant level. You cannot use the same warehouse ID in two different sites. Part Maintenance Certain information in the part record is stored at the tenant level and certain information is stored at the site level. When you create a part, you can select a site for the part and define all information for the part, including information that is ultimately stored at the tenant level. To edit a part, you must make the appropriate selection in the Site ID field. To edit tenant-level information, select *Tenant* in the Site ID field. The fields that contain tenant-level information become available. To edit site-level information, select the site ID where the part exists. If the part exists in multiple sites, you must edit site-level information on a site-by-site basis. You can add multiple parts to a site at one time by using the Site Parts dialog box available on the Maintain menu. You can add the same part to multiple sites at one time using the Sites for Part dialog box available on the View menu. Use these Part Maintenance functions on the site level: Vendor Pricing Information Customer Pricing Information Resetting Material Requirement Costs Calculating Standard Unit Costs Resetting Part Information Specifying Part Locations ABC Analysis Setting Up Cycle Count Purchase History Information Infor10 ERP Express (VISUAL) Release Notes 25

26 Setting up master data in a multi-entity, multi-site environment Material Requirements Information Where Used Report Material Requirements Report Other functions can be used at either the site or tenant level, or be used for multiple sites at one time. Outside Service Maintenance Certain information in the outside service record is stored at the tenant level and certain information is stored at the site level. When you create an outside service, you can select a site for the outside service and define all information for the outside service, including information that is ultimately stored at the tenant level. To edit an outside service, you must make the appropriate selection in the Site ID field. To edit tenant-level information, select *Tenant* in the Site ID field. The fields that contain tenant-level information become available. To edit site-level information, select the site ID where the outside service exists. If the outside service exists in multiple sites, you must edit site-level information on a site-by-site basis. You can add multiple outside services to a site at one time by using the Site Services dialog box available on the Maintain menu. You can add the same outside service to multiple sites at one time using the Sites for Services dialog box available on the View menu. Use these Outside Service Maintenance functions on the site level: Resetting Service Operation Costs Vendor Pricing Shop Resource Maintenance Certain information in the shop resource record is stored at the tenant level and certain information is stored at the site level. When you create a shop resource, you can select a site for the shop resource and define all information for the shop resource, including information that is ultimately stored at the tenant level. To edit a shop resource, you must make the appropriate selection in the Site ID field. To edit tenantlevel information, select *Tenant* in the Site ID field. The fields that contain tenant-level information become available. To edit site-level information, select the site ID where the shop resource exists. If the shop resource exists in multiple sites, you must edit site-level information on a site-by-site basis. You can add multiple shop resources to a site at one time by using the Site Resources dialog box available on the Maintain menu. You can add the same shop resource to multiple sites at one time using the Sites for Resources dialog box available on the View menu. 26 Infor10 ERP Express (VISUAL) Release Notes

27 Setting up master data in a multi-entity, multi-site environment Use these Shop Resource Maintenance functions on the site level: Resetting Operation Costs Creating Shop Groups Employee Maintenance Employees can enter labor tickets for any site they are assigned to. If employees are not assigned to a site, they cannot enter labor tickets for that site. When employees use Labor Ticket Entry, they can only select work orders associated with the sites to which they are assigned. They cannot select a work order form a site to which they are not assigned. Assign employees to sites using the Allowable Sites function available on the View menu. When you assign an employee to a site, you can also specify the pay rate the employee earns in each site. Customers In Customer Maintenance, you set up credit limit information at the accounting entity level. You set up order management information at the site level. Banks Bank Accounts are separated by Accounting Entity. If you upgrade your database from a previous version and the Entity field is blank, the manufacturing Entity ID from your database is used. For each accounting entity, you can specify a default Bank Account ID for both Accounts Payable and Accounts Receivable. Infor10 ERP Express (VISUAL) Release Notes 27

28 Manufacturing Transactions in a multi-entity, multi-site environment Manufacturing Transactions in a multi-entity, multisite environment These transactions are made at the site level. Each transaction ID must be unique at the tenant level. You cannot use the same ID in one site that you use in a second site. Special conditions about certain transactions are noted: ECNs While you enter ECNs by site, the ECN impacts all sites where the part exists. Engineering Masters, Quote Masters, and Work Orders You can copy a master from one site to a second site provided that the parts, resources, and services exist in both sites. You can use an engineering master created in one site to generate a work order in a second site provided that the parts, resources, and services exist in both sites. Equipment Maintenance Estimates Inter-branch Transfer When you set up an inter-branch transfer, the site ID you choose in the Site ID field is the document owner. It is not necessarily the site that originates the inter-branch transfer. Use Inter-branch Transfer to move materials between two sites with the same parent entity. Inventory Trace Inventory Transactions You can transfer inventory between warehouse locations in the same site only. Labor Tickets Physical Inventories Purchase Orders Purchase Receipts Purchase Requisitions Receiving Inspection RFQs RMAs Sales Orders Shipping Tasks Tasks are identified by site. Only users assigned to the site can administer tasks for that site. Unplanned Maintenance 28 Infor10 ERP Express (VISUAL) Release Notes

29 Manufacturing Transactions in a multi-entity, multi-site environment Buying and selling between accounting entities To move inventory from a site in one accounting entity to a site in another accounting entity, you can set up an internal purchase order to begin the transfer of inventory. When you create the internal purchase order, a corresponding sales order is made in the site that is shipping the goods. To set up an internal purchase order: 1 Set up FOB codes to use with internal purchase orders. Use FOB codes to specify which site owns the inventory while it is in transit. 2 Specify default accounts. Before you ship any inventory between sites, specify the default in transit accounts to use in financials Application Global Maintenance. 3 Set up an internal customer. Create a customer record for sites that order materials from other sites. 4 Set up an internal vendor. Create a vendor record for sites that send shipments from other sites. Use the Internal Site ID to select the site ID the vendor ID represents. 5 Create the internal purchase order. Use the internal vendor you specified as the vendor ID, and then select the internal customer ID you defined for the site specified in the Site ID field. 6 Complete the purchase order. When you save the purchase order, the corresponding customer order is created in the site that is shipping the materials. Use the Show Buy/Sell Status dialog box to track the status of your internal orders. This dialog box is available in both Purchase Order Entry and Customer Order Entry. To track internal orders: If you are accessing the Show Buy/Sell Status dialog box in Customer Order Entry, select an internal order. If you are accessing the Show Buy/Sell Status dialog box in Purchase Order Entry, you do not need to select an order. Infor10 ERP Express (VISUAL) Release Notes 29

30 Financial Transactions in a Multi-entity, Multi-site environment Financial Transactions in a Multi-entity, Multi-site environment Some financials transactions, such as invoices, are by site. You can make and receive payments for multiple sites. Accounts Payable Invoices You can create invoices only in currencies assigned to the parent entity of the site. Accounts Receivable You can create invoices only in currencies assigned to the parent entity of the site. Cash Application You can apply a single cash receipt to invoices from multiple sites, provided that each site s parent entity tracks the currency of the transaction. Using Customer Groups, you can apply a single cash receipt to invoices from multiple customers. Cash Payment You can pay invoices from multiple sites with a single payment, provided that each site s parent entity tracks the currency of the transaction. Using Vendor Groups, you can receive payment from multiple vendors. 30 Infor10 ERP Express (VISUAL) Release Notes

31 Other functions in a multi-site, multi-entity environment Other functions in a multi-site, multi-entity environment Use these functions by site: Cash Management If multiple sites are assigned to the same financial calendar, then these sites can also be associated with the same cash plan. Costing Run costing on a site-by-site basis. Material Planning You can view multiple sites in the Planning window and create transactions to move inventory from one site to another. If the sites are in the same accounting entity, you can create an Inter-branch transfer directly in the Planning Window. If the sites are not in the same accounting entity, you must use the purchase and sales process. Scheduling Work orders are separated by site and only use shop resources available in that site. Each site has its own production schedule. You can view schedules for multiple sites simultaneously in the Scheduling Window. Projects and A&D You can view multiple sites in the Project Summary Window. In Cash Book, when you select a bank account, information for the associated accounting entity is shown. Infor10 ERP Express (VISUAL) Release Notes 31

32 Reporting Reporting Many reports can be run for multiple sites and multiple entities. An Entity/Site selection control is used on these reports. Financial Reporting Calendars You can set up Reporting Calendars to generate consolidated reports across entities, even if the entities use different financial calendars. You can also use Reporting Calendars to set up custom reporting timeframes within an entity, such as by quarters or years. You can use these reporting calendars in the Advanced mode of many financial reports. 32 Infor10 ERP Express (VISUAL) Release Notes

33 Reporting You can use Reporting Calendars in the Advanced mode to print reports for multiple sites and entities. To print these reports for multiple entities, the entities must share at least one currency. The shared currencies are listed in the Report Currency drop-down list. If the selected entities do not share a currency, Not Available is displayed. Infor10 ERP Express (VISUAL) Release Notes 33

34 Other Enhancements Other Enhancements Cost Centers Use cost centers, or dimensional reporting, to associate costs with particular records in your database, such as warehouse IDs, customer IDs, and vendor IDs. Dimensional reporting provides more granularity to your general ledger transactions. The link between the record and the costs is the dimension ID. After you create dimension IDs, you can assign them to particular records, such as a warehouse ID. You can specify a dimension ID for credit transactions and for debit transactions. When you use the warehouse ID for a transaction, such as a shipment, the cost of the transaction is stored with the dimension ID. You can then report all the costs for the dimension ID. Because the dimension ID is associated with a warehouse, you can track the value of all transactions that use the warehouse. You can assign the same dimension ID to multiple records. For example, if you had multiple warehouses in Virginia, you could assign the same dimension ID to all of the Virginia warehouses to track costs associated with your Virginia operation. You can associate dimension IDs with these record types: Bank Accounts Buyer IDs Commodity Codes Customer IDs Department IDs Employee IDs Product Codes Sales Rep IDs Shop Resource IDs Territory Codes Vendor IDs Warehouse IDs Costs are recorded to dimension IDs for these transactions: Accounts Payable Invoices, including recurring invoices Accounts Payable Payments 34 Infor10 ERP Express (VISUAL) Release Notes

35 Other Enhancements Accounts Receivable Cash Application Accounts Receivable Invoices, including recurring invoices Bank Adjustments Financial Allocations General Journal Entries, including recurring transactions Indirect Labor Inventory Adjustments, including Inter Branch Transfers and adjustments from Physical Inventory Counts Purchase Receipts Shipments Work Order Finished Goods Receipt Work Order Labor (Direct labor) Work Order Material Issues Work Order Service Dispatch For some of the transactions, the dimension ID is determined by priorities that you establish. You can specify priority information for these transactions: Accounts Payable Invoices, lines Indirect Labor Inventory Adjustments, including Inter Branch Transfers and adjustments from Physical Inventory Counts Purchase Receipts Shipments Work Order Finished Goods Receipt Work Order Labor (Direct labor) Work Order Material Issues Work Order Service Dispatch For each dimension group, you can specify which record type should be examined first for a dimension ID for these transactions. Dimensional information is only recorded for new transactions. Historical data will not contain dimensions and therefore will not be available for dimensional reporting. Customer Groups In certain cases, you may have more than one customer ID for a single customer. For example, if you have different billing addresses to use with the same company, you would create separate customer IDs to manage this difference. Infor10 ERP Express (VISUAL) Release Notes 35

36 Other Enhancements When you have different customer IDs for the same customer company, you can group them together in Customer Groups. When individual customer IDs are grouped together in Customer Groups, you can receive payment from the customer parent and apply them to invoices for the individual customer IDs. If you are licensed to use multiple sites, you can use Customer Group Maintenance to group customer IDs that you use with different sites together under one parent customer. Vendor Groups In certain cases, you may have more than one vendor ID for a single vendor. For example, if you have different credit and terms arrangements or different billing addresses to use with the same company, you would create separate vendor IDs to manage these differences. When you have different vendor IDs for the same vendor company, you can group them together in Vendor Groups. When individual vendor IDs are grouped together in Vendor Groups, you can make payments to the vendor parent and apply them to invoices for the individual vendor IDs. If you are licensed to use multiple sites, you can use Vendor Group Maintenance to group vendor IDs that you use with different sites together under one parent vendor. Contact Maintenance You can now maintain contacts separately from customer or vendor records. Use Contacts Maintenance to create contacts. In addition to standard contact information, you can record this information about your contacts: Social network URLs Personal information, such as date of birth and marital status Preferred contact method You can assign contacts to vendors and customers directly in Contact Maintenance, or you can use Customer Maintenance and Vendor Maintenance. Buyer Maintenance You can now specify buyers in the Buyer Maintenance table. In documents that include a buyer, such as Purchase Requisition Entry, you can select a buyer from the list of buyers you define. You can access Buyer Maintenance from the Admin menu. 36 Infor10 ERP Express (VISUAL) Release Notes

37 Other Enhancements Single Sign On (SSO) If you enable SSO, users do not have to specify credentials when they log into ERP Express (VISUAL). The credentials they specified when they logged into their work station are used as their credentials for access to ERP Express (VISUAL). Enabling SSO is optional. When SSO is enabled, a user can log in as SYSADM even if SYSADM is not set up as a Windows user. All user names (other than SYSADM) must have a corresponding entry in active directory when SSO is enabled. Landed Cost You can now create landed cost invoices with average costing. User ID and Password Length You can now specify user IDs and passwords of up to 20 characters. Password in Command Line Passwords are no longer passed in command line arguments. Export Attendance Transactions This executable has been renamed from VMIMPEXP.EXE to VMLABEXP. EIS The EIS module has been removed from version Infor has other EIS tools that can be used to accomplish similar functionality. Infor10 ERP Express (VISUAL) Release Notes 37