Page Comparison

...

This Import will allow the User to add or update Charges on GLAs for Billing. In order to add a Charge to a GLA, the 'Bill' flag of the GLA Catalog must already be set.

By default this import will always Add new charges, not Update existing charges. Care should be taken, as this can create duplicate charges.

...

GLA Full Codes

Required

Datatype is Hierarchical String.

Charge Catalog Name

Conditionally Required (unless Charge Catalog Full Name is provided instead)

Datatype is StringThis is a full sequence of GLA Components separated by the GLA_CONCATENATOR .

The default value is 'blank'.

The Charge Catalog Name expects just the name, and will only work if the name is unique in the whole catalog.

The GLA_CHARGE_TYPE flag can also be used to help define which catalog you are trying to use.

NOTE: Instead of mapping the Catalog Name or the Catalog Full Name, the Catalog can be set in the Import Record Format.
If the Import Record Format has a value and it is also mapped, the mapped value takes precedence.

Charge Catalog Full Name

Conditionally Required (unless Charge Catalog Name is provided instead)

Datatype is Hierarchical String.

The default value is 'blank'.

This is the full hierarchical path of the Charge Catalog.

This should be used if the Catalog Name is not unique.

The GLA_CHARGE_TYPE flag can also be used to help define which catalog you are trying to use.

NOTE: Instead of mapping the Catalog Name or the Catalog Full Name, the Catalog can be set 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 string.

Charge Catalog Name

Required

Datatype is String.

Instead of mapping this, the value can be supplied for all records in the Import Record Format.

If the Import Record Format has supplies a value and it is also mapped, the mapped value takes precedence.

The name imports if it is a unique value in the catalog.

Owner Contact Customer Number

...

Owner Dept. Hierarchy

Datatype is Hierarchical String.

Import matched the Department Hierarchy Code, not the Name.

...

For example, if the Department, XYZ, is a child to Department, Billing, the Owner Department Hierarchy field should be Billing, XYZ.

Bill Date

Datatype is DateString.

The default value is today's date.

...

Datatype is Number.

Stop Date

Data type is DateString.

Default value is ' blank'.

Used for MRCs only and is ignored for NRCs.

Charge Catalog Full Name

Data type is String.

This can be used in place of the Charge Catalog Name and expects the full catalog Path.

New Override Amount

Data type is Number.

This is only allowed if the Charge Catalog entry allows overrides.

If you map the New Override Amount and provide a blank value, then any existing Override Amount on the charge will be removed.

Used for UPDATE only.

New Quantity

...

Data type is String.

Default value is ' blank'.

The value must match an existing Billing Group.

...

Flags / Conditional Logic

GLA_CHARGE_TYPE:

Default value Value is 'blank'.

This flag is only needed if there are multiple Charges with the same Names that have the different types.

NONRECURRING.

If this is set, it must be set to the code of one of the CHARGE_TYPE List Values from the  List Values  grid.

The only allowed System Use values are the System Use Values: MONTHLY_RECURRING, NONRECURRING, QUARTERLY, SEMI_ANNUAL, and ANNUAL_RECURRING.

UPDATE:

Default Value vales is UPDATE

If set, this import will UPDATE existing records.

...

This can be used to set Stop Dates on MRCs, change Override Amounts, Quantity, Description, GLA, or Prorate flag.

...

Effective Date

Data type is String.

Default Value is TODAY

Allowed Expected 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.

Backdate and Today.

See the Notes for more details.

Warnings and Errors

When an Import Line fails, it is usually because the Line falls into one of the following categories:

...

...

...

...

The following warnings display if the Service Charge UPDATE fails:

• 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 : Invalid GLA '<gla>'
• Error : GLA '<gla>' is not Billable
• Error : Blank or Missing GLA
• 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 owner provided
• Error : Full Charge Catalog Path <CHRG_CATALOG_FULL_NAME> is Invalid
• Error : Charge Type <CC_CHARGE_TYPE_CODE> is Invalid
• Error : Dept Hierarchy <deptHierarchy has no Billing Group
• Error : Contact <fname> <lname> has no Billing Group
• Error : Missing required Owner or Billing Group
• Error : Trying to use Inactive Charge Catalog <chargeCatalogName>
• Error : Trying to assign amount for Non-Overidable Charge
• Error : Invalid Charge Catalog '<chargeCatalogName>'
• Error : "No Matching Charge Catalog entries for '<chargeCatalogName>'
• Error : "Multiple Matching Charge Catalog entries for '<chargeCatalogName>'
• Error : Missing Charge Catalog"

• Error : Missing Billing Group"

• Error : Unable to convert '<BILL_DATE>' into a valid date
• Error : Unable to convert '<STOP_DATE>' into a valid date

...

• 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
Notes Notes

• 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 MRC has been billed, then Updating it can be updated. Changing the GLA, Amount, Quantity, or Prorate Flag, will stop the existing the new Charge stops the previous Charge and create a new Charge record begins 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 throughStop Date becomes the day before the import was run. The Start Date becomes the day the import was run.