Overview
The purpose of this importer is to import products, specifically:
- point of sale products
- products relating to miscellaneous usage records provided by service suppliers. These usage files are often referred to as call data records ('CDRs').
This importer, unlike most others, does not use the Bulk Import framework to receive and process the files using Cumulus. In this case Emersion's Batch Mediation System ('BMS') receives and processes these files. Files will be delivered to a secure FTP location that will be provided to you upon subscribing to the importer. The BMS will automatically process the files that are pushed.
Business Rules
When updating an existing product, only the following fields will be updated. If you try update a field other than the ones below, it will be ignored by the BMS.
- GL Code
- Product Category
- Product Subcategory
- Manufacturer
- Colour
- Tax Type
- Price Type
- Product Status
- Supplier Name
- Supplier Code
- Product Name
- Description
The product identifier/SKU is used to find existing products that will be updated using this importer.
Licencing
This feature is available to subscribers of the following:
- Emersion Core
- Optional Modules
- Upon Request (please contact your Account Manager)
Import Result Notification
There is no automated communication to our customers of the success or failure of an import.
If the import succeeds you will see products available for use within Cumulus. If you cannot see the products, the import failed.
If the import fails, raise a ticket with the service desk team so we can assist you.
Importing The Data
Once the necessary setup is complete, you will need to deliver the file to the appropriate SFTP location. The Emersion support team will advise you further on the necessary connection details.
Sample File
Data Definition
Filename format
The filename format is broken up into 5 sections separated by underscores, these are as follows;
- Source company (SAMPLE) - 1-8 CHARS
- Destination company (EME) - 3 CHAR
- Sequence Number (5) - up to 8 NUMBERS
- Date generated (20171105) - 8 String (YYYYMMDD)
- Time generated (165900) - 6 String (HHMMSS)
Example valid filename: EMEO_EME_00000001_20181203_000012.csv
Sequence number is a customer-generated number. It can be anything, but is commonly an incremented number each file that is uploaded.
The product importer data template file contains example records as a guide.
Header Record
| Field | Field Type | Example | Description |
|---|---|---|---|
| Record Type | String (6) | HDR | The type of record (always HDR) |
| Sequence Number | Integer (8) | 1 | The file sequence number |
| File Generation Date/Time | String (15) | 20171103_165455 | The date and time the file was generated, separated by an underscore. |
Detail Record
| Source File Column Number | Field | Field Type | Mandatory on Add | Used in Update? | Example | Description |
|---|---|---|---|---|---|---|
| 0 | Record Type | String | Yes | N/A | DET | The type of record (always DET) |
| 1 | Product Identifier/SKU | String | Yes | Yes | CHG-EMO-3858 | The unique identifier representing the product. It will be the SKU in the product definition, and also the product key used for inbound service and equipment transactions. |
| 2 | Product Name | String | Yes | Yes | My fancy modem | The product name as it will appear in the system. |
| 3 | Description | String | Yes | Yes | This is a special fancy modem | A long description of the product. |
| 4 | Product Status | String | Yes | Yes | Active | The status of the product. |
| 5 | Start Date | Date | Yes | No | 2013-10-10 | The date the product was considered created and usable. |
| 6 | Category | String | Yes | Yes | 'Network' or '1294' | The product category the product associated with. The category must exist in Emersion prior to importing products for it. |
| 7 | SubCategory | String | No | Yes | Cabling | The product sub category in Emersion. The sub category must exist in Emersion prior to importing products for it. |
| 8 | Supplier Name | String | No | Yes | Super Distributors Pty Ltd | The supplier the product is sourced from. Not accepted where Service Type Category is provided. |
| 9 | Supplier Code | String | No | Yes | CATR | The supplier code that provides the product. |
| 10 | Product Price Type | ID or String | No | Yes | 'units' or Product Price Type ID | The type of pricing that applies to this product. This is a vanity field and has no bearing on calculation. Reference Data available via the Unit Type / Price Type report under Report > List > Reference.
|
| 11 | GST Code | ID or String | Yes | Yes | 'australia-gst' or Tax Type ID | The Emersion tax type to be used. Tax types are are maintained by Emersion and are available to access via the Tax Type List report under Reports > List > Reference.
|
| 12 | GL Code | ID or String | Yes | Yes | MISC_PRODUCT | The ledger code required for the product. Internal codes cannot be used. The ID or text input is valid. Reference Data available via the Ledger Codes (and Mapping) report under Report > List > Reference. |
| 13 | Is Serialised | Boolean | Yes | Yes | false | Controls whether the product is serialised when purchased or fulfilled. Not accepted where Service Type Category is provided. Defaults to false. |
| 14 | Track Inventory | Boolean | Yes | Yes | false | Controls whether inventory is tracked when purchasing within Emersion. Not accepted where Service Type Category is provided. Defaults to false. |
| 15 | Manufacturer | ID or String | No | Yes | Apple | String or ID matching one of the manufacturers within the Emersion reference list. Not accepted where Service Type Category is provided. |
| 16 | Colour | ID or String | No | Yes | Red | String or ID matching one of the colours within the Emersion reference list. Not accepted where Service Type Category is provided. |
| 17 | Can Assign Service | Boolean | No | No | false | Controls whether a service can be bound against the product sale if created within the Cumulus Purchase section. Not accepted where Service Type Category is provided. Defaults to false. |
| 18 | Encrypt Serial Number | Boolean | No | No | false | Controls whether the 'Serial Number' provided for Inventory is encrypted on entry. Not accepted where Service Type Category is provided unless product type is 'Voucher'. Only used if 'Track Inventory' and 'Is Serialised' are used. |
| 19 | Product Type ID | ID or String | Yes | No | 'Billable Item' | One of 'Service Charge', 'Billable Item', 'Physical Product', 'Labour' or 'Voucher' (or related ID). |
| 20 | Service Type Category | ID or String | No | No | 'EMEO Managed Services' | The name or ID of the service type category that the product should go under. Used for creating inbound Service and equipment products. It should also be noted that the service type category has been enhanced as a result of this project to include a reference to the managing account id. A validation check would ensure that the connector's account id is the managing account id for the service type category; otherwise, an error will be returned. |
| 21 | Supplier Category | String | No | Yes | 'My Supplier Category' | The name of the Supplier Category |
Footer Record
| Field | Field Type | Example | Description |
|---|---|---|---|
| Record Type | String | FTR | The type of record (always FTR) |
| Total Records | Integer | 10045 | The total records including the header |