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

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...