PARSER FOR GENERATING FINANCIAL MANAGER APPLICATION RULES

• US 20100131399A1
• Filed: 03/05/2009
• Published: 05/27/2010
• Est. Priority Date: 11/27/2008
• Status: Abandoned Application

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: George, Dileep, Madasamy, Sivabalarajan, Bhadke, Rojal, Anand, Dheeraj, Jagini, Samatha, Tungaturthy, Prasad
• Application Number:
  US12/398,385
• Publication Number:
  US 20100131399A1
• Time in Patent Office: Days
• US Class Current: 705/35
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

In one embodiment, one or more business rules are received from a calculation manager. A calculation manager allows a user to generate the rules using a graphical format. The business rules are generated in a mark-up language, such as extensible mark-up language (XML). Data for the one or more business rules is loaded into a data structure for parsing. Data for the nodes may be read in by a token parser. When the token parser encounters a token, a business decision is determined. The token parser analyzes the data for the node to determine how to convert it to a business rule for the financial manager. This process continues as nodes are read in and with each token that is encountered, a business decision is determined until the rule for the financial manager is generated.

Claims

1. A method comprising:

receiving one or more business rules generated from a graphical format of a calculation manager, the one or more business rules generated in a first language and first format;

loading data for the one or more business rules into a structure for parsing;

reading data for a node in the set of nodes of the structure until data in the node is encountered in which a business decision is needed; and

parsing data read for the node to facilitate conversion of the parsed data to a financial manager rule in a second format and a second language compatible with a financial manager based on a conversion rule associated with the business decision.

2. The method of claim 1, wherein reading and parsing comprising:

reading a first node of the structure;

determining if a token is encountered;

if a token is encountered, determining that the business decision is needed.

3. The method of claim 2, further comprising:

if the token is not encountered, reading additional data for the node until a token is encountered.

4. The method of claim 1, wherein the data stored for the data structure is a ruleset, wherein the ruleset is parsed based on rules the ruleset is referring to.

5. The method of claim 4, wherein the data stored for the data structure is a rule, the rule referring to a component.

6. The method of claim 5, wherein the data stored for the data structure is a component.

7. The method of claim 1, wherein the first language is extensible markup language and the second language is a scripting language.

8. The method of claim 1, wherein the first language is nodal and the calculation manager rules are broken into nodes and stored in the data structure, wherein the nodes store rulesets, rules, and components.

9. The method of claim 1, further comprising:

inserting a timer statement into the financial manager rules, the timer statement allowing a time to be recorded when the financial manager rules are executed by the financial manager, the time recorded indicating a time taken to perform a financial transaction.

10. The method of claim 1, further comprising:

determining a disable statement in the calculation manager rules;

inserting a comment statement in one of the converted financial manager rules, the comment statement disabling execution of the one of the converted financial manager rules.

11. The method of claim 1, further comprising:

storing status of the parsing in a call stack;

determining when an error occurs during parsing; and

outputting the call stack, the call stack including information on the status of the parsing before the error occurred.

12. A computer-readable medium comprising encoded logic for execution by the one or more processors, the logic when executed operable to:

receive one or more business rules generated from a graphical format of a calculation manager, the one or more business rules generated in a first language and first format;

load data for the one or more business rules into a structure for parsing;

read data for a node in the set of nodes of the structure until data in the node is encountered in which a business decision is needed; and

parse data read for the node to facilitate conversion of the parsed data to a financial manager rule in a second format and a second language compatible with a financial manager based on a conversion rule associated with the business decision.

13. The computer-readable medium of claim 12, wherein logic operable to read and parse comprising logic operable to:

read a first node of the structure;

determine if a token is encountered;

determine that the business decision is needed if a token is encountered.

14. The computer-readable medium of claim 13, wherein the logic when executed is further operable to read additional data for the node until a token is encountered if the token is not encountered.

15. The computer-readable medium of claim 12, wherein the first language is nodal and the calculation manager rules are broken into nodes and stored in the data structure, wherein the nodes store rulesets, rules, and components.

16. The computer-readable medium of claim 12, wherein the logic when executed is further operable to insert a timer statement into the financial manager rules, the timer statement allowing a time to be recorded when the financial manager rules are executed by the financial manager, the time recorded indicating a time taken to perform a financial transaction.

17. The computer-readable medium of claim 12, wherein the logic when executed is further operable to:

determine a disable statement in the calculation manager rules;

insert a comment statement in one of the converted financial manager rules, the comment statement disabling execution of the one of the converted financial manager rules.

18. The computer-readable medium of claim 12, wherein the logic when executed is further operable to:

store status of the parsing in a call stack;

determine when an error occurs during parsing; and

output the call stack, the call stack including information on the status of the parsing before the error occurred.

19. The computer-readable medium of claim 12, wherein the data stored for the data structure comprises a ruleset, rule, and component.

20. An apparatus comprising:

one or more processors; and

logic encoded in one or more tangible media for execution by the one or more processors and when executed operable to;

receive one or more business rules generated from a graphical format of a calculation manager, the one or more business rules generated in a first language and first format;

load data for the one or more business rules into a structure for parsing;

read data for a node in the set of nodes of the structure until data in the node is encountered in which a business decision is needed; and

parse data read for the node to facilitate conversion of the parsed data to a financial manager rule in a second format and a second language compatible with a financial manager based on a conversion rule associated with the business decision.