APPS.PO_CUSTOM_SUBMISSION_CHECK_PVT SQL Statements

The following lines contain the word 'select', 'insert', 'update' or 'delete':

Line: 40

   *     p_online_report_id:  Id to be used when inserting records into
   *                          PO_ONLINE_REPORT_TEXT_GT table.
   *     p_user_id:           User performing the action
   *     p_login_id:          Last update login_id
   *     p_sequence:          Sequence number of last reported error
   *
   * Modifies: None. [The custom code has to be written by customer.]
   * Effects:  This procedure runs the custom document submission checks on
   *           passed in document.
   * Returns:
   *  x_return_status:  FND_API.G_RET_STS_SUCCESS if API succeeds
   *                    FND_API.G_RET_STS_UNEXP_ERROR if unexpected error occurs
   *
   * NOTE: For writing custom code, please refer to the instructions given at
   *       the top of this file.
   */
  PROCEDURE do_pre_submission_check(
    p_api_version                    IN             NUMBER,
    p_document_id                    IN             NUMBER,
    p_action_requested               IN             VARCHAR2,
    p_document_type                  IN             VARCHAR2,
    p_document_subtype               IN             VARCHAR2,
    p_document_level                 IN             VARCHAR2,
    p_document_level_id              IN             NUMBER,
    p_requested_changes              IN             PO_CHANGES_REC_TYPE,
    p_check_asl                      IN             BOOLEAN,
    p_req_chg_initiator              IN             VARCHAR2,
    p_origin_doc_id                  IN             NUMBER,
    p_online_report_id               IN             NUMBER,
    p_user_id                        IN             NUMBER,
    p_login_id                       IN             NUMBER,
    p_sequence                       IN OUT NOCOPY  NUMBER,
    x_return_status                  OUT NOCOPY     VARCHAR2
  )
  IS
    l_api_name    CONSTANT varchar2(50)  := 'do_pre_submission_check';

Line: 183

   *     p_online_report_id:  Id to be used when inserting records into
   *                          PO_ONLINE_REPORT_TEXT_GT table.
   *     p_user_id:           User performing the action
   *     p_login_id:          Last update login_id
   *     p_sequence:          Sequence number of last reported error
   *
   * Modifies: None. [The custom code has to be written by customer.]
   * Effects:  This procedure runs the custom document submission checks on
   *           passed in document.
   * Returns:
   *  x_return_status:  FND_API.G_RET_STS_SUCCESS if API succeeds
   *                    FND_API.G_RET_STS_UNEXP_ERROR if unexpected error occurs
   *
   * NOTE: For writing custom code, please refer to the instructions given at
   *       the top of this file.
   */
  PROCEDURE do_post_submission_check(
    p_api_version                    IN             NUMBER,
    p_document_id                    IN             NUMBER,
    p_action_requested               IN             VARCHAR2,
    p_document_type                  IN             VARCHAR2,
    p_document_subtype               IN             VARCHAR2,
    p_document_level                 IN             VARCHAR2,
    p_document_level_id              IN             NUMBER,
    p_requested_changes              IN             PO_CHANGES_REC_TYPE,
    p_check_asl                      IN             BOOLEAN,
    p_req_chg_initiator              IN             VARCHAR2,
    p_origin_doc_id                  IN             NUMBER,
    p_online_report_id               IN             NUMBER,
    p_user_id                        IN             NUMBER,
    p_login_id                       IN             NUMBER,
    p_sequence                       IN OUT NOCOPY  NUMBER,
    x_return_status                  OUT NOCOPY     VARCHAR2
  )
  IS
    l_api_name    CONSTANT varchar2(50)  := 'do_post_submission_check';