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

 

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

bulk_record_usage_m Error Messages

Table of contents
This article applies to:Aria Crescendo

Overview

The following error messages can be generated by bulk_record_usage_m.

1001: unexpected error


1004: authentication error

Associated Inputs: auth_key


25000: Bulk usage loader competed with some error(s)


24318: Bulk errors


1009: account does not exist

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


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.


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


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


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


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

Tags

This page has no custom tags.

Classifications

This page has no classifications.