×
Discuss about Archiving, Close of Business, Delivery Setup, Security Management System, Global Processing etc…
$DEL Files
- kripesh
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 452
- Thank you received: 63
- kripesh
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 452
- Thank you received: 63
9 years 9 months ago #16078
by kripesh
Have a great day !
Replied by kripesh on topic $DEL Files
There is a field in FILE.CONTROL called DELETE.HISTORY. If this is set to Y then while creating files at the database it will also create a file like FBNK.CUSTOMER$DEL
This is mainly to keep track of Deleted Records which was not done previously in earlier releases of T24.
This DELETE.HISTORY can be set for file whose PGM.FILE is set to type H or U only...
Anything else ???
This is mainly to keep track of Deleted Records which was not done previously in earlier releases of T24.
This DELETE.HISTORY can be set for file whose PGM.FILE is set to type H or U only...
Anything else ???
Have a great day !
Please Log in or Create an account to join the conversation.
- gm.saran
- Offline
- Elite Member
Less
More
- Posts: 203
- Thank you received: 29
9 years 9 months ago #16079
by gm.saran
Replied by gm.saran on topic $DEL Files
from which release onwards this functionality is avail?
Please Log in or Create an account to join the conversation.
- kripesh
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 452
- Thank you received: 63
- jpb
- Offline
- Moderator
- TAFj-R20 - 'unix'
Less
More
- Posts: 2854
- Thank you received: 649
9 years 9 months ago #16084
by jpb
Replied by jpb on topic $DEL Files
... it's available from R13
Please Log in or Create an account to join the conversation.
- hamza.benali
- Offline
- Junior Member
Less
More
- Posts: 22
- Thank you received: 0
9 years 1 month ago #17014
by hamza.benali
Replied by hamza.benali on topic $DEL Files
Is it available only for new created applications or we should activated for existing ones.
For exemple for CUSTOMER application are we able to have deletion history.
Thanks in advance.
For exemple for CUSTOMER application are we able to have deletion history.
Thanks in advance.
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- TAFj-R20 - 'unix'
Less
More
- Posts: 2854
- Thank you received: 649
9 years 1 month ago #17015
by jpb
Replied by jpb on topic $DEL Files
R13 documentation (nothing mentioned how to activate explicitly):
History of Deleted Items
Business Background
Every business transaction detail is stored in the database. However, any unauthorized transaction that is deleted by the user gets permanently removed from the database and eliminates its future reference. There is a necessity and demand therefore to preserve deleted transaction details.
Previous Functionality
When unauthorized transactions are deleted, they are permanently removed from the database. There is no audit trail for the deleted unauthorized records.
New functionality
A new file referred as ‘Delete’ file is introduced to capture the records deleted from unauthorized files. The Delete file is given a $DEL suffix.
$DEL file creation is allowed only for H and U type applications, when DELETE.HISTORY field in FILE.CONTROL is set to ‘Y’.
When ‘hold’ and ‘unauthorized’ records are deleted from the application, they are stored in the corresponding $DEL file of the application.
These records are viewed using the enquiry VIEW.DELETE.HISTORY.
Note: Application Name is a mandatory input for this enquiry.
The enquiry displays all the transaction references with the corresponding date and time of deletion.
To form a unique ID, the ID format of these records take the form: <Transaction reference>;<Date and Time in milliseconds>
Audit fields are updated with User details (who performed the deletion operation) with the corresponding Date and Time.
Date time fields are also updated accordingly.
Records in the $DEL file are deleted permanently using the predefined multi-threaded service EB.PURGE.DEL.FILE.
Deletion criteria in the parameter file EB.PURGE.DEL.FILE.PARAM must be configured. This file has two fields, APPLICATION.NAME which can be multivalued and PURGE.DATE to specify the date before which the records are purged.
Note:Note:For AA transactions, FILE.CONTROL is set individually for AA.ARRANGEMENT.ACTIVITY and required property class files. Upon deletion of parent record, the parent record along with related child property class records are moved to the corresponding $DEL files for which FILE.CONTROL is set.
For LD defined with schedules, FILE.CONTROL is set for LD application. On deletion, LD record is moved to the corresponding $DEL file. Support for moving related defined schedule to $DEL file is withheld
Model
The Enquiry VIEW.DELETE.HISTORY is added to ‘System Administration’ section under Admin Menu.
Please click here to look at the model bank documentation relating to this SI.
Benefits
With the introduction of the delete file, any unauthorized transaction deleted by the user will be preserved in the database and used for audit trail.
History of Deleted Items
Business Background
Every business transaction detail is stored in the database. However, any unauthorized transaction that is deleted by the user gets permanently removed from the database and eliminates its future reference. There is a necessity and demand therefore to preserve deleted transaction details.
Previous Functionality
When unauthorized transactions are deleted, they are permanently removed from the database. There is no audit trail for the deleted unauthorized records.
New functionality
A new file referred as ‘Delete’ file is introduced to capture the records deleted from unauthorized files. The Delete file is given a $DEL suffix.
$DEL file creation is allowed only for H and U type applications, when DELETE.HISTORY field in FILE.CONTROL is set to ‘Y’.
When ‘hold’ and ‘unauthorized’ records are deleted from the application, they are stored in the corresponding $DEL file of the application.
These records are viewed using the enquiry VIEW.DELETE.HISTORY.
Note: Application Name is a mandatory input for this enquiry.
The enquiry displays all the transaction references with the corresponding date and time of deletion.
To form a unique ID, the ID format of these records take the form: <Transaction reference>;<Date and Time in milliseconds>
Audit fields are updated with User details (who performed the deletion operation) with the corresponding Date and Time.
Date time fields are also updated accordingly.
Records in the $DEL file are deleted permanently using the predefined multi-threaded service EB.PURGE.DEL.FILE.
Deletion criteria in the parameter file EB.PURGE.DEL.FILE.PARAM must be configured. This file has two fields, APPLICATION.NAME which can be multivalued and PURGE.DATE to specify the date before which the records are purged.
Note:Note:For AA transactions, FILE.CONTROL is set individually for AA.ARRANGEMENT.ACTIVITY and required property class files. Upon deletion of parent record, the parent record along with related child property class records are moved to the corresponding $DEL files for which FILE.CONTROL is set.
For LD defined with schedules, FILE.CONTROL is set for LD application. On deletion, LD record is moved to the corresponding $DEL file. Support for moving related defined schedule to $DEL file is withheld
Model
The Enquiry VIEW.DELETE.HISTORY is added to ‘System Administration’ section under Admin Menu.
Please click here to look at the model bank documentation relating to this SI.
Benefits
With the introduction of the delete file, any unauthorized transaction deleted by the user will be preserved in the database and used for audit trail.
The following user(s) said Thank You: hamza.benali
Please Log in or Create an account to join the conversation.
- hamza.benali
- Offline
- Junior Member
Less
More
- Posts: 22
- Thank you received: 0
9 years 1 month ago #17017
by hamza.benali
Replied by hamza.benali on topic $DEL Files
Thank you for your answer,
I already went into those detailed explanations in R13UG, but still am not able to understand how we could activate history deletion for an existing application, especially for core applications I don't think we could re-execute the file creation to activate DELETE.HISTORY field.
I already went into those detailed explanations in R13UG, but still am not able to understand how we could activate history deletion for an existing application, especially for core applications I don't think we could re-execute the file creation to activate DELETE.HISTORY field.
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- TAFj-R20 - 'unix'
Less
More
- Posts: 2854
- Thank you received: 649
9 years 1 month ago - 9 years 1 month ago #17022
by jpb
Replied by jpb on topic $DEL Files
Use JED to change FILE.CONTROL, e.g.
@ID.............. CUSTOMER
and run CREATE.FILES for CUSTOMER, it will only create the $DEL file.
@ID.............. CUSTOMER
@ID.............. CUSTOMER
DESCRIPTION...... Customer details
PRODUCT.......... ST
SUFFIXES......... $HIS $NAU $DEL
FILE.TYPE........ 2
FILE.MODULO...... 31
CLASSIFICATION... CUS
SUB.PRODUCT...... CUSTOMER
SYS.CLEAR.FILES.. N
CUS.CLEAR.FILES.. Y
RECORD.STATUS....
CURR.NO.......... 2
INPUTTER......... 1_DIM 13_CONVERSION.DETAIL
DATE.TIME........ 0205171442
AUTHORISER.......
CO.CODE.......... IE0010001
DEPT.CODE........ 1
AUDITOR.CODE.....
AUDIT.DATE.TIME..
BRANCH.FILE...... BST
FILE............. CUSTOMER
PC.FILE..........
RELATED.FILE..... CUSTOMER
LOCAL.REF.MASTER.
RESERVED2........
RESERVED1........
SIM.REQD.........
DELETE.HISTORY... Y
DL.DATE.FIELD....
and run CREATE.FILES for CUSTOMER, it will only create the $DEL file.
Last edit: 9 years 1 month ago by jpb. Reason: typo
Please Log in or Create an account to join the conversation.
Time to create page: 0.147 seconds