Function and function identifier issues
Covers when to split or reuse function identifiers, when one contract supports multiple functions, and why multiple rows are needed for function and ICT service combinations.
What this issue group covers
This page covers cases where the function itself is not necessarily wrong, but the way it is split and linked in the register is off. In the register, functions follow your own internal organisation, not a fixed official list, and each unique combination of financial entity, licensed activity, and function name needs its own function identifier.
Use this page when you are unsure whether to reuse a function, create another one, or add more rows in the contract detail template. If the problem is the identifier itself, rather than the way functions are structured, use the standalone page below.
Related
Issues covered on this page
I have the same function more than once
What this usually means
This usually means the same function name appears under more than one licensed activity. That is not automatically a duplicate. In Functions, the same function can appear more than once when the licensed activity changes, because each financial entity, licensed activity, and function name combination needs its own unique function identifier.
What to check and how to fix it
Check whether the function name is the same but the licensed activity is different.
If the licensed activity changes, keep separate function rows instead of merging them.
Check Functions for one row per valid combination of financial entity, licensed activity, and function name.
If one row is covering more than one licensed activity, split it into separate rows.
Check the function identifiers assigned to those rows.
If two different licensed activities are sharing one function identifier, assign a different identifier to each combination.
Check whether the function should instead be reported as support functions.
If it is not linked to a registered or licensed activity, report it as support functions rather than forcing it under the wrong activity.
Check every linked Contractual arrangements row.
If the same contract supports that function under more than one licensed activity, link each row to the matching function identifier instead of reusing one identifier for all cases.
I do not know how to report this contract
What this usually means
This usually means one contractual arrangement supports more than one function. The contract reference stays the same, but the contract detail template needs separate rows so each supported function is linked clearly.
What to check and how to fix it
Check whether the contractual arrangement supports more than one function.
If it does, do not try to force all of them into one row.
Check that each supported function already exists in Functions.
If a function is missing there, create the correct function row first and assign its function identifier before linking the contract.
Check the contractual arrangement reference number.
If you are still reporting the same contract, keep the same contract reference number rather than creating a new contract only because another function is involved.
Check Contractual arrangements for separate rows per supported function.
If one contract supports several functions, add a row for each function that the contract supports.
Check whether the same contract also covers more than one ICT service.
If it does, split the rows further so each valid ICT service and function combination is recorded separately.
Check that each row holds one value per data element.
If you are trying to record several function identifiers in one field, split them into separate rows before moving on.
I do not know why I need multiple rows
What this usually means
This usually means you are treating Contractual arrangements as a one-row-per-contract table. It is more granular than that. Where a contractual arrangement covers multiple ICT services supporting multiple functions, the register needs separate rows for the valid combinations.
What to check and how to fix it
Check whether the contract includes more than one ICT service.
If it does, add separate rows for each ICT service covered by that contract.
Check whether each ICT service supports one or more functions.
If one ICT service supports several functions, add separate rows for each supported function.
Check that the same contract reference number is reused across those rows when they all belong to the same contractual arrangement.
If you change the contract reference only to create extra rows, the contract structure becomes unclear.
Check that each row contains one value for each data element.
If more than one value is valid for a field, split the record into additional rows instead of combining values in one row.
Check the final set of rows for completeness.
If a valid ICT service and function combination is missing, add it before moving on.
What to do next
Once Functions has one row per real function combination and Contractual arrangements has one row per valid contract, ICT service, and function combination, the remaining issue is usually the identifier itself or another cross-record link problem. If the structure now looks right but the identifier is still wrong, go to My function identifier is invalid.