Oracle International Corporation

Suman Guha

Shibhu Nambiar

David Scott Merrill

Margaret Sue Lloyd

Kim E Powell

Sanjay Singh Thakur

Kalyana Chakravarthy Dande

Neil Ramsay

Karthik Natarajan

Shyam Sundar Santhanam

Karlay Tan

Snigdha Dharmavaram

Mayukh Bhaowal

Lee Hian Quek

Lee-Hian Quek

Angela Xian

Rohit Lobo Prabhu

Rohit Lobo

Keng Lap Ao

Manjula Evans

Amol Tiwari

Anurag Khanna

Valerie Jeanne Dubois

Chun Yu Tsui

A system is provided that dynamically determines a sold-to legal entity associated with an electronic financial document. The system receives a request to generate the electronic financial document and qualifiers including attributes of the electronic financial document. The system further selects a supply chain financial orchestration flow based on programmable business rules and the qualifiers. The system further selects a sold-to legal entity that is defined by the selected supply chain financial orchestration flow. The system further generated the electronic financial document comprising the selected sold-to legal entity.

System that dynamically determines sold-to legal entities

A document management system creates a copy of a first purchase document when a request to modify the first purchase document is received. The copy of the first purchase document is a second purchase document. The system receives modifications for the second purchase document. The system requests approval of the modifications of the second purchase document. The system receives approval of the modifications of the second purchase document. The system integrates the modifications of the second purchase document into the first purchase document. The first purchase document remains active at least after the second purchase document is created and before the receiving approval.

Document management system

A method of managing software design specifications with functional rule versioning may include storing references to a plurality of software components in a database system, and storing references to a plurality of functional rules in the database system. In some embodiments, the functional rules may define behaviors that may be assigned to the plurality of software components. The method may also include receiving a selection of one or more software components from the plurality of software components. The one or more software components may define a software product. The method may additionally include receiving assignments of the plurality of functional rules to the one or more software components, and providing an interface for navigating through the one or more software components and editing the assignments.

Functional rule and component storage

A method of implementing a packet transport protocol between a source and a receiver may include receiving input from a source system including data fields indicating whether the source system will allow packet transport to be handled by the receiver. The method may also include receiving input indicating that a packet from the source is required by the receiver. The input can include a first timing requirement indicating at time when the packet is required at the receiver, and a selection between first and second protocols that mandate, respectively, that packet transport is handled by the receiver in the first protocol and by the source in the second protocol. The method may also include determining, based on the data fields, whether the source will allow use of the selected protocol. The method may also include transmitting a request for the packet, in which the request includes a second timing requirement.

Packet transport protocol processing

A method of modifying a requisition within approval and budgetary constraints by a procurement organization may include receiving the requisition from a requesting organization, where the requisition may comprise one or more lines, each having been approved by the requesting organization. The method may also include receiving a change to be applied to a first line associated with a first budget allocation, where the change may be received from a buyer in the procurement organization, and the change may be associated with a second budget allocation. The method may additionally include determining that the change violates a threshold, sending the change to the requesting organization for a second approval, receiving, from the requesting organization, an indication as to whether the second approval is granted, and creating a purchase order based on the indication as to whether the second approval is granted.

Approval system for buyer-initiated requisition modifications

In one embodiment, controls for an agreement from a supplier are set up. The agreement includes a plurality of items for purchase. The controls may be used to determine a degree of touchlessness in the buying of the items. The controls may be configured at the agreement level. A requisition from a requester for a target item is received. In one embodiment, sourcing rules and ASLs may be searched to determine if a sourcing rule and ASL applies to the item. If so, then the sourcing rule and ASL may be used to determine an agreement. If a sourcing rule and ASL do not apply, agreements can be searched to determine an agreement for the target item. Once the agreement is determined, controls are determined from the agreement, where the controls govern the plurality of items of the agreement.

Simplified configuration of touchless buying

A method, system, and computer program product for providing document security for procurement agents. The method commences by establishing user authentication credentials for at least two procurement agents. Then, initially granting limited access to a first set of documents where the first set of documents is initially under control of the first procurement agent (and initially inaccessible by the second procurement agent), and initially granting limited access to a second set of documents, where the second set of documents is initially under control of the second procurement agent. A procurement application receives an access request from the first user to access a document from among the second set of documents, causing the procurement application to confirm the first user authentication credentials, retrieve the document access rule for the first procurement agent, and allow/deny access by the first user to the document from among the second set of documents.

Flexible document security for procurement agents

One embodiment of the invention includes a computer-implemented method for supplier update of a procurement system. The method includes providing a customizable procurement entity to a supplier, receiving a modified procurement entity from the supplier, wherein the modified procurement entity comprises an update made by the supplier to the customizable procurement entity, reviewing and approving the modified procurement entity, and publishing the modified procurement entity to the procurement system.

Enhanced supplier catalog collaboration

Particular embodiments provide for a user configurable purchase order template. A list of attributes for a purchase order template may be created and output to a user. The user may then select which attributes in the list are internal attributes or external attributes. After the purchase order document has been approved by the supplier and the purchaser, changes may be necessary. When a change is desired, the system determines if the changed attribute is an external attribute or an internal attribute. If the changed attribute is an external attribute, the external entity may be contacted for approving the change. After the external entity has approved the change, the purchase order may be amended. If the changed attribute is an internal attribute, the attribute may be changed without contacting the external entity. If the change is an internal change, then the purchase order may not be amended, but an internal change relating to the purchase order may be made.

Change order template for purchase order document amendment

A computer-readable medium, computer-implemented method, and apparatus are provided. In one embodiment, a change order for a purchasing document is created, and one or more attributes of the change order are modified. Approval of the change order is submitted and approved, and a change type of the change order is determined. When the change type is external, acknowledgment of the change order is requested and a revision number attribute of the purchasing document is incremented. The purchasing document is updated with the change order and the change order is archived.

Growing community of inventors

Fremont, CA, United States of America

Suman Guha