Define Document Sequences

Define document sequences for contracts only if you need to autonumber contracts or clauses, or when you're doing the setup for the partner agreement type of contracts.

Important: If you're unfamiliar with the setup of document sequences, be sure to read the topics in the Document Sequences chapter in the Oracle Fusion Cloud Applications Implementing Applications guide.

You can define document sequences for contracts at these levels:

• Global
• Ledger
• Legal Entity
• Business Unit

You can define document sequences for clauses at these levels:

• Global
• Ledger
• Business Unit

Note: Each contract type you're using can have a different sequence.

Here are the steps to define the document sequences:

1. In Setup and Maintenance, search for the Manage Document Sequence Categories task.
2. In the Application field, search for Enterprise Contracts.

   You should see document sequence categories for the contract header table, OKC_K_HEADERS_ALL_B, and the clause table, OKC_ARTICLES_ALL.

3. Create a new document sequence category for the table, OKC_K_HEADERS_ALL_B, to store contract header information.

   You don't need to create document sequences for the table, OKC_ARTICLES_ALL, that stores clauses, because you'll number the clauses manually.

4. Save your changes.
5. To create partner program enrollment contracts from the Partner Relationship Management application, create a new document sequence category for the table, OKC_K_HEADERS_ALL_B, to store contract header information.
6. Save your work.
7. Next, search for the Manage Document Sequences task.
8. In the Application field, search for Enterprise Contracts.
9. Create a document sequence in the primary table and assign it to the document category created for the contract header in the child table.

   The assignment start date needs to be before the contract type assignment start date.

   Select the primary ledger for the determinant value that's used to determine the document autonumbering scope and save your work.

10. To create partner program enrollment contracts from the Partner Relationship Management application, create a document sequence in the primary table and assign it to document category created for contract header in the child table.

    Select the primary ledger for the determinant value that's used to determine the document autonumbering scope and save your work.

Note: A contract created when autonumbering is disabled must have the line number provided, even if in the meantime you've changed the line type option back to autonumbering. The change won't propagate to the already created contract.