Processing Terms Used When Generating Microsoft Word Documents

Document structure

A document structure is the entire document structure that includes any children for which the parent element is either repeating, an alternate, or an element that is included due to a rule. The structure represents the descendent hierarchy of text elements and depends on the repeating nature of the parent element. other repeating elements, rules, or alternates are possible as descendents of the parent element, but they are not considered document structures.

Microsoft Word XML (Microsoft Word Extensible Markup Language) Microsoft Word XML (Microsoft Office Open Extensible Markup Language) Microsoft Office Open Extensible Markup Language

Microsoft Office 2007, or later version, enables the PeopleSoft Supplier Contract Management system to generate the Microsoft Word document content and complete the check-out and check-in processes without losing Microsoft Word formatting.

The system creates and saves the file in a Microsoft Word XML Document format (.xml extension instead of a .doc extension).

Nonrepeating elements

Nonrepeating elements are clauses, sections, or rules that are based on transaction information. However, nonrepeating elements are not based on repeating transaction information; rather, they are based on transaction information for which only a single value will ever exist for the contract. For example, a supplier name or a contract end date is a single value. Nonrepeating elements can also be based on document creation wizard binds because they have only one value for the contract.

Repeating elements

A repeating element is a clause, section, or rule that is based on transaction information. You map to this information using bind variables that may have multiple values for a contract. Examples of repeating elements might be contract items on a purchase order contract or contact information on an ad hoc contract. The repeating nature of the bind variable used in the element determines whether the element itself is to repeat or not.

Source transaction

Indicates whether the document was created for use with a purchasing contract, purchase order, or for ad hoc use. An Ad Hoc document is one that has been created for general use. These documents are not constrained by procurement requirements and can be used for a variety of organizational uses, such as purchasing a one-time miscellaneous item or a service outside of the procurement system.

A Purchasing Contract document is tied to a specific contract ID and extracts specific information from the contract to include in the document. The document contains a link back to its source transaction so that you can identify the source from within the document authoring system.

A Purchase Order document is a document that is based on a purchase order and is linked to a PeopleSoft Purchasing purchase order.