thumb_up
thumb_down
link
Copy link
Copied
insert_emoticon
lmatfy
Copied

Add and change sales contacts (KnSalesRelationOrg / KnSalesRelationPer UpdateConnectors)

UpdateConnector for adding and changing sales contacts.

UpdateConnector name:

  • KnSalesRelationOrg (for organisations)
  • KnSalesRelationPer (for persons)

    Note: 

    You can use this UpdateConnector to add or change one contact person. You cannot add/change multiple contact persons at the same time!

    If you want to add contacts, delivery addresses and departments for an organisation, you use the 'KnOrganisation' UpdateConnector.

Contents

Preparation
Description

Actions that can be performed with the connector

Action

Comment

INSERT

Add a sales contact

Download an XML example file

UPDATE

change a sales contact.

Download an XML example file (add contact)

Download an XML example file (add IBAN)

Points of attention:

  • UPDATE sales contact

    In the case of an UPDATE, use the code of the sales contact (field: 'DbId').

  • UPDATE organisation or person

    In the case of an UPDATE of linked organisation or person details (in the 'KnOrganisation' or 'KnPerson' segment), you must also specify a unique key for the organisation or person. Use the code of the organisation or person for this purpose and specify the correct value in the 'MatchOga' field.

    You can derive the code of the organisation or person based on the number of the sales contact. To do so, you use operator 9 in the 'MatchOga' field (for organisations) or the 'MatchPer' field (for persons). You cannot specify a value in the 'BcCo' field.

  • Sales contact with existing organisation or person

    You can link a sales contact to an existing organisation or person by delivering a value in the 'BcCo' field.

A sales contact is always an organisation or a person. Therefore, you need to create an organisation or person immediately when you add a sales contact.

See also the remarks for the connectors for organisations and persons.

Mandatory and optional objects in the XSD Schema Tool

If you use the XSD Schema Tool to generate an XML file, the XML file contains the following objects:

Debtor (M)

KnOrganisaton (M)

KnBankAccount

KnBasicAddressAdr (M)

KnBasicAddressPad (M)

KnContact

KnBasicAddressAdr (D)

KnBasicAddressPad (D)

Kn Person (D)

KnBankAccount

KnBasicAddressAdr (D)

KnBasicAddressPad (D)

The meanings of the codes for the segments:

  • M: Mandatory
  • D: Depends on another object. When you deliver certain objects, their associated segments are also required.

Product range

Fields:

  • AsGr (Product range)
  • AsYN (Allow different product range)

The Product range monitoring activation must be enabled.

Sales contact code

Field: DbId

If you run an INSERT, you add a sales contact with the provided code. If you do not deliver a code, the code can be determined automatically based on the auto numbering of sales contacts, provided this has been recorded.

Is debtor

Field: IsDb

If this field has the value 'True', this means that the sales contact is regarded as a debtor. This means extra fields become mandatory, such as the 'PaCd' and 'VaDu' fields.

eVerbinding company ID

Field: EnId

See also: Configure e-invoices using 'eVerbinding'

Mandatory fields

You must provide values for the following fields even though these fields appear as optional fields in the XSD Tool.

  • PrLi (Line discount)
  • PrFc (Invoice discount)
  • ClPc (Credit restriction)
  • PrPt (Payment discount)
  • KrLi (Credit limit)

For these fields, you can deliver the value zero.

Addresses

  • In an address, you must always enter the country code in the 'CoId' field.
  • Deliver the fields that are needed for a complete address (this depends on the properties of the country code).
  • For the first address (in practice, for a new record), you do not need to deliver a start date in the 'BeginDate' field. If an address already exists, use 'BeginDate' to indicate the effective date of the address change.
  • If the 'ResZip' field has the value 'True', the system looks up the city for the postal code entered. In this case, you do in fact still need to enter a city in the 'Rs' field. If the system cannot find a city for the postal code entered, it uses the value entered in 'Rs' for the city.
  • For delivery addresses, use the value 'AFL':

    <ViKc>AFL</ViKc>

Bank account number

You specify a bank account number for a person or organisation in the 'KnBankAccount' segment. You can provide an IBAN number or a bank account number (old style).

  • IBAN number

    Specify the following fields:

    • CoId: country code
    • Iban: IBAN number
    • IbCk: IBAN number check
  • Bank account number

    Specify the following fields:

    • CoId: country code
    • BaAc: bank account number. The bank account number should have 10 positions. For a 9-position bank account number, you must add a leading zero.

If you supply an IBAN bank account number, Profit determines the BIC code automatically. This only happens if the following conditions are satisfied:

  • The bank account number is a Dutch account number.
  • The BIC code has not been entered in the XML or in Profit.

Directly to

  1. UpdateConnector descriptions

Process

Profit UpdateConnector descriptions

Work area

app