...
Flag Name | Valid |
---|
...
Flag Name | Values | Description | |||||
---|---|---|---|---|---|---|---|
noLoadValidationFlag | Y or N | Turns off the following checks for SMF:
| |||||
preserveNull | Y or N | This parameter is linked with tag5284, which nulls DB fields during the process of update. For example, you have 10 fields populated in the table for a record. You send a file to update it with only 7 fields and preserveNull flag set to Y - as a result, 7 fields will be updated, 3 fields will be nulled. If the flag is set to N, only these 7 fields will be updated, the other 3 fields will be left unchanged | |||||
tagNochangecase | Y or N | Originates from panels, defines for which incoming tags case should not be changed | |||||
historyOnlyFlag | Y or N | Toggles updating data in the composite table. Insert will always be performed, update can be switched off | |||||
accountingValidationFlag | Y or N | The simple way to view the accountingValidationFlag is that it is used to route the messages to use the core panels which triggers the application of the panel logic and error handling. This mimics the user functionality and experience. Using the panels, it shows the missing required flags and provides a direction for debugging if there are errors. When the flag is not passed, it attempts to do a direct insert into the database and it bypasses the logic. It is frequently used by our data management clients who do not require the same level of accounting checks. For loading in accounting transactions, you should be using the accountingValidationFlag setting it to Y.
accountingValidationFlag= N or null: accountingValidationFlag=Y: | |||||
skipIfExistFlag | Y or N | Used in resolution logic. Toggles exclusion of existing records | |||||
inactiveFlag | Y or N | Refers to SECURITYDBO.SECURITY_MASTER.INACTIVE_FLAG database field | |||||
updateMasterTablesFlag | list of tags | Not a flag in general terms. Defines the list of tags that are updated in history and composite tables when Generic SMF is loaded in history mode | |||||
fieldCompareFlag | Y or N | When this flag is set to ‘Y’, SMF record is updated only if some field(s) had their value(s) changed, i.e. SMF record with new effective date is inserted in History and updated in composite tables only if a field has a different value from one in Database - otherwise no action is performed | |||||
journalizingFlag | EXCLUDE_JOURNAL | When this flag is set to ‘EXCLUDE_JOURNAL’ then journal information is not written to database | |||||
spokeCheckFlag | 1 | To skip standard Security Resolution, set spokeCheckFlag to "1" in your SMF message. Aliases will be loaded into DB "as is" instead | |||||
vendorModeFlag | VENDOR_MODE | Represents tag 1085 in SMF panels which allows to skip the default lookup security alias calculation for pan-qissuedetail.htm if this flag is set as ‘VENDOR_MODE’. | |||||
exchangeModeFlag | Not used in EagleML |