1.13.1 Segment Identification Number
This topic provides information on dividend equalization adjustment upload of segment identification number.
Table 1-82 Segment Identification Number
Field Name (as expected in the file) | Data type | Length | Attributes | Characteristics/rules | Values |
---|---|---|---|---|---|
SEGMENTID | VARCHAR2 | 80 | Optional | - | Segment ID. Value for Segment ID is 06REL |
SEQUENCENUMBER | NUMBER | 22 | Mandatory | - | Sequence Number |
PROCESSID | VARCHAR2 | 50 | Mandatory | - | Process ID |
BROKERCODE | VARCHAR2 | 12 | Mandatory | - | The code to uniquely identify the broker. Broker code and rule effective date forms a PRIMARY KEY combination |
RULEEFFECTIVEDATE | DATE | - | Mandatory | - | The date from which the changes are applicable. This along with broker code forms the PRIMARY KEY |
RPENTITYID | VARCHAR2 | 12 | Mandatory | - | Indicates the unique identification code for the related party entity associated with the unitholder |
RPENTITYTYPE | VARCHAR2 | 1 | Mandatory | - | Indicates the entity type of the unitholder's related party |
PREFMAILMODE | VARCHAR2 | 1 | Optional | - | Indicates the preferred mail mode for the related party entity |
REPORTINGLEVEL | VARCHAR2 | 1 | Optional | - | Indicates which all reports to be sent to the entities mapped |
REMARKS | VARCHAR2 | 255 | Optional | - | Indicates the descriptive remarks column for the record |
APPLYTO | VARCHAR2 | 12 | Mandatory | - | Based on the level selected in the Related party Level field , the user can either select fund ID (if he has selected Fund in Related Party Level) or AMC ID (if he has selected AMC Related Party Level) etc. If the user selects ALL in the Related Party Level then the system will default ALL in this field also and the user will not be allowed to edit it |
APPLYLEVEL | VARCHAR2 | 3 | Mandatory | - |
Related party level would specify at which level does the user wants to associate the Related Party. The possible LOV values are:
|
SEQUENCENUMBER | Number | 10 | Mandatory | - | System generated sequence number of records in the file |
PROCESSID | String | 50 | Mandatory | - |
The Process ID, along with the system generated sequence number, identifies the uploaded record uniquely. Each file must have a unique Process ID. This should be same for all records within a file. |
BULKCLIENTCODE | String | 12 | Mandatory | - | The Code of the Bulk Client |
IMPORTFILENAME | String | 255 | Mandatory | - | Name of the file being uploaded should be specified. Each file must have a unique name |
UPLOADMODE | String | 1 | Mandatory | - | ‘N’ for New unit holder uploads and ‘I’ for Incremental change |
FUNDID | Alphanumeric | 6 | Mandatory | - | ID of the fund involved in the transaction. A valid fund ID maintained in the system |
UNITHOLDERID | String | 12 | Mandatory | - | The unit holder ID available in FCIS |
EFFECTIVEDATE | Date | 10 | Optional | - | Effective Date |
G2UNITS | Number | 30,12 | Optional | - | Adjustable Units |
AUTH_STAT | Varchar2 | 1 | Mandatory | - | Must be ‘A’ |
USERID | Varchar2 | 15 | Mandatory | - | Represents the user ID who has entered the latest record |
Parent topic: Dividend Equalization Adjustment Upload