[Home] [Help]
308: being done for the reversed line as all info like accounting event id is
309: not being populated. Moreoevr, with any additional change / validation
310: in base, we had to change the code.
311:
312: To avoid all this, used base API ap_cancel_pkg.Ap_Cancel_Single_Invoice
313: to cancel the TDS invoice. This way,much of the task is being done by base
314: and hence no inconsistency.
315:
316: 11 12-apr-2004 Aparajita for bug#3556035. Version#619.2
336:
337: When an invoice is cancelled , it was not getting cancelled and instead throwing an error
338: cannot update null into ap_invoices_all.last_update_date. This error was captured in
339: JAI_CMN_ERRORS_T on the client's instance through an exception handler.
340: The value to be set into this column was retreived through an API call to ap_cancel_pkg.Ap_Cancel_Single_Invoice
341:
342: Due to some internal exception, the out parameter corresponding to the the last_update_date is null
343:
344: Spoke to lgopalsa she was of the opinion that in the ap_cancel_pkg.Ap_Cancel_Single_Invoice API ,
340: The value to be set into this column was retreived through an API call to ap_cancel_pkg.Ap_Cancel_Single_Invoice
341:
342: Due to some internal exception, the out parameter corresponding to the the last_update_date is null
343:
344: Spoke to lgopalsa she was of the opinion that in the ap_cancel_pkg.Ap_Cancel_Single_Invoice API ,
345: the standard who columns are being set anyway and there is no need to set it explicitly in the
346: procedure.
347:
348: As part of this fix , removed the last_update_date from the columns in the update ap_invoices_all
536: -- end added by Aparajita on 05/11/2002 for bug # 2586784
537:
538: -- Start for bug#3536079
539: v_return_value :=
540: ap_cancel_pkg.Ap_Cancel_Single_Invoice
541: (
542: for_pay_status_tds_rec.invoice_id ,
543: cancelled_invoices_rec.last_updated_by,
544: cancelled_invoices_rec.last_update_login ,