M3 Integration

The incoming transactions from M3 are routed through the Kemin FTP server.  M3/InforOS generates XML files and uploads them there.   LabVantage (LV) has a scheduled task (every 15 minutes) that connects to the FTP, downloads the files, parses out the data from the XML, then creates a new M3 Transaction in LabVantage.  The sample/batch has not yet been created in LV at this point.  A user must find the appropriate transaction, complete the data entry, then click the Process button to create the LV batch.

Outgoing to M3

The SendToM3 action is called from the Historical Batches page.  There is a button in the toolbar labeled “Send To M3” that will start the process.  There is a new button to initiate the data send and an M3 status column displaying if it’s been transferred.  The green check mark shows that it has been transferred to M3 with no errors.

After clicking the Send To M3 button, another window will appear that is displaying current data for the batch and prompting input for the release.  Any data that is not accurate can be corrected by moving the batch back into Pending Release, then modified and re-released.

Expiring/manufactured dates will be pushed to M3 and updated to match LabVantage so any incorrect dates will only need to be manually updated in one place.  Dates updated in M3 will not push back to LV.

The user that released the LabVantage batch is the one that will be sent to M3, not the user that Sent to M3.  That user must have an account in M3 to release through this interface.

Manufactured Goods

The same LV batch is used for the examples below.  In the examples, the Any LV product that is not a Raw Material batch type follows the same steps.  Fields marked with a red asterisk and yellow background are require fields.

Approvals

Clicking OK will send the release to M3.  M3 expiry and manufactured dates can be updated from LabVantage using this process.

Rejections

As with the approvals, the dates will be pushed to M3.     For rejections, there is an additional rejection reason field that needs to be provided.

 


 

 

Raw Materials

The same LV batch is used for the examples below.  Fields marked with a red asterisk and yellow background are require fields.

Approvals

Clicking OK will send the release to M3.  M3 expiry and manufactured dates can be updated from LabVantage using this process.

Rejections

As with the approvals, the dates will be pushed to M3.     For rejections, there are additional fields that need to be provided.

 

Potential Issues

There are several issues that could occur.  Missing data, data in an unexpected format, connections with M3 or the FTP server, M3 data in a different status (already released, lot doesn’t exist, user doesn’t exist in M3 – shown below, etc).

Any error messages received from M3 or generated out of LabVantage will be displayed on the page after attempting to transmit the data to M3.  If there is an error, the green check will not appear on the list.

Changes made to the system

This process uses custom in house written java code as well as page configurations.

Item Type
Item Name
New/Edit
SDC Batch edit
SDC M3_IncTransaction new
SDC SystemIntegration new
Page LV_HistBatchList 
edit
Page LV_TReleaseBatchMnt 
edit
Page
M3_IncTransactionList 
new
Page
M3_IncTransactionMaint 
new
Page
ReleaseToM3 
new
Page
SystemIntegrationAuditView 
new
Page
SystemIntegrationList 
new
Page
SystemIntegrationLookup 
new
Page
SystemIntegrationMaint 
new
Page
SystemIntegrationView
new
Action

GetFTPFiles

new
Action

ProcessTransaction

new
Action SendToM3 new
Task Get M3 Files (recurring ever 15 minutes) new
Java Code (custom) 35 files new
Java library

dom4j-1.6.1.jar

new
Java library

jsch-0.1.55.jar

new
Java library

junit-4.11.jar

new
Java library

org.apache.oltu.oauth2.client-1.0.2.jar

new
Java library
org.apache.oltu.oauth2.common-1.0.2.jar
new