Customers

• Category (field BCGCOD)

This is the category associated with the customer.
A customer category makes it possible to:

• have an additional customer classification,
• have default values upon creation,
• and assign an automatic numbering to customers according to a counter associated with the customer category.

• Active (field BPCSTA)

Use this field to activate or deactivate a customer.
This is designed to create a customer in several steps or to activate it once all the information are validated.

 It is possible to make a customer inactive even though flows are still in progress for him. Making a customer inactive does not prevent from completing the flow. For example, it is possible to generate a delivery for a customer made inactive after entering the order. When the customer is inactive, the only forbidden creation is the creation of a document that does not result from a flow.

• Customer (field BPCNUM)

This field is used to enter the code used to identify the customer. It can be entered directly or selected from the Customer table.
 This customer list is not exhaustive, any customer not present in this list can still order the product.

• field BPCNAM

This is the customer's corporate or company name, not accessible at this level.

• Short description (field BPRSHO)

This field specifies the customer's company name.

• Acronym (field BPRLOG)

BP's acronym.

• field BPRNAM

Business Partner company name.

• Natural person (field LEGETT)

When it is activated, this indicator makes it possible to specify that the BP is a physical person. When it is not activated, it is a corporate body.
If the BP is a corporate body, it is mandatory to enter the "VAT identification number" and the "Site tax ID number" if their entry has been set up at country level as mandatory.

• Mailing prohibited (field BPRFBDMAG)

This field is used to forbid the user to send marketing mail to the selected customer.

• Country (field CRY)

This code is used to identify amongst other things, the Country of a BP.
This is important information, associated with a number of characteristics useful for performing controls on other linked information, in particular:

• the telephone number format,
• the format of the number that identifies a company or an activity (site tax ID number, NAF in France), and whether its entry is mandatory or not,
• the postal code format of the town and also the code of the geographic subdivision, and whether their entry is mandatory,
• whether the VAT number of this community is mandatory,
• the Bank ID code format.

• Language (field LAN)

Code controlled in the language table making it possible to define the language of a business partner.

• Currency (field CUR)

This code is used to identify the currency of a site, a BP, etc. Is is controlled in the currency table.
The currency suggested by default is the budget one.

• Site tax ID no. (field CRN)

Single identification number for the company.
It is mandatory to enter this number if both the following conditions are satisfied:

• its entry is set to mandatory by setup of the country record,
• the BP is a corporate body.

Its entry format depends on the setup carried out at the level of the Country record.

In France, this number, assigned by the INSEE on registering a company with the national registrar of companies, contains 9 numbers, is unique and cannot be changed. This is used by all public bodies and the administrations in contact with businesses.

• SIC code (field NAF)

This fields displays the SIC code (subject to activity code KFA), according to the French company's activity codification.

• EU VAT no. (field EECNUM)

This is VAT identification number of the buyer. The EU tax number depends on the BP country and the associated check process.
It is possible to associate a VAT identification number for this BP by delivery address in function (a BP can be identified in different countries according to the VAT).

• EU VAT ID validation (field EVCVAL)

Note: This field is only available if a web service is identified in the EVCSERVICE – Webservice for EU VAT ID parameter (CPT chapter, VAT group) and the sender's EU VAT ID is set in the EVCCOMPANY—EU VAT ID source company parameter (CPT chapter, VAT group)

Click the Validation action to interactively validate your EU VAT ID.

A message box displays with the validation results. The exact content varies by check result and web service used.

• If the validation was successful, you receive a confirmation message and the Validation check box is selected.
• For an unsuccessful validation, you receive a message that displays the reason for the failed validation.
• If no full validation could be performed (for example, if only the VAT ID was validated and not the address), you have the option to accept the results as valid or not. If you select Yes, the Validation check box is selected.

Note: Successful validation results are stored in a table.

If a previously-validated VAT ID is modified, the Validation check box is cleared.

Validation levels:

A Qualified validation verifies the EU VAT ID and company name and address. All data must be valid.

An Unqualified or simple validation only verifies the EU VAT ID. Note that the EU validation web service performs only unqualified validations.

Address management:

Results are recorded with the original address code.

For the main EU VAT ID, the standard company address is used.

You can manually revalidate IDs using the EU VAT ID revalidation function (EVCBAT).

• Verified (field EVCVALDON)

If a previously-validated VAT ID is modified, the Validation check box is cleared.

A message box displays with the validation results. The exact content varies by check result and web service used.

• If the validation was successful, you receive a confirmation message and the Validation check box is selected.
• For an unsuccessful validation, you receive a message that displays the reason for the failed validation.
• If no full validation could be performed (for example, if only the VAT ID was validated and not the address), you have the option to accept the results as valid or not. If you select Yes, the Validation check box is selected.

Note: This field is only available if a web service is identified in the EVCSERVICE – Webservice for EU VAT ID parameter (CPT chapter, VAT group) and the sender's EU VAT ID is set in the EVCCOMPANY—EU VAT ID source company parameter (CPT chapter, VAT group)

• Intersite (field BETFCY)

This flag is used to specify that this is an inter-sites BP:

• The inter-site customer/supplier BPs are used for multi-site exchanges.
• a customer BP is a purchasing site or a financial site,
• a customer BP is a purchasing site or a financial site.
  

• Site (field FCY)

Site code that has to be identified as a BP within the frame of multi-site exchanges.

The following data need to be entered:

• The requesting site (purchase or financial sites) at the level of the customer BP.
• The supplying site (sales or financial sites) at the level of the supplier BP.
• For the customer, a warehouse site, belonging to the same company, will identify each ship-to address.

• Customer (field BPCFLG)

This field is automatically ticked when the BP is a customer.

• Sales rep (field REPFLG)

This field is automatically ticked when the BP is a sales representative.

• Prospect (field PPTFLG)

This field is automatically ticked when the BP is a prospect.

• Supplier (field BPSFLG)

This field is automatically ticked when the BP is a supplier.

• Miscellaneous BP (field BPRACC)

This field is automatically ticked when it concerns a miscellaneous BP.
A miscellaneous BP is only used in accounting.

• Service supplier (field PRVFLG)

This option is used to include a BP among the list of after-sales service providers.

An after-sales service provider is an organization that may be called on to conduct

an intervention to be carried out for a service request (Repair, advice, audit, quote etc...)

For each service provider, it is possible to register their skills, their geographic intervention area,

their price list conditions for invoicing.

• Carrier (field BPTFLG)

This field is automatically checked when the BP is a carrier.

• Service caller (field DOOFLG)

The contractor represents the actual customer for whom a service request is made.
When a service request does not include any contractor, the service is supplied on behalf of the direct customer of the current organization.
By contrast, when a service request includes a contractor, the service is provided to the customer but is is made on behalf of the contractor. The customer receiving assistance is not the organization's customer but the contractor's.
Regarding invoicing, the data loaded by default is the contractor's (invoiced customer, pay-by BP, ...). Therefore, it is mandatory to create a customer record for the contractor.
This option makes it possible to discern the contractor population.
This option is also mandatory to be able to link customers to their contractor(s).

• Address code (field CODADR)

Address code of the business partner (BP).

• Address code (field XCODADR)

This code is used to identify the various addresses associated with the managed record (user, company, site, business partner of any description, etc.).
Each address code is unique to a given record.
In general, it is mandatory to enter an address for each record, and one of them must be declared as the default address using the corresponding box.

You cannot modify or delete an address code when it is used at the level of a Bank ID number or for a contact.
In this case, to be able to modify or delete an address code, you first need to remove it from the level of the Bank ID number or contact.

• Description (field XBPADES)

Specify the information linked to the address.

• Country (field XBPACRY)

This code is used to identify the country associated with the address.

In the Country table, which controls this field, some specific characteristics are used to perform controls on the related information, in particular:

• the phone number format,
• the format of the number identifying a company or an activity (SIRET, NAF in France),
• the format of the postal/town-city code as well as that of the geographical subdivision, and whether their entry is mandatory or not,
• the format of the bank ID number,
• the IBAN management.

• Description (field XCRYNAM)

Title associated with the previous code.

• field XADDLIG1

This table lists the various address lines. The formats of the title and of the entry are defined in the country table.

• field XADDLIG2

• field XADDLIG3

• Postal code (field XPOSCOD)

The postal code, which entry format is defined in the Country table, is used to define the town/city, state/region and the geographical subdivision, if defined for the country.
If you modify the postal code, the city/town and state/region corresponding to this new code are automatically displayed. The principle is the same for the geographical subdivision if it is present for the country.
You can also directly enter a town/city name or state/province. If the city/town, state/region are defined, the associated postal codes are displayed automatically.
The control of this information and its mandatory nature depend on the setup carried out in the country management. For the control to be applied, the POSCOD - Warning nonexistent postal code parameter (SUP chapter, INT group) must also be set to 'Yes'.

Particular cases:

- for ANDORRA, indicate 99130,
- for MONACO, indicate 99138,
- for the other foreign countries, indicate the national identifier of the country or 99999 if not known.

When the postal code is defined as mandatory for the country, it must be entered if the Postal Code or City/town fields are entered, or if information is modified in the BP address window. However, this control is not applied in document creation.

• City (field XCTY)

The city automatically suggested is the one associated with the postal code previously indicated. It is also possible to manually enter the name of a town/city:
- If the town/city is already defined, the associated postal code is automatically displayed,
- If it does not exist and the postal code control has been set up in the Country record, a warning message is displayed but the continuation of the entry is authorized (in order for this control to be applied, the CTY - Nonexistent city alert parameter - SUP chapter, INT group - must also be set 'Yes'),
- If it does not exist and the postal code is set up as mandatory for the country, a blocking message is displayed in case the fields Postal code or City/Town are entered or in case of modification of information in the address window of the BP. However, this control is not carried out in document creation.

Notes.

• Its format is defined in the Country record setup.
• Depending on this setup, the entered town/city can automatically be converted into uppercase after it has been entered.
• In order to make selections easier without taking into account the format (accented characters/uppercase letters/lowercase letters), the selection window available on this field proposes a column dedicated to the search, where the names of the towns/cities are displayed in uppercase.

• field ITINERAIRE

Click this icon to open a mapping site and locate the entered address.

• field XSAT

This field contains the geographical subdivision corresponding to definition of the postal address. For example, a 'department' for France, and a state for the United-States.

The description of the geographic subdivision, as well as the control on the information entry, are defined in theCountries setup.

This field loads automatically after the postal code and town/city have been entered and is based on the Postal codes setup.
If the field is controlled, the control is carried out with respect to the Geographical subdivision table.

• Website (field XFCYWEB)

This field is used to indicate a web site.

• External identifier (field XEXTNUM)

This free field makes it possible to stock a variable identifier, which can be used for specific processing.
Example: when generating international transfer files in XML format, the content of this field identifies the credited BP, when the SIRET number is missing (see setup of Bank files).

• Default address (field XBPAADDFLG)

When selected, this check box indicates that the address is a default address. Only one of the addresses in the selected record can (and must) be selected. This always corresponds to one of the BP's addresses.
The customer's default address can be different from the BP's default address.

• Address validation (field VALADR)

Click on this button to send an address to the validation service of Sage Sales Tax (SST) addresses. If this address is found, it is updated with respect to the format of American postal services.
This field is only available when the LTA activity code is activated.

 The validation service of SST addresses is defined in the parameters related toSage Sales Tax.

• Validated (field XADRVAL)

This box is checked automatically if the address is processed by the validation service of Sage Sales Tax (SST) addresses when the 'Address validation' button is checked. The check box is not selected and cannot be accessed when the address is unknown.

 The validation service of SST addresses is defined in the parameters related toSage Sales Tax.

• field XTEL1

This field indicates the phone number. Its entry format depends on the country.
The level of control applied to the entered number format depends on the general parameter CTLTEL - Phone number control (SUP chapter, INT group).

• field XWEB1

This field is used to specify the email address of the contact.

• ABC class (field ABCCLS)

Code making it possible to identify the ABC category of a business partner.
The ABC category is designed to classify business partners according to their importance in the turnover, for example.
Values between 'A' and 'D' can be entered. At the time of creation, the BP, having no statistical data available, is classified in category "D" by default.

• Minimum order (field WORDMINAMT)

Minimum tax excl. amount, expressed in folder currency, below which customer orders cannot be saved.

• field XCUR

This is the folder currency.

• Allow order close (field ORDCLE)

This information, initialized by the sold-to customer, is used to authorize or not the closing of a line or the order. This information is modifiable on order entry if the transaction allows this.

• Loan authorized (field LNDAUZ)

This indicator is designed to define whether a loan of goods for this customer is authorized.
The product concerned also has to be authorized for the loans and has to be managed by location.

• One order per delivery (field ODL)

This information, initialized by the sold-to customer, is used to prohibit the grouping of several orders in the same shipment. This information is modifiable on order entry if the transaction allows this.

• Partial delivery (field DME)

This information, initialized by the sold-to customer, is used to specify how the order is delivered. There are three possible values:

• Authorized means that the order can be partly delivered. 
• Complete linemeans that the order can be partly delivered if the complete line is delivered.
• Complete order means that the order must be delivered in full (a single delivery).

This also means that a partial allocation cannot be performed on an order line or order if the stock is insufficient to cover the full line or order: the Partial Allocations option must be displayed on the order or in the mass allocation options.When entering the quantity to be allocated to the line or when performing a Manual allocation on the line, a warning message displays if the delivery is partial.

Note:When you select Complete line or Complete order, you can ignore this warning message and force the partial delivery.

• Price/Amount type (field PRITYP)

This flag determines if the prices of products (sales invoices) and amounts (customer BP invoices) are expressed ex-tax or tax incl. This flag influences the price list search. Only those price lists defined in a mode or those accepting a price conversion will be taken into account.

The document price/amount type excludes or includes tax depending on the type defined at customer level.

If the supplier is connected with a customer category, this information is initialized by the amount type defined at the level of the field Price type/Amount typeof the category.

• Freight invoicing (field FREINV)

Flag used to specify if freight must be charged to the customer or if the latter does not have to bear these charges. This exemption can be linked to no conditions at all or to a tax excl. or tax incl. threshold.
The freight calculated from the carrier price and integrated when delivering via a dedicated invoicing element.
 For more details, see the general setupFRENUM.
The thresholds are defined in the carrier record.

• Invoicing mode (field IME)

This information is initialized by the sold-to customer and is used to define the customer's invoicing mode. This invoicing mode is used subsequently to invoice the delivery notes or the direct invoicing orders by regrouping or splitting them. This information is used in the automatic invoicing processes and in the manual invoicing function (where a control is performed with respect to this information).

The available invoicing modes and their impact on the delivery invoicing are as follows:  

• 1 invoice / DN: This invoicing mode requires the existence of a separate invoice for each delivery created.
• 1 invoice / completed order: This invoicing mode only authorizes the invoicing of the deliveries associated with an order if said order is completed and all the invoices associated with this order are validated and all the deliveries belong to the automatic invoicing selection. A single invoice will then be generated grouping all the deliveries for the order.
• 1 invoice / order: This invoicing mode is used to create an invoice for all the deliveries of the order that are validated when the invoicing process is run. A single invoice will be generated grouping all these deliveries.
• 1 invoice / ship-to customer: This invoicing mode is used to create an invoice for all the deliveries concerning the same ship-to customer on a single invoice when the automatic invoicing process is run. There also is a control performed upon manual invoicing of the deliveries.
• 1 invoice / period: This invoicing mode is used to create an invoice for all the deliveries based on the invoicing frequency defined by the customer. For instance, if the frequency is weekly, all the deliveries during week 32 (relating to the shipment date or delivery date based on the INVREFDAT - Origin date for invoicing setup) are grouped on a single invoice. There is a specific feature linked to the invoicing frequency when the chosen value is upon request.Deliveries with this kind of frequency will be grouped together. A control is also carried out in manual delivery invoicing mode to only enable the grouping together of deliveries with an invoicing mode by period and a manual invoicing mode.
• Manual invoice: This invoicing mode is not considered in the automatic invoicing processes. Invoicing will be manual on invoice entry.

Impact of the invoicing mode on delivery generation: orders with an invoicing mode 1 invoice/order or 1 invoice/completed order will never be grouped on a same delivery.

Beside these invoicing modes, there are pieces of information that, if varying from one delivery to the next, prohibit the grouping together of two deliveries. Please refer to the automatic delivery invoicing.

The impact of the invoicing modes on the direct invoicing orders is as follows:

• 1 invoice / DN: This invoicing mode requires the existence of a separate invoice for each direct invoicing delivery. On the other hand, an order can be only partly invoiced by the automatic invoicing function from the moment that the order delivery mode is not Complete order.If the order delivery mode is Complete order,all the order lines will need to be invoiced (the stock-managed order lines will need to be allocated), otherwise the invoice will not be generated. On manual invoicing of an order of this type, there are no constraints with respect to the delivery mode, and it will be possible to draw up a partial invoice even if the delivery mode is Complete order.
• 1 invoice / completed order: This invoicing mode requires the existence of a separate invoice for each direct invoicing delivery. An order will have however to be fully handled in order to be invoiced using the automatic invoicing function. There will thus be only one invoice for this order. In manual invoicing it isn't necessary to follow this rule; it is possible to partially invoice an order of this type.
• 1 invoice / order: For the orders with direct invoicing, this invoicing mode corresponds to the invoicing mode previously described: 1 invoice / DN. 1 invoice / DN:
• 1 invoice / ship-to customer: This invoicing mode is used to create an invoice for all the orders with direct invoicing concerning the same ship-to customer on a single invoice when the invoicing process is run. If order lines concern various ship-to customers within a single order there will be as many invoices as there are delivery addresses on the lines. There also is a control performed upon manual invoicing of the orders.
• 1 invoice / period: This invoicing mode is used to create an invoice for all the orders based on the invoicing frequency defined by the customer. For instance, if the frequency is weekly, all the orders during week 32 (relating to the requested delivery date in the order header) are grouped on a single invoice. There is a specific feature linked to the invoicing frequency when the chosen value is upon request.The orders with this kind of frequency will be grouped together.
• Manual invoice: This invoicing mode is not considered in the automatic invoicing processes. Invoicing will be manual on invoice entry.

Beside these invoicing modes, there are pieces of information that, if varying from one order to the next, prohibit the grouping together of two deliveries. Please refer to the automatic order invoicing.

• Invoice period (field INVPER)

Flag used to define the customer invoicing frequency.
This invoicing can take place every day, every week, every 10 days, every fortnight, every month or upon request.

• Invoicing term (field INVCND)

Use this field to specify the Invoicing term. This information is optional.
This filed initializes the entered invoicing term on the customer order, when the order is linked to a Service or Generic product with a Sold and not Deliverable flow type.

• Due date origin (field DUDCLC)

Date used as the calculation basis for the open items and which can take the value 'Invoice date' or 'Delivery date'.

• Accept electronic invoice (field AEIFLG)

• Commission category (field COMCAT)

Commission category used to select the commission rate of the sales representative record for the commissioning calculation.

• field REP

Code of the sales representative associated with the customer and controlled in the sales representative table. The sales representative of the sold-to customer has priority over the sales representative of the ship-to customer.
An activity code is used to define the number (maximum of 2) of sales representatives submitted as the default value upon order.

• field MORREP

• No. (field INVDTA)

This is the code for the invoicing element.

• Description (field SHO)

This is the short title for the invoicing element.

• % or amount (field INVDTAAMT)

These are the information relative to the invoicing footer. The invoicing elements correspond to the category of customer used or to the elements set up to be displayed on the customer record if no category has been associated to the customer.
When the invoicing elements come from a setup with a default value, this value is used and converted into the customer's currency using its rate type and the current date of the system (datesyst).

• field INVDTATYP

This column specifies if this is a percentage, an ex-tax amount or a tax-incl. amount.

• Curr. (field WWCUR)

This is the (customer) currency in which the amount is expressed.

• Order (field WORDTEX)

This text indicator is used to signal that an order text has been defined for this customer. This text will be used on each order so as to be printed on the order acknowledgment.

• Invoice (field WINVTEX)

This text indicator is used to signal that an invoice text has been defined for this customer. This text will be used on each modified invoice.

• Print acknowledgement (field OCNFLG)

Flag used to specify whether the acknowledgement of receipts must be printed or not for the orders.

• Template code (field TPMCOD)

This field is used to indicate the reference of a print template listing the reports to use in priority (and the number of copies) with the documents used in commercial management. It is thus possible to specify the reports and to reserve them to some BPs.

To enable an electronic invoicing for Portuguese legislation, you must select a PDF print template code or invoice report compatible with Portuguese legislation. The archive destination for the template in PDF format is determined by the EFATPRT – Default destination for EFAT (LOC chapter, POR group) parameter setting.

• Electronic invoice (field ELECTINV)

Select this check box to send an electronic invoice to the customers who agreed to receive electronic invoices.

To activate the electronic invoicing feature, you must select a Print template code of the Archive type.

This field only applies to the Portuguese legislation and is available when the EFAT activity code is active. The electronic invoice is in compliance with the legal requirements of the Portuguese tax authorities.

Please refer to the EFAT communication documentation for further information.

• Contact (field CNTEFAT)

You can only enter a contact with a valid email address linked to the customer record.

This field is only available if the Electronic invoice check box is selected.

• Start date (field STRDATEFAT)

This field is only available when the Electronic invoice check box is selected.

• Customer type (field BPCTYP)

The customer type can take the following values: Normalor Miscellaneous.
The Miscellaneous type is used to cause the automatic opening of an address entry window for all the commercial documents (it is considered that these are 'cover-all' customers that are not distinguished in accounting).
The default category is Normal.

• Our supplier no. (field BPCBPSNUM)

The number under which the company is known as a supplier for the customer.
This information is indicative only.

• Rate type (field CHGTYP)

This is the rate type (local menu where the standard values are modifiable) used to determine which rate will be used by default to find the posting rate of sales documents.

• Business (field BUS)

This field is used to qualify the economic activity of the customer with a level of segmentation adapted to the segmentation needs of the commercial team.

• Source (field ORIPPT)

This field is used to record the commercial channel at the origin of the identification and qualification of a business partner.

• Customer since (field BPCSNCDAT)

This field is used to specify the date from which the BP has been a customer of the company.

• When creating or copying a customer, this date is automatically loaded with the current date.
• In the case of the conversion of a prospect into a customer from the orders, this date is automatically loaded with the order date.

• Token credits (field PITCDT)

This field displays the total number of tokens credited by the customer as a result of their different orders.
This total does not take into account the points credited as a result of a manual addition of points specified in the next field.
Reminder: the tokens are the bonuses that each customer can credit upon different successive orders.

• Manual supplement (field PITCPT)

This field is used to perform a manual addition of points (tokens) for the customer, independently of the receipt of a sales order.
It is essentially used when a customer has passed an order that gives them nearly all the necessary points to obtain the gift. In this case, the sales team can decide to offer several missing points (tokens) by entering them directly in the customer record.
The latter carrying the manual points is always saved for information purposes.

• Total token credit (field TOTPIT)

This field displays the total number of tokens credited by the customer as a result of their different orders.
This total also includes the tokens credited from the manual addition of points.
When this total exceeds the number of necessary tokens indicated further on or in the service contract template, a contract is offered to the customer.

• Points debit (field BPCPITDEB)

You can enter a point debit rule directly for a customer.
The debit indicated in the customer record is applied only for the contractual debit. All additional debits are specified at the level of the point debit rule.
Click the Actions icon and Point debit to view or define a Point debit rule.
The entry of a value in this field leads to the creation of a point debit rule where only the customer component is entered.

• Value 0 (field NULPIO)

This option is used to block the tree of rules for debiting points during the analysis of a service request coverage.
In other words, this is used to block all consumption of points for service requests pertaining to this customer.

• Service contract (field COTCHX)

This field is used to indicate the service contract template that will be automatically offered to the customer each time enough tokens have been accumulated.

• Tokens necessary (field COTPITRQD)

This field displays the minimum number of tokens necessary for a customer to be offered a service contract.

This information has priority over its equivalent in the service contract template.

• Credit control (field OSTCTL)

Select the type of control that you want to apply on the customer credit amount:

• Controlled: The control is carried out in real time when creating the order, during the allocation and during the delivery, based on the authorized credit level. The customer can be delivered if their credit level is lower than their authorized credit level. This control can be performed:
• By company or by folder, based on the value of the general sales parameter OSTCTL - Credit control level (TC chapter, OST group).
• With an archived or updated (revised) rate, based on the value of the general Common Data parameter: OSTCHGTYP - Rate origin WIP ctrl. (TC chapter, OST group).
  If the control is performed based on an updated rate, the rate type to be used is the one set by the OSTTYPCUR - Rate type updated rate ctrl parameter (TC chapter, OST group).
  When the control on credit is done at the 'Folder’ level, the control is always applied based on the updated rate, regardless of the value of theOSTCHGTYP - Rate origin WIP ctrl. parameter.

The WIP is controlled with respect to the risk BP of the customer. If the risk BP is shared by several customers, it means that the WIP of each customer will be controlled the same way with respect to the risk BP by cumulating the total of the different customers movements.
When the customer is associated to a different risk BP, the amount of the authorized WIP cannot be accessed. It can be viewed on the risk BP record. The displayed WIP is the risk BP,

• Free: the customer can always be delivered.
• Blocked: the customer can no longer be delivered.

• Authorized credit (field WOSTAUZ)

Maximum credit amount authorized for this customer. It is used if the customer is declared as ‘Controlled’ in the WIP control field. This amount is expressed in the currency of:

• The folder when the control is at folder level;
• The Common Data site of the user when the credit control applies at the company level.

• field XCUR

• Credit level total (field XOST)

This is the total credit amount calculated by the system.
This amount includes:

• Orders in progress (excluding loan orders and delivery requests) if the OSTORD - On order in order total parameter (VEN chapter, OST group) is set to Yes.
• Deliveries in progress (excluding non billable deliveries).
• The delivered but not invoiced elements.
• Loan orders and delivered loan orders in progress when the parameter OSTLND - Loan in order total (VEN chapter, OST group) is set to Yes.
• The invoiced but not posted elements.
• The accounting balance.
• The notes payable/receivable, based on the OSTDRAFT - Customer credit note P/R amt. parameter (TC chapter, OST group).

On the relevant documents, the credit amount:

• Considers the total of calculated taxes on all lines of these documents,
• Does not consider:
• Invoicing elements
• Global VAT adjustment.

• Credit insurance (field WCDTISR)

Amount of the insurance subscribed to specialized organisms (sfac and others) for the cover of the customer risk in case of default. This amount is expressed in the folder currency.

• Insurance date (field CDTISRDAT)

End date of the insurance subscribed to specialized organisms (sfac and others) for the cover of the customer risk in case of default.

• Insurance company (field BPCCDTISR)

The insurance company is declared as a miscellaneous BP. This information field is designed to associate essential descriptive details to the insurance companies (titles, addresses, contacts, etc.).

• Customer notes (field BPCNOTE)

Click on this icon to display a screen where you can:

• Enter information on the customer as a note. This information is available for inquiry in the functions that have been selected at the Note category level.
• Define a validity period for the note.
• Specify it the note must be displayed automatically.
• Create multiple notes for the same customer, and indicate if they must be displayed as a priority.

Notes are limited to a screen inquiry and cannot be printed.

For further information, see the documentation on Notes.

• field TSCCOD

You can enter a code in order to link a statistical group to the customer. This code is controlled in the table of statistical groups. It can be used in statistics, price list settings, or as a selection criteria in specific automatic processes.

• Bill-to customer (field BPCINV)

It is the code for the bill-to customer, which is initialized by default with the customer code entered in the header.
This customer can be another customer chosen from the customer table.

It is possible to search a customer or several customer grouped under the same criteria by selecting 'Quick customer search'. A list of matching items is generated on tabulating to the next field.
For a more advanced search, all fields present in the block can be entered. The list of matches is narrowed down with each tabulation.

• Address (field BPAINV)

This field is designed to indicate an invoicing address code for the selected invoiced customer. It is the default address of the customer.
When entering sales document, this address code will be proposed. If needed, it is modifiable.

• Pay-by customer (field BPCPYR)

This field is used to enter the pay-by customer code, initialized by default to the customer code entered in the header. The invoice payment schedule will be allocated to this BP.
This customer can be another customer chosen from thecustomer table.

• Address (field BPAPYR)

This field is designed to indicate a payment address code for the selected pay-by BP. It is the default address of the customer.
When entering sales document, this address code will be proposed. If needed, it is modifiable.

• Factor (field FCTNUM)

Code of the factor proposed as a default value on the invoices for this customer.
The presence a Factor code in an invoice indicates that this invoice is transferred to a factoring organization and that the payment must be made in favour of the Factor.

• Group customer (field BPCGRU)

The group customer code is initialized by default to the customer code entered in the header.

• Risk customer (field BPCRSK)

Code of the customer on which the credit control is performed.
This customer is initialized with the Bill-to customer, the Pay-by customer or the Group customer depending on the value taken by the common data parameter INIBPRRSK - Risk BP initialization. It can be modified: it can be the value of the customer itself or any other customer selected in the customer table.

• Accounting code (field ACCCOD)

This field is designed to specify the accounting code of the BP.
The accounting code is a default value used when creating accounting documents.
It refers to a table that lists a certain amount of elements (collective accounts, accounts or parts of accounts) that can be used for the determination of the documents that will be posted.

• Account structure (field DIA)

The account structure is not compulsory data.
If a structure is loaded, it is submitted to be applied upon the creation of a customer invoice (once the invoice tax excl. amount has been entered).

• Payment term (field PTE)

Enter the code linked to the current BP by default, and which is used to determine:

• the payment conditions,
• the payment method,
• the open item type,
• the scheduling of payments (one or several open items: immediate credit, 30 days, end of the month, etc.)

When managing this table, it is possible to simulate the calculation rules that will be applied in entry mode.

• Payment days (field J1)

The payment days in the payment terms are replaced by the payment days introduced in the customer record.
The value entered must be a date in the month (between 1 and 30), or 99 which corresponds to the last day of the month.
The use of this date is used to automatically postpone the due date calculated up to the nearest day of the month.
There can be up to six dates for each customer.

• Unavailable period (field UVYCOD2)

In this field a predefined unavailable period can be indicated. In this case, the calculated due dates for this customer cannot be in this unavailable period. They are then postponed to the first available date.

• Settlement discount (field DEP)

Enter the code linked by default to the current BP, which is used to identify the early discount and late charge rates (up to 12). These rates will be applied to a payment depending on a number of early or late days compared to the due date.

• Payment bank (field PAYBAN)

• The automatic payment proposal processing automatically assigns this bank account to all the payments of this BP.
• This bank code is used in the Bank field of the Data tab in the Cash forecasts function.

  This code is controlled in the table of Bank accounts.

• Reminder group (field GRP)

Reminder group with which the customer is associated.

The reminder group is used to define a group of management rules that are applicable during the launch of the reminder letters.
The Type of reminder and the Reminder threshold is by default recovered from the reminder group during the creation of the record (but not re-initialized if allocated to a different group of characteristics).
However it is the values from the customer record that prevail over those of the group or the category for these two fields (if they are different ).
A customer that is not attached to a reminder grouped is not considered.

• Reminder type (field FUPTYP)

Type of reminder process for the customer.

 The reminder type, and reminder threshold, taken into account by the reminder report are those of the customer record (and not those of the reminder group which are only used upon initialization).

• This field is controlled by a local menu and can take the following values : 
  No reminder:
  The customer is never reminded.
• Reminder by invoice:
  The customer receives as many reminder letters as invoices that are late for payment.
• Global reminder:
  A single reminder level is addressed to the customer for all the late invoices.
• Global reminder by level:
  The open items are grouped by identical level and the customer receives a reminder letter by level. Each reminder level contains all the open items overdue for a given level.
• Global by lead-time: The open items are grouped by late open item ranges (for example, all open items that are overdue by 30 to 60 days).

The customer receives one reminder letter per late open item range (or more, depending on the reminder group).
Each reminder letter contains all the overdue open items for a given late range. The values for the late range can be modified via the parameters.
In this way, it is possible that for a given customer to pass from a reminder letter for level 1 to a level 3 reminder letter if the number of days variance justifies it.

• Minimum reminder (field FUPMINAMT)

Minimum amount below which reminder letter is not issued for this customer.
This amount is expressed in the common currency defined in the CURSHRFLD setup.
This minimum amount means the minimum amount of the due date or the global minimum amount of the reminder letter. One of these options can be selected when setting up the reminder groups.

• field FUPCUR

This field displays the currency of the reminder threshold, based on the value of the CURSHRFLD - Common field currency parameter.

• Open item statement frequency (field SOIPER)

Flag used to determine the frequency of the open item statements for this customer.
The frequency of these statements can be every week, every 10 days, every fortnight, every month or upon request.

• Credit card (field SEBPC)

Click Credit cardbutton to open the Payment gateway customer data window. Use this function to add and maintain multiple payment cards for a customer.

This button is available if the activity code SEPP - Credit card integrationis activated.

• Tax rule (field VACBPR)

A tax rule represents the tax territoriality principle, in other words, the calculation rules to be applied to determine the tax amount.
As a general rule, by crossing a tax rule linked to the BP with a Tax level, you can determine the tax code to be applied to the document line and so, to the entry line.
In this field, you enter the tax rule associated with the BP: this tax rule will be suggested by default in all the transactions used by this business partner.

• Exemption no. (field VATEXN)

This field is designed to enter the number assigned to the tax exemption.

• VAT collection agent (field AGTPCP)

• Regional taxes (field AGTSATTAX)

Once checked, this box is used to specify that the provincial taxes must be applied to the selected customer.

• Subject to tax (field BELVATSUB)

If this box is checked, the customer is subject to VAT. This box is checked by default when the BP country is Belgium.

• Dimension type (field DIE)

The dimension types that are preloaded in the gid match the default dimension types associated with the 'Customer' base data.

• Dimension (field CCE)

The setup determines if the analytical dimensions can be modified. They are initialized based on the setup of the default dimension.

In creation mode, if no order line has been entered and the project code is modified, the analytical dimensions are reset based on the setup of default dimensions.

In creation mode, as in modification mode, if an order line is entered and the project code is modified, the analytical dimensions are not reset.

• Provinces (field SATTAX)

This fields is designed to specify the provinces for which provincial taxes exist.
This grid is dependant from the Argentine legislation.

• Provinces (field DESSAT)

This is the title of the province.

• Application (field TYPAPL)

This field is used to define whether the tax applies upon entry in the region, upon exit, or always.

• Collection agent (field FLGSATTAX)

This field is designed to specify if the customer is a tax collector for this provincial tax.

• Tax rule (field CSHVATRGM)

This field can only be entered when the following conditions are met:

• The KPO - Portuguese activity code is active
• The customer country is Portugal

You use this field to indicate if the customer is subject to article 23 of the Portuguese law 71/2013 on VAT rules. If yes, all invoices sent to this customer will go through a specific process at the payment level, once the invoices have been settled. The payments must indeed be subject to a tax return, which means that the customer must be provided with a special payment notice listing all VAT amounts by tax level.

• VAT start date (field VATSTRDAT)

This field is mandatory when the customer is subject to article 23 of the Portuguese law 71/2013 on VAT rules.
You use it to enter the date as of which the law is enforced for the customer.

• VAT end date (field VATENDDAT)

• Address code (field BPAADD)

Use this field to codify the shipping address of the ship-to customer.
You can only use an address from the predefined addresses of the Address tab.
By default, the customer's default address is suggested as the shipping address.

• Address code (field XBPAADD)

It is the code for the delivery address unavailable in this context.

• field XBPADES

Description of the address (for internal usage). For instance: temporary address, principal warehouse address...

• Active (field XENAFLG)

This check box is used to specify if the delivery address is active or not.
When an address is inactive, it cannot be used on a new sales document.

• Language (field XLAN)

This code indicates the language of the delivery address, used in the reports linked to this delivery.
This code is controlled in the table of languages.

• Default ship-to customer (field XBPDADDFLG)

This check box is selected to indicate that this is the default customer.
The ship-to corresponding address is proposed for this customer in the quotes, orders, deliveries and invoices

• Company name 1 (field XBPDNAM0)

It is the company name for the delivery address mentioned in both fields.

• Company name 2 (field XBPDNAM1)

It is the company name for the delivery address mentioned in both fields.

• Tax rule (field XVACBPR)

Enter the tax rule associated with the ship-to customer. This tax rule is controlled in the table of tax rules.

When creating a sales document, the tax rule applying to the delivery address is suggested by default, if this address uses a specific tax rule.

• Entity/Use (field XSSTENTCOD)

Enter the Entity/use code to calculate the precise tax amount for the customer. This tax code is compatible with the Avalara system and makes it possible to determine the customer type for fiscal purposes.

This field is available for all countries. The Entity/Use code can be entered for any delivery address when a document is being processed for a country that is tax-exempt. When the Calculate alldocuments connection with SST is set to No andan Entity/use code is entered, the document is exempt from tax and not subject to processing costs.

• Sales rep 1 (field XREP0)

Enter the codes of the sales representative associated to the delivery address and controlled in the sales representatives table.
The customer's sales representatives, when defined, have priority on the sales representatives of the delivery address.
An activity code is used to define the number (maximum of 2) of sales representatives submitted as the default value upon order.

• field REPX

• Sales rep 2 (field XREP1)

Enter the codes of the sales representative associated to the delivery address and controlled in the sales representatives table.
The customer's sales representatives, when defined, have priority on the sales representatives of the delivery address.
An activity code is used to define the number (maximum of 2) of sales representatives submitted as the default value upon order.

• Preparation (field TWPRPTEX)

• Delivery (field TWDLVTEX)

• Shipment site (field XSTOFCY)

This is the storage site code from which the customer is generally delivered. This site, which is controlled in the site table, must be identified as a warehouse.

This information can only be accessed if the order is of the inter-company or inter-site type. It is used to indicated which shipping site will be used by the sales company that the inter-site/inter-company supplier identified. It will then serve to initialize the shipment site for each line of the purchase order. It is mandatory in this context.

The shipment site is initialized by order of priority, as follows:

• usual shipment site defined in the delivery address identified by the receiving site previously calculated is used. It must belong to the supplier's company,
• site identified by the supplier if it is a warehouse site.

If after this search, the site is still not identified, you must then manually enter it. A control is applied to check if the entered site belongs to the same company as the supplier site and if the site is a storing site. The Actions icon is used to view all the sites available for selection.

Specificities linked to automatically-generated purchase orders: if the shipment site is still not identified after the execution of the previous steps, the shipment site is initialized using the first warehouse site found, in alphabetical order, in the list of storage sites for the company identified by the supplier.

When generating the corresponding sales order, the shipping site of the sales order header is equal to the site defined here.

• Receiving site (field XRCPFCY)

This is the storage site code where the customer is generally delivered.
This site is used when the customer is inter-site. It corresponds to the receipt site.
The receipt site can only be entered for an intersite customer. It is controlled in the sites table and must be identified as a warehouse (Warehouse flag for the site is set to 'Yes') belonging to the same company as the customer.

• Loan location (field XBPCLOC)

Name of the location where the products will be transferred to when validating a loan delivery (location change) to identify the loan products.
Within the framework of a loan, the goods remain the site's property. To materialize the goods transfer, the dedicated locations are used.
The location type must be Customer.
The loan quantity of a product is displayed in the totals of the table Product-sites.
This notion of location is only used for the loans deliveries.
This field is only available if a shipping site is entered on the delivery address. The location needs to be attached to this site.

• Subcontract location (field XSCOLOC)

In this field, enter a location by subcontract supplier address (where the supplier is defined as a customer). This location must be of the Sub-contractor type and will be used for sub-contractor deliveries.

This filed is only available if a shipping site is entered on the delivery address. The location necessarily belongs to this site.

• Route no. (field XDRN)

Number of the round, controlled by a local menu.
This information is used when generating picking tickets or allocation lists to select the orders or deliveries linked with a carrier round.

• Delivery priority (field XDLVPIO)

In this field, specify the delivery priority (Normal, Urgent, Very urgent). The priority is used to classify orders during the delivery preparations.
It is initialized by the customer delivery address. It is used on the order lines by default where it can be modified if the delivery method for the order is not Complete. If you modify this information and order lines already exist, the system will suggest that you apply this modification to the order lines.
This information is used in the automatic allocation processing of orders to determine the priority of the orders.

The order lines applying to non-deliverable products are not impacted by this information.

• Delivery mode (field XMDL)

Enter the code used to define the information related to the transport and delivery. This code is managed in the table of delivery methods.

• Delivery lead time (field XDAYLTI)

Enter the delivery lead-time for this customer, expressed in a number of days. This lead-time is used to calculate the shipment date according to the delivery date requested by the customer.

• Carrier (field XBPTNUM)

This code identifies the carrier in charge of the carriage to determine the costs linked with the goods transportation at the customer.

• Pick ticket (field XNPRFLG)

This box, when ticked, is used to specify that the delivery notes must be edited for this customer.

• Pckg. slip (field XNDEFLG)

This box, when ticked, is used to specify that the picking tickets must be edited for this customer.

• Monday (field XUVYDAY1)

This indicator is used to identify which days of the week are work days for the customer.
If a day is declared as a work day, the customer can receive delivery on it.
If the calculation of the delivery date results in a day that is not worked, this date is automatically postponed to the first available work day.

• Tuesday (field XUVYDAY2)

• Wednesday (field XUVYDAY3)

• Thursday (field XUVYDAY4)

• Friday (field XUVYDAY5)

• Saturday (field XUVYDAY6)

• Sunday (field XUVYDAY7)

• Unavailable period (field XUVYCOD)

Use this code to specify the unavailability periods of the Business Partner (e.g. leave). During the order process, the delivery date is automatically carried over to the first available date.

This code is controlled in the table of unavailable periods.

• Incoterm (field XEECICT)

The Incoterm codes, set by the International Chamber of Commerce, seek to standardize the terms the most used in the international commerce by defining the respective responsibilities of the seller and the buyer agreed upon on establishement of the sales contract by a unique word similarly understood throughout the world.

The Incoterm code, controlled in Incoterm table is used in the INTRASTAT file (Exchange of goods declaration). It can also be used to define the price lists.

• Incoterm town (field XICTCTY)

It is the city associated to some types of incoterm. For example: FOB Le Havre. A selection window is used to choose a city listed in the system. It is however possible to enter a city that is not listed.

• Freight agent (field XFFWNUM)

The forwarding agent field is used to identify a BP appointed by the sender or the recipient to ensure transport continuity when the goods need to undergo several successive transports. The forwarding agent is controlled in the Carriers table.

The forwarding agent and their address are used in the Intrastat file to declare the flows of goods between the forwarding agent’s address and the sender’s address, or between the forwarding agent’s address and the recipient’s address.

For example, this situation applies to the shipment of goods abroad, since customs formalities are performed by a forwarding agent in another EU country. An Intrastat declaration needs to be submitted for the transfer of goods to this other EU country.

• field XFFWADD

This is the address code of the forwarding agent. It is initialized with the default address of the BP corresponding to the forwarding agent. This address is used to determine whether submitting an Intrastat document is necessary for this flow.

• EU VAT no. (field XEECNUM)

This is the VAT identification number of the buyer.
If the country of the ship-to address is different from the usual customer's country and if this customer is identified with the VAT of the ship-to country, then it is necessary to enter the VAT number.

• Intrastat increase (field XEECINCRAT)

This field is subject to the Exchange of goods declaration (Intrastat).

This conversion factor is used in the Intrastat declaration for the exchange of goods. It is used in supplier invoices and applied to the fiscal value of the product line to obtain the statistical value.
It is initialized by either the increase conversion factor entered on the product-supplier record or the supplier record.

• EU VAT ID validation (field EVCVAL2)

• Validated (field EVCVALDON2)

• Intrastat transp. location (field XEECLOC)

A transport location must be specified in the EU exchange declaration. It is combined with the Incoterm code in order to determine the delivery conditions referring to the sales contract terms that specify the respective obligations of the buyer and seller.

This information is not used in the French declaration.

• Address (field BIDBPAADD)

This field specifies the address code of the bank ID number, controlled in the address codes of the managed entity (company, site, customer, supplier, etc.).

This address code is used to define the default bank ID number in payment contexts where an address is known.

• Country (field BIDCRY)

This code is used to identify the country associated with the bank account.

The country table, containing this code, gathers information that is useful to perform controls, and namely:

• the telephone number format,
• the format of the number identifying a company or an activity (SIRET, NAF in France),
• the postal code format,
• the format of the Bank ID number code.

• IBAN prefix (field IBAN)

The IBAN is an internationally agreed standard of identifying bank accounts in a structured format.
IBAN can be used in national and/or international payment transactions (country-specific).
The IBAN code consists of: 

• A 4-digit IBAN prefix composed of:
  - a country code (2 letters),
  - two check digits
  This prefix is displayed. It is calculated automatically upon the bank account information entered in the Bank ID field.the bank account information (country specific, up to 30 characters).
• The bank account information (country-specific, up to 30 characters).

 Not all countries support IBAN. The IBAN format applied to bank accounts is controlled by the IBAN management option, defined in theCountries setup.

• Bank acct. number (field BIDNUM)

This number identifies the bank account of a given bank, for a given country.
The entry format of a Bank ID number is dependent on the country where the bank is domiciled.

For the entry of the Bank ID number to be correct, it is necessary to predefine the entry format in the Countrytable and to activate the option IBAN managementfor those countries supporting the IBAN format.

 In case of an IBAN this field has to contain the bank account part only, beginning from the 5th character of the IBAN. The first 4 characters of the IBAN (country code and check digits) are calculated automatically and displayed in the field IBAN pref.

• Default (field BIDNUMFLG)

This field indicates that the Bank ID number is used by default for payments (in the absence of a more precise rule).

• Currency (field BIDCUR)

This code is used to identify the currency associated with the bank account.
It is managed in the currencytable.

It is recommended to use the ISO coding during the creation of a new currency.

• ISR customer no. (field BVRNUM)

This field requires the KSW – Swiss localization activity code to be active. You use it to enter the ISR customer number for the given bank account. This number is used for payments with ISR number (inpayment slip with reference numbers).

For suppliers, the ISR customer no. is also used to search for a matching BP account if support for ISR code line entry on purchase invoices is active in the SWIPURBVR - Swiss ISR usage purchasing parameter (LOC chapter, SWI group).

Refer to the Swiss legislation guide on the How to tab for more details regarding payment and ISR setup.

• Paying bank (field PAB1)

This field, which is mandatory for payments, defines the paying bank related to the account number. The first line contains the name of the bank.

• Beneficiary (field BNF)

This field identifies the bank account's beneficiary (physical or moral person).

• Paying bank 2 (field PAB2)

• Paying bank 3 (field PAB3)

• Paying bank 4 (field PAB4)

• BIC code (field BICCOD)

To perform the automatic processing of payment requests, the sender's bank needs the BIC code of the recipient's bank. This code is an ISO identifier managed by the international banking system, and namley the SWIFT system, the Society for Worldwide Interbank Financial Telecommunication.

The BIC code is the only standardized bank identifier at international level. All banks can have a BIC code, even if they do not belong to the SWIFT network.

The BIC code can be comprised of 8 to 11 characters. In both cases, the first 8 characters of the BIC code generally designate the bank's head office and are structured under the form BBBB PP AA, which correspond to the following information :

• BBBB is the bank mnemonic identifier;
• PP is the ISO country code;
• AA stands for a service code often to serve a geographic purpose.

• Intermediary bank (field MIDPAB1)

In some commercial exchanges, upon the request of Business Partners or payment issuing banks, an intermediary bank is sometimes used. For that purpose, the identifiers of this bank must be entered (BIC code, paying bank, country). This information remains optional (it does not need to be entered if no intermediary bank is mandatory).

• Paying bank 1 (field MIDPAB2)

• Paying bank 2 (field MIDPAB3)

• Paying bank 3 (field MIDPAB4)

• BIC code (field MIDBICCOD)

• Country (field MIDCRY)

• Contact code (field CCNCRM)

Each contact associated with the record is identified by a unique key, which is used to share contacts common to several records.

This code defines the unique key in the contact record. This key can be manually assigned or if it is not entered, it can be defined via the CCN sequence number counter.

By default, this counter is constructed of a sequence number made up of 15 characters. To ensure the correct functioning of the Contact object, it is strongly advised to conserve these standard characteristics.

• Last name (field CNTLNA)

Indicate the family name of the contact.

• Contact code (field KCCNCRM)

Each contact associated with the record is identified by a unique key, which is used to share contacts common to several records.

This code defines the unique key in the contact record. This key can be manually assigned or if it is not entered, it can be defined via the CCN sequence number counter.

By default, this counter is constructed of a sequence number made up of 15 characters. To ensure the correct functioning of the Contact object, it is strongly advised to conserve these standard characteristics.

• Title (field KCNTTTL)

This field associates a closing sentence with a contact's family name.
This information can be used on documents to be sent to contacts.

• Last name (field KCNTLNA)

Indicate the family name of the contact.

• First name (field KCNTFNA)

First name of the contact.

• Function (field KCNTFNC)

This field specifies the position of the contact to choose from a pre-defined list.
The local menu 233 lists all the possible positions.

• Department (field KCNTSRV)

This text field indicates the department to which the contact is attached.
No table controls this information.

• Role (field KCNTMSS)

This field, used for information purposes, makes reference to the codes entered in miscellaneous table 906.

• Language (field KCNTLAN)

This fields specifies the language of the contact.

• Date of birth (field KCNTBIR)

Birthday of the contact, only present for information reasons.

• Category (field KCNTCSP)

• Address (field KCNTADD)

The value of the contact's address code, controlled in the address codes of the supported entity ( Addressestab), is for information purposes only. This code is used to link the contact to one of the addresses of the relevant entity.

• field KADDNAM

Title associated with the previous code.

• Email (field KCNTWEB)

This field is used to specify the email address of the contact.

• Telephone (field KCNTTEL)

This field indicates the phone number. Its entry format depends on the country.
The level of control applied to the entered number format depends on the general parameter CTLTEL - Phone number control (SUP chapter, INT group).

• Fax (field KCNTFAX)

This field specifies the fax number where the entry format is identical to that of the telephone and is dependent on the country.

• Mobile phone (field KCNTMOB)

This field indicates the mobile phone number with an entry format that depends on the country.

• Mailing prohibited (field KCNTFBDMAG)

This indicator is designed to specify that the contact cannot be selected in a mailing.

• Default contact (field KCNTFLG)

When this box is checked, the selected contact becomes the default contact.