Home > Aria Crescendo Documentation > Aria Crescendo API List > Aria Crescendo API Error Messages > update_acct_plan_m Error Messages

update_acct_plan_m Error Messages

Table of contents

Overview

The following error messages can be generated by update_acct_plan_m.

1001: unexpected error


1004: authentication error

Associated Inputs: auth_key, client_id, client_no


1016: invalid input, acct_no: (acct_no) is not a valid long, assignment_directive: (assignment_directive) is not a valid long, “billing_group_no: (billing_group_no) is not a valid long, threshold_billing_rule_no: (threshold_billing_rule_no) is not a valid long            

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, acct_no, assignment_directive, billing_group_no, threshold_billing_rule_no

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.

Additional Comments: For the get_order_m API, this is the error code returned when the user passes an invalid order value for the <status_filter_cd> input which is other than the allowed values (0/null, 1, 2, 3, 4 and 5).
 

Alternate Message Output

1016: username cannot be longer than 30 characters
1016: first_name cannot be longer than 30 characters
1016: last_name cannot be longer than 30 characters

Associated APIs: create_user_m, update_user_m

Associated Inputs: username, first_name, last_name


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.


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


1035: invalid assignment directive, Invalid Assignment Directive: (assignment_directive)

Associated Inputs: master_plan_assign_directive, assignment_directive


1064: Invalid surcharge directive

Associated Inputs: surcharge_directive

4027: Changes for this plan were not saved because the collection attempt associated with this change was unsuccessful.

Associated Inputs: do_collect


5004: invalid responsibility level cd

Associated Inputs: resp_level_cd

Additional Comments: Resp_level_cd=4 is not supported in Aria Crescendo.


5053: Missing values for required plan instance field

Associated Inputs:   plan_instance_field_value

Additional Comments: This field is required, but did not have a value.


5059: Invalid Product Field Value.

Associated Inputs: field_value

Additional Comments: The value must be from the configured allowed values.


5060: Invalid Product Field Directive.

Associated Inputs: plan_instance_field_directive


5061: Number of Product Field value exceeds maximum number of allowed values.

Associated Inputs: field_value

Additional Comments: The value must meet the configured maximum values.


5062: Number of Product Field values does not meet required minimum number of values.

Associated Inputs: field_value

Additional Comments: The value must meet the configured minimum values.


5063: Field cannot be added because it is not a plan instance field.

Associated Inputs:  plan_instance_field_name


5076: Only child accounts can have parent-pay MPIs.


7034: invalid dunning state

Associated Inputs: dunning_state


7038: A Billing Group is required for a Self-Pay Child Account's MPI.


14003: error assigning supp plan

Additional Comments: Unknown error while assigning a supplemental plan to an account. Contact Aria Customer support for assistance.


14012: Alternate rate schedule's currency does not match the account's currency.

Associated Inputs: alt_rate_schedule_no, client_alt_rate_schedule_id

Additional Comments: The alt_rate_schedule currency does not match the  account currency.


14019: invalid usage accumulation reset months value

Associated Inputs: usage_accumulation_reset_months

Additional Comments: The accumulation months is not between 0 and 99.


14023: Offset Interval must be greater than zero

Associated Inputs: offset_interval


14024: Invalid Offset Interval and Assignment Directive combination.

Associated Inputs: offset_interval, assignment_directive

Additional Comments: Offset_interval only applies to the anniverary date.


14025: Invalid do_write and assignment directive combination for queuing plan.

Associated Inputs: assignment_directive, do_write

Additional Comments: Preview cannot be done for queued anniversary date cases.


14026: The Effective Date must be in the future, "YYYY-MM-DD" format, and a valid date.

Associated Inputs: effective_date


14033: Invalid Promo Code

Associated Inputs: promo_cd


14036: Invalid client service id

Associated Inputs: client_service_id, client_plan_instance_service_id, client_percent_eval_service_id, custom_rate_client_service_id


14038: Invalid client rate schedule id

Associated Inputs: client_alt_rate_schedule_id, rollover_client_rate_sched_id


14046: If you passed in an invalid plan_instance_no, this message will appear: "Invalid plan instance number". If you passed in an invalid master_plan_instance_id, this message will appear: "Invalid master_plan_instance_id".

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

Additional Comments: The plan_instance_no or master_plan_instance_id 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: If you passed in an invalid client_plan_instance_id, this message will appear: "Invalid client plan instance identifier". If you passed in an invalid client_master_plan_instance_id , this message will appear: "Invalid client_master_plan_instance_id".

Associated Inputs: client_plan_instance_id, client_master_plan_instance_id, client_percent_eval_plan_instance_id


14059: The senior master plan instance cannot be responsible for another plan instance because it is set to Parent Pay

Associated Inputs: resp_master_plan_inst_no and client_resp_master_plan_inst_id, parent_acct_master_plan_instance_no

Additional Comments: The responsible plan instance is a child pay,


14063: duplicate plan instance client defined id.

Associated Inputs:client_plan_instance_id, new_client_plan_inst_id


14068: invalid parent account master plan instance number

Associated Inputs: parent_acct_mp_inst_no, parent_acct_master_plan_inst_id


14074: Plan status cannot be updated because the status of the existing plan does not allow it

Associated Inputs: plan_status_cd


14077: Account status not support plan provisioning.

Associated Inputs: status_cd

Additional Comment: The current status of the account does not allow provisioning.


14078: Master plan instance status not support plan provisioning.

Associated Inputs: status_cd

Additional Comments: The current status of the master plan does not allow provisioning.


14079: Supp plan instance status not support plan provisioning.

Associated Inputs: supp_plan.status_cd


14084: Invalid rate schedule. Please verify start date and end date of provided rate schedule.

Associated Inputs: alt_rate_schedule_no, alt_rate_schedule_id


14086: Plan Units cannot be below the minimum required units for this child plan.

Associated Inputs: plan_units


14087: The maximum number of allowable units has been exceeded.


14094:Invalid Plan Instance Status CD.

Associated Inputs: plan_status_cd


14098: Invalid proration invoice timing

Associated Inputs: mp_proration_invoice_timing, proration_invoice_timing


14112 Cannot update/replace/cancel any queued plan instance which is in queued assignment

Associated Inputs: plan_instance_no, client_plan_instance_id


14108 Plan cannot be queued because parent plan instance's status is non-provisioned

Associated Input: assignment_directive


14109 Plan cannot be queued because master plan instance is in dunning or has completed dunning(i.e., dunning state is 'In Progress' or 'Completed')

Associated Input: assignment_directive


14133: MPIs that are in dunning or have completed dunning without exiting successfully are not displayed, because they cannot be converted from self-pay to parent-pay while in this state. The MPIs that are in dunning are NNNNN, NNNNN, NNNNN, etc..


14134: Please apply outstanding manually applicable payments before modifying payment responsibility..


14135: The Responsible Master Plan instance provided is queued for assignment and not allowed to be used for payment responsibility.


14310: Invalid input: For bill lag days, Enter a number between +billing interval and - billing interval days.


14311: Invalid input: For bill lag days, Enter a number less than/equal to billing interval days.


15001: invalid coupon code

Associated Inputs: coupon_codes


15002: coupon expired

Associated Inputs: coupon_codes, coupon_cd


15006: Duplicate surcharge number in input

Associated Inputs: acct_surcharges, mpi_surcharges, mp_surcharge_no


15008: Invalid surcharge rate schedule no

Associated Inputs: rate_schedule_no, mp_rate_schedule_no


15009: Invalid surcharge number

Associated Inputs: surcharge_no, mp_surcharge_no


15011: The coupon code provided for this account or master plan does not match its specified Coupon Applicability Scope, which determines whether the coupon is available at the account level, the master plan instance level, or both.

Associated Inputs: coupon_cd


15012: Coupon code has already been applied and cannot be used again.

Associated Inputs: coupon_codes


15013: The surcharge provided for this Account or Master Plan does not match its specified Surcharge Applicability Scope, which determines whether the surcharge is available at the account level, master plan instance level or both.

Associated Inputs: mpi_surcharges, mp_surcharge_no


15014: Duplicate Surcharges found.

Associated Input: mp_surcharge_no


15015: Surcharge can't be assigned because its application scope is payment method

Associated Inputs: mpi_surcharges, mp_surcharge_no


23013: Invalid usage threshold applicability

Associated Inputs: usage_threshold_applicability

Additional Comments: The usage_threshold_applicability is not in, "ut" or "up".


26010:Invalid billing group number

Associated Inputs: billing_group_no


26012: Invalid client-defined billing group ID.

Associated Inputs: client_billing_group_id


26030: The dunning state of the master plan instance cannot be updated to In Progress because no applicable dunning process was found. Please review the dunning processes defined for the appropriate dunning group, plan, payment method, and/or the client-default to ensure a dunning process exists for this scenario.

Associated Inputs: dunning_state


26046: Invalid dunning step. The dunning step does not exist in the dunning process configuration.


Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.