Method for generating documents using layer-specific inheritance rules

• US 7,664,737 B2
• Filed: 05/31/2005
• Issued: 02/16/2010
• Est. Priority Date: 05/31/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Yospe, Nathan F., Brookler, David E., Weinberg, Paul N., Sullivan, Dave L., Endo, Richard T., Tinari, Philip A.
• Primary Examiner(s): Vital; Pierre M
• Assistant Examiner(s): Obisesan; Augustine
• Application Number:
  US11/141,997
• Publication Number:
  US 20060271523A1
• Time in Patent Office: 1,722 Days
• Field of Search: 707/1, 707/3, 707/100
• US Class Current: 707/786
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/131 Fragmentation of text files, e.g. creating reusable text-blocks; Linking to fragments, e.g. using XInclude; Namespaces
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71

Abstract

Audience specific document targeted at a particular media type are generated by accessing data from an audience hierarchy. When obtaining a data value for a particular audience, if that value does not exist for that audience then the audience hierarchy may be utilized to find the data value for an inherited audience. By adding regional, cultural or regulatory subdivisions within the audience hierarchy and inheriting large portions of existing audience specific data entries, a large number of audience specific documents may be generated with a minimal amount of data entry required. Audiences may be specified in a given order for traversal within the hierarchy and displayed in a data entry and editing application utilizing visual characteristics to inform a user if the value for a particular piece of data is inherited from another layer or utilized from the particular layer in use. Audience specific documents may be masked and accessed by payment.

Claims

1. A method for generating documents using layer-specific inheritance rules using a computer system, said method comprising:

constructing a main data table for said document that does not require altering in any way in order to add support for a new audience;

constructing a data attribute table that contains audience specific names for at least some fields in said main data table;

constructing an audience order table that contains the next audience identifier to use in finding a suitable value by inheritance;

obtaining a new audience identifier associated with a new audience;

querying a user for a new audience order associated with said new audience identifier,

obtaining said new audience order from said user wherein said new audience order comprises an ordered list of at least one audience identifier and inserting said new audience order into said audience order table;

accepting a subset of data for an audience with respect to another audience into said data attribute table wherein said subset of data is unique with respect to said another audience, wherein new audience data not contained in said subset of data is inherited from at least one other parent audience, wherein said audience and said another audience differ in one of more of language, country, region, regulatory, or cultural designations, wherein said data attribute table is augmented only with those said subset of data values that are unique to said new audience; and

,

generating a document with said subset of data associated with said new audience and with existing data associated with an existing audience when said subset of data is not found in said data attribute table for said new audience.

2. The method of claim 1 further comprising:

determining a stop flag level for said new audience and setting said stop flag level in said audience order table.

3. The method of claim 1 further comprising:

repeating said adding said subset of data until enough data exists to generate a document for said new audience, and wherein not all data attributes need to be updated for said new audience.

4. The method of claim 1 further comprising:

disabling support for said new audience by setting a disable flag for said new audience in an audience table.

5. The method of claim 1 further comprising:

enabling support for said new audience by setting an enable flag for said new audience in an audience table.

20. The method of claim 2, further comprising:

if said stop flag level in said audience order table is set, then obtaining and displaying values lower in an inheritance chain in a data entry program in a different color.

6. A method for generating documents using layer-specific inheritance rules using a computer system, said method comprising:

constructing a main data table for said document that does not require altering in any way in order to add support for a new audience;

constructing a data attribute table that contains audience specific names for at least some fields in said main data table;

constructing an audience order table that contains the next audience identifier to use in finding a suitable value by inheritance;

accepting a subset of data for an audience with respect to another audience into a data attribute table wherein said subset of data is unique with respect to said another audience, wherein new audience data not contained in said subset of data is inherited from at least one other parent audience and wherein said audience and said another audience differ in one or more of language, country, region, regulatory, or cultural designations, wherein said data attribute table is augmented only with those said subset of data values that are unique to said new audience;

obtaining a first audience identifier and setting a current audience identifier to said first audience identifier;

accessing a first field in a main data table in a database;

obtaining a reference identifier from said first field in said main data table;

accessing said data attribute table using said reference identifier and said current audience identifier to obtain a first audience specific value;

determining if said first audience specific value exists in said data attribute table;

providing said first audience specific value if said first audience specific value has been determined to exist via said determining step;

setting said current audience identifier to a next audience order identifier obtained from a next position from an audience order table if said first audience specific value has been determined to not exist via said determining step;

repeating said accessing said data attribute table, said determining if said first audience specific value exists, said providing said first audience specific value if said first audience specific value has been determined to exist until all audience order identifiers having said audience identifier have been accessed; and

,

repeating said accessing said first field in said main data table in said database and said obtaining said reference identifier from said first field and said accessing said data attribute table, said determining if said first audience specific value exists, said providing said first audience specific value if said first audience specific value has been determined to exist until all audience order identifiers having said audience identifier have been accessed and until all fields have been accessed for a first document.

7. The method of claim 6 further comprising:

accessing an audience table to determine if an audience is enabled.

8. The method of claim 6 further comprising:

accepting payment for access to audience specific information.

9. The method of claim 6 further comprising:

generating a document into a desired media type.

10. The method of claim 9 wherein said media type is print.

11. The method of claim 9 wherein said media type is XML.

12. The method of claim 9 wherein said media type is HTML.

13. The method of claim 6 further comprising:

said obtaining said audience identifier further comprising presenting a user interface to a user.

14. The method of claim 6 further comprising:

said obtaining said first audience identifier further comprising obtaining information from an environment variable on a computer associated with a user.

15. The method of claim 6 further comprising:

said obtaining said audience identifier further comprising obtaining information from a browser session variable.

16. A method for providing an audience specific product name from an audience order hierarchy in computer database using layer-specific inheritance rules, said method comprising:

constructing a main data table for said computer database that does not require altering in any way in order to add support for a new audience;

constructing a data attribute table that contains audience specific names for at least some fields in said main data table;

constructing an audience order table that contains the next audience identifier to use in finding a suitable value by inheritance;

accepting a subset of data for an audience with respect to another audience into said data attribute table wherein said subset of data is unique with respect to said another audience, wherein new audience data not contained in said subset of data is inherited from at least one other parent audience, and wherein said audience and said another audience differ in one or more of language, country, region, regulatory, or cultural designations, wherein said data attribute table is augmented only with those said subset of data values that are unique to said new audience;

obtaining a first audience identifier and a product identifier for the purpose of providing a product name associated with an audience from an audience order hierarchy for use in document generation;

querying said main data table for a name identifier associated with said product identifier;

querying said data attribute table a first time for said product name associated with a first data attribute entry comprising said name identifier and said first audience identifier;

querying said audience order table for an audience order entry comprising said first audience identifier and an audience order field when said first data attribute table query returns a null result;

selecting a second audience identifier from said audience order field wherein said selected second audience identifier follows sequentially from said first audience identifier in said audience order field;

querying said data attribute table a second time for a second data attribute entry comprising said second audience identifier and said name identifier;

providing said product name from said second data attribute entry when said second data attribute table query returns a non-null result.

17. The method of claim 16 further comprising:

repeating the query of said data attribute table for a third time as specified when said second data attribute entry returns a null result.

18. The method of claim 16 further comprising:

halting the querying of said data attribute table when said audience order entry comprises a stop flag; and

providing instead a failure result for said product name.

19. The method of claim 16 further comprising:

halting the querying of said data attribute table when said audience order entry comprises a disable flag; and

providing instead a null string for said product name.