WO2016060553A1

WO2016060553A1 - A method for converting file format and system thereof

Info

Publication number: WO2016060553A1
Application number: PCT/MY2015/050128
Authority: WO
Inventors: Kim Seng Kee; Keong Hway CHHUA; Theng Soo TAN
Original assignee: Kim Seng Kee
Priority date: 2014-10-13
Filing date: 2015-10-13
Publication date: 2016-04-21
Also published as: MY186628A

Abstract

The present invention discloses a method for converting any types of file format into a Electronic Document (eDoc) comprises the steps of: receiving, by a Input Module (1), inputs relating to the conversion from a user server; executing, by a Process Mode Module (2), the modes of the conversion based on the inputs of the user; determining, by a Converter Controller Module (3), the format type of the file and retrieving a suitable type of converter from a database server; and activating, by the Converter Controller Module (3), the retrieved converter for converting the file into a Electronic Document (eDoc) format.

Description

A METHOD FOR CONVERTING FILE FORMAT AND SYSTEM THEREOF

FIELD OF INVENTION

The invention relates to a method and system of converting file format. More particularly, the invention relates to a method and system that can convert a file, or multiple file in any file type to Electronic Document or multiple electronic Documents and vice versa.

BACKGROUND OF THE INVENTION

The legacy system that uses RDBMS as its database cannot store documents and folios, the documents and folios must be split into tables with different primary keys and foreign keys to be able to store onto RDBMS. The thousands of table designs must include all input tables, intermediate tables and output tables is a very complicated undertaking. The thousands of tables complicate systems development life cycle (SDLC) & complicates data managements. Therefore, to provide a one view of customer folio, general ledger folio, stock folio, etc. is a difficult effort as the data must be transformed between each process (web, transmission, storage, processing (batch, online, BPM), data-warehousing, data-mining, output.

In Legacy system, it is difficult to integrate data & system because it is usually developed by different group as Legacy systems involve thousands of tables. The Documents, Flows, Business Rules & Codes are often lost in the process, therefore difficult for business personnel to talk to the computer people.

SUBSTITUTE SHEETS (RULE 26) Because of the complexity, software changes are slow, complex & expensive, the dateline are difficult to meet. What is really needed is an efficient system which stores structured, semi-structured and unstructured data (and the schema which describes the data), and manages the relationships between data items.

Consequently, a Emulating Manual System (eMS) is proposed to emulate manual filing system by storing and processing electronic document that operates on Relational Database Management System (RDBMS) and the invention provides a method and system for two ways conversion between eDoc and all other file types.

SUMMARY OF INVENTION The invention provides a method for converting any types of file format into a Electronic Document (eDoc) comprises the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; executing, by a Process Mode Module, the modes of the conversion based on the inputs of the user; determining, by a Converter Controller Module, the format type of the file and retrieving a suitable type of converter from a database server; and activating, by the Converter Controller Module, the retrieved converter for converting the file into a Electronic Document (eDoc) format. Preferably, the modes of the conversion include a Batch Mode and a Online Mode. The Batch Mode comprises the step of stacking up the files, in the event of a communication link between the user server and the database server is not established. Whereas the Online Mode comprises the step of transmitting request information to the database server for initiating the conversion process, in the event of the communication link between the user server and the database server is established.

In one embodiment of the invention, the Converter Controller Module further

SUBSTITUTE SHEETS (RULE 26) comprises a Read Module for retrieving a dictionary for the insertion of data into a Electronic Document (eDoc).

In another embodiment of the invention, the Converter Controller Module further comprises a String Module for forming strings of the Electronic Document (eDoc).

Yet in another embodiment of the invention, the Converter Controller Module further comprises a Updating Module for inserting data in the row into the Electronic Document (eDoc).

Yet in another embodiment of the invention, the Converter Controller Module further comprises a Transaction Processing Module for storing the Electronic Document (eDoc) into the database server. The invention further discloses method for converting a RDBMS table format into a Electronic Document (eDoc) comprises the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module, a RDBMS Converter from a database server; and activating, by the Converter Controller Module, the RDBMS converter for converting the RDBMS table into the Electronic Document (eDoc) format; wherein the RDBMS Converter is configured to: extract table information including table name and column from the file, activate a Read Module to retrieve a dictionary for the insertion of data into a Electronic Document (eDoc), activate a String Module to form strings of the Electronic Document (eDoc), activate a Updating Module to insert data in the row into the Electronic Document (eDoc), and activate a Transaction Processing Module to store the Electronic Document (eDoc) into the database server.

The invention further discloses a method for converting a XML file format into a Electronic Document (eDoc) comprises the steps of: receiving, by a Input Module,

SUBSTITUTE SHEETS (RULE 26) inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module, a XML Converter from a database server; and activating, by the Converter Controller Module, the XML converter for converting the XML file into the Electronic Document (eDoc) format; wherein the XML Converter is configured to: create a eDoc sections and a eDoc rows for storing XML information, element information, attribute information, and sequence information, activate a String Module to form strings of the Electronic Document (eDoc), activate a Updating Module to insert data in the row into the Electronic Document (eDoc), and activate a Transaction Processing Module to store the Electronic Document (eDoc) into the database server.

The invention further discloses a method for converting a Excel file format into a Electronic Document (eDoc) comprises the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module, a Excel Converter from a database server; and activating, by the Converter Controller Module, the Excel converter for converting the Excel file into the Electronic Document (eDoc) format; wherein the Excel Converter is configured to: extract information relating to cell format, stple, computation, condition, and data type from the file, activate a Read Module to retrieve a dictionary for the insertion of data into a Electronic Document (eDoc), activate a String Module to form strings of the Electronic Document (eDoc), activate a Updating Module to insert data in the row into the Electronic Document (eDoc), and activate a Transaction Processing Module to store the Electronic Document (eDoc) into the database server. The invention further discloses a method for converting a HTML file format into a Electronic Document (eDoc) comprises the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module, a HTML Converter from a database server; and activating, by the Converter Controller Module, the HTML converter for converting the HTML file into

SUBSTITUTE SHEETS (RULE 26) the Electronic Document (eDoc) format; wherein the HTML Converter is configured to: extract information relating to table input from the file, activate a Read Module to retrieve a dictionary for the insertion of data into a Electronic Document (eDoc), activate a String Module to form strings of the Electronic Document (eDoc), activate a Updating Module to insert data in the row into the Electronic Document (eDoc), and activate a Transaction Processing Module to store the Electronic Document (eDoc) into the database server.

The invention further discloses a method for converting a Unreadable File Format into a Electronic Document (eDoc) comprises the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module, a Unreadable File Converter from a database server; and activating, by the Converter Controller Module, the Unreadable File converter for converting the Unreadable file into the Electronic Document (eDoc) format; wherein the Unreadable File Converter is configured to: create eDoc with section; create eDoc rows to store file name, file type, and file Base64 data, activate a Updating Module to insert data in the row into the Electronic Document (eDoc), and activate a Transaction Processing Module to store the Electronic Document (eDoc) into the database server. The invention also provides a method for converting a Electronic Document (eDoc) into any types of file format comprising the steps of: receiving, by a Input Module, inputs relating to the conversion from a user; executing, by a Process Mode Module, the modes of the conversion based on the inputs of the user; determining, by a Converter Controller Module, the format type of the file and retrieving a suitable type of converter from a database; and activating, by the Converter controller Module, the retrieved converter for converting the Electronic Document (eDoc) into any types of file format. Preferably, the modes of the conversion include a Batch Mode and a Online Mode. The Batch Mode comprises the step of stacking up the files, in the event of a communication link between the user server and the database server is not

SUBSTITUTE SHEETS (RULE 26) established. Whereas the Online Mode comprises the step of transmitting request information to the database server for initiating the conversion process, in the event of the communication link between the user server and the database server is established. In one embodiment of the invention, the Converter Controller Module further comprises a Retrieval Module for retrieving sections and rows information from a Electronic Document (eDoc).

The invention further discloses a method for converting a Electronic Document (eDoc) into RDBMS table format comprises the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module, a RDBMS Converter from a database server; and activating, by the Converter Controller Module, the RDBMS converter for converting the Electronic Document (eDoc) into the RDBMS table format; wherein the RDBMS Converter is configured to: activate a Retrieval Module to extract sections and rows information from the Electronic Document (eDoc), create a sql query string that contains the sections and rows information, and insert the sql query into the RDBMS table. The invention further discloses a method for converting a Electronic Document (eDoc) into XML file format comprises the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module, a XML Converter from a database server; and activating, by the Converter Controller Module, the XML converter for converting the Electronic Document (eDoc) into the XML file format; wherein the XML Converter is configured to: activate a Retrieval Module to extract sections and rows information from the Electronic Document (eDoc), retrieve file names from the sections and rows information, create new elements with the value from the sections rows information, create attribute and sequentially insert into the created elements, and compile the

SUBSTITUTE SHEETS (RULE 26) elements to form the XML file.

The invention futher discloses a method for converting a Electronic Document (eDoc) into Excel file format comprises the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module, a Excel Converter from a database server; and activating, by the Converter Controller Module, the Excel converter for converting the Electronic Document (eDoc) into the Excel file format; wherein the Excel Converter is configured to: activate a Retrieval Module to extract sections and rows information from the Electronic Document (eDoc), retrieve file names from the sections and rows information, create cells with its corresponding value, computation, condition, and cell style, create sheets and insert the created cells accordingly, and compile the sheets to form the Excel file. The invention further discloses a method for converting a Electronic Document (eDoc) into HTML file format comprises the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module, a HTML Converter from a database server; and activating, by the Converter Controller Module, the HTML converter for converting the Electronic Document (eDoc) into the HTML file format; wherein the HTML Converter is configured to: activate a Retrieval Module to extract sections and rows information from the Electronic Document (eDoc), create component div strings which include location x-y, style, id, and component type, extract values from the sections and rows information and insert into the component div, and compile the components div to form the HTML file.

The invention further discloses a method for converting a Electronic Document (eDoc) into Unreadable File Format comprising the steps of: receiving, by a Input Module, inputs relating to the conversion from a user server; retrieving, by a

SUBSTITUTE SHEETS (RULE 26) Converter Controller Module, a Unreadable File Converter from a database server; and activating, by the Converter Controller Module, the Unreadable File converter for converting the Electronic Document (eDoc) into the Unreadable File file format; wherein the Unreadable File Converter is configured to: activate a Retrieval Module to extract sections and rows information from the Electronic Document (eDoc), retrieve file name, file type, and file base64 binary data from the sections and rows information, compile the retrieved information to form the Unreadable File.

At least one of the preceding objects is met, in whole or in part, by the invention, in which the embodiment of the invention discloses a system for converting any types of file format into a Electronic Document (eDoc) comprises: a Input Module for receiving inputs relating to the conversion from a user server; a Process Mode Module for executing the modes of the conversion based on the inputs of the user; and a Converter Controller Module configured to determine the format type of the file and retrieving a suitable type of converter from a database server, and to activate the retrieved converter for converting the file into a Electronic Document (eDoc) format. Preferably, the modes of the conversion include a Batch Mode and a Online Mode. The Batch Mode comprises a computer-executable instruction for stacking up the files, in the event of a communication link between the user server and the database server is not established. Whereas the Online Mode comprises a computer-executable instruction for transmitting request information to the database server for initiating the conversion process, in the event of the communication link between the user server and the database server is established. In one embodiment of the invention, the Converter Controller Module further comprises a Read Module for retrieving a dictionary for the insertion of data into a Electronic Document (eDoc).

In another embodiment of the invention, the Converter Controller Module further

SUBSTITUTE SHEETS (RULE 26) comprises a String Module for forming strings of the Electronic Document (eDoc).

Yet in another embodiment of the invention, the Converter Controller Module further comprises a Transaction Processing Module for storing the Electronic Document (eDoc) into the database server.

The invention further discloses a system for converting a RDBMS table format into a Electronic Document (eDoc) comprises: a Input Module for receiving inputs relating to the conversion from a user server; and a Converter Controller Module configured to retrieve a RDBMS Converter from a database server, and to activate the RDBMS converter for converting the RDBMS table into the Electronic Document (eDoc) format; wherein the RDBMS Converter comprises: a computer-executable instruction for extracting table information including table name and column from the file, a computer-executable instruction for activating a Read Module to retrieve a dictionary for the insertion of data into a Electronic Document (eDoc), a computer-executable instruction for activating a String Module to form strings of the Electronic Document (eDoc), a computer-executable instruction for activating a Updating Module to insert data in the row into the Electronic Document (eDoc), and a computer-executable instruction for activating a Transaction Processing Module to store the Electronic Document (eDoc) into the database server.

The invention further discloses a system for converting a XML file format into a Electronic Document (eDoc) comprises: a Input Module for receiving inputs relating to the conversion from a user server; and a Converter Controller Module configured to retrieve a XML Converter from a database server, and to activate the XML

SUBSTITUTE SHEETS (RULE 26) converter for converting the XML file into the Electronic Document (eDoc) format; wherein the XML Converter comprises: a computer-executable instruction for creating a eDoc sections and a eDoc rows for storing XML information, element information, attribute information, and sequence information, a computer-executable instruction for activating a String Module to form strings of the Electronic Document (eDoc), a computer-executable instruction for activating a Updating Module to insert data in the row into the Electronic Document (eDoc), and a computer-executable instruction for activating a Transaction Processing Module to store the Electronic Document (eDoc) into the database server.

The invention further discloses a system for converting a Excel file format into a Electronic Document (eDoc) comprises: a Input Module for receiving inputs relating to the conversion from a user server; and a Converter Controller Module configured to retrieve a Excel Converter from a database server, and to activate the Excel converter for converting the Excel file into the Electronic Document (eDoc) format; wherein the Excel Converter comprises: a computer-executable instruction for extracting information relating to cell format, stple, computation, condition, and data type from the file, a computer-executable instruction for activating a Read Module to retrieve a dictionary for the insertion of data into a Electronic Document (eDoc), a computer-executable instruction for activating a String Module to form strings of the Electronic Document (eDoc), a computer-executable instruction for activating a Updating Module to insert data in the row into the Electronic Document (eDoc), and a computer-executable instruction for activating a Transaction Processing Module to store the Electronic Document (eDoc) into the database server.

The invention further discloses a system for converting a HTML file format into a Electronic Document (eDoc) comprises: a Input Module for receiving inputs relating to the conversion from a user server; and a Converter Controller Module configured to retrieve a HTML Converter from a database server, and to activate the HTML

SUBSTITUTE SHEETS (RULE 26) converter for converting the HTML file into the Electronic Document (eDoc) format; wherein the HTML Converter comprises: a computer-executable instruction for extracting information relating to table input from the file, a computer-executable instruction for activating a Read Module to retrieve a dictionary for the insertion of data into a Electronic Document (eDoc), a computer-executable instruction for activating a String Module to form strings of the Electronic Document (eDoc), a computer-executable instruction for activating a Updating Module to insert data in the row into the Electronic Document (eDoc), and a computer-executable instruction for activating a Transaction Processing Module to store the Electronic Document (eDoc) into the database server.

The invention further discloses a system for converting a Unreadable File Format into a Electronic Document (eDoc) comprises: a Input Module for receiving inputs relating to the conversion from a user server; a Converter Controller Module configured to retrieve a Unreadable File Converter from a database server, and to activate the Unreadable File converter for converting the Unreadable file into the Electronic Document (eDoc) format; wherein the Unreadable File Converter comprises: a computer-executable instruction for creating eDoc with section, a computer-executable instruction for creating eDoc rows to store file name, file type, and file Base64 data, a computer-executable instruction for activating a Updating Module to insert data in the row into the Electronic Document (eDoc), and a computer-executable instruction for activating a Transaction Processing Module to store the Electronic Document (eDoc) into the database server. The invention also provides a system for converting a Electronic Document (eDoc) into any types of file format comprises: a Input Module for receiving inputs relating to the conversion from a user; a Process Mode Module to execute the modes of the conversion based on the inputs of the user; and a Converter Controller Module configured to retrieve the format type of the file and retrieving a suitable type of

SUBSTITUTE SHEETS (RULE 26) converter from a database, and to activate the retrieved converter for converting the Electronic Document (eDoc) into any types of file format. Preferably, system according to claim 14, wherein the modes of the conversion include a Batch Mode and a Online Mode. The Batch Mode comprises a computer-executable instruction for stacking up the files, in the event of a communication link between the user server and the database server is not established. Whereas the Online Mode comprises a computer-executable instruction for transmitting request information to the database server for initiating the conversion process, in the event of the communication link between the user server and the database server is established.

In one embodiment of the invention, the Converter Controller Module further comprises a Retrieval Module for retrieving sections and rows information from a Electronic Document (eDoc). The invention further discloses a system for converting a Electronic Document (eDoc) into RDBMS table format comprises: a Input Module for receiving inputs relating to the conversion from a user server; and a Converter Controller Module configured to retrieve a RDBMS Converter from a database server, and to activate the RDBMS converter for converting the Electronic Document (eDoc) into the RDBMS table format; wherein the RDBMS Converter comprises: a computer-executable instruction for activating a Retrieval Module to extract sections and rows information from the Electronic Document (eDoc), a computer-executable instruction for creating a sql query string that contains the sections and rows information, and a computer- executable instruction for inserting the sql query into the RDBMS table.

The invention further discloses a system for converting a Electronic Document (eDoc) into XML file format comprises: a Input Module for receiving inputs relating to the conversion from a user server; a Converter Controller Module configured to retrieve a XML Converter from a database server, and to activate the XML converter for

SUBSTITUTE SHEETS (RULE 26) converting the Electronic Document (eDoc) into the XML file format; wherein the XML Converter comprises: a computer-executable instruction for activating a Retrieval Module to extract sections and rows information from the Electronic Document (eDoc), a computer-executable instruction for retrieving file names from the sections and rows information, a computer-executable instruction for creating new elements with the value from the sections rows information, a computer-executable instruction for creating attribute and sequentially insert into the created elements, and a computer-executable instruction for compiling the elements to form the XML file. The invention further discloses a system for converting a Electronic Document (eDoc) into Excel file format comprises: a Input Module for receiving inputs relating to the conversion from a user server; and a Converter Controller Module configured to retrieve a Excel Converter from a database server, and to activate the Excel converter for converting the Electronic Document (eDoc) into the Excel file format; wherein the Excel Converter comprises: a computer-executable instruction for activating a Retrieval Module to extract sections and rows information from the Electronic Document (eDoc), a computer-executable instruction for retrieving file names from the sections and rows information, a computer-executable instruction for creating cells with its corresponding value, computation, condition, and cell style, a computer- executable instruction for creating sheets and insert the created cells accordingly, and a computer-executable instruction for compiling the sheets to form the Excel file.

The invention further discloses a system for converting a Electronic Document (eDoc) into HTML file format comprises: a Input Module for receiving inputs relating to the conversion from a user server; and a Converter Controller Module configured to retrieve a HTML Converter from a database server, and and to activate the HTML converter for converting the Electronic Document (eDoc) into the HTML file format; wherein the HTML Converter comprises: a computer-executable instruction for activating a Retrieval Module to extract sections and rows information from the

SUBSTITUTE SHEETS (RULE 26) Electronic Document (eDoc), a computer-executable instruction for creating component div strings which include location x-y, style, id, and component type, a computer-executable instruction for extracting values from the sections and rows information and insert into the component div, and a computer-executable instruction for compiling the components div to form the HTML file.

The invention further discloses a system for converting a Electronic Document (eDoc) into Unreadable File Format comprises: a Input Module for receiving inputs relating to the conversion from a user server; and a Converter Controller Module configured to retrieve a Unreadable File Converter from a database server, and activate the Unreadable File converter for converting the Electronic Document (eDoc) into the Unreadable File file format; wherein the Unreadable File Converter comprises: a computer-executable instruction for activating a Retrieval Module to extract sections and rows information from the Electronic Document (eDoc), a computer-executable instruction for retrieving file name, file type, and file base64 binary data from the sections and rows information, a computer-executable instruction for compiling the retrieved information to form the Unreadable File.

Effectively, the invention provides a system and method for converting file from its original file format, into eDoc, or vice versa (hereinafter referred to as "exchange"). The advantage of exchange that specialize in eDoc, will assist and allow eDoc as a unique data structure, to be co-exist and communicate with other system that may be processing different file format. User of exchange send in file of any format, through exchange controller, will convert the file to and from eDoc according to received instruction, or identify by exchange convert controller. The Converter Controller can intelligently detect the file format that user send to be convert. The Converted file will be return as output, or store into database. With Exchange, users can use any eDoc related system even though don't

SUBSTITUTE SHEETS (RULE 26) have any knowledge about eDoc. Exchange can read and interpret data inside file that want to be converted, and convert the file into eDoc. For example, when Exchange converting Excel file, each of the file and cell information like file name, cell sheet, data format, value, font style, cell style, condition and computation will be read, interpret and stored into eDoc and the Excel file converted to eDoc. User of exchange can use Exchange to run batch mode and online mode. Online is real time process meanwhile the batch mode is a process mode that will process a large amount of documents. One skilled in the art will readily appreciate that the invention is well adapted to carry out the objects and obtain the ends and advantages mentioned, as well as those inherent therein. The embodiments described herein are not intended as limitations on the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

For the purpose of facilitating an understanding of the invention, there is illustrated in the accompanying drawing the preferred embodiments from an inspection of which when considered in connection with the following description, the invention, its construction and operation and many of its advantages would be readily understood and appreciated.

Figure 1 illustrates a flow chart for creating a Electronic Document (eDoc) template string.

Figure 2 illustrates a flow chart of extracting process from a Electronic

Document (eDoc) String.

SUBSTITUTE SHEETS (RULE 26) illustrates a flow chart of retrieving process for data from the Column of extracted Electronic Document Header (eDoc-Header). illustrates a flow chart of updating process for data from the retrieved row index and column index. illustrates a flow chart of uploading process for a Electronic Document (eDoc) String. illustrates a flow chart of paging process of a Electronic Document (eDoc) for a Electronic File (eFile). illustrates a flow chart of indexing process of a Electronic Document (eDoc) for a Electronic File (eFile). illustrates a flow chart of reading process of a Electronic Document (eDoc) for a Electronic File (eFile). illustrates a flow chart of Mapping process of a Electronic Document (eDoc) for a Electronic File (eFile). illustrates an example of Electronic Dictionary (eDict) or metadata is used to describe the attribute/behavior in a string. illustrates an example eLedger containing details of a customer profile and item details. illustrates an example creation of subDoc based on the example as in Figure 11.

SUBSTITUTE SHEETS (RULE 26) Figure 13 illustrates an example of how eFiles store in a RDBMS Table. Figure 14 illustrates a Transaction Processing System.

Figure 15 illustrates the master flowchart of the exchange process.

Figure 16 illustrates the process flowchart of Converter Controller. Figure 17 illustrates the process of converting RDBMS table into eDoc and vice versa.

Figure 18 illustrates the process of converting XML file into eDoc and vice versa. Figure 19 illustrates the process of converting Excel file into eDoc and vice versa.

Figure 20 illustrates the process of converting HTML file into eDoc and vice versa.

Figure 21 illustrates the process of converting unreadable file format into eDoc and vice versa.

Figure 22 is a block diagram of the system for two ways conversion between the eDoc and all other file types.

DETAILED DESCRIPTION OF THE INVENTION

SUBSTITUTE SHEETS (RULE 26) The invention will now be described in greater detail, by way of example, with reference to the drawings.

Data is stored in a format called Electronic Document (eDoc), which serves as the display, storage, processing, and transmission format throughout the systems development life cycle, without transformation at any stage. Data can be imported from or exported to any format including PDF, XML, XLS and CSV.

An Electronic File (eFile) stores eDocs (with all data file types) on a database (RDBMS). Filing System predominantly utilizes the database read, write and index functions only. Therefore it can utilise almost all popular RDBMS, and if necessary can handle any customised, in-house database systems.

As illustrated in Figure 1 , the system to emulate manual filing system for storing and processing document that operates on Relational Database Management System (RDBMS), comprising ; a String Template (1) having at least one details of document number, number of sections and number of rows defined based on at least one Input; a String Module (2) for generate a Electronic Document (eDoc) (11) having at least one Electronic Document Identifier (eDoc-Identifier), Section, Rowtype and Column by validating the document number, number of sections and number of rows based on the String Template (1); and a Extraction Module (3) for extracting the Electronic Document Identifier (eDoc-Identifier), Section, Rowtype and Column of Electronic Document (eDoc) (11) generated by the String Module (2) for retrieval process. The system also includes a Retrieval Module (4) for retrieving at least one Retrieved Data from the data of Electronic Document (eDoc) (11) stored in the database based on at least one Input of the Section, Rowtype and Column; a Updating Module (5) for updating the Retrieved Data of Electronic Document (eDoc) (11) and store at least one Updated Data to the database based on the Input of Section, Rowtype and Column defined; and a Formation Module (6) for forming the updated

SUBSTITUTE SHEETS (RULE 26) Electronic Document (eDoc) (11) by retrieving the Updated Data based on the Input of Section, Rowtype and Column. Further, the system has a Paging Module (7) for append Electronic Document (eDoc) (11) in the database into at least one Electronic File (eFile) (13) according to a predefined Page limit; a Indexing Module (8) for forming at least one Index to the Electronic File (eFile) (13) based-on document identifier, date, end sequence number, document status, document offset and document length; and a Read Module (9) for retrieving the Index and at least one Data Relative Page (Page 0) of the Electronic File (eFile) (13) based on at least one Read Input to at least one Output. In addition the system further includes a Mapping Module (10) for updating at least one Retrieved Data based on at least one Mapping Input by determining the Electronic File (eFile) (13) using the Read Module (9) to retrieve the Retrieved Data of Electronic Document (eDoc) (11) using the Retrieval Module (4), in which the Updating Module (5) update the Retrieved Data to the database and forming the Retrieved Data into the Electronic Document (eDoc) (11) using the Formation Module (6) for updating into at least one Electronic File (eFile) (13) using Paging Module (7) and forming at least one Index using the Indexing Module (8); and a Enquiry Module (14) for retrieving a pluralities of Electronic Document (eDoc) (11) information using a Read Module (10) based on at least one Information for the Electronic Document Identifier (eDoc-Identifier), Section, Rowtype and Column of Electronic Document (eDoc) (11), in which the retrieved Electronic Document (eDoc) (11) information having at least one file history display into at least one list form.

As illustrated in Figure 2, the system or module are initiated by creating a template by defining a new document and indicate number of sections and number of rows required, which will be defined by an input from a user or a database (101). Then, the system or module creates a Electronic Document (eDoc) based on the document number defined from the input (102). Thereafter, the system or module interprets the eDoc Identifier for further processing, where the system or module validates how

SUBSTITUTE SHEETS (RULE 26) many sections or Rowtype defined in the input to form a eDoc template string (103). If there is section defined in the input, the system or module will create a new section and define or classify (label) the section if it is the 1^st Section in the input (106). Then the system or module validates is there any Rowtype defined in the input (107). If there is Rowtype defined in the input, the system or module will create a new Rowtype based on a Predefined Dictionary (108). The system or module further will validates if there is any other Section or Rowtype defined in the input for further processing (104,107). If there no other Section or Rowtype defined in the input, the system or module will further process to generate the eDoc template string with a document number (105).

As illustrated in Figure 3, the system or module are initiated by retrieving a Electronic Document (eDoc) String for extraction process (201), where the system extract a eDoc Identifier from the eDoc String having a document number (202). Then, the system will determine the section of the eDoc Identifier predefined in the eDoc String (203). If there is section defined in the eDoc Identifier (204), the system will split the section into Rowtype for further processing (205). Then, the Rowtype will split into column of data (207), where the column of data will be stored into a Database (208). The system further will validates if there is any other Section or Rowtype defined in the input for further processing (204,206). If there no other Section or Rowtype defined in the input, the system will further process for retrieval of data in the Column.

As illustrated in Figure 4, the system or module are initiated by receiving input from a database or a user (301). Then, the system validates the Section and Rowtype based on the receiving input for retrieval process (302,303). If valid section is determined, the system validates the Rowtype. If the valid Rowtype is determined, the system will locate the row index and column index (304). Then, the data is retrieved from the located row index and column index (305) and outputs the results for further

SUBSTITUTE SHEETS (RULE 26) processing (306).

As illustrated in Figure 5, the system or module are initiated by receiving input from a database or a user (401). Then, the system validates the Section and Rowtype based on the receiving input for updating process (402,403). If valid section is determined, the system validates the Rowtype. If the valid Rowtype is determined, the system will locate the row index and column index (404). Then, the data is updated to the located row index and column index based on the input received (405). Then, the updated data will be stored into a Database (406).

As illustrated in Figure 6, the system or module are initiated by retrieving the updated data stored in a Database for uploading process (501), where the system append the Electronic Document (eDoc) to output (502). Then, the systems will determine the number of section from the updated data stored in a Database to be assembled. If there is section defined in updated data, the systems will retrieve all the section from the updated data stored in a Database (503). Then, the system will retrieve all Rowtype for further processing (506). The system further will validates if there is any other Section or Rowtype defined in the updated data stored for further processing (504,507). If there no other Section or Rowtype defined in the input, the system will further proceed to append the retrieved Section, Rowtype and values (508) to be uploaded into a eDoc String (505).

As illustrated in Figure 7, the system or module are initiated by receiving input from a database or a user, in which it contains information such as: ledger identifier, document identifier, account 1 and account 2 and eDoc (601). Then, the system validates with the database if this account is a new account (602). If it's not a new account, the system retrieves the existing Page from the database for later processing (603) and append eDoc form input to the eDoc from Page (604). However, if it's a new account, the system validate if the length of the combined eDoc is greater than

SUBSTITUTE SHEETS (RULE 26) the Page limit (605). If the length of the combined eDoc is greater than Page Limit, the system chops the combined eDoc into desired Pages according to predefined Page limit (608). Otherwise, each Index will be formed based-on document identifier, date, end sequence number, document status, document offset and document length (606). Then, store Page and Index into database (607).

As illustrated in Figure 8, the system or module are initiated by receiving input from a database or a user, in which it contains information such as: document identifier, date, end sequence no, document status, document offset and document length (701). Then, forming an Index by combining all input as a string and each input is separated by colon (:) (702) and return the formed Index to the system that triggered this operation (703).

As illustrated in Figure 9, the system or module are initiated by receiving input from a database or a user, in which it contains information such as: ledger identifier, document identifier, account 1 and account 2 (801). Then, the system retrieves Index (indexes) and DATA of Relative Page for a given or specified account from a eFile stored in the database (802). Thereafter, parse the Index into individual index for processing (803). Then, the system retrieves a index that contains document identifier or information from the input received (804). Then, the system validates if there matching indexes from the input received (805). If found, the system will extract the offset and the length of the target eDoc (806) and the system further extract the eDoc from DATA of Relative Page (807). Then, output the extracted eDoc to the database or user requested (808).

As illustrated in Figure 10, the system or module are initiated by receiving input from a database or a user, such as source or details of eDoc (901). Then, parse source eDoc for further processing (902). Then, identify and load destination eDoc (for later updating) (903). Then, loading predetermined mapping instructions (904). Then, the

SUBSTITUTE SHEETS (RULE 26) system validate if the data of the predetermined source column fulfill the predetermined requirement (907), if there are more mapping instruction. Then, perform computation on the data of the predetermined source column if there is one more mapping instruction (908). However, if there are no further mapping instruction, the system store the updated destination eDoc back into database (906). Thereafter, the system will sum up the result from the computation with the data of the predetermined destination column and update the final result to the predetermine destination column (909). This process will be carried on till there is no more mapping instruction (905) and store the updated destination eDoc back into database (906). eDoc Filing System account-centric system that acts as a display, transmission, storage and processing medium from end to end without requiring any other transformation or normalization.

Electronic File (eFile) is an electronic folio (similar to a file in conventional manual filing systems) where all types of documents with different data types can be stored together in an account-centric manner. The Filing system logically stores all data and information that relate to a single account in an Electronic File (eFile), in chronological order. The Electronic Document (eDoc) are stored as sequential strings of data mapped to a data dictionary, and may include multiple data types in each string (e.g. image files, binary files, comma separated format, XML or any of the nearly 500 data formats in existence today). This allows the storage of any type of data within one record. The way eDoc stores its data provides near real-time data mining without the need for data modeling. eDoc is a data storage format comprising strings containing multiple rows each preceded by a unique row code: RxxV - Rxx being the row# and V the version#.

SUBSTITUTE SHEETS (RULE 26) Multiple rows of data of various rows make an eDoc. All data is stored in variable length or fixed length columns. Each row contains multiple columns separated by terminators. There are special terminators for start and end of DxxV (documents), RxxV (rows), etc. eDoc is designed for change. Various versions of RxxV and DxxV can exist concurrently. eDoc can be converted to XML and vice versa. eDoc is similar to XML as its data also has separators and identifiers and tags, but eDoc has additional system fields that provide new functionality. If required, XML is used as a universal transmission document and passed to other systems, where data can be normalized to tables. The table 1.0 and 2.0 further describes the terminators (separator) and identifiers and tags. eDoc String

Example of eDoc String -Data Structure : (store in LxxV) uDxxVu

uSxxVu

uRIDOuuuuuMuuuuuMuMuuuuuuiiRu

uRxxVuuu ... MuuRu

URxxVuuu ... MuuRu

uSu uSxxVu uSu

Du

SUBSTITUTE SHEETS (RULE 26) Terminators (separator) coding structure

Table 1.0

LDSRC coding structure

Table 2.0

SUBSTITUTE SHEETS (RULE 26) The Document Identifier (such as RIDO) will only contain one or the whole Document, in which the Document Identifier is stored in the first Section. The Document Identifier contains details such as creator details, document details, update history, attributes and etc. Furthermore, the eDoc String data structure is also an Nth-dimension data structure where another eDoc String can be encapsulated within the u[ ... u] and stored in a Column. The LDSRC Codes is also representing the GIS of an eDoc String stored. To retrieve the eDoc String, the LDSRC Codes are used to locate them. Example of eDoc String : (store in LHRO)

uDHRlu

uSOOlu

URID0udxxvuluUuLHR0uLD08003uuuDHRluCuuuuuuuldl302EuLea ve Applicationul2/12/2013ύύύύ, &-

URNA5uuluUuuuuuuuuuuuUploaduuuuuuNurul

AfizabintilbrahimuLot No. 4 LrgKingland 1, TmnKingland Phase 2, 88100 Petagas, KKuMalaysiauNurulAfizabintilbrahimuDato Sri

MikeuSisteruOl 6-8451196MIT

SUPPORTuFizauuuuuuuuuu8uSUPPORTuuuuuuu^

30-12-5720uM454 101 9729ύ61692683ύ830430-12-

5720u2000u2500u500uuuuuucobraangels@gmail.comuuuuu^ uu20Oct08u20Jan09u29/ll/2013u28/l 1/2013ύύύύύύύύύύύύύύύύύύύύ uuuuuuuuuuuuPETALING JAYAuuuuuuu014

3757463uuuuuuuuuuuJunior Server

AdministratoruuuuuuuFemaleuuokuokuokuReco

Su4.0ύ12ύύύύ11.0u09/12/2013uluUuCREATIVEuuM00000036uProje ct Εοαηύύύύύ(, ) MRU

SUBSTITUTE SHEETS (RULE 26) uR133uMuuuuuuuuuuuuuuuuu2u2u^

-UuRu

uRRpDl ύΐ ύύύύύύύύύύύύύύύύύύύύ approve

10 ΛΟύύύύύύύύύύύύύύύύύύύύύύύύύ

ύύ04/ 12/2013 ύύύύύύύύύύύύύύύύύύύ

ύύύύύύύύύύύύύύύύύύύύύύΐΐΐύύύ

ύύύύ *&& uuRu uR134uD313MuuuuuM640uuuuuuuuuuuM640u^

LLOANM

ϋ[

UDHR1 MS001 uuRlDOudxxvulu VuLHR0uLD08003uuu DHRluCuuuuuuuldl302EuLeave

Applicationul 2/12/2013ύύύύ, &-. uuRu uRR134uD313uluuMuul640uuuuuMuuuuul640u2014 uuuuPERSONALLOANuuuuuuu( Ή uuRuilSuuDu ii]

ύύύύύ('-Λ uuRu

eDict

As illustrated in Figure 11 , the Electronic Dictionary (eDict) or metadata is used to describe the attribute/behavior of each ledger (LxxV), document (DxxV) and Rowtype (RxxV). For LxxV level, the ledger identifier, eDoc updating methods (FIFO, LIFO, Update or Overwrite) and number of eDoc to be kept in eLedger is predefined in Ledger type eDict. For DxxV level, the document type to be or can be

SUBSTITUTE SHEETS (RULE 26) stored is predefined in the Document type eDict. For RxxV level, the Rowtype type eDict is categorized into 3 parts; first, general attributes such as name, data type, data length and so forth; second, display attributes such as font type, size, color and so forth; third, computation attributes like data validation and computation. The table 3.0, 4.0 and 5.0 shows an example of metadata or library predefined for Ledger, Document and Rowtype.

Ledger eDict - Definition

SUBSTITUTE SHEETS (RULE 26) 19 htag data 4

20 htype display 4

21 hstyle display 255

22 lig data 255

23 dup entry 1

24 msk display 200

25 cond compute 255

26 comp compute 255

27 next compute 4

28 der data

29 mnle validate 2

30 mxv validate 14

31 mnv validate

32 resl reserved

33 res2 data 4

34 res3 reserved

35 res4 reserved

36 res5 reserved

37 bal data balance

38 size data Size of this row

39 secu data 8 Security

40 cksum data 8 Checksum

Table 3.0

Document eDict - Definition

I Dictionary

SUBSTITUTE SHEETS (RULE 26) Name Function Length Description row data 4 RDD0

doc data 4 Document (DxxV)

sq data 4 Sequence#

St data 2 Status

ig data 4 LD10

acl data 16 Doc (DXXV)

ac2 data 16

proj data 4 Project

datatyp data 1 File type (Excel/Email/bin/eDoc) usg data 1

opt data 1

subfield data 4

nml data 32 Document name

nm2 data 32

le data 2 Size of Doc

de data 1 Version

def data 16

hid data 10

htag data 4

htype display 4

hstyle display 255

lig data 255

dup entry 1

msk display 200

cond compute 255

comp compute 255

next compute 4

SUBSTITUTE SHEETS (RULE 26) 28 der data

29 mnle validate 2

30 mxv validate 14

31 mnv validate

32 resl reserved

33 res2 data 4

34 res3 reserved

35 res4 reserved

36 res5 reserved

37 bal data balance

38 size data Size of this row

39 secu data 8 Security

40 cksum data 8 Checksum

Table 4.0

Rowtype eDict - Definition

SUBSTITUTE SHEETS (RULE 26) datatyp data 1 Data (9/A/X/B/D/T) usg data 1 Usage (C/Blank) opt data 1 Optional subfield data 4 Subfield

nml data 32 Label

nm2 data 32 Name of column le data 2 Max Length de data 1 Decimal (2 dec) def data 16 Default

hid data 10 HTML ID htag data 4 HTML Type htype display 4 # of elements hstyle display 255 Font, x, y, etc lig data 255 URL

dup entry 1 Duplicate msk display 200 Mask

cond compute 255 Condition comp compute 255 Computation next compute 4 Tab index der data - Derived Data mnle validate 2 Minimum length mxv validate 14 Maximum value mnv validate Minimum value resl reserved

res2 data 4 Section

res3 reserved

res4 reserved

res5 reserved

SUBSTITUTE SHEETS (RULE 26) 37 bal data -

38 size data - Size of this row

39 secu data 8 Security

40 cksum data 8 Checksum

Table 5.0

Example ofeDict structure uDDROu

uSOOlu

< 40 columns in horizontal representation > uRDCOu doc ύ sq ύ st ύ Ig ύ acl ύ ac2 ύ proj ύ datatyp ύ usg ύ opt ύ subfield ύ nml ύ nm2 ύ le ύ de ύ defu hid ύ htag ύ htype ύ hstyle ύ lig ύ dup ύ msk ύ cond ύ comp ύ next ύ der ύ mnle ύ mxv ύ mnv ύ resl ύ res2 ύ res3 ύ res4 ύ res5 ύ bal ύ size u seciiu cksumuRu uSu

uDu eLedger Electronic Ledger (eLedger) is where summaries or derivatives of eFile that is kept in variable length or fixed length format thus allowing for greater flexibility and fast retrieval. The Information in eLedger can be deleted and modified. Each eFile can have multiple eLedgers if required (for speedy reporting purposes). The update method of each eDoc to the eLedger is predefined in eLedger dictionary. The eLedger can contain n copies of eDoc that arrange in FIFO or LIFO manner; or new eDoc

SUBSTITUTE SHEETS (RULE 26) can override the exiting eDoc in the eLedger; or the update only manipulate data from certain column(s) in eDoc with the predefine column(s) in eLedger. The system may further include Zero Balancing function where every transaction can be traced and no information is ever deleted, which means everything will be balanced (always balance to last cent). All transactions have a copy in the Transaction Ledger, so changes to any account are immediately verifiable and problems isolated. The system also may make the system naturally SOX Compliant (Sarbanes-Oxley Act of 2002). The system may further include Reverse Processing where a new eLedger can be generated or regenerated from eFile based on new configuration or updated configuration.

As illustrated in Figure 12, the eLedger contains example customer profile that includes customer details (RNA6 - Name and Address Rowtype) and summary of total item such as apple, orange and pear bought daily (R320 - 32-day Rowtype) and monthly (R130 - 13-month Rowtype) for year 2014. The summary in the eLedger are populated from the daily transactions in eFile.

Rowtype Header & Footer

SUBSTITUTE SHEETS (RULE 26) n+2 RWSZ size

n+3 RWSE security

n+4 RWCS checksum

Table 6.0

All Rowtype contains a Header with 8 columns and a Footer with 4 columns as shown on the Table 6 above. The row code (RWCD) of the Rowtype Header indicates its uniqueness among other same Rowtypes that appear within a Section and ledger (RWLG), account 1 (RWA1), account 2 (RWA2) and company & department (RWCO) indicates the location of the Rowtype in the database. The security (RWSE) of the Rowtype Footer is used to ensure that the right user(s) can access this row and the checksum (RWCS) is to ensures the data within the row is not corrupted.

Subsequent Documents (SubDoc)

As illustrated in Figure 13, the creation of Subsequent Documents (subDoc), where the system splits a Doc so that it can be debited/credited to relevant account, each subDoc is appended as a string one after another. The Main Doc and subDoc(s) will have the same document identifier. For example, an invoice with document identifier, D232 may have a subDoc to debit customer account and subDoc to credit Apple, Orange and Pear Stock. (Referring to the example in Figure 2).

Reserve and Commit

It's a process where a set of predefined requirements have to be adhered before any updating can take place. For example in an invoice, the requirements will be the customer must have sufficient credit to be debited from the account and there must be sufficient stock to be stocked out before the process is committed.

SUBSTITUTE SHEETS (RULE 26) Header + Index + Data

As illustrated in Figure 14, the eFiles are stored in a RDBMS table, where the table comprises of Control, Index and Data. The Control section contains key and details about the Page. The Index is used to locate the location of each eDoc in a Page, where the Indexing are done in Horizontal manner to create sub-filing system within a filing system. The Data is where the eFile is stored. Example of Index for Account 1, Relative Page is as below:

DHR0.-20140828: 5: U: 0: 122/DHR0:20140828: 6: U: 122:

250/DHR0.-20140828: 7: U: 250: 372/

Each account contains a eFile and the eFile contains number of eDocs. The eFile is chopped into Pages according to Page size before storing into RDBMS. The Page number begins from Relative Page and when a new Page is added, the Relative Page is advanced to Page 1 and the Page number of the newly added Page is 0 and so forth. Besides that, Relative Page is also a relative page to the system; the enquiry will always start from Relative Page.

The Control section may also include the following:

lg - ledger identifier

acl - account 2

lpgn - last page no

ssq - start document sequence no

sin - start Page line no

esq - end document sequence no

eln - end Page line no

date - last updated date

SUBSTITUTE SHEETS (RULE 26) st - the status of the eFile such as deleted

co - company and department

bal - balance of all eDocs Transaction Processing

The Transaction Processing will ensure that any eDocs that are to be stored into the database is Sarbanes-Oxley (SOX) compliance. This is achieved by making sure that the status of each storing and updating process is reported back to Transaction Processing; for this case, eDoc sequence number is used. The process is considered complete when the storing and updating at Transaction eFile and eLedger and Master eFile and eLedger are executed sucessfully.

As illustrated in Figure 14, the Transaction Processing System used for Processing eDoc Transaction by receiving eDoc from a program (1001). Then, store received eDoc into Transaction eFile using Paging and Indexing Module (1002). Thereafter, update received eDoc to Transaction eLedger using Paging and Indexing Module (1003). Verify if Transaction eLedger updated successfully (1004). If received eDoc updated successfully, the system will store received eDoc into Master eFile using Paging and Indexing Module (1005). Then, update received eDoc to Master eLedger using Mapping Module (1006). Verify if Master eLedger updated successfully, go to step 1005; or else go to step 1008 to restart the process. Then, if Master eLedger updated successfully, the system returning the update status. e-Exchange

Referring to figure 15, an overall process flow of the executing exchange instruction is illustrated. Firstly, retrieve input from user or other system, the input contains data that related in exchange process (1101). Secondly, check the input to determine the

SUBSTITUTE SHEETS (RULE 26) mode of the process. The mode includes batch mode or online mode (1102). The batch mode is a mode that runs conversion process to process a large amount of document. Preferably, this mode runs temporary after the system is offline. The online mode is a mode that runs the conversion process in real time. And lastly, convert the file by a Converter Controller (1103). The Converter Controller process contains many file type process including XML, EXCEL, HTML, RDBMS, Table and all other file type (hereinafter referred to as "unreadable file type"). The Converter controller process includes both ways conversion, from other file type to eDoc, and from eDoc to other file type. In addition, other modules such as Retrieval Module, Read Module, Updating Module, String Module, and Transaction Processing Module are provided for use in the conversion process.

Referring to figure 16, a detailed process of the Converter Controller is disclosed. First, receive input from user or other system (1201). Then, validate the request to make sure which process will be executed (1202). Based on the format of the file, the Converter Controller retrieves a corresponding converter and activates the converter to convert the file (1203-1207). For example, if the file type is a RDBMS table, the controller retrieves a RDBMS converter from the database and activates the RDBMS converter to process the file. The types of converter include RDBMS converter, XML converter, Excel converter, HTML converter, and unreadable file converter. It should be noted that each converter can perform two ways conversion, from eDoc to other file type, and from other file type to eDoc.

Referring to figure 17, a process flowchart of the RDBMS converter is illustrated. In step 1301, retrieve input which contains the necessary data for the conversion process. In step 1302, read the source to determine if the file is a eDoc or RDBMS table. In step 1303, check if it is a request for converting the other file into eDoc format or vice versa. In step 1304, read the eDoc file if it is a request for converting the eDoc into a RDBMS table. In step 1305, get dictionary using the Read Module. In step 1306,

SUBSTITUTE SHEETS (RULE 26) check if there are more section. In step 1307, check if there are more rows in the sections. In step 1308, create sql query string that contains all data in the row. In step 1309, insert the sql query into the RDBMS table. In step 1310, read the RDBMS table including table name and column if it is a request for converting the RDBMS table into eDoc format. In step 1311, get dictionary using the Read Module. The dictionary is needed when inserting data into eDoc. In step 1312, check if there are more rows in the RDBMS table. In step 1313, form an eDoc string using the String Module. In step 1314, insert all data extracted from the rows into eDoc using the Updating Module. In step 1315, store eDoc using the Transaction Processing Module. In step 1316, display the outcome of the conversion on a display.

Referring to figure 18, a process flowchart of the XML converter is illustrated. In step 1401, retrieve input from users. In step 1402, read the file. In step 1403, check if it is a request for converting XML file into eDoc or vice versa. In step 1404, read the eDoc and get retrieve information from the sections and rows using the Retrieval Module if the request is for converting eDoc into XML file. In step 1405, check if there is more section. In step 1406, check if there is more rows in the sections. In step 1407, check the information type that stored in the row. Each row type will contain only one data type such as XML file name, element, or attribute. In step 1408, check if the row type is for storing file name. In step 1409, get file name from eDoc row. In step 1410, check if the row type is for storing element. In step 1411, create new element with value from eDoc row. In step 1412, create attribute and insert into element refer to sequence. In step 1413, insert all elements to form a XML and store the XML file into a storage. Each child element will append into its parent element depending on its sequence. In step 1414, create eDoc with section, and then store the XML name into eDoc row inside the eDoc if the request is for converting XML file into eDoc. In step 1415, check if there are more elements. In step 1416, create eDoc row and store element name, element value, and sequence. In step 1417, check if there are more attributes for the elements. In step 1418, create eDoc row and store attribute name,

SUBSTITUTE SHEETS (RULE 26) value, and element sequence. In step 1419, check if the elements have more child element. In step 1420, add the latest sequence. A sequence is an identification which contains parent sequence and its own identification. In step 1421, insert the sequence into the parent sequence. In step 1422, combine all eDoc row string to form a eDoc using the Updating Module. In step 1423, store the processed data by Transaction Processing Module. In step 1424, display the outcome of the conversion on a display.

Referring to figure 19, a process flowchart of the Excel converter is illustrated. In step 1501, retrieve input sent by users. In step 1502, read the source. In step 1503, check if it is a request for converting Excel file into eDoc or vice versa. In step 1504, read eDoc to get all sections and rows by the Retrieval Module if the request is for converting eDoc into Excel File. In step 1505, get Excel file name from eDoc. In step 1506, check if there are more sections in the eDoc. In step 1507, check is there are more rows in the sections. In step 1508, create cell with its corresponding value, computation, condition, and cell style and insert the information into sheets. In step 1509, insert all cells including sheet into Excel document. The Excel file is created with the file name and store it into storage. In step 1510, get dictionary from the Read Module if the request is for converting Excel file into eDoc. In step 1511, form eDoc with section. In step 1512, read the Excel file to get data and file name. In step 1513, check if there are more sheets in the Excel file. In step 1514, check if there are more cells in the sheet. In step 1515, read cell and store all data and information into row of eDoc. The information includes cell format, style, computation, condition, and data type. In step 1516, store the eDoc by the Transaction Processing Module. Referring to figure 20, a process flowchart of the HTML converter is illustrated. In step 1601, retrieve input sent by users. In step 1602, read the source. In step 1603, check if it is a request for converting HTML file into eDoc or vice versa. In step 1604, create basic HTML string which contains empty header and body if the request is for converting eDoc into HTML file. In step 1605, read edoc using the Retrieval Module

SUBSTITUTE SHEETS (RULE 26) to get all sections and rows. In step 1606, check if there are more section in the eDoc. In step 1607, check if there are more rows in the sections. In step 1608, check if the rows store component data. Some of the rows just contain data that are not related to HTML. In step 1609, create component div string which includes location x-y, styple, id and component type information. In step 1610, get values for the component from eDoc using the Retrieval Module and insert the values into the component. In step 1611, insert div into HTML. In step 1612, get dictionary from the Read Module if the request is for converting HTML file into eDoc. In step 1613, get HTML input list from user session. In step 1614, check if there are more non table inputs for HTML table. In step 1615, get value for the list using servlet library and insert data into eDoc using the Updating Module. In step 1616, check if there are more inputs for HTML table. In step 1617, check if the inputs is meant for new row or same row. One row can have multiple inputs. In step 1618, create eDoc row and insert data into the row if the input is meant for new row. In step 1619, get data for input and insert the data into eDoc row. In step 1620, insert all eDoc rows to form a eDoc using the Updating Module. In step 1621, store the processed eDoc by the Transaction Processing Module.

Referring to figure 21, a process flowchart of the Unreadable File converter is illustrated. In step 1701, retrieve input sent by users. In step 1702, read the source. In step 1703, check if it is a request for converting unreadable file into eDoc or vice versa. In step 1704, read eDoc by the using the Retrieval Module if the request is for converting eDoc into unreadable file. In step 1705, check if there are more sections in the eDoc. In step 1706, check if there are more rows in the sections. In step 1707, check if the row type is either for storing file name. Each row type are used for storing the file. In step 1708, get file name. The file name is the real name for the file, and it will be used for storing the file. In step 1709, check if the row type is for storing file type. In step 1710, get file type. In step 1711, get Base64 data from file source. The Base64 data is a binary data which is contained in the file. In step 1712, create the file

SUBSTITUTE SHEETS (RULE 26) using file name, file type, and Base64 data. In step 1713, create eDoc with sections. In step 1714, create eDoc row to store file name. In step 1715, create eDoc row to store file type. In step 1716, crate eDoc row and store file Base64 data. In step 1717, insert all eDoc rows into eDoc by using the Updating Module. In step 1718, store the processed eDoc by the Transaction Processing Module. In step 1719, display the outcome of the conversion on a display.

Referring to figure 22, the system for two ways conversion between the eDoc and all other file types is illustrated. The system comprises: a Input Module (1) for receiving inputs relating to the conversion from a user server; a Process Mode Module (2) for executing the modes of the conversion based on the inputs of the user; and a Converter Controller Module (3) configured to determine the format type of the file and retrieving a suitable type of converter from a database server, and to activate the retrieved converter for two ways conversion between the file into a Electronic Document (eDoc) format. Preferably, the Converter Controller Module (3) includes a Read Module (4) for retrieving a dictionary for the insertion of data into a Electronic Document (eDoc), a String Module (5) for forming strings of the Electronic Document (eDoc), a Updating Module (6) for inserting data in the row into the Electronic Document (eDoc), a Transaction Processing Module (7) for storing the Electronic Document (eDoc) into the database server, a Retrieval Module (8) for retrieving sections and rows information from a Electronic Document (eDoc).

SUBSTITUTE SHEETS (RULE 26)

Claims

1. A method for converting any types of file format into a Electronic Document (eDoc) comprising the steps of:

receiving, by a Input Module (1), inputs relating to the conversion from a user server; executing, by a Process Mode Module (2), the modes of the conversion based on the inputs of the user;

determining, by a Converter Controller Module (3), the format type of the file and retrieving a suitable type of converter from a database server; and

activating, by the Converter Controller Module (3), the retrieved converter for converting the file into a Electronic Document (eDoc) format.

2. A method according to claim 1, wherein the modes of the conversion include a Batch Mode and a Online Mode.

3. A method according to claim 2, wherein the Batch Mode comprises the step of stacking up the files, in the event of a communication link between the user server and the database server is not established.

4. A method according to claim 2, wherein the Online Mode comprises the step of transmitting request information to the database server for initiating the conversion process, in the event of the communication link between the user server and the database server is established.

5. A method according to any one of claims 1 to 4, wherein the Converter Controller Module (3) further comprises a Read Module (4) for retrieving a dictionary for the insertion of data into a Electronic Document (eDoc).

6. A method according to any one of claims 1 to 5, wherein the Converter Controller

SUBSTITUTE SHEETS (RULE 26) Module (3) further comprises a String Module (5) for forming strings of the Electronic Document (eDoc).

7. A method according to any one of claims 1 to 6, wherein the Converter Controller Module (3) further comprises a Updating Module (6) for inserting data in the row into the Electronic Document (eDoc).

8. A method according to any one of claims 1 to 7, wherein the Converter Controller Module (3) further comprises a Transaction Processing Module (7) for storing the Electronic Document (eDoc) into the database server.

9. A method for converting a RDBMS table format into a Electronic Document (eDoc) comprising the steps of:

receiving, by a Input Module (1), inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module (3), a RDBMS Converter from a database server; and

activating, by the Converter Controller Module (3), the RDBMS converter for converting the RDBMS table into the Electronic Document (eDoc) format;

wherein the RDBMS Converter is configured to:

extract table information including table name and column from the file,

activate a Read Module (4) to retrieve a dictionary for the insertion of data into a Electronic Document (eDoc),

activate a String Module (5) to form strings of the Electronic Document (eDoc), activate a Updating Module (6) to insert data in the row into the Electronic Document (eDoc), and

activate a Transaction Processing Module (7) to store the Electronic Document (eDoc) into the database server.

10. A method for converting a XML file format into a Electronic Document (eDoc)

SUBSTITUTE SHEETS (RULE 26) comprising the steps of:

receiving, by a Input Module (1), inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module (3), a XML Converter from a database server; and

activating, by the Converter Controller Module (3), the XML converter for converting the XML file into the Electronic Document (eDoc) format;

wherein the XML Converter is configured to:

create a eDoc sections and a eDoc rows for storing XML information, element information, attribute information, and sequence information,

11. A method for converting a Excel file format into a Electronic Document (eDoc) comprising the steps of:

receiving, by a Input Module (1), inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module (3), a Excel Converter from a database server; and

activating, by the Converter Controller Module (3), the Excel converter for converting the Excel file into the Electronic Document (eDoc) format;

wherein the Excel Converter is configured to:

extract information relating to cell format, stple, computation, condition, and data type from the file,

activate a String Module (5) to form strings of the Electronic Document (eDoc), activate a Updating Module (6) to insert data in the row into the Electronic Document

SUBSTITUTE SHEETS (RULE 26) (eDoc), and

12. A method for converting a HTML file format into a Electronic Document (eDoc) comprising the steps of:

receiving, by a Input Module (1), inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module (3), a HTML Converter from a database server; and

activating, by the Converter Controller Module (3), the HTML converter for converting the HTML file into the Electronic Document (eDoc) format;

wherein the HTML Converter is configured to:

extract information relating to table input from the file,

13. A method for converting a Unreadable File Format into a Electronic Document (eDoc) comprising the steps of:

receiving, by a Input Module (1), inputs relating to the conversion from a user server; retrieving, by a Converter Controller Module (3), a Unreadable File Converter from a database server; and

activating, by the Converter Controller Module (3), the Unreadable File converter for converting the Unreadable file into the Electronic Document (eDoc) format;

wherein the Unreadable File Converter is configured to:

SUBSTITUTE SHEETS (RULE 26) create eDoc with section;

create eDoc rows to store file name, file type, and file Base64 data,

activate a Updating Module (6) to insert data in the row into the Electronic Document

(eDoc), and

14. A method for converting a Electronic Document (eDoc) into any types of file format comprising the steps of:

receiving, by a Input Module (1), inputs relating to the conversion from a user;

executing, by a Process Mode Module (2), the modes of the conversion based on the inputs of the user;

determining, by a Converter Controller Module (3), the format type of the file and retrieving a suitable type of converter from a database; and

activating, by the Converter Controller Module (3), the retrieved converter for converting the Electronic Document (eDoc) into any types of file format.

15. A method according to claim 14, wherein the modes of the conversion include a Batch Mode and a Online Mode.

16. A method according to claim 15, wherein the Batch Mode comprises the step of stacking up the files, in the event of a communication link between the user server and the database server is not established.

17. A method according to claim 15, wherein the Online Mode comprises the step of transmitting request information to the database server for initiating the conversion process, in the event of the communication link between the user server and the database server is established.

SUBSTITUTE SHEETS (RULE 26)

18. A method according to any one of claims 14 to 17, wherein the Converter Controller Module (3) further comprises a Retrieval Module (8) for retrieving sections and rows information from a Electronic Document (eDoc).

19. A method for converting a Electronic Document (eDoc) into Rdbms table format comprising the steps of:

activating, by the Converter Controller Module (3), the RDBMS converter for converting the Electronic Document (eDoc) into the RDBMS table format;

wherein the RDBMS Converter is configured to:

activate a Retrieval Module (8) to extract sections and rows information from the Electronic Document (eDoc),

create a sql query string that contains the sections and rows information, and insert the sql query into the RDBMS table.

20. A method for converting a Electronic Document (eDoc) into XML file format comprising the steps of:

activating, by the Converter Controller Module (3), the XML converter for converting the Electronic Document (eDoc) into the XML file format;

wherein the XML Converter is configured to:

SUBSTITUTE SHEETS (RULE 26) retrieve file names from the sections and rows information,

create new elements with the value from the sections rows information,

create attribute and sequentially insert into the created elements, and

compile the elements to form the XML file.

21. A method for converting a Electronic Document (eDoc) into Excel file format comprising the steps of:

activating, by the Converter Controller Module (3), the Excel converter for converting the Electronic Document (eDoc) into the Excel file format;

wherein the Excel Converter is configured to:

retrieve file names from the sections and rows information,

create cells with its corresponding value, computation, condition, and cell style, create sheets and insert the created cells accordingly, and

compile the sheets to form the Excel file.

22. A method for converting a Electronic Document (eDoc) into HTML file format comprising the steps of:

activating, by the Converter Controller Module (3), the HTML converter for converting the Electronic Document (eDoc) into the HTML file format;

wherein the HTML Converter is configured to:

activate a Retrieval Module (8) to extract sections and rows information from the

SUBSTITUTE SHEETS (RULE 26) Electronic Document (eDoc),

create component div strings which include location x-y, style, id, and component type,

extract values from the sections and rows information and insert into the component div, and

compile the components div to form the HTML file.

23. A method for converting a Electronic Document (eDoc) into Unreadable File Format comprising the steps of:

activating, by the Converter Controller Module (3), the Unreadable File converter for converting the Electronic Document (eDoc) into the Unreadable File file format; wherein the Unreadable File Converter is configured to:

retrieve file name, file type, and file base64 binary data from the sections and rows information,

compile the retrieved information to form the Unreadable File.

24. A system for converting any types of file format into a Electronic Document (eDoc) comprising:

a Input Module (1) for receiving inputs relating to the conversion from a user server; a Process Mode Module (2) for executing the modes of the conversion based on the inputs of the user; and

a Converter Controller Module (3) configured to determine the format type of the file and retrieving a suitable type of converter from a database server, and to activate the retrieved converter for converting the file into a Electronic Document (eDoc) format.

SUBSTITUTE SHEETS (RULE 26)

25. A system according to claim 1, wherein the modes of the conversion include a Batch Mode and a Online Mode.

26. A system according to claim 2, wherein the Batch Mode comprises a computer- executable instruction for stacking up the files, in the event of a communication link between the user server and the database server is not established.

27. A system according to claim 2, wherein the Online Mode comprises a computer- executable instruction for transmitting request information to the database server for initiating the conversion process, in the event of the communication link between the user server and the database server is established.

28. A system according to any one of claims 1 to 4, wherein the Converter Controller Module (3) further comprises a Read Module (4) for retrieving a dictionary for the insertion of data into a Electronic Document (eDoc).

29. A system according to any one of claims 1 to 5, wherein the Converter Controller Module (3) further comprises a String Module (5) for forming strings of the Electronic Document (eDoc).

30. A system according to any one of claims 1 to 6, wherein the Converter Controller Module (3) further comprises a Updating Module (6) for inserting data in the row into the Electronic Document (eDoc).

31. A system according to any one of claims 1 to 7, wherein the Converter Controller Module (3) further comprises a Transaction Processing Module (7) for storing the Electronic Document (eDoc) into the database server.

SUBSTITUTE SHEETS (RULE 26)

32. A system for converting a RDBMS table format into a Electronic Document (eDoc) comprising:

a Input Module (1) for receiving inputs relating to the conversion from a user server; and

a Converter Controller Module (3) configured to retrieve a RDBMS Converter from a database server, and to activate the RDBMS converter for converting the RDBMS table into the Electronic Document (eDoc) format;

wherein the RDBMS Converter comprises:

a computer-executable instruction for extracting table information including table name and column from the file,

a computer-executable instruction for activating a Read Module (4) to retrieve a dictionary for the insertion of data into a Electronic Document (eDoc),

a computer-executable instruction for activating a String Module (5) to form strings of the Electronic Document (eDoc),

a computer-executable instruction for activating a Updating Module (6) to insert data in the row into the Electronic Document (eDoc), and

a computer-executable instruction for activating a Transaction Processing Module (7) to store the Electronic Document (eDoc) into the database server.

33. A system for converting a XML file format into a Electronic Document (eDoc) comprising:

a Converter Controller Module (3) configured to retrieve a XML Converter from a database server, and to activate the XML converter for converting the XML file into the Electronic Document (eDoc) format;

wherein the XML Converter comprises:

a computer-executable instruction for creating a eDoc sections and a eDoc rows for storing XML information, element information, attribute information, and sequence

SUBSTITUTE SHEETS (RULE 26) information,

34. A system for converting a Excel file format into a Electronic Document (eDoc) comprising:

a Converter Controller Module (3) configured to retrieve a Excel Converter from a database server, and to activate the Excel converter for converting the Excel file into the Electronic Document (eDoc) format;

wherein the Excel Converter comprises:

a computer-executable instruction for extracting information relating to cell format, stple, computation, condition, and data type from the file,

35. A system for converting a HTML file format into a Electronic Document (eDoc) comprising:

SUBSTITUTE SHEETS (RULE 26) a Input Module (1) for receiving inputs relating to the conversion from a user server; and

a Converter Controller Module (3) configured to retrieve a HTML Converter from a database server, and to activate the HTML converter for converting the HTML file into the Electronic Document (eDoc) format;

wherein the HTML Converter comprises:

a computer-executable instruction for extracting information relating to table input from the file,

36. A system for converting a Unreadable File Format into a Electronic Document (eDoc) comprising:

a Input Module (1) for receiving inputs relating to the conversion from a user server; a Converter Controller Module (3) configured to retrieve a Unreadable File Converter from a database server, and to activate the Unreadable File converter for converting the Unreadable file into the Electronic Document (eDoc) format;

wherein the Unreadable File Converter comprises:

a computer-executable instruction for creating eDoc with section,

a computer-executable instruction for creating eDoc rows to store file name, file type, and file Base64 data,

SUBSTITUTE SHEETS (RULE 26) a computer-executable instruction for activating a Transaction Processing Module (7) to store the Electronic Document (eDoc) into the database server.

37. A system for converting a Electronic Document (eDoc) into any types of file format comprising:

a Input Module (1) for receiving inputs relating to the conversion from a user;

a Process Mode Module (2) to execute the modes of the conversion based on the inputs of the user; and

a Converter Controller Module (3) configured to retrieve the format type of the file and retrieving a suitable type of converter from a database, and to activate the retrieved converter for converting the Electronic Document (eDoc) into any types of file format.

38. A system according to claim 14, wherein the modes of the conversion include a Batch Mode and a Online Mode.

39. A system according to claim 15, wherein the Batch Mode comprises a computer- executable instruction for stacking up the files, in the event of a communication link between the user server and the database server is not established.

40. A system according to claim 15, wherein the Online Mode comprises a computer- executable instruction for transmitting request information to the database server for initiating the conversion process, in the event of the communication link between the user server and the database server is established.

41. A system according to any one of claims 14 to 17, wherein the Converter Controller Module (3) further comprises a Retrieval Module (8) for retrieving sections and rows information from a Electronic Document (eDoc).

SUBSTITUTE SHEETS (RULE 26)

42. A system for converting a Electronic Document (eDoc) into RDBMS table format comprising:

a Converter Controller Module (3) configured to retrieve a RDBMS Converter from a database server, and to activate the RDBMS converter for converting the Electronic Document (eDoc) into the RDBMS table format;

wherein the RDBMS Converter comprises:

a computer-executable instruction for activating a Retrieval Module (8) to extract sections and rows information from the Electronic Document (eDoc),

a computer-executable instruction for creating a sql query string that contains the sections and rows information, and

a computer-executable instruction for inserting the sql query into the RDBMS table.

43. A system for converting a Electronic Document (eDoc) into XML file format comprising:

a Input Module (1) for receiving inputs relating to the conversion from a user server; a Converter Controller Module (3) configured to retrieve a XML Converter from a database server, and to activate the XML converter for converting the Electronic Document (eDoc) into the XML file format;

wherein the XML Converter comprises:

a computer-executable instruction for retrieving file names from the sections and rows information,

a computer-executable instruction for creating new elements with the value from the sections rows information,

a computer-executable instruction for creating attribute and sequentially insert into the created elements, and

SUBSTITUTE SHEETS (RULE 26) a computer-executable instruction for compiling the elements to form the XML file.

44. A system for converting a Electronic Document (eDoc) into Excel file format comprising:

a Converter Controller Module (3) configured to retrieve a Excel Converter from a database server, and to activate the Excel converter for converting the Electronic Document (eDoc) into the Excel file format;

wherein the Excel Converter comprises:

a computer-executable instruction for creating cells with its corresponding value, computation, condition, and cell style,

a computer-executable instruction for creating sheets and insert the created cells accordingly, and

a computer-executable instruction for compiling the sheets to form the Excel file.

45. A system for converting a Electronic Document (eDoc) into HTML file format comprising:

a Converter Controller Module (3) configured to retrieve a HTML Converter from a database server, and and to activate the HTML converter for converting the Electronic Document (eDoc) into the HTML file format;

wherein the HTML Converter comprises:

a computer-executable instruction for activating a Retrieval Module (8) to extract

SUBSTITUTE SHEETS (RULE 26) sections and rows information from the Electronic Document (eDoc),

a computer-executable instruction for creating component div strings which include location x-y, style, id, and component type,

a computer-executable instruction for extracting values from the sections and rows information and insert into the component div, and

a computer-executable instruction for compiling the components div to form the HTML file.

46. A system for converting a Electronic Document (eDoc) into Unreadable File Format comprising:

a Converter Controller Module (3) configured to retrieve a Unreadable File Converter from a database server, and activate the Unreadable File converter for converting the Electronic Document (eDoc) into the Unreadable File file format;

wherein the Unreadable File Converter comprises:

a computer-executable instruction for retrieving file name, file type, and file base64 binary data from the sections and rows information,

a computer-executable instruction for compiling the retrieved information to form the Unreadable File.

SUBSTITUTE SHEETS (RULE 26)