Documente Academic
Documente Profesional
Documente Cultură
1.
2.
level
3.
4.
Requisitions: The only close action available for Requisitions is Final Close.
Purchase Orders: For a full list of the close actions that can be performed on each of
the different Purchasing document types
Close
A purchase order is automatically closed once it is received (if you require a receipt) and is
billed for all purchase order shipments. Since you do not require or expect any further
activity, Purchasing closes the purchase order. You can also manually close the purchase
order early if you do not expect further activity. Adding lines to it or receiving against it,
reopens the purchase order. Purchasing does not consider closed purchase orders for
accruals.
Close can be done at the header, release, line, and shipment levels.
Close for Invoicing
A purchase order control that you can assign manually or that Purchasing can assign
automatically when the amount invoiced reaches a defined percentage of the order quantity.
You can close for invoicing at the header, release, line, and shipment levels.
Note: that if you close for invoicing a purchase order header that is currently open,
Purchasing sets the status of all purchase order shipments to Closed for Invoicing,
but the purchase order lines and header remain open. This status will not prevent
you from matching an invoice to the purchase order or to the receipt.
Close for Receiving
A purchase order control you can assign manually or that Purchasing can assign
automatically when the amount received reaches a defined percentage of the order quantity.
You can close for receiving at the header, release, line, and shipment levels.
Finally Close
A purchase order control you can assign to prevent modifications to or
actions against completed documents, lines, and shipments by finally closing
them. Finally-closed documents are not accessible in the corresponding entry
windows, and you cannot perform the following actions against finally-closed
entities: receive, transfer, inspect, deliver, correct receipt quantities, invoice,
return to supplier, or return to receiving. Finally Close documents can not be
reversed so consideration should be given when performing this action.
You can choose finally close at the header, release, line, and shipment levels.
If you are using encumbrance or budgetary control, Finally Close
automatically creates credit encumbrance journal entries in your general
ledger system to reverse the encumbrance that corresponds to the purchase
order header, lines, or shipments you are closing, using the action date you
specify in Action Date. See: Budgetary Control and Online Funds
Checking, Oracle General Ledger User's Guide.
What Close Actions are valid for each document type and entity?
Current
Document
Type
Finally
Close
Close
Close
for
Invoice
Close
for
Receipt
Planned PO
Header
Planned PO
Line
Planned PO
Shipment
Standard PO
Header
Standard PO
Line
Standard PO
Shipment
Blanket
Agreement
Header
Blanket
Agreement
Line
Contract
Agreement
Header
Release
Header
Release
Shipment
Requisition
Header
Requisition
Line
This is applicable to purchase orders that do not have a status of Closed, that
is, the Mass Close program closes all the shipments that are not already
closed, canceled, encumbered or frozen. When you run the concurrent
program, the purchase orders are specified are closed completely (this
includes headers, lines, shipments).
You can mass close purchase orders with the following statuses:
Frozen
On Hold
Approved
Reserved
Contract Agreement
For Blanket Releases the functionality is being considered as an Enhancement Request - per
Product Management -
RELEASES
The parameters for running the concurrent program are Document Type, Document number,
Date Range and Supplier Name.A report is generated as output from the concurrent
program. This report lists the document number and document type of the Oracle
Purchasing documents that were updated by the program."
Testing
To test the functionality, you can create a purchase order - and approve it.
- Then, move to Purchasing - Reports/Run
- Single Request
- Choose Operating Unit
- Give the purchase order type - then the purchase order number
- Dates are required
- Submit the request
Next, move to Purchase Orders/Purchase Order Summary
- query the purchase order - and it should now be closed
BEGIN
-- Parameters :
-- p_docid : Header ID for Document
-- Table: PO_HEADERS_ALL.PO_HEADER_ID
-- p_doctyp : Document Type
-- Table: PO_HEADERS_ALL.TYPE_LOOKUP_CODE
-- Values : STANDARD, BLANKET, RELEASE
-- p_lineid : Line ID for Document
-- Table: PO_LINES_ALL.PO_LINE_ID
-- p_shipid : Ship ID for Document
-- Table: PO_LINE_LOCATIONS.LINE_LOCATION_ID
-- p_action : Action to be performed
-- Table: PO_ACTION_HISTORY.ACTION_CODE
-- Values: 'CLOSE' -- Close for Receiving
-'INVOICE CLOSE'
-'FINALLY CLOSE'
-- p_reason : Reason for Closing. This must be entered for Manual
Closing
-- p_calling_mode : Whether being invoked from 'PO', 'RCV' or
'AP'. This
-determines which of the Closed States needs
to be
-checked (receiving, invoicing or both). This
must be
-entered for Auto Closing
-- p_conc_flag : Whether invoked from a Concurrent Process. This
must be
-entered for Manual Closing and is used by the
Funds Checker
-- p_return_code : Return Status of PO Closing
-- p_auto_close : Whether to invoke Auto Closing or Manual
Closing
-- p_action_date is added to function close_po()
ELSE
DBMS_OUTPUT.PUT_LINE('Cannot close PO#'||po_details_rec.segment1);
END IF;
END;
END LOOP;
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line(' Exception closing PO using
PO_ACTIONS.CLOSE_PO'||SQLERRM);
END xx_po_close_prc;