Search

US-12625707-B2 - System and method for system extensibility

US12625707B2US 12625707 B2US12625707 B2US 12625707B2US-12625707-B2

Abstract

According to some embodiments, systems and methods are provided including a memory storing processor-executable code; and a processing unit to execute the processor-executable program code to cause the system to: receive a request for a sequence, the sequence including two or more components; identify one or more possible sequences based on the request; build a sequence based on the identified one or more possible sequences, wherein building the sequence includes adding an extension to the sequence; validate the built sequence; and store the validated sequence. Numerous other aspects are provided.

Inventors

  • Zhijie Ai

Assignees

  • SAP SE

Dates

Publication Date
20260512
Application Date
20240408

Claims (14)

  1. 1 . A system comprising: a memory storing processor-executable program code; and a processing unit to execute the processor-executable program code to cause the system to: receive a request for a procedure, the procedure including two or more components; identify one or more possible procedures based on the request; build the procedure based on the identified one or more possible procedures, wherein building the procedure includes adding extension code to a first component of the first possible procedure at an extension point of the first component to modify the first possible procedure and output a reuse component, wherein the extension point is a pre-defined location in a standard view virtual data model of the component; validate the reuse component in the built procedure; convert the validated reuse component to a binary artificial, wherein the binary artificial is a runtime object in a binary format; and store the binary artificial in a persistency layer.
  2. 2 . The system of claim 1 , further comprising processor-executable program code to cause the system to: validate, via an extension validator, the added extension code prior to conversion.
  3. 3 . The system of claim 2 , wherein the validation is via at least one of a static code scan, a unit test, a static documentation scan and a check of inconsistency codes.
  4. 4 . The system of claim 1 , wherein none of the possible procedures are selected in a case the possible procedures are unsuitable for user requirements.
  5. 5 . The system of claim 4 , wherein the built procedure is a new procedure.
  6. 6 . The system of claim 1 , wherein the one or more possible procedures are identified by fuzzy logic.
  7. 7 . The system of claim 1 , wherein the one or more possible procedures include for each component of the procedure: a function, one or more extension points, limitations and sample usage codes.
  8. 8 . The system of claim 1 , wherein the added extension is added to a first component of the two or more components of the possible procedure.
  9. 9 . A computer-implemented method comprising: receiving a request for a procedure, the procedure including two or more components; identifying one or more possible procedures based on the request; building a procedure based on the identified one or more possible procedures, wherein building the procedure includes adding extension code to a first component of the first possible procedure at an extension point of the first component to modify the first possible procedure and output a reuse component, wherein the extension point is a pre-defined location in a standard view virtual data model of the component; validating the reuse component in the built procedure; converting the validated reuse component to a binary artificial, wherein the binary artificial is a runtime object in a binary format; and storing the binary artificial in a persistency layer.
  10. 10 . The method of claim 9 , wherein the one or more possible procedures are identified by fuzzy logic.
  11. 11 . The method of claim 9 , wherein the one or more possible procedures include for each component of the procedure: a function, one or more extension points, limitations and sample usage codes.
  12. 12 . A non-transitory computer readable medium having executable instructions stored thereon to perform a method, the method comprising: receiving a request for a procedure, the procedure including two or more components; identifying one or more possible procedures based on the request; building a procedure based on the identified one or more possible procedures, wherein building the procedure includes adding extension code to a first component of the first possible procedure at an extension point of the first component to modify the first possible procedure and output a reuse component, wherein the extension point is a pre-defined location in a standard view virtual data model of the component; validating the reuse component in the built procedure; converting the validated built procedure to a binary artificial, wherein the binary artificial is a runtime object in a binary format; and storing the binary artificial.
  13. 13 . The medium of claim 12 , wherein the one or more possible procedures are identified by fuzzy logic.
  14. 14 . The medium of claim 12 , wherein the one or more possible procedures include for each component of the procedure: a function, one or more extension points, limitations and sample usage codes.

Description

BACKGROUND As organizations evolve, computer platforms (including a hardware system and an operating system) supporting the organizations become larger and more complex. For example, when a system is updated, the updates may be added to the system instead of replacing elements of the systems. Additionally, it may be difficult to re-use elements from a prior iteration, thereby requiring other new elements. The accumulation of the new elements, including updates, to the system without removing older elements of the system may result in technical debt. As a result, with each update and change, it may be more difficult to add updates and changes as the platform resources may not be available. Systems and methods are desired which support the expansion of system architecture. BRIEF DESCRIPTION OF THE DRAWINGS Features and advantages of the example embodiments, and the manner in which the same are accomplished, will become more readily apparent with reference to the following detailed description taken in conjunction with the accompanying drawings. FIG. 1 is a block diagram of a system. FIG. 2 is a block diagram of a system according to some embodiments. FIG. 3A is a block diagram of a system architecture according to some embodiments. FIG. 3B is a continuation of the block diagram of FIG. 3A according to some embodiments. FIG. 4 is a flow diagram according to some embodiments. FIG. 5 is a non-exhaustive example of a user interface according to some embodiments. FIG. 6 is a non-exhaustive example of a user interface according to some embodiments. FIG. 7 is a non-exhaustive example of a user interface according to some embodiments. FIG. 8 is a non-exhaustive example of a user interface according to some embodiments. FIG. 9 is a non-exhaustive example of a user interface according to some embodiments. FIG. 10 is a flow diagram according to some embodiments. FIG. 11 is non-exhaustive example of a user interface according to some embodiments. FIG. 12 is a non-exhaustive example of a user interface according to some embodiments. FIG. 13 is a non-exhaustive example of a user interface according to some embodiments. FIG. 14 is a non-exhaustive example of a user interface according to some embodiments. FIG. 15 is a block diagram of a non-exhaustive example of a component hierarchy according to some embodiments. FIG. 16 is a non-exhaustive example of a table according to some embodiments. FIG. 17 is a block diagram of a deployment architecture according to some embodiments. Throughout the drawings and the detailed description, unless otherwise described, the same drawing reference numerals will be understood to refer to the same elements, features and structures. The relative size and depiction of these elements may be exaggerated or adjusted for clarity, illustration, and/or convenience. DETAILED DESCRIPTION In the following description, specific details are set forth in order to provide a thorough understanding of the various example embodiments. It should be appreciated that various modifications to the embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the disclosure. Moreover, in the following description, numerous details are set forth for the purpose of explanation. However, one of ordinary skill in the art should understand that embodiments may be practiced without the use of these specific details. In other instances, well-known structures and processes are not shown or described in order not to obscure the description with unnecessary detail. Thus, the present disclosure is not intended to be limited to the embodiments shown but is to be accorded the widest scope consistent with the principles and features disclosed herein. It should be appreciated that in development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developer's specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure. One or more embodiments or elements thereof can be implemented in the form of a computer program product including a non-transitory computer readable storage medium with computer usable program code for performing the method steps indicated herein. Furthermore, one or more embodiments or elements thereof can be implemented in the form of a system (or apparatus) including a memory, and at least one processor that is coupled to the memory and operative to perform exemplary method steps. Yet further, in another aspect, one or more embodiments or eleme