Fallback Data Delivery
This section includes information about the process by which orders submitted in Fallback are posted to NetSuite.
Data Delivery and Consolidation
Data delivery and consolidation occur automatically, without any interaction from an administrator. During the data delivery process, data from Fallback transactions is transferred to NetSuite. The automatic consolidation process ultimately results in a final NetSuite transaction record that represents the order submitted in Fallback. When the NetSuite transaction is created, inventory and general ledger accounts are impacted.
The data from the order submitted in Fallback is saved on the device where the order was submitted. When NetSuite is back online, and a sales associate logs in to use SCIS, the process that sends transaction data to NetSuite is initiated. The delivery process creates SCIS Fallback Session and SCIS Fallback Transmission Batch records in NetSuite.
SCIS Fallback Session and SCIS Transmission Batch Records
Administrators can view these records for reference and troubleshooting purposes:
-
SCIS Fallback Session records in NetSuite represent the session created each time a sales associate logs in to Fallback. One SCIS Fallback Session can be linked to multiple SCIS Transmission Batch records.
-
SCIS Transmission Batch records contain the original output of transaction data in JSON format. There can be multiple transactions in a Transmission Batch record.
SCIS Fallback Session and SCIS Transmission Batch records are locked. These records are intended for reference purposes only.