DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the
first inventor to file provisions of the AIA .
Response to Arguments
2. The Amendment filed on October 12, 2026 has been entered. The Examiner acknowledges the amendments to claims 1, 8, 15.
Rejections under 35 U.S.C. § 101: Applicant argues that the claims are directed to the operations of a GUI and the placement and type of interactive fields within the GUI as well as how the specific interactive fields interact with the data, and hence the instant claims are analogous to the example in MPEP 2106.04(a)(1) and do not recite an abstract idea. The Examiner disagrees noting that the argument deflects from addressing abstract ideas and instead pursues a display interface example. Abstract ideas are manifest in configuring and storing mapping relationships between records, selection of relationship types between direct and indirect, and pairing field data from the primary table to data in the contract file. Additionally, the processor creates mapping entries between items that associate contract billing object to the billing elements. These abstract ideas are shown in the analysis below.
Applicant additionally argues that improvements directed to a graphical user interface are patent eligible, and since the claims are directed to operations and use of a GUI, and are directed to improvements in computer technology. The Examiner notes that the amendments indicate the use of various features on graphical display applied to mapping enterprise resource planning data to contract records but these appear to be the general linking of GUI elements to the area of tracking financial planning and resource allocation against contractual obligations. No improvement to computer technology is stated or noted in the claims. These arguments are not compelling and the objections based on 35 U.S.C § 101 will not be withdrawn.
Rejections under 35 U.S.C. § 102/103: Applicant’s arguments highlight that the claims are directed to display and operation of a graphical user interface. Included within the claims are particular aspects defining elements of the graphical user interface ("displaying, in the GUI, a field pairing interface comprising a first field corresponding to a data element in the primary table, and a second field corresponding to a data element in the contract file; allowing a user to manually provide data elements to the first field and to the second field fields via one of dropdown menus, auto-complete inputs, and drag-and-drop components; receiving, from the GUI, input values corresponding to the data element in the primary table and data element in the contract file, wherein the input values are the data elements in the first field and in the second field"). Additional arguments point out that the features of the GUI are not present in prior art. The Examiner finds the argument compelling and the rejections to claims 1-20 based on 35 U.S.C. § 102/103 are withdrawn.
Claim Rejections 35 U.S.C. § 101
35 U.S.C. § 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1-20 are rejected under 35 U.S.C. § 101 because the claimed invention is directed
to non-statutory subject matter. The claims, 1-20 are directed to a judicial exception (i.e., law of nature, natural phenomenon, abstract idea) without providing significantly more.
Step 1
Step 1 of the subject matter eligibility analysis per MPEP § 2106.03, required the claims to be a process, machine, manufacture or a composition of matter. Claims 1-20 are directed to a process (method), machine (system), and product/article of manufacture, which are statutory categories of invention.
Step 2A
Claims 1-20 are directed to abstract ideas, as explained below.
Prong one of the Step 2A analysis requires identifying the specific limitation(s) in the claim under examination that the examiner believes recites an abstract idea, and determining whether the identified limitation(s) falls within at least one of the groupings of abstract ideas of mathematical concepts, mental processes, and certain methods of organizing human activity.
Step 2A-Prong 1
The claims recite the following limitations that are directed to abstract ideas, which can be summarized as being directed to a method, the abstract idea, of configuring and mapping transactional records and contracting data in a resource planning environment.
Claim 1 discloses A method for configuring and storing mapping relationships
between transactional records and contract data in an enterprise resource planning ("ERP")
environment, (following rules or instructions, observation, evaluation, judgement, opinion), comprising:
receiving, a selection of a primary table and
responding to selection of the primary table by defining a relationship type; (following rules or instructions, observation, evaluation, judgement, opinion),
receiving, a selection of the relationship type, the relationship type being one of a direct relationship or an indirect relationship; (following rules or instructions, observation, evaluation, judgement, opinion),
in an instance where the relationship type selection is a direct relationship, displaying, a first field corresponding to a data element in the primary table, and a second field corresponding to a data element in the contract file; (following rules or instructions, observation, evaluation, judgement, opinion),
allowing a user to manually provide data elements to the first field and to the second field fields; (following rules or instructions, observation, evaluation, judgement, opinion),
receiving, input values corresponding to the data element in the primary table and data element in the contract file, wherein the input values are the data elements in the first field and in the second field; (following rules or instructions, observation, evaluation, judgement, opinion), and
creating, in the mapping table, a first mapping entry in a mapping table that
associates the value corresponding to the selected field from the primary table with the value corresponding to the selected field from the contract file; (following rules or instructions, observation, evaluation, judgement, opinion), and in an instance where the relationship type selection is an indirect relationship,
displaying, a second field pairing comprising a third field and a fourth field, the third field corresponding to a contract billing object and the fourth field corresponding to a primary table billing element; (following rules or instructions, observation, evaluation, judgement, opinion),
allowing a user to manually provide data elements to the first field and to the second field, (following rules or instructions, observation, evaluation, judgement, opinion),
receiving, user-provided input values for the contract billing object and the primary table billing element; (following rules or instructions, observation, evaluation, judgement, opinion), and
creating, in the mapping table, a second mapping entry in a mapping table that
associates the value corresponding to the contract billing object with the value corresponding to the primary table billing element, (following rules or instructions, observation, evaluation, judgement, opinion),
Additional limitations in the method include wherein the relationship type selection comprises an intercompany relationship type, and wherein creating the second mapping entry comprises: associating a first value corresponding to a delivering company code in the primary table with a second value corresponding to a receiving company code derived from a project or internal customer; (following rules or instructions, observation, evaluation, judgement, opinion), and resolving transactional records representing cross-company postings by identifying entries in the primary table in which the delivering company code and the receiving company code satisfy an intercompany billing condition, (following rules or instructions, observation, evaluation, judgement, opinion – claim 2), where inputs for the direct relationship type are validated by confirming the contract reference and verifying that the table values conform to a predetermined format, (following rules or instructions, observation, evaluation, judgement, opinion – claim 3), and where the mapping table includes an entry type indicator and the entries are stored with a corresponding indicator denoting a direct or indirect relationship type, ((following rules or instructions, observation, evaluation, judgement, opinion – claim 4), and resolving transactional records by lookup of the mapping entry to match a transactional field to a contract identifier, (following rules or instructions, observation, evaluation, judgement, opinion – claim 5), including resolving transactional records using a second mapping entry to map a billing element value to a contract billing object (following rules or instructions, observation, evaluation, judgement, opinion – claim 6), and generating a transaction record that includes an identifier of the contract item and mapping method used, (following rules or instructions, observation, evaluation, judgement, opinion – claim 7).
Each of these claimed limitations involve organizing human activity by following rules or instructions, and employ mental processes involving observation, evaluation, judgement, and opinion.
Claims 8-20 recite similar abstract ideas as those identified with respect to claims 1-7.
Thus, the concepts set forth in claims 1-20 recite abstract ideas.
Step 2A-Prong 2
As per MPEP § 2106.04, while the claims 1-20 recite additional limitations which are hardware or software elements such as a graphical user interface ("GUI"), displaying selectable options, a field pairing interface comprising, comprising a first field corresponding to a data element in the primary table, and a second field corresponding to a data element in the contract file;
via one of dropdown menus, auto-complete inputs, and drag-and-drop components, runtime processing applying a lookup operation that uses the first mapping entry to match a transactional field value to a contract item identifier, runtime processing applying a dereferencing operation that uses the second mapping entry to map a billing element value in the transactional record to a contract billing object, a non-transitory computer-readable medium containing instructions when executed by a hardware-based processor, causes the processor to perform stages for configuring and storing mapping relationships, resolving, during runtime processing, transactional records representing cross-company postings by identifying entries in the primary table in which the delivering company code and the receiving company code satisfy an intercompany billing condition, resolving, during runtime processing, transactional records in the primary table by applying a dereferencing operation that uses the second mapping entry to map a billing element value in the transactional record to a contract billing object, a system for configuring and storing mapping relationships between transactional records and contract data in an enterprise resource planning ("ERP") environment, one processor that executes the instructions to perform stages,
these limitations are not sufficient to qualify as a practical application being recited in the claims along with the abstract ideas since these elements are invoked as tools to apply the instructions of the abstract ideas in a specific technological environment. The mere application of an abstract idea in a particular technological environment and merely limiting the use of an abstract idea to a particular technological field do not integrate an abstract idea into a practical application (MPEP § 2106.05 (f) & (h)).
Evaluated individually, the additional elements do not integrate the identified abstract ideas into a practical application. Evaluating the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually.
The claims do not amount to a “practical application” of the abstract idea because they neither (1) recite any improvements to another technology or technical field; (2) recite any improvements to the functioning of the computer itself; (3) apply the judicial exception with, or by use of, a particular machine; (4) effect a transformation or reduction of a particular article to a different state or thing; (5) provide other meaningful limitations beyond generally linking the use of the judicial exception to a particular technological environment.
Accordingly, claims 1-20 are directed to abstract ideas.
Step 2B
Claims 1-20 do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the additional elements when considered both individually and as an ordered combination, do not amount to significantly more than the abstract idea.
The analysis above describes how the claims recite the additional elements beyond those identified above as being directed to an abstract idea, as well as why identified judicial exception(s) are not integrated into a practical application. These findings are hereby incorporated into the analysis of the additional elements when considered both individually and in combination.
For the reasons provided in the analysis in Step 2A, Prong 1, evaluated individually, the additional elements do not amount to significantly more than a judicial exception. Thus, taken alone, the additional elements do not amount to significantly more than a judicial exception.
Evaluating the claim limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually. In addition to the factors discussed regarding Step 2A, prong two, there is no indication that the combination of elements improves the functioning of a computer or improves any other technology. Their collective functions merely amount to instructions to implement the identified abstract ideas on a computer.
Therefore, since there are no limitations in the claims 1-20 that transform the exception into a patent eligible application such that the claims amount to significantly more than the exception itself, the claims are directed to non-statutory subject matter and are rejected under 35 U.S.C. § 101.
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as
set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Claims 1-20 remain rejected under 35 U.S.C. § 101.
Claims 1, 8, and 15, are not rejected by prior art under 35 U.S.C. § 103.
Dependent claims 2-7, 9-14, and 16-20 are not rejected because of their inherent dependency on claims 1, 8, and 15.
The closest prior art to the invention includes Kennis, (US 20050209876 A1), “Methods And Systems For Transaction Compliance Monitoring,” and Scott, (US 8041613 B2), “Systems, Applications and Products in Data Processing for Cross Dock.”
None of the prior art alone or in combination teach the claimed invention as recited in this claim wherein the novelty is in the combination of all the limitations and not in a single limitation.
Regarding claim 1, Kennis teaches similar capabilities in the enterprise resource planning field; A method for configuring and storing mapping relationships between transactional records and contract data in an enterprise resource planning ("ERP") environment, comprising: (An automated transaction integrity monitoring system (100) operative to monitor electronic transactions of an enterprise, [Abstract],
receiving, from a graphical user interface ("GUI"), a selection of a primary table, and responding to selection of the primary table by displaying selectable options for defining a relationship type;
receiving, from the GUI, a selection of a relationship type, the relationship type being one of a direct relationship or an indirect relationship; (An extractor (140) obtains data from heterogeneous data sources such as enterprise databases. A staging database (155) caches data from the data sources. A mapper (150) maps enterprise data into an enterprise ontology used to express enterprise policies, [Abstract].
Amended claims disclose allowing a user to manually provide data elements to the first field and to the second field fields via one of dropdown menus, auto-complete inputs, and drag-and-drop components; Neither Kennis or Scott teach GUI options or their applications. None of the prior art alone or in combination teaches the claimed invention as recited in claim 1 wherein the novelty is in the combination of all the limitations and not in a single limitation.
Independent claims 8 and 15 are not rejected for reasons similar to those provided for Claim 1. In these claims, the addition of a non-transitory, computer-readable medium or a system comprising a non-transitory, computer-readable medium and at least one processor does not change the rationale for non-rejections of the claims.
The prior art made of record and not relied upon is considered pertinent to
applicant's disclosure or directed to the state of the art is listed on the enclosed PTO-892.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MICHAEL BOROWSKI whose telephone number is (703)756-1822, and email is michael.borowski@uspto.gov. The examiner can normally be reached M-F 8-4:30.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Jerry O’Connor, can be reached on (571) 272-6787. The fax phone number for the organization where this application or proceeding is assigned is (571) 273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at (866) 217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call (800) 786-9199 (IN USA OR CANADA) or (571) 272-1000.
/MB/
Patent Examiner, Art Unit 3624
/MEHMET YESILDAG/Primary Examiner, Art Unit 3624