MSD Cloud Export Overview
This document will contain information specific to the MSD Cloud export template. For general information about the Data Extraction Service and it's API please see the general purpose documentation
Job Run Parameters
This template supports filtering against the DBGen range OR the TradingDate of finalised SalesTransactions/ZReports.
EITHER DBGen filtering OR trading date filtering must be used. Filtering on both is not supported.
Parameter Definitions
| Parameter | Type | Description |
|---|---|---|
| DBGenFrom | Number (optional) | The (inclusive) start of the DBGen range which will be used to filter data. (required if using DBGen filtering) |
| DBGenTo | Number (optional) | The (inclusive) end of the DBGen range which will be used to filter data. If unspecified the current latest DBGen from the server will be used. |
| TradingDateFrom | DateTime (optional) | The (inclusive) start of the TradingDate range which will be used to filter data. Please note that the time will reference the time the order/zreport was closed/finalised (required if TradingDateTo is set) |
| TradingDateTo | DateTime (optional) | The (inclusive) end of the TradingDate range which will be used to filter data. Please note that the time will reference the time the order/zreport was closed/finalised (required if TradingDateFrom is set) |
When configuring a schedule, you should only use DBGenFrom and use it in Auto Value mode to ensure all data is sent to MSD Cloud.
You should also initialise the period to export from using the "Reset to Trading Date" button.
WARNING: You should be very careful when using the TradingDateFrom/To options as there is no safety to ensure that MSD Cloud doesnt already have the sales you are re-exporting, and when received they will merge without duplicate detection.
Auto Value Considerations
DBGenFrom supports auto values which (when executing an auto value job run) will update to the value supplied at DBGenTo (or the latest DBGen from the sales data). When DBGenFrom is set to use an auto value it will use the value of the auto value + 1 to ensure that repeated executions will never export already exported sales data.
Output Files
The output files are formatted specific to meet the requirements of MSD Cloud.
These files will then be transferred via SFTP to a designated server. SFTP details will be provided by MSD Cloud and are specific to each customer.
Special Considerations
You will need to ensure that all sale items have a unique PLU number in PowerEPOS
Template Settings
| Setting | Description |
|---|---|
| Job Name | This is a name you can enter to describe the job in a way that you will recognise it amongst other potential DES jobs that you have configured for the same customer |
| Notification Emails | Each time the job runs it can be OPTIONALLY configured to email a notification so say that it succeeded for failed. This is usually blank unless special monitoring is needed |
| Master Config Outlet | This is the outlet that will be used as a "point of view" when determining default PLU pricing. If the customer is multi-outlet, it is common to create a completely new outlet called "Stock Use Only" that can be configured to give the most suitable MSD Cloud pricing. |
| Tax Service Mode | This is the service mode that will be used in combination with the Master Config Outlet to determine the tax rules and amounts for each PLU when providing the configuration to MSD Cloud. It is common to create a completely new service mode called "Stock Use Only" that can be configured to give the mots suitable MSD Cloud tax values. |
| Remote Order Variance Line PLU | You can select a PLU that will be used to represent any Remote Order Variance lines. This is needed because Remote Order Variance lines do not have a PLU number. (Remote Order Variance lines are added by POS to a transaction in the event the remote order paid amounts dont match the POS expected amounts) |
| Custom Product PLU | You can select a PLU that will be used to represent any custom products when sending through to MSD Cloud. This is needed because custom products do not have their own PLU number. |
| SFTP Credentials | This section allows you to manage the SFTP credentials used to send MSD Cloud the exported data |