SCIS Integration Subtab
Is SCIS Integration Enabled
You can use this boolean to enable or disable SCIS integration with your Commerce site. From the 2025.2 release of SuiteCommerce and SuiteCommerce Advanced, this setting is disabled by default.
|
ID |
isSCISIntegrationEnabled |
|
UI location |
My Account > SCIS Integration |
|
JSON file |
ReturnAuthorization.json |
|
Configuration file (pre-Vinson) |
Configuration.js |
Location Type Mapping Store Internal ID
This string lets you define the location-type identifier that Commerce web stores use to link a transaction with an in-store purchase. 1 = store, 2 = online.
|
ID |
locationTypeMapping.store.internalid |
|
UI location |
My Account > SCIS Integration |
|
JSON file |
ReturnAuthorization.json |
|
Configuration file (pre-Vinson) |
Configuration.js |
Location Type Mapping Store Name
This string lets you add a description for the locationTypeMapping.store.internalid property.
|
ID |
locationTypeMapping.store.name |
|
UI location |
My Account > SCIS Integration |
|
JSON file |
ReturnAuthorization.json |
|
Configuration file (pre-Vinson) |
Configuration.js |
Transaction Record Origin Mapping
This array lets you set what displays in a user's account. Each transaction record origin mapping object requires the following properties:
-
ID (string) – where the purchase record came from (backend, instore, online).
-
Origin (number) – the frontend properties related to what's displayed in a user's account. This is related to the locationTypeMapping.store.internalid property.
-
Name (string) – the text displayed in the Origin column of a user's My Purchases list.
-
Detailed Name (string) – the text displayed in the Purchase Details page.
|
IDs |
|
|
UI location |
My Account > Transaction Record Origin Mapping |
|
JSON file |
MyAccount.json |
|
Configuration file (pre-Vinson) |
SC.MyAccount.Configuration.js |