| Table of Contents | ||||
|---|---|---|---|---|
|
Capability
The GLA Charges Import allows a This Import will allow the User to add or update Charges to any existing GLAon GLAs for Billing.
By default this import will always Add new charges, not Update existing charges. Care should be taken, as this can create duplicate charges.
There is an optional UPDATE Flag that can be set to force the import to do Updates instead of Adds.
The import cannot delete existing charges, but it can set an existing MRC charge Stop Date to end the charge.
Matches On
This Import looks up GLAs based on the GLA Full Codes.
...
For adds and updates, the import will need the 'GLA Full Codes' to find the GLA record to apply the charge to.
For updates, the import needs to find the charges to update.
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.
Fields
GLA Full Codes
Required
...
This is a full sequence of GLA Components separated by the GLA_CONCATENATOR .
Multiple levels of a hierarchy "path" (like Locations) are connected by the HIERARCHYPATH_SEPARATOR string.
The default value for this string is right angle-brace (>) with a space on either side: " > ".
When importing nested LocationsGLA's, the separator you use for each level of the hierarchy must match the concatenator string.For example, Site A > Building B > Room C.
Charge Catalog Name
Required
...
For a multi-level Department Hierarchy the Full Path of the Hierarchy MUST be used.
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 String.
...
Override Amount
Datatype is String Number.
This is only allowed if the Charge Catalog entry allows overrides.
...
All other values enter as False [0].
Quantity
Datatype is String Number.
Stop Date
Data type is String.
...
New Override Amount
Data type is String Number.
This is only allowed if the Charge Catalog entry allows overrides.
Used for UPDATE only.
New Quantity
Data type is string Number.
Used for UPDATE only.
RECID
Data type is String Number.
Used as a lookup for Charge updates.
Effective Date
Data type is String.
Expected values are Backdate and Today.
Billing Group Override
Data type is String.
...
UPDATE:
Default vales is UPDATE
If set, this import will UPDATE existing records.
If the import cannot find an existing record to update, it will error. If the UPDATE flag is set, the import only updates existing charges.
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.
Expected values are Backdate and Today.
See the Notes for more details.
Warnings and Errors
The following warnings display if the Service Charge UPDATE fails:
...
- 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>
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.To find an existing charge for UPDATE, the following fields are required: GLA, Charge Catalog, and Charge Type. The following additional fields are used if provided: Start Date, Override Amount, and Quantity. Alternatively, the Service Charge RECID can be provided which overrides all other provided key values.
- If an NRC has been billed, it cannot be updated in any way.
- If an existing MRC has been billed, it can be updated. Changing the GLA, Amount, Quantity, or Prorate Flag, the new Charge stops the previous Charge and a new Charge record begins with the appropriate changes. The Stop Date becomes the day before the import was run. The Start Date becomes the day the import was run.
...