公开(公告)号：US20170061559A1

公开(公告)日：2017-03-02

申请号：US14842568

申请日：2015-09-01

Applicant: SAP SE

Inventor： Christoph Ehrhardt ,  Boris Aljancic ,  Frank Barthel

IPC: G06Q50/18 ,  G06Q50/00 ,  G06F21/62

CPC classification number: G06Q50/18 ,  G06F21/6254 ,  G06Q50/01

Abstract: Embodiments provide a control framework that fosters the integration of information handling systems with data from internal and/or external sources, compliant with various requirements (e.g., regulatory-based, arising from network terms and conditions). A configuration platform addresses data protection and privacy concerns, allowing flexible definition and application of rules. Rules may consider factors such as data source, national jurisdiction, and purpose of the end user. The rules may address whether/how consent is to be obtained, possible anonymization of personal data, and other issues. Once defined, the framework rules govern processing personal data obtained from internal and/or external sources in a legally compliant manner. Rules and/or configurations may be stored centrally (e.g., locally on premises, remotely in the cloud), with each business process requesting a particular valid rule set when processing personal data. A configuration interface allows the enterprise to dynamically comply with data privacy obligations supported by a (context-sensitive) rules engine.

Abstract translation: 实施例提供了一种控制框架，其促进信息处理系统与来自内部和/或外部来源的数据的整合，其符合各种要求（例如，基于监管，来自网络条款和条件）。 配置平台解决数据保护和隐私问题，允许灵活定义和应用规则。 规则可以考虑最终用户的数据源，国家管辖权和目的等因素。 这些规则可以解决是否/如何获得同意，可能的匿名化个人数据和其他问题。 一旦定义，框架规则就以合法的方式管理从内部和/或外部来源获取的个人数据。 规则和/或配置可以集中存储（例如，在本地的本地，在云中远程），每个业务处理在处理个人数据时请求特定的有效规则集。 配置界面允许企业动态地遵守（上下文相关）规则引擎支持的数据隐私义务。

公开(公告)号：US20240386356A1

公开(公告)日：2024-11-21

申请号：US18665299

申请日：2024-05-15

Applicant: SAP SE

Inventor： Miklos Zoltan Szabo ,  Matthias Saettele ,  Jochen Mayerle ,  Christoph Ehrhardt ,  Stefan Feickert ,  Bastian Distler ,  Christoph Ernst ,  Edrilan Berisha ,  Florence Jungnickel

IPC: G06Q10/0637 ,  G06F16/18

Abstract: Various examples are directed to systems and methods of using a database management system (DBMS) to post a transaction. An enterprise resource planning (ERP) application may receive first transaction data associated with a first transaction including acquisition of a first component of a first component type. The first transaction data may describe an indicator of the first component, a cost of the first component of a first component type, and a first environmental metric associated with the first component. The ERP application may write a first transaction entry to a universal journal table of the DBMS, the first transaction entry comprising a description of the first transaction, and a component breakdown key. The ERP application may also write a first component breakdown entry to a component breakdown table of the DBMS.