OneCore Docs
Breadcrumbs

Creating Calculation/Contract by Copying

It is possible to copy the Calculation or the Contract Create > Copy Calculation/Contract and the user confirms that they really want to copy and whether they want to view the new contract.

After confirming Yes, the system will check:

  • If a calculation is being copied (the detailed contract status shows Calculation = A), the OC will check the Offer Creation Date and Validity Period to enable contract copying in OneCore Settings:

    • If the offer creation date + Validity period to allow copying is > the current date, the OC will not allow copying:

    • If Offer Creation Date + Validity Period for Enabling Copy =< current date, OC will copy and create a new calculation.

Once confirmed, the system will check:

  • Flag Mandatory Quote ApprovalOneCore Setup. If the value of the field will be:

    • Yes

      • Displays the message "Approval of the quote is mandatory, it is not possible to create a copy. (Quote Approval is mandatory, it is not possible to create a copy)".

    • No

      • Proceeds to the next review

  • If copying from a change copy, variant or from a contract with a change copy is not running:

    • If so, the copy stops. "It is not possible to create a calculation/contract from the variant."

    • Or: "It is not possible to create a calculation/contract from the change copy."

    • Or: "The contract cannot be copied, it must be in a status from Offer to Suspended"

    • If not, it continues

  • If the calculation is being copied (the detailed contract status shows Calculation=A), the OC will check the Offer Creation Date and Validity Period to enable contract copying in OneCore Settings:

    • If Offer Creation Date+Validity Period to Allow Copy is > current date, OC will not allow copying:

    • If Offer Creation Date+Validity Period for Permit Copy =< current date, OC will copy and create a new calculation.

  • If the contract is being copied (the detailed contract status shows Calculation=N), the OC will perform a check

    • Contract Creation Date and Validity Period to enable contract copying in OneCore Settings:

      • If the Contract Creation Date + Validity Period to allow copying is > the current date, OC will not allow copying.

      • If Contract Creation Date + Validity Period for Permit Copy =< current date, the OC proceeds to the next check.

    • Contract Status:

      • If > Status is Active, it will not allow contract copying

      • If Status is < = Approved, Signed, or Active

  • If the contract is being copied (the detailed contract status shows Calculation = N), the OC will perform a check

    • Contract Creation Date and Validity Period to enable contract copying in OneCore Settings:

      • If the Contract Creation Date + Validity Period to allow copying is > the current date, the OC will not allow copying:

      • If Contract Creation Date + Validity Period for Permit Copy =< current date, the OC proceeds to the next check:

    • Contract Status:

      • If > Status is Active, it will not allow contract copying

      • If Status = Approved, Signed, or Active

  • By copying, the system creates a calculation or contract as the original image, performing the following actions:

    • The new entity will be created as the original image, but some data will be different from the source entity (described below)

    • A new entity will be created with a number and detailed status as follows:

      • If a calculation is being copied:

        • The new entity will receive a number from the number series for calculations according to the Financing Model in the Calculation Nos field,

        • The new entity will get a detailed status according to the Initial Detailed Calculation Status setting in OneCore Settings. Also, the Calculation Creation Date will have the current date

        • If the original calculation contains records in the Approval History, these will not be copied to the new calculation

      • If a contract is being copied:

        • The new entity will receive a number from the number series of contracts according to the Financing Model, the Contract Nos field.

        • The new entity will get a detailed status according to the Initial Detailed Contract Status setting in OneCore Settings. Also, the Contract Creation Date will have the current date

        • Global Dimension 2 (Contract Code) will be added to the new contract New Contract No.

    • All numbers that are based on the calculation/contract number (e.g. object number) will be renumbered in relation to the new entity number

    • Insurance contracts within the new entity will be renumbered according to their number series

    • Approval Date and Signature Date are deleted if they were filled in in the source quote/contract

    • The last modified date and time is overwritten to the current system date and time

    • Changed will be overwritten according to the logged-in user

    • Created By (field not pulled on the Financing Contract tab) is overwritten according to the logged-in user

    • If they were filled in in the original calculation/contract, the following will not be transferred to the new entity:

      • Item No.

      • Chassis No. (VIN)

      • Serial Number

      • Registration Plate No.

      • VTP/OEV No.

      • Green Card No.

      • Links to the Agreement.

    • If a contract is copied and the Approver ID and Approval Protocol ID fields have been filled in, these values will not be transferred to the new entity

    • If the original contract contains any posted or posted items, they will not be transferred to the new contract

    • Payment calendars (contracts, services, and insurance) will not be transferred to the new entity:

      • Flag Complete calculation(4047060)) = will be set to N

      • Records in the Payment Calendar (API Financing Contract Line (4026398)) will not be transferred – i.e. the new entity will always be without a payment contract

      • Records in the API Service Payment Line (4026683)) will not be transferred – the new entity will be without payment cal. Services

      • Records in the Client Insurance Calendar (API Ins. Client Payment Cal. (4027105)) will not be transferred – the new entity will be without payment cal. poj. Client

      • Records in the Insurance Company Calendar (API Ins. Company Payment Cal. (4027106)) will not be transferred – the new entity will be without payment cal. Insurance

      • Entries in the Commission Calendar (API Ins.Comm. Payment Calendar (4027107)) – the new entity will be without payment cal. Commission

    • If the original contract contains Attachments to the Agreement and/or Subject Matter, these attachments will also be copied

    • If the original contract contains records in the Approval History, these will not be copied to the new contract

    • After the copy is created, you will see the message: "Contract No. OL00003 has been created. Do you want to see it?"

CZ localization (Luxury Tax):

If the user copies a calculation/contract created before the legislative change came into effect, then it is necessary to open the calc overview. inputs and close it again – the system will add the calculation input to the unclaimed part of the VAT, if necessary, and then recalculate the contract instalments.