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