[Home] [Help]
200: * the security check on
201: * p_document_subtype: The subtype of the document.
202: * Valid Document types and Document subtypes
203: * Document Type Document Subtype
204: * RFQ ---> STANDARD
205: * QUOTATION ---> STANDARD
206: * REQUISITION ---> PURCHASE/INTERNAL
207: * RELEASE ---> SCHEDULED/BLANKET
208: * PO ---> PLANNED/STANDARD
201: * p_document_subtype: The subtype of the document.
202: * Valid Document types and Document subtypes
203: * Document Type Document Subtype
204: * RFQ ---> STANDARD
205: * QUOTATION ---> STANDARD
206: * REQUISITION ---> PURCHASE/INTERNAL
207: * RELEASE ---> SCHEDULED/BLANKET
208: * PO ---> PLANNED/STANDARD
209: * PA ---> CONTRACT/BLANKET
204: * RFQ ---> STANDARD
205: * QUOTATION ---> STANDARD
206: * REQUISITION ---> PURCHASE/INTERNAL
207: * RELEASE ---> SCHEDULED/BLANKET
208: * PO ---> PLANNED/STANDARD
209: * PA ---> CONTRACT/BLANKET
210: * p_type_clause: The document type clause to be used in
211: * constructing where clause
212: *
285: -------------------------------------------------------------------------------
286: --Start of Comments
287: --Name: check_std_po_price_updateable
288: --Function:
289: -- Checks whether price updates are allowed on this Standard PO line.
290: -- See the package body for detailed comments.
291: --End of Comments
292: -------------------------------------------------------------------------------
293: PROCEDURE check_std_po_price_updateable (
335: -- ID of a Complex Work pay item.
336: --p_add_reasons_to_msg_list
337: -- (Only applies if x_price_updateable = PO_CORE_S.G_PARAMETER_NO.)
338: -- If PO_CORE_S.G_PARAMETER_NO, the API will add the reasons why price updates
339: -- are not allowed to the standard API message list. Otherwise, the API
340: -- will not add the reasons to the message list.
341: --OUT:
342: --x_return_status
343: -- FND_API.G_RET_STS_SUCCESS if the API completed successfully.