Proposal For TrackTraceRx-Netsuite Integration

Proposal summary 

This proposal covers the serialization process along with RF-Smart and the TrackTrace-Netsuite integration for handling the DSCSA rule. 

Requirement 

The pharmaceutical industry has been in the process of moving to serialization for all RX product for some time now.  The guidance the industry has been given revolves around EPCIS and GS1 standards and there are numerous “providers” in the marketplace for total interoperability.  We are in the process of reviewing providers to make a selection and will need your help with integration to NetSuite and RF-Smart.   

We looked over the TrackTrace documentation, and it also offers the best functionalities for serialization needs. Their open APIs appear to allow access to the majority of their functionalities. So we can integrate the same if necessary. 

Prerequisite 

• Second Source RX need to provide the import file with list of items, customer, vendors, location for the initial sync with TrackTraceRX. The Second Source RX will also need to provide all the missing and required data for integrating these records with TrackTraceRX. 

Deliverable 

To comply with the DSCSA and serialization, following actions needs to be performed in the Second Source RX account. 

• Collecting serial numbers during IR and IF creation by RF-Smart 

• TrackTrace-NetSuite integration 

Collecting serial numbers during IR and IF creation by RF-Smart 

We can use the current lot number items in the Second Sorce RX account itself for the serialization process, provided the RF-Smart should be able to track the serial numbers while receiving and picking items as of below. 

We hope RF-Smart will perform the following actions. 

Purchase order Receiving (IR creation) 

• Track the serial number in the Item Receipt (IR) creation, while receiving Lot numbered items for each item quantity. 
• So that the purchase order (PO) Receiving interface of the RF-Smart will be compatible to track the serial number upon scanning the items while receiving. 
• Once IR is created, we hope that the item and corresponding serial number will be available under the specific IR in the “RFS-mart outbound serials” tab. 
   

Sales order Picking 

• Track the serial number in the Item fulfilment (IF) creation, while picking Lot numbered items for each item quantity. 

• So that the sales order (SO) picking interface of RF-Smart will be compatible to add the serial number upon scanning the items for picking 
• Once IF is created, we hope that the item and corresponding serial number will be available under the specific IF in the “RF-Smart outbound serials” tab. 

TrackTrace-NetSuite integration 

TrackTraceRX-NetSuite integration will be done for the inbound and outbound operations. 

The authentication will be by using the API key. We assume the API key will be provided by TrackTraceRX.  

1)Inbound operations 

The flow will be like, the created PO from NS will be sent to vendor and TrackTraceRX. Vendor will send the EPCIS data with serial information to TrackTraceRX. Simultaneously, vendor will also send the items physically to Second Source RX warehouse. RapidRX will compare the electronic and physical data, and will handle the further steps. The Item receipt will be created in NetSuite by Second Source RX by using RF-smart when Items are received physically in Second Source RX warehouse. 

1.1) Item Sync: 

• Item creation, update, inactive/deletion from NetSuite will be synced to TrackTraceRX in real-time. 

• Item creation – POST /products 
• Item update/inactive – PUT /products/{product_uuid} 
• Item delete – DELETE /products/{product_uuid} 

• We will sync the Existing item (list provided by Second Source RX) from NS to TrackTraceRX. This will be a onetime initial sync. 

• We will be only considering all lot numbered items in NetSuite for the integration. 

1.2) Location sync:  

• Location creation, inactive/deletion from NetSuite will be synced to TrackTraceRX in real-time. 

• Location creation – POST /locations 

• Location Inactive – PUT /locations/{uuid} 
• Location delete – DELETE /locations/{uuid} 

• We will sync the Existing Locations (list provided by Second Source RX) from NS to TrackTraceRX. This will be a onetime initial sync. 

 
 
1.3) Vendor sync 

• The vendors creation/deletion/inactivation in the Second Sorce RX  account will be synced with TrackTraceRX in real time.  

• Only vendors flagged by Second Sorce RX in the vendor record will be taken into consideration for integration. 

• Vendor creation – POST /trading_partners 
• Vendor inactive –  PUT /trading_partners/{uuid} 
• Vendor deletion- DELETE /trading_partners/{uuid} 

• We will sync the existing Vendor (list provided by Second Source RX) from NS to TrackTraceRX. This will be a onetime initial sync. 

On the next step TrackTraceRX will receive the EPCIS information from vendor and TrackTraceRX will create shipments in their system. Rapid RX will, compare the electronic and physical data, and will perform the further steps in the inbound flow. 

We are not including the solution for, how to fetch inbound from TrackTraceRX and double Serial verification in the proposal, as we hope RapidRX will handle the same. In case of any concerns/process change, then we can consider this as change of request and implement further. 

2)Outbound operations 

2.1) Customer sync 

• The customers created/deleted/inactivated in the Second Sorce RX  account will be synced with TrackTraceRX in real time.  
• Only customers flagged by Second Sorce RX in the customer record will be taken into consideration for integration. 

• Customer creation Type CUSTOMER- POST /trading_partners 
• Customer inactivation – PUT /trading_partners/{uuid} 
• Customer deletion- DELETE /trading_partners/{uuid} 

• We will sync the existing Customer (list provided by Second Source RX) from NS to TrackTraceRX. This will be a onetime initial sync. 

2.2) Sales order(SO) Sync 

• Second Sorce RX will create Sales orders in NetSuite account. The sales order creation, update, delete will be synced to TrackTraceRX in real time. 

• Sales order create TYPE SALES- POST /transactions/{transaction_type} 
• Sales order update – PUT /transactions/{transaction_type}/{transaction_uuid} 
• Sales order delete – DELETE /transactions/{transaction_type}/{transaction_uuid} 

• This integration will happen only for the Customers and only for the items that are already integrated with TrackTraceRX. 

2.3) Sales order(SO) close sync 

Second Sorce RX will close the Sales orders in NetSuite account by clicking the close order button. The closed orders will be deleted from TrackTraceRX on a scheduled basis. The closed order sync will only happen for the sales orders which are already synced to TrackTraceRX. 

• Sales order delete – DELETE /transactions/{transaction_type}/{transaction_uuid} 

2.4) Item fulfilment(IF) Sync 

Warehouse manager will create the Item fulfilment in NetSuite using RF-Smart for the sales order. During the creation the serial information will be updated in “RF-Smart outbound serials” tab of IF by RF-Smart. The Item fulfillment will be created in the shipped status. 

Once the IF is created in NetSuite, we will send the item, invoice details including the serial information data to TrackTraceRX. This action will be Realtime/scheduled. This will create a shipment picking in TrackTraceRX. 

• Item Fulfillment create – POST /shipments/picking/ 
  – POST /shipments/picking/{picking_uuid}/pick_and_close 

Assumptions 

• We assume the “RF-Smart outbound serials” tab custom record look like below and the table added by RF-smart can be fetched using suite script. 

Item	Serial Number
Item 1	1211
Item 1	1222
Item 2	1223

• We assume that the TrackTraceRX APIs can be used from the documentation Swagger UI (tracktraceweb.com) 
• Whenever a PO is created/updated/cancel in NetSuite, the same details will be sent to the vendor automatically as per the current functionality in the account. As it is currently happening in NetSuite, we wouldn’t need to do anything in this section. 
• Second Sorce RX will provide the import file with list of items, customer, vendors, location for the initial sync with TrackTraceRX. The Second Sorce RX will also provide all the missing and required data for the integration. 
• We assume that only one IF will be created for each sales order. There won’t be multiple IF created for the same SO. And we hope the IF will be created in shipped status and invoice will also be autogenerated along with IF. 

• We will initially implement in the NetSuite SB and TrackTraceRX test account. After your confirmation, we can establish connection between NetSuite production and TrackTraceRX production. 
• Item receipt will be created by Second Source RX after the verification of serial number. So, we will not be syncing the Item receipt from TrackTraceRX. 
• Assume that sales order cancel will not happen in Second Source RX. So, not needed to be considered in the NS-TrackTraceRX integration.  

Note 

• We will handle the error cases in the corresponding records. The user can resync the record by correcting the issue. If the sync is happened in the scheduled process, we will consider the corresponding record in each scheduled process until it get synced successfully. 

Scope Limitation / Terms & Conditions 

• IF update/deletion is not considered for integration with TrackTraceRX in the scope as this is not a case in the Second Source RX account. 
• PO is not considered for integration with TrackTraceRX in the scope as is not required for TrackTraceRX. 

• Location and vendor update is not considered for integration with TrackTraceRX in this scope. 
• Sending the PO details to Vendor is not considered in this scope as SecondResource is already doing it now. 
• Receiving(IR) and fulfilling(IF) are already tracking in TrackTraceRX. So, we are not considering separate inventory(Stock) sync. 
• We will not sync the existing list of Shipping method, tax, discount etc to TrackTraceRX. 
• We will only consider the Lot numbered Items in NetSuite for the sync with the TrackTraceRX. 

• Item Receipt creation will not be considered to sync from TrackTraceRX as it will be created by Second Source RX when the items are physically received. 
• Only newly created transactions will be considered for the integration, the existing transaction sync will not be included in this scope as it is not needed. 
• The changes outside of the proposal will be considered as additional change of request. 

Risks 

• If we face any difficulty to do item IF sync in real time, we will be doing it in a scheduled process. So, there will be a delay in syncing the IF to TrackTraceRX. 
• For SO sync, if the number of items is greater than a particular limit it may take more time to save the SO or depending on the performance, we may change it to scheduled process.  
• While sending the SO and IF details to TrackTraceRX, we will sync the details of lot numbered items only. If there are any items other than lot numbered items, then those details will not be synced with TrackTraceRX. 
• Only the SO and IF created for the synced customer will be considered for the sync.