Pando

Confidentiality Notice:
This document contains confidential information that is proprietary to Quaking Aspen Pvt. Ltd. (“Pando”). Distribution of this document or communication of its contents in part or whole to any third party is strictly prohibited without prior written consent from Pando.

Introduction 

The Integration Guide Document is a guideline for the Integration Partner to understand the requirements of Pando in relation to each of the Interfaces (Masters and Transactions). 

This document contains the following:
Interfaces 
Master Data Interfaces 
Manage related Interfaces
Payment Related Interfaces

Interfaces 

The following are the Interfaces that would be required between the Client ERP and Pando:

This document contains the following chapters

• Introduction 
• Interfaces 
• Master Data Interfaces 
• Transporter Master
• Manage related Interfaces 
• Payment Related Interfaces
• Freight Provision Posting 
• Freight Invoice Posting
• Payment Status

This document comprises of the following chapters: 

1.Master Data Interfaces 

2.Manage related Interfaces  

Master Data Interfaces 

Consignee Master 

Direction: Client ERP to Pando 

● Primary Consignees - Destination Location Codes for Primary Movement available as per Client ERP system.

● Secondary Consignees - Destination Location Codes for Secondary Movement available as per Client ERP system - 

Requirements 

• Creation of new consignee should flow to Pando - all required fields along with the consignee reference ID 
• Update of details of existing consignee (even if select fields are updated) should flow to Pando - all fields required by
  Pando to flow; Pando will update all the fields for that consignee reference ID. Flow to be triggered only if Pando related fields are updated. 
• Preceding zeros in Consignee reference ID (if any) should be removed at the middleware so that only the number is available on Pando
• Consignees in all status should flow to Pando 

Trigger 

● Suggested Trigger from Pando: Immediate data push to Pando on Create and Change 

Payload - Json 

{ 

"data": [ 

{ 

"name": "Plank And Weave Retail Private Limi", 

"reference_number": "8109862", 

"address": "2007 - 2008, ISHANYA", 

"city": "PUNE",

"state": "Maharashtra", 

"pincode": "411006", 

"region": "13", 

"mobile_number": "9879525119", 

"email": "purchase@plankandweave.com", 

"customer_type": "Customer Site" 

} 

] 

} 

Endpoint: <domain_name>/api/erp/consignee 

Material Master 

Direction: Client ERP to Pando 

Only Materials which are required for Pando should flow 

Requirements

• Creation of new material should flow to Pando - all required fields along with the material SKU code 
• Update of details of existing material (even if select fields are updated) should flow to Pando - all fields required by Pando to flow; Pando will update all the fields for that material SKU code. Flow to be triggered only if Pando related fields are updated. 
• Preceding zeros in Material SKU Code (if any) should be removed at the middle ware so that only the code is available on Pando 

Trigger 

• Suggested Trigger from Pando: Immediate data push to Pando on Create and Change 

Payload - Json 

{ 

"data": [ 

{ 

"name": "Plank And Weave Retail Private Limi", 

"reference_number": "8109862", 

"address": "2007 - 2008, ISHANYA", 

"city": "PUNE",

"state": "Maharashtra", 

"pincode": "411006", 

"region": "13", 

"mobile_number": "9879525119", 

"email": "purchase@plankandweave.com", 

"customer_type": "Customer Site" 

} 

Endpoint: <domain_name>/api/erp/material

Other Generic Masters maintained only on Pando directly 

• Depot Master - List of Nodes - Factories / Depots 
• Transporter Master - List of Transporter/vendor master 
• Rate Matrix (Contract) - Base Freight Charges for a particular lane
• Vehicle Type Master - Vehicle Type and Capacity of vehicle 
• Detention Master - Detention & Transit Delay related charges
• Loading / Unloading - Charges for Loading / Unloading  
• SLA Penalty - Placement Delay penalty related charges 

The details of the above masters are available in the Blueprint Document for the user.

Transporter Master

Direction: ERP to Pando

• Each Transporter Reference ID is mapped to ONLY ONE GST Code (One GST Code, One GST Type - FCM/RCM and One GST Rate. If a Transporter is billing from multiple locations (multiple GST IDs / multiple GST Types, multiple GST Rate), then they are configured as multiple transporter IDs in the Client ERP. Client to check in the system and confirm.

• State in Transporter Master and the State is Depot Master would determine the CGST+SGST or IGST billing. Hence it is important to have the spellings of the states to be matching across these masters. Client to check in the system and correct data.

Requirements

• Creation of new transporter should flow to Pando - all required fields along with the transporter reference ID

• Update of details of existing transporter (even if select fields are updated) should flow to Pando - all fields required by Pando to flow; Pando will update all the fields for that transporter reference ID. Flow to be triggered only if Pando related fields are updated.

• Preceding zeros in Transporter reference ID (if any) should be removed at the middle ware so that only the number is available on Pando

Trigger

• Suggested Trigger from Pando: Immediate data push to Pando on Create and Change

Payload - Json

{

  "data": [

    {

      "name": "Stellar Innovative Transportation",

      "reference_number": "940271",

      "city": "Howrah",

      "state": "West Bengal",

      "pincode": "711302",

      "contact_name": "Stellar Innovative Transportation",

      "contact_mobile": "8585086862",

      "contact_email": "mukesh.gupta@stellarvaluechain.com",

      "pan_number": "AACCI5750L",

      "gst_type": "FCM",

      "percentage": "12"

    }

  ]

}

Endpoint:     <domain_name>/api/erp/transporter

Manage related Interfaces 

Delivery Picklist 

• Direction: Client ERP to Pando.
  Delivery Picklist should have the list of materials to be moved from a source to a destination. This should be a Dispatchable Lot (Material confirmed post stock check of the Sales Order) used for planning the truck.
  
  
• Based on the materials received and the constraints maintained on Pando, Optima would plan clubbing and prepare an Indent Plan. 

Trigger 

The trigger would be the following: 

• Client ERP to send all Open Deliveries at a given point in time (scheduled). Pando to schedule Optima Run at a scheduled point of time. Optima schedule to be checked based on time taken to load all deliveries from Client ERP to Pando. 

Requirements 

Client ERP should ensure that only Open Deliveries are sent to Pando 

What is an Open Delivery?

All Deliveries available in the Client ERP with following conditions: 

• Deliveries for which an Indent ID is BLANK should be sent to Pando. (this mapping is detailed in the Modified Picklist Interface below)

Payload – JSON

Modified Picklist 

Direction: Pando to Client ERP. 

• Modified Picklist should have the list of materials to be moved from a source to a destination as given in the delivery picklist with an Indent ID map.
  
  
• Indent ID is a 16+ digit alpha-numeric code with hyphens (ABCD-1012-O-1001) ● Definition: Client ID - Depot ID - (O=Optima, M=Manual - Running number) 

Trigger 

At creation of an Indent. The data for each Indent is sent as and when the Indent Creation (post Optima Run) happens through email. 

Excel file structure

Material Invoice 

Material Invoice should flow from Client ERP to Pando. 

• Material Invoice creation in SAP flows to Pando against Pando Indent ID ● Cancellation of Material Invoice does not flow into Pando. If Material Invoice is cancelled and re-invoiced, the revised Material Invoice will flow into Pando, the final Material Invoice is updated on Pando. 
• Material Invoice can be revised on Pando until Indent reaches ‘Delivered’ status. 

Trigger 

Since Material Invoice is required for LR Print & Truck-Out, Material Invoice should flow from Client ERP to Pando instantly. After Material Invoices for all Materials in that Indent is created in Client ERP. Note: This variation can be adopted if Client ERP is NOT able to provide (only) one Material Invoice per Pick-Up Drop combination.

Important: All Material Invoices for that Indent has to flow into Pando at the same time. Hence, SAP has to send Material Invoice to Pando only after creation of the material invoice for the last delivery in that Indent.

Requirements 

• Indent ID mapped against a Delivery Number is carried on to the Material Invoice. 
• Only Material Invoices where Indent ID mapping is available is sent to Pando.
• Materials Quantities for a Material SKU Code are aggregated at the following level and sent to Pando: 
  • Indent + Material Invoice Number + Material SKU Code + MRP 
  • This would ease the EPOD update on Pando 

• Material Invoice details for an Indent should flow into Pando in full.
  
  Reason: Pando updates Material Invoice for an Indent. Hence if Pando receives Material Invoice for an Indent multiple times, Pando would update the Material Invoice received in the end.
  
  Note: Presence of Indent ID mapping has to be made mandatory for creation of a Material Invoice. For the immediate period post Go-Live, if we are rolling out for select locations, it has to be made mandatory only for the locations where roll-out is happening. When Indent ID is Blank; PGI Should not be made Possible. The customer is expected to handle the enhancement.

Payload – JSON

POD flow to Pando 

Direction: ERP to Pando 

• When POD is done in Client ERP data flows to Pando. 
• To be discussed Client to identify what data has to be posted back to Pando. ● Below Payload is available to post data packets from Client ERP to Pando. 

Trigger 

• Client ERP would have its own Process of capturing POD. 

Requirements 

• POD has to be captured in Client ERP and then the data flows to Pando. 

A. Primary - GRN data to Pando

B. Vendor - GRN + Material Invoice data

Truck In to Pando 

Direction: ERP to Pando 

• Truck In done in ERP will be sent to pando to mark the truck arrival.
   

Trigger 

• When truck in action is completed ERP to send this payload to Pando 

Payload – Json

Truck Out to Pando 

Direction: ERP to Pando 

• Truck out done in ERP will be sent to pando to mark the truck dispatch. 

Trigger 

• When truck out action is completed ERP to send this payload to Pando 

Payload – JSON

Secondary - Direct dispatch to Pando 

Direction: ERP to Pando 

The delivery details and the material invoice details are sent to Pando to create Indent in Pando at dispatched status. 

Trigger 

When Shipment is created all the deliveries and material invoices related to that shipment is to be sent to Pando using this payload. 

Payload – JSON

"category": "20a", optional

Payment Related Interfaces

Freight Provision Posting 

Direction: Pando to Client ERP.

• Freight Provision is created at a Indent + Material Level based on Volumetric Weight of each Material / Weight of each Material.

• Base Freight is apportioned Material-wise

Trigger

Instant Trigger of Freight Provision interface would be done on Truck out (Dispatched Status). But still this trigger point is debatable On the BBP discussion (Since Client ERP Payment process my vary)

Requirements

• Based on the input given by Pando, Freight Provision to be created on SAP.

Payload - Json

{

  "movement_type": "1",

  "transporter_code": "940147",

  "transporter_name": "Aditiya logistic",

  "indent_number": "client-9002-O-12090",

  "total_indent_value": 720,

  "material": [

    {

      "material_invoice_number": "3021109039",

      "material_code": "LED10WBL-65KB22HB",

      "consignee_code": "8110051",

      "total_freight_provision": 720,

      "line_item_number": "000010",

      "oda_freight_charge": 0,

      "fixed_charge": 0,

      "additional_point_charge": 0,

      "miscellaneous_charge": 0,

      "loading_charge": 0,

      "unloading_charge": 0,

      "lr_charge": 0,

      "freight_charge": "720.00"

    }

  ]

}

Endpoint:    Client to Provide Url

Freight Invoice Posting

Direction: Pando to Client ERP.

• Once Freight Invoice is raised by the transporter and approved by the Bill Checker on Pando, the Freight Invoice is posted to the Client ERP for payment.

• Each Freight Invoice maybe a collection of multiple Indents.

• Freight Invoice posting is created at a Invoice + Material Level based on Volumetric Weight of each Material / Weight of each Material <to be checked with Client and confirmed>

• Final Freight Value is apportioned Material-wise

Trigger

At approval of an Invoice. The data for each Invoice is sent as and when the Invoice is approved on Pando by the Bill Checker - Live. It is not scheduled.

Requirements

• Based on the input given by Pando, Freight Invoice gets posted on Client ERP.

• Client to check detailed fields in Freight Invoice Posting Excel and confirm if all required fields are covered.

Payload – Json

{

  "transporter_code": "940183",

  "invoice_number": "11621BLL000066",

  "invoice_total": 34430,

  "invoice_date": "2021-12-17",

  "tax_code": 1,

  "tax_type": 1,

  "tax_percentage": 12,

  "hsn_sac": "996511",

  "indents": [

    {

      "indent_id": “client-9082-O-1655",

      "order_reference": "client-9082-O-1655",

      "movement": 1,

      "material_invoice_number": "1221106713",

      "sku": "000002134814512510",

      "source": "Indore",

      "source_ref_id": "9082",

      "gate_ref_id": "9082",

      "destination": "Jaipur",

      "destination_ref_id": "401618",

      "destination_gate_ref_id": "",

      "quantity": 87,

      "weight": 1067.664,

      "volume": 118.407,

      "invoice_value_freight": 5238.89,

      "invoice_value_detention": 0,

      "invoice_value_defect": 0,

      "consignee_category": "",

      "line_item_number": "000080",

      "oda_freight_charge": 0,

      "fixed_charge": 0,

      "additional_point_charge": 0,

      "miscellaneous_charge": 0,

      "loading_charge": 0,

      "unloading_charge": 0,

      "lr_charge": 0,

      "sla_delay": 0,

      "transit_delay": 0,

      "penalty": 0,

      "shortage": 0,

      "damage": 0,
"carton_damage": 0,

      "debit_adjustment": 0,

      "extra_km_charge": 0,

      "base_freight_charge": 5238.89,

      "weight_unit": "kg",

      "quantity_unit": "BOX",

      "volume_unit": "cft"

    }]}

Endpoint:     Client to provide Url

Payment Status

Direction: ERP to Pando

• Once a freight invoice is paid, the SAP is updated with a Clearing Document Number against the Posting Document Number.

• This Clearing Document Number should flow to Pando against the Freight Invoice as the Unique ID.

• Pando would update the Invoice as ‘Paid’ once Pando receives a Clearing Document Number against a Freight Invoice raised.

Trigger

Schedule (D-1). All documents cleared yesterday will flow to Pando. Or Instant trigger to Pando as and when document is posted in Client ERP – debatable on BBP discussion since client Pay process would vary.

Requirements

• No advance to be managed by Pando / Integration

• No partial invoice payment to be managed by Pando / Integration

• Pando should receive only Payment Status related to Pando, hence this has to be managed in the SAP by creating a separate Document Type for Pando related payments processed.

Payload – Json

{

"type": "1",

"reference_number": "freight invoice#",

"document_number": "",

"updated_date": "18-07-2020",

"document_type": ""

}

Endpoint: <domain_name>/api/erp/material_invoice