assign_custom_acct_plan_rates_m Error Messages
- Last updated
- Save as PDF
Overview
The following error messages can be generated by assign_custom_acct_plan_rates_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
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
14107: Invalid Service Number.
Associated Input: custom_rate_service_no
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
14005: invalid Plan service combination
Associated Inputs: custom_rate_service_no, custom_rate_service_id
Additional Comments: The given Plan number and service number combination for master and Supplemental Plans is not valid.
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
14015: The custom rates for services other than usage and recurring types can have only one tier with rate_seq_no set to 1, the from_unit set to 1 and to_unit left empty. Alt: custom from and to units not supported for given service_no
Associated Inputs: custom_rate_from_unit, custom_rate_to_unit
Additional Comments: For the custom rate sequence, the "from" unit in one tier is not immediately after the end unit in the previous tier. Tiers are not allowed for other than recurring and usage services.
14043: Invalid Plan instance rate_seq combination
Associated Inputs: custom_rate_from_unit, custom_rate_to_unit
Additional Comments: If the from/to units are not specified, the given rate_seq_no must be a valid rate_seq_no.
14014: When entering custom rates, the end sequence number of one tier must immediately precede the start sequence number of the next tier. Alt: invalid rate tier structure
Associate Inputs: custom_rate_to_unit, custom_rate_seq_no
Additional Comments:
When entering custom rates, the tiers must be continuous, that is, the end sequence number of one tier must immediately precede the start sequence number of the next tier. In addition, the rate schedule must have the same number of units in each tier, and the same number of tiers, as the schedule on which it is based. From_units must be greater than - and less than to_units.
14129: Rate per unit cannot be negative.
Associated Input: rate_per_unit
14027: The end units of final rate tier is not infinity
Associated Inputs: custom_rate_to_unit
Additional Comments: The custom rates final unit must be infinity.