Infor ERP VISUAL

Infor MyDay Integration Guide

Copyright 2009 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.

Publication Information
Release: Infor ERP VISUAL 6.5.4/Infor MyDay 1.1.2 Publication Date: August 14, 2009

Contents
About this guide................................................................................................................................ 4 Intended audience......................................................................................................................... 4 Prerequisite knowledge................................................................................................................. 4 Organization.................................................................................................................................. 4 Setup and configuration ................................................................................................................... 5 Prerequisite ................................................................................................................................... 5 Setting up Infor ERP VISUAL........................................................................................................ 5 Connecting the core product to Infor On-Ramp........................................................................... 14 Configuring MyDay for drillbacks to the core product.................................................................. 19 Verifying the integration .............................................................................................................. 20 Troubleshooting the integration .................................................................................................... 21 Infor ERP VISUAL business events that generate BODs............................................................. 22 Data maps ........................................................................................................................................ 25 Metrics and reports supported by VISUAL data .......................................................................... 26

Infor ERP VISUAL MyDay Integration Guide

4 | About this guide

About this guide

The Infor ERP VISUAL MyDay Integration Guide provides implementation information for the integration between Infor ERP VISUAL and Infor MyDay. This guide describes integration requirements and provides setup instructions specific to VISUAL. This guide also provides information about the business events or user actions in VISUAL that send the various business object documents (BODs) to Infor On-Ramp.

Intended audience
This guide is intended for system administrators who implement the integration between VISUAL and MyDay, or who need to troubleshoot or trace data back from MyDay to VISUAL.

Prerequisite knowledge
To fully understand the information presented in this guide, you should first read the Infor Open SOA Overview Guide. The Infor Open SOA Overview Guide discusses the major concepts of Infor Open Services Oriented Architecture (SOA) and defines common terminology. The Infor Open SOA Overview Guide also includes a list of related documents and support information.

Organization
This document includes: Setup and configuration lists the tasks that must be done before information flows from one product to the other. Troubleshooting the integration offers suggestions on how to analyze problems with the integration. Business events that generate BODs explains the events or user actions that cause the enterprise resource planning (ERP) system to generate a business object document (BOD). Data maps explains where you can find information about the mapping between the MyDay metrics and reports and the VISUAL tables.

Infor ERP VISUAL MyDay Integration Guide

Setup and configuration | 5

Setup and configuration

Follow the steps in this section to set up the required data and connections in VISUAL, MyDay, and associated applications.

Prerequisite
You must run VISUAL with an Oracle 9 or later or SqlServer 2005 or later database. MyDay is not compatible with SQLBase.

Setting up Infor ERP VISUAL

Use the steps in this section to set up VISUAL so that it can generate BODs and place them in an inbox where Infor Business Information Services (BIS) can retrieve them.

Maintaining SOA information

Certain default information must appear on each BOD. Set this information in SOA Maintenance. Note: You must be logged in as the SYSADM user to access SOA Maintenance.

Infor ERP VISUAL MyDay Integration Guide

6 | Setup and configuration

To access SOA Maintenance, go to the Application Global Maintenance window by selecting Admin, Application Global Maintenance. From Application Global Maintenance, select Maintain, SOA Maintenance.

Enter information in the following fields: VISUAL Instance ID Enter a unique identifier for the Visual Instance ID. The system uses the value you enter as the third component of the Logical ID; for example, infor.visual.vmfg654. Please make a note of the value you enter in the Visual Instance ID field. You need the information to perform set up operations in MyDay. Note: The logical ID is also the same as the fortress.id property that is set in the fortress configuration file.

Infor ERP VISUAL MyDay Integration Guide

Setup and configuration | 7

Tenant ID Enter infor. SOA Location Enter a specific site location. In BODs, the system uses the value you enter for the location attribute. If you are using VISUAL Global Financials, enter the Site ID defined in the Topology. Calendar Name Enter the name you would like to use for your accounting calendar. The system uses this information in BODs such as AccountingChart. Language ID Enter the ID for the language you use. The format for the language ID is the ISO two character code for the language in lower case followed by a dash, then the ISO two character code for the country in upper case. For example, the code for US English is en-US. MyDay Version Click the drop-down button to select the version of MyDay to which you are integrating. At this time, 1.1.2 is the only option. 3 The Noun Settings table lists each VISUAL application that can currently export BOD information, and the ID of the BOD that sends the information. Specify the following settings for each Name: Granularity You can not change this setting at this time. SOR - Select the SOR check box if VISUAL is the system of record for the BOD ID. Clear the check box if VISUAL is not the SOR for the BOD ID. The SOR owns a particular set of data and publishes it to other components. For more information on SOR, refer to the Infor Open SOA Overview Guide. Sync - You can only send a Sync BOD if VISUAL is the SOR for the BOD. If VISUAL is the SOR, click the Sync drop-down button and select Out to publish the BOD. Select Disabled if VISUAL is the SOR but you do not want to publish the BOD. Process - If VISUAL is the SOR, click the Process drop-down button and select In if you would like VISUAL to receive BODs from other components. If VISUAL is not the SOR, click the drop-down button and select Out to generate a Process BOD. If you do not want VISUAL to send the BOD, click the drop-down button and select Disable. Filter - If the Allow Filter check box is selected, you can filter the information you send in a BOD. Depending on the noun, you can filter information by ID or Date. Click the Filter button and enter a starting value and an ending value. VISUAL will send records created or modified between the two dates you specify, or between the two IDs you specify. VISUAL inserts the dates you specify in the From Date and To Date columns. VISUAL inserts the IDs you specify in the Starting ID and Ending ID fields. 4 Click Save to save your settings.

After you generate BODs, the system deactivates the Visual Instance ID, Tenant ID, SOA Location, and Calendar Name fields. You cannot edit the information in these fields after BODs are generated. The options in the Sample BODs box are intended for use by an Infor professional.

Infor ERP VISUAL MyDay Integration Guide

8 | Setup and configuration

Sending historical data

Note We strongly recommend that you contact PSO to perform the initial data set up and load. Refer to the VISUAL noun settings for current release for the settings to use and the order in which you should send the BODs. To send historical data: 1 In the SOA Maintenance table, click a BOD designated as 1 in the Initial Load Seq. column in the VISUAL noun settings for current release table, below. Press the shift key while clicking rows to select more than one BOD (for example, you can select all BODs designated as 1 in the VISUAL noun settings for current release). In the Action drop-down box, select Add. Click the Send Selected button. VISUAL sends the BODs to the On-Ramp. Repeat the process for BODs with an initial load setting of 2 through 5.

2 3 4

VISUAL noun settings for current release

Use this table to determine the settings you should use for the BODs. The chart also indicates the order you should send the BODs in the initial load. Initial Load Seq.

ID Accounting Chart Accounting Period Accounts Codes Company Address Consignment Receipt Return Consignment Receiver Currency Customer Customer Order Employee

Noun AccountingChart FinancialCalendar ChartOfAccounts CodeDefinition Location

SOR Unchecked Unchecked Unchecked Unchecked Unchecked

Sync Disabled Disabled Disabled Disabled Disabled

Process Disabled Disabled Disabled Out Out

Notes

1 2

Shipment ReceiveDelivery Currency CustomerPartyMaster SalesOrder Personnel

Checked Checked Unchecked Unchecked Checked Unchecked

Out Out Disabled Disabled Out Disabled

Disabled Disabled Disabled Out Disabled Out

5 5 4 5 3

Infor ERP VISUAL MyDay Integration Guide

Setup and configuration | 9

ID Engineering Master Estimate Exchange Rates GLMovement IBT Receiver IBT Shipper Inter Branch Transfer Inventory Adjustment Inventory Count Inventory Hold LaborTicket Ledger

Noun BillOfResources Quote CurrencyExchangeRa te SourceSystemGLMov ement ReceiveDelivery Shipment Transfer InventoryAdjustment InventoryCount InventoryHold EmployeeWorkTime SourceSystemJournal Entry

SOR Unchecked Checked Unchecked Checked Checked Checked Checked Checked Checked Checked Checked Checked

Sync Disabled Out Disabled Disabled Out Out Disabled Disabled Disabled Disabled Disabled Disabled

Process Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled

Initial Load Seq.

Notes

5 5

Opportunity Part Payable Payable Invoice Person Purchase Order Purchase Receipt Return Purchase Receiver Receivable

Opportunity ItemMaster PayableTransaction Invoice Person PurchaseOrder

Checked Unchecked Checked Checked Unchecked Checked

Disabled Disabled Out Out Disabled Out

Disabled Out Disabled Disabled Out Disabled

5 3 5 5 3 5

Sync can be changed to "Out" if using SOA enabled version of Visual CRM

Shipment ReceiveDelivery ReceivableTransactio n

Checked Checked Checked

Out Out Out

Disabled Disabled Disabled

5 5 5

Infor ERP VISUAL MyDay Integration Guide

10 | Setup and configuration

ID Receivable Invoice Requisition RFQ RFQ Quote Shipment Return Shipper ShipTo Address Shop Resource Vendor Vendor Balance Warehouse Address Work Order Work Order Issue Work Order Issue Return Work Order Receipt Work Order Receipt Return

Noun Invoice Requisition RFQ Quote ReceiveDelivery Shipment Location ConstrainedResource SupplierPartyMaster SupplierBalance Location ProductionOrder Shipment ReceiveDelivery ReceiveDelivery

SOR Checked Checked Checked Checked Checked Checked Unchecked Checked Unchecked Checked Unchecked Checked Checked Checked Checked

Sync Out Out Out Out Out Out Disabled Disabled Disabled Disabled Disabled Out Out Out Out

Process Disabled Disabled Disabled Disabled Disabled Disabled Out Disabled Out Disabled Out Disabled Disabled Disabled Disabled

Initial Load Seq. 5 5 5 5 5 5 2

Notes

2 5 5 5 5

Shipment

Checked

Out

Disabled

Editing visualconfig.xml
To ensure that drill back from MyDay functions correctly, you must edit the <LogicalIDExeMap> portion of the visualconfig.xml file to match the settings you specified in SOA Maintenance. 1 2 3 Locate visualconfig.xml in the local directory where you installed your VISUAL files. Open the file with a text editor. In the LogID name portion, edit the logical ID to match the one you specified in SOA Maintenance. For example, if you entered vmfg654 in the Visual Instance ID field, type lid://infor.visual.vmfg654 in the LogID. In this case, the line of code would be:
<LogicalID name="lid://infor.visual.vmfg654">

Infor ERP VISUAL MyDay Integration Guide

Setup and configuration | 11

In the path portion, edit the path to match the location of your VISUAL executables. For example, if your VISUAL executables reside in c:/Infor Global Solutions/VISUAL Enterprise, edit the path portion as follows:
<path>c:/Infor Global Solutions/VISUAL Enterprise/</path>

If you are using Infor ERP VISUAL Global Financials 7.2, edit the second LogID section to match the logical ID you specified in the Fortress Logical ID field in Global Financials SOA Maintenance. Specify the location of your Global Financials executables in the path portion. If you do not use Global Financials, do not edit the second LogID section. Save the file.

Setting up drill back in VISUAL

Use Drill Back Maintenance in VISUAL to choose which program MyDay opens when drilling back. Note: You must be logged in as the SYSADM user to access Drill Back Maintenance. 1 To access Drill Back Maintenance, from the Admin menu, select Drill Back Maintenance.

The Drill Back ID column lists all of the drill back views from MyDay. To change the VISUAL program associated with the view, double-click the Program Name column header and select the program you would like to use. For example, for the PurchaseOrderView, you could choose to drill back to the Purchase Management Window instead of the Purchase Order Entry window. The system inserts the Program ID associated with the Program Name in the Program ID field. When you are finished changing the default settings, click the Save button.

Infor ERP VISUAL MyDay Integration Guide

12 | Setup and configuration

Opening operations in the Edit Operation dialog when drilling back

If you would like VISUAL to open the Edit Operation dialog when you drill back on an operation from MyDay, edit your VISUAL.ini file. 1 In the Maintain Drill Back dialog, select Manufacturing Window as the Program Name used for drill backs from the ProductionOperationView. Navigate to the VISUAL.ini file and open it in a text editor. The VISUAL.ini is located in the same directory as the VISUAL executables. In the [VISUAL Mfg] section, add the following entry: DrillbackOpenOpForEditing=Y 4 Save and close the file.

Mapping user-defined codes in VISUAL to SOA codes

BODs employ SOA codes for elements such as currency, language, country, and unit of measure. To ensure that information flows properly from VISUAL, use Code Mapping Maintenance to associate the codes you use in VISUAL to the SOA codes. When VISUAL sends information to a BOD, the system replaces the user-defined codes in VISUAL with the codes you mapped to them in Code Mapping Maintenance. When information is sent into VISUAL via a BOD, the system replaces SOA codes with their corresponding VISUAL user-defined codes. If you use user-defined Country codes, Currency codes, and Unit codes, you must map them to ISO codes. You can control access to Code Mapping Maintenance in Program Security. 1 To access Code Mapping Maintenance, from the Admin menu, select Code Mapping Maintenance.

Infor ERP VISUAL MyDay Integration Guide

Setup and configuration | 13

2 3

Click the List ID drop-down button and select the code category you would like to map. Click the Agency ID drop-down and select an agency from the list. The Agency is the group responsible for devising a standard set of codes. To add a new code mapping, click the Insert Row button. Double-click the VISUAL Code column heading and select the VISUAL code you would like to assign to a SOA code. Double-click the SOA Code column heading and select the code to map to the VISUAL code. When you are finished adding code mappings, click the Save button.

4 5

6 7

You can also assign ISO codes to your VISUAL units of measure in Unit of Measure Maintenance. Refer to Infor ERP VISUAL User's Guide Volume II for more information.

Mapping Infor ERP VISUAL CRM Sales Plan Stages

Note This information applies to Infor ERP VISUAL CRM users only. Certain MyDay reports and metrics use specific sales stages. Use the Stages tab in Sales Plan Definition to map your existing stages to codes MyDay can use. 1 In Sales Plan Definition, click the Stages tab.

Infor ERP VISUAL MyDay Integration Guide

14 | Setup and configuration

In the Stages table, click the SOA Code drop-down button to select a SOA stage for each of your stage names. Click Ok to save your changes.

Updating VISUAL Exchange triggers

If you use Infor ERP VISUAL Global Financials, run VMVXCTGR.EXE for all triggers to update the connection between VISUAL Manufacturing and VISUAL Global Financials. VMVXCTGR.EXE is located in the same directory as the other VISUAL Manufacturing executables. Performing this step is not necessary if you do not use VISUAL Global Financials.

Connecting the core product to Infor On-Ramp

Use the steps in this section to create a configuration for Infor On-Ramp that allows it to mediate message exchanges between your core product and the components that were installed with a standard

Infor ERP VISUAL MyDay Integration Guide

Setup and configuration | 15

MyDay installation. For conceptual information about using the DEM and DCA applications, see the appropriate online help or user guide.

Specifying the core product as an accounting entity in MyDay

During the MyDay installation, you must specify the VISUAL site name as an accounting entity. This is done during the Creating security hierarchies for accounting entities step in Infor Security, and in the Specifying an account entity in Public MDM step. Enter the value you used in the Visual Instance ID field in SOA Maintenance. For more information, refer to Maintaining SOA Information.

Importing the core product delivery bundle

The delivery bundle is a collection of component templates that are part of a solution. The bundle includes templates for servers, containers, and resources that are supported by Infor. The MyDay delivery bundle contains templates of all the standard components that are installed by the MyDay installer. A delivery bundle for a core product such as ERP or FMS typically contains only the core component template. For an integration between MyDay and a core product, you must import the delivery bundles of both products. You imported the MyDay delivery bundle during the installation of MyDay. To import the core product delivery bundle: 1 The delivery bundle for this product is stored in the Extensions directory on your VISUAL install DVD. Copy the delivery bundle XML file to a local folder. Sign in to the Infor Deployment, Configuration, and Administration application using the URL, user ID and password you defined for the MyDay administrator during the MyDay installation. Click Deployment Configuration. Click Templates and then Delivery Bundles in the left pane. The Delivery Bundles page is displayed. Click Import in the upper-right corner of the page. Browse for the core product delivery bundle file that you copied in step 1. Click Import and wait for confirmation that the import process completed successfully.

3 4 5 6 7

Generating the core product deployment

To access the deployment configurator and generate a default deployment for the ERP delivery bundle, follow these steps: 1 2 Select Deployment Configuration, Deployment Builder, Configurator. In the Delivery Bundle field, select the core product delivery bundle that you imported in the previous section

Infor ERP VISUAL MyDay Integration Guide

16 | Setup and configuration

In the Server area, specify Use Existing and select the application server instance that was created during the generation of the MyDay deployment. In the Container area, specify Use Existing and select the container instance that was created during the generation of the MyDay deployment. In the Database area, specify New to create a new database instance for the core product, separate from the MyDay database instance. Specify this information: Template Specify MSSQL for SqlServer databases or ORACLE for Oracle databases. ID Specify the logical ID (LID) of the core product database resource, for example infor.visual.vmfg654. Hostname Specify the hostname of the computer where the core product database runs, for example server2.infor.com. Port Specify the port number of the core product database. Username Specify the user name used to log into the core product database. Password Specify the password used to log into the core product database. Note Infor does not recommend that you share a database server for the core product and for MyDay. If the core product and MyDay do share a database server, you can select an existing database resource that was created during the generation of the MyDay deployment.

Click Check Database in the upper-right corner to test whether the connection to this database resource is successfully established. In the Component area, specify the Preferred name information. DCA automatically supplies the first two nodes of the name (for example, infor.visual) based on the selected template, so you specify only the last local node. For example, if your core product is installed and configured with the logical ID infor.visual.server2_ssvm654, specify server2_ssvm654. Note This name must be lowercase, and all three nodes of the full ID must match the logical ID configured for the core product. This value must also match the fortress.id value of the core product, which in most cases is found in the fortress.properties file of the core product installation. If you do not enter the appropriate value, you will have problems during the routing and delivery of messages.

Click Generate. The Configurator displays a pop-up window with the list of components that it will generate. Review the actions that will be performed. If any error notifications are listed, click Close to return to the Configurator, correct the errors, and click Generate again.

10 Click Confirm to generate the default core product deployment. 11 Select Deployment Configuration > Deployment Builder > Components. 12 Select the component with the ID [lid_prefix].[preferred_name] from the Components list view, where [lid_prefix] is the logical ID prefix of your core product and [preferred_name] is the value that was specified for the Preferred name field in step 7, for example, infor.visual.server2_ssvm654 13 If the information in the database fields of this component matches that of your core product database, you have finished generating the ERP deployment. If the fields do not match:

Infor ERP VISUAL MyDay Integration Guide

Setup and configuration | 17

a b

Click Edit. Specify this required information on the PROPERTIES tab: Schemaname Specify the ERP database name. Username Specify the user name used to log into the ERP database. Password Specify the password used to log into the ERP database.

c d

Click Check Database to test whether the connection to this database resource is successfully established. Click Submit.

Configuring the audit of messages from components

Auditing of components is helpful when you must debug the system or track messages, but consider the performance trade-off. When auditing is enabled, the volume of messages handled by Infor On-Ramp is at least double its normal amount. Therefore, unless you have concerns or special needs, we recommend that you do not enable auditing during this installation process. Later, if necessary, you can enable auditing of messages going into specific components only by modifying the CSIAudit component and then sending an updated deployment to Infor On-Ramp. We recommend that you do not enable auditing during initial data loads, when the volume of messages is likely to be higher than the day-to-day transactions that the system will handle later. To configure the CSI-Audit component to audit messages from other components: 1 2 3 4 5 Click Components. Select the CSI-Audit component and click Edit. Click the Audits tab. Click New. In the pop-up window, select the component to audit. Select All Messages to audit all the messages from this component. Otherwise, clear the All Messages field and select the specific messages to audit. Click OK to save your selections and close the pop-up window. Repeat steps 4 through 6 for each component to audit. Click Submit to save the component.

6 7 8

Executing deployment
Ensure that the Infor On-Ramp service, infor.container.1, is running before you perform these steps. To deploy all the components to On-Ramp: 1 Click Deployments.

Infor ERP VISUAL MyDay Integration Guide

18 | Setup and configuration

2 3 4 5

Click the button next to the <<DRAFT>> deployment in the list of deployments. Click Deploy in the upper-right corner of the Deployment <<Draft>> page. A dialog box is displayed. Specify the Name and Description of the deployment and click OK. Sign out of the DCA application.

Creating a routing
To create a routing between MyDay and the core product: 1 Sign in to the Infor Dynamic Enterprise Management application, using the URL, user ID and password you defined for the MyDay administrator during the MyDay installation. Click New on the Routings page to display the Routing (New) page. Specify a name for the routing, for example, MyDay VISUAL Routing. Click Submit. Click Select Bundles in the upper-right corner to display the Select Bundles dialog box. Select the MyDay delivery bundle, for example, MyDay 1.1.2, as Delivery Bundle 1 and select the core product delivery bundle, for example, Infor ERP VISUAL 6.5.4 as Delivery Bundle 2. If there is only one component instance for each template in the bundles, all component instances are selected by default. If there is more than one component instance, the Include field is cleared and the Component Instance field is empty. You must manually select the component instance. To do this, click on the empty Component field to display a drop-down list of available instances for this component template, and select the instance. 7 Click Generate. The lower pane in the Routing page displays all the configurable routes between all the approved component instances in DCA. Many of the mandatory routes between components are hidden. To see all the routes between all the components, click Detail Report. To see the configurable routes that are not yet used, click Unused Routes. 8 Click Approve in the upper-right corner.

2 3 4 5 6

Note A routing is created based on a single delivery bundle, or on any two delivery bundles. Therefore, for additional delivery bundles to be part of a routing, create additional routings between the appropriate delivery bundles. A routing can support only one instance of any component. Therefore, if you have multiple instances of a component, for example, multiple installations of an ERP application, you must create separate routings for each instance.

Infor ERP VISUAL MyDay Integration Guide

Setup and configuration | 19

Activating the solution

Ensure that the Infor On-Ramp service, infor.container.1, is running before you perform these steps. Activating the solution sends the routing defined earlier to Infor On-Ramp. To activate the solution: 1 2 3 4 5 Click Solutions in the left pane of the DEM application. Select <<Draft>> in the list of solutions. Click Activate in the upper-right corner of the Solution <<Draft>> page. A dialog box is displayed. Specify the name and description of the deployment and click OK. Sign out of the DEM application.

Restarting Infor On-Ramp

To load the new configuration, restart the Infor On-Ramp service, infor.container.1, using the Windows Service Manager application. Check the log files in the [MyDayHome]/esb/logs folder to ensure that there are no errors related to the configuration you just completed.

Configuring MyDay for drillbacks to the core product

To configure MyDay so that it allows drillbacks to the source system from the metrics and reports: 1 Sign in to the Infor MyDay Administration application using the URL, user ID and password that were set up during MyDay installation. Click Deployments. Click New. Add a row for your core product, specifying the information listed here. Name Specify the application name, for example, VISUAL. Logical ID Prefix Specify the logical ID prefix in the format infor.[appname], for example, infor.visual. Logical ID Specify the logical ID in the format lid://infor.[appname].[instance], for example, lid://infor.visual.vmfg654.

2 3 4

Infor ERP VISUAL MyDay Integration Guide

20 | Setup and configuration

Host Name or IP Address Specify the host server name or IP address for the core product. For VISUAL, enter localhost. Port Number Specify the port for the core product. For VISUAL, enter 9090. Secured Specify Yes if the drillback to the core product is secured (SSL based) or No it if is unsecured. For VISUAL, set this to No. 5 6 Click Submit Sign out of the application.

Verifying the integration

After the integration is complete, you should be able to send data from the core product to MyDay. To verify this, sign in to MyDay and set up a user. Then sign in as that user and launch several metrics and reports to verify that the installation worked and data is flowing through the system. Ensure that the metrics and reports you select are supported for your core product.

Infor ERP VISUAL MyDay Integration Guide

Troubleshooting the integration | 21

Troubleshooting the integration

Troubleshooting the data flow After the completion of the integration, if the data is not flowing all the way through the system, there are several places you can look for problems: Use the Infor Common Services Infrastructure (CSI) application to find failures related to BOD structure. For example, if a message has an invalid format, or is missing a mandatory field, CSI describes the problem. Use the Audited Messages > History function to view successful message transmissions. Use the Errors > History function to find failed message transmissions. For more information, see the CSI documentation. To troubleshoot other problems, look at the log files for the individual Infor MyDay components, which are located in the logs folder of the tomcat container where each component is deployed.

Infor ERP VISUAL MyDay Integration Guide

22 | Infor ERP VISUAL business events that generate BODs

Infor ERP VISUAL business events that generate BODs

The following table explains the events that generate a BOD from Infor ERP VISUAL: Verb Process Process Noun CodeDefinition CustomerPartyMaster VISUAL sends this BOD to On-Ramp when users
Update, add, or delete a code mapping in SOA Code Maintenance. For VISUAL Manufacturing, create, update, or delete information in Customer Maintenance. For CRM, create, update, or delete a record in Account Maintenance.

Sync

Invoice

Post a payable or receivable invoice to the general ledger.

Process

ItemMaster

Add or edit basic information in the Part Maintenance header. Change the Stocked check box selection in Settings. Add or edit part notations. Add or edit information on the Part Maintenance Costing tab, such as ABC Code, material cost, labor cost, burden cost, and service cost. Add or edit information leadtime (in days), order policy, order point qty, min/max order qty, safety stock qty, order up to qty, and days of supply on the Part Maintenance Planning tab. Add or edit information on the Part Maintenance Order Mgt tab, such as HTS code, material code, part aliases information, substitute parts information, and cross selling parts information. Add or edit information\ the default NMFC code ID on the Defaults tab. Add or edit information the tariff code or VAT code on the Intrastat tab. Add or edit information for the part unit of measure in Unit of Measure Conversions. Add or edit information in Part Location Maintenance.

Infor ERP VISUAL MyDay Integration Guide

Infor ERP VISUAL business events that generate BODs | 23

Verb Process

Noun Location

VISUAL sends this BOD to On-Ramp when users

Add or edit entity, company name or address information in Application Global Maintenance. Add or edit warehouse name or address information in Warehouse Maintenance. Add or edit addresses in Vendor Maintenance. Add or edit addresses in Customer Maintenance. In CRM, add or edit addresses in Account Maintenance.

Sync

Opportunity

For CRM users only: Create, update or delete an opportunity in Opportunity Maintenance.

Sync

PayableTransaction

Post a payable invoice. Adjust the Paid to Date and Balance Due (VISUAL controls these fields). Create a Credit Memo. Delete a payment. Post an unapplied payment.

Process

Person

Create or update information in Sales Rep Maintenance. Create or update certain BODs that contain information about a person such as ItemMaster (planner and buyer), ProductionOrder (planner), Requisition (requestor party), and PurchaseOrder (buyer). In CRM, create or update information in Quota Maintenance.

Process Sync Sync

Personnel ProductionOrder PurchaseOrder

Create or update information in Employee Maintenance. Create or update work order information in the Manufacturing Window. Create or edit a purchase order. Generate a purchase order from an RFQ, requisition, or planned order. Copy an existing purchase order to create a new purchase order. Receive a quantity that changes the purchase order received quantity or status.

Sync

Quote

Create or edit a quote in the Estimating Window. Create or edit unit price or quantity in the Quote Line Item Price dialog box. In CRM, create or edit information in Quote Maintenance.

Sync

ReceivableTransaction

Post a receivable invoice. Adjust the Paid to Date and Balance Due (VISUAL controls these fields). Create a Credit Memo. Post an unapplied cash transaction. Delete a cash receipt.

Infor ERP VISUAL MyDay Integration Guide

24 | Infor ERP VISUAL business events that generate BODs

Verb Sync

Noun ReceiveDelivery

VISUAL sends this BOD to On-Ramp when users

Create or edit information in Purchase Receipt Entry. Create or edit return information in Shipping Receipt Entry. Generate Work Order Receipts and Work Order Issue Returns Create or edit Consignment Receipts

Sync Sync Sync

Requisition RFQ SalesOrder

Create or edit information in Purchase Requisition Entry. Create or edit information in RFQ Entry. Create or edit information in RFQ Vendor Quote. Create or edit information in Customer Order Entry. Generate a customer order from a quote. Copy a customer order to generate a new customer order. Post an invoice related to the customer order.

Sync

Shipment

Create or edit information in Shipping Entry Create or edit information in Customer Order Entry for the customer order associated with the shipping entry Create or edit address information in Carrier Maintenance for the carrier selected in Customer Order Entry. Create or edit information in Customer Maintenance for the customer associated with the shipment.

Process

SupplierPartyMaster

Create or edit information in Vendor Maintenance

Infor ERP VISUAL MyDay Integration Guide

Data maps | 25

Data maps
Use the documents in the Mapping Reports ZIP file, provided on Infor365, to map information between Infor ERP VISUAL database tables and the elements of each BOD used with MyDay. The documents also allow you to trace information between the VISUAL database and certain MyDay metrics or databases. The ZIP file contains these files: PDF documents that explain the mapping between VISUAL and: BOD elements and attributes MyDay export services MyDay metrics

The PDFs were produced using the report design files in the ZIP. Note: The mappings described in the PDFs may not be currently used in supported metrics and reports. Please consult the list of metrics and reports currently supported by VISUAL data. A Readme document that explains how to set up the report design files and data sources, in case you want to create custom reports that are filtered to show only certain data from the PDFs. An XML document that contains data mapping information between VISUAL database tables and the elements of each BOD used with MyDay. The XML document also contains notes that describe calculations or default values used in the BOD elements, and it notes the windows where the data appears in VISUAL. This XML document is intended to be used as a data source for the report design files. Infor Reporting report design files that you can use to create mapping reports. The data sources for these reports are the XML document and several MyDay databases. You can filter on columns in these reports to search for a specific MyDay metric or export service, a specific BOD element, or a specific VISUAL table or window. You will find this information especially helpful if you are used to developing custom reports for your ERP and you are interested in extending MyDay with new custom reports based on information in MyDay's centralized, SOA-enabled reporting database. Infor reserves the right to change Business Document structures in future versions. Although Infor will make every attempt to provide backward compatibility, custom integrations built on a specific version of Business Documents may need to be reworked to be compatible with newer versions of SOA components.

Infor ERP VISUAL MyDay Integration Guide

26 | Data maps

Metrics and reports supported by VISUAL data

A list of MyDay metrics and reports that are currently supported by VISUAL data is available in the VISUAL documentation area of Infor365.

Infor ERP VISUAL MyDay Integration Guide