FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR DYNAMIC DATA MAPPING AND CONFIGURATION VIA A USER INTERFACE (UI)”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR DYNAMIC DATA MAPPING AND CONFIGURATION VIA A USER INTERFACE (UI)
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to product catalogue system. More particularly, embodiments of the present disclosure relate to dynamic data mapping and configuration via a user interface (UI).
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Enterprise Product Catalogue (EPC) enables organizations to effectively manage a catalogue of products that are relevant to customers. EPC helps organizations manage the end-to-end processes and product data relevant to product development, product launch, and product management activities of an organization. EPC provides relevant business components which are necessary to configure, integrate, and maintain the product and service catalogue across the enterprise. The management of product catalogues often involves working with multiple tables and mapping tables associated with them. The efficient management of data across multiple tables can be a complex and time-consuming task. Traditionally, users have had to manually navigate through various tables and enter data individually, which can lead to errors and inefficiencies. Additionally, configuring table dependencies and mapping different tables to each other often requires technical expertise and knowledge of database structures.

[0004] In managing product catalogues, users often deal with many tables and the connections between them. Creating forms for each table and showing related data has been difficult. In existing solution, this has required creating separate forms for each table and making many API calls to get the needed data, which complicates the process and increases the chance of mistakes. The users must often manually navigate through multiple tables and enter data, which is slow and prone to errors. Existing forms for data entry lack flexibility in setting up table connections and dependencies, limiting users' control over how tables relate to each other. This is particularly challenging for non-technical users who may struggle with the complexities of database structures.
[0005] Moreover, without an updated process, users have to manually update each table, leading to an inefficient workflow. This is problematic when handling large amounts of data. Some systems provide basic data entry forms, but they are often not intuitive or user-friendly, making the data entry process confusing and frustrating, which impacts overall productivity.
[0006] These issues in existing solutions highlight the need for a better system.
SUMMARY
[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0008] An aspect of the present disclosure may relate to a method for dynamic data mapping and configuration via a user interface (UI), the method comprising displaying, by a display unit, a UI for selection of a base table, wherein the base table is a primary table to which one or more mapping tables will be mapped. The

method comprises upon selection of the base table, adding, by an addition unit, the one or more mapping tables to the selected base table based on a first user input, wherein each of the one or more mapping tables is associated with the selected base table. The method comprises defining, by a definition unit, based on a second user input, a set of mapping properties for each of the one or more mapping tables. The method comprises storing, by a storage unit, the mapping properties to configure the base table. The method comprises displaying, by the display unit, the configured base table, wherein the configured base table is updated to a set of pre stored mapped data, which comprises data previously configured and stored based on the defined set of mappings between the base table and the one or more mapping tables according to a configuration of the UI.
[0009] In an exemplary aspect of the present disclosure, the UI is implemented using an Angular framework.
[0010] In an exemplary aspect of the present disclosure, the method further comprises enabling, by an enable unit, a user to define relationship and dependency between the base table and the one or more mapping tables based a third user input, wherein dependency corresponds to the relationship that dictates how data in one table is connected to data in another table.
[0011] In an exemplary aspect of the present disclosure, each of the one or more mapping tables comprise a set of data to be mapped.
[0012] In an exemplary aspect of the present disclosure, the method further comprises enabling, by the enable unit, a user to review and modify the set of pre stored mapped data.
[0013] In an exemplary aspect of the present disclosure, the set of mapping properties comprises at least a stepper name, a search table, and one or more configurations for filtering entries from the search table.

[0014] Another aspect of the present disclosure may relate to a system for dynamic data mapping and configuration via a user interface (UI), the system comprises a display unit configured to display a UI for selection of a base table, wherein the base table is a primary table to which one or more mapping tables will be mapped. The system comprises an addition unit connected to at least the display unit, wherein the addition unit configured to add the one or more mapping tables to the selected base table based on a first user input upon selection of the base table, wherein each of the one or more mapping tables is associated with the selected base table. The system comprises a definition unit connected to at least the addition unit, wherein the definition unit is configured to define, based on a second user input, a set of mapping properties for each of the one or more mapping tables. The system comprises a storing unit connected to at least the definition unit, wherein the storage unit is configured to store the mapping properties to configure the base table. The system comprises the display unit connected to at least the storage unit, wherein the display unit is configured to display the configured base table, wherein the configured base table is updated to a set of pre-stored mapped data, which comprises data previously configured and stored based on the defined set of mappings between the base table and the one or more mapping tables according to a configuration of the UI.
[0015] Another aspect of the present disclosure may relate to a user equipment (UE) for dynamic data mapping and configuration via a user interface (UI), the UE comprises a processor configured to display a UI for selection of a base table, wherein the base table is a primary table to which one or more mapping tables will be mapped. The processor is further configured to add the one or more mapping tables to the selected base table based on a first user input upon selection of the base table, wherein each of the one or more mapping tables is associated with the selected base table. The processor is further configured to define, based on a second user input, a set of mapping properties for each of the one or more mapping tables. The processor is further configured to store the mapping properties to configure the

base table. The processor is further configured to display the configured base table, wherein the configured base table is updated to a set of pre-stored mapped data, which comprises data previously configured and stored based on the defined set of mappings between the base table and the one or more mapping tables according to a configuration of the UI.
OBJECTS OF THE INVENTION
[0016] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0017] It is an object of the present disclosure to provide a system and method for dynamic data mapping and configuration via user interface wizard.
[0018] It is another object of the present disclosure to provide a system and method for dynamic data mapping and configuration via user interface wizard.
[0019] It is another object of the present disclosure to provide an efficient system for managing data across multiple tables. By offering a streamlined workflow and automated processes, the invention aims to improve the overall efficiency and accuracy of product catalogue tasks.
[0020] It is another object of the present disclosure to provide a system and method for dynamic data mapping and configuration via user interface wizard that enables dynamic table mapping. Users can easily configure the relationships between tables, allowing for flexible management of product catalogue and eliminating the need for manual navigation and data entry in individual table sheets.
[0021] It is another object of the present disclosure to provide a user-friendly interface that simplifies the data entry process. By guiding users through a wizard-

based system, the invention enhances usability and reduces the learning curve, making it accessible to users with varying levels of technical expertise.
[0022] It is another object of the present disclosure to provide a system and method that seeks to save time and effort by eliminating the need for manual data entry in multiple tables. Users can efficiently populate tables through the wizard interface, reducing errors and enhancing productivity.
[0023] It is another object of the present disclosure to provide a system and method that aims to improve the accuracy of product catalogue. By reducing manual input and providing predefined values, the invention minimizes the risk of data inconsistencies and errors.
[0024] It is yet another object of the present disclosure to provide a system and method that allows users to configure table dependencies easily. Users can define relationships between tables, enabling efficient data mapping and ensuring data integrity across the system.
DESCRIPTION OF THE DRAWINGS
[0025] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0026] FIG. 1 illustrates an exemplary block diagram of a computing device [100] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0027] FIG. 2 illustrates an exemplary block diagram of a system [200] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
[0028] FIG. 3 illustrates a method flow diagram [300] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
[0029] FIG.4 illustrates an exemplary signalling flow diagram [400] for dynamic data mapping and configuration via a user interface, in accordance with exemplary embodiments of the present disclosure.
[0030] FIG. 5 illustrates an exemplary network architecture [500] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
[0031] FIG. 6A illustrates an exemplary network architecture [500] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
[0032] FIG. 6B illustrates an exemplary network architecture [500] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.

[0033] FIG. 7A illustrates an exemplary network architecture [500] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
5 [0034] FIG. 7B illustrates an exemplary network architecture [500] for dynamic
data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
[0035] FIG. 8A illustrates an exemplary network architecture [500] for dynamic
10 data mapping and configuration via a user interface, in accordance with exemplary
implementations of the present disclosure.
[0036] FIG. 8B illustrates an exemplary network architecture [500] for dynamic
data mapping and configuration via a user interface, in accordance with exemplary
15 implementations of the present disclosure.
[0037] FIG. 9A illustrates an exemplary network architecture [500] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure. 20
[0038] FIG. 9B illustrates an exemplary network architecture [500] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
25 [0039] FIG. 10A illustrates an exemplary network architecture [500] for dynamic
data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
[0040] FIG. 10B illustrates an exemplary network architecture [500] for dynamic
30 data mapping and configuration via a user interface, in accordance with exemplary
implementations of the present disclosure.
9

[0041] FIG. 11A illustrates an exemplary network architecture [500] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure. 5
[0042] FIG.11B illustrates an exemplary network architecture [500] for dynamic data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
10 [0043] FIG. 12A illustrates an exemplary network architecture [500] for dynamic
data mapping and configuration via a user interface, in accordance with exemplary implementations of the present disclosure.
[0044] FIG. 12B illustrates an exemplary network architecture [500] for dynamic
15 data mapping and configuration via a user interface, in accordance with exemplary
implementations of the present disclosure.
[0045] The foregoing shall be more apparent from the following more detailed description of the disclosure. 20
DETAILED DESCRIPTION
[0046] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of
25 embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the
30 problems discussed above.
10

[0047] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment.
5 It should be understood that various changes may be made in the function and
arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0048] Specific details are given in the following description to provide a thorough
10 understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. 15
[0049] Also, it is noted that individual embodiments may be described as a process
which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations may be performed in parallel or
20 concurrently. In addition, the order of the operations may be re-arranged. A process
is terminated when its operations are completed but could have additional steps not included in a figure.
[0050] The word “exemplary” and/or “demonstrative” is used herein to mean
25 serving as an example, instance, or illustration. For the avoidance of doubt, the
subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
30 known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
11

description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.
5 [0051] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital
10 Signal Processing) DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or
15 processing unit is a hardware processor.
[0052] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a
20 communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable
25 of implementing the features of the present disclosure. Also, the user device may
contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
30 [0053] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
12

form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other
types of machine-accessible storage media. The storage unit stores at least the data
5 that may be required by one or more units of the system to perform their respective
functions.
[0054] As used herein “interface” or “user interface” refers to a shared boundary
across which two or more separate components of a system exchange information
10 or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
15 [0055] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller,
20 Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc. As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected
25 with the system.
[0056] As discussed in the background section, traditional systems require users to
manually navigate through multiple tables and enter data individually. This process
is time-consuming and prone to errors, as users may accidentally input incorrect or
30 inconsistent data. Existing data entry forms often lack flexibility in mapping tables
and configuring dependencies. Users have limited control over the relationships
13

between tables, making it difficult to handle complex data management scenarios. Configuring table dependencies and mapping different tables to each other typically requires technical expertise and knowledge of database structures. This creates a barrier for non-technical users who may struggle with the complexities involved. 5
[0057] Without a streamlined process, users may need to access and manually
update individual table sheets, leading to a fragmented and inefficient workflow.
This approach is time-consuming and prone to errors, especially when dealing with
large datasets. Some existing systems provide basic data entry forms, but they lack
10 an intuitive and user-friendly interface. This can make the data entry process
confusing and frustrating for users, impacting overall productivity.
[0058] These problems and limitations in the existing solutions necessitate the
development of a system and method for dynamic data mapping and configuration
15 via user interface wizard. The present invention addresses these problems by
providing an efficient table mapping and data entry wizard that offers a user-friendly interface, dynamic table mapping, and streamlined data entry processes.
[0059] The present disclosure aims to overcome the above-mentioned and other
20 existing problems in this field of technology by providing a method and system of
dynamic data mapping and configuration via a user interface (UI). The present
invention provides an efficient table mapping and data entry wizard that offers a
user-friendly interface, dynamic table mapping, and streamlined data entry
processes. The present invention simplifies the task of managing data spread across
25 different tables. It replaces the tedious manual work with an easy-to-use wizard.
This means users don't have to spend hours navigating through tables or worry about making mistakes. Instead, they can effortlessly organize their data with a few simple clicks, making their work much smoother and more efficient.
30 [0060] FIG. 1 illustrates an exemplary block diagram of a computing device [100]
upon which the features of the present disclosure may be implemented in
14

accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [100] may also implement a method for one
or more complaint resolutions utilising the system [200]. In another
implementation, the computing device [100] itself implements the method for one
5 or more complaint resolutions using one or more units configured within the
computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0061] The computing device [100] may include a bus [102] or other
10 communication mechanism for communicating information, and a hardware
processor [104] coupled with bus [102] for processing information. The hardware
processor [104] may be, for example, a general-purpose microprocessor. The
computing device [100] may also include a main memory [106], such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus
15 [102]for storing information and instructions to be executed by the processor [104].
The main memory [106] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [104]. Such instructions, when stored in non-transitory storage media
accessible to the processor [104], render the computing device [100] into a special-
20 purpose machine that is customized to perform the operations specified in the
instructions. The computing device [100] further includes a read only memory
(ROM) [108] or other static storage device coupled to the bus [102] for storing static
information and instructions for the processor [104].
25 [0062] A storage device [110], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
30 displaying information to a computer user. An input device [114], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
15

bus [102] for communicating information and command selections to the processor
[104]. Another type of user input device may be a cursor controller [116], such as a
mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [104], and for controlling
5 cursor movement on the display [112]. The input device typically has two degrees
of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0063] The computing device [100] may implement the techniques described
10 herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [100] causes
or programs the computing device [100] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
computing device [100] in response to the processor [104] executing one or more
15 sequences of one or more instructions contained in the main memory [106]. Such
instructions may be read into the main memory [106] from another storage medium,
such as the storage device [110]. Execution of the sequences of instructions
contained in the main memory [106] causes the processor [104] to perform the
process steps described herein. In alternative implementations of the present
20 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0064] The computing device [100] also may include a communication interface
[118] coupled to the bus [102]. The communication interface [118] provides a two-
25 way data communication coupling to a network link [120] that is connected to a
local network [122]. For example, the communication interface [118] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [118] may be a
30 local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [118] sends and receives electrical,
16

electromagnetic or optical signals that carry digital data streams representing various types of information.
[0065] The computing device [100] can send messages and receive data, including
5 program code, through the network(s), the network link [120] and the
communication interface [118]. In the Internet example, a server [130] might
transmit a requested code for an application program through the Internet [128], the
ISP [126], the local network [122], the host [124] and the communication interface
[118]. The received code may be executed by the processor [104] as it is received,
10 and/or stored in the storage device [110], or other non-volatile storage for later
execution.
[0066] Referring to FIG. 2, an exemplary block diagram of a system [200] for dynamic data mapping and configuration via a user interface (UI), is shown, in
15 accordance with the exemplary implementations of the present disclosure. The
system [200] comprises at least one display unit [202], at least one addition unit [204], at least one definition unit [206], at least one storage unit [208] and at least one enable unit [210]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. As shown
20 in the figures all units shown within the system should also be assumed to be
connected to each other. Also, in FIG. 1 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present in a user
25 device to implement the features of the present disclosure. The system [200] may
be a part of the user device / or may be independent of but in communication with the user device (may also be referred herein as a UE). In another implementation, the system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity
30 and partly in the user device.
17

[0067] The system [200] is configured for dynamic data mapping and
configuration via a user interface (UI), with the help of the interconnection
between the components/units of the system [200]. The system [200] enables
dynamic table mapping where users can easily configure the relationships between
5 tables, allowing for flexible data management and eliminating the need for manual
navigation and data entry in individual table sheets. The system enables users to
add multiple mapping tables to the data management system. Users can
dynamically create and define these additional tables based on their specific
requirements. The ability to add multiple mapping tables provides flexibility and
10 accommodates complex data scenarios that involve multiple related entities or data
categories. Once users have added the mapping tables, they can configure the relationships between these tables and a base table.
[0068] The system [200] comprises a display unit [202] configured to
15 display a UI for selection of a base table, wherein the base table is a primary table
to which one or more mapping tables will be mapped. Further, the display unit [202] is responsible for showing the UI where a user can select a primary table, known as the base table. The selection of a base table involves presenting a user interface (UI) where a user can choose a primary table from a list or database. This
20 base table serves as the central reference point to which other tables, known as
mapping tables, will be connected. The selection process can be done through checkboxes, highlighting, or other user-friendly selection mechanisms. The UI presented for selection is a Wizard interface. An exemplary screenshot depicting the selection of a base table and mentioning the wizard’s name has been shown in
25 FIG 6A. The user interface for creating the wizard configuration allows users to
define the base table and add mapping tables as required. Users can specify the properties and attributes of these tables, such as field names, data types, and relationships between tables. The base table is a primary table in the product catalogue system. It serves as the starting point or reference point for the data
30 mappings. The wizard interface provides a structured framework for the data entry
process and includes options to define a base table and one or more mapping tables,
18

wherein each of the one or more mapping tables comprises a set of data to be
mapped. Mapping tables are additional tables in the system that are linked to the
base table. Users can define one or more mapping tables within the wizard
configuration. These mapping tables establish connections and dependencies with
5 the base table, enabling the mapping of relevant data entries. The set of data within
a mapping table includes rows and columns of information that corresponds to the fields and records in a database table. Each record within the set can be uniquely identified and may contain multiple fields or attributes that describe the properties or characteristics of the data. 10
[0069] Further, the UI is implemented using an Angular framework, wherein
Angular is a robust platform and framework for building single-page client
applications using (Hypertext Markup Language (HTML), Cascading Style Sheets
(CSS), and TypeScript. Angular features a component-based architecture, allowing
15 developers to create reusable and modular components. It supports powerful data
binding, dependency injection, and directives to extend HTML capabilities. The
framework includes a sophisticated routing system, extensive forms handling, and
leverages Reactive Extension for JavaScript (RxJS) for managing asynchronous
operations. Angular's CLI automates development tasks, and its use of TypeScript
20 ensures type safety and modern JavaScript features. Overall, Angular simplifies the
development of dynamic, scalable, and maintainable web applications.
[0070] The wizard interface is a graphical user interface (GUI) presented to the user during the data entry process. It serves as a visual and interactive platform that
25 guides the user through the steps required to enter and map data. The interface is
designed to be intuitive, user-friendly, and visually appealing. The wizard interface follows a step-by-step approach, breaking down the data entry process into manageable stages. Each step focuses on a specific aspect of data entry, guiding the user through the entry of data for the base table and mapping tables.
30
19

[0071] The interface ensures that users follow a structured path and complete all
necessary data entry tasks. Within each step of the wizard interface, guidance is
provided to the user on what data to enter and how to enter it. Clear instructions,
tooltips, and examples are offered to help users understand the required data format
5 and ensure accurate entry. The guidance ensures that users enter the necessary data
in the correct fields and formats. The wizard interface guides the user through the data entry process for both the base table and the mapping tables.
[0072] The user is prompted to enter relevant data for the base table and then
10 proceed to the mapping tables, entering data as per the defined relationships and
mapping properties. This ensures that all necessary data is entered and linked
appropriately. The wizard interface includes validation checks to ensure data
accuracy and integrity. The user is notified of any errors or missing data during the
data entry process, allowing them to correct or provide the required information
15 before proceeding to the next step. This helps in maintaining data quality and
consistency. By presenting a wizard interface to the user for data entry, the system
streamlines the data entry process and ensures that the user follows a structured
approach. The interface guides the user through the entry of data for the base table
and mapping tables, providing clear instructions and error handling mechanisms.
20 This step enhances the user experience and improves the accuracy and efficiency
of the data entry and mapping processes.
[0073] The system [200] further comprises an addition unit [204] connected to at least the display unit [202], wherein the addition unit [204] is configured to add the
25 one or more mapping tables to the selected base table based on a first user input
upon selection of the base table, wherein each of the one or more mapping tables is associated with the selected base table. The addition unit [204] adds the mapping tables to the selected base table based on user input. Each mapping table is associated with the base table. The user is given the ability to define mapping
30 properties for each mapping table.
20

[0074] The first user input is the initial action provided by the user, through the UI,
to add one or more mapping tables to the selected base table. The selection of the
base table is executed via the UI, where a user can interact with a list-based
representation of available tables and choose the primary table that will serve for
5 data mapping. Further, this can be done through text input, selection from
predefined options, or other appropriate input methods based on the field's data type and requirements.
[0075] In an implementation of the present disclosure, in a product catalogue, a
10 "Products" table may serve as the base table, representing the main source of all
products. The user interface displayed by the display unit [202] allows the user to
select the "Products" table as the base table. Upon selection, the addition unit [204]
can add related tables such as "Product Details" "Pricing" and "Inventory" as
mapping tables, establishing the necessary associations with the base table. A user
15 accesses the user interface and creates a wizard configuration. They define the base
table as "Products" and add the mapping tables "Orders", "Customers" and "Inventory" to the configuration. An exemplary screenshot depicting the process has been shown in FIG 6B.
20 [0076] The system [200] further comprises a definition unit [206] connected to at
least the addition unit [204], wherein the definition unit [206] is configured to define, based on a second user input, a set of configurations for each of the one or more mapping tables. An exemplary screenshot depicting the process has been shown in 7A. The definition unit [206] defines the configurations for each mapping
25 table based on user input, which enables the user to configure the respective
relationships to the base table. The second user input is the later action provided by the user to define configurations for the mapping tables, including setting parameters and specifying how the data should be handled. The set of configurations comprises at least a stepper name, a search table, and one or more
30 mapping properties corresponding to the search table. The stepper name refers to
an interface name assigned to a particular mapping table. It provides a unique
21

identifier for the mapping table within the system. The UI allows the user to search
for entries in the mapping tables and select multiple rows to be mapped with the
base table; providing the user with the option to specify values for fields that are
not pre-defined or mapped in the wizard configuration. This enables the user to save
5 and submit the mappings, thereby completing the data entry process and storing the
mapped data in the data management system. An exemplary screenshot depicting the process has been shown in FIG 7B.
10 [0077] The user can define and assign a descriptive name that reflects the purpose
or function of the mapping table. This name helps the user distinguish and manage multiple mapping tables effectively. The search table is the table from which entries will be searched or retrieved during the mapping process. The user can specify the search table for each mapping table individually. It allows the user to choose a
15 specific table that contains the relevant data entries required for mapping with the
base table. The user has the ability to define properties for filtering entries within the mapping tables. These properties serve as criteria for selecting or filtering specific entries from the search table. The user can specify various conditions or rules based on field values, such as selecting entries that meet specific criteria or
20 filtering out irrelevant entries. An exemplary screenshot depicting the process has
been shown in FIG 8A.
[0078] In an implementation of the present disclosure, in the product catalogue, in the next steps, the user may want to define how product details, pricing information,
25 and inventory levels are mapped to the "Products" table. The UI provided by the
display unit allows the user to customize these mapping properties, such as linking product IDs to specific details, pricing tiers, or inventory statuses. The user proceeds to define mapping properties for each mapping table. For the "Orders" mapping table, they specify the stepper name as "Order Mapping" the search table
30 as "Customers" and properties for filtering entries based on customer information.
The user configures the relationships between the base table and the mapping tables.
22

The user establishes connections between the "Products" table and the "Orders"
"Customers" and "Inventory" tables, ensuring that the data entries are linked
correctly. The user is presented with a wizard interface that guides them through
the data entry process. The user follows the step-by-step instructions and enter
5 product information, such as name, description, and price, in the "Products" table.
In the next steps, the user searches for customer entries in the "Customers" table and selects multiple rows that are associated with the products they entered. This links the customer information to the corresponding products in the "Orders" table. An exemplary screenshot depicting the process has been shown in FIG. 8B and 9A.
10
[0079] The user has the option to specify values for fields that are not pre-defined or mapped in the wizard configuration. For example, they can input additional details in the "Inventory" table, such as stock quantity and location, that are specific to each product. An exemplary screenshot depicting the process has been shown in
15 FIG 9B.
[0080] The wizard provides the user with the option to specify values for fields that
are not pre-defined or mapped in the wizard configuration. During the data entry
process, the system allows the user to specify values for fields that are not pre-
20 defined or mapped in the wizard configuration. This step gives the user the
flexibility to add additional data and ensure that all necessary fields are filled, even
if they were not explicitly defined in the initial mapping configuration. The system
recognizes that data requirements may vary beyond the pre-defined or mapped
fields in the wizard configuration. To accommodate this, it provides the user with
25 the option to specify values for additional fields that are not predefined or mapped.
These are fields within the base table or mapping tables that have not been explicitly
defined or included in the initial wizard configuration. The user may encounter such
fields during the data entry process and need to provide values for them. When the
user comes across an unmapped field, the system prompts them to specify a value
30 for that field. This can be done through text input, selection from predefined
options, or other appropriate input methods based on the field's data type and
23

requirements. The wizard ensures that the values specified for unmapped fields
adhere to the appropriate data types and validation rules. It performs necessary data
consistency checks and provides feedback or error messages to users if any
inconsistencies are detected. By allowing the user to specify values for unmapped
5 fields, the system ensures the completeness of the data entry process. The user can
provide the necessary information, even if it goes beyond the initially defined fields,
ensuring comprehensive and accurate data representation. This step offers the user
the flexibility to include additional data fields that may not have been considered
during the initial wizard configuration. By enabling the user to specify values for
10 these unmapped fields, the system ensures that all necessary information is
captured, providing a more comprehensive and customized data entry experience. An exemplary screenshot depicting the process has been shown in FIG 10A.
[0081] The system [200] further comprises a storage unit [208] connected to at least
15 the definition unit [206], wherein the storage unit [208] is configured to store the
set of configurations to configure the base table. The storage unit [208] stores the set of configurations to configure the base table. It ensures that the configurations for the one or more mapping tables made by the user are saved for future reference.
20 [0082] In an implementation of the present disclosure, in the next steps, in the
product catalogue, once the data entry process is complete, the user saves and submits the mappings. The entered data, along with the mapped relationships, is stored in the data management system. The system [200] enables the user to save and submit the mappings, thereby completing the data entry process and storing the
25 mapped data in the data management system. After the user has completed the data
entry and mapping process, the system enables them to save and submit the mappings. This step finalizes the data entry process and ensures that the mapped data is stored securely within the data management system. An exemplary screenshot depicting the process has been shown in FIG 10b, 11A and 11B.
30
24

[0083] The system provides a save function that allows the user to save their
entered data and mappings. This function captures all the information and
associations made during the data entry process. In addition to saving the mappings,
the system offers a submit function that signifies the completion of the data entry
5 process. When the user submits their mappings, it indicates that they are ready to
finalize the data entry and proceed with further data management tasks. Upon
submission, the system stores the mapped data securely within the data
management system. This ensures that the entered data, along with its associated
relationships and mappings, is stored for future access and retrieval. The system
10 performs data validation and integrity checks before saving and storing the mapped
data. It verifies that the entered data meets the defined criteria and conforms to the
required formats. Any inconsistencies or errors are highlighted to the user for
correction before final submission. By enabling the user to save and submit the
mappings, the system ensures the completion of the data entry process. An
15 exemplary screenshot depicting this process has been shown in FIG. 12A and 12B.
The secure storage of the mapped data guarantees its availability for future use and analysis. This step maintains data integrity and allows the user to leverage the entered data within the data management system for various purposes, further enhancing the overall data management experience. 20
[0084] The system [200] further comprises the display unit [202]
configured to display the configured base table, wherein the configured base table
is updated to a set of pre stored mapped data, which comprises data previously
configured and stored based on the defined set of mappings between the base table
25 and the one or more mapping tables according to a configuration of the UI. Some
data fields have been considered during the initial wizard configuration, which are
pre stored with the configuration settings. These are fields within the base table or
mapping tables that have not been explicitly defined or included in the initial
wizard configuration. Therefore, the previously configured means that the data and
30 its mappings have been set up in advance, with relationships and dependencies
between the base table and mapping tables already defined and stored in the
25

system. The defined set refers to a specific group of configurations and parameters that have been explicitly detailed and saved.
[0085] In an aspect of the present disclosure, the display unit [202] is configured to
5 present the configured base table to the user. This base table undergoes updates to
reflect a set of pre-stored mapped data. This data encompasses information previously configured and stored for each of the one or more mapping tables, based on the defined mappings between the base table and the associated mapping tables, as dictated by the configuration of the user interface (UI). The display unit serves
10 as the interface through which the user can interact with the dynamically updated
base table, showcasing the results of the mapping process in a clear and accessible manner. The set of pre-stored mapped data refers to a predetermined collection of information that has been previously configured and stored within the system. This data is specifically related to the mappings between the base table and one or more
15 associated mapping tables. The term "pre-stored" indicates that this data has been
saved in advance, ready for retrieval and use when needed. "Mapped data" signifies the information resulting from the mapping process, where data from different tables is linked and organized according to specified relationships and dependencies. The configuration of the UI involves designing and setting up the
20 user interface to allow users to interact with and control the data mapping and
configuration processes. This includes elements like menus, forms, buttons, and displays that facilitate user input and control.
[0086] Further, the display unit [202] presents the configured "Products" table to
25 the user, updated with pre-stored mapped data from the "Product Details", "Pricing"
and "Inventory" tables. This allows the user to view an integrated and updated
product catalogue. Once the mappings are saved and submitted, the user can
proceed with other data management tasks within the system. They can perform
analyses, generate reports, extract data, or carry out any other relevant operations
30 using the stored and mapped data.
26

[0087] Further, the method comprises enabling, by an enable unit [210], a user to
define relationship and dependency between the base table and the one or more
mapping tables based on a third user input, wherein dependency corresponds to the
relationship that dictates how data in one table is connected to data in another table.
5 The present disclosure encompasses the enable unit [210], that enables the user to
define the relationships and dependencies between the base table and the associated mapping tables. This capability is triggered by a third user input, indicating the user's intention to establish these connections. The third user input is an action given by the user to define the relationships and dependencies between the base table and
10 the mapping tables, detailing how data connections are to be established. These
mapping tables establish connections and dependencies with the base table, enabling the mapping of relevant data entries. The data in another table refers to the information stored in the mapping tables, which is to be linked with the base table according to the defined mappings and configurations.
15
[0088] The term "relationship" denotes the way data in one table relates to data in another, encompassing diverse types of associations such as one-to-one, one-to-many, or many-to-many relationships. Meanwhile, "dependency" refers to the relationship that governs how data from one table depends on or is influenced by
20 data in another table. This could include hierarchical dependencies or constraints
such as foreign key relationships.
[0089] In an implementation, the enable unit [210] is further configured to enable a user to review and modify the set of pre stored mapped data. This functionality
25 allows the user to access the stored dataset previously generated through the
mapping process and make necessary adjustments based on their specific requirements. By providing the user with the capability to review and modify the pre-stored mapped data, the system enhances user control and flexibility in managing their datasets. To review and modify pre-stored mapped data, the user
30 accesses the data mapping UI and navigates to the section displaying the base table
and its mappings. They view the pre-stored data, select the mapping table to modify,
27

and make necessary changes to configurations like relationships and dependencies.
After saving these changes, the system updates and stores the new configurations,
which are then reflected in the UI. During the data entry process, the system [200]
allows users to specify values for fields that are not pre-defined or mapped in the
5 wizard configuration. This step gives users the flexibility to add additional data and
ensure that all necessary fields are filled, even if they were not explicitly defined in the initial mapping configuration. The system [200] recognizes that data requirements may vary beyond the pre-defined or mapped fields in the wizard configuration. To accommodate this, it provides users with the option to specify
10 values for additional fields that are not predefined or mapped. These are fields
within the base table or mapping tables that have not been explicitly defined or included in the initial wizard configuration. Users may encounter such fields during the data entry process and need to provide values for them. When users come across an unmapped field, the system prompts them to specify a value for that field.
15
[0090] In an implementation of the present disclosure, in the product catalogue, the user can define a relationship where each product in the "Products" table is linked to pricing information from the "Pricing" table and inventory levels from the "Inventory" table. The users may be review and modify these mappings to ensure
20 the data remains up to date, reflecting changes in product details, pricing, and
inventory.
[0091] Referring to FIG. 3, an exemplary method flow diagram [300] for dynamic data mapping and configuration via a user interface (UI), in accordance with
25 exemplary implementations of the present disclosure is shown. In an
implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302].
30
28

[0092] At step 304, the method comprises displaying, by a display unit [202], a UI
for selection of a base table, wherein the base table is a primary table to which one
or more mapping tables will be mapped. The present disclosure comprises the
‘dynamic data mapping’ refers to the process of establishing relationships and data
5 correspondences between different datasets or tables and configuration refers to the
setup and arrangement of software and data elements. The term ‘configuration’ refers to the setup and arrangement of software and data elements according to parameters and rules defined by the user. Further, the display unit [202] is responsible for showing the user interface (UI) where the user can select a primary
10 table, known as the base table. The selection of a base table involves presenting a
user interface (UI) where a user can choose a primary table from a list or database. This base table serves as the central reference point to which other tables, known as mapping tables, will be connected. An exemplary screenshot depicting the selection of a base table and mentioning the wizard’s name has been shown in FIG
15 6A The UI presented is a Wizard interface. The base table is a primary table in the
product catalogue system. It serves as the starting point or reference point for the data mappings. The wizard interface provides a structured framework for the data entry process and includes options to define a base table and one or more mapping tables, wherein each of the one or more mapping tables comprise a set of data to be
20 mapped. The one or more tables will be mapped means that the selected base table
will be linked to mapping tables which contain data that needs to be correlated with the base table. The mapping process involves defining how data fields in the mapping tables correspond to fields in the base table. The set of data within a mapping table includes rows and columns of information that correspond to the
25 fields and records in a database table. Each record within the set can be uniquely
identified and may contain multiple fields or attributes that describe the properties or characteristics of the data. Further, the wizard UI is implemented using an Angular framework, wherein Angular is a robust platform and framework for building single-page client applications using (Hypertext Markup Language
30 (HTML), Cascading Style Sheets (CSS), and TypeScript. Angular features a
component-based architecture, allowing developers to create reusable and modular
29

components. It supports powerful data binding, dependency injection, and
directives to extend HTML capabilities. The framework includes a sophisticated
routing system, extensive forms handling, and leverages Reactive Extension for
JavaScript (RxJS) for managing asynchronous operations. Angular's CLI automates
5 development tasks, and its use of TypeScript ensures type safety and modern
JavaScript features. Overall, Angular simplifies the development of dynamic, scalable, and maintainable web applications.
[0093] The wizard interface is a graphical user interface (GUI) presented to the user
10 during the data entry process. It serves as a visual and interactive platform that
guides users through the steps required to enter and map data. The interface is
designed to be intuitive, user-friendly, and visually appealing. The wizard interface
follows a step-by-step approach, breaking down the data entry process into
manageable stages. Each step focuses on a specific aspect of data entry, guiding the
15 user through the entry of data for the base table and mapping tables.
[0094] At step 306, upon selection of the base table, adding, by an addition unit [204], the one or more mapping tables to the selected base table based on a first user input, wherein each of the one or more mapping tables is associated with the
20 selected base table. The addition unit [204] adds the mapping tables to the selected
base table based on user input. Each mapping table is associated with the base table. The user is given the ability to define mapping properties for each mapping table. The first user input is the initial action provided by the user, through the UI, to add one or more mapping tables to the selected base table. The selection of the base
25 table is executed via the UI, where a user can interact with a list-based
representation of available tables and choose the primary table that will serve for data mapping.
[0095] In an implementation of the present disclosure, in a product catalogue, a
30 "Products" table may serve as the base table, representing the main source of all
products. The user interface displayed by the display unit [202] allows the user to
30

select the "Products" table as the base table. Upon selection, the addition unit [204]
can add related tables such as "Product Details," "Pricing" and "Inventory" as
mapping tables, establishing the necessary associations with the base table. A user
accesses the user interface and creates a wizard configuration. The user defines the
5 base table as "Products" and adds the mapping tables "Orders," "Customers," and
"Inventory" to the configuration. An exemplary screenshot depicting the process has been shown in FIG 6B.
[0096] At step 308, defining, by a definition unit [206], based on a second user
10 input, a set of configurations for each of the one or more mapping tables. An
exemplary screenshot depicting the process has been shown in 7A. The definition unit [206] defines the configurations for each mapping table based on user input. The set of configurations comprises at least a stepper name, a search table, and one or more mapping properties corresponding to the search table. The stepper name
15 refers to an interface name assigned to a particular mapping table. It provides a
unique identifier for the mapping table within the system. The second user input is the later action provided by the user to define configurations for the mapping tables, including setting parameters and specifying how the data should be handled. An exemplary screenshot depicting the process has been shown in FIG 7B.
20
[0097] The user can define and assign a descriptive name that reflects the purpose or function of the mapping table. This name helps user distinguish and manage multiple mapping tables effectively. The search table is the table from which entries will be searched or retrieved during the mapping process. The user can specify the
25 search table for each mapping table individually. It allows the user to choose a
specific table that contains the relevant data entries required for mapping with the base table. The user may define properties for filtering entries within the mapping tables. These properties serve as criteria for selecting or filtering specific entries from the search table. The user can specify various conditions or rules based on
30 field values, such as selecting entries that meet specific criteria or filtering out
31

irrelevant entries. An exemplary screenshot depicting the process has been shown in FIG 8A.
[0098] In an implementation of the present disclosure, in the product catalogue, in
5 the next steps, the user may want to define how product details, pricing information,
and inventory levels are mapped to the "Products" table. The UI provided by the display unit allows the user to customize these mapping properties, such as linking product IDs to specific details, pricing tiers, or inventory statuses. The user proceeds to define mapping properties for each mapping table. For the "Orders"
10 mapping table, they specify the stepper name as "Order Mapping" the search table
as "Customers" and properties for filtering entries based on customer information. The user configures the relationships between the base table and the mapping tables. The user establishes connections between the "Products" table and the "Orders," "Customers" and "Inventory" tables, ensuring that the data entries are linked
15 correctly.: The user is presented with a wizard interface that guides them through
the data entry process. They follow the step-by-step instructions and enter product information, such as name, description, and price, in the "Products" table. In the next steps, the user searches for customer entries in the "Customers" table and selects multiple rows that are associated with the products they entered. This links
20 the customer information to the corresponding products in the "Orders" table. An
exemplary screenshot depicting the process has been shown in FIG. 8B and 9A.
[0099] The user has the option to specify values for fields that are not pre-defined
or mapped in the wizard configuration. For example, they can input additional
25 details in the "Inventory" table, such as stock quantity and location, that are specific
to each product. An exemplary screenshot depicting the process has been shown in FIG 9B.
[0100] The wizard provides the user with the option to specify values for fields that
30 are not pre-defined or mapped in the wizard configuration. During the data entry
process, the system allows the user to specify values for fields that are not pre-
32

defined or mapped in the wizard configuration. This step gives users the flexibility
to add additional data and ensure that all necessary fields are filled, even if they
were not explicitly defined in the initial mapping configuration. The system
recognizes that data requirements may vary beyond the pre-defined or mapped
5 fields in the wizard configuration. To accommodate this, it provides the user with
the option to specify values for additional fields that are not predefined or mapped. These are fields within the base table or mapping tables that have not been explicitly defined or included in the initial wizard configuration. The user may encounter such fields during the data entry process and need to provide values for them. When the
10 user comes across an unmapped field, the system prompts them to specify a value
for that field. This can be done through text input, selection from predefined options, or other appropriate input methods based on the field's data type and requirements. The system ensures that the values specified for unmapped fields adhere to the appropriate data types and validation rules. It performs necessary data
15 consistency checks and provides feedback or error messages to the user if any
inconsistencies are detected. By allowing the user to specify values for unmapped fields, the system ensures the completeness of the data entry process. The user can provide the necessary information, even if it goes beyond the initially defined fields, ensuring comprehensive and accurate data representation. This step offers the user
20 the flexibility to include additional data fields that may not have been considered
during the initial wizard configuration. By enabling the user to specify values for these unmapped fields, the system ensures that all necessary information is captured, providing a more comprehensive and customized data entry experience. An exemplary screenshot depicting the process has been shown in FIG 10A.
25
[0101] At step 310, storing, by a storage unit [208], the set of configurations to configure the base table. The present disclosure comprises the storage unit [208] stores the set of configurations configure the base table. It ensures that the configurations for the one or more mapping tables made by the user are saved for
30 future reference.
33

[0102] In an implementation of the present disclosure, in the next steps, in the
product catalogue, once the data entry process is complete, the user saves and
submits the mappings. The entered data, along with the mapped relationships, is
stored in the data management system. The system [200] enables the user to save
5 and submit the mappings, thereby completing the data entry process and storing the
mapped data in the data management system. After the user has completed the data
entry and mapping process, the system enables them to save and submit the
mappings. This step finalizes the data entry process and ensures that the mapped
data is stored securely within the data management system. An exemplary
10 screenshot depicting the process has been shown in FIG 10B, 11A and 11B.
[0103] The system provides a save function that allows the user to save their entered data and mappings. This function captures all the information and associations made during the data entry process. An exemplary screenshot depicting
15 this process has been shown in FIG. 12A and 12B. In addition to saving the
mappings, the system offers a submit function that signifies the completion of the data entry process. When the user submits their mappings, it indicates that they are ready to finalize the data entry and proceed with further data management tasks. Upon submission, the system stores the mapped data securely within the data
20 management system. This ensures that the entered data, along with its associated
relationships and mappings, is stored for future access and retrieval. The system performs data validation and integrity checks before saving and storing the mapped data. It verifies that the entered data meets the defined criteria and conforms to the required formats. Any inconsistencies or errors are highlighted to the user for
25 correction before final submission. By enabling the user to save and submit the
mappings, the system ensures the completion of the data entry process. The secure storage of the mapped data guarantees its availability for future use and analysis. This step maintains data integrity and allows the user to leverage the entered data within the data management system for various purposes, further enhancing the
30 overall data management experience.
34

[0104] At step 312, displaying, by the display unit [202], the configured base table,
wherein the configured base table is updated to a set of pre stored mapped data,
which comprises data previously configured and stored based on the defined set of
mappings between the base table and the one or more mapping tables according to
5 a configuration of the UI. The previously configured means that the data and its
mappings have been set up in advance, with relationships and dependencies between the base table and mapping tables already defined and stored in the system. The defined set refers to a specific group of configurations and parameters that have been explicitly detailed and saved.
10
[0105] In an example, the present disclosure encompasses the display unit [202] to present the configured base table to the user. This base table undergoes updates to reflect a set of pre-stored mapped data. This data encompasses information previously configured and stored for each of the one or more mapping tables, based
15 on the defined mappings between the base table and the associated mapping tables,
as dictated by the configuration of the user interface (UI). The display unit serves as the interface through which users can interact with the dynamically updated base table, showcasing the results of the mapping process in a clear and accessible manner. The set of pre-stored mapped data refers to a predetermined collection of
20 information that has been previously configured and stored within the system. This
data is specifically related to the mappings between the base table and one or more associated mapping tables. The term "pre-stored" indicates that this data has been saved in advance, ready for retrieval and use when needed. "Mapped data" signifies the information resulting from the mapping process, where data from different
25 tables is linked and organized according to specified relationships and
dependencies. The configuration of the UI involves designing and setting up the user interface to allow users to interact with and control the data mapping and configuration processes. This includes elements like menus, forms, buttons, and displays that facilitate user input and control.
30
35

[0106] In an implementation of the present disclosure, in the product catalogue, the
display unit [202] presents the configured "Products" table to the user, updated with
pre-stored mapped data from the "Product Details", "Pricing" and "Inventory"
tables. This allows the user to view an integrated and updated product catalogue.
5 Once the mappings are saved and submitted, the user can proceed with other data
management tasks within the system. They can perform analyses, generate reports, extract data, or carry out any other relevant operations using the stored and mapped data.
10 [0107] Further, the method comprises enabling, by an enable unit [210], a user to
define relationship and dependency between the base table and the one or more mapping tables based a third user input, wherein dependency corresponds to the relationship that dictates how data in one table is connected to data in another table. The present disclosure encompasses the enable unit [210], to enable the user to
15 define the relationships and dependencies between the base table and the associated
mapping tables. This capability is triggered by a third user input, indicating the user's intention to establish these connections. The third user input is an action given by the user to define the relationships and dependencies between the base table and the mapping tables, detailing how data connections are to be established. The data
20 in another table refers to the information stored in the mapping tables, which is to
be linked with the base table according to the defined mappings and configurations.
[0108] The term "relationship" denotes the way data in one table relates to data in
another, encompassing various types of associations such as one-to-one, one-to-
25 many, or many-to-many relationships. Meanwhile, "dependency" refers to the
relationship that governs how data from one table depends on or is influenced by
data in another table. This could include hierarchical dependencies or constraints
such as foreign key relationships. The enable unit [210] is further configured to
enable a user to review and modify the set of pre stored mapped data. This
30 functionality allows users to access the stored dataset previously generated through
the mapping process and make necessary adjustments based on their specific
36

requirements. By providing users with the capability to review and modify the pre-stored mapped data, the system enhances user control and flexibility in managing their datasets. To review and modify pre-stored mapped data, the user accesses the data mapping UI and navigates to the section displaying the base table and its mappings. They view the pre-stored data, select the mapping table to modify, and make necessary changes to configurations like relationships and dependencies. After saving these changes, the system updates and stores the new configurations, which are then reflected in the UI.
[0109] In an implementation of the present disclosure, in the product catalogue, the users can define a relationship where each product in the "Products" table is linked to pricing information from the "Pricing" table and inventory levels from the "Inventory" table. The users may be review and modify these mappings to ensure the data remains up to date, reflecting changes in product details, pricing, and inventory.
[0110] Thereafter, the method terminates at step 314.
[0111] Referring to FIG. 4, an exemplary signalling flow diagram [400] for dynamic data mapping and configuration via a user interface (UI), in accordance with exemplary implementations of the present disclosure is shown. The signalling flow diagram [400] shows a process of how an API (Application Programming Interface) request is handled within a particular system, such as EPC (Enterprise Product Catalogue).
[0112] At step S1, the EPC (Enterprise Product Catalogue) UI sends the user authentication and authorization request to IAM (Identity Access Management) system. IAM is a system that ensures the security of the system by managing user identities and controlling their access to resources. When an API request comes in, the IAM system authenticates (confirms the identity of the user or system making

the request) and authorizes (checks whether the requester has permission to access the requested data or functionality) the request.
[0113] At step S2, The IAM sends the 200: response with user roles to the EPC UI. The HTTP 200 response denotes a success status response code which indicates that the request has succeeded. IAM send the response with defined roles for the user to interact with EPC UI.
[0114] At step S3, the EPC UI sends HTTP request which is sync call to the Elastic Load Balancer (ELB). After the IAM system has validated the request, it goes to the Load Balancer. The Load Balancer's job is to distribute incoming network traffic across multiple servers (in this case, EPC application instances) to ensure no single server becomes overwhelmed with too many requests.
[0115] At step S4, the ELB sends the HTTP request to a controller layer which is the EPC Micro Service (MS). Once the Load Balancer distributes the request, it lands at one of the backend EPC application instances. This is where the request is processed, and the appropriate response is generated.
[0116] At step S5, the EPC MS sends the database (DB) a database query. ES Cluster (Elasticsearch Cluster) is the database used to store data. An Elasticsearch cluster is a group of one or more Elasticsearch nodes instances that are connected together. The power of an Elasticsearch cluster lies in the distribution of tasks, storing data, and in failure tolerance.
[0117] At step S6, then the database sends the query response to the EPC MS.
[0118] At step S7, EPC UI receives a HTTP 200 message which is an acknowledgement response from the EPC MS.

[0119] At step S8, the ELB sends an HTTP 200 acknowledgement response to the EPC UI.
[0120] Referring to FIG. 5, an exemplary ne system architecture [500] for dynamic data mapping and configuration via a user interface (UI), in accordance with exemplary implementations of the present disclosure is shown.
[0121] The system architecture [500] comprises one or more channels such as Enterprise Product Catalogue (EPC) User Interface (UI) [501] and Other Channels [502], firewall [511], load balancer [512], Enterprise Product catalogue (EPC) system [501] comprising EPC instances [503], Operations Administration and Management (OAM) instances [504], Identity Access Management (IAM) instances [505], Elastic search cluster (ES cluster) [510], Fulfilment Management System (FMS) [506], Subscription Engine (SE) [507], Customer Relationship Management (CRM) [508], and a Data Information Framework (DIF) [509].
[0122] In an exemplary aspect of the present disclosure, channels in the context of the invention refer to different user interfaces, such as web applications or external systems, through which REST API requests are made to the EPC system [501]. These channels act as a means of communication between users or external systems and the EPC system [501]. When a REST API request is sent to the EPC system [501], it goes through an authentication and authorization process performed by the IAM (Identity Access Management) instances [505]. The IAM instances [505] verify the identity and permissions of the requester to ensure they have the necessary access rights to interact with the EPC system [501].
[0123] Once the request is validated and authorized by the IAM instances [505], it is passed on to a load balancer [512]. The load balancer's role is to distribute incoming requests across multiple backend EPC (Enterprise Product Catalogue) instances [503]. This ensures that the workload is evenly distributed and helps improve the system's performance and scalability. The backend EPC instances

[503] receive the API request from the load balancer [512]. The EPC instances [503] handle and process the request, performs the necessary operations and generate the appropriate response. This includes retrieving data, applying business logic, and interacting with other components within the EPC system [501]. OAM (Operation and Administration Management) instances [504] serve as a broadcaster in the system. It manages the microservices registry, which contains information about the various microservices within the EPC system [501]. This includes details such as dependencies, communication protocols, and other necessary information for the microservices to effectively communicate with each other. OAM instances [504] ensure that the different microservices can discover and interact with one another seamlessly.
[0124] FMS (Fulfilments management system) [506] acts as a middleware component in the system [500]. It facilitates the integration of the API services provided by the EPC system [501] with other system nodes or external systems. FMS [506] handles the routing, transformation, and communication between different components, allowing for smooth interoperability and data exchange.
[0125] The ES cluster [510] refers to Elasticsearch Cluster which is a database used to store data. An Elasticsearch cluster is a group of one or more Elasticsearch nodes instances that are connected together. The power of an Elasticsearch cluster lies in the distribution of tasks, storing data, and in failure tolerance.to the database used to store data within the system. It is responsible for persisting and retrieving data required by the EPC system [501]. The ES cluster [510] is designed to handle large volumes of data and provide efficient data storage and retrieval capabilities.
[0126] In summary, the channels serve as user interfaces or external systems that send REST API requests to the EPC system. These requests undergo authentication and authorization, are load balanced across backend EPC application instances, and are processed by the EPC instance. OAM Instances [504] manage the microservices

registry for effective communication, FMS [506] acts as a middleware for integration, and the ES cluster [510] serves as the database for data storage.
[0127] Another aspect of the present disclosure may relate to a user equipment (UE) for dynamic data mapping and configuration via a user interface (UI), the system comprises a processor configured to display a UI for selection of a base table, wherein the base table is a primary table to which one or more mapping tables will be mapped. The processor is further configured to add the one or more mapping tables to the selected base table based on a first user input upon selection of the base table, wherein each of the one or more mapping tables is associated with the selected base table. The processor is further configured to define, based on a second user input, a set of mapping properties for each of the one or more mapping tables. The processor is further configured to store the mapping properties to configure the base table. The processor is further configured to display the configured base table, wherein the configured base table is updated to a set of pre stored mapped data, which comprises data previously configured and stored based on the defined set of mappings between the base table and the one or more mapping tables according to a configuration of the UI.
[0128] As is evident from the above, the present disclosure provides a technically advanced solution for dynamic data mapping and configuration via a user interface which presents a wizard. The present solution introduces a novel table mapping and data entry wizard, addressing the shortcomings of conventional product catalogue. Through a user-friendly interface, users, can seamlessly navigate and manage data across numerous tables within the EPC. The system introduces dynamic table mapping capabilities, allowing users to configure dependencies and relationships between tables with ease. Furthermore, the invention updates data entry processes by providing a wizard-style interface, guiding users systematically through data entry across multiple tables, thereby reducing errors and enhancing efficiency. With increased flexibility in mapping, users gain greater control over their EPC product catalogue system promoting a more updated and natural workflow.

[0129] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0130] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

I/We Claim:
1. A method [300] for dynamic data mapping and configuration via a user interface (UI),
the method comprising:
- displaying, by a display unit [202], a UI for selection of a base table, wherein the base table is a primary table to which one or more mapping tables will be mapped;
- upon selection of the base table, adding, by an addition unit [204], the one or more mapping tables to the selected base table based on a first user input, wherein each of the one or more mapping tables is associated with the selected base table;
- defining, by a definition unit [206], based on a second user input, a set of configurations for each of the one or more mapping tables;
- storing, by a storage unit [208], the set of configurations to configure the base table; and
- displaying, by the display unit [202], the configured base table, wherein the configured base table is updated to a set of pre stored mapped data, which comprises data previously configured and stored based on the defined set of mappings between the base table and the one or more mapping tables according to a configuration of the UI.

2. The method [300] as claimed in claim 1, wherein the UI is implemented using an Angular framework.
3. The method [300] as claimed in claim 1, further comprises enabling, by an enable unit [210], a user to define relationship and dependency between the base table and the one or more mapping tables based a third user input, wherein dependency corresponds to the relationship that dictates how data in one table is connected to data in another table.
4. The method [300] as claimed in claim 1, wherein each of the one or more mapping tables comprises a set of data to be mapped.
5. The method [300] as claimed in claim 3, further comprises enabling, by the enable unit [210], a user to review and modify the set of pre stored mapped data.

6. The method [300] as claimed in claim 1, wherein the set of configurations comprises at least a stepper name, a search table, and one or more mapping properties for filtering entries from the search table.
7. A system [200] for dynamic data mapping and configuration via a user interface (UI), the system comprises:

- a display unit [202] configured to display a UI for selection of a base table, wherein the base table is a primary table to which one or more mapping tables will be mapped;
- an addition unit [204] connected to at least the display unit [202], wherein the addition unit [204] is configured to add the one or more mapping tables to the selected base table based on a first user input upon selection of the base table, wherein each of the one or more mapping tables is associated with the selected base table;
- a definition unit [206] connected to at least the addition unit [204], wherein the definition unit [206] configured to define, based on a second user input, a set of configurations for each of the one or more mapping tables;
- a storage unit [208] connected to at least the definition unit [206], wherein the storage unit [208] configured to store the set of configurations to configure the base table; and
- the display unit [202] connected to at least the storage unit [208], wherein the display unit [202] configured to display the configured base table, wherein the configured base table is updated to a set of pre stored mapped data, which comprises data previously configured and stored based on the defined set of mappings between the base table and the one or more mapping tables according to a configuration of the UI.

8. The system [200] as claimed in claim 7, wherein the UI is implemented using an Angular framework.
9. The system [200] as claimed in claim 7, wherein the system further comprises an enable unit [210] configured to enable a user to define relationship and dependency between the base table and the one or more mapping tables based on a third user input, wherein dependency corresponds to the relationship that dictates how data in one table is connected to data in another table.

10. The system [200] as claimed in claim 7, wherein each of the one or more mapping tables comprises a set of data to be mapped.
11. The system [200] as claimed in claim 9, wherein the enable unit [210] is further configured to enable a user to review and modify the set of pre stored mapped data.
12. The system [200] as claimed in claim 7, wherein the set of configurations comprises at least a stepper name, a search table, and one or more mapping properties for filtering entries from the search table.
13. A user equipment (UE) for dynamic data mapping and configuration via a user interface (UI) comprising:
a processor configured to:
- display a UI for selection of a base table, wherein the base table is a primary table to which one or more mapping tables will be mapped;
- add the one or more mapping tables to the selected base table based on a first user input upon selection of the base table, wherein each of the one or more mapping tables is associated with the selected base table;
- define, based on a second user input, a set of configurations for each of the one or more mapping tables;
- store the set of configurations to configure the base table; and
- display the configured base table, wherein the configured base table is updated to a set of pre stored mapped data, which comprises data previously configured and stored based on the defined set of mappings between the base table and the one or more mapping tables according to a configuration of the UI.