Home » Applications » Oracle Fusion Apps & E-Business Suite » AR_RECEIPT_PUB.APPLY_ON_ACCOUNT
icon9.gif  AR_RECEIPT_PUB.APPLY_ON_ACCOUNT [message #189423] Thu, 24 August 2006 09:48 Go to next message
mj_73
Messages: 4
Registered: August 2006
Location: Texas
Junior Member
I'm a somewhat newbie to Oracle Developing... so here is my question/error.

I am trying to make a call to the api to apply payments on account but am receiving the following error:

DECLARE
*
*
ERROR at line 1:
ORA-06550: line 161, column 7:
PLS-00306: wrong number or types of arguments in call to 'APPLY_ON_ACCOUNT'
ORA-06550: line 161, column 7:
PL/SQL: Statement ignored

 v_program_user        VARCHAR2(15);
 v_api_version         VARCHAR2(15);
 -- standard api variables
 v_return_status       VARCHAR2(240);
 v_msg_count           NUMBER;
 v_msg_data            VARCHAR2(240);
 v_count               NUMBER;

 AR_RECEIPT_API_PUB.APPLY_ON_ACCOUNT(
   p_api_version           => v_api_version,
   p_cr_id                 => v_cash_receipt_id,
   p_amount_applied        => tran.amount,
   p_gl_date               => 'v_gl_date',
   p_apply_gl_date         => 'v_gl_date',
   p_called_from           => v_program_user,
   x_return_status         => v_return_status,
   x_msg_count             => v_msg_count,
   x_msg_data              => v_msg_data);

[Updated on: Thu, 24 August 2006 10:15]

Report message to a moderator

Re: AR_RECEIPT_PUB.APPLY_ON_ACCOUNT [message #210430 is a reply to message #189423] Wed, 20 December 2006 16:18 Go to previous messageGo to next message
kumarkovela
Messages: 6
Registered: March 2005
Location: delhi, india
Junior Member

Hi ,

Pass parameter p_cash_receipt_id instead of p_cr_id.

then it'll be work.

thanks
kumar
icon7.gif  Re: AR_RECEIPT_PUB.APPLY_ON_ACCOUNT [message #210432 is a reply to message #210430] Wed, 20 December 2006 16:21 Go to previous messageGo to next message
mj_73
Messages: 4
Registered: August 2006
Location: Texas
Junior Member
Thanks... I found that by checking the FORM.
Re: AR_RECEIPT_PUB.APPLY_ON_ACCOUNT [message #210521 is a reply to message #189423] Thu, 21 December 2006 03:33 Go to previous messageGo to next message
kumarkovela
Messages: 6
Registered: March 2005
Location: delhi, india
Junior Member

Hi,

How can we populate customer number after executing APPLY_ON_ACCOUNT api. The API is successfully, but i'm unable to populate mandatory customer number.

thanks
KUMAR
Re: AR_RECEIPT_PUB.APPLY_ON_ACCOUNT [message #210596 is a reply to message #210521] Thu, 21 December 2006 08:04 Go to previous messageGo to next message
mj_73
Messages: 4
Registered: August 2006
Location: Texas
Junior Member
I am using
AR_RECEIPT_API_PUB.CREATE_CASH
then calling ON_ACCT API. the create cash api uses the customer_id.
Re: AR_RECEIPT_PUB.APPLY_ON_ACCOUNT [message #211011 is a reply to message #210596] Mon, 25 December 2006 01:45 Go to previous message
dongta_ndh
Messages: 2
Registered: December 2006
Junior Member
Hi,
Please use it as follow :

ar_receipt_api_pub.create_apply_on_acc(
p_api_version => 1.0,
p_init_msg_list => p_init_msg_list,
p_commit =>p_commit,-- :p_commit,
p_validation_level =>p_validation_level,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_usr_currency_code => p_usr_currency_code,
p_currency_code => p_currency_code,--:p_currency_code,
p_usr_exchange_rate_type => p_usr_exchange_rate_type,
p_exchange_rate_type =>p_exchange_rate_type,--'User',-- :p_exchange_rate_type,
p_exchange_rate =>p_exchange_rate,--:RA_RECEIP_FDT.CONVERSION_RATE,-- :p_exchange_rate,
p_exchange_rate_date =>p_exchange_rate_date,--:RA_RECEIP_FDT.TRX_DATE,--:p_exchange_rate_date,
p_amount => :RA_RECEIP_FDT.AMOUNT,--:p_amount,
p_factor_discount_amount => p_factor_discount_amount,

p_receipt_number => p_receipt_number,

p_receipt_date => p_receipt_date,
p_gl_date => :parameter.GL_DATE,--:p_gl_date,
p_maturity_date => p_maturity_date,
p_postmark_date => p_postmark_date,

p_customer_id => Cus_id_v,--1141,--:p_customer_id,

p_customer_name => p_customer_name,
p_customer_number => p_customer_number,
p_customer_bank_account_id => p_customer_bank_account_id,
p_customer_bank_account_num => p_customer_bank_account_num,
p_customer_bank_account_name => p_customer_bank_account_name,
p_location => p_location,
p_customer_site_use_id => p_customer_site_use_id,
p_customer_receipt_reference => p_customer_receipt_reference,
p_override_remit_account_flag => p_override_remit_account_flag,
p_remittance_bank_account_id => p_remittance_bank_account_id,
p_remittance_bank_account_num => p_remittance_bank_account_num,
p_remittance_bank_account_name => p_remittance_bank_account_name,
p_deposit_date => p_deposit_date,

p_receipt_method_id =>receipt_method_id,-- 4207,--:p_receipt_method_id,


p_receipt_method_name => p_receipt_method_name,
p_doc_sequence_value => p_doc_sequence_value,
p_ussgl_transaction_code =>p_ussgl_transaction_code,
p_anticipated_clearing_date => p_anticipated_clearing_date,
p_called_from => p_called_from,
p_attribute_rec => p_attribute_rec,
p_global_attribute_rec => p_global_attribute_rec,
p_receipt_comments =>:RA_RECEIP_FDT.DESCRIPTION,-- p_receipt_comments,
p_issuer_name => p_issuer_name,
p_issue_date => p_issue_date,
p_issuer_bank_branch_id => p_issuer_bank_branch_id,
p_cr_id => p_cr_id,

p_amount_applied => :RA_RECEIP_FDT.AMOUNT,--:p_amount_applied,
p_apply_date =>p_apply_date,

p_apply_gl_date => :parameter.GL_DATE,--:p_apply_gl_date,
app_ussgl_transaction_code => app_ussgl_transaction_code,
app_attribute_rec => app_attribute_rec,
app_global_attribute_rec => app_global_attribute_rec,
app_comments => app_comments,
p_application_ref_num => p_application_ref_num,
p_secondary_application_ref_id => p_secondary_application_ref_id,
p_customer_reference => p_customer_reference,
p_customer_reason => p_customer_reason,
p_secondary_app_ref_type => p_secondary_app_ref_type,
p_secondary_app_ref_num => p_secondary_app_ref_num,
p_call_payment_processor => p_call_payment_processor
);
Previous Topic: What is the role of a Tech n Func consultant
Next Topic: How to use and write an user_exit in Oracle Application Form?
Goto Forum:
  


Current Time: Thu Dec 08 06:40:26 CST 2016

Total time taken to generate the page: 0.06477 seconds