Oracle Apps Different Types of Purchase Order

A Standard Purchase Order is one time purchasing to buy goods or services.You can create PO when you know the Item, Price, Delivery schedule and Payment terms

A Blanket Purchase Agreement it’s a long time agreement where you don’t know about Quantity, Price and required Delivery schedule. The Quantity and Price fields will be disabled when you make Blanket Purchase Agreement. You have to enter a Price. The required Quantity, Delivery Schedule and final Price will be informed to the Supplier by creating Blanket Releases against the Blanket Purchase Agreement.

A Planned Purchase Order it’s a long time agreement where you are not sure about the required delivery schedules. You know the details like Item, Price, Delivery Schedule and Payment Terms. In the Planned purchase order you have to enter a Need-By date, but this date that you enter will be treated only as a tentative date. The exact date on which the shipments are to be delivered is informed to the Supplier by creating Schedule Releases against the Planned purchase order.

A  Contract Purchase Agreement is document which gives standard term and conditions created. You do not know even the item that is to be purchased. The only information that you provide in a Contract Purchase Agreement is Supplier, Supplier Site, Payment Terms and Agreement Control details. Standard Purchase Orders are created by referring to the Contract Purchase Agreement when something is to be purchased against this Contract Purchase Agreement.

Oracle Apps Diffrence Between PTO , ATO and CTO

Difference between PTO, ATO and CTO

PTO - Pick to Order environment where the goods are manufactured based on forecasted demand. It’s a fixed configuration of product available which can be order and no changes can be done in this configuration.

ATO: - Assemble to order environment is one in which the product or service is "assembled on receipt of the sales order". The parts are kept in stock but not manufactured until the actual order is created.  Receipt of the order initiates assembly of the customized product. Assemble-to-order is useful where a large number of finished products can be assembled from common components.

CTO: - Configure to Order is a method which allows you to configure your final product by select base product. Based on these selections, configurable items on each quote or order typically generates the "unique product" configuration and manufacturing routing and/or bill of materials based on various features and options. Vendor receiving company subsequently builds that configuration dynamically upon receipt of the order.

Oracle Apps :- You are not allowed to create Order lines

User will get an Error while try to create Order line.

 "You are not allowed to create Order lines"

Solution:-

This is might be because of Processing Constraint which don't have Validation template.

To Fix the issue Navigate to Order Management Super User responsibility

Setups>Rules>Security>Processing Constraints

Query the Application by F11

Enter Application: - Order Management

Enter Entity: - Order Lines

Once the result come query for Create Operation.

There would be one record which don.t have validation Template attached to it.

User Action = Not Allowed and Enabled Check box was ON and the system check box is OFF

The Condition was "ANY" but there were no Validation Template and in Applicable to Tab "All Responsibility" Tab was enabled.

Delete that record and save.

This will eliminate the issue.

Oracle Apps How to Find the Concurrent Request

Hi Folks

Below is the query to find out the Concurrent Name.

select a.user_concurrent_queue_name

from fnd_concurrent_queues_vl a,

FND_CONCURRENT_QUEUE_CONTENT b,

fnd_concurrent_programs_vl c

where a.concurrent_queue_id=b.concurrent_queue_id

and b.type_id = c.concurrent_program_id

and c.user_concurrent_program_name=:RequestName