Abstract: Extensibility tools are provided to customers for defining custom restriction rules for enhanced access controls. In an example method, a listing of restriction rules available for a business role are presented. The restriction rules include predefined restriction rules and at least one custom restriction rule placeholder, wherein the predefined restriction rules are delivered with the enterprise software system the at least one customer restriction rule placeholders are associated with a link to custom code developed as a customer-specific restriction rule. A selection of a particular custom restriction rule is received and associated with the particular business role. When evaluating the restriction rule, the custom code and a set of master data defined in the custom code is accessed to determine restrictions for each of the end users associated with the business role. A set of access objects are derived for each user based on the information.

Abstract: Techniques are described for providing extensibility tools to customers for defining custom restriction rules for enhanced access controls. In an example method, a listing of restriction rules available for a business role are presented. The restriction rules include predefined restriction rules and at least one custom restriction rule placeholder, wherein the predefined restriction rules are delivered with the enterprise software system the at least one customer restriction rule placeholders are associated with a link to custom code developed as a customer-specific restriction rule. A selection of a particular custom restriction rule is received and associated with the particular business role. When evaluating the restriction rule, the custom code and a set of master data defined in the custom code is accessed to determine restrictions for each of the end users associated with the business role. A set of access objects are derived for each user based on the information.

Abstract: Disclosed herein are system, method, and computer program product embodiments for the detection and resolution of conflicts in data synchronization. An embodiment operates by receiving an upload from a user device of one or more changes to a local copy of a master document. A conflict is identified between the one or more uploaded changes and one or more previous changes to the master document. A super user is notified of the conflict. A resolution of the conflict is received. The resolution to resolve the conflict is applied.

Abstract: The present disclosure involves computer-implemented methods, software, and systems for determining a most suitable address for a master data object instance for a given usage in a business transaction document, master data object, or business process. A computer-implemented method includes determining, using at least one computer, an address determination sequence, applying the address determination sequence to available address instances of a master data object instance, identifying a most suitable address from among the available instances, and retrieving an address value from the identified most suitable address instance.

Abstract: The present disclosure is directed to executing transformation rules. In some implementations, a method includes receiving a request to apply a predefined transformation rule to a portion of a service. In response to at least the request, the predefined transformation rule is identified from a plurality of predefined transformation rules included in a business model. Each of the plurality of predefined transformation rules are configured to update at least one service independent of generating code in a service layer. The predefined transformation rule is assigned to the portion of the service.

Abstract: The disclosure generally describes computer-implemented methods, computer-program products, and systems for modeling and deploying decision services. One computer-implemented method includes during uptime processing: generating at least one shadow database table corresponding to a new business object (BO) persistency model, establishing change recording for at least one database table associated with an old BO persistency model, retrieving, as changed data and using at least one computer, changed BO data from the at least one database table, transforming, as transformed data, the changed data to correspond to the new BO persistency model, writing the transformed data to the generated at least one shadow database table, and retrieving, as further changed data, BO data from the at least one database table upon a determination that the BO data has changed in the at least one database table after a prior retrieval of the BO data from the at least one database table.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to an address snapshot and an approval process definition business object.

Abstract: The present disclosure involves computer-implemented methods, software, and systems for efficiently handling address data in business transaction documents. A computer-implemented method includes receiving a modification to address data associated with an existing address instance, receiving, using at least one computer, an indication of a modification type, creating a new snapshot instance, associating the modified address data with the new snapshot instance, retrieving a unique reference value for the new address snapshot instance, and associating the unique reference value identifying the new address snapshot instance with the address instance.

Abstract: A computer-implemented system may include reception of an instruction to create an association for an element of a UI component model, determination of a first business object model of the association, determination of a second business object model of the association, definition of foreign key parameters associating an attribute of the first business object model with an attribute of an element of the second business object model, reception of an instruction to bind the element of the UI component model to a second attribute of the element of the second business object model, and creation of metadata in the UI component model associating the element of the UI component model with the second attribute of the element of the second business object model, the metadata comprising the foreign key parameters.

Abstract: A context for a service request made by a service consumer can be used to establish a constraint rules set that is applied by a service provider. A context associated with a first service request can be received from a service consumer. An identity of the service consumer can be verified. A constraint value request associated with the service request can be received from a service provider responding to the service request. One or more constraints can be derived from the first context. An identity of a service provider that will fulfill the service request can be verified. The one or more constraints can be provided to the service provider. Related systems, apparatus, methods, and/or articles are also described.

Abstract: The disclosure generally describes computer-implemented methods, computer-program products, and systems for modeling and deploying decision services. One computer-implemented method includes during uptime processing: generating at least one shadow database table corresponding to a new business object (BO) persistency model, establishing change recording for at least one database table associated with an old BO persistency model, retrieving, as changed data and using at least one computer, changed BO data from the at least one database table, transforming, as transformed data, the changed data to correspond to the new BO persistency model, writing the transformed data to the generated at least one shadow database table, and retrieving, as further changed data, BO data from the at least one database table upon a determination that the BO data has changed in the at least one database table after a prior retrieval of the BO data from the at least one database table.

Abstract: A computer-implemented system may include reception, from a user interface client application, of a user interface request conforming to a user interface component model, translation of the user interface request from the user interface component model to a business object model, execution of interactions associated with the translated request with a backend service layer, the interactions conforming to the business object model, determination of business object node changes and business object property changes conforming to the business object model and corresponding to the interactions, translation of the business object node changes and the business object property changes to user interface data changes and user interface event property changes conforming to the user interface component model, and provision of the user interface data changes and user interface event property changes to the user interface client.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to an address snapshot and an approval process definition business object.

Abstract: A computer-implemented system may receive and store first metadata defining a view of a user interface component, the first metadata conforming to a user interface view model, receive and store second metadata defining a controller of the user interface component, the second metadata conforming to a user interface controller model, receive and store third metadata defining data of the user interface component, the third metadata conforming to a user interface data model, and execute a framework to provide the user interface component to a client based on the first metadata, the second metadata and the third metadata.

Abstract: The present disclosure involves computer-implemented methods, software, and systems for efficiently handling address data in business transaction documents.. A computer-implemented method includes receiving a modification to address data associated with an existing address instance, receiving, using at least one computer, an indication of a modification type, creating a new snapshot instance, associating the modified address data with the new snapshot instance, retrieving a unique reference value for the new address snapshot instance, and associating the unique reference value identifying the new address snapshot instance with the address instance.

Abstract: The present disclosure involves computer-implemented methods, software, and systems for determining a most suitable address for a master data object instance for a given usage in a business transaction document, master data object, or business process. A computer-implemented method includes determining, using at least one computer, an address determination sequence, applying the address determination sequence to available address instances of a master data object instance, identifying a most suitable address from among the available instances, and retrieving an address value from the identified most suitable address instance.

Abstract: A computer-implemented system may include reception of an instruction to create an association for an element of a UI component model, determination of a first business object model of the association, determination of a second business object model of the association, definition of foreign key parameters associating an attribute of the first business object model with an attribute of an element of the second business object model, reception of an instruction to bind the element of the UI component model to a second attribute of the element of the second business object model, and creation of metadata in the UI component model associating the element of the UI component model with the second attribute of the element of the second business object model, the metadata comprising the foreign key parameters.

Abstract: A computer-implemented system may include reception, from a user interface client application, of an instruction to execute a user interface script conforming to a user interface component model, and determination of whether to execute the user interface script in the user interface client application or in a user interface backend application. If it is determined to execute the user interface script in the user interface client application, first program code associated with the user interface script is executed in the user interface client application, and if it is determined to execute the user interface script in the user interface backend application, second program code associated with the user interface script is executed in the user interface backend application.

Abstract: A computer-implemented system may include reception, from a user interface client application, of a user interface request conforming to a user interface component model, translation of the user interface request from the user interface component model to a business object model, execution of interactions associated with the translated request with a backend service layer, the interactions conforming to the business object model, determination of business object node changes and business object property changes conforming to the business object model and corresponding to the interactions, translation of the business object node changes and the business object property changes to user interface data changes and user interface event property changes conforming to the user interface component model, and provision of the user interface data changes and user interface event property changes to the user interface client.

Abstract: The present disclosure is directed to executing transformation rules. In some implementations, a method includes receiving a request to apply a predefined transformation rule to a portion of a service. In response to at least the request, the predefined transformation rule is identified from a plurality of predefined transformation rules included in a business model. Each of the plurality of predefined transformation rules are configured to update at least one service independent of generating code in a service layer. The predefined transformation rule is assigned to the portion of the service.