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

 

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

update_acct_plan_multi_m Error Messages

Table of contents
This article applies to:Aria Crescendo

Overview

The following error messages can be generated by update_acct_plan_multi_m.

1001: unexpected error


1004: authentication error

Associated Inputs: auth_key


1010: missing required parameters

Associated Inputs: all required inputs, typically one of the following: custom_rate_per_unit, custom_rate_seq_no, status_cd, dunning_state


1016: invalid input

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

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.


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.


1031: can not pass in an alternate starting date AND alternate billing day

Associated Inputs: alt_bill_day, alt_start_date


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


1034: there is no data to be modified


1035: invalid assignment directive

Associated Inputs: master_plan_assign_directive, assignment_directive


1049: Billing or plan changes not allowed due to the account status

Associated Inputs: N/A

Additional Comments: This message indicates a processing problem.


1053: invalid notification template group id

Associated Inputs:billing_group.notify_template_group


1064: Invalid surcharge directive

Associated Inputs: surcharge_directive

1068: Combine invoices must be either 1-Long Cycle or 2-Short Cycle or 3-Consider Client Param.

Associated Inputs: combine_invoices


1069: Long cycle (Combine invoice) is not available, since plan instance has plan rollover or contract rollover or future plan changes in the middle of the cycle or while generating a pending invoice.


1101: Credit-only proration is not valid in this case because there is a mandatory child supplemental plan that will be assigned and result in charges on the account.

Associated Inputs: master_plan_assign_directive


3003: could not create invoice


3017: pro-ration period cannot be greater than plan billing interval


3018: invalid automatic offset months option


4006: invalid pay method

Associated Inputs: alt_pay_method, pay_method_type, pay_method_type


4008: invalid expiration date

Associated Inputs: alt_pay_method, cc_expire_mm, cc_expire_yyyy, credit_expiry_date, pay_method_type

Additional Comments: Dates must be in yyyy-mm-dd format.


4009: invalid cc number

Associated Inputs: cc_number, alt_pay_method, cc_num, pay_method_type


4010: invalid bank draft info

Associated Inputs: bank_acct_no, bank_routing_no, alt_pay_method

Additional Comments:

  1. The client parameter BANK_DRAFT_INDICATOR must be enabled. 1.
  2. Bank_acct_no and bank_routing_no are required.
  3. Valid bank_routing_no from Aria's ABA lookup in case of US address.
  4. Bank_routing_no must be numeric.
  5. For US, bank_routing_no should be 9 digits in length (left padded with zeros).
  6. Bank_routing_no must pass checksum validation.

4017: duplicate payment method client defined id.

Associated Inputs: client_payment_method_id, new_client_payment_method_id

Additional Comments: This value must be unique at the client level.


4024: Invalid auto collection on plan change input

Associated Inputs: auto_collect_on_plan_chng


4025: Invalid rollback_plan_chng_collect_fail input

Associated Inputs: rollback_plan_chng_collect_fail


4026: Invalid auto_send_stmt_on_plan_chng input

Associated Inputs: auto_send_stmt_on_plan_chng


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

Associated Inputs: do_collect


4032: cc_id is required.

Associated Inputs: cc_id, pay_method_type

Additional Comments: cc_id is required for this payment processor.

 


5003: invalid notify method

Associated Inputs: notify_method_no


5004: invalid responsibility level cd

Associated Inputs: resp_level_cd

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


5020: alternate billing day must be between 1 and 31

Associated Inputs: alt_bill_day


5029: invalid item or sku

Associated Inputs: filter_item_no, filter_client_item_id, client_sku


5041: Invalid invoicing option provided

Associated Inputs: invoicing_option


5051: the responsible master plan instance number/identifier is not associated with the senior account number

Associated Inputs: resp_master_plan_inst_no, parent_acct_master_plan_inst_id

Additional Comments: The responsible mpi_no must be from the senior/parent account.


5052: Invalid product field

Associated Inputs: plan_instance_fields_info.field_name, field_name

Additional Comments: The field is not mapped to the plan.


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


6021: Invalid state_prov entered

Associated Inputs: bill_state_prov, state_prov, stmt_state_prov, bill_state_prov


6027: IBAN is alphanumeric and is 16 to 34 characters in length

Associated Inputs:  iban, alt_pay_method_iban


6029: Bank swift code is alphanumeric and is 8 or 11 characters in length

Associated Inputs: bank_swift_cd, alt_pay_method


6031: BBAN is numeric and up to 16 digits

Associated Inputs: alt_payment_method, bank_acct_no


6033: Bank branch code is numeric and up to 10 digits

Associated Inputs: bank_branch_cd


6034: Basic bank account number or IBAN is required for Direct Debit

Associated Inputs: iban, bank_acct_no


6045: Account can have only one active NETS payment method.

Associated Inputs: payment_method_type


7027: master plan instance cannot be created without billing group

Associated Inputs: billing_group_idx/cdid

Additional Comments: Billing_group is mandatory when master_plan_instance.resp_level_cd = 1.


7028: duplicate billing group client defined id.

Associated Inputs: client_billing_group_id, new_client_billing_group_id

Additional Comments: This value must be unique at the client level.


7029: The new_client_dunning_group_id field contains the ID of an existing dunning group.

Associated Inputs: client_dunning_group_id

Additional Comments: This value must be unique at the client level.


7029: The new_client_dunning_group_id field contains the ID of an existing dunning group.

Associated Inputs: client_dunning_group_id

Additional Comments: This value must be unique at the client level.


7030: The new master plan instance must be associated with a dunning group. You must enter a dunning group when associating a master plan instance.

Associated Inputs: dunning_group_idx/cdid

Additional Comments: Dunning_group is mandatory when master_plan_instance.resp_level_cd = 1.


7031: Invalid dunning_process_no

Associated Inputs: dunning_process_no


7033: Invalid client defined dunning process id

Associated Inputs: client_dunning_group_id


7034: invalid dunning state

Associated Inputs: dunning_state


12010: Client account group does not exist

Associated Inputs: collections_acct_group_no, client_acct_group_id, alt_client_acct_group_id


14004: Invalid_plan_no

Associated Inputs: new_plan_no, rollover_plan_no


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.


14006: invalid rate schedule no

Associated Inputs: acct_rate_schedule_no, mpi_rate_schedule_no, master_plans_detail, alt_rate_schedule_no, supp_plan.alt_rate_schedule_no


14008: account has supplemental plans that are not eligible under this master plan

Additional Comments: The supplemental plan is not linked to the master plan.


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.


14013: New plan does not have a rate schedule with a currency matching the account's currency.

Associated Inputs: alt_rate_schedule_no, acct_currency

Additional Comments: The given rate schedule currency does not match the account's currency.


14016: The plan is already assigned to the account

Associated Inputs: new_plan_no


14017: Date must be in YYYY-MM-DD format

Associated Inputs: alt_proration_start_date

Additional Comments: The alt_proration_start_date must be within the last billed period.


14019: invalid usage accumulation reset months value

Associated Inputs: usage_accumulation_reset_months

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


14022: supplemental plan violates plan exclusion group

Associated Inputs: plan_no

Additional Comments: The supplemental plan is not matched with the master plan exclusion group.


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


14028: Tier Pricing Rule Flat Rate is not valid to configure for the Single Line Upgrade proration


14030: Invalid Assignment Directive provided for Single Line Upgrade proration.

Associated Inputs: assignment_directive


14031: Oracle error while selecting for Single Line Upgrade proration.


14032: The Assignment Directive awarding credit cannot be used with the Single Line Upgrade proration invoice service plan.


14033: Invalid Promo Code

Associated Inputs: promo_cd


14035: Invalid client plan id

Associated Inputs: client_plan_id, custom_rate_client_plan_instance_id


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


14042: Promo Code Expired

Associated Inputs: promo-cd


14045: Promo code's start date is in the future

Associated Inputs: promo_cd


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


14049: Invalid parent plan instance no

Associated Inputs: parent_plan_instance_no


14051: Invalid plan status for the new plan

Associated Inputs: plan_instance_status, status_cd


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,


14060: Plan cannot be replaced because the plan stauts of the existing lan does not allow the plan to be replaced

Additional Comments: The current status of the MPI does not allow its plan to be replaced


14063: duplicate plan instance client defined id.

Associated Inputs:client_plan_instance_id, new_client_plan_inst_id


14064: Supplemental plan of this plan instance cannot be set as its parent plan.

Associated Inputs: existing_plan_instance_no


14065:Promo code not allowed for supp plan

Associated Inputs: promo_cd


14066: Assignment directive cannot be anniversary for master plan

Associated Inputs: assignment_directive


14067: Supplemental plan cannot have resp level code and parent account master plan instance number


14068: invalid parent account master plan instance number

Associated Inputs: parent_acct_mp_inst_no, parent_acct_master_plan_inst_id


14070: Cannot cancel plan which is under dunning

Associated Inputs: existing_plan_instance_no

14072: Offset interval not allowed for master plan assignment.

Associated Inputs: offset_months


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

Associated Inputs: plan_status_cd


14075: Supplemental plan not eligible under this plan instance.

Associated Inputs: new_plan_no


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


14081: Plan instance already cancelled

Associated Inputs: existing_plan_instance_no


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.


14088: Mandatory child plans cannot be canceled unless their parent plan is also canceled.


14094:Invalid Plan Instance Status CD.

Associated Inputs: plan_status_cd


14097: An existing plan instance cannot be used when assigning a new plan to an account (plan_directive = 1).

Associated Inputs: existing_plan_instance_no, existing_client_plan_instance_id


14098: Invalid proration invoice timing

Associated Inputs: mp_proration_invoice_timing, proration_invoice_timing


14099: Duplicate plan instance provided meaning the same instance cannot be provided for update/replace/cancel in the same API

Associated Inputs: existing_plan_instance_no


14100: Too many plan operations. Please reduce the number of plan operations to be under <limit>.


14101: Mandatory child plans cannot be replaced unless their parent plan is also modified.


14102: Invalid parent plan instance id

Associated Inputs: parent_client_plan_instance_id


14103: cannot rollover queued plan as the original initial plan in not matching the current plan

Associated Inputs: new_plan_no


14107: Invalid Service Number.

Associated Input: custom_rate_service_no


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


14110 The effective date of a queued child plan assignment must be on or after the effective date of the queued parent plan assignment

Associated Inputs: effective_date


14111 Plan cannot be queued because parent plan instance is not in scheduled queue ie. Effective date is not given


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

Associated Inputs: plan_instance_no, client_plan_instance_id


14113 The plan provided is not a valid child of the plan that will be associated with the parent plan instance on the effective date provided

Associated Inputs: new_plan_no


14124 The effective date of a queued parent plan assignment must be on or before the effective date of the queued child plan assignment


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


15010: Coupon code not allowed for supp plan

Associated Inputs: coupon_cd


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


15016 Invalid coupon directive

Associated Inputs: coupon_directive


18005: Invalid Template number

Associated Inputs: alt_msg_template_no, cn_alt_msg_template_no, alt_inv_template_no, alt_stmt_template_no


18010: Invalid Credit Memo Template number

Associated Inputs: credit_memo_template

Additional Comments: The credit memo template must be mapped to the "CM" template class.


18011: Invalid Rebill Template number

Associated Inputs: rebill_template

Additional Comments: The rebill template must be mapped to "RB" template class.


20026: agreement id OR credit card info is required

Associated Inputs: pay_method_type, bill_agreement_id, cc_num

Additional Comments: The pay_method_type is "13", the bill_agreement_id is null and cc_num is null.


20031: agreement id is mandatory for this payment method

Associated Inputs: pay_method_type, bill_agreement_id

Additional Comments: The pay_method_type is "29" and the bill_agreement_id is null.


23013: Invalid usage threshold applicability

Associated Inputs: usage_threshold_applicability

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


25001: failed to calculate taxes


25003: Provided inventory item is not bundled with the plan definition

Associated Inputs: client_sku

Additional Comments: You have entered an invalid inventory item.


25004: Inventory item units cannot exceed the number of plan units

Additional Comments: item_units


25005: Inventory item units must be equal to or greater than the minimum quantity defined in the Product Catalog

Associated Inputs: item_units, plan_no, client_plan_id


25006: Total inventory item units must equal the number of plan units assigned

Associated Inputs: item_units, plan_no, client_plan_id


25007: Inventory item  units must be equal to or less than the maximum quantity specified in the Product Catalog

Associated Inputs: item_units, plan_no, client_plan_id

Additional Comments: The NSO type is individual and the item_units is less than the maximum quantity specified in the product catalog.


25009: One or more provided inventory items are not eligible for purchase.

Associated Inputs: client_sku

Additional Comments: Inventory items are not mapped to the plans on the account.


25020: Illegal characters entered

Associated Inputs: All character field inputs like firstname lastname, dunning_group_name, comments, etc.


26010:Invalid billing group number

Associated Inputs: billing_group_no


26012: Invalid client-defined billing group ID.

Associated Inputs: client_billing_group_id


26013: Invalid dunning group number

Associated Inputs: dunning_group_no


26014: Invalid client-defined dunning group ID.

Associated Inputs: client_dunning_group_id


26018: Invalid dunning group directive

Associated Inputs: dunning_group_directive


26019: Provided primary payment method idx or primary payment method client defined id is invalid

Associated Inputs: primary_payment_method_idx, primary_client_payment_method_id


26020: Provided secondary payment method idx or secondary payment method client defined id is invalid

Associated Inputs: backup_client_payment_method_id, backup_payment_method_idx


26021: Invalid billing group idx

Associated Inputs: billing_group_idx


26022: Invalid dunning group idx

Associated Inputs: dunning_group_idx


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


26031: Client payment terms id not found.

Associated Inputs: client_payment_term_id


26032: Payment terms is not available for the account .

Associated Inputs: payment_terms_no, payment_terms_name, client_payment_term_id

Additional Comments: The payment_terms_no must be mapped to the acct_group_no.


26034: Payment terms not found.

Associated Inputs: payment_terms_no, payment_terms_name, client_payment_term_id


26035: Invalid Payment option.

Associated Inputs: payment_option

Additional Comments: The payment_option is not "TERMS" or "METHODS".


26036: Payment Terms Required.

Associated Inputs: payment_option, payment_terms_no, client_payment_term_id

Additional Comments: The payment_option is "TERMS" and the payment_terms_no or client_payment_term_id was not entered.


26037: EAN GLN number and EAN GLN requisition numbers are required for EAN GLN Payment Terms.

Associated Inputs: payment_terms_no, payment_terms_name, client_payment_term_id, ean_gln_num, ean_gln_requisition_num

Additional Comments: The payment_terms_no is valid and requires that ean_gln_num and ean_gln_requisition_num values are entered, but these values were not entered.


27001: Invalid fulfilment directive

Associated Inputs: fulfillment_directive


27002: The fulfilment service provided is already invoiced.

Associated Inputs: service_no, client_service_id


27003: invalid plan unit instance

Associated Inputs: plan_unit_inst_no


27004: invalid plan unit instance id

Associated Inputs: client_plan_unit_inst_id, new client_plan_unit_inst_id


27005: The service provided is not a fulfillment based service.

Associated Inputs: service_no

Additional Comments: The entered service_no must be a  a fulfillment based service.


27006:The fulfillment date should not be provided in the future for the immediate fulfilment directive

Associated Inputs: service_fulfillment_date


27007: The fulfillment date should not be provided before account creation date

Associated Inputs: fulfillment_directive, service_fulfillment_date, acct.created

Additional Comments: The fulfillment_directive is immediate and service_fulfillment_date is before the acct.created date.


27008: The fulfilment date should not be provided beyond billing period. The fulfillment date must not be outside the current billing

Associated Inputs: service_fulfillment_date


27009: The fulfilment date should not be provided in past when fulfilment directive provided as future

Associated Inputs: service_fulfillment_date, fulfilment_directive


27010: The fulfilment date should be provided when fulfilment directive provided as futureThe fulfillment date cannot be blank when the fulfillment directive indicates a future fulfillment date

Associated Inputs: .service_fulfillment_date, fulfilment_directive


27016: Since this account does not have a retroactive start date, the service fulfillment date must be the same as the current date when fulfillment_directive = 1.

Associated Inputs: fulfillment_directive, service_fulfillment_date

Additional Comments: The fulfillment_directive is immediate (1) and the service_fulfillment_date is not the current date.


27017: Eligible service no/service id is required when Eligible fulfillment date/fulfillment directive is specified.

Associated Inputs: service_fulfillment_date, fulfillment_directive, client_service_id, service_no

Additional Comments: Service_fulfillment_date and fulfillment_directive were entered and the client_service_id or service_no was not entered.


27019: Invalid fulfillment directive as the account start date is in future.

Associated Inputs: fulfillment_directive (1), alt_start_date

Additional Comments: The fulfillment_directive is immediate (1) and alt_start_date is in the future.


27020: Fulfillment date cannot be earlier than start date.

Associated Inputs: service_fulfillment_date


27022: Since this account has a retroactive start date, the service fulfillment date must be on or after the account's retroactive start date and on or before the current date when fulfillment_directive = 1.

Associated Inputs: fulfillment_directive, service_fulfillment_date, retroactive_start_date

Additional Comments: The fulfillment_directive is immediate (1) and service_fulfillment_date falls before the retroactive_start_date.


27024: Duplicate plan unit instance index in input

Associated Inputs: plan_unit_inst_idx


29004: Provided contact idx is invalid.

Associated Inputs: contact_idx, bill_contact_idx, stmt_contact_idx, dest_contact_idx, item_dest_contact_idx

Additional Comments: When there is no matching map index available for acct_contact_idx, contact_idx, bill_contact_idx, stmt_contact_idx, dest_contact_idx, item_dest_contact_id, this error occurs.


29005: The contact number provided is invalid for the specified account.

Associated Inputs: acct_contact_no, bill_contact_no, stmt_contact_no


You must to post a comment.
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.