Robot for implementing process automation in enterprise resource planning systems
Patent Information
- Application Number
- IN201941007859
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2019-02-28
- Publication Date
- 2026-10-22
- Estimated Expiration
- 2039-02-28
AI Technical Summary
Current robotic process automation (RPA) technologies for Enterprise Resource Planning (ERP) systems face challenges such as complex automation processes, high infrastructure costs, scalability issues, security concerns, and the need for professional expertise to create and maintain bots, along with latency and compliance issues, which hinder efficient process automation and return on investment.
A robot comprising a workbench module, code generator module, core library template module, bot execution module, orchestrator module, logging module, and audits and reports module, which facilitates easy creation, execution, and management of bots without professional help, supporting various protocols and providing detailed logs and reports, thus enabling efficient process automation within ERP systems.
Enables easy creation and management of bots within ERP systems, reducing the need for professional experts, lowering infrastructure costs, and improving scalability and security, while providing detailed logs and reports for enhanced monitoring and compliance, thus enhancing the efficiency and effectiveness of process automation.
Abstract
Description
FORM 2THE PATENTS ACT 1970 (39 OF 1970)&The Patents Rule, 2003COMPLETE SPECIFICATION(See Section 10 and Rule 13)TITLE OF THE INVENTION: ROBOT FOR IMPLEMENTING PROCESSAUTOMATION IN ENTERPRISE RESOURCE PLANNING SYSTEMSApplicant:Name: BEEZ INNOVATION LABS PRIVATE LIMITEDAddress: PLOT NO.2, SARASWATHY NAGAR EXTENSION, NEDUNGUNDRAM,CHENNAI - 600048, TAMIL NADU, INDIANationality: IndianPREAMBLE TO THE DESCRIPTIONThe following specification particularly describes the invention and the manner in which it is to be performed.TITLE OF THE INVENTION: ROBOT FOR IMPLEMENTING PROCESS AUTOMATION IN ENTERPRISE RESOURCE PLANNING SYSTEMSFIELD OF THE INVENTIONThe present disclosure is generally related to a robot for implementing process automation in enterprise resource planning systems.BACKGROUND OF THE INVENTIONToday, there is a growing focus on developing a front end digital business strategy in almost every major industry worldwide to automate operations, lower costs, and improve customer service. As emerging technologies have begun threatening long-established companies in verticals such as retail, insurance, banking, etc., the push for automation is now more critical than ever when it comes to optimizing front-end business processes to meet growing consumer expectations.Using automation at the right time, right place, and in the right format is absolutely essential for the success of enterprises. This creates complexity for all enterprises to assess the most relevant method of automation and the business scenarios and areas that need to be automated, as well as how much time, effort, and money to be invested.Most of the enterprises across the globe use Enterprise Resource Planning (ERP) systems such as SAP as their business automation tool, and most of the key business processes which are to be automated lies within that ERP system.Currently, graphical user interface (GUI) based robotic process automation (RPA) technology has emerged as a leading front-end solution to lead the enterprise digital transformation charge. However, the enterprises with front-end RPA for ERP system face the following challenges: complex automation processes demand more systems (desktop computers, laptop computers, etc.) which make scalability challenging; expanding the infrastructure increases the costs in parallel; rendering time and performance is a trade-off when it comes to front-end automation; the robots run largely unattended, this implies that enterprise RPA technologies must have strong built-in support for complex processes that include exception handling, along with a solution to recover from failures automatically; the number of scripts (especially over a complex process) makes it difficult to maintain and identify the right fix when the automation fails; reusability is a challenge; scripts differ based on inputs for same application; access over executing a business process cannot just be a dialog user with necessary authorization, it also needs to be bound by business process and by a business owner; and robots need to have an access grouping by business process and business owner, which is always a trade off with front-end automation.Further, the process of creating a bot to perform a specific functionality automatically is not as easy task in the existing ERP systems. All the users cannot create the bots on their own, it requires professional experts for the creation of the bots.Further, enabling GUI Scripting in ERP systems has a SOX (Sarbanes-Oxley) compliance issue. RPA on ERP system requires front-end access, which needs a dialog user whereas maintaining dialog users for automation raises security concerns and is an operational overhead. RPA has a latency issue when automated via GUI which is Front-end Way, this leads to delays in processing time and does not make huge differences on the effort for a Robot over a Human, hence challenging in meeting the Return on Investment. ERP system processes are system heavy, which means they require huge investment on VMs (Virtual Machines) to be created to run and control the process using RPA, this leads to Huge Infrastructure cost. When huge numbers of RPA automations run on an ERP system, it consumes dialog work processes of the ERP system server leading to system availability and performance. Concurrent executions are not possible for a same User ID in ERP system which will lead to multiple dialog user creation.There is, therefore, a need in the art for a robot for implementing process automation in enterprise resource planning system that overcomes the aforementioned drawbacks.SUMMARY OF THE INVENTIONA robot for implementing process automation in enterprise resource planning systems is disclosed. The robot comprises a workbench module, a code generator module, a core library template module, a core library helper module, a bot execution module, an orchestrator module, a logging module, and an audits and reports module.The workbench module has reporting and the bot creation wizard features, acts as a singleview dashboard, and facilitates: the creation / modification / deletion of one or more bots, maintaining and execution of the one or more bots, and displaying a holistic view of active / inactive bots in the ERP system repository.The code generator module is an object of a high-level program language used in the enterprise resource planning system, with methods to add declaration and operational syntaxes, and facilitates the framing of program lines dynamically to the one or more hots based on the inputs provided by a user during the bot creation.The core library template module is a pre-defined template with one or more attributes and one or more functions that are inherited by the one or more bots, and facilitates the accomplishing of homogeneity among the one or more bots.The core library helper module is a set of reusable: routines, protocols, and tools, and facilitates the user to create the one or more bots with minimum effort and without any professional help.The bot execution module acts as an interface for the execution of the one or more bots in the ERP system for one or more requests received from external services, said bot execution module (15) being the place where the one or more requests are received.The orchestrator module receives the one or more requests from the bot execution module for initiation, said orchestrator module (16) acting as an execution engine for the one or more bots and returning one or more results to the execution module (15), with each bot execution having an execution id and a log id that logs the execution steps, with said orchestrator module comprising a data persistent unit that facilitates the receiving of one or more inputs from the user and delivers the output to the user after the execution of a bot; and an execution unit which triggers the execution of the functions which are defined in the bot.The logging module facilitates the logging of all the procedural and functional activities carried out by the one or more bots during execution and stores them in a repository (18).And, an audits and reports module facilitates the providing of detailed information of the bot executions over a period of time, said detailed information being stored in a database (20).The bots are created easily within a short period of time, without engaging a professional expert, and are capable of supporting one or more protocols such as REST, RFC, OData and / or Web-RFC, etc.BRIEF DESCRIPTION OF THE DRAWINGSFigure 1 illustrates an embodiment of a robot for implementing process automation in enterprise resource planning systems, in accordance with the present disclosure.Figure 2 illustrates an embodiment of a workflow of the robot for implementing process automation in enterprise resource planning systems, in accordance with the present disclosure.DESCRIPTION OF THE INVENTIONThroughout this specification, the use of the word "comprise" and “include”, and variations such as "comprises", "comprising", “includes”, and “including” may imply the inclusion of an element or elements not specifically recited.A robot (10) for implementing process automation in enterprise resource planning systems (ERP) is disclosed. As illustrated in Figure 1, the robot comprises a workbench module (11), said workbench module (11) having reporting and the bot creation wizard features, acting as a single-view dashboard, and facilitating: the creation / modification / deletion of one or more bots, maintaining and execution of the one or more bots, and displaying a holistic view of active / inactive bots in the ERP system repository; a code generator module (12), said code generator module being an object of a high-level program language used in an ERP system, with methods to add declaration and operational syntaxes, and facilitating the framing of program lines dynamically to the one or more bots based on the inputs provided by a user during bot creation; a core library template module (13), which is a pre-defined template with one or more attributes and one or more functions that are inherited by the one or more bots, said core library template module (13) facilitating the accomplishing of homogeneity among the one or more bots; a core library helper module (14), which is a set of reusable: routines, protocols, and tools, said core library helper module (14) facilitating the user to create the one or more bots with minimum effort and without any professional help; a bot execution module (15) that acts as an interface for the execution of the one or more bots in the ERP system for one or more requests received from external services, said bot execution module (15) being the place where the one or more requests are received, which are subsequently passed to an orchestrator module (16) for initiation, said orchestrator module (16) acting as an execution engine for the one or more bots and returning one or more results to the execution module (15), with each bot execution having an execution id and a log id that logs the execution steps; a logging module (17) that facilitates the logging of all the procedural and functional activities carried out by the one or more hots during execution and stores them in a repository (18); and an audits and reports module (19), that facilitates the providing of detailed information of the hot executions over a period of time, said detailed information being stored in a database (20).In an embodiment of the present disclosure, the robot (10) creates the one or more bots automatically using a wizard. In the wizard, the one or more bots are created by incorporating a report program or the like. The one or more bots can also be reused when a business has an already created report program or the like. The robot helps in easy conversion of reports of the ERP system into automation bots. The types of bots that can be created using the wizard are as follows:1. Business Configuration Bot - Which helps in adding business configuration settings in ERP system;2. Business Object Listener Bot - Which monitors business operations and pushes business data to any data analytical platform to evaluate and analyze data inconsistencies;3. Report Program Bot - Which incorporates existing automation reports and converts it to a bot;4. BDC Bot - Bots are created using business process recordings (existing / new); and5. Empty Bot - Bots to be created from the scratch.The user can select any one of the above-mentioned bot type in the wizard. Based on the selection, the user provides inputs and other parameters before clicking on a Finish button. The robot (10) creates the bot automatically based on the user preference without witting a single line of code. Hence, using the robot (10), a bot is created easily within a short period of time, without engaging a professional expert. The one or more Bots created via the wizard using the robot (10) are capable of supporting various protocols such as REST, RFC, OData and / or Web-RFC, etc.In an embodiment of the present disclosure, the orchestrator module (16) comprises a data persistent unit that facilitates the receiving of one or more inputs from the user and delivers the output to the user after the execution of a bot, and an execution unit which triggers the execution of the functions which are defined in the bot.In an embodiment of the present disclosure, the robot (10) may work on a networked environment. The network may be the Internet, a virtual private network, a local area network, a wide area network, a broadband digital network or any other appropriate structure for enabling communication between two or more nodes or locations. The network may include a shared, public, or private data network. Further, the network may encompass a wide area or local area, and may include one or more wired and / or wireless connections.In an embodiment of the present disclosure, said workbench module (11), said code generator module (12), said core library template module (13), said core library helper module (14), said bot execution module (15), said orchestrator module (16), said logging module (17), said audits and reports module (19), said repository (18), and said database (21) may reside on a single server or may be spread across a plurality of servers, in which case they are interoperable through their respective server.In yet another embodiment of the present disclosure, the workbench module (101) is a web application accessible from devices such as desktop computers, laptop computers, handheld devices, smart devices, and wearable devices.In yet another embodiment of the present disclosure, the workbench module (11) is an application installable on devices such as desktop computers, laptop computers, handheld devices, smart devices, and wearable devices.The method of working of the robot is illustrated in Figure 2.The Robot (10) is an automation agent which governs the creation and management of the one or more bots within a respective ERP system (001). A Bot (000) requires defined inputs (100) as follows whenever it is selected for execution within the orchestrator module (102):a. Bot Input (100. b)- Inputs to be passed to the selected bot;b. Execution ID (100. c) - Unique Identifier to recognize respective execution requests; andc. Bot Protocol (100. d)- Type of Protocol used.Only the bot input is provided by the user, and the Execution ID and the bot Protocol are taken care of by the robot (10).The Bot Inputs (100) for the selected hot are passed to the orchestrator module (17). The orchestrator module (17) is supported by the core library modules (103), i.e. core library template module and core library helper module, which aid in managing the process of logging, error handling, and message handling, apart from providing reusable interfaces to fasten the development of the bot.A log object (201) is created for the Execution ID (100.c) to log all the execution steps except the steps involved in actual business logic. This object logs the activities related to license validation, authorization validation (at user level and bot level) and execution life cycle events.Then, Existence of the bot in Bot Repository (104) is carried out. Next, the data persistent unit (202) holds the inputs needed to execute the business logic. The Bot Input (lOO.b) is passed to the data persistent unit (202). The Execution unit (203) is then initiated by passing both the Execution ID (100.c) and the Bot Protocol (100.d) as inputs. The execution unit takes care of updating the execution details in the Bot Repository (104).The Execution unit creates an Execution Log object (203.a) for the Execution ID (lOO.b), as its attribute, to log the steps of actual business logic execution. License validation and authorization check are done.A Bot Trigger Method (205) of the bot is then triggered. The method (205) takes inputs from the data persistent unit (202) and the execution unit (203). This is the starting point of actual execution of the business logic in the bot. All the steps of business logic execution are captured by Execution Log Object (203.a) and stored in a log (105).Upon completion of the business logic execution, Execution Messages (204) are captured. The Execution unit (203) updates execution status in the Bot Repository (104).The log object (201) captures each and every step of all the above processes and saves complete logs in the log (105).The working of the robot (10) as disclosed in the present disclosure will now be further explained with the help of the below example.A scenario of Swift key creation in an ERP system: Swift key code is a standard format of Bank Identifier Codes (BIC) and it is unique identification code for a bank.Creation of a Bot:Login to the provided robot (10) workbench transaction, where a user can create a new bot or use the already created bots which he / she has been provided access.Initial step in the process is recording the swift key creation process, which is completed by logging into the ERP system, inputting the required parameters, and saving the recording.In the robot (10) creation wizard, select the bot type as BDC bot which is assigned with a process recording script generated in the above step.Bot creation through the wizard process once the required information is provided in the creation wizard with the required fields like Country key, Swift key code, and bank name. The same fields are as inputs during bot execution. The robot (10) generates business logic automatically for execution.Execution of a Bot:In the Robot (10), bots can be triggered on demand or can be scheduled to a required time and frequency.Select the bot created for Swift key creation in from a Bots list in dashboard and click on trigger. Provide the required inputs on the pop-up like country code, swift key code, bank name etc. as prompted.Once continued, the request is passed and executed on the robot (10) as mentioned in the Figure. 2.After execution, the robot (10) responds back to the user saying Swift key has been created in the ERP system.It will be apparent to a person skilled in the art that the above description is for illustrative purposes only and should not be considered as limiting. Various modifications, additions, alterations and improvements without deviating from the spirit and the scope of the disclosure may be made by a person skilled in the art. Such modifications, additions, alterations and improvements should be construed as being within the scope of this disclosure.List of Reference Numerals10 - A Robot for Implementing Process Automation in Enterprise Resource PlanningSystems11- Workbench Module12 - Code Generator Module13 - Core Library Template Module14 - Core Library Helper Module15 - Bot Execution Module16 - Orchestrator Module17 - Logging Module18 - Repository19 - Audits and Reports Module20 - Database000 - Bot001 -ERP system100 - Defined Inputs100. b - Bot Inputs100. c - Execution ID100. d - Bot Protocol102 - Execution within Orchestrator Module104 -Bot Repository105 - Log201 - Log Object202 - Passing Bot Input to Data Persistence Unit203 - Execution Unit203. a - Execution Log Object204 - Execution Messages205 - Bot Trigger MethodViswanath VenkateshIN / PA-2121Agent for the ApplicantCLAIMS:
Claims
We Claim1. A robot (10) for implementing process automation in enterprise resource planning systems, said robot comprising:a workbench module (11), said workbench module (11) having reporting and the bot creation wizard features, acting as a single-view dashboard, and facilitating: the creation / modification / deletion of one or more bots that are capable of supporting one or more protocols, maintaining and execution of the one or more bots, and displaying a holistic view of active / inactive bots in the ERP system repository;a code generator module (12), said code generator module (12) being an object of a high-level program language used in an ERP system, with methods to add declaration and operational syntaxes, and facilitating the framing of program lines dynamically to the one or more bots based on the inputs provided by a user during bot creation;a core library template module (13), which is a pre-defined template with one or more attributes and one or more functions that are inherited by the one or more bots, said core library template module (13) facilitating the accomplishing of homogeneity among the one or more bots;a core library helper module (14), which is a set of reusable: routines, protocols, and tools, said core library helper module (14) facilitating the user to create the one or more bots with minimum effort and without any professional help;a bot execution module (15) that acts as an interface for the execution of the one or more bots in the ERP system for one or more requests received from external services, said bot execution module (15) being the place where the one or more requests are received;an orchestrator module (16) that receives the one or more requests from the bot execution module (15) for initiation, said orchestrator module (16) acting as an execution engine for the one or more bots and returning one or more results to the execution module (15), with each bot execution having an execution id and a log id that logs the execution steps, and said orchestrator module (16) comprising: a data persistent unit that facilitates the receiving of one or more inputs from the user and delivers the output to the user after the execution of a bot; and an execution unit which triggers the execution of the functions which are defined in the bot; a logging module (17) that facilitates the logging of all the procedural and functional activities carried out by the one or more hots during execution and stores them in a repository (18); andan audits and reports module (19), that facilitates the providing of detailed information of the hot executions over a period of time, said detailed information being stored in a database (20), with said workbench module (11), said code generator module (12), said core library template module (13), said core library helper module (14), said bot execution module (15), said orchestrator module (16), said logging module (17), said audits and reports module (19), the repository (18), and the database (21) residing on a single server or across a plurality of servers with interoperability through their respective server.
2. A robot (10) for implementing process automation in an enterprise resource planning systems as claimed in claim 1, wherein the one or more protocols are REST, RFC, OData, and Web-RFC.
3. A robot (10) for implementing process automation in an enterprise resource planning systems as claimed in claim 1, wherein the workbench module (101) is a web application accessible from desktop computers, laptop computers, handheld devices, smart devices, and wearable devices.
4. A robot (10) for implementing process automation in an enterprise resource planning systems as claimed in claim 1, wherein the workbench module (11) is an application installable on desktop computers, laptop computers, handheld devices, smart devices, and wearable devices.Date: February 28, 2019Viswanath VenkateshIN / PA-2121Agent for the ApplicantABSTRACTTITLE: ROBOT FOR IMPLEMENTING PROCESS AUTOMATION IN ENTERPRISE RESOURCE PLANNING SYSTEMSA robot (10) for implementing process automation in enterprise resource planning systems is disclosed. The robot comprises a workbench module (11) that facilitates the creation / modification / deletion of one or more bots; a code generator module (12) that facilitates the framing of program lines dynamically; a core library template module (13) that facilitates the accomplishing of homogeneity among the one or more bots; a core library helper module (14) that facilitates a user to create the one or more bots with minimum effort and without any professional help; a bot execution module (15) that received one or more bot execution requests, and subsequently passes them to an orchestrator module (16) to initiate the one or more requests and return one or more results to the execution module (15); a logging module (17) that facilitates the logging of all the activities carried out by a bot during execution, which are stored in a repository (18); and an audits and reports module (19) that facilitates the providing of information of the bot executions over a period of time, said information being stored in a database (20). The bots created in the robot (10) are capable of supporting one or more protocols.The figure to be included is Figure 1Viswanath VenkateshIN / PA-2121Agent for the Applicant
