update_acct_plan_status_m Error Messages
- Last updated
- Save as PDF
Overview
The following error messages can be generated by update_acct_plan_status_m.
1001: unexpected error
1004: authentication error
Associated Inputs: auth_key, client_id, client_no
1009: account does not exist, Account not found: AriaNo (acct_no), Account not found: Userid (userid), or Account not found: ClientId (client_acct_id)
Associated Inputs: acct_no, account_no, client_acct_id, user_id, userid, parent_acct_no
14077: Account status not support Plan provisioning.
Associated Inputs: status_cd
Additional Comment: The current status of the account does not allow provisioning.
25020: Illegal characters entered
Associated Inputs: All character field inputs like firstname lastname, dunning_group_name, comments, etc.
1010: missing required parameters, Missing input: (object-name) is required with assignment_directive ($AriaNo)
Associated Inputs: all required inputs, typically one of the following: custom_rate_per_unit, custom_rate_seq_no, status_cd, dunning_state, userid, acct_no, client_acct_id, assignment_directive, billing_group_no, client_billing_group_id, threshold_billing_rule_no, client_threshold_billing_rule_id
Alternate Message Output
1010: username is required
1010: first name is required
1010: last name is required
1010: email is required
1010: roles are required
Associated APIs: create_user_m, get_user_details_m, delete_user_m, update_user_m
Associated Inputs: username, first_name, last_name, email, role_no
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
14051: Invalid Plan status for the new Plan
Associated Inputs: plan_instance_status, status_cd
14132: Custom rates cannot be assigned for this non-provisioned status.
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.
7034: invalid dunning state
Associated Inputs: dunning_state
24009: Invalid Queue Date
Associated Input: queue_date
Additional Comments: Queue date must be in the future.
24010: Invalid Queue Days
Associated Input: queue_days
Additional Comments: Queue days must not be negative
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.