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

 

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

get_usage_history_m Error Messages

Table of contents
This article applies to:Aria Crescendo

Overview

The following error messages can be generated by get_usage_history_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


20007: Limit Records number must be greater than zero

Associated Inputs: Limit, limit_records


20013: Skip Records number must be greater than zero

Associated Input: offset


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.


3036: Invoice_line_item does not have qualifying invoice_no or transaction_no

Associated Input: invoice_line_item

Additional Comments: Invoice_no is required if invoice_line_item is specified


1033:  a parameter that represents a true or false value contains invalid input

Associated Inputs: alt_collect_on_approve, alt_send_statement_on_approve, cancel_orders_on_discard, cascade_action, do_auto_discard, do_collect, change_status_after_coll, reset_dates_after_status, disable_existing_on_update, do_write, exclude_terminated_plan_inst, include_all_rate_schedules, include_plan_hierarchy, retrieve_bundled_nso, retrieve_included_nso, include_translations, include_inactive_items, include_invoice_activity_eligibility, include_rs_summary, include_translations, include_service_supp_fields/include_product_fields/, include_plan_instance_fields/include_plan_services/, include_surcharges, include_void_transactions, include_voided, invoice_unbilled_usage, is_unlinked_refund, record_cc_on_auth_failure, retrieve_excluded_usage, send_email, usage_pooling, do_write


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.


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


16012: Contract end date is less than start date

Associated Inputs: date_range_start, date_range_end, start_date, end_date, length_months


1067: Locale no does not exist in the system.

Associated Inputs: locale_no, master_plan_instance_no


1066: Locale name does not exist in the system.

Associated Inputs: locale_name


You must to post a comment.
Last modified
15:22, 11 Aug 2017

Tags

This page has no custom tags.

Classifications

This page has no classifications.