Abstract: Efficient transport of content packages comprising multiple objects, is achieved utilizing lineage analysis. User selection of an object in a package, triggers a dependency request to a landscape containing the object. The landscape returns a dependencies result, which includes dependencies between the selected object and others present within the landscape. The dependencies result is used to create a dependents tree structure. Based upon the dependents tree and the originally selected object, a lineage view is created and afforded to the user. Example lineage views may comprise spider charts with the selected object at the center. The user may further explore object dependencies by interacting with the lineage view to create other lineage views. Providing intuitive visualization of object dependencies, aids in efficient package transport (e.g., by allowing a user to identify dependent object(s) missing from the package, and/or particular objects having many dependent objects that also require transport).

Abstract: Content packages (including, e.g., visualizations, models) are replicated from one landscape to another that is restricted. The restricted landscape may be governed by regulations relating to privacy or other concerns. For package replication, a poll-pull mechanism is applied. Specifically, the first landscape creates a replicate package job targeting to the restricted landscape. The restricted landscape periodically polls and checks for any replicate package job for targeted for it. If any targeted replicate package jobs are discovered by polling, the restricted landscape will pull the job details to create a new replicate package job in its own (restricted) landscape. Under this approach, even though the replicate package job was initiated in the first landscape, it will be executed in the restricted landscape, thereby conforming to any governing regulations.

Abstract: In an example embodiment, a graphical user interface-based software tool is provided that uses integrated process information and information of a technical infrastructure to provide automatically-analyze integrations. There are several current approaches to capturing information relevant to the above questions available within a computer system, but each of them only captures a fragment of the information that will be utilized and are not linked. Additionally, most of them do not include extensibility information. The provided tool solves these issues.

Abstract: Embodiments relate to file-based sharing of content through a content distribution network. A request is received from a source to disseminate content to a target consumer. The request does not include target consumer URL information. Based upon the request, content metadata stored in a database with content data, is referenced to generate a file including metadata comprising a portion of the content metadata. The file does not include the content data. The file is exported to the source. The source delivers the file to the target consumer through a communication channel (e.g., shared folder, email) located outside of the distribution network. The file is imported from the target consumer. The metadata of the file is processed to examine its integrity. The metadata may comprise a key for reference during this process. Upon confirming integrity of the file, the content data and the content metadata are distributed to the target consumer.

Abstract: A software package comprising a plurality of software objects and package metadata is accessed and used to provide a graphical user interface including a first area in which details about the software objects are displayed and a second area where a user can select a location path, in an analytic cloud tenant on which the package is to be imported. A selection is made of the location path for at least one resource object. The system determines if the package metadata is of a type that includes information about a parent resource object but not descendant resource objects and not ancestor resource objects other than the parent resource object, for each resource object in the plurality of software objects, and if so, recursively identifies a parent object for each resource object in the plurality of software objects. The ancestor hierarchy from the recursively identified parent object(s) is reversed and inverted.

Abstract: A software package comprising a plurality of software objects and package metadata is accessed and used to provide a graphical user interface including a first area in which details about the software objects are displayed and a second area where a user can select a location path, in an analytic cloud tenant on which the package is to be imported. A selection is made of the location path for at least one resource object. The system determines if the package metadata is of a type that includes information about a parent resource object but not descendant resource objects and not ancestor resource objects other than the parent resource object, for each resource object in the plurality of software objects, and if so, recursively identifies a parent object for each resource object in the plurality of software objects. The ancestor hierarchy from the recursively identified parent object(s) is reversed and inverted.

Abstract: A distribution network communicates content to tenant groups in a secure manner. An engine of the distribution network receives content created utilizing an application having different customers and partners. The engine also receives: a first identifier indicating a customer of the application with which a tenant is associated, and a second identifier indicating a partner of the application with which the tenant is associated. The engine references a stored database table to correlate the first identifier and the second identifier. Based upon the first identifier and the second identifier, the engine evaluates whether the tenant is to be provided access to the content. The engine may provide the tenant with the content according to an access right determined from the first identifier and the second identifier. Certain embodiments may find particular use disseminating content to new tenants of a customer, based upon prior distribution to other tenants of that customer.

Abstract: Methods, systems, and computer-readable storage media for receiving, by an analytics content network (ACN), a configuration request through a tenant configuration application programming interface (TC-API) of a plurality of APIs, the configuration request including an identifier that uniquely identifies an analytics system tenant that is embedded in an application tenant within a customer landscape, the ACN distributing analytics content to multiple customer landscapes, determining, by the ACN, one or more analytics content that is to be distributed to the analytics system tenant at least partially based on the identifier, providing, by the ACN, a content package that includes the one or more analytics content within an API payload for response to the request, and transmitting, by the ACN, a response to the request through the TC-API, the response comprising the API payload.

Abstract: Methods and apparatus are disclosed for serializing software objects for loading onto a cloud-hosted tenant, or for other serialized operations. Nodes and edges of a directed graph represent respective software objects and the dependencies among the software objects. A search for strongly connected components reveals cyclic dependencies. Each strongly connected component can be replaced by a contracted node to obtain a condensation of the original directed graph. A topological ordering can be determined for the condensation, and the software objects can be processed or loaded according to the topological ordering. Such ordering provides that software objects of a strongly connected component are processed consecutively while, for all other dependencies, a prerequisite object is processed (loaded) before its dependent object(s). Examples of SAP Analytics Cloud and Data Warehouse Cloud are provided. Exemplary, push and pull loading procedures, topological ordering, and validation are disclosed.

Abstract: Methods and apparatus are disclosed for serializing software objects for loading onto a cloud-hosted tenant, or for other serialized operations. Nodes and edges of a directed graph represent respective software objects and the dependencies among the software objects. A search for strongly connected components reveals cyclic dependencies. Each strongly connected component can be replaced by a contracted node to obtain a condensation of the original directed graph. A topological ordering can be determined for the condensation, and the software objects can be processed or loaded according to the topological ordering. Such ordering provides that software objects of a strongly connected component are processed consecutively while, for all other dependencies, a prerequisite object is processed (loaded) before its dependent object(s). Examples of SAP Analytics Cloud and Data Warehouse Cloud are provided. Exemplary, push and pull loading procedures, topological ordering, and validation are disclosed.

Abstract: A distribution network may efficiently communicate items/item details in a private manner, with different access rights tailored to various tenants residing within a same or different customer landscape. A first input comprising a flat file with items/item details, is received. A second input comprising permissions entries for per-user, per-item direct access rights (e.g., view, read, write, delete) is also received. The first and second inputs are recursively processed to find nearest ancestors having the direct access rights, with a hash maintained including the nearest ancestors. An effective permitted structure (e.g., tree comprising root and leaf nodes) is generated by recursively adding descendant items having inherited access rights, to the nearest ancestors. Ultimately, descendant item(s) are privately distributed to a user with an access right according to the effective permitted structure. Embodiments may be particularly suited to the private distribution of analytics content (e.g.

Abstract: A distribution network may efficiently communicate items/item details in a private manner, with different access rights tailored to various tenants residing within a same or different customer landscape. A first input comprising a flat file with items/item details, is received. A second input comprising permissions entries for per-user, per-item direct access rights (e.g., view, read, write, delete) is also received. The first and second inputs are recursively processed to find nearest ancestors having the direct access rights, with a hash maintained including the nearest ancestors. An effective permitted structure (e.g., tree comprising root and leaf nodes) is generated by recursively adding descendant items having inherited access rights, to the nearest ancestors. Ultimately, descendant item(s) are privately distributed to a user with an access right according to the effective permitted structure. Embodiments may be particularly suited to the private distribution of analytics content (e.g.

Abstract: A distribution network communicates content to tenant groups in a secure manner. An engine of the distribution network receives content created utilizing an application having different customers and partners. The engine also receives: a first identifier indicating a customer of the application with which a tenant is associated, and a second identifier indicating a partner of the application with which the tenant is associated. The engine references a stored database table to correlate the first identifier and the second identifier. Based upon the first identifier and the second identifier, the engine evaluates whether the tenant is to be provided access to the content. The engine may provide the tenant with the content according to an access right determined from the first identifier and the second identifier. Certain embodiments may find particular use disseminating content to new tenants of a customer, based upon prior distribution to other tenants of that customer.

Abstract: Embodiments relate to file-based sharing of content through a content distribution network. A request is received from a source to disseminate content to a target consumer. The request does not include target consumer URL information. Based upon the request, content metadata stored in a database with content data, is referenced to generate a file including metadata comprising a portion of the content metadata. The file does not include the content data. The file is exported to the source. The source delivers the file to the target consumer through a communication channel (e.g., shared folder, email) located outside of the distribution network. The file is imported from the target consumer. The metadata of the file is processed to examine its integrity. The metadata may comprise a key for reference during this process. Upon confirming integrity of the file, the content data and the content metadata are distributed to the target consumer.

Abstract: Methods, systems, and computer-readable storage media for receiving, by an analytics content network (ACN), a configuration request through a tenant configuration application programming interface (TC-API) of a plurality of APIs, the configuration request including an identifier that uniquely identifies an analytics system tenant that is embedded in an application tenant within a customer landscape, the ACN distributing analytics content to multiple customer landscapes, determining, by the ACN, one or more analytics content that is to be distributed to the analytics system tenant at least partially based on the identifier, providing, by the ACN, a content package that includes the one or more analytics content within an API payload for response to the request, and transmitting, by the ACN, a response to the request through the TC-API, the response comprising the API payload.

Abstract: A system includes identification of dimension filters associated with a visualization, identification, from the identified dimension filters, of nested dimension filters associated with a first dimension, generation of a composite filter based on the identified nested dimension filters, transmission of a query to a data source, the query including the composite filter, reception of a result set based on the query from the data source, and display of the visualization presenting the result set on the display.

Abstract: A system includes identification of dimension filters associated with a visualization, identification, from the identified dimension filters, of nested dimension filters associated with a first dimension, generation of a composite filter based on the identified nested dimension filters, transmission of a query to a data source, the query including the composite filter, reception of a result set based on the query from the data source, and display of the visualization presenting the result set on the display.

Abstract: In in-memory workspace management, a request is received from a user to open a document. It is determined whether the document is opened. Upon determining that the document is already opened, an existing workspace instance corresponding to the opened document is shared with the user. A mapping between the workspace request identifier and a workspace identifier is maintained in a workspace map. A reference count mapped to the workspace identifier is incremented since the existing workspace instance is shared with the user. It is determined whether the document is edited. The shared workspace instance is discontinued from sharing and is forked to create a new workspace instance for editing. The mapping between workspace request identifier and workspace identifier is removed from the workspace map. The reference count map is updated to decrement the reference count corresponding to the workspace identifier.

Abstract: Various embodiments of systems and methods for performing predictive analysis are described herein. In one aspect, the method includes receiving a command for publishing a chain comprising a plurality of components connected together to perform predictive analysis. Based upon the command, a plurality of procedures corresponding to the plurality of components of the chain is generated. The generated procedures are integrated according to an order of connectivity of the components within the chain. A database object including the integrated procedures is generated. The database object is stored within a database. The stored database object is executable for performing predictive analysis.

Abstract: A workflow execution framework is generated to execute a received workflow. The workflow is semantically analyzed to determine workflow chain and associated workflow components. To execute the workflow chain, a terminal component in the workflow chain and a corresponding sequential hierarchy of the workflow components are detected. A result descriptor of a data source component corresponding to the terminal component is computed and stored in an execution state table. Result descriptors are computed for the workflow components succeeding the data source component in the sequential hierarchy and are stored in the execution state table. Upon detecting a dataflow between the data source component and one of the succeeding workflow components, data along each row of the execution state table is extracted to process the one of the succeeding workflow components. The workflow is executed by processing the workflow components associated with the workflow chain, thereby executing the workflow chain.