...
Default Value is NONRECURRING.
This flag is only needed if there are multiple Charges with the same Names that have the different types.
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 System Use values are: MONTHLY_RECURRING, NONRECURRING, QUARTERLY, SEMI_ANNUAL, and ANNUAL_RECURRING.
UPDATE:
Default vales Value is UPDATE
If set, this import will UPDATE existing records.
...
Effective Date
Data type is String.
Expected 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 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.
...
- Error : Invalid GLA '<gla>'http://2019-7merge.2019-7oracle-merge.dev360.pcr.com/
- 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>
...
- 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 MRC Monthly Recurring Charge has been billed, it can be updated. Changing then Updating the GLA, Amount, Quantity, or Prorate Flag, the new Charge stops the previous will stop the existing Charge and create 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 rundate 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) style h6 sort title