...
GLA Full Codes
Required
Datatype is String.
This is a full sequence of GLA Components separated by the GLA_CONCATENATOR .
The default value for this string is right angle-brace (>) with a space on either side: " > ".
When importing nested GLA's, the separator you use for each level of the hierarchy must match the concatenator stringHierarchical String.
Charge Catalog Name
Required
Datatype is Hierarchical String.
Instead of mapping this, the value can be supplied for all records in the Import Record Format.
...
Owner Dept. Hierarchy
Datatype is Hierarchical String.
Import matched the Department Hierarchy Code, not the Name.
...
Used for MRCs only and is ignored for NRCs.
Charge Catalog Full Name
Data type Datatype is Hierarchical String.
This can be used in place of the Charge Catalog Name and expects the full catalog Path.
...
UPDATE:
Default Value is UPDATE.
If set, this import will UPDATE existing records.
...
Data type is String.
Default Value is TODAY.
Allowed values are BACKDATE and TODAY.
This flag is used to determine the date that an updated charge will stop and restart.
Alternate Recurring Charges (Quarterly, Semi-Annual and Annual), when updated, will always use BACKDATE as the Effective Date.This flag is only used when updating existing charges. If the import is adding a new charge, then this flag is ignored.
See the Notes for more details.
Warnings and Errors
The following warnings display if the Service Charge UPDATE fails:
Errors
When an Import Line fails, it is usually because the Line falls into one of the following categories:
The value provided from another table was not found, or had multiple matches within the Database
Toggle cloak Cloak - Error : Could not find provided Billing Group <BILLING_GROUP>
- Error : Could not find provided Contact name <fname> <lname>
- Error : Could not find provided Contact number <customerNumber>
- Error : Could not find the Dept Hierarchy for <deptHierarchy>
- Error : "No Matching Charge Catalog entries for '<chargeCatalogName>'
- Error : "Multiple Matching Charge Catalog entries for '<chargeCatalogName>'
- Error : Invalid GLA '<gla>'
- Error : Full Charge Catalog Path <CHRG_CATALOG_FULL_NAME> is Invalid
- Error : Charge Type <CC_CHARGE_TYPE_CODE> is Invalid
- Error : Invalid Charge Catalog '<chargeCatalogName>'
The value provided from another table is Inactive
Toggle cloak Cloak - Error : Trying to use Inactive Charge Catalog <chargeCatalogName>
A blank value was provided, for a field with a required value
Toggle cloak Cloak - Error : Blank or Missing GLA
- Error : No owner provided
- Error : Missing required Owner or Billing Group
- Error : Missing Charge Catalog"
- Error : Missing Billing Group"
The value provided is not acceptable for the record type being created
Toggle cloak Cloak - Warning: Not updating Prorate flag because new Stop Date is before today
- Warning: Not updating Amount because new Stop Date is before today
- Warning: Not updating Override Amount because new Stop Date is before today
- Warning: Not updating Quantity because new Stop Date is before today
- Warning: Not updating Billing Group Override because new Stop Date is before today
- Warning: Not updating Contact Owner because new Stop Date is before today
- Warning: Not updating Dept Hierarchy Owner because new Stop Date is before today
...
The following errors are displayed if the GLA Charges INSERT or UPDATE fails:
...
- Error : GLA '<gla>' is not Billable
...
- Error :
...
- Dept Hierarchy
...
- <deptHierarchy has no Billing Group
- Error : Contact <fname> <lname> has no
...
- Billing Group
...
- Error : Trying to assign amount for Non-Overidable
...
- Charge
...
- Error :
...
- Unable to convert '<BILL_DATE>' into a valid date
- Error : Unable to convert '<STOP_DATE>' into a valid date
The System was unable to save the record
Toggle cloak Cloak - Error : Failed to save GLA_Charges record; <errorMessage>
If you experience any of these Errors, without another accompanying Message about what might have caused the Save Failure, please submit a Ticket to PCR.
Notes
| Anchor | ||||
|---|---|---|---|---|
|
- Any GLA Charge MUST have a valid Owner, either a Contact or a Department Hierarchy.
- By default the GLA Charges import always adds new charges. It never updates or removes charges. This can create duplicates.
- If the UPDATE flag is set, the import will only update existing charges. This can be used to set Stop Dates on MRCs, or change Override Amounts, Quantity, Description, GLA, or Prorate flag.
- If an NRC has been billed, it cannot be updated in any way.
- If an existing Monthly Recurring Charge has been billed, then Updating the GLA, Amount, Quantity, or Prorate Flag, will stop the existing Charge and create a new Charge with the appropriate changes. The date of this stop and start is determined by the Effective Date flag. If this is set to 'TODAY', then it will stop the existing charge with yesterday's date, and start the new charge with today's date. If it is set to 'BACKDATE', then it will use the date that the existing charge has been billed through.
| Child pages (Children Display) | ||||
|---|---|---|---|---|
|