Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!

 

Home > Aria Crescendo API List > Aria Crescendo API Error Messages > record_usage_m Error Messages

record_usage_m Error Messages

Table of contents
This article applies to:Aria Crescendo

Overview

The following error messages can be generated by record_usage_m.

1001: unexpected error


1004: authentication error

Associated Inputs: auth_key


1009: account does not exist

Associated Inputs: acct_no, account_no, client_acct_id, user_id, parent_acct_no


14071: Master Plan Instance information is missing

Associated Inputs: plan_instance_no, client_plan_instance_id, master_plan_instance_no, client_master_plan_instance_id

Additional Comments: Both plan_no and plan_id must be entered. Master plan instance is required if the invoice_no is not provided.


25020: Illegal characters entered

Associated Inputs: All character field inputs like firstname lastname, dunning_group_name, comments, etc.


14053: Invalid master plan instance number

Associated Inputs: master_plan_instance_no


14054: Invalid client master plan instance identifier

Associated Inputs: client_master_plan_instance_id


14046: Invalid plan instance number

Associated Inputs: plan_instance_no, master_plan_instance_no, filter_plan_instance_no, percent_eval_plan_instance_no, client_plan_instance_id,

Additional Comments: The master_plan_instance_no must belong to the account, or it is invalid. The percent_eval_plan_instance_no must belong to the account and also to the MPI given in input.


14047:Invalid client plan instance identifier

Associated Inputs: existing_client_plan_instance_id, client_master_plan_instance_id, client_percent_eval_plan_instance_id


23020: Usage unit value is too large.


14126: Rate field cannot be negative if amt, billable_units, or usage_units are negative values.


14127: Amount cannot be positive if the billable/usage unit is negative.


14125: Negative Usage not allowed for Usage-based services in which Usage Pooling is enabled unless pre-rated.


1024: invalid date format

Associated Inputs: bill_birthdate, birthdate, degrade_date, initial_credit_date, invoice_line_reversing_date, service_fulfillment_date, queue_date, start_bill_date, end_bill_date, start_date, end_date, stmt_birthdate, bill_birthdate

Additional Comments: All date inputs must be in yyyy-mm-dd format.


20002: Usage Type or Usage Type Code must be entered


20003: Invalid Usage Type


20004: Invalid Usage Type Code


20006: usage code or type not on active plan


1016: invalid input

Associated Inputs: alt_service_no_to_apply, assignment_directive, auto_skip_to_next_bill_date, client_billing_group_id, custom_rate_service_no/custom_rate_client_service_id, plan_instance_no, plan_instance_service_no, client_plan_instance_id, client_plan_instance_service_id, plan_instance_no, plan_instance_service_no, client_plan_instance_id, client_plan_instance_service_id, plan_instance_service_no, eligible_plan_no, eligible_service_no, email, force_master_bill_date_reset, fulfillment_only, include_master_plans, include_supp_plans, include_billing_groups, include_payment_methods, include_master_plans, include_supp_plans, include_billing_groups, include_payment_methods, invoice_no, length_months, end_date, limit, limit_records, modify_directive, contract_plan_instances_update, modify_directive, contract_plan_instances_update, offset, percent_amount, percent_eval_plan_instance_no, client_percent_eval_plan_instance_id, percent_eval_service_no, client_percent_eval_service_id, phone_ext, work_phone_ext, plan_unit_inst_status_cd, plan_units, reason_code, start_date, end_date, start_date, end_date, status_cd

Additional Comments:  This error can be caused by the wrong type of input, for example, text in a numbers-only field, an  or specifying a value other than one of the documented allowable values.


You must to post a comment.
Last modified
13:39, 17 Aug 2017

Tags

This page has no custom tags.

Classifications

This page has no classifications.