Description:DESCRIPTION
Technical Field
[001] This disclosure relates generally to in-memory database management systems, and more particularly to method and system for automated conversion of virtual data model views.
Background
[002] SAP HANA (High-performance ANalytic Application) is an in-memory, column-oriented, relational database management system. SAP HANA provides calculation views for data modeling and analytics. An upgrade to SAP HANA, SAP S/4HANA is an enterprise resource planning (ERP) software suite with a streamlined, next-generation architecture. With SAP S/4HANA, a feature for Core Data Services (CDS) views, a new architecture for comprehensive data modelling, was introduced.
[003] As enterprises transition from SAP HANA to SAP S/4HANA, a key consideration is how to balance customization with system stability, agility, and upgradability. A clean core strategy has emerged as a best practice, emphasizing the importance of keeping the SAP S/4HANA core clean from excessive customizations. The clean core strategy may ensure that businesses can innovate rapidly without compromising system integrity, maintainability, and future readiness.
[004] Currently, the enterprises are doing a lot of custom and manual development for the transition without focusing on the clean core strategy. Consequently, the enterprises are faced with several challenges, such as increased complexity, higher maintenance costs, slower upgrades, reduced flexibility, and technical debt.
[005] The techniques in the present state of art fail to facilitate a smoother and efficient transition from the calculation views to CDS views. There is, therefore, a need for method and system for automated migration from the calculation views to the CDS views.

SUMMARY
[006] In one embodiment, a method for automated conversion of virtual data model views is disclosed. In one example, the method may include receiving, via a user interface, a calculation view file of a virtual data model in an in-memory database management system. It should be noted that the calculation view file may include a graphical representation of the virtual data model. The method may further include generating, via a Large Language Model (LLM), a first Core Data Services (CDS) view file corresponding to the calculation view file based on a direct CDS view generation prompt. It should be noted that a CDS view file may include a code-based definition of the virtual data model. It should be noted that the direct CDS view generation prompt may include the calculation view file and a set of calculation view-CDS view conversion instructions. The method may further include generating, via the LLM, a second CDS view file corresponding to the calculation view file based on an intermediate representation generation prompt and a syntax conversion prompt. It should be noted that the intermediate representation generation prompt may include the calculation view file and a set of calculation view-intermediate representation conversion instructions. It should be noted that the syntax conversion prompt may include an intermediate representation of the calculation view file and a set of CDS syntax instructions. The method may further include comparing, via the LLM, the first CDS view file and the second CDS view file based on a set of accuracy and performance parameters. The method may further include generating, via the LLM, a final CDS view file corresponding to the calculation view file based on the comparing and a final CDS view generation prompt. It should be noted that the final CDS view generation prompt may include the first CDS view file, the second CDS view file, results of the comparing, and a set of final CDS view generation instructions.
[007] In another embodiment, a system for automated conversion of virtual data model views is disclosed. In one example, the system may include a processor and a computer-readable medium communicatively coupled to the processor. The computer-readable medium may store processor-executable instructions, which, on execution, may cause the processor to receive, via a user interface, a calculation view file of a virtual data model in an in-memory database management system. It should be noted that the calculation view file may include a graphical representation of the virtual data model. The processor-executable instructions, on execution, may further cause the processor to generate, via an LLM, a first Core Data Services (CDS) view file corresponding to the calculation view file based on a direct CDS view generation prompt. It should be noted that a CDS view file may include a code-based definition of the virtual data model. It should be noted that the direct CDS view generation prompt may include the calculation view file and a set of calculation view-CDS view conversion instructions. The processor-executable instructions, on execution, may further cause the processor to generate, via the LLM, a second CDS view file corresponding to the calculation view file based on an intermediate representation generation prompt and a syntax conversion prompt. It should be noted that the intermediate representation generation prompt may include the calculation view file and a set of calculation view-intermediate representation conversion instructions. It should be noted that the syntax conversion prompt may include an intermediate representation of the calculation view file and a set of CDS syntax instructions. The processor-executable instructions, on execution, may further cause the processor to compare, via the LLM, the first CDS view file and the second CDS view file based on a set of accuracy and performance parameters. The processor-executable instructions, on execution, may further cause the processor to generate, via the LLM, a final CDS view file corresponding to the calculation view file based on the comparing and a final CDS view generation prompt. It should be noted that the final CDS view generation prompt may include the first CDS view file, the second CDS view file, results of the comparing, and a set of final CDS view generation instructions.
[008] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
BRIEF DESCRIPTION OF THE DRAWINGS
[009] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles.
[010] FIG. 1 is a block diagram of an exemplary system for automated conversion of virtual data model views, in accordance with some embodiments of the present disclosure.
[011] FIG. 2 illustrates a functional block diagram of a system for automated conversion of virtual data model views, in accordance with some embodiments of the present disclosure.
[012] FIG. 3A and FIG. 3B illustrate a flow diagram of an exemplary process for automated conversion of virtual data model views, in accordance with some embodiments of the present disclosure.
[013] FIG. 4 illustrates a flow diagram of an exemplary process for validating an intermediate representation of a calculation view file, in accordance with some embodiments of the present disclosure.
[014] FIG. 5 illustrates a flow diagram of a detailed exemplary control logic for automated conversion of virtual data model views, in accordance with some embodiments of the present disclosure.
[015] FIG. 6 is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
DETAILED DESCRIPTION
[016] Exemplary embodiments are described with reference to the accompanying drawings. Wherever convenient, the same reference numbers are used throughout the drawings to refer to the same or like parts. While examples and features of disclosed principles are described herein, modifications, adaptations, and other implementations are possible without departing from the spirit and scope of the disclosed embodiments. It is intended that the following detailed description be considered as exemplary only, with the true scope and spirit being indicated by the following claims.
[017] Referring now to FIG. 1, an exemplary system 100 for automated conversion of virtual data model views is illustrated, in accordance with some embodiments of the present disclosure. The system 100 may include a computing device 102. The computing device 102 may be, for example, but may not be limited to, server, desktop, laptop, notebook, netbook, tablet, smartphone, mobile phone, or any other computing device, in accordance with some embodiments of the present disclosure. The computing device 102 may automate the conversion of a calculation view file of a virtual data model in an in-memory database management system (such as SAP HANA) to a corresponding Code Data Services (CDS) view file (compatible with SAP S/4HANA) using a Large Language Model (LLM).
[018] As will be described in greater detail in conjunction with FIGS. 2 – 6, the computing device 102 may receive, via a user interface, a calculation view file of a virtual data model in an in-memory database management system. It should be noted that the calculation view file may include a graphical representation of the virtual data model. The computing device 102 may further generate, via an LLM, a first CDS view file corresponding to the calculation view file based on a direct CDS view generation prompt. It should be noted that a CDS view file may include a code-based definition of the virtual data model. It should be noted that the direct CDS view generation prompt may include the calculation view file and a set of calculation view-CDS view conversion instructions. The computing device 102 may further generate, via the LLM, a second CDS view file corresponding to the calculation view file based on an intermediate representation generation prompt and a syntax conversion prompt. The intermediate representation generation prompt may include the calculation view file and a set of calculation view-intermediate representation conversion instructions. The syntax conversion prompt may include an intermediate representation of the calculation view file and a set of CDS syntax instructions. The computing device 102 may further compare, via the LLM, the first CDS view file and the second CDS view file based on a set of accuracy and performance parameters. The computing device 102 may further generate, via the LLM, a final CDS view file corresponding to the calculation view file based on the comparing and a final CDS view generation prompt. It should be noted that the final CDS view generation prompt may include the first CDS view file, the second CDS view file, results of the comparing, and a set of final CDS view generation instructions.
[019] In some embodiments, the computing device 102 may include one or more processors 104 and a memory 106. Further, the memory 106 may store instructions that, when executed by the one or more processors 104, may cause the one or more processors 104 to automate conversion of virtual data model views, in accordance with aspects of the present disclosure. The memory 106 may also store various data (for example, a calculation view file, a first CDS view file, a second CDS view file, an intermediate representation, a final CDS view file, a direct CDS view generation prompt, intermediate representation generation prompt, and the like) that may be captured, processed, and/or required by the system 100.
[020] The system 100 may further include a display 108. The system 100 may interact with a user interface 110 accessible via the display 108. The system 100 may also include one or more external devices 112. In some embodiments, the computing device 102 may interact with the one or more external devices 112 over a communication network 114 for sending or receiving various data. The communication network 114 may include, for example, but may not be limited to, a wireless fidelity (Wi-Fi) network, a light fidelity (Li-Fi) network, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a satellite network, the internet, a fiber optic network, a coaxial cable network, an infrared (IR) network, a radio frequency (RF) network, and a combination thereof. The one or more external devices 112 may include, but may not be limited to, a remote server, a laptop, a netbook, a notebook, a smartphone, a mobile phone, a tablet, or any other computing device.
[021] Referring now to FIG. 2, a functional block diagram of a system 200 for automated conversion of virtual data model views is illustrated, in accordance with some embodiments of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1. The system 200 may be analogous to the system 100. The system 200 may implement the computing device 102. The system 200 may include, within the memory 106, a receiving module 202, a preprocessing module 204, a generating module 206, a validating module 208, a comparing module 210, and an LLM module 212. The LLM module 212 may include an LLM 214.
[022] Initially, the receiving module 202 may receive, via a user interface, a calculation view file 216 of a virtual data model in an in-memory database management system. In an embodiment, the in-memory database management system may be SAP High-Performance Analytic Appliance (HANA). It should be noted that the calculation view file 216 may include a graphical representation of the virtual data model. Further, the receiving module 202 may send the calculation view file 216 to the preprocessing module 204.
[023] Further, the preprocessing module 204 may preprocess the calculation view file 216 using a set of preprocessing techniques (such as parsing techniques or text extraction/cleaning techniques). In particular, the preprocessing module 204 may extract metadata and structure information (e.g., data objects, or the like) from the calculation view file 216. Additionally, the preprocessing module 204 may parse the calculation view file 216 to identify a set of key components of the virtual data model. By way of an example, the set of key components may include, but may not be limited to, joins, aggregations, filters, unions, projections, or the like. The set of components (i.e., joins, filters, or aggregations) may be nodes used to graphically connect the different data objects in the calculation view file. Further, the preprocessing module 204 may send the calculation view file 216 along with the preprocessed data of the calculation view file 216 (i.e., the set of key components, the metadata, and the structure information), to the generating module 206.
[024] Further, the generating module 206 may generate, via the LLM 214, a first CDS view file (i.e., an ‘as-is’ (or directly generated) CDS view file) corresponding to the calculation view file 216 based on a direct CDS view generation prompt. By way of an example, the LLM 214 may be, but may not be limited to, Generative Pre-trained Transformer (GPT) (e.g., GPT-3, GPT-4, GPT-4o, or the like), Large Language Model Meta Artificial Intelligence (LLaMA), Gemini, Claude, or the like. It should be noted that a CDS view file may include a code-based definition of the virtual data model. The direct CDS view generation prompt may include the calculation view file 216 and a set of calculation view-CDS view conversion instructions.
[025] To generate the first CDS view file, the generating module 206 may create the direct CDS view generation prompt based on the calculation view file 216. Further, the generating module 206 may provide the direct CDS view generation prompt to the LLM 214 within the LLM module 212. Further, the LLM module 212 may generate, via the LLM 214, the first CDS view file based on the direct CDS view generation prompt.
[026] Additionally, the generating module 206 may generate, via the LLM, a second CDS view file corresponding to the calculation view file 216 based on an intermediate representation generation prompt and a syntax conversion prompt. The intermediate representation generation prompt may include the calculation view file 216 and a set of calculation view-intermediate representation conversion instructions. The syntax conversion prompt may include an intermediate representation of the calculation view and a set of CDS syntax instructions. In some embodiments, the first CDS view file and the second CDS view file may be generated in parallel.
[027] To generate the second CDS view file, the generating module 206 may first create the intermediate representation generation prompt based on the calculation view file 216. Further, the generating module 206 may provide the intermediate representation generation prompt to the LLM 214 within the LLM module 212. Further, the generating module 206 may generate, via the LLM 214, the intermediate representation of the calculation view file 216 based on the intermediate representation generation prompt.
[028] Upon generating the intermediate representation, the validating module 208 may validate, via the LLM 214, the intermediate representation based on predefined structure criteria. Upon unsuccessful validation, the generating module 206 may identify, via the LLM 214, one or more missing attributes in the intermediate representation. Further, the generating module 206 may dynamically create an intermediate representation modification prompt based on the identified one or more missing attributes. The intermediate representation modification prompt may include the intermediate representation, the identified one or more missing attributes, and a set of intermediate representation modification instructions. Further, the generating module 206 may provide the intermediate representation modification prompt to the LLM 214 within the LLM module 212. Further, the generating module 206 may generate, via the LLM 214, a modified intermediate representation based on the intermediate representation modification prompt.
[029] Additionally, to create the second CDS view file, the generating module 206 may create the syntax conversion prompt based on the intermediate representation of the calculation view file 216. Further, the generating module 206 may provide the syntax conversion prompt to the LLM 214 within the LLM module 212. Further, the LLM may convert the syntax (e.g., Extensible Markup Language (XML)) into a syntax (e.g., Structured Query Language (SQL)) corresponding to the intermediate representation based on the syntax conversion prompt to obtain the second CDS view file.
[030] Once the first CDS view file and the second CDS view file are generated, the comparing module 210 may compare, via the LLM 214, the first CDS view file and the second CDS view file based on a set of accuracy and performance parameters. The set of accuracy and performance parameters may include at least one predefined accuracy parameter. The at least one predefined accuracy parameter may be based on an accuracy of the virtual data model represented in the generated CDS view file (i.e., the first CDS view file and the second CDS view file) relative to the virtual data model represented in the calculation view file 216. Additionally, the set of accuracy and performance parameters may include at least one predefined performance parameter. The at least one predefined performance parameter may be indicative of a performance of the generated CDS view file in a corresponding database management system (such as SAP S/4HANA).
[031] Further, the generating module 206 may generate, via the LLM 214, a final CDS view file 218 corresponding to the calculation view file 216 based on the comparing and a final CDS view generation prompt. The final CDS view generation prompt may include the first CDS view file, the second CDS view file, results of the comparing, and a set of final CDS view generation instructions. To generate the final CDS view file 218, the generating module 206 may create the final CDS view generation prompt based on the first CDS view file, the second CDS view file, and the results of the comparing. Further, the generating module 206 may provide the final CDS view generation prompt to the LLM 214 within the LLM module 212. Further, the LLM module 212 may generate, via the LLM 214, the final CDS view file 218 based on the final CDS view generation prompt. In other words, the final CDS view file 218 may be an optimal version of CDS view obtained based on optimization of the set of accuracy and performance parameters of the first CDS view file and the second CDS view file.
[032] It should be noted that all such aforementioned modules 202 – 212 may be represented as a single module or a combination of different modules. Further, as will be appreciated by those skilled in the art, each of the modules 202 – 212 may reside, in whole or in parts, on one device or multiple devices in communication with each other. In some embodiments, each of the modules 202 – 212 may be implemented as dedicated hardware circuit comprising custom application-specific integrated circuit (ASIC) or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Each of the modules 202 – 212 may also be implemented in a programmable hardware device such as a field programmable gate array (FPGA), programmable array logic, programmable logic device, and so forth. Alternatively, each of the modules 202 – 212 may be implemented in software for execution by various types of processors (e.g., processor 104). An identified module of executable code may, for instance, include one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, function, or other construct. Nevertheless, the executables of an identified module or component need not be physically located together but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose of the module. Indeed, a module of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different applications, and across several memory devices.
[033] As will be appreciated by one skilled in the art, a variety of processes may be employed for automated conversion of virtual data model views. For example, the exemplary system 100 and the associated computing device 102, may perform automated conversion of virtual data model views, by the processes discussed herein. In particular, as will be appreciated by those of ordinary skill in the art, control logic and/or automated routines for performing the techniques and steps described herein may be implemented by the system 100 and the associated computing device 102 either by hardware, software, or combinations of hardware and software. For example, suitable code may be accessed and executed by the one or more processors on the system 100 to perform some or all of the techniques described herein. Similarly, application specific integrated circuits (ASICs) configured to perform some or all of the processes described herein may be included in the one or more processors on the system 100.
[034] Referring now to FIG. 3A and FIG. 3B, an exemplary process 300 for automated conversion of virtual data model views is illustrated via a flow chart, in accordance with some embodiments of the present disclosure. The process 300 may be implemented by the computing device 102 of the system 100. In some embodiments, the process 300 may include receiving, by a receiving module (such as the receiving module 202) via a user interface, a calculation view file (such as the calculation view file 216) of a virtual data model in an in-memory database management system, at step 302. The calculation view file may include a graphical representation of the virtual data model.
[035] Upon receiving the calculation view file, the process 300 may include preprocessing, by a preprocessing module (such as the preprocessing module 204), the calculation view file using a set of preprocessing techniques, at step 304. The step 304 may include steps 306 and 308. The process 300 may include extracting, by the preprocessing module, metadata and structure information from the calculation view file, at step 306. Additionally, the process may include parsing, by the preprocessing module, the calculation view file to identify a set of key components of the virtual data model, at step 308.
[036] Once the calculation view file is preprocessed, the process 300 may include generating, by a generating module (such as the generating module 206) via an LLM, a first CDS view file corresponding to the calculation view file based on a direct CDS view generation prompt, at step 310. The direct CDS view generation prompt may include the calculation view file and a set of calculation view-CDS view conversion instructions. It should be noted that a CDS view file may include a code-based definition of the virtual data model. The step 310 may include steps 312 and 314.
[037] To generate the first CDS view file, the process 300 may include creating, by the generating module, the direct CDS view generation prompt based on the calculation view file, at step 312. Upon creating the direct CDS view generation prompt, the process 300 may include providing, by the generating module, the direct CDS view generation prompt to the LLM, at step 314.
[038] Additionally, the process 300 may include generating, by the generating module via the LLM, a second CDS view file corresponding to the calculation view file based on an intermediate representation generation prompt and a syntax conversion prompt, at step 316. The intermediate representation generation prompt may include the calculation view file and a set of calculation view-intermediate representation conversion instructions. The syntax conversion prompt may include an intermediate representation of the calculation view file and a set of CDS syntax instructions. The step 316 may include steps 318, 320, 322, 324, 326, and 328.
[039] To generate the second CDS view file, the process 300 may include creating, by the generating module, the intermediate representation generation prompt based on the calculation view file, at step 318. Upon creating the intermediate representation generation prompt, the process 300 may include providing, by the generating module, the intermediate representation generation prompt to the LLM, at step 320. Further, the process 300 may include generating, by the generating module via the LLM, the intermediate representation of the calculation view file based on the intermediate representation generation prompt, at step 322.
[040] Once the intermediate representation is generated, the process 300 may include validating, by a validating module (such as the validating module 208) via the LLM, the intermediate representation based on predefined structure criteria, at step 324. This is further explained in greater detail in conjunction with FIG. 4.
[041] Upon validation, the process 300 may include creating, by the generating module, the syntax conversion prompt based on the intermediate representation of the calculation view file, at step 326. Upon creating the syntax conversion prompt, the process 300 may include providing, by the generating module, the syntax conversion prompt to the LLM, at step 328.
[042] Upon generating the first CDS view file and the second CDS view file, the process 300 may include comparing, by a comparing module (such as the comparing module 210) via the LLM, the first CDS view file and the second CDS view file based on a set of accuracy and performance parameters, at step 330. Upon comparison, the process 300 may include generating, by the generating module via the LLM, a final CDS view file (such as the final CDS view file 218) corresponding to the calculation view file based on the comparing and a final CDS view generation prompt, at step 332. The final CDS view generation prompt may include the first CDS view file, the second CDS view file, results of the comparing, and a set of final CDS view generation instructions. The step 332 may include steps 334, and 336.
[043] To generate the final CDS view file, the process 300 may include creating, by the generating module, the final CDS view generation prompt based on the first CDS view file, the second CDS view file, and the results of the comparing, at step 334. Upon creating the final CDS view generation prompt, the process 300 may include providing, by the generating module, the final CDS view generation prompt to the LLM, at step 336.
[044] Referring now to FIG. 4, an exemplary process 400 for validating an intermediate representation of a calculation view file is illustrated via a flow chart, in accordance with some embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIG. 3. The process 400 may include validating, by the validating module via the LLM, the intermediate representation based on predefined structure criteria, at step 324. The step 324 may include steps 402, 404, 406, and 408.
[045] When the validation is unsuccessful, the process 400 may include identifying, by a generating module (such as the generating module 206) via the LLM, one or more missing attributes in the intermediate representation, at step 402. Upon identifying the one or more missing attributes, the process 400 may include dynamically creating, by the generating module, an intermediate representation modification prompt based on the identified one or more missing attributes, at step 404. The intermediate representation modification prompt may include the intermediate representation, the identified one or more missing attributes, and a set of intermediate representation modification instructions.
[046] Upon creating the intermediate representation modification prompt, the process 400 may include providing, by the generating module, the intermediate representation modification prompt to the LLM, at step 406. Upon receiving the intermediate representation modification prompt, the process 400 may include generating, by the generating module via the LLM, a modified intermediate representation based on the intermediate representation modification prompt, at step 408.
[047] Referring now to FIG. 5, a detailed exemplary control logic 500 for automated conversion of virtual data model views is illustrated via a flow chart, in accordance with some embodiments of the present disclosure. FIG. 5 is explained in conjunction with FIGS. 1 – 4. Initially, a user 502 (e.g., a software developer) may provide (or upload) a calculation view file (e.g., SAP HANA calculation view file) through a user interface, at step 504 of the control logic 500. The user interface may include one or more web apps based on Streamlit 506. It should be noted that the SAP HANA calculation view file may be analogous to the calculation view file 216.
[048] Upon receiving the SAP HANA calculation view file, the receiving module 202 may send the SAP HANA calculation view file to the preprocessing module 204 through a backend Application Programming Interface (API) 508. Further, the preprocessing module 204 may preprocess the SAP HANA calculation view file using a set of preprocessing techniques, at step 510. In particular, the preprocessing module 204 may extract metadata and structure information from the SAP HANA calculation view file. Additionally, the preprocessing module 204 may parse the SAP HANA calculation view file to identify a set of key components (e.g., joins, aggregations, or filters) of the virtual data model in the SAP HANA calculation view file. Further, the preprocessing module 204 may send the metadata, structure information, and the set of key components to the generating module 206.
[049] Upon receiving the preprocessed data, the generating module 206 may create a direct CDS view generation prompt based on the SAP HANA calculation view file. The direct CDS view generation prompt may include the metadata, the structure information, the set of key components, and a set of calculation view-CDS view conversion instructions. The set of calculation view-CDS view conversion instructions may include instructions for an LLM (such as the LLM 214) to convert the SAP HANA calculation view file into an As-Is CDS view file (analogous to the first CDS view file).
[050] By way of an example, an exemplary direct CDS view generation prompt created by the generating module 206 is described below.
“Input: [a pre-processed Calculation View File corresponding to a Virtual Data Model]
Convert the Calculation View File provided into an as-is Code Data Services (CDS) View File which is compatible with SAP S/4 HANA software suite.
Please ensure the following:
• Preserve all relevant data and metadata from the Calculation View File.
• Adapt any deprecated or outdated structures to their updated equivalents in the as-is CDS View File.
• Maintain compatibility with the specifications of SAP S/4 HANA software suite.
• Validate the output to ensure the as-is CDS View File adheres to the CDS View File schema or structure.”
[051] Upon creating the direct CDS view generation prompt, the generating module 206 may send the direct CDS view generation prompt to the LLM 214 within the LLM module 212. Further, the LLM module 212 may generate, via the LLM 214, the As-Is CDS view file based on the direct CDS view generation prompt, at step 512. The LLM 214 may ensure the structural integrity and adherence to SAP CDS syntax (e.g., SQL syntax) of the As-Is CDS view file.
[052] In addition to generation of the As-Is CDS view file, the generating module 206 may create an intermediate representation generation prompt using the SAP HANA calculation view file. The intermediate representation generation prompt may include the metadata, the structure information, the set of key components corresponding to the SAP HANA calculation view file, and a set of calculation view-intermediate representation conversion instructions. The set of calculation view-intermediate representation conversion instructions may include instructions for the LLM to generate an intermediate representation corresponding to the SAP HANA calculation view file.
[053] By way of an example, an exemplary intermediate representation generation prompt created by the generating module 206 is described below.
“Input: [a pre-processed Calculation View File corresponding to a Virtual Data Model]
Based on the Calculation View File provided, generate an Intermediate Representation of the Calculation View File.
The intermediate representation should:
• Identify and extract key components of the Calculation View File (e.g., headers, sections, fields, data blocks).
• Describe the structural organization of data objects in the Calculation View File (e.g., hierarchy, relationships, dependencies).
• Be suitable for further transformation into other formats or for documentation purposes.”
[054] Further, the generating module 206 may send the intermediate representation generation prompt to the LLM 214 within the LLM Module 212. Further, the LLM module 212 may generate, via the LLM 214, the intermediate representation corresponding to the SAP HANA calculation view file based on the intermediate representation generation prompt, at step 514. Once the intermediate representation is generated, the validating module 208 may validate, via the LLM 214, the intermediate representation based on predefined structure criteria (e.g., predefined rules corresponding to file structure).
[055] In some embodiments, if the validation is unsuccessful, the generating module 206 may identify, via the LLM 214, one or more missing attributes in the intermediate representation. Upon identifying the one or more missing attributes, the generating module 206 may dynamically adjust (or modify) the intermediate representation generation prompt to obtain the intermediate representation modification prompt based on the identified one or more missing attributes. The intermediate representation modification prompt may include the intermediate representation, the identified one or more missing attributes, and a set of intermediate representation modification instructions. The set of intermediate representation modification instructions may include instructions for the LLM 214 to modify the intermediate representation based on the identified one or more missing attributes.
[056] By way of an example, an exemplary adjusted (or modified) intermediate generation prompt created by the generating module 206 is described below.
“Input: [Intermediate Representation of a Calculation View File provided as input]
Based on the Intermediate Representation provided, evaluate the correctness, structure, and format of the intermediate representation. Based on the evaluation, identify whether there are any missing attributes in the intermediate representation. If any missing attributes are found, modify the Intermediate Representation. Generate the modified Intermediate Representation as the output.”
[057] Further, the generating module 206 may provide the intermediate representation modification prompt to the LLM 214 within the LLM module 212. Further, the LLM module 212 may generate, via the LLM 214, a modified intermediate representation based on the intermediate representation modification prompt. Upon validation, the generating module 206 may create a syntax conversion prompt based on the intermediate representation of the SAP HANA calculation view file. The syntax conversion prompt may include the intermediate representation, and a set of CDS syntax instructions. Upon creating the syntax conversion prompt, the generating module 206 may send the syntax conversion prompt to the LLM 214 within the LLM module 212.
[058] Further, the LLM module 212 may convert, via the LLM 214, the ‘XML’ syntax into ‘SQL’ syntax corresponding to the intermediate representation. In other words, the LLM module 212 may update, via the LLM 214, the intermediate representation to align with the SAP S/4HANA database structures to obtain the second CDS view file, at step 516. To update the intermediate representation, the LLM 214 may apply naming conversions, schema updates, data type adjustments, or the like. Once the second CDS view file is generated, the generating module 206 may create a verification prompt based on the second CDS view file. The verification prompt may include the second CDS view file and a set of verification instructions. The set of verification instructions may include instructions for the LLM 214 to verify the second CDS view file based on a set of accuracy and performance parameters. Further, the generating module 206 may send the verification prompt to the LLM 214 within the LLM module 212. Further, the LLM module 212 may verify, via the LLM 214, the second CDS view file based on the verification prompt, at step 518. The verification of the second CDS view file may include validating the second CDS view file for performance optimization and SAP best practices.
[059] In some embodiments, if the verification is unsuccessful, the LLM 214 may recommend indexes, annotations, or query optimizations corresponding to the second CDS view file. Upon successful verification, the comparing module 210 may compare, via the LLM 214, the As-Is CDS view file with the second CDS view file based on the set of accuracy and the performance parameters, at step 520. Based on the comparison, the generating module 206 may create, via the LLM 214, a final CDS view generation prompt based on the As-Is CDS view file, the CDS view file, and results of the comparing. The final CDS view generation prompt may include the As-Is CDS view file, the CDS view file, the results of the comparing, and a set of final CDS view generation instructions. The set of final CDS view generation instructions may include instructions for the LLM 214 to generate a final CDS view file 522 corresponding to the SAP HANA calculation view file.
[060] By way of an example, an exemplary final CDS view generation prompt created by the generating module 206 is described below.
“Input: [As-Is CDS View File, and a second CDS View File provided as input]
The input includes two versions of CDS view files corresponding to a same virtual data model. Both the CDS view files have been obtained through conversion of the same calculation view file.
Based on the As-Is CDS View File and CDS View File provided, compare the two CDS view files based on a set of performance and accuracy parameters.
For optimized accuracy, ensure that accuracy of the virtual data model represented in the generated CDS view file (i.e., the As-Is CDS view file and the second CDS view file) relative to the virtual data model represented in the calculation view file is accurate. For optimized performance, ensure that the performance of the generated CDS view file in a corresponding database management system (such as SAP S/4HANA). Based on the comparison, generate an optimal final CDS view file for the virtual data model.”
[061] Further, the generating module 206 may send the final CDS view generation prompt to the LLM 214 within the LLM module 212. Further, the LLM module 212 may generate, via the LLM 214, the final CDS view file 522 corresponding to the SAP HANA calculation view file based on the final CDS view generation prompt.
[062] As will be also appreciated, the above-described techniques may take the form of computer or controller implemented processes and apparatuses for practicing those processes. The disclosure can also be embodied in the form of computer program code containing instructions embodied in tangible media, such as floppy diskettes, solid state drives, CD-ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer or controller, the computer becomes an apparatus for practicing the invention. The disclosure may also be embodied in the form of computer program code or signal, for example, whether stored in a storage medium, loaded into and/or executed by a computer or controller, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.
[063] The disclosed methods and systems may be implemented on a conventional or a general-purpose computer system, such as a personal computer (PC) or server computer. Referring now to FIG. 6, an exemplary computing system 600 that may be employed to implement processing functionality for various embodiments (e.g., as a SIMD device, client device, server device, one or more processors, or the like) is illustrated. Those skilled in the relevant art will also recognize how to implement the invention using other computer systems or architectures. The computing system 600 may represent, for example, a user device such as a desktop, a laptop, a mobile phone, personal entertainment device, DVR, and so on, or any other type of special or general-purpose computing device as may be desirable or appropriate for a given application or environment. The computing system 600 may include one or more processors, such as a processor 602 that may be implemented using a general or special purpose processing engine such as, for example, a microprocessor, microcontroller or other control logic. In this example, the processor 602 is connected to a bus 604 or other communication medium. In some embodiments, the processor 602 may be an Artificial Intelligence (AI) processor, which may be implemented as a Tensor Processing Unit (TPU), or a graphical processor unit, or a custom programmable solution Field-Programmable Gate Array (FPGA).
[064] The computing system 600 may also include a memory 606 (main memory), for example, Random Access Memory (RAM) or other dynamic memory, for storing information and instructions to be executed by the processor 602. The memory 606 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 602. The computing system 600 may likewise include a read only memory (“ROM”) or other static storage device coupled to bus 604 for storing static information and instructions for the processor 602.
[065] The computing system 600 may also include a storage devices 608, which may include, for example, a media drive 610 and a removable storage interface. The media drive 610 may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an SD card port, a USB port, a micro USB, an optical disk drive, a CD or DVD drive (R or RW), or other removable or fixed media drive. A storage media 612 may include, for example, a hard disk, magnetic tape, flash drive, or other fixed or removable medium that is read by and written to by the media drive 610. As these examples illustrate, the storage media 612 may include a computer-readable storage medium having stored therein particular computer software or data.
[066] In alternative embodiments, the storage devices 608 may include other similar instrumentalities for allowing computer programs or other instructions or data to be loaded into the computing system 600. Such instrumentalities may include, for example, a removable storage unit 614 and a storage unit interface 616, such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit 614 to the computing system 600.
[067] The computing system 600 may also include a communications interface 618. The communications interface 618 may be used to allow software and data to be transferred between the computing system 600 and external devices. Examples of the communications interface 618 may include a network interface (such as an Ethernet or other NIC card), a communications port (such as for example, a USB port, a micro USB port), Near field Communication (NFC), etc. Software and data transferred via the communications interface 618 are in the form of signals which may be electronic, electromagnetic, optical, or other signals capable of being received by the communications interface 618. These signals are provided to the communications interface 618 via a channel 620. The channel 620 may carry signals and may be implemented using a wireless medium, wire or cable, fiber optics, or other communications medium. Some examples of the channel 620 may include a phone line, a cellular phone link, an RF link, a Bluetooth link, a network interface, a local or wide area network, and other communications channels.
[068] The computing system 600 may further include Input/Output (I/O) devices 622. Examples may include, but are not limited to a display, keypad, microphone, audio speakers, vibrating motor, LED lights, etc. The I/O devices 622 may receive input from a user and also display an output of the computation performed by the processor 602. In this document, the terms “computer program product” and “computer-readable medium” may be used generally to refer to media such as, for example, the memory 606, the storage devices 608, the removable storage unit 614, or signal(s) on the channel 620. These and other forms of computer-readable media may be involved in providing one or more sequences of one or more instructions to the processor 602 for execution. Such instructions, generally referred to as “computer program code” (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system 600 to perform features or functions of embodiments of the present invention.
[069] In an embodiment where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into the computing system 600 using, for example, the removable storage unit 614, the media drive 610 or the communications interface 618. The control logic (in this example, software instructions or computer program code), when executed by the processor 602, causes the processor 602 to perform the functions of the invention as described herein.
[070] Various embodiments provide method and system for automated conversion of virtual data model views. The disclosed method and system may receive via a user interface, a calculation view file of a virtual data model in an in-memory database management system. The calculation view file may include a graphical representation of the virtual data model. Further, the disclosed method and system may generate, via an LLM, a first Core Data Services (CDS) view file corresponding to the calculation view file based on a direct CDS view generation prompt. A CDS view file may include a code-based definition of the virtual data model. The direct CDS view generation prompt may include the calculation view file and a set of calculation view-CDS view conversion instructions. Further, the disclosed method and system may generate, via an LLM, a second CDS view file corresponding to the calculation view file based on an intermediate representation generation prompt and a syntax conversion prompt. The intermediate representation generation prompt may include the calculation view file and a set of calculation view-intermediate representation conversion instructions. The syntax conversion prompt may include an intermediate representation of the calculation view file and a set of CDS syntax instructions. Moreover, the disclosed method and system may compare, via an LLM, the first CDS view file and the second CDS view file based on a set of accuracy and performance parameters. Thereafter, the disclosed method and system may generate, via an LLM, a final CDS view file corresponding to the calculation view file based on the comparing and a final CDS view generation prompt. The final CDS view generation prompt may include the first CDS view file, the second CDS view file, results of the comparing, and a set of final CDS view generation instructions.
[071] Thus, the disclosed method and system try to overcome the technical problem of automated conversion of virtual data model views. The disclosed method and system may automatically convert of SAP HANA calculation view file into SAP S/4 HANA CDS view file. The disclosed method and system may keep the core clean in the SAP S/4 HANA CDS view file. The disclosed method and system may provide standardization and upgrade-friendly by minimizing the custom code and modifications in the core SAP S/4 HANA CDS view file. The disclosed method and system may enhance the system performance and sustainability. The disclosed method and system may reduce resource requirements, errors, and time.
[072] In light of the above mentioned advantages and the technical advancements provided by the disclosed method and system, the claimed steps as discussed above are not routine, conventional, or well understood in the art, as the claimed steps enable the following solutions to the existing problems in conventional technologies. Further, the claimed steps clearly bring an improvement in the functioning of the device itself as the claimed steps provide a technical solution to a technical problem.
[073] The specification has described method and system for automated test case generation. The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[074] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, nonvolatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.
[075] It is intended that the disclosure and examples be considered as exemplary only, with a true scope and spirit of disclosed embodiments being indicated by the following claims.  , Claims:CLAIMS
I/We Claim:
1. A method (300) for automated conversion of virtual data model views, the method (300) comprising:
receiving (302), by a computing device (102) via a user interface, a calculation view file (216) of a virtual data model in an in-memory database management system, wherein the calculation view file (216) comprises a graphical representation of the virtual data model;
generating (310), by the computing device (102) via a Large Language Model (LLM) (214), a first Core Data Services (CDS) view file corresponding to the calculation view file (216) based on a direct CDS view generation prompt , wherein a CDS view file comprises a code-based definition of the virtual data model, and wherein the direct CDS view generation prompt comprises the calculation view file (216) and a set of calculation view-CDS view conversion instructions;
generating (316), by the computing device (102) via the LLM (214), a second CDS view file corresponding to the calculation view file (216) based on an intermediate representation generation prompt and a syntax conversion prompt, wherein the intermediate representation generation prompt comprises the calculation view file (216) and a set of calculation view-intermediate representation conversion instructions, and wherein the syntax conversion prompt comprises an intermediate representation of the calculation view file (216) and a set of CDS syntax instructions;
comparing (330), by the computing device (102) via the LLM (214), the first CDS view file and the second CDS view file based on a set of accuracy and performance parameters; and
generating (332), by the computing device (102) via the LLM (214), a final CDS view file (218) corresponding to the calculation view file (216) based on the comparing and a final CDS view generation prompt, wherein the final CDS view generation prompt comprises the first CDS view file, the second CDS view file, results of the comparing, and a set of final CDS view generation instructions.

2. The method (300) as claimed in claim 1, comprising preprocessing (304) the calculation view file (216) using a set of preprocessing techniques, wherein the preprocessing comprises:
extracting (306) metadata and structure information from the calculation view file (216); and
parsing (308) the calculation view file (216) to identify a set of key components of the virtual data model.

3. The method (300) as claimed in claim 1, wherein generating the first CDS view file comprises:
creating (312) the direct CDS view generation prompt based on the calculation view file (216); and
providing (314) the direct CDS view generation prompt to the LLM (214).

4. The method (300) as claimed in claim 1, wherein generating the second CDS view file corresponding to the calculation view file (216) comprises:
creating (318) the intermediate representation generation prompt based on the calculation view file (216);
providing (320) the intermediate representation generation prompt to the LLM (214); and
generating (322), via the LLM (214), the intermediate representation of the calculation view file (216) based on the intermediate representation generation prompt.

5. The method (300) as claimed in claim 4, comprising:
validating (324), via the LLM (214), the intermediate representation based on predefined structure criteria;
identifying (402), via the LLM (214), one or more missing attributes in the intermediate representation based on an unsuccessful validation;
dynamically creating (404) an intermediate representation modification prompt based on the identified one or more missing attributes, wherein the intermediate representation modification prompt comprises the intermediate representation, the identified one or more missing attributes, and set of intermediate representation modification instructions;
providing (406) the intermediate representation modification prompt to the LLM (214); and
generating (408), via the LLM (214), a modified intermediate representation based on the intermediate representation modification prompt.

6. The method (300) as claimed in claim 4, wherein generating the second CDS view file corresponding to the calculation view file (216) comprises:
creating (326) the syntax conversion prompt based on the intermediate representation of the calculation view file (216); and
providing (328) the syntax conversion prompt to the LLM (214).

7. The method (300) as claimed in claim 1, wherein generating the final CDS view file corresponding to the calculation view file (216) comprises:
creating (334) the final CDS view generation prompt based on the first CDS view file, the second CDS view file, and the results of the comparing; and
providing (336) the final CDS view generation prompt to the LLM (214).

8. A system (100) for automated conversion of virtual data model views, the system (100) comprising:
a processor (104); and
a memory (106) communicatively coupled to the processor (104), wherein the memory (106) stores processor executable instructions, which, on execution, causes the processor (104) to:
receive (302), via a user interface, a calculation view file (216) of a virtual data model in an in-memory database management system, wherein the calculation view file (216) comprises a graphical representation of the virtual data model;
generate (310), via a Large Language Model (LLM) (214), a first Core Data Services (CDS) view file corresponding to the calculation view file (216) based on a direct CDS view generation prompt, wherein a CDS view file comprises a code-based definition of the virtual data model, and wherein the direct CDS view generation prompt comprises the calculation view file (216) and a set of calculation view-CDS view conversion instructions;
generate (316), via the LLM (214), a second CDS view file corresponding to the calculation view file (216) based on an intermediate representation generation prompt and a syntax conversion prompt, wherein the intermediate representation generation prompt comprises the calculation view file (216) and a set of calculation view-intermediate representation conversion instructions, and wherein the syntax conversion prompt comprises an intermediate representation of the calculation view file (216) and a set of CDS syntax instructions;
compare (330), via the LLM (214), the first CDS view file and the second CDS view file based on a set of accuracy and performance parameters; and
generate (332), via the LLM (214), a final CDS view file (218) corresponding to the calculation view file (216) based on the comparing and a final CDS view generation prompt, wherein the final CDS view generation prompt comprises the first CDS view file, the second CDS view file, results of the comparing, and a set of final CDS view generation instructions.

9. The system (100) as claimed in claim 8, wherein the processor executable instructions cause the processor (104) to preprocess (304) the calculation view file (216) using a set of preprocessing techniques, wherein the preprocessing comprises:
extract (306) metadata and structure information from the calculation view file (216); and
parse (308) the calculation view file (216) to identify a set of key components of the virtual data model.

10. The system (100) as claimed in claim 8, wherein generating the first CDS view file, the processor executable instructions cause the processor (104) to:
create (312) the direct CDS view generation prompt based on the calculation view file (216); and
provide (314) the direct CDS view generation prompt to the LLM (214).

11. The system (100) as claimed in claim 8, wherein generating the second CDS view file corresponding to the calculation view file (216), the processor executable instructions cause the processor (104) to:
create (318) the intermediate representation generation prompt based on the calculation view file (216);
provide (320) the intermediate representation generation prompt to the LLM (214); and
generate (322), via the LLM (214), the intermediate representation of the calculation view file (216) based on the intermediate representation generation prompt.

12. The system (100) as claimed in claim 11, wherein the processor executable instructions cause the processor (104) to:
validate (324), via the LLM (214), the intermediate representation based on predefined structure criteria;
identify (402), via the LLM (214), one or more missing attributes in the intermediate representation based on an unsuccessful validation;
dynamically create (404) an intermediate representation modification prompt based on the identified one or more missing attributes, wherein the intermediate representation modification prompt comprises the intermediate representation, the identified one or more missing attributes, and set of intermediate representation modification instructions;
provide (406) the intermediate representation modification prompt to the LLM (214); and
generate (408), via the LLM (214), a modified intermediate representation based on the intermediate representation modification prompt.

13. The system (100) as claimed in claim 11, wherein generating the second CDS view file corresponding to the calculation view file (216), the processor executable instructions cause the processor (104) to:
create (326) the syntax conversion prompt based on the intermediate representation of the calculation view file (216); and
provide (328) the syntax conversion prompt to the LLM (214).

14. The system (100) as claimed in claim 8, wherein generating the final CDS view file (218) corresponding to the calculation view file (216), the processor executable instructions cause the processor (104) to:
create (334) the final CDS view generation prompt based on the first CDS view file, the second CDS view file, and the results of the comparing; and
provide (336) the final CDS view generation prompt to the LLM (214).