BPs
Use this function to create and maintain the Business partner table and associated tables: Addresses, Contacts, and Bank details.
You can create, display, and update the database information associated with a business partner.
A business partner can be a supplier, customer, sales representative, carrier, order-giver, service provider, factoring organization, and so on.
A business partner can have multiple roles. A customer can also be a supplier and/or service provider and/or carrier and so on. In this case, there is a single business partner record, which is used to provide the grouped common identifying data including related roles, different addresses, bank accounts, and contacts.
Each business partner type has certain common data, as well as additional data linked to one of the business partner roles.
For order-givers and service providers, the additional information is available from the related functions in the Actions panel.
An intersite business partner ships product between sites without invoicing.
Prerequisites
Refer to Implementation.
Screen management
Header
This section details basic information about the business partner.
Category (field BRGCOD) |
This is the customer category or supplier category associated with the BP. You can
When converting a BP to a customer or a supplier, using the same category as the one used for the BP makes it possible to assign the customer or supplier to the same code as the BP. |
BP (field BPRNUM) |
Enter or search for the BP code. When you add the code, the short and long descriptions populate with existing information. |
Identity tab
Use this section to enter the identification data for the business partner such as selecting roles and entering role-specific details.
Select the Service provider checkbox to access the Service provider info from the Actions panel, Functions menu. The term Service provider refers to an after-sales service provider you can call when all internal customer support employees are unavailable.
Select the Service caller (Order-giver) checkbox to access the Order-giver info from the Actions panel, Functions menu. The term Order-giver groups all customers for the account for which customer support services are carried out. That is, service requests that are processed for customers of our customers.
EU VAT ID validation
You can interactively validate the EU VAT no. by selecting the EU VAT ID validation icon.
Note: This includes validating GB VAT numbers.
A message box displays with the validation results. The exact content varies depending on the check result and web service used.
- If the validation is successful, you receive a confirmation message and the Verified checkbox is selected.
- If the validation failed, you receive a message that displays the reason for the failure.
- If the validation could not be completed (for example, if only the VAT number was validated and not the address), you have the option to accept the results as valid or not. If you select Yes, the Verified checkbox is selected.
Note: The validation results for EU VAT IDs are stored in a table. GB VAT numbers are not stored.
If a previously-validated VAT number is modified, the Verified checkbox is cleared.
Validation levels:
A Qualified validation verifies the EU VAT no. and company name and address. All data must be valid.
An Unqualified or simple validation only verifies the EU VAT no. 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 no., the standard company address is used.
You can manually revalidate VAT numbers using the EU VAT ID revalidation function (EVCBAT).
Note: This field is only available if a web service is identified by the EVCSERVICE – Webservice for EU VAT ID parameter (CPT chapter, VAT group) and the sender's EU VAT number is set by the EVCCOMPANY—EU VAT ID source company parameter (CPT chapter, VAT group)
Identity tab
Short description (field BPRSHO) |
Title used in some screens or reports when there is not enough space to view the long title. By default the short title, the long title, or the column header of a data are saved in the connection language of the user.
A user who logs on with this language sees the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions are available in the folder language. The connection language needs to be defined as a default language for the folder. |
Company name 1(field BPRLOG) |
Business partner company name. |
Company name 2 (field BPRNAM) |
Business partner company name. |
Natural person (field LEGETT) |
When selected, it means the BP is a physical person. If not, it is a corporation. If the BP is corporation, you must enter the VAT identification number and the Site tax ID number if required for their country. |
Mailing prohibited (field BPRFBDMAG) |
Select this option to prevent mail from being sent to this company. |
Country (field CRY) |
This code is used to identify the Country and determines the following formats and if they are required or not for the country:
|
Language (field LAN) |
Enter or select the default language. |
Currency (field CUR) |
This code is used to identify the currency of a site, a BP, etc. It is controlled in the currency table. Use the ISO coding when creating a new currency. |
Site tax ID no. (field CRN) |
Unique identification number for the company.
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 organizations 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 code. |
Doc. type (field DOCTYP) |
This field only displays when the KSP activity code is activated. |
EU VAT no. (field EECNUM) |
This is the VAT identification number of the BP or the GB VAT number. This European VAT number must be entered on all the invoices destined to or coming from the European Union. This number starts with two letters identifying the business partner country followed by a number depending on the country. In France the number is comprised of FR, then 2 numbers identifying the tax office of the place where the company conducts its activities, followed by the Company tax ID no.(SIREN) of the company. This information must necessarily be entered if the Company Registration number is set up as being mandatory for the country of the company. |
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) Select the EU VAT ID validation action to interactively validate your EU VAT ID or GB VAT number. A message box displays with the validation results. The exact content varies by check result and web service used.
Note: Successful validation results are stored in a table. If a previously-validated VAT ID is modified, the Validation checkbox is cleared. Validation levels:
Address management:
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 Verified checkbox is cleared. A message box displays with the validation results. The exact content varies by check result and web service used.
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) |
VAT number (field VATNO) |
Registration number (field REGNUM) |
EORI number (field EORINUM) |
If the Country profile for this entity has the EORI identification field selected, you can enter an EORI number, which is prefixed with the country's ISO code. Note: This number is needed for entities doing business within the UK and for EU companies importing and exporting goods and services with UK companies. |
Status (field VALIDATE) |
This displays whether this record was compared to the French Sirene® database. You can set this value using the BP ID validation function. |
Validated by (field USR) |
When a users changes the status to validated, their user ID automatically displays. |
Intersites
Intersite (field BETFCY) |
Select this checkbox to indicate if this is an intersite BP:
|
Site (field FCY) |
The site code for a BP within the frame of multisite exchanges. The following data needs to be entered:
|
Roles
Customer (field BPCFLG) |
Sales rep (field REPFLG) |
Prospect (field PPTFLG) |
Public sector (field BPPFLG) |
This field can be accessed if the MAXPD - Maximum period (companies) activity code is activated. Select this checkbox to specify that the BP is a public sector organization. In this case, the maximum number of days for the last payment due date of an invoice destined to this BP is defined by the DMAXPAYP - Maximum period (Public sector) parameter (TC chapter, RSK group). If this BP is a private sector company, the period for the last payment due date of an invoice destined to this BP is defined by the DMAXPAY - Maximum period (companies) parameter (TC chapter, RSK group). However, you can have an special agreement with this BP and grant them a longer period. Enter this period at the level of the Contractual period field (DAYPAY), available in the BP/Company tab. |
Supplier (field BPSFLG) |
Miscellaneous BP (field BPRACC) |
Miscellaneous business partner (for Sales and Purchase ledger accounting). If this box is ticked, the document type and accounting code fields become active. |
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) |
Service caller (field DOOFLG) |
The contractor represents the actual customer for whom a service request is made. |
Ship-to (field PTHFLG) |
Field reserved for Argentina (KAG activity code) designed to specify the VAT collector. |
Grantor (field CCNFLG) |
This tick-box is designed to list the BP as Grantor; thus, the BP will be listed as Grantor in concession agreements. |
Electronic invoice
Electronic invoice type (field EINVTYP) |
Select the invoice type. Not used is selected by default and no other field display in this block. |
Service code (field INTSRVCOD) |
Routing code (field RTGCOD) |
Electronic address (field ELCADD) |
E-invoicing mapping code (field MAPCOD) |
Addresses tab
Use this section to enter the business partner addresses. You need to enter at least one address. When several addresses are linked to the same BP, you must define one of them as the default address. In creation mode, the first address entered is the one suggested by default.
When entering the post code, an automatic control can be performed and the town entered depending on the settings of the CTY - Nonexistent city alert, POSCOD - Nonexistent postal code alert, and POSCODCPY - Multi-country post codes parameters (SUP chapter, INT group).
Addresses grid
Address code (field CODADR) |
Address code of the business partner (BP). |
Detail
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.).
You cannot modify or delete an address code when it is used at the level of a Bank ID number or for a contact. |
Description (field XBPADES) |
Country (field XBPACRY) |
Enter or select the country code, managed in the Country table. The country determines certain formats including:
|
Description (field XCRYNAM) |
field XADDLIG1 |
field XADDLIG2 |
field XADDLIG3 |
Postal code (field XPOSCOD) |
Enter the postal code for the city according the country-specific format, as defined in the Country table. If defined, when the postal code is changed or entered, the city name automatically displays. The reverse is true is you enter the city name. Specific cases:
The control of this information is required if the POSCOD - Nonexistent postal code alert parameter (SUP chapter, INT group) is Yes. |
City (field XCTY) |
Enter the city. If defined in the Country table, the postal code automatically displays. If the CTY - Nonexistent city alert parameter (chapter SUP, group INT) is set to Yes, a control warns you that the postal code is missing. Notes:
|
field ITINERAIRE |
Click this icon to open a mapping site and locate the entered address. |
field XSAT |
Website (field XFCYWEB) |
External identifier (field XEXTNUM) |
Default address (field XBPAADDFLG) |
Telephone
field XTEL1 |
field XTEL2 |
field XTEL3 |
field XTEL4 |
field XTEL5 |
field XWEB1 |
field XWEB2 |
field XWEB3 |
field XWEB4 |
field XWEB5 |
Accounting tab
Use this section to enter the information used in accounting to consolidate and add any information required for European accounting.
An access code is available for you to filter the business partners presented in the miscellaneous accounting reports.
Accounting code (field ACCCOD) |
This field is used to specify the accounting code of the BP. |
Consolidation group (field GRUGPY) |
Consolidation area: field under control of the CSL activity. Choose the group of companies for which consolidations are to be carried out. |
Consolidation (field GRUCOD) |
This code is used during the data extraction operation in prevision of the consolidation. Used to identify the company from which the entries are extracted. |
Report access code (field ACS) |
Access code used as a filter for accounting reports. |
Fiscal code (field FISCOD) |
Fiscal code (for Italy only). |
IVA partita (field VATNUM) |
Field reserved for Italy to enter the VAT number. |
Item type for expense account (field BPRGTETYP) |
The document type (3 alphanumeric characters) makes reference to the Document type record that characterizes the documents generated in the Sales and Purchase ledger accounting. A selection and a tunnel are available from the contextual menu. |
Cash excluded (field CFOEXD) |
This field defaults to 'No', meaning the BP is taken into account in the forecast management. |
CFONB payment (field MODPAM) |
This field is used to indicate the payment method.
This information is taken into account upon generation of the bank files. |
Related company (field CPYREL) |
Partner (field CSLBPR) |
Bank details tab
Use this section to record bank details and associated paying banks. The entry format of the Bank account no. depends on the country where the bank is based.
The information related to international transfers can be accessed in record mode, usually the Intermediary bank. An intermediary bank is often used in commercial relationships with non-western countries at the request of the BP or issuing bank.
If the conditions are met, the Enter bank details window is automatically displayed when leaving the Country field. In this window, you can enter the bank details in your local format.
See Enter bank details window documentation for more information.
Grid Bank details
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:
|
IBAN prefix (field IBAN) |
The IBAN is an internationally agreed standard of identifying bank accounts in a structured format.
Not all countries support IBAN. The IBAN format applied to bank accounts is controlled by the IBAN management option, defined in the Countries setup. |
Bank acct. number (field BIDNUM) |
This number identifies the bank account of a given bank, for a given country. For the entry of the Bank ID number to be correct, it is necessary to predefine the entry format in the Country table and to activate the option IBAN management for 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) |
Use this field to specify that this bank account number is used by default for payments, for the selected address. |
Currency (field BIDCUR) |
This code is used to identify the currency associated with the bank account. 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. |
Nonresident (field ACCNONREI) |
Select Yes if the account is not located in the country where the owner lives. This identifies the BP account as a nonresident account. No is the default value. A nonresident account is used to enter the Economic reason code in payments when the following conditions are met:
|
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 :
|
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) |
Bank sort codes |
Enter bank details |
Use this window to enter the bank details in your local format. The information entered is then automatically recovered in the fields of the Bank details section. This window automatically opens when leaving the Country field, but only if the following conditions are met:
|
Contacts tab
In this section, you can list the contact persons for the BP in the Contacts table. You also need to indicate the default contact.
To add a new contact:
- Select an existing Contact (relationship)
- Create a new contact:
- Enter a code
- Add details: the code is automatically created when saving the record.
In both cases, the contact is automatically recorded in the Contacts table.
The management of contacts, from the Contacts function, ensures that each individual record is unique. A contact with a particular role can be recorded as one Contact amongst many business partners. Based on the record of one contact, you can create relationships across records, provided that they have a Contact section.
A contact can only be recorded as a person or individual. Only identification information such as the last name, first name, date of birth are common to the contact (relationship) record and to the details entered at the general contact level.
Other information such as the address, email address, landline number and fax number are managed separately between the relationship contact and each one of his/her contacts. At the 'relationship' contact level, the information is considered as being personal; at the general contact level, the information is considered as being professional.
For further examples, see the documentation of the Contacts function.
Grid Contacts
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. |
Detail
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. |
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. |
Department (field KCNTSRV) |
This text field indicates the department to which the contact is attached. |
Role (field KCNTMSS) |
This field, used for information purposes, makes reference to the codes entered in miscellaneous table 906. |
Language (field KCNTLAN) |
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. |
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) |
Default contact (field KCNTFLG) |
When this box is checked, the selected contact becomes the default contact. |
Contacts |
Copy contacts |
BP / company tab
The display of this section is subject to the MUL - Multi-company business partner activity code.
Use this section in a multi-legislation and multi-company context. You can define exceptions by indicating specific information by company/BP at the level of the BP and/or customer. For example, the tax rule, payment condition, default BP discount code, accounting code, and so on.
Grid
Company (field CPY) |
Company for which the BP exception is applied. This exception can concern:
|
Customer tax rule (field VACBPC) |
The customer tax rule by default is stored in the Customer record. |
Supplier tax rule (field VACBPS) |
The supplier tax rule by default is stored in the Supplier record. The general principles linked to the multi-legislation setup are detailed here. |
Customer pymt. terms (field PTEBPC) |
The customer payment conditions are stored in the Customer record. |
Supplier pymt. terms (field PTEBPS) |
The supplier payment conditions are stored in the Supplier record. |
Customer early disc. (field DEPBPC) |
The customer discounts and late charges are stored in the Customer record. |
Supplier early disc. (field DEPBPS) |
The supplier early discounts and late charges are stored in the Supplier record. |
Customer acct. code (field ACCBPC) |
The customer accounting codes are stored in the Customer record. |
Supplier acct. code (field ACCBPS) |
The supplier accounting codes are stored in the Supplier record. |
Authorized entry (field ACEAUZ) |
The entry of commercial documents or accounting entries is authorized for all business partners, by default. For a multi-company management, you can set this field to No to disable the entry for the business partner on specific companies. Particular cases: Prospects
|
Cash excluded (field CFOEXDCPY) |
Contractual period (field PAYDAY) |
This field can be accessed if the MAXPD - Maximum period (companies) activity code is activated. It is relevant only if the BP is a private sector company, not a public sector organization. |
Payment bank ISR/QR (field PAYBANBVR) |
This field is related to the SWICUSBVR - Swiss ISR usage Sales (LOC chapter, SWI group) parameter. The payment bank information is used to print the necessary sender’s bank account information on ISR payment forms. Use this bank account as the destination account when paying the invoice. The ISR payment bank for the invoice is determined by the Payment bank ISR field in one of the following functions. The system pulls the information from the first entry found:
|
Electronic invoice type (field EINVTYP) |
E-invoicing mapping code (field MAPCODBPC) |
Reports
By default, the following reports are associated with this function :
BPARTNER : Business partner listing
GLGRP : GL journal account details
GLGRPAUX : Auxiliary general ledger
GLGRPDEV : General ledger/currency
GLGRPDEVAUX : Auxiliary ledger/currency
TRSNMOUV : BPs with no postings
UNALLOCCASH1 : List of prepymts to allocate
This can be changed using a different setup.
Customer
When the business partner is a customer, you can use this action to manage data specific to the customer.
Supplier |
When the business partner is a supplier, you can use this action to manage data specific to the supplier. |
Carrier |
When the business partner is a carrier, you can use this action to manage data specific to the carrier. |
Sales reps |
When the business partner is a sales rep, you can use this action to manage data specific to the sales rep. |
Prospect |
When the business partner is a prospect, you can use this action to manage data specific to the prospect. |
Menu Bar
Use this function to manage information essential to the management of service suppliers. A service provider is a partner company that accepts to carry out certain work to solve the customer service requests. The service providers must be have certain skills and competences. They must be part of the geographic areas in which they have agreed to intervene on. This function is also used to enter the financial conditions for the business collaboration. Skills group Enter all the skills groups in which the service supplier has been recognized as competent. Intervention fields Define the geographic areas in which the service supplier can intervene. It is based on a mechanism that can only be applied to certain countries. In fact, this functionality is based on a certain type of post code structure. For example, if a service provider can intervene throughout the Hauts de Seine Department (France), it is possible to enter:
This service provider will then be suggested for any customer whose location falls within a post code starting with 92. This method of functioning requires a structure which is slightly hierarchical giving a meaning to each letter or number in the post code. For the countries where this functioning cannot be used, each complete post code must then be opened. It is also possible to declare that a service provider has access to All fields. This checkbox indicates that the service provider has no restriction on the intervention location. Financial info Use this section to save the normal intervention conditions negotiated between two parties. The valuation of an intervention is carried out on the basis of an hourly rate. This amount is then increased by any travel expenses. Several expense invoicing formulas are proposed as standards:
The payment conditions for the intervention and any expenses can also be saved. |
This function behaves in a specific way. The order giver management presents a rarely used characteristic. It is possible to plan in advance the nature of the information that it will be necessary to manage in order to maintain a relation with an order-giver. This information can for example correspond to one of the notions given below or to something completely different.
etc. Thus, from its initial opening, this window contains a certain number of unusable fields. The window contains:
To be able to use one of these fields, you must first define its characteristics by clicking on Function/Define the screen in the actions panel. Alphanumeric type fields: It is possible to define three characteristics for this type of field.
Other types of fields: All the fields that are not of the alphanumeric type obey the same setup procedure. Only two characteristics can be defined for these fields.
These setup operations can be carried out on unused fields and also on fields that have become obsolete. In fact, the information has been stored throughout the usage duration of this field. You are thus warned before any semantic modification of a field that leads to the deletion of all the information previously saved in this field. It is then necessary to be sure that the information to be deleted is of no further interest. When the window setup is complete, you must click on the Functions/Safeguard the configuration menu. The setup applies to all the order-giver's records. The screen is identical for all order-givers. It is not possible to use a different window structure for different order-givers. The window is then automatically closed and the following message displayed: The window must be reopened to benefit from the information. On alphanumerical fields, click Selection from the Actions icon in order to display the list of labels linked to fields that have been defined in configuration mode. If numeric information is related to the financial amounts, these amounts must be expressed in the Business partner currency. This currency is displayed for information purposes in the window header. |
This function opens a new window that displays together the Before-sales and After-sales activity of the current Business partner. The actions carried out are sorted from the most recent to the oldest. All the following record types are grouped within this history:
On each table line, click Detail from the Actions panel to access the complete record of each action displayed in the history. |
Note: This option is only available if you have the license for Data Clean and Control.
This validation functionality is available in several functions. It is limited to French companies, which are listed in the French government SIRENE database. You can use it to confirm data related to an existing BP and to help build an accurate BP record when creating a new BP. You can access this functionality from the Site tax ID no. field or from the Actions menu in these functions:
How to validate a BPThis only applies to French BPs registered in France. For an existing BP: You can compare data in your record with the SIRENE database. The BP information block displays data in the current record that is compared against the SIRENE database. For a new BP: You can find information about a new BP to complete the new record. In this case, the fields in the BP information block are empty. If you are validating an existing BP, you can update your record. Performing an update overwrites existing data with data from the SIRENE database.
In the Site tax ID no. field, select BP ID validation from the More actions icon. Or select BP ID validation from the Actions menu. In the BP ID validation screen that opens, you can search the SIRENE database according to the search criteria you enter. You can search by 1 or up to all 4 criteria. All entered criteria are considered in the search. For example, if you search by a company name and a city, results match both inputs. If you enter a Company name, you can search for all companies that begin with the characters entered in that field or for all companies that contain those characters. If there is no match, try removing 1 or more criteria and search again. Searches are performed for all criteria entered.
This is helpful if you know the company name but not the SIREN or SIRET number.
The Company information grid displays results, if any, found in the database based on all criteria entered. The Site information grid displays a list of sites with unique SIRET numbers that share the same SIREN number. If you search by Company tax ID no. and Site tax ID no., there is only 1 result in the grid because SIRET numbers are unique for each company site. Working with search resultsThe Company information and Site information grids display results from the search of the SIRENE database. Each grid only displays up to 200 records. If there are more than 200, you need to refine your search criteria to reduce the number of results. The EU VAT no. is not part of the SIRENE database. Sage X3 calculates the number that displays in the grid.
The grids highlight fields where the data in your record and the database do not match. If a field is highlighted in yellow, the SIRENE data does not match your records. If you are creating a new BP, the columns are highlighted yellow but there are no reasons. If a row is highlighted in red, that company is listed as closed in the SIRENE database. The Reason column details why a field or fields are highlighted such as
In the Site information grid, select a site with an address that is a match for the company you want to validate. The matching company in the Company information grid is automatically selected and the Site information grid only displays the site or sites for that company. For an existing BP: If the records are different, you can select Update to overwrite the current BP record with the data from SIRENE. This action cannot be undone. Be sure it is the same BP before your update the record.
For a new BP: Selecting Update populates the new BP record with the data from SIRENE. |
Use this function to directly access the appointments object. If you click New, the appointment is populated with the BP code. |
Use this function to directly access the calls object. If you click New, the call is populated with the BP code. |
This function is used to directly access the tasks object. If you click New, the task is populated with the BP code. |
This function is used to directly access the appointments object. If you click New, the appointment is populated with the BP code. |
This function is used to directly access the calls object. If you click New, the call is populated with the BP code. |
This function is used to directly access the tasks object. If you click New, the task will be pre-entered with the BP code. |
This function is used to directly access the projects object. If you click New, the project is populated with the BP code. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
At least one address must existThis message is displayed in creation or modification of a business partner, upon of validation, if no address has been assigned to the business partner.
An address must be defined as defaultThis message is displayed in creation or modification of a business partner, upon validation, if no address has been assigned as the default address.
Country: ...non-existent recordThis message is displayed when the country code entered does not exist in the Countries table. Use the Actions icon to access the Countries table and create the country record.
Code already exists on line NNNSeveral events can trigger this message:
- The Bank account no. already exists in one of the lines in the grid. You must enter another number.
- The address code already exists in one of the lines in the grid. You must enter another code.
- The name of the contact already exists in one of the lines in the grid. You must enter another name.
This message is displayed when the currency code entered does not exist in the Currencies table. Use the Actions icon to access the Currencies table and create the currency code.
Non-existent address codeThis message is displayed when the address code entered in the bank details or for the contact does not exist at the level of the selected entity. You must define this code beforehand in the Address section.
Post code does not existThis message is displayed when the post code entered does not exist in the Post codes table. This error is not blocking and it is possible to continue with the entry. To prevent this message from displaying again, you must create the post code in the Post codes table.
Town does not existThis message is displayed when the town/city name entered does not exist in the system. This error is not blocking and it is possible to continue with the entry.
This address code is used in a Bank IDThis message is displayed when the address code that you have attempted to delete is used at the level of one or more bank account numbers. In order to delete an address code, you must first remove it at the bank account number level.
This address code is used in a contactThis message is displayed when the address code that you have attempted to delete is used at the level of one or more contacts. In order to delete an address code, you must first remove it at the Contact level.
Tables used
Refer to documentation Implementation