Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
outlinetrue
stylenone

Capability

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.

...

At minimum, you must provide the GLA, Charge Catalog and Charge Type. You can also optionally provide the Start Date, Override Amount, and Quantity.                                                                                                                               

If the values you provide match more than one charge, then all of those that match will be updated.

Alternatively, you can provide the GLA Charge RECID, and this will override all other key values to find the exact GLA Charge to update.

...

GLA Full Codes

Required

Datatype is Hierarchical String.

Charge Catalog Name

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

...

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'.

...

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.

Owner Contact Customer Number

...

Owner Dept. Hierarchy

Datatype is Hierarchical String.

Import matched the Department Hierarchy Code, not the Name.

...

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

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

...

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.

Errors

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

  1. 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>'


  2. The value provided from another table is Inactive

    Toggle cloak


    Cloak
    • Error : Trying to use Inactive Charge Catalog <chargeCatalogName>


  3. 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"


  4. 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
    • 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


  5. 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
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.

  • For an existing Monthly Recurring Charge, if you update the GLA, Amount, or Quantity, it 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.

  • If you update existing Alternate Recurring Charges (Quarterly, Semi-Annual and Annual), they will stop and start like MRCs, but they will always behave as if the Effective Data is set to 'BACKDATE'.

Child pages (Children Display)
styleh6
sorttitle