PROPOSAL SUMMARY
This proposal outlines the scope of purchase order integration from NetSuite to BlueScope and the limitations and drawbacks of this integration.
REQUIREMENT
BlueScope team needs to integrate NetSuite with BlueScope for creating purchase orders based on the data provided from the NetSuite on a scheduled basis.
DELIVERABLES
We will be sending the purchase orders from the NetSuite to BlueScope that are created for BlueScope vendor.
The purchase orders will be sent on a scheduled basis.
Studco is having a scheduled saved search for sending the details to create the purchase orders in BlueScope. We will be using this saved search in a scheduled script and sent it to the BlueScope by using the API provided from the BlueScope.
When the scheduled script is triggered, the purchase orders will be created in BlueScope side.
The purchase order data will be sent by using the API provided by the BlueScope and the body will be similar to the sample provided. The body will be having batch numbers (serial numbers) to uniquely identify the items.
We will also create a custom record in NetSuite to store the BlueScope Material number and corresponding Studco material number along with the material description and unit of measurements for the ease of development.
When the request is processed, if an error occurs, we will be creating a custom record in NetSuite for storing the error details for the future reference. Also, Studco will be notified if an error is generated while sending the purchase order details to BlueScope through the API.
PREREQUISITES
We will require the API and JSON sample body from the BlueScope team to create the purchase orders.
ASSUMPTIONS
- We will send a single purchase order detail in a single request. If there is multiple PO, request will be sent separately.
- The script will be a scheduled script. It will be based on a schedule and not a real time. That means script will work for a particular interval of time.
- We will be using a custom record for storing the integration details like errors details.
- The unit of measurement will be taken based on the UOM value given in the material mapping sheet.
- We will be using Qauth 2.0 auth
When discussed with the technical architect, suggested the following.
Need to find how the item line number can be found when the same item is in multiple line items.
Need to confirm if this includes the kit items.
Confirm if the there exists multiple serial/lot number for an item and and how this can be handled in API.
How to identify the exact line number in the purchase order based on the lot?