WO2016060549A1

WO2016060549A1 - A system for processing data and method thereof

Info

Publication number: WO2016060549A1
Application number: PCT/MY2015/050124
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

Abstract

The present invention discloses a system for processing data bi-directionally comprises a relational table-based design platform (1); and a Emulating Manual System (eMS) platform (2) connected to the relational table-based design platform (1) through a Exchange Module (3) via a communication network; wherein the Exchange Module (3) provides two ways conversion between table-based file format of the relational table-based design platform (1) and Electronic Document (eDoc) of the eMS platform (2) so that either one of the platforms can process data of the other platform.

Description

A SYSTEM FOR PROCESSING DATA AND METHOD THEREOF

FIELD OF INVENTION

The invention relates to a system and method for processing data. More particularly, the invention relates to the invention provides a system and method for processing data in a way such that the Emulating Manual System and the Legacy system can operate concurrently.

BACKGROUND OF THE INVENTION

The legacy system that uses RDBMS as its database (hereinafter referred to as "a relational table-based design system") 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 system and method for processing data in a way such that the Emulating Manual System and the Legacy system can operate concurrently.

SUMMARY OF INVENTION

The invention provides a system for processing data bi-directionally comprises: a relational table-based design platform; and a Emulating Manual System (eMS) platform connected to the relational table-based design platform through a Exchange Module via a communication network; wherein the Exchange Module provides two ways conversion between table-based file format of the relational table-based design platform and Electronic Document (eDoc) of the eMS platform so that either one of the platforms can process data of the other platform.

In one embodiment of the invention, the system further comprises one or more database servers for storing data of the platforms.

Preferably, the Exchange Module comprises: a Input Module for receiving inputs relating to the conversion from either one of the platforms; a Process Mode Module for executing the modes of the conversion based on the inputs of the user; and a

SUBSTITUTE SHEETS (RULE 26) Converter Controller Module configured to determine the format type of the file and retrieving a suitable type of converter from the database server, and to activate the retrieved converter for perform two ways conversion between the table-based file format and the Electronic Document (eDoc) format.

Advantageously, the Converter Controller Module comprises a Read Module for retrieving a dictionary for the insertion of data into a Electronic Document (eDoc); a String Module for forming strings of the Electronic Document (eDoc); a Updating Module for inserting data in the row into the Electronic Document (eDoc); a Transaction Processing Module for storing the Electronic Document (eDoc) into the database server; and a Retrieval Module for retrieving sections and rows information from a Electronic Document (eDoc).

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.

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 method for processing data bi- directionally comprises the steps of: receiving request from either a relational table- based design platform or a Emulating Manual System (eMS) platform; retrieving, by the Exchange Module, data for conversion from a database server; retrieving, by the Exchange Module, a suitable type of converter from the database server; and converting, by the Exchange Module, the format of the retrieved data into a designated format based on the received request.

SUBSTITUTE SHEETS (RULE 26) The invention also provides a method for reading data from a Emulating Manual System platform comprises the steps of: receiving a request from a relational table- based design platform; retrieving a designated Electronic Document (eDoc) from a database server; converting the Electronic Document into table-based file format; and displaying the converted file on the relational table-based design platform.

The invention also provides a method for reading data from a relational table-based design platform comprises the steps of: receiving a request from a Emulating Manual System (eMS) platform; retrieving a designated table-based file from a database server; converting the file into Electronic Document (eDoc) format; and displaying the Electronic Document (eDoc) on the Emulating Manual System (eMS) platform.

The invention also provides a method for storing data from a Emulating Manual System (eMS) platform comprises the steps of: receiving a request from a relational table-based design platform; retrieving a designated Electronic Document (eDoc) from a database server of the Emulating Manual System (eMS) platform; converting the Electronic Document into table-based file format; and storing the converted file in a database server of the relational table-based design platform.

The invention also provides a method for storing data from a relational table-based design platform comprises the steps of: receiving a request from a Emulating Manual System (eMS) platform; retrieving a designated table-based file from a database server of the relational table-based design platform; converting the file into Electronic Document (eDoc) format; and storing the Electronic Document (eDoc) in a database server of the Emulating Manual System (eMS) platform.

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

SUBSTITUTE SHEETS (RULE 26) 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.

Figure 3 illustrates a flow chart of retrieving process for data from the Column of extracted Electronic Document Header (eDoc-Header).

Figure 4 illustrates a flow chart of updating process for data from the retrieved row index and column index. Figure 5 illustrates a flow chart of uploading process for a Electronic Document

(eDoc) String.

Figure 6 illustrates a flow chart of paging process of a Electronic Document

(eDoc) for a Electronic File (eFile).

SUBSTITUTE SHEETS (RULE 26) 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. illustrates an example of how eFiles store in a RDBMS Table. illustrates a Transaction Processing System. illustrates the master flowchart of the exchange process. illustrates the process flowchart of Converter Controller. illustrates the process of converting RDBMS table into eDoc and vice versa.

SUBSTITUTE SHEETS (RULE 26) Figure 18 a block diagram of the two-systems.

DETAILED DESCRIPTION OF THE INVENTION

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

SUBSTITUTE SHEETS (RULE 26) 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 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.

SUBSTITUTE SHEETS (RULE 26) 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 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.

SUBSTITUTE SHEETS (RULE 26) 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 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

SUBSTITUTE SHEETS (RULE 26) 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 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

SUBSTITUTE SHEETS (RULE 26) 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 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

SUBSTITUTE SHEETS (RULE 26) 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#. 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

uRIDOuuuuuMuuuuuMuMuuuuMuRu

uRxxVuuu ... MuuRu iiRxxVuuu ... MuuRu

uSu

SUBSTITUTE SHEETS (RULE 26) iiSxxVu iiSu

uDu

Terminators (separator) coding structure

Table 1.0

LDSRC coding structure

SUBSTITUTE SHEETS (RULE 26) RxxV Row Code RNA5: Name Address Rowtype version 5

CxxV Column Code C005: Column 5

VxxV SubColumn Code

Table 2.0

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 LHR0)

uDHRlu

uSOOlu

uRID0udxxvuluUuLHR0uLD08003uuuDHRluCuMuuuuldl302EuLea ve Application!! 12/ 12/2013ύύύύ, &-. MRU

URNA5uuluUuuuuuuuuuuuUploaduuuuuuNurul

AfizabintilbrahimuLot No. 4 LrgKingland 1, TmnKingland Phase 2,

88100 Petagas, KKuMalaysiauNurulAfizabintilbrahimuDato Sri MikeuSisteru016-8451196uuIT

SUPPORTuFizauuuuuuuuuu8uSUPPORTuuuuu^

30-12-5720ύύύ454 101 9729ύ61692683ύ830430-12- 5720u2000u2500u500uuuuuucobraangels@gmail.comuuuu^ uu20Oct08u20Jan09u29/ll/2013u28/l 1/2013ύύύύύύύύύύύύύύύύύύύύ

SUBSTITUTE SHEETS (RULE 26) uuuuuuuuuuuuPETALING JAYAuuuuuuu014

3757463 ύύύύύύύύύύύ Junior Server

AdministratoruuuuuuuFemaleuuokuokuokuRecom

Su4. Ού12ύύύύ11.0u09/12/2013uluUuCREATIVEuMu00000036uProje ct hoanuuuuu(, ) MRU ΰΊί133ύΜύύύύύύύύύύύύύύύύύ2ύ2

-uuRu

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

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

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

ύύύύύύύύύύύύύύύύύύύύ

ύύύύ *&& utiRu ΰΊί134ύΌ313ύ1ύύύύύύ1640ύύύύύύύύύύύύ1

LLOANM

ii[

UDHRl MSOOl uuRlOOudxxvulu VuLHR0uLD08003uuu DHRluCuuuuuuuldl302EuLeave

Applicationul2/l2/20l3uuuu, &-. uuRu ύ^Ρ134ύΌ313ύ1ύύύύύύ1640ύύύύύύύύύύύύ1640ύ2014 uuuuPERSONALLOANuuuuuuu( Ή uuRuilSuuDu ii] iiSu

uDu

eDict

SUBSTITUTE SHEETS (RULE 26) 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 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) nml data 32 Ledger name

nm2 data 32 Update method (FIFO/LIFO/U/O) le data 2 Max document

de data 1

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

der data

mnle validate 2

mxv validate 14

mnv validate

resl reserved

res2 data 4

res3 reserved

res4 reserved

res5 reserved

bal data balance

size data Size of this row

secu data 8 Security

cksum data 8 Checksum

SUBSTITUTE SHEETS (RULE 26) Table 3.0

Document eDict - Definition

SUBSTITUTE SHEETS (RULE 26) 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 4.0

Rowtype eDict - Definition

SUBSTITUTE SHEETS (RULE 26) St data 2 Status

ig data 4 LD10

acl data 16 RowCol (RxCx) ac2 data 16

proj data 4 Project

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

SUBSTITUTE SHEETS (RULE 26) 32 resl reserved

33 res2 data 4 Section

34 res3 reserved

35 res4 reserved

36 res5 reserved

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 u sq u st u lg u acl u acl u proj u datatyp u usg u opt u subfield u nml u nml u le u de u defu hid u htag u htype u hstyle u lig u dup u msk u cond u comp u next ύ der u mnle u mxv u mnv u resl u resl u res3 u res4 u res5 u bal u size ύ secuu cksumuRu uSu

uDu eLedger

SUBSTITUTE SHEETS (RULE 26) 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 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) 5 RWLG ledger

6 RWA1 account 1

7 RWA2 account 2

8 RWCO company & department n+1 RWBA balance

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 (RWAl), 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).

SU BSTITUTE SH EETS (RU LE 26) 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.

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

SUBSTITUTE SHEETS (RULE 26) 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

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

SUBSTITUTE SHEETS (RULE 26) updated successfully, the system returning the update status. Exchange Module 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 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.

SUBSTITUTE SHEETS (RULE 26) 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, 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.

Two Systems data processing

Referring to figure 18, a two system is illustrated. The Two Systems is a further embodiment of the invention utilising the Exchange Module (3) to enable the possibility of operating the Legacy system (1) and eMS (2) concurrently without the need for migrating the system from one to the other. As a result, users of the Legacy system (1) do not need to change their usual operating method and still able to read or store the data in form of eDoc. The system comprises a Legacy system platform (1), a eMS platform (2), and a Exchange Module (3) connecting the two platforms (1, 2) together via a communication network. The two platforms (1, 2) are able to receive inputs, data, or instructions from their corresponding user. The Exchange Module (3)

SUBSTITUTE SHEETS (RULE 26) is configured to receive instructions or request from the user, to retrieve data and the right type of converter from the database server, and to perform the conversion of data format based on the requests/instructions. Effectively, the Exchange Module (3) enables the platforms (1, 2) to read data from or write data to the other platform.

SUBSTITUTE SHEETS (RULE 26)

Claims

1. A system for processing data bi-directionally comprising:

a relational table-based design platform (1); and

a Emulating Manual System (eMS) platform (2) connected to the relational table- based design platform (1) through a Exchange Module (3) via a communication network;

wherein the Exchange Module (3) provides two ways conversion between table-based file format of the relational table-based design platform (1) and Electronic Document (eDoc) of the eMS platform (2) so that either one of the platforms can process data of the other platform.

2. A system according to claim 1, further comprising one or more database servers for storing data of the platforms (1, 2).

3. A system according to claim 1 or claim 2, wherein the Exchange Module (3) comprises:

a Input Module for receiving inputs relating to the conversion from either one of the platforms;

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 the database server, and to activate the retrieved converter for perform two ways conversion between the table-based file format and the Electronic Document (eDoc) format.

4. A system according to claim 3, wherein the Converter Controller Module comprises a Read Module for retrieving a dictionary for the insertion of data into a Electronic Document (eDoc);

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

a Updating Module for inserting data in the row into the Electronic Document (eDoc); a Transaction Processing Module for storing the Electronic Document (eDoc) into the database server; and

a Retrieval Module for retrieving sections and rows information from a Electronic Document (eDoc).

5. A system according to claim 3 or claim 4, wherein the modes of the conversion include a Batch Mode and a Online Mode.

6. A system according to claim 5, 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.

7. A system according to claim 5, 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.

8. A method for processing data bi-directionally comprising the steps of:

receiving request from either a relational table-based design platform (1) or a Emulating Manual System (eMS) platform (2);

retrieving, by the Exchange Module (3), data for conversion from a database server, retrieving, by the Exchange Module (3), a suitable type of converter from the database server; and

converting, by the Exchange Module (3), the format of the retrieved data into a designated format based on the received request;

9. A method for reading data from a Emulating Manual System platform (2)

SUBSTITUTE SHEETS (RULE 26) comprising the steps of:

receiving a request from a relational table-based design platform (1);

retrieving a designated Electronic Document (eDoc) from a database server;

converting the Electronic Document into table-based file format; and

displaying the converted file on the relational table-based design platform (1).

10. A method for reading data from a relational table-based design platform (1) comprising the steps of:

receiving a request from a Emulating Manual System (eMS) platform (2);

retrieving a designated table-based file from a database server;

converting the file into Electronic Document (eDoc) format; and

displaying the Electronic Document (eDoc) on the Emulating Manual System (eMS) platform (2).

11. A method for storing data from a Emulating Manual System (eMS) platform (2) comprising the steps of:

receiving a request from a relational table-based design platform (1);

retrieving a designated Electronic Document (eDoc) from a database server of the Emulating Manual System (eMS) platform (2);

converting the Electronic Document into table-based file format; and

storing the converted file in a database server of the relational table-based design platform (1).

12. A method for storing data from a relational table-based design platform (1) comprising the steps of:

receiving a request from a Emulating Manual System (eMS) platform (2);

retrieving a designated table-based file from a database server of the relational table- based design platform (1);

converting the file into Electronic Document (eDoc) format; and

SUBSTITUTE SHEETS (RULE 26) storing the Electronic Document (eDoc) in a database server of the Emulating Manual System (eMS) platform (2).

SUBSTITUTE SHEETS (RULE 26)