The core functionality not to support Basic non-support functionality for simplified migration of financing contracts is located in the Role Center OneCore - – Migration Role Center.
Current content of the Role Center:
Choice | Meaning | Note |
Difference Contract Check | Overview of contracts for which differences have been checked with results | The content is generated by the Mass Contract Check task |
Migration Processing Log Contracts | Overview of entries in the log, where there are records of the progress of tasks, such as Contract Recalculation, Activation of Migrated Contracts, etc. | Logging includes both success and any errors found. |
Migration - Posted Payments | Overview of records in the auxiliary table to mark migrated contract payments as posted | The table is filled by import via the configuration package and processed by the Mark posted/unposted task. Installments |
Configuration Packages | Quick access to the standard overview of configuration packages |
|
Mass Contract Check | A batch job that performs a contract recalculation to check and compare whether the key indicators after the recalculation of the contract are shgodly with the migrated ones | The result is in the Contract Difference Check overview |
Migrated Contracts Activation | Batch Job to Activate Migrated Contracts |
|
Migrated Contracts Overview | Report with output to Excel for creating a checklist of migrated contracts |
|
Recalculation of Migrated Contracts | Batch Job for Recalculation of Migrated Contracts |
|
Mark posted/unposted. Installments | A batch job that, based on the contents of the pre-prepared Migration – Posted Payments table, marks the payments in the payment calendars of the monitored contracts as posted without posting documents | The function allows both setting and reversing (deletion of markings) |
All Contracts tile | Overview Difference Contract Check Without Filtering |
|
Bad Contracts tile | Overview Contract Difference Check with filter for contracts with recalculation error |
|
Different Contracts tile | Overview Contract Difference Check with filter for contracts with recalculation difference |
|
Features and overviews are described later in the individual chapters.
...
If migravane contracts are entered into a new system manually, OC allows you to create a contract (i.e. not an offer, but a contract) with a manually entered (existing) number. This option exists only for contracts without services.
A contract can be created using the Create Calculation/Contract Wizard.
...
When the Next button is pressed, the OC system will perform the following checks:
If the user does not fill in the Contract No. and confirms the Next button, the OC will display a message that the Contract No. cannot be empty.
If the user fills in the Contract No. and confirms the Next button, the OC will check whether there is a contract (calculation) with the entered number in the system. If it exists, it will display a message that the contract number already exists.
If the checks are passed, the user continues to create the contract as usual, in steps 2/3 and 3/3 there is no special setting for migrated contracts.
Contract Card and Contract Activation
...
Don't Post Down Payment on Activation (Down Payment Posting Blocked) = A
Don't Allow Initial Fee Posting Blocked on Activation (Initial Fee Posting Blocked) = A
The OC will not charge As part of the activation, the OC does not post a down payment or entry fee as part of the activation(an essential requirement for migration).
If an Instalment Sales contract has been activated and flag has been set on the Contract Financing Product:
...
Example migration using configuration packages:
Package Name | Tables/Tables Included | Data entities | Note |
SIM_CONTACT
| 18 Customer 5050 Contact 5051 Contact Alt. Address 5054 Contact Business Relation | Customer Contact Contact Address Contact and Customer Relation | Contract Client Migration |
SIM_0_DIM_VALUE | 349 Dimension Value | Contract Numbers to Table Dimension Values | Prerequisita before contract migration; Dimension No. 2 must be set before import Contract |
SIM_1_CONTRACT | 4026397 API Financing Contract Header | Contract Headers | Both the order and the use of validations of individual fields are important here |
SIM_2_OBJECT | 4026560 API Financed Object | Financed Objects for Contract Headers | Both the order and the use of validations of individual fields are important here |
SIM_3_CALCINP | 4026450 API Contract Calculation Input | Calculation Inputs – Contract Value Data | Value data in calc. inputs must match the values from the header of the contract or other migrated data |
SIM_4_GUARANTEE | 4026447 API Contract Guarantee | Contract Guarantee | Data is not mandatory |
SIM_5_LICENSE_PLATE | 4026584 API License Plate History | License Plate History | Data is not mandatory |
SIM_6_MIGR_POSTED_P | 4046950 API Migration - Posted Payment | Flags that contract payment calendar lines have already been posted | The data is not mandatory, it is an adjustment of the data generated by the system when activating contracts (payment calendars) based on the posting status of payments in the periods before the migration date |
Note: This setting is available in the database with the client's web address https://onecore-20test-cz.iao.soliteaseyfor.netcom/BC/ (information as of 15.10.2022) and individual packages are exported including a sample Excel table in the following directories:
File Type | Directory | Note |
Exported Configuration Package |
|
| Status as of 15.10.2022 | ||||
Exported Excel file |
|
| Status as of 15.10.2022 |
Note 2: under certain circumstances (e.g. changes in the table??), the order of columns in the field list of the migrated table may be changed – the changed request is renumbered according to the sequential field numbers; The order is is an integral part of the package definition and must be used exactly as defined in the package, or in the Excel spreadsheet that was created from the package, and not according to this default setting.
...
Role Center: OneCore - Migration
A prerequisite for running the task is that the status of the contracts after import allows for recalculation of the contract (e.g. contracts are in the Signed status). The program skips independently of the specified contract filter, where Status >=Active.
...
The task performs the Payment Calculation function on the selected contracts and saves the result in the contract header, where the amounts can be checked on the contract card on the Calculation tab after the end of the run.
In the event of an error occurring over the migrated data, a record of the occurrence of the error is made in the Recalculation Error Log (API Recalculation Error Log (4046810)), which is also recorded in the case of successful recalculation.
Note: Due to the fact that the recalculation will overwrite the fields on the contract header, which may have contained the original payment amounts from the migration, it is necessary to combine the original data (e.g. the migration input data to migration) and the resulting data after the recalculation when comparing the payment amount before and after the recalculation.
...
Role Center: OneCore - Migration
A prerequisite for running the task is that the status of the contracts after import allows the contract to be activated according to the settings of Detailed Contract Statuses and their sequences.
...
The task for the selected contracts activates the contract and writes the result (successful or with error) to the Migrated Contract Processing Log (API Migr. Cont. Batch Log (4046951)).
Example of a log:
...
Once activated, the contracts are ready to be processed.
...