Kontoparametre - Relasjoner

Kontoparametre kan ha relasjoner som beskrevet i tabellen nedenfor. 

Som standard har ikke Kontoparametre noen relasjoner til andre Kontoparametre. Dette betyr at når en regnskapskode velges i brukergrensesnittet, vil ikke radcellene i andre kolonner endres, og brukeren kan velge en hvilken som helst annen kode i disse cellene.

Det er mulig å sette opp relasjoner i Innstillinger > Kontoparametre > Klikk på et Kontoparameter > fanen Relasjoner. Det er 9 mulige effekter på fakturalinjenes Kontoparametre, avhengig av innstillingene for regnskapsparameterrelasjoner.

• Ingen relasjon
  Når konto/dimensjon er angitt, vil ingen andre Kontoparametre angis eller fylles ut automatisk.
   
• Krav (UI: Påkrev spesifikk)
  • If 1 requirement is set it will be selected automatically. 
  • If 2 or more requirements are set, the user must select one of them.
     
• Suggestion (UI: Suggest)
  This means the user may select one of the suggestions OR any other code OR leave the cell blank.
  • If 1 suggestion is set, it will be selected automatically.
  • If 2 or more suggestions are set, none will be selected automatically but they will be displayed as suggestions when the user selects the cell.
     
• AnyValue (UI: Require Any)
  The user must select any of the available values. Leaving the cell blank is not permitted.
   
• NotApplicable (UI: Forbid)
  The cell will be disabled and it will not be possible to select any of the values.
   
• RequirementOrNoValue (UI: "Requirement or no value", "krav eller ingen verdi")
  • If 1 requirement is set it will be selected automatically. The user may still remove the cell value to leave a blank cell. 
  • If 2 or more requirements are set, the user must select one of them OR leave the cell blank.

Invoice Line GUI Effects

Here we see 5 types of relations between Account and VAT Code and Interim: 
[ Requirement, Suggestion, NotApplicable, AnyValue, RequirementOrNoValue ]

Target accounting parameter values must be created before relations can be made.

Example 1: Operation Requirement

However, if the accounting code 123 has a relation of operation "Requirement" to VatCode 4, then this VatCode will be automatically selected for the user.

Example: When selecting a code with required relations, the required relations are set automatically and locked.

Example 2: Operation Suggestion

An accounting parameter value 123 of type "AccountingCode" may have multiple relations to individual dimension value codes, 4,5,6 all with "operation" set to Suggestion. As a result, the user will see those suggestions 4,5,6 appear in the dimension value cell whenever the Accounting Code 123 is selected in the UI.
Note:

• If there is one relation with operation suggestion, it will be selected automatically.
  
   
• If there are 2 or more relations with operation suggestion, the suggestions will not be selected automatically but only be listed when clicking in the cell.
  
   
• It is still possible to select any other value in the dimension value cell without restrictions.

Example: When selecting a code with suggested relations, each suggestion is listed.

Example 3: Operation AnyValue

An accounting code 123 with relation to VatCodes of operation AnyValue will accept any VatCode except blank.

Example: Operation: AnyValue (not blank)When the user selects a code with AnyValueas relation, some value other than blank has to be selected.

Example 4: Operation NotApplicable

An accounting code 123with relation to VAT Code and operation NotApplicable will disable the VatCode field.

Example: VAT Code and Interim has been disabled since the relation operation was set to NotApplicable for both

Allowed operations for each relation

Effect of operations in API and UI

The relations and operations determine which invoice line columns are automatically filled in (required) or contain suggestions (suggested) codes and which are disabled or allows any value.

Code example

Below is an example of an AccountingCode-A with relations to cDimensionCodeValue-R1, AccountingCode-B, VatCode-R1 and TransactionTypeCode-R1.All relations of the same type, must have the same operation.

• Dimension
  The relation to type: Dimension needs an extra property typeCode: which is the name of the dimension in addition the regular code property which is one of the values of that dimension.
• Interim
  As hinted from the code name below, an Interim code is really just a regular GL Accounting Code where the relation type Interim is used
• VatCode
  The VatCode has to be a regular VatCode available in the system.
• TransactionTypeCode
  The TransactionTypeCode has to be a regular TransactionTypeCode available in the system.

[
    {
        "code": "{{AccountingCode-A}}",
        "status": "Active",
        "relations": [
            {
                "typeCode": "{{cDimensionCode-A}}",
                "code": "{{cDimensionCodeValue-R1}}",
                "type": "Dimension",
                "operation": "Requirement"
            },
            {
                "code": "{{AccountingCode-B}}",
                "type": "Interim",
                "operation": "Requirement"
            },
            {
                "code": "{{VatCode-R1}}",
                "type": "VatCode",
                "operation": "Requirement"
            },
            {
                "code": "{{TransactionTypeCode-R1}}",
                "type": "TransactionType",
                "operation": "Requirement"
            }
        ],
        "description": []
    }
]