syteline_myday_integrationguide

Infor ERP SyteLine

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 SyteLine 8.01, Infor MyDay 1.01.00 Publication Date: 16 January 2009

Contents | 3 of 15

Infor ERP SyteLine MyDay Integration Guide

Contents

About this guide................................................................................................................................ 4 Intended audience......................................................................................................................... 4 Prerequisite................................................................................................................................... 4 Organization.................................................................................................................................. 4

Setup and configuration................................................................................................................... 5 Prerequisites ................................................................................................................................. 5 Setting up Infor ERP SyteLine ...................................................................................................... 5 Connecting Infor ERP SyteLine to Infor MyDay ............................................................................ 7 Setting up Infor MyDay for drillback to Infor ERP SyteLine ........................................................... 9

SyteLine business events that generate BODs ............................................................................ 10 Data maps ........................................................................................................................................ 15

Metrics and reports supported by SyteLine data......................................................................... 15

4 of 15 | About this guide


About this guide

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

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

Prerequisite 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 Service Oriented Architecture (SOA) and defines common terminology. The Infor Open SOA Overview Guide also includes a list of related documents and information on how to contact support.

Organization The Infor ERP SyteLine MyDay Integration Guide includes these sections:

Setup and Configuration lists the tasks that must be done before information flows from one product to the other.

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 SyteLine tables.

Setup and configuration | 5 of 15


Setup and configuration

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

Prerequisites Make sure you have installed and configured all the necessary hardware and software for all of the components. For more information, refer to these documents:

Infor MyDay Installation and Configuration Guide

Infor ERP SyteLine Installation Guide

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

Set up the logical ID and BOD replication

1 On the Intranets form, create a new intranet for Infor On-Ramp, with the following settings:

a In the Intranet field, enter the name to identify the intranet, for example: InforBUS.

b In the Description field, enter an appropriate description, for example: Infor On-Ramp connection.

c Select the External check box.

d On the General tab, from the Transport drop-down list, select ESB.

2 On the Sites/Entities form, create a logical "site" for the Infor On-Ramp:

a In the Site field, specify a name to identify this site as your On-Ramp site, for example: InforBUS. Specify an appropriate Site Name and Description.

b In the Type field, select Site.

c In the Intranet Name field, select the intranet you created in Step 1.

d On the Site User Map tab, map the following:

• From Site – Specify the local site, for example OH.

6 of 15 | Setup and configuration


• User Name - Set this field to the user ID that Infor On-Ramp will use to log into SyteLine. This user must already be set up on the SyteLine Users form at the local site.

3 On the Sites/Entities form, configure the local site (for example, OH) to generate and/or receive business object documents (BODs).

a On the General tab for the local site record, specify the Message Bus Logical ID for the site. This identifies the SyteLine site to Infor On-Ramp. Specify it as lid://infor.syteline.site where site is the name of the local site, for example lid://infor.syteline.oh. The logical ID must be all lowercase. Note: The logical ID entered here must match the resource component name defined in Infor DCA for this SyteLine site, as described on page 8.

b In the Link Info tab for the local site record, add an entry with the To Site set to the On-Ramp site (for example InforBUS).

4 Use the Tenant ID value on the Process Defaults form to specify the tenant ID. Currently you must leave this value blank so that it defaults to infor.

5 On the Replication Rules form, create a new rule:

− From the Source Site drop-down list, select the local site you configured in Step 3.

− From the Target Site drop-down list, select the On-Ramp site you created in Step 2.

− From the Category drop-down list, select ESB.

− From the Interval Type drop-down list, select any option except Transactional.

6 On the Replication Management form, click Regenerate Replication Triggers.

Note: Infor has “turned off” some BOD definitions for this release by selecting some Skip check boxes in the ESB replication category, found in the Replication Categories form. Selecting the check box ensures that the BOD is never generated. At a later date, you may be instructed to turn on these BOD definitions to enable integration to new metrics, reports, or products.

Set up single-click deployment

Make sure SyteLine single-click deployment has been set up, as described in the SyteLine Installation Guide. The single-click deployment is used when drilling back from MyDay to SyteLine.



Set up codes and fields

If you are upgrading from a version of SyteLine prior to 8.01, make the following changes in order to ensure BOD generation:

Form Updates Countries Make sure existing country names are mapped to

the appropriate ISO country codes and names on the Countries form. When adding new countries, we recommend that you use the ISO definitions for the countries.

Currency Codes Make sure existing currency codes and descriptions are mapped to the appropriate ISO currency codes and descriptions on the Currency Codes form. When adding new currencies, we recommend that you use the ISO codes and definitions.

Delivery Terms Make sure existing delivery terms codes are mapped to the appropriate Incoterms codes on the Delivery Terms form. When creating new delivery terms, we recommend that you use the Incoterms definitions for the terms codes.

Unit of Measure Codes Make sure existing U/M codes and descriptions are mapped to the appropriate ISO U/M codes and descriptions on the Unit of Measure Codes form. When adding new U/Ms, we recommend that you use the ISO codes and definitions.

Run the Replication Document Data Request Utility

To perform an initial load of SyteLine data into BODs that are placed in the Replication Documents Outbox, run the Replication Document Data Request Utility at each site. Select Initial Load when running the utility to ensure that the BODs are loaded in the proper order. See the SyteLine online help for more information about the utility.

After the data is loaded initially, SyteLine sends updates automatically when users change certain data or certain transactions occur in SyteLine. For a list of the events that generate BODs, see See “SyteLine business events that generate BODs” on page 10.

Connecting Infor ERP SyteLine to Infor MyDay During the MyDay installation, you set up the data related to your ERP system, using the steps in the MyDay Installation Guide.

Create and Deploy a Routing Definition

Use the information provided here to specify required ERP data during the “Creating and Deploying a Routing Definition” step of the installation process.

8 of 15 | Setup and configuration


1 Import the enterprise template - Import the enterprise template that is provided for SyteLine integrations, currently found in [MyDayPackage]\Installer\etc\SampleEnterpriseTemplate.xml. Note: The appropriate file will, at some point, be available from the online registry site.

2 Create a SyteLine database resource instance - The resource for your SyteLine site database connection should include the following settings:

− Template - Specify MSSQL.

− ID - Specify syteline.

− Description - Specify a description of the resource, for example SyteLine database server.

− Hostname – Specify the machine name used in the URL to connect to the SyteLine database, for example: eagle.infor.com.

− Port – Specify the port used in the URL to connect to the SyteLine database, for example: 8080.

− Schemaname – Specify the SyteLine application database name, for example: OH_App.

− Username and password - Specify the user name and password used to log on to the SyteLine database.

− URL - This field contains the SyteLine database server, port, and database name, in this format: jdbc:jtds:sqlserver://dbserver:port/db_name For example, jdbc:jtds:sqlserver://eagle.com:8080/OH_App

3 Create a component instance - The component instance for the SyteLine database resource should include the following settings:

− Template - Specify SyteLine.

− Deployed in Container - Select infor.container.1.

− ID - Specify the site name, for example, oh. This name must be lowercase. The full component instance name shown on the COMPONENT page (infor + resource name + site name) should match the logical ID defined in SyteLine, minus the “lid://” prefix (see page 6). Thus, if the SyteLine logical ID is “lid://infor.syteline.oh” specify “oh” here.

− Description - Specify a description, for example, SyteLine OH database.

− Error component - Specify infor.csi.local.

− poller.deleteProcessedMessages - Specify false to allow for an audit trail during initial testing. This setting controls the deletion of processed messages from the On-Ramp tables.

− Database – Select the SyteLine database resource created in Step 2.

− Schemaname – Specify the SyteLine application database name, for example: OH_App.

− Username and password – Specify the user name and password used to log on to the SyteLine database.



4 Create a routing - Specify one or more routings that the Infor On-Ramp uses to move data between SyteLine and other Infor applications such as BIS and MDM.

Specify the site as an accounting entity in MyDay

During the “Specifying an accounting entity” steps of the installation process (in Infor Security and in PublicMDM), specify the SyteLine site name as the accounting entity.

Setting up Infor MyDay for drillback to Infor ERP SyteLine If you want users in Infor MyDay to be able to drill back to SyteLine, you must create drillback views and links to the ERP system, as described in the MyDay Administration Role User Guide.

To set this up, add an entry for SyteLine in the MyDay Deployments tab with these values:

Field Value Name SyteLine

Logical ID Prefix infor.syteline

Logical ID lid://infor.syteline.site where instance is the site name, for example oh. This should match the logical ID defined in SyteLine.

Host Name or IP Address SyteLine host server name or IP address

Port Number (blank)

Secured No

10 of 15 | SyteLine business events that generate BODs


SyteLine business events that generate BODs

This list explains the events (user actions) that generate a BOD from SyteLine:

Verb Noun User action to generate the BOD Sync AccountingChart Run the Replication Document Manual Request Utility

with AccountingChart selected. (This should be done once per site, after the Chart of Accounts is set up at the site.)

Sync BillofResources Perform a cost rollup in these forms: Current BOM Cost Roll Up (current item BillOfResources BOD)

Single Level Current BOM Cost Roll Up (current item BillOfResources BOD) Roll Current Cost to Standard Cost (financial standard BillOfResources BOD)

Process ChartOfAccounts Create or update an account record in the Chart of Accounts form

Process CodeDefinition Add a Certification/License Add a Commodity Code Add a Customer Type Add an Education Major Add or update an INCO Delivery Term on the Delivery Terms form

Add an Inventory Adjustment Reason Code Add or update an ISO Country code on the Countries form

Add or update an ISO U/M on the Unit of Measure Codes form

Add an Obsolete Slow Moving Code Add a Position Add a Province/State Add a Shift ID on the Scheduling Shifts form Add a Skill Add a Tax Code of type Exempt Add a Tax Jurisdiction Add a Training Course Add a unit code on the Unit Code 1 - 4 forms Add a Work Experience

BODs for some other codes, such as Language IDs and cost methods, are automatically generated when the the Replication Document Manual Request Utility is run

SyteLine business events that generate BODs | 11 of 15


Verb Noun User action to generate the BOD Process Currency Add or update a Currency Code

Process CurrencyExchangeRateMaster Add or update a Currency Rate

Process CustomerPartyMaster Change any information on the Customers form Change any information on the Ship Tos form

Process FinancialCalendar Change any information on the Accounting Periods form Run the Change Reports To Entity utility

Sync GLMovement Run the Change Reports To Entity utility Run the Copy Balances to Budgets utility Modify Chart of Accounts Budget and Plan information Run the Rebalance Ledger Period Totals utility Run Ledger Posting for Journals Run the Mass Journal Posting utility

Sync InventoryAdjustment Perform Quantity Adjustment Perform Miscellaneous Receipt or Miscellaneous Adjustment

Perform Cycle Count Posting - one BOD is generated for each combination of item, warehouse, and location where the quantity on hand has changed

Perform Physical Inventory Posting - one BOD is generated for each combination of item, warehouse, and location where the quantity on hand has changed

Sync Invoice Print and post an invoice through the Consolidated Invoicing form

Post an invoice through the Invoice Posting (A/R) form

Process ItemMaster Make any change to an item on the Items form Add or change an item description on the Multi-Lingual Item form

Process Location Create a new Warehouse or Location Update General Parameters form (creates a Location BOD with the site as the location)

Sync PayableTransaction Generate a new voucher from any of these forms: Generate A/P Transactions, A/P Recurring Voucher Generation, Generate Landed Cost Vouchers, A/P Vouchers and Adjustments, Voucher Builder

Change the voucher authorization status on the A/P Vouchers and Adjustments or Voucher Authorization forms

Post a voucher through the A/P Voucher Posting form Post a payment from any of these forms: A/P Check Printing/Posting, A/P Draft Printing/Posting, A/P EFT Posting, A/P Wire Posting

Set or release a Hold status on a voucher from the A/P Posted Transactions Detail form



Verb Noun User action to generate the BOD

Process Person Add or update information about a salesperson or sales manager on the Salespersons form

Update information related to a salesperson on the Employees form (for employee sales people) or Vendors form (for outside sales people)

Sync ProductionOrder Change a job or production schedule release status from Firm to Released or from Released to Complete (in these cases, multiple BODs are sent for ProductionOrder, Routing, BOM and Operation)

Change a job or production schedule release status from Complete to Released, from Released to Stopped, or from Stopped to Released (in these cases, only the ProductionOrder BOD is sent)

Change any of the following job data: Qty Released, Qty Complete, Start Date or End Date

Delete a job or production schedule release, where the job status is not Firm or the production schedule release status is not Planned

Sync ProductionReceiver Change the Quantity Complete for a job or a production schedule

Perform a material withdrawal for a by-product

Sync PurchaseOrder Print the Purchase Order Report Print the Builder Purchase Order Report Change the Purchase Order status to Complete Print a Change Order Report Delete a Purchase Order

Sync Quote Change the Estimate status to Quoted Delete an Estimate

SyteLine business events that generate BODs | 13 of 15



Sync ReceivableTransaction Generate an invoice for customers with an ‘Open Item’ balance method. The status is set as Open.

Generate a debit memo/finance change for customers with an ’Open Item’ balance method. The status is set as Open. If all or part of the debit memo/finance charge is left unapplied, a second BOD is generated. Similar transactions are grouped and shown under an invoice number ‘0’ with a status of UnappliedCash

Make a payment and apply it to an invoice for customers with an ‘Open Item’ balance method. The status changes to Paid. If all or part of the payment is left unapplied, a second BOD is generated. Similar transactions are grouped and shown under an invoice number ‘0’ with a status of UnappliedCash.

Generate a credit memo and attach it to an invoice for customers with an ‘Open Item’ balance method. This changes the status to Paid. If all or part of the credit memo is left unapplied, a second BOD is generated. Similar transactions are grouped and shown under an invoice number ‘0’ with a status of UnappliedCash.

Create an invoice, payment, credit memo, debit memo or finance charge transaction for a customer with a ‘Balance Forward’ balance method. The system maintains one balance under invoice number ‘0.’ Its status is set as follows: for a debit balance, the status is set as Open; for a zero balance, the status is set as Paid; for a credit balance, the status is set as UnappliedCash.

Sync ReceiveDelivery Make changes to a Project, Job, Customer Order (with a negative quantity), Purchase Order, RMA, Production Order or Transfer Order that cause a material transaction to occur

Sync Requisition Print the requisition on either the Purchase Requisition Report or the PO Requisition Report forms

Convert a requisition to a purchase order Convert additional items on an existing requisition (in this case, another BOD is created, replacing the original BOD)

Delete a requisition

Sync SalesOrder Print the Customer Order Verification Report Delete an order




Sync Shipment Make changes to a Project, Job, Customer Order, Purchase Order (with a negative quantity), RMA, Production Order or Transfer Order that cause a material transaction to occur

Sync SupplierBalance Change the status or vendor on a Purchase Order Change the price on a Purchase Order Line

Process SupplierPartyMaster Add or update Vendor information Update the vendor’s address information Update Bank Address information

Data maps | 15 of 15


Data maps

Use the documents in the ZIP file provided on Infor365 to map information between SyteLine database tables and the elements of each BOD used with MyDay and to trace information between the SyteLine database and the Infor Business Information Services (BIS) database. The ZIP file contains these files:

An XML document that contains data mapping information between SyteLine 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 the forms/windows/screens where the data appears in SyteLine.

Two Infor Reporting report design files that allow you to build reports based on the XML document and a linked BIS database that contains BOD-to-MyDay export service mapping. You can filter on columns in these reports to search for a specific MyDay export service, a specific BOD element, or references to a specific SyteLine table or form/field combination.

A readme file that explains how to install the report templates and set up the XML and database as data sources for the reports.

A PDF file containing all mapping information between SyteLine and BODs. This PDF was produced using one of the report design files in the ZIP.

A PDF file containing all mapping information between MyDay Export Service to SyteLine BOD mapping and descriptions. This PDF was produced using the other report design files in the ZIP.

You will find this information especially helpful if you are used to developing custom reports based on SyteLine and are interested in extending MyDay with new custom reports based on information in MyDay's centralized, SOA-enabled reporting database.

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