Skip to main content

PO::Document Types

Document Types

Document Types is used to define access, security, and control specifications for all Purchasing documents. You cannot enter new document types but you can enter new document subtypes only for RFQs and quotations. Purchase Agreement, Purchase Order, Quotation, Release, Request for Quotation, and Requisition are all the documents types available.
Navigation: Purchasing Responsibility=> Setup=> Purchasing=> Document Types

Owner Can Approve to indicate that document preparers can approve their own documents. This field is not applicable when the Document Type is Quotation or RFQ.
Approver Can Modify to indicate that document approvers can modify documents. This field is not applicable when the Document Type is Quotation or RFQ.

Can Change Forward To to indicate that users can change the person the document is forwarded to. This field is not applicable when the Document Type is Quotation or RFQ.

Can Change Forward From to indicate that users can change the name of the document creator. This field is applicable only when the Document Type is Requisition.

Can Change Approval Hierarchy to indicate that approvers can change the approval hierarchy in the Approve Documents window. This field is not applicable when the Document Type is Quotation or RFQ.

Disable to disable a document type. This field is applicable only for user-defined quotations and RFQs.

Security Level informs who are all eligible to access the documents.

Hierarchy - Only the document owner and users above the owner in the defined purchasing security hierarchy may access these documents.
Private - Only the document owner may access these documents.
Public - Any user may access these documents.
Purchasing - Only the document owner and users listed as buyers in the Define Buyers window may access these documents.

Access Level gives restriction to user on these documents.

Full - Users can view, modify, cancel, and final close documents.
Modify - Users can only view and modify documents.
View Only - Users can only view documents.

Forward Method: The following options apply regardless of whether you are using position hierarchies or the employee/supervisor relationship to determine your approval paths. The Forward Method field is not applicable when the Document Type is Quotation or RFQ. Choose one of the following options:
Direct - The default approver is the first person in the preparer's approval path that has sufficient approval authority.
Hierarchy - The default approver is the next person in the preparer's approval path regardless of authority. (Each person in the approval path must take approval action until the person with sufficient approval authority is reached.)

Archive On: The Archive on field is applicable only when the Document Type is Purchase Agreement, Purchase Order, or Release. Choose one of the following options:

Approve - The document is archived upon approval. This option is the default. The Change Order workflow begins only if this option is chosen
Transmission - The document is archived upon transmission. A document transmission action would be printing, faxing, or e-mail.

Default Hierarchy field is not applicable when the Document Type is Quotation or RFQ. Otherwise, when Use Approval Hierarchies is enabled in the Financial Options window, you can enter a position hierarchy from the Position Hierarchy window. This hierarchy then becomes the default in the Approve Documents window.

Approval Workflow: The PO Approval workflow is used for approving purchase orders. The PO Requisition Approval workflow is used for approving requisitions. If you've created a workflow of your own, you can select that for this document. Select the Approval Workflow you want to use for this particular document type, or use the default that is already provided.

Workflow Startup Process: Usually the Workflow Startup Process is the highest-level process in a workflow. The default startup process for the PO Approval workflow is the PO Approval Top Process. The default startup process for the PO Requisition Approval workflow is the Main Requisition Approval Process. If you've created a startup process of your own, you can select that for this document.

Autocreate Workflow: This is applicable for requisitions only, select the Autocreate Workflow you want to use for automatically creating purchase orders or releases from approved requisition lines, or use the default that is provided. The default workflow that comes with Purchasing is the PO Create Documents workflow. If you've created a workflow of your own, you can select that for this document.

Autocreate Workflow Startup Process: This is applicable for requisitions only, select the Autocreate Workflow Startup Process you want to use, or use the default that is already provided.
The highest-level process for the PO Create Documents workflow is the Overall Document Creation / Launch Approval Process. If you've created a startup process of your own, you can select that for this document.

Comments

Popular posts from this blog

Oracle Subledger Accounting (SLA) Tables, Views

Oracle Subledger Accounting (SLA) Tables, Views Oracle Subledger Accounting Tables: TABLE NAME DESCRIPTION XLA_AAD_GROUPS The XLA_AAD_GROUPS table stores the merge dependencies analyzed during the merge analysis.  All application accounting definitions with the same GROUP_NUM must be merged together. XLA_AAD_HDR_ACCT_ATTRS The XLA_AAD_HDR_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the AAD level. XLA_AAD_HEADER_AC_ASSGNS Store the analytical criteria for the application accounting definitions. XLA_AAD_LINE_DEFN_ASSGNS This table stores the journal lines definitions for the application accounting definitions. XLA_AAD_LOADER_DEFNS_T The XLA_AAD_LOADER_DEFNS_T table is the interface table that facilitates the data transfer from data files and the database. XLA_AAD_LOADER_LOGS The XLA_AAD_LOADER_LOGS table stores the errors and logs generated by the application accounting definitions loader. XLA_AAD_SOURCES XLA_AAD_SOURCES table stores a...

Oracle Fusion Cloud: Supplier Import Process using File Based Data Import (FBDI)

 Supplier Data Migration or Upload to Oracle Fusion environment File-Based Data Import for Oracle Procurement Cloud Supplier import in oracle fusion   In this post , We will discuss about Supplier import in oracle fusion. Oracle has provided the FBDI tool to import suppliers from External  Source  to the Oracle fusion. Supplier Import in Oracle fusion we first need to  Download  the Supplier Import FDBI  templates  given by the Oracle fusion to import suppliers. Oracle has given 5 Different FBDI templates to Import supplier in Fusion. Here in this post , I will share the Complete steps for Supplier import in oracle fusion. You can refer this post for Supplier Import.   Steps for Supplier import in oracle fusion     Step1- First we need to download Supplier Data  Template  from Oracle Repository. Go to this path for Oracle Repository. ( select Based on your Cloud version) https://docs.oracle.com/en/...

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects Introduction When it comes to contractual billing, invoice and revenue generation are two separate processes, which during the lifespan of a project may or may not always coincide with each other and so do the balances in revenue and receivables accounts.  This interim difference between revenue and invoice account balances is bridged using Unbilled Receivables (UBR) and Unearned Revenue (UER) Accounts. Unearned Revenue (UER) Unearned Revenue (also termed as deferred revenue or UER) signifies money received for the goods or services, which are yet to be delivered.  As per the principles of Revenue Recognition, UER is recorded as on the balance sheet unless it is converted to Revenue upon delivery of goods or services For Example XYZ Consulting Ltd. receives an annual maintenance contract of $ 12,000 on Dec 31, 2014 for the period of Jan 01, 2015 to Dec 31, 2015. At the start of the contract as of Dec 31, 2...