Abstract: Techniques to automatically generate invoices for contracts, each of which may include any number of line items. Each contract line item may be associated with (1) a particular invoice plan that defines one or more applicable billing types (e.g., for non-recurring, recurring, and use charges) and any adjustments to the total billed amount, (2) a particular invoicing schedule that defines the timing for the invoice generation, (3) a particular account to which invoices are addressed, and (4) a flag to selectively enable automatic invoice generation. An invoice engine automatically generates invoices for a set of one or more contracts by processing each enabled line item of each contract based on the associated invoice plan and invoicing schedule to generate a set of one or more invoice line items for the contract line item. All invoice line items for each account are aggregated into an invoice for the account.

Abstract: Techniques to generate invoices for “events” (e.g., activities, orders, and so on) and taking into account applicable entitlements. The events are for actions and/or transactions to be performed, and may be related to contracts having entitlements that may specify special pricing for the events. An entitlement may define what event items are covered (e.g., time, expenses, parts), and the amount that is covered and the applicable discounts for each event item. To generate invoices for the events, contracts applicable to the events are initially determined and any entitlements that cover the events are identified. An original invoice amount for each event may be initially determined based on a standard pricing scheme (e.g., based on standard Price and/or Rate Lists) for this type of event. A revised invoice amount and discounts (if any) may then be determined for the event based on the applicable entitlements (if any).

Abstract: Techniques to facilitate the creation of contracts and to automatically instantiate entitlements into contracts. A number of entitlement templates may be created for various entitlements. Each entitlement template is typically defined to include certain specifically defined entitlements. The entitlement templates may further be associated with products. A contract may thereafter be formed having any number of line items for one or more products and/or assets. Upon execution of the contract, an agreement is formed and the entitlements (if any) for each product/asset included in the contract may be instantiated (e.g., via a button on a screen). Upon instantiation of the entitlements into the contract, the covered products/assets become entitled and can thereafter receive the entitlements defined in the templates associated with the products/assets.

Abstract: A method and system for collecting, storing, and processing automatic identification code information includes receiving automatic identification code information and parsing it based on stored definitions for automatic identification codes and/or automatic identification code standards. Various data configurations may be used to store definitions and to facilitate parsing of raw automatic identification code data. For example, a first component may be used for generally defining one or more automatic identification code standards and a second component may be used for detailed information regarding code definitions, such as information relating to code segments. In addition, the system may facilitate further processing of parsed automatic identification code information, such as for cycle counting or parts movement of inventory.

Abstract: Techniques to support various operations (e.g., drag-and-drop, stretch) and data manipulation in a browser environment, e.g., to allow data for an object located in one part of a document (e.g., a webpage) to be associated with another object located in another part of the document. In one design, a document includes at least one applet for at least one display window. Each applet includes at least one browser object representative of an entity for an end application. Each browser object is associated with a respective set of one or more scripts used to facilitate a set of one or more operations (e.g., drag-and-drop, stretch) permitted for the browser object. A data transfer object is generated upon initiation of a selected operation and includes data associated with a source (browser) object. The data transfer object may thereafter be operated on by various target (browser) object to effectuate the selected operation.