CARL Source
Settings

CARL Source is configured by setting several parameters that determine how certain processes operate.
Certain settings depend on the Profile, see Profile Settings.

 

Key Features

These values apply to all users within the application.
The settings are grouped on a single screen and organized by module.

  1. Go to the [System] and select [Module Settings] present in the block [Settings].
    → The list of key settings for a module is displayed on the right side of the screen once the module is selected.

  2. Edit the values and confirm.
    → The values will be applied immediately or the next time you log in, as appropriate.

 

Equipment Module

Parameter

Behavior

Email template (MEASUREREADINGTMPL)

Code of the message template Email to be sent in the event of measurement reading beyond the limits.

Criteria from the WR due to unavailability Asset (UNAVAIL_MRCRITERION)

Attribute of the WR which sets the value of the "Asset "unavailable".

Criterion value from the WR due to unavailability Asset (UNAVAIL_MRVALUE)

Value of the criterion WR for which the "Asset "Unavailable" is checked by default. If there are multiple values, they should be entered in the format [VALUE1, VALUE2, etc.], where VALUE1 and VALUE2 are the codes for the values.

Location Structure / Tree structure (LocationTreeViewStructure)

The code for the structure displayed by default when calling up the Tree structure for a Location.

A generic value that can be overridden by the User Profile parameter of the same name.

Method for Allocating an Energy Invoice (REPARTITION_MODE)

Allows you to specify whether the breakdown of the energy invoice This is done manually or by using the allocation information from the most recent energy invoice.

Equipment Type Group 1 for Specific Assets (Eqpt1TypeGroup1)

Define an initial group of asset types that determines specific behavior or display settings for these assets within the software’s features. Asset , WR, work orders, WO reports.

In the business context TRANSPORTATION, this value must be set to FIXE if the default groups are used. This value is customizable.

Group 2: Equipment Types for Specific Assets (Eqpt1TypeGroup2)

Define a second group of asset types that triggers specific behavior or display settings for these assets within the software’s features. Asset , WR, work orders, WO reports.

In the business context TRANSPORTATION, this value must be set to "ROULANT" if the default groups are used. This value is customizable.

 

Work Module

Parameter

Behavior

Prohibits closing a work order if actions are still required (CLOSE_WO_CTRL).

If this box is checked, it is not possible to close a work order if there is at least one remaining process operation ofevaluation Action: "Create" a WR" or "Create a work order," and for which WR or the work order has not been created.

Prohibited from closing a diagnostic if actions are required (CLOSE_DIAG_CTRL).

If this box is checked, it is not possible to close a diagnosis if there is at least one remaining process operation ofevaluation Action: "Create" a WR" or "Create a work order," and for which WR or the work order has not been created.

Updating work order dates/occupancy dates, process operations (OCC_UPDATE_WODATE).

Indicates whether it is possible to enter a Labor reporting, a Process operation or a consumption excluding the dates of the work order, which are then updated.

Re-billing Coefficient for Purchased Supplies (RATE_ITEMCOST).

Multiply the purchase cost coefficient for work order items, for use in quote reports intended for rebilling.

Labor Re-billing Rate (RATE_LABOURCOST).

Coefficient used to initialize the rebilling coefficient for Specialties.

Miscellaneous Billing Coefficient (RATE_MISCCOST).

A multiplier coefficient for the costs of work order process operations, for use in quotes intended for rebilling.

Service Billing Coefficient (RATE_SERVICECOST).

Multiplier coefficient for the purchase costs of work orders, for use in quote reports intended for rebilling.

Inventory Rebilling Coefficient (RATE_STOCKCOST).

Multiplier coefficient for the costs of materials consumed during a work order, for use in quotes intended for rebilling.

Replace Location point by the ascendant of the Main point (REPLACE_LOCATION).

When entering a WR or a work order, when the user enters the Main point, CARL Source Research Location point which contains this Main pointIf this box is checked, Location point possibly already entered in WR or the work order will be replaced by the one found.

Updating scheduled work order dates / planned resource dates (UPDATE_WODATE).

CARL Source allows resources (human and other) to be entered outside the start and end dates of thework order, which will then be updated.

Data refresh following return to details (WOS_DATE_REFRESH).

After changing the date in the details of an open work order created through the scheduling module, the macro-planning and the assignment table are automatically updated.

Current color criteria for GANTT bars (WO_COLORCRITERIA).

Attribute used to determine the color of the bars in the work order scheduling, including priority, status, and Type of work order.

Scheduling smoothing horizon (WO_PLANNINGHORIZONSMOOTHING)

Specifies, in number of days, the smoothing horizon for the work order schedule.
This refers to the number of days in advance that the work order is created relative to the trigger date.

Document type: Quotes for accidents (DAMAGEDOCTYPE)

Specifies the document type for "Accident" quotes.

Updating scheduled work order dates / planned resource dates (UPDATE_WODATE).

CARL Source allows users to enter resources (human and other) outside the start and end dates of thework order, which will then be updated.

Default process operation type based on mapping (WO_GIS_DEFAULT_PROCESS).

Default process operation type for initializing process operations based on the map.

Default process operation type based on mapping (WO_INIT_MAIN_ADDRESS_WTH_WOPRC).

Initialization of the main address with the first geolocated process operation.

OptaPlanner - Search Slot Definition Range (WO_OPTA_PERIOD).

Range for defining search time slots for automatic resource assignment (Day, 4 hours). The "Day" value is selected by default.

OptaPlanner - No time to define search windows (WO_OPTA_STEP).

Time interval value used to define search windows for automatic resource assignment (30 minutes, 1 hour, 2 hours, 4 hours). The default value is “1 hour.”

OptaPlanner: Assignment job timeout (in minutes) (WO_OPTA_TIMEOUT).

Maximum duration of the automatic resource assignment process before the process is terminated (in minutes). The default value is set to 10 minutes.

OptaPlanner: Wait time without solution improvements (in seconds) (WO_OPTA_UNIMPROVED_TIME).

The maximum waiting time before the solution is deemed the best available. The default value is set to 5 seconds.

 

Resources Module

Parameter

Behavior

Number of days limiting the generation of work order completion reports (PAYMENTHORIZON).

This setting determines the time horizon beyond which completion reports are not suggested.

  • For each work order, a completion date is calculated (based on whether the deadline has passed or is still to come).
  • If this date is within the limit of the current day + this parameter, the line is displayed.
  • If it exceeds this limit, the line is not generated.

Example: For a 30-day period starting today through September 15, 2025, only work orders with a date on or before 10/15/2025 appear.

Automatically fill in discrepancies between work orders (PAYMENT_AUTO_GAP_FILLING).

When enabled, this setting ensures that no period remains unbilled between two invoices: the missing period is calculated on a pro-rata basis, and a supplementary invoice is automatically generated to fill the gap.

Monitoring of work durations against the maintenance schedule (TIMETABLECTRL).

In the Occupations, CARL Source will prevent users from entering more hours of labor reporting than the hours declared in the calendar Technician.

Automatic generation of PR orders from the Contract (CREATE_CONTRACTPR).

Upon validation of a period of Contract For each work order, purchase requests will be generated automatically based on the entries made in the [Schedule] tab.

"Daily" View (PLANNING_DAY)

Determines whether the "daily view" is included in the selection of views in the resource planning.

"Day" view: no time (for a cell—minutes) (PLANNING_DAYSTEP)

In the "Day" view of the resource planning, the scheduler will divide the workspace into vertical columns based on the specified time (in minutes). Recommended value: 60.

"Day" view: no travel required (PLANNING_DAY_MOVE_STEP)

In the "Day" view of the resource planning, the graphical movement of an activity on the schedule is done in time “steps” of the specified value (in minutes). Recommended value: 15.

"Day" view: no zoom in or out (PLANNING_DAY_RESIZE_STEP)

In the "Day" view of the resource planning...the time "increment" for graphically modifying the duration of a scheduled activity is set in time increments equal to the specified value (in minutes).

"Work Week" View (PLANNING_WEEK)

Determines whether the "Week" view is available in the list of views resource planning.

"Week" view: no time (in a cell—minutes) (PLANNING_DAYSTEP)

In the "Week" view of the resource planning, the schedule will divide the workspace into vertical columns based on the specified time (in hours). Recommended value: 2.

"Week" view: no travel (PLANNING_WEEK_MOVE_STEP)

In the "Week" view of the resource planning... The graphical movement of an activity on the schedule is performed in time "steps" of the specified value (in minutes). Recommended value: 60.

"Week" view: no zoom in/out (PLANNING_WEEK_RESIZE_STEP)

In the "Week" view of the resource planning...the time "increment" for graphically modifying the duration of a scheduled activity is set in increments of the specified value (in minutes).

"Work Fortnight" View (PLANNING_FORTNIGHT)

Determines whether the "Fortnight" view is available in the list of views resource planning.

"Fortnight" view: no time (for a cell—minutes) (PLANNING_FORTNIGHTSTEP)

In the "Fortnight" view of resource planning, the schedule will divide the workspace into vertical columns based on the specified time period (in hours). Recommended value: 2.

"Fortnight" view: no travel required (PLANNING_FORTNIGHT_MOVE_STEP)

In the "Fortnight" view of the resource planning... The graphical movement of an activity on the schedule is done in time "steps" of the specified value (in minutes). Recommended value: 60.

"Fortnight" view: no zoom in/out (PLANNING_FORTNIGHT_RESIZE_STEP)

In the "Fortnight" view of the resource planning...the time "increment" for graphically modifying the duration of a scheduled activity is set in increments of the specified value (in minutes).

"Monthly Work" View (PLANNING_MONTH)

Determines whether the "Month" view is available in the list of views for the resource planning.

"Month" view: no scrolling (PLANNING_MONTH_MOVE_STEP)

In the "Month" view of the resource planning... The graphical movement of an activity on the schedule is performed in time "steps" of the specified value (in minutes). Recommended value: 120.

"Month" view: no zoom in/out (PLANNING_MONTH_RESIZE_STEP)

In the "Month" view of the resource planning...the time "increment" for graphically modifying the duration of a scheduled activity is set in increments of the specified value (in minutes).

"x-day" rolling view (PLANNING_FORTNIGHT)

Determines whether the sliding view is available in the view selection menu of the resource planningas well as the number of days in the view.

"x-day" rolling view: no time (in a cell—minutes) (PLANNING_FORTNIGHTSTEP)

In the scrollable view of the resource planning, the schedule will divide the workspace into vertical columns based on the specified time (in hours). Recommended value: 2.

"x-day" rolling view: no scrolling required (PLANNING_FORTNIGHT_MOVE_STEP)

In the scrollable view of the resource planning... The graphical movement of an activity on the schedule is done in time "steps" of the specified value (in minutes). Recommended value: 60.

"x-day" rolling view: no zoom in/out (PLANNING_FORTNIGHT_RESIZE_STEP)

In the scrollable view of the resource planning...the time "increment" for graphically modifying the duration of a scheduled activity is set in time increments equal to the specified value (in minutes).

Start date for filtering the shopping cart (PLANNING_DEF_STARTDATEFILTER)

Set the start date for the default filter of the work order basket.

End date for filtering the shopping cart (PLANNING_DEF_ENDDATEFILTER)

Set the end date for the default filter of the work order basket.

Resource(s) displayed (PLANNING_DISPLAYPRES)

Determines the type(s) of Resource(s) displayed in the resource planning

Default duration of an activity (minutes) (PLANNING_DURATION)

Sets the default duration when creating a task.

First day of the workweek (PLANNING_FIRSTDAY)

Determines the first day of the workweek displayed in the resource planning.

Primary sorting attribute for Sections (PLANNING_SECTIONFILTERATT)

Specifies the default sort attribute for resources in the resource schedule.

Monitoring Planned Resources (PLANNING_UNPLANNEDRSRCALLOC)

Specifies the type of check performed to ensure consistency between the resources initially assigned to a work order and the resource to which the work order is to be assigned. By default, set to "Notify."

Number of days in a workweek (PLANNING_WKNBDAYS)

Specifies the number of days of the week displayed following the first specified day.

An attribute whose value determines the color of a work order (PLANNING_WOCOLORATTR)

By default, the colors of activities on the schedule are based on the attribute defined in this setting.

Start time of the workday (PLANNING_WORKBEGIN)

Determines the start time of a day as displayed on the Resource schedule.

End of the workday (PLANNING_WORKEND)

Determines the end time of a day displayed on the Resource schedule.

 

Purchasing Module

Parameter

Behavior

Invoicing Method (INVOICEMETHOD)

If the parameter is set to "BL", the invoice is automatically generated from a delivery note, following a Receipt.

Otherwise, it is created based on the PO.

Invoicing is required to close a PO (INVOICE_LOCK_POCLOSE)

In all cases, if invoicing is pending, the invoice must be paid in full before the PO can be closed.

If the parameter is set to "Yes", a PO can be closed off only if there has been Invoicing.

If the parameter is set to "Disclaimer", a confirmation message will appear when the PO is closed if no invoice has been created.

If the parameter is set to "No", a PO without an invoice may be closed without prior notice.

Creating multi-budget POs (MULTI).

Indicate whether it is possible to create a PO containing lines assigned to Budgets distinct.

Automatic closure of PO's that have been fully received (PO_AUTO_CLOSED)

If the box is checked, as soon as the quantity for each line in the PO has been entirely received, the PO is automatically marked as "Closed" (unless Invoicing is required or in progress; see the "Invoicing required to close a PO" setting).

Automatic closure of fully invoiced POs (PO_INVOICED_CLOSED)

If the box is checked, the balance from the last Invoice (If multiple invoices have been issued) triggers the creation of the corresponding PO(s), provided the following conditions are met:

  • POs are fully processed,
  • The "Automatically settle received POs" setting is checked,
  • POs have been fully invoiced, and the other invoices have been closed,
  • The user is authorized to close the invoice.

Confirm a PO without a quantity (PO_VALID_QUANTITY_ZERO)

If the checkbox is selected, it will be possible to confirm a PO even if the quantity on the line is 0.

Automatic reconciliation of fully received PRs (PR_AUTO_CLOSED)

If the box is checked, as soon as the quantity for each line in the Purchase request was received...the purchase request automatically changes to the "Closed" status.

Complete existing PO's (PR_POCOMPLETION)

If the box is checked, the conversion of Purchase request en PO It adds lines to existing POs whenever possible (if there is an open or unconfirmed PO placed with the same Supplier).

Email model for creating a PO from a PR (TMPL_CREATEDFROMPR).

Determine the Message model Sent to the requester when their purchase request is converted into a PO.

Email model for the PO (TMPL_REPORT).

Determine the Message model for PO's submitted by the user via email.

Delay Coefficient (LATECOEFF)

Determines the delay coefficient used in calculating the Supplier quality index.

Litigation ratio (LITIGATIONCOEFF)

Determines the dispute coefficient used in calculating the Supplier quality index.

LDA Coefficient (PRLINECOEFF)

Determines the weighting of Purchase request lines in the calculation of the Supplier quality index.

Invoicing Entries (INVOICE_BUDGMVTDATE)

Whether an invoice can be recorded depends on the value of the INVOICE_BUDGMVTDATE parameter (Are invoicing entries conditional on the date entered?).

  • If the parameter is not checked (False)
    Budget entries recorded as invoiced expenses are posted (upon settlement of the invoice) with an allocation date equal to Today's date (system date).
  • If checked (True)
    Budget entries are recorded with an allocation date equal to Date entered on the General tab of the invoice (accounting entry).
    This feature provides flexibility in cost allocation, which is useful for managing and controlling expenses on a year basis.
    It includes controls designed to ensure a consistent sequence of journal entries resulting from the purchasing cycle:
  1. When an order is received, the Delivery note’s receipt date must be on or after the PO’s creation date. Otherwise, a message will appear blocking the User: “The delivery date cannot be earlier than the PO’s approval date.”
  2.  On an invoice, the accounting entry date must be on or after the Receipt date:

If invoicing is on a PO basis, then the receipt date corresponds to the first date on which the Delivery notes were received,

If invoicing is based on a delivery note, then the receipt date corresponds to the date the delivery note was received,

Otherwise, when closing the invoice, a message appears: “ The date of the accounting entries must be on or after {deliveryDate} ".

  1. We verify that invoicing occurs after the receipt date—either in the year corresponding to the receipt date or in a year following that of the receipt. An invoice entry cannot be assigned to a prior year for a purchase received in the current year.

Otherwise, when closing the invoice, a message appears: “ The date of the accounting entries must be on or after {deliveryDate} »

How to create Asset purchasing, receipt, and inventory (DELIV_CREAT_MATERIAL)

In the case of a two-step PR/PO receipt process, the Asset Items from inventory purchases can be created:

  1. Upon item entry into inventory (default value),
    For a serialized item WITHOUT Receiving inspection on Asset will be created upon receipt/item entry (simultaneous action)
    For a serialized item WITH Receiving inspection on Asset will be created during item entry.
  2. Upon receipt.
    For a serialized item WITHOUT Receiving inspection on Asset will be created upon receipt/item entry (simultaneous action)
    For a serialized item WITH Receiving inspection on Asset will be created upon receipt.

Breakdown of deliveries by PO line via Client (PO_CUSTOMER)

Enables the option on the PO form to select a delivery schedule for order lines based on the associated Client.

Breakdown of deliveries by PO lines via Management (PO_DEPARTMENT)

Enables the option on the PO form to select a delivery allocation for order lines based on the associated department.

Enable automatic approval of a reconciled invoice (INVOICE_IMPORT_AUTO_VALIDATED)

Enables automatic validation of an invoice when the amounts on the imported e-invoice match the amounts on the invoice generated with the PO, subject to the tolerance defined in the profile settings.

Enable automatic balancing of a reconciled invoice (INVOICE_IMPORT_AUTO_CLOSED)

Automatically closes a validated invoice when the amounts on the imported e-invoice match the amounts on the invoice generated with the PO.

Enable e-invoice import (INVOICE_IMPORT_ENABLED)

Enables the import of e-invoices via API and provides a general invoice tab designed for importing invoices.

Approve an invoice without a specified PO number (pre-invoice) (INVOICE_PREINVOICE_ENABLED)

Enables the upload of e-invoices via API even if no matching PO code or original invoice is found in the application. The draft invoice is in read-only mode and will require manual correction.

 

Inventory Module

Parameter

Behavior

Resupply Method (RSTMODE).

Definition of Resupply method : global or by Warehouse.

Type of inventory valuation (STOCKVALUETYPE)

The WAP of the items is calculated and valued by Organization or generally speaking.

Automatic closure of transfer requests that have been fully received (PRINTERN_AUTO_CLOSE)

The transfer requests are marked as "Closed" as soon as the Receipt process is complete for all line items.

 

Module Customers

Parameter

Behavior

Invoicing for an item in stock (STOCKITEM_PRICE).

Setting the invoicing price for an item in stock: WAP or Standard Price.

 

Accounts Module

Parameter

Behavior

Carry forward unfulfilled commitments to the next year at the close of the year (TRANSFER_COMMITTED).

When closing a ExerciseThe remaining amount committed to budgets and cost centers is carried forward to the first day of the following year.

Pricing (including tax) (INCLUDINGTAX_ENTRY).

Inventory valuations and accounting entries are based on the total amount, including all taxes.

Deactivate invalid budgets at the end of the year (INACTIVE_BUDGACC).

At the end of a year, the Budgets Those with an end date earlier than the end date of the closed Year are set to "inactive" status.

Disable the Cost center invalid at the end of the Year (INACTIVE_COSTCENTER).

At the end of a year, the Cost center Those with an end date earlier than the end date of the closed Year are set to "inactive" status.

 

Data Exchange Module

Parameter

Behavior

Default date format for exports (DEFAULT_EXPORT_DATE_FORMAT)

The format used to write dates if the exchange interface does not specify one.

Default format for dates and times in exports (DEFAULT_EXPORT_DATETIME_FORMAT)

The format used to write dates and times if the exchange interface does not specify one.

Default format for hours in exports (DEFAULT_EXPORT_TIME_FORMAT)

The format used to enter hours if the exchange interface does not specify one.

Date and time expressed in UTC in the export (DEFAULT_EXPORT_DATETIME_AS_UTC)

If enabled (true), this setting allows date-times (not just dates or times) to be written in UTC in the generated XML file.

Default format for dates during import (DEFAULT_IMPORT_DATE_FORMAT)

The format used to interpret dates if the exchange interface does not specify one.

Default format for dates and times during import (DEFAULT_IMPORT_DATETIME_FORMAT)

The format used to interpret date and time values if the exchange interface does not specify one.

Default format for hours during import (DEFAULT_IMPORT_TIME_FORMAT)

The format used to read hours if the exchange interface does not specify one.

Date and time expressed in UTC during import (DEFAULT_IMPORT_DATETIME_AS_UTC)

If enabled (true), this setting allows the system to read date-times (not just dates or times) in UTC from the XML file.

NOTE: Even if the value is in UTC in the XML, it will be converted to the time zone currently in effect at that location in the XML document. That is, the time zone specified by a `timezone` attribute on the entity or at the root of the document.

Default agent for imports (IMPORTXMLACTOR)

Code of the Agent CARL Source, which will be logged as having created or modified the data when the import is not performed from within the application (e.g., Mobile or Web Service).

Authentication chain for the default agent in imports (IMPORTXMLAUTH)

Password for the User CARL Source is used when the agent is required (e.g., to import data). It must be preceded by Simple:.
Example: simple:azerty.

It is also possible to specify crypt: .

Maximum size of imported files (in KB) (INBOUNDUPLMAXSIZE)

Item entries that are too large will not be processed by thedata exchange.

 

Notes regarding dates and times during data exchanges.

The format settings described in the table above are not filled in by default, whether during an update or a new installation.

These must be entered manually and adjusted as needed to match the formats used in versions prior to version 5.0.

Starting with version 5.0, the software supports multiple time zones within the same instance: the time zone specified in an exchange is not only used to read or write the value to or from the XML, but is also retained and stored on the business entities.

 

Allowed time zone formats

Here are some examples of time zone formats allowed during data exports and imports: