Site Access Request

To bulk-send a Site Access Request (SAR), create a CSV file with the .csv file extension. The contents of every line in the file must use the following format:

<nmi>, <from_role>, <to_role>, <reason_code>, <notes>

Note:  No header row is required for the SAR CSV file.

Field Format Mandatory Definition
nmi Text (10 characters) Yes NMI, excluding the checksum.
from_role Text (5 characters) Yes Valid Initiator for transaction according to market rules i.e. LNSP, MC, MPB, MPC, FRMP, LR
to_role Text (5 characters) Yes Valid Recipient for transaction according to market rules i.e. LNSP, FRMP, LR, MPC, MPB or MC
reason

Reason Code one of the following:

  • New Retailer for site
  • Records old and need to be updated
  • No Access details on file for NMI
  • No Hazard Details on file for NMI
  • Site Visit Required
  • Other
 Yes  
Notes Text (240 characters) Yes/No Free text. Mandatory if Reason Code = “Other”

File example:

6304167823, LNSP, FRMP, No Access details on file for NMI ,
6304253600, LNSP, FRMP, No Hazard Details on file for NMI ,
6304339377, LNSP, MC, Records old and need to be updated ,
6304425154, LNSP, FRMP, Site Visit Required,
6304510931, LNSP, MP, Site Visit Required, This is near where I live. There are snakes nearby
6304987542, LNSP, FRMP, Other, I poured coffee on my PC and deleted the data. Please send what you have urgently

MTS will apply the following validation rules to the entire file. If any of these conditions are met, the entire file will be rejected. In the case of multiple errors, only the first one encountered is reported.

Order Validation Description Message
1 Too many columns A row has too many columns specified Too many columns (i.e. extra commas)
2 Too few columns A row does not have enough columns specified Too few columns
3 Too many rows The file has more than 1000 rows Too many rows (> 1000)

MTS will apply the following validation rules to each record in the file. If any of these conditions are met, the row will be skipped and an error reported. If there are multiple errors identified with a row, only the first one encountered is reported.

Order Validation Description Message
1 Mandatory field not supplied A mandatory field (NMI, From Role, To Role, Reason Code) is missing in any row. Mandatory field <field name> missing
2 Invalid NMI NMI does not exist in MTS. NMI not known
3 Invalid NMI NMI is Abolished in MTS. NMI is Abolished
4 Duplicate row Two rows exist with the same NMI, From Role and To Role. Duplicate record exists
5 Already sent Nominated recipient of the SAR has already been sent a SAR for that NMI for that calendar day. SAR already sent for NMI today
6 Invalid From role From Role is valid. From Role is not valid
7 Invalid To role Not one of "LNSP", "FRMP", "MPB" or "MC". To Role is not one of LNSP, FRMP, MPB or MC
8 To role = the business If raising to a participant the current organization owns. Role participant is current business
9 Invalid Reason Code Reason Code not one of the following:
  • New Retailer for site
  • Records old and need to be updated
  • No Access details on file for NMI
  • No Hazard Details on file for NMI
  • Site Visit Required
  • Other
 Invalid Reason Code
10 Missing special note Reason Code = "Other", but Note is blank Note must be entered for selected Reason Code
11 Note too long The Notes must be at most 240 characters The Notes must be at most 240 characters

Note:  MTS will remove any leading and trailing white-space characters from each field when parsing the CSV file. Therefore, any mandatory field for which only white space characters are supplied will be considered missing.