View source | Discuss this page | Page history | Printable version   
Main Page
Upload file
What links here
Recent changes

PDF Books
Add page
Show collection (0 pages)
Collections help


ERP/3.0/Developers Guide/Database Model/org.openbravo.utility.cleanup.log/OBULOG Config

This article is protected against manual editing because it is automatically generated from Openbravo meta-data. Learn more about writing and translating such documents.
Back button.png   Back to ERP/3.0/Developers Guide/Database Model/org.openbravo.utility.cleanup.log



This table contains the following columns:

Name Nullable Data Type Description

Obulog_Config_ID No VARCHAR (32)
AD_Client_ID No VARCHAR (32) A Client is a company or a legal entity. You cannot share data between Clients.
AD_Org_ID No VARCHAR (32) An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations.
Isactive No CHAR (1) There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reporting. There are two reasons for de-activating and not deleting records:

(1) The system requires the record for auditing purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are existing invoices for it. By de-activating the Business Partner you prevent it from being used in future transactions.

Created No TIMESTAMP (7) The Created field indicates the date that this record was created.
Createdby No VARCHAR (32) The Created By field indicates the user who created this record.
Updated No TIMESTAMP (7) The Updated field indicates the date that this record was updated.
Updatedby No VARCHAR (32) The Updated By field indicates the user who updated this record.
AD_Table_ID No VARCHAR (32) The Table indicates the table in which a field or fields reside.
Older_Than No DECIMAL When the clean up process is executed, records older than this number of days will be removed. If this value is 0, all records will be removed.
AD_Column_ID Yes VARCHAR (32) Link to the database column of the table
Hqlwhereclause Yes VARCHAR (2000) By using this HQL filter, the user will never be able to see data that does not fit the criteria. The HQL where clause is added to the query to retrieve the data which is returned by the datasource
IsTruncate No CHAR (1) Truncate all data in the table (technically truncate table DB statement). When flagged, all data in the table will be completely removed not being possible to define any other restriction.

It is only possible to truncate a table in case there is no any other table in the system having a foreign key pointing to this one.

Truncating a table results performs better in terms of time/resources consumption.

Entity_Alias Yes VARCHAR (60) Defines the main entity alias in the HQL Where Clause so it can be used in subqueries. If left empty there'll be no alias on the main entity.





Foreign key column to AD_Client table, (column: AD_Client_ID)



Foreign key column to AD_Org table, (column: AD_Org_ID)




Creation Date


Created By

Foreign key column to AD_User table, (column: AD_User_ID)




Updated By

Foreign key column to AD_User table, (column: AD_User_ID)



Foreign key column to AD_Table table, (column: AD_Table_ID)





Foreign key column to AD_Column table, (column: AD_Column_ID) It has a validation "AD_Column must be in AD_Table", with the following code



HQL Where Clause


Truncate Table


Entity Alias


Other Info

Check Constraints

These are the check constraints for this table:


Back button.png   Back to org.openbravo.utility.cleanup.log

Retrieved from ""

This page has been accessed 1,635 times. This page was last modified on 2 December 2019, at 01:53. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.