|
|
|
1004: authentication error
|
<client_no>, <auth_key> |
1016: invalid input
Additional Comments: This error can be caused by the wrong type of input; for example, text in a numbers-only field, or specifying a value other than one of the documented allowable values.
|
<client_no>, <acct_no>, <plan_instance_no>, <alt_rate_schedule_no>, <plan_units>, <plan_status>, <plan_instance_field_directive assignment_directive>, <custom_rate_service_no>, <custom_rate_seq_no>, <custom_rate_from_unit>, <custom_rate_to_unit>, <custom_rate_per_unit offset_interval>, <force_master_bill_date_reset>, <dunning_state>, <resp_level_cd>, <usage_accumulation_reset_months>, <mp_surcharge_no>, <mp_surcharge_directive>, <mp_rate_schedule_no proration_invoice_timing>, <service_no>, <svc_location_no>, <dest_contact_no plan_instance_supp_field_update_only>, <force_bill_date_reset>, <recurring_processing_model_ind>, <usage_accumulation_reset_months_renewal_option>, <bill_lag_days>, <new_dunning_step>, <config_dunning_late_fee_option>, <config_dunning_email_option>, <resp_master_plan_instance_no>, <billing_group_no>, <offset_months>, <auto_offset_months_option> |
1024: invalid date format
Additional Comments: All date inputs must be in yyyy-mm-dd format.
|
<effective_date>, <degrade_date>, <alt_proration_start_date>, <application_date> |
1033: a parameter that represents a true or false value contains invalid input
|
<do_write>, <usage_pooling>, <force_currency_change>, <remove_pi_custom_rates>, <include_plan_instance_queue> |
1035: invalid assignment directive, Invalid Assignment Directive: (assignment_directive)
|
<assignment_directive> |
1064: Invalid surcharge directive
|
<mp_surcharge_directive> |
4027: Changes for this Plan were not saved because the collection attempt associated with this change was unsuccessful.
|
|
5004: invalid responsibility level cd
Additional Comments: Resp_level_cd=4 is not supported in Aria Billing Cloud.
|
<resp_level_cd> |
5053: Missing values for required Plan instance field
Additional Comments: This field is required, but did not have a value.
|
<plan_instance_field_value> |
5059: Invalid Product Field Value.
Additional Comments: The value must be from the configured allowed values.
|
<plan_instance_field_value> |
5060: Invalid Product Field Directive.
|
<plan_instance_field_directive> |
5061: Number of Product Field value exceeds maximum number of allowed values.
Additional Comments: The value must meet the configured maximum values.
|
<plan_instance_field_value> |
5062: Number of Product Field values does not meet required minimum number of values.
Additional Comments: The value must meet the configured minimum values.
|
<plan_instance_field_value> |
5063: Field cannot be added because it is not a Plan instance field.
|
<plan_instance_field_name> |
5075: Only self-pay Master Plan Instances can be assigned to a Billing Group.
|
<billing_group_no><client_billing_group_id> |
7034: invalid dunning state
|
<dunning_state> |
7035: The Plan selected for update is a Master Plan. The force_master_bill_date_reset input can only be used in conjunction with Supplemental Plans. Please clear the value of force_master_bill_date_reset or input a Supplemental Plan.
|
<force_master_bill_date_reset> |
7036: The Plan selected for update is a Supplemental Plan. The force_bill_date_reset input can only be used in conjunction with Master Plans. Please clear the value of force_bill_date_reset or input a Master Plan.
|
<force_bill_date_reset> |
7038: A Billing Group is required for a Self-Pay Child Account's MPI.
|
|
14003: error assigning Supplemental 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.
Additional Comments: The alt_rate_schedule currency does not match the account currency.
|
<alt_rate_schedule_no>, <client_alt_rate_schedule_id> |
14019: usage_accumulation_reset_months must be from 0 to 99 Alt: invalid usage accumulation reset months value
Additional Comments: The accumulation months is not between 0 and 99.
|
<usage_accumulation_reset_months> |
14023: Offset Interval must be greater than zero
|
<offset_interval> |
14024: Invalid Offset Interval and Assignment Directive combination.
Additional Comments: Offset_interval only applies to the anniverary date.
|
<offset_interval>, <assignment_directive> |
14025: Invalid do_write and assignment directive combination for queuing Plan.
Additional Comments: Preview cannot be done for queued anniversary date cases.
|
<assignment_directive>, <do_write> |
14026: The Effective Date must be in the future, "YYYY-MM-DD" format, and a valid date.
Associated Inputs: effective_date
|
<effective_date> |
14033: Invalid Promo Code
|
<promo_cd> |
14036: Invalid client service id
|
<custom_rate_client_service_id>, <client_service_id> |
14039: Invalid client rate schedule id
|
<client_alt_rate_schedule_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".
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.
|
<resp_master_plan_instance_no>, <resp_client_master_plan_instance_id> |
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".
|
<resp_client_master_plan_instance_id> |
14059: The senior Master Plan Instance cannot be responsible for another Plan instance because it is set to Parent Pay
Additional Comments: The responsible Plan instance is a child pay,
|
<resp_master_plan_instance_no>, <resp_client_master_plan_instance_id> |
14063: duplicate Plan instance client defined id.
|
<resp_client_master_plan_instance_id> |
14068: invalid parent account Master Plan Instance number
|
<resp_master_plan_instance_no>, <resp_client_master_plan_instance_id> |
14074: Plan status cannot be updated because the status of the existing Plan does not allow it
|
<plan_status> |
14077: Account status not support Plan provisioning.
Additional Comment: The current status of the account does not allow provisioning.
|
|
14078: Master Plan Instance status not support Plan provisioning.
Additional Comments: The current status of the Master Plan does not allow provisioning.
|
<plan_status> |
14079: Supplemental Plan instance status not support Plan provisioning.
|
<plan_status> |
14084: Invalid rate schedule. Please verify start date and end date of provided rate schedule.
|
<alt_rate_schedule_no>, <client_alt_rate_schedule_id> |
14086: Plan Units cannot be below the minimum required units for this child Plan.
|
<plan_units> |
14087: The maximum number of allowable units has been exceeded.
|
|
14094:Invalid Plan Instance Status CD.
|
<plan_status> |
14098: Invalid proration invoice timing
|
<proration_invoice_timing> |
14112 Cannot update/replace/cancel any queued Plan instance which is in queued assignment
|
<plan_instance_no>, <client_plan_instance_id> |
14108 Plan cannot be queued because parent Plan instance's status is non-provisioned
|
<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')
|
<assignment_directive> |
14133: Self-pay MPI cannot be converted to parent-pay as it is currently in dunning or completed dunning without exiting.
Additional Comments: 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.
|
|
14136: Offset months must be greater than or equal to 0.
|
|
14137: To permit usage pooling on plans the invoice settings parameter 'Allow MPI Level Usage Pooling' needs enabling.
|
|
14300: Cannot force currency change while account has Master Plan / Supplemental Plans that do not have an available rate schedule in the target currency
|
<force_currency_change> |
14302: Pending Invoices must be discarded prior to forcing a currency change.
|
<force_currency_change> |
14303: Surcharges must be discarded or voided prior to forcing a currency change.
|
<force_currency_change> |
14304: Rated but unbilled usage records must be discarded prior to forcing a currency change.
|
<force_currency_change> |
14305: Discounts (flat rate) or Coupons in an existing currency must be discarded or voided prior to forcing a currency change.
|
<force_currency_change> |
14306: Pending Orders in an existing currency must be discarded or voided prior to forcing a currency change.
|
<force_currency_change> |
14307: Force currency change not allowed with the supplied assignment directive.
|
<force_currency_change> |
14310: Enter a Bill Lag days between +/- Plan's Billing Interval.
Additional Comments: Invalid input: For bill lag days, Enter a number between +billing interval and - billing interval days.
|
<bill_lag_days> |
14311: Enter a Bill Lag days less than/equal to Plan's Billing Interval.
Additional Comments: Invalid input: For bill lag days, Enter a number less than/equal to billing interval days.
|
<bill_lag_days> |
14313: There are threshold billing rules attached to this account that will need to be removed prior to changing currency since they are not in the future currency.
|
<force_currency_change> |
14314: There is an active rollover contract for existing currency and it should be cancelled or terminated before proceeding.
|
<force_currency_change> |
14402: Usage Pooling is not allowed when the Rating Model rates usage on a ‘per record’ basis.
|
<force_currency_change> |
15001: invalid coupon code
|
<coupon_codes> |
|
|
<coupon_codes> |
15006: Duplicate surcharge number in input
|
<mp_surcharge_no> |
15008: Invalid surcharge rate schedule no
|
<mp_rate_schedule_no> |
15009: Invalid surcharge number
|
<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.
|
<coupon_codes> |
15012: Coupon code has already been applied and cannot be used again.
|
<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.
|
<mp_surcharge_no> |
15014: Duplicate Surcharges found.
|
<mp_surcharge_no> |
15015: Surcharge can't be assigned because its application scope is payment method
|
<mp_surcharge_no> |
16021: The currency for the contract completion rollover target rate schedule must match the currency on the account.
|
|
23013: Invalid usage threshold applicability
Additional Comments: The usage_threshold_applicability is not in, "ut" or "up".
|
<usage_threshold_applicability> |
26010: Invalid billing group number
|
<billing_group_no> |
26012: Invalid client-defined billing group ID.
|
<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.
|
<dunning_state> |
26046: Invalid dunning step. The dunning step does not exist in the dunning process configuration.
|
|
26048: The Responsible Master Plan Instance cannot be changed for this Parent-pay Master Plan Instance since it is in dunning or has completed dunning without exiting successfully as a result of an unpaid balance transfer.
|
|
