Patent application number | Description | Published |
20090137276 | SIMULTANEOUS INTERFACE USE - In a portable data carrier ( | 05-28-2009 |
20090199206 | DATA STORAGE MEDIUM AND METHOD FOR CONTACTLESS COMMUNICATION BETWEEN THE DATA STORAGE MEDIUM AND A READER - The present invention relates to a method and an accordingly set tip data carrier for contactless, in particular parallel, communication of a reading device ( | 08-06-2009 |
20100108772 | PORTABLE DATA CARRIER - A portable data carrier ( | 05-06-2010 |
20140043145 | DATA STORAGE MEDIUM AND METHOD FOR CONTACTLESS COMMUNICATION BETWEEN THE DATA STORAGE MEDIUM AND A READER - A method and a data carrier for contactless communication of a reading device with at least two communication-ready applications located on a portable data carrier. A first communication-readiness signal is generated for a first application and sent to the reading device, the signal having a first identification number that is assigned to the first application and indicates to the reading device the communication readiness of said first application, and a second communication-readiness signal is generated and sent for a second application, the second signal having a second identification number different from the first identification number, which is assigned to said second application and indicates to the reading device the communication readiness of the second application. The identification numbers simulate for the reading device the communication readiness of a data carrier in each case. The reading device thus has the impression of communicating with applications of two separate data carriers. | 02-13-2014 |
20140082247 | Method for the Data Exchange Between a Terminal and a Chip Card - A method includes exchanging data between a chip card and a terminal in a contact-based manner via a contact field. The method comprises the steps of: activating a first contact assignment in response to a first communication protocol present on the contact field and occupying a first part of contact surfaces of the contact field; recognizing a change of the communication protocol from a first communication protocol to a second communication protocol with a protocol recognition unit in the chip card; and activating a second contact assignment in response to the recognized second communication protocol occupying a second part of contact surfaces of the contact field. The first and the second part of contact surfaces of the contact field are selected from an ISO-7816-2 contact field having a maximum of six contact surfaces and the second communication protocol requires at least two data lines. | 03-20-2014 |
Patent application number | Description | Published |
20080262881 | LOGICALLY CENTRALIZED SCRAP MANAGEMENT USING PLANNING OPERATIONS - The present disclosure relates to methods, systems, and software for processing or otherwise managing scrap information in a business application. For example, the software can instantiate a planning business object using production model data for production activities. The business object data and scrap information may be used to calculate requirements for a production planning model. The calculations may include adding an activity yield to activity scrap and fixed resource scrap to generate a component quantity. The component quantity can be multiplied by a component scrap ratio to generate additional component requirements. The component quantity may be added to the additional component requirements to determine a total quantity. | 10-23-2008 |
20090171736 | METHOD AND SYSTEM FOR CENTRALIZED MANAGEMENT OF SOURCES OF SUPPLY - Methods, systems, and software for determining sources of supply are provided. The system for determining sources of supply is centralized so as to be accessible to a plurality of clients. Sources of supply may be determined and the results prioritized according to user defined criteria. Specifically, the system may offer or facilitate a reusable, centralized service that can data mine sources of supply, which are stored in a business object. These sources of supply may include transportation lane, purchase contract, scheduling agreement, material costing, and any other suitable sources of supply. In some cases, this example system can assign priorities to centralized sources of supply that may help make decisions easier for the planner. | 07-02-2009 |
20100070556 | Architectural Design for Data Migration Application Software - Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing data migration. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include a Product Property Management process component, a Production Model Management process component, a Business Partner Data Management process component, a Product Data Maintenance process component, an Installed Base Data Management process component, a Price Master Data Management process component, an Identity Management process component, an Engineering Change Processing process component, a Migration Data Dispatching process component, and several other process components. | 03-18-2010 |
20110307353 | Managing Consistent Interfaces for Goods Tag, Production Bill of Material Hierarchy, and Release Order Template Business Objects across Heterogeneous Systems - 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 a goods tag, a production bill of material hierarchy, and/or a release order template business object. | 12-15-2011 |
20120016894 | SOLUTION-SPECIFIC BUSINESS OBJECT VIEW - A computer-implemented system may include one or more storage devices storing first metadata defining an instance of a first metaobject, second metadata defining an instance of a solution supplement metaobject, wherein the second metadata comprises annotations to the first metadata, and wherein the first metaobject and the solution supplement metaobject are instances of a meta-metaobject. Also stored is executable program code of a service to determine merged metadata based on the first metadata and the annotations to the first metadata. A processor is included to execute the executable program code. | 01-19-2012 |
20140026114 | LAYERING OF BUSINESS OBJECT MODELS VIA EXTENSION TECHNIQUES - An extension node can be defined in a second layer of a software architecture for a first business object existing in a first layer and originally having an association with a second business object that is also in the first layer. The extension node can be defined to have an association with the second business object existing in a second layer of the software architecture. The association of the second business object can be altered from the first business object to the extension node so that at run time, metadata defining one or more nodes of the first business object and the extension node can be read from a metadata repository and a run time version of the first business object can be constructed at run time in a run time business object load based on the metadata. | 01-23-2014 |
20140157154 | MANAGING BUSINESS OBJECTS - In accordance with aspects of the disclosure, a system and methods are provided for managing business objects in memory. The system and methods may be provided for defining a context of one or more input parameters of data used to determine one or more properties of one or more business objects, defining one or more rules associated with the one or more properties of each business object, and generating a metadata model for each business object based on the context of the one or more input parameters of each business object and the one or more rules associated with the one or more properties of each business object. | 06-05-2014 |
20140164284 | Business Object Data Structures with Node Keys - Data is received that characterizes a business object that includes a plurality of nodes each having at least one element, at least one of the nodes comprising at least one node key that in turn identifies at least one of element of the corresponding node. At least a portion of the received data is persisted into at least one database table using the at least one node key to define a structure of the at least one database table. Thereafter, the business object can be instantiated using the at least one database table. Related apparatus, systems, techniques and articles are also described. | 06-12-2014 |
20140172895 | Modeled Associations for Business Object Data Structures - A service request to execute an operation on a business object is received. Thereafter, a metadata repository is polled to obtain a modeled association corresponding to the service request. The modeled association involves at least one node of the business object. The at least one node of the business object is then called using the modeled association to respond to the service request. Related apparatus, systems, techniques and articles are also described. | 06-19-2014 |
20140172918 | Role Based Access Management for Business Object Data Structures - A service request from a user is received to execute an operation on an instance of a business object. Thereafter, an access control check is performed to confirm whether the user is allowed to execute the requested operation on a type of business object corresponding to the business object specified and based on an access group associated with the user. Subsequently, the user is either provided with access to the instance of the business object to execute the operation if the access control check confirms that the user is allowed to execute the operation on the instance of the business object, or prevented from accessing the instance of the business object to execute the operation on the instance of the business object. Related apparatus, systems, techniques and articles are also described. Related apparatus, systems, techniques and articles are also described. | 06-19-2014 |