Wednesday, January 14, 2009

AOL

1.which is most priority in Profile options? if profile option is set at Site Level and user level, which will be overriden by which?

Ans:User level profile option value will override site level profile option value.

2.Cross validation rules
Ans: Using these, you can prevent to enter few code combinations across application.
Generate Accounts like concurrent program or Front end forms will give error while system tries to create code combination and will also give reason as cross validation error message.
Eg: If balancing segment is '00' then cost center should not be '00'.

3.Security rules
Ans: These will be defined at segment level and assigned to particular responsibilities. User with above responsibility can not view certain values of segment, which are excluded by security rule.

Notes:
1.HR Data is at BG Level
GL Data is at SOB Level
Sub Ledgers like AP/AR/FA/PA... Data at OU Level
INV, BOM, WIP data is at Inventory org level

organization_id is Inventory organization Id
Ord_id is OU id

PO

Using this module client can create requisitions, purchase orders, requests for quotoation and receipts quickly and effectively.
4 Types of POs
1.Standard PO
2.Planned PO
3.Blanket Purchase Agreement
4.Contract Purchase Agreement

Client/Customer will have option to enter below
Price
Quantity
Terms&conditions
Goods& services
Delivery schedule
Accounting and
Supplier shipment authorization

Clinet/Customer creats...
Standard PO, when he want vendor commitment and to specific item or service for a particular scheduled time, but long-term agreement is not appropriate.

Planned PO, when customer want long-term agreement committing to buy items or services.

Blanket PA/Release, this will be created with negotiated volume discounts and want to create blanket releases against agreement to place actual order.

Contract PA/Release, customer will do this without indicating goods or services. Later will create po on these contracts.

Global Agreements: Buyers can negotiate price & terms. Later will create po on these.

PO APIs:
1.Open Requisition Interface-->Upload requisitions
PO_REQUISITIONS_INTERFACE_ALL
PO_REQ_DIST_INTERFACE_ALL
2.Purchasing Document Interface-->Upload purchase orders, responses to RFQs
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE
3.Receiving Open Interface-->Upload receipt information into
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE

Matching:
2-way matching
invoice price <= PO price
quantitiy billed <= quantity ordered

3-way matching
invoice price <= PO price
quantity billed <= quantity ordered
quantity billed <= quantity received
4-way matchinginvoice price <= PO price
quantity billed <= quantity ordered
quantity billed <= quantity accepted

Good Links
http://www.oracleappshub.com/oracle-purchasing/po-tips-and-useful-query/