Onventis supports different interfaces for suppliers, which can be addressed either via so-called interface events (outgoing) or via BcJob (incoming/outgoing).
These are:
- Excel
- Onventis proprietary XML format (XML/XSD)
- SAP IDoc/RFC
interface events
Outgoing interfaces are controlled in Onventis Buyer via so-called “Interface Events”. Currently, four events are available for the supplier data object.
- 5002 (Supplier_AcceptSupplierUpdate)
- 5003 (Supplier_StatusChanged)
- 5005 (Supplier_Deleted)
- 5006 (Supplier_WorkItemCompleted)
Information
Interfaces can only be set up in cooperation with Onventis Consulting. If you are interested, please get in touch with your direct contact person. |
Events
The events are explained below.
5002 (Supplier_AcceptSupplierUpdate)
Event 5002 (Supplier_AcceptSupplierUpdate) is executed when the user manually triggers the action > “Transfer to ERP system” in the respective supplier master record at the organizational level (central).
5003 (Supplier_StatusChanged)
Event 5003 (Supplier_StatusChanged) is triggered when a supplier status change is processed automatically without a work object (automatic status assignments based on the status mapping function from supplier qualification).
5005 (Supplier_Deleted)
Event 5005 (Supplier_Deleted) is triggered when a supplier is deleted in Onventis Buyer.
5006 (Supplier_WorkItemCompleted)
Event 5006 (Supplier_WorkItemCompleted) is triggered when a work item is finally completed in Onventis Buyer (central level and organizational unit level).
When is a work object considered complete:
- If no approval was required, the event is triggered immediately after the work object has been successfully processed.
- If an approval workflow is configured and approval is required, the event is triggered immediately after the last approval step is approved (if the work object was rejected, the event is not triggered and the work object is not processed in the master record).
Excel import and export
The supplier management in Onventis Buyer offers the possibility to export the supplier list into an Excel file. At the same time, suppliers can also be imported via BcJobs using corresponding Excel files.
The supplier import and export via Excel also supports the options for extending suppliers for organizational units.
This means that the enhancement for organizational units can already be made when importing the supplier data, and master data can be defined for the respective organizational units.
File structure
The Excel file (supplier import (total)) is divided into five different spreadsheets, which can also be used as independent files and imports:
- Supplier (vendor master record (central))
- Address (optional addresses, which are assigned to the suppliers via the unique, central supplier number)
- Bank (optional bank details, which are assigned to the suppliers via the unique, central supplier number)
- Contact (optional contacts, which are assigned to the suppliers via the unique, central supplier number)
- OrgUnitSpecific (vendor master record (organizational unit); organizational unit-specific specifications of master data and configurations)
Files and BC jobs
The import templates in Excel format are available on the Master Data Import Templates page.
The following BcJob configurations are required to use the import templates:
Description | BcJob configuration |
Vendor import (total) via Excel
This import includes all the individual imports mentioned below in a single file. |
Controller: Import Controller
Adapter: Supplier Adapter Converter: Supplier Import-Converter (Excel) Port: depending on scenario |
Import of supplier addresses via Excel | Controller: Import Controller
Adapter: Supplier Address Import Adapter Converter: Supplier Address Import-Converter (Excel) Port: depending on scenario |
Import of supplier bank details via Excel | Controller: Import Controller
Adapter: Supplier Bank Details Import Adapter Converter: Supplier Bank Details Import Converter (Excel) Port: depending on scenario |
Import of supplier contact persons via Excel | Controller: Import Controller
Adapter: Supplier Contact Import Adapter Converter: Supplier Contact Import-Converter (Excel) Port: depending on scenario |
Import of organizational unit-specific characteristics via Excel | Controller: Import Controller
Adapter: Supplier OrgUnit Extension Import Adapter Converter: Supplier OrgUnit Extension Import-Converter (Excel) Port: depending on scenario |
Spreadsheets
The individual spreadsheets (or single imports) and the columns/attributes they contain are described below.
Supplier
Supplier | ||||||
Column heading | Description | Mandatory field | Example value | Data type (length) | Import | Export |
SupplierNr | Unique supplier number of a supplier within an Onventis Buyer organization | yes | ONV000001 | varchar(35) | yes | yes |
Disabled | Blocks the supplier’s access (to the Onventis Supplier Organization provided by the provider)
0 = Vendor access not blocked |
no | 0 | tinyint | yes | yes |
QualificationStatus | Title of the supplier Qualification status at the organizational level
0 = Not yet qualified |
no | Successful | translation string | no | yes |
NrExtern | External supplier number of a supplier within the Onventis Buyer Organization | no | EXT000001 | varchar(35) | yes | yes |
AdditionalNumbers | Additional number(s) | no | ADD000001 | varchar(35) | yes | yes |
DunsNumber | Nine-digit D-U-N-S number assigned by D&B (Dun & Bradstreet, Bisnode) | no | 314820668 | varchar(35) | yes | yes |
DunsCheck | Result of D-U-N-S validation (requires Bisnode Small Package)
0 = Validation not performed |
no | 2 | int | no | yes |
DunsValidationDate | Timestamp of the DUNS validation | no | 17.02.2021 16:12 | timestamp | no | yes |
Name1 | Company name | yes | ONVENTIS GmbH | nvarchar(100) | yes | yes |
Name2 | Company addendum | no | Stuttgart location | nvarchar(100) | yes | yes |
ManagingDirector | Management (multiple entries separated by commas) | no | Frank Schmidt | nvarchar(200) | yes | yes |
ManagingDirectorTitle | Management title
0 = Managing Director |
no | 0 | int | yes | yes |
DistrictCourt | Register number | no | HRB 21731 | nvarchar(100) | yes | yes |
CommercialCourt | Registry Court | Local court Stuttgart | nvarchar(100) | yes | yes | |
Currency | Currency of the supplier (if not specified, the currency is taken from the provider) | yes (if nothing is specified, the currency is taken from the provider) | EUR | char(3) | yes | yes |
Url | Website / URL | no | www.onventis.de | nvarchar(200) | yes | yes |
Street | Street of the main address | depending on the configuration of the organizational settings within the Onventis Buyer organization | Gropiusplatz 10 | nvarchar(100) | yes | yes |
Street2 | Street 2 of the main address | no | STEP Area | nvarchar(100) | yes | yes |
Building | main address building | no | House 1 | nvarchar(50) | yes | yes |
Floor | Floor of the main address | no | 5 | nvarchar(50) | yes | yes |
Room | Room of the main address | no | 05 Oct | nvarchar(50) | yes | yes |
ZIPCity | Postcode of the main address | yes | 70563 | varchar(20) | yes | yes |
City | Place of the main address | yes | Stuttgart | nvarchar(50) | yes | yes |
Country | Country of the main address as ISO code – examples:
DE = Germany If this column is not specified, the value DE is used by default when creating new data. |
yes (if not specified, the value DE is automatically used for new creation) | EN | ISO code | yes | yes |
Region | Region of the main address as ISO code – examples:
BW = Baden Württemberg Only available for Germany, Austria and USA |
no | BW | ISO code | yes | yes |
PBox | P.O. Box of the main address | yes, if a postcode or the city for the P.O. box has been specified | P.O. Box | varchar(20) | yes | yes |
ZIPPBox | Postcode of the P.O. Box of the main address | yes, if a P.O. Box or the location for the P.O. Box has been specified | 70563 | varchar(20) | yes | yes |
CityPBox | Location of the post office box of the main address | yes, if a P.O. box or the postal code for the P.O. box has been specified | Stuttgart | nvarchar(50) | yes | yes |
Culture | Language of the supplier as ISO code: Examples:
de-DE = German If this column is not specified, the user language is taken from the provider. |
yes (if not specified, the user language is taken from the provider). | en-EN | ISO code | yes | yes |
Phone | Phone number | no | +49 711 686875-0 | varchar(50) | yes | yes |
Fax | Fax number | no | +49 711 686875-10 | varchar(50) | yes | yes |
E-mail for general system notifications | yes | info@onventis.de | varchar(50) | yes | yes | |
EmailForFreetextOrder | E-mail address for free text orders | no | info@onventis.de | varchar(50) | yes | yes |
EmailForRequest | E-mail address for calls for tenders | no | info@onventis.de | varchar(50) | yes | yes |
EmailForAuction | E-mail address for auctions | no | info@onventis.de | varchar(50) | yes | yes |
EmailForOrder | E-mail address for catalogue orders | no | info@onventis.de | varchar(50) | yes | yes |
EmailForContact | E-mail address for contact | no | info@onventis.de | varchar(50) | yes | yes |
UserLoginName | Login Name of the main contact person | yes, is required for the initial creation of a supplier (Admin user of the Onventis Supplier Organization) | User0123456 | varchar(50) | yes | no |
UserPassword | Password of the main contact person | yes, is required for the initial creation of a supplier (Admin user of the Onventis Supplier Organization) | Password123! | varchar(50) | yes | no |
UserSalutation | Salutation of the main contact person
1 = Mr |
yes, is required for the initial creation of a supplier (Admin user of the Onventis Supplier Organization) | 1 | tinyint | yes | yes |
UserFirstName | First name of the main contact person | yes, is required for the initial creation of a supplier (Admin user of the Onventis Supplier Organization) | Max | nvarchar(50) | yes | yes |
UserLastName | Last name of the main contact person | yes, is required for the initial creation of a supplier (Admin user of the Onventis Supplier Organization) | Sample | nvarchar(50) | yes | yes |
UserPosition | Position of the main contact person | no | Purchasing Manager | nvarchar(50) | yes | yes |
UserPhone | Phone number of the main contact person | no | +49 711 686875-0 | varchar(50) | yes | yes |
UserFax | Fax number of the main contact person | no | +49 711 686875-10 | varchar(50) | yes | yes |
UserMobilePhone | Mobile phone number of the main contact person | no | +49 173 12345678 | varchar(50) | yes | yes |
UserEmail | E-mail of the main contact person | yes, is required for the initial creation of a supplier (Admin user of the Onventis Supplier Organization) | info@onventis.de | varchar(50) | yes | yes |
SupplierStatusNr | Supplier status to be assigned to the supplier | no | 00001 | varchar(35) | yes | yes |
Categories | Category(ies) to be assigned to the supplier. Several entries are separated from each other with a “|” symbol | no | 00001|00002 | nvarchar(250) | yes | yes |
InternalSupplier | Identification as an internal supplier (intercompany).
0 = Not activated |
no | 0 | tinyint | yes | yes |
SalesTaxID | VAT number of the main address | no | DE12345678 | varchar(35) | yes | yes |
SalesTaxIDCheck | Result of the EU VIES VAT ID validation (only for linked suppliers from the portal)
0 = NA -> (Not applicable, as no EU VAT ID was provided and cannot be checked) |
no | 2 | int | no | yes |
TaxNumber | Tax number | no | 123456 | varchar(35) | yes | yes |
NrAtSupplier | Customer number at the supplier | no | CUS123456 | varchar(35) | yes | yes |
Remark | Comment | no | Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. | ntext | yes | yes |
File(s) | Files (included in the standard system, no document management) | no | Document1.pdf, Document2.zip | file reference (text) | no | yes |
BankName | Name of the bank of the main bank account
Mandatory field if you want to create a main bank account (at least one attribute of the main bank account is filled) |
yes* | Demo Bank Stuttgart | varchar(50) | yes | yes |
BankStreet | Street of the main bank connection | no | Stuttgart Street 1 | varchar(100) | yes | yes |
BankZip | Postcode of the main bank account | no | 70563 | varchar(20) | yes | yes |
BankCity | Location of the main bank account | no | Stuttgart | varchar(50) | yes | yes |
BankCountry | Country of the main bank connection as ISO code – examples:
DE = Germany |
EN | ISO code | yes | yes | |
BankRegion | Region of the main bank connection as ISO code – examples:
BW = Baden Württemberg Only available for Germany, Austria and USA |
no | BW | ISO code | yes | yes |
BankCurrency | Currency of the bank account as ISO code – examples:
EUR = Euro |
no | EUR | ISO code | yes | yes |
IBAN | IBAN of the main bank account
* Mandatory field if no account number is specified |
yes* | DE89370400440532013000 | varchar(35) | yes | yes |
BIC | BIC/SWIFT of the main bank account | no | HASPDEHH | varchar(20) | yes | yes |
BankAccount | Main bank account number
* Mandatory field if no IBAN is given |
yes* | 648489890 | varchar(50) | yes | yes |
BankNumber | Bank code of the main bank | no | 50010517 | varchar(50) | yes | yes |
InvoiceSupplierNr | Linked invoice supplier (SupplierNr of the referenced supplier) | no | ONV000005 | varchar(35) | yes | yes |
PaymentTermsNr | Number of the assigned terms of payment (if managed in Onventis Buyer) | no | 00001 | varchar(35) | yes | yes |
PaymentTerms | Payment term as text (if not managed in Onventis Buyer) | no | 30 days net | nvarchar(100) | yes | yes |
DeliveryTermsCode | Incoterms (number) | no | EXW | nvarchar(50) | yes | yes |
DeliveryTerms | Free house | no | Free house | nvarchar(100) | yes | yes |
DeliveryTermsPlace | Place for delivery term (if Incoterms are used) | no | Reception Building 1 | nvarchar(200) | yes | yes |
PaymentMethodsNr | Number of the assigned payment method | no | 00001 | varchar(35) | yes | yes |
InvoiceVerification | GR-related auditing
0 = not activated |
no | 1 | tinyint | yes | yes |
DoubleInvoiceAudit | Double-checking of accounts
0 = not activated |
no | 1 | tinyint | yes | yes |
Standard | Standard supplier
0 = not activated |
no | 1 | tinyint | yes | yes |
ComplianceChecked | Compliance checked
0 = not activated |
no | 1 | tinyint | yes | yes |
DisabledSAP | Deactivate data communication to ERP
0 = not activated |
no | 1 | tinyint | yes | yes |
OrgUnitInArticleCondition | Use organizational unit and customer data in sales conditions
0 = not activated |
no | 1 | tinyint | yes | yes |
EvaluatedReceipt | Automatic goods receipt settlement
0 = not activated |
no | 1 | tinyint | yes | yes |
ResponsibleUserGroupNo | Responsible user group/purchasing group | no | 00001 | varchar(35) | yes | yes |
ResponsibleUserNr | Responsible user | no | 00001 | varchar(35) | yes | yes |
OrderProcessingType | Type of purchase order processing workflow
1 = Use standardized workflow The vendor can be assigned a uniform workflow that is always used or different workflows that take effect depending on the account assignment category, etc. Important: |
no | 1 | int | yes | yes |
OrderProcessNr | Number of the assigned purchase order processing workflow if “Use uniform workflows” was selected in the type | no | 00001 | varchar(35) | yes | yes |
MultiOrderProcessNr | Number of the assigned purchase order processing workflows. If there are several order processing worklows, the numbers must be separated with the “|” symbol. Example:
Purchase order processing workflows no. 000001, 000006 and 000004 are to be assigned to the vendor. The default is 000004. The column must be filled as follows: 000001|[S]000004|000006 |
no | 000001|[S]000004|000006 | varchar(1000) | yes | yes |
OrderProcessNrByCostAllocType | Assign different workflows per account assignment category:
The entries should be formatted as follows: Example: Formatting: |
no | 000028$A|000029$K | varchar(1000) | yes | yes |
OrderProcessNrByOrgUnit | Assign different workflows per organizational unit:
The entries should be formatted as follows: Example: Formatting: Important: Is now possible via the worksheet OrgUnitSpecific in the column OrderProcessNumber |
no | 000028$000001|000029$000006 | varchar(1000) | yes | yes |
OrderProcessNrByOrgObject | Assign different workflows per organizational object:
The entries should be formatted as follows: Example: Formatting: |
no | 000028$000001|000029$000006 | varchar(1000) | yes | yes |
OrderProcessNrByOrderType | Assign different workflows per order type:
The entries should be formatted as follows: Normal order = 1 Example: Formatting: |
no | 000028$1|000029$3 | varchar(1000) | yes | yes |
Transmission | Order transmission type (bitmask possible):
1 = Email |
no | 1 | int | yes | yes |
TransmissionAttachmentType | Attachments in the order transmission channel e-mail (bitmask possible):
0 = Email with link Bitmask Example: |
no | 5 | int | yes | yes |
OrderRangeFlag | Use vendor-dependent number range for purchase orders
0 = Not activated |
no | 1 | tinyint | yes | yes |
MinOrderValue | Minimum order quantity | no | 10 | decimal(18, 4) | yes | yes |
ERPOrderNr | ERP Import from <Order number> | no | 1234 | varchar(50) | yes | yes |
DeliveryProgram | Product range | no | Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. | ntext | yes | yes |
SapCoAreaNr | Standard SAP controlling area. Enter the number of a controlling area here. |
no | 0001 | varchar(1000) | yes | yes |
SapCompCodes | Standard SAP company code. Enter the number of one or more company codes here. (several entries should be separated by a “|” symbol) |
no | 0001|0002 | varchar(1000) | yes | yes |
SapPurchaseOrgs | SAP Purchasing Organizations. Multiple purchasing organizations can be separated by “|” symbol. |
no | 0001 | varchar(1000) | yes | yes |
SapControlAccountNr | SAP reconciliation account | no | 123465 | varchar(1000) | yes | yes |
SapAccountGroupNr | SAP account group | no | 123456 | varchar(1000) | yes | yes |
AllOrgUnits | Extend supplier for all organizational units
0 = not activated |
no | 0 | tinyint | yes | yes |
OrgUnitExtensions | Organizational units to which the vendor is to be extended | no | STGT|MUN|BER | varchar(1000) | yes | yes |
HtmlAttachmentFlag | Specifies whether or not a supplier should receive HTML attachments to an RFx.
0 = not activated |
no | 0 | tinyint | yes | yes |
ReleasedMaterialGroupsNr | Approved material groups | no | Mat1|Mat2 | varchar(50) | yes | yes |
RejectedMaterialGroupsNr | Rejected mateial groups | no | Mat1|Mat2 | varchar(50) | yes | yes |
MaterialGroupRemark | Comment on the material groups | no | Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. | ntext | yes | yes |
Deleted | Specifies whether a supplier is to be deleted
0 = not activated |
no | 0 | yes | no |
Address
Address | ||||||
Column heading | Description | Mandatory field | Example value | Data type (length) | Import | Export |
SupplierNr | Unique supplier number (NrIntern) of the supplier at organization level to which the optional address refers. | yes | ONV000001 | varchar(35) | yes | yes |
AddressNr | Unique address number within a supplier | yes | 000001 | varchar(35) | yes | yes |
Street | Street of the main address | depending on the configuration of the organizational settings within the Onventis Buyer organization | Gropiusplatz 10 | nvarchar(100) | yes | yes |
Street2 | Street 2 of the main address | no | STEP Area | nvarchar(100) | yes | yes |
Building | main address building | no | House 1 | nvarchar(50) | yes | yes |
Floor | Floor of the main address | no | 5 | nvarchar(50) | yes | yes |
Room | Room of the main address | no | 05 Oct | nvarchar(50) | yes | yes |
ZIPCity | Postcode of the main address | yes | 70563 | varchar(20) | yes | yes |
City | Place of the main address | yes | Stuttgart | nvarchar(50) | yes | yes |
Country | Country of the main address as ISO code – examples:
DE = Germany If this column is not specified, the value DE is used by default when creating new data. |
yes (if not specified, the value DE is automatically used for new creation) | EN | ISO code | yes | yes |
Region | Region of the main address as ISO code – examples:
BW = Baden Württemberg Only available for Germany, Austria and USA |
no | BW | ISO code | yes | yes |
PBox | P.O. Box of the main address | no | P.O. Box | varchar(20) | yes | yes |
ZIPPBox | Postcode of the P.O. Box of the main address | no | 70563 | varchar(20) | yes | yes |
CityPBox | Location of the post office box of the main address | no | Stuttgart | nvarchar(50) | yes | yes |
NrAtSupplier | Customer number at the supplier | no | CUS123456 | varchar(35) | yes | yes |
SalesTaxID | VAT number of the main address | no | DE12345678 | varchar(35) | yes | yes |
SalesTaxIDCheck | Result of the EU VIES VAT ID validation (only for linked suppliers from the portal)
0 = NA -> (Not applicable, as no EU VAT ID was provided and cannot be checked) |
no | 2 | int | no | yes |
Phone | Phone number | no | +49 711 686875-0 | varchar(50) | yes | yes |
Fax | Fax number | no | +49 711 686875-10 | varchar(50) | yes | yes |
E-mail for general system notifications | yes | info@onventis.de | varchar(50) | yes | yes |
Bank
Bank | ||||||
Column heading | Description | Mandatory field | Example value | Data type (length) | Import | Export |
SupplierNr | Unique supplier number (NrIntern) of the supplier at organization level to which the optional bank details refer. | yes | ONV000001 | varchar(35) | yes | yes |
BankNr | Unique number for the optional bank details within a supplier | yes | 000001 | varchar(35) | yes | yes |
Name | Bank name | yes | Demo Bank Stuttgart | varchar(50) | yes | yes |
Street | Street of the optional bank account | no | Stuttgart Street 1 | varchar(100) | yes | yes |
ZIPCity | Postcode of the optional bank account | no | 70563 | varchar(20) | yes | yes |
City | Location of the optional bank account | no | Stuttgart | varchar(50) | yes | yes |
Country | Country of the optional bank details as ISO code – examples:
DE = Germany |
EN | ISO code | yes | yes | |
Region | Region of optional bank details as ISO code – examples:
BW = Baden Württemberg Only available for Germany, Austria and USA |
no | BW | ISO code | yes | yes |
Currency | Currency of the bank account as ISO code – examples:
EUR = Euro |
no | EUR | ISO code | yes | yes |
Account | Account number of the optional bank account
* Mandatory field if no IBAN is given |
yes* | 648489890 | varchar(50) | yes | yes |
Number | Bank code/Bank number of the optional bank account | no | 50010517 | varchar(50) | yes | yes |
IBAN | IBAN of the optional bank account
* Mandatory field if no account number is specified |
yes* | DE89370400440532013000 | varchar(35) | yes | yes |
BIC | BIC/SWIFT of the optional bank details | no | HASPDEHH | varchar(20) | yes | yes |
Contact
Contact | ||||||
Column heading | Description | Mandatory field | Example value | Data type (length) | Import | Export |
SupplierNr | Unique supplier number (NrIntern) of the supplier on organization level to which the optional contact refers. | yes | ONV000001 | varchar(35) | yes | yes |
ContactNr | Unique number for optional contact within a supplier | yes | 000001 | varchar(35) | yes | yes |
Salutation | Salutation of the optional contact person
1 = Mr |
no | 1 | tinyint | yes | yes |
FirstName | First name of the optional contact person | no | Max | nvarchar(50) | yes | yes |
LastName | Last name of the optional contact person | yes | Sample | nvarchar(50) | yes | yes |
Position | Position of the optional contact person | no | Purchasing | nvarchar(50) | yes | yes |
Department | Department of the optional contact person | no | Purchasing | tbd | yes | yes |
Phone | Phone number of the optional contact person | no | +49 711 686875-0 | varchar(50) | yes | yes |
Fax | Fax number of the optional contact person | no | +49 711 686875-10 | varchar(50) | yes | yes |
MobilePhone | Mobile phone number of the optional contact person | no | +49 173 12345678 | varchar(50) | yes | yes |
E-mail of the optional contact person | no | info@onventis.de | varchar(50) | yes | yes | |
Remark | Comment | no | Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. | ntext | yes | yes |
Standard | Standard contact
0 = not activated |
no | 1 | tinyint | yes | yes |
OrgUnitSpecific
OrgUnitSpecific | ||||||
Column heading | Description | Mandatory field | Example value | Data type (length) | Import | Export |
SupplierNo | Unique vendor number of the vendor to which the OrgUnit extension refers. | yes | ONV000001 | varchar(35) | yes | yes |
OrgUnitNo | OrgUnit number to which the OrgUnit extension refers to. | yes | ONV000001 | varchar(35) | yes | yes |
QualificationStatus | Title of the supplier Qualification status at the OrgUnit level
0 = Not yet qualified |
no | Successful | translation string | no | yes |
NoInternal | Unique vendor number of a vendor within an OrgUnit extension | no | EXT000001 | varchar(35) | yes | yes |
NoExternal | External vendor number of a vendor within an OrgUnit extension | no | EXT000001 | varchar(35) | yes | yes |
NoAdditional | Additional number(s) | no | ADD000001 | varchar(35) | yes | yes |
E-mail for general system notifications | no | info@onventis.de | varchar(50) | yes | yes | |
EmailForFreetextOrder | E-mail address for free text orders | no | info@onventis.de | varchar(50) | yes | yes |
EmailForRequest | E-mail address for calls for tenders | no | info@onventis.de | varchar(50) | yes | yes |
EmailForAuction | E-mail address for auctions | no | info@onventis.de | varchar(50) | yes | yes |
EmailForOrder | E-mail address for catalogue orders | no | info@onventis.de | varchar(50) | yes | yes |
EmailForContact | E-mail address for contact | no | info@onventis.de | varchar(50) | yes | yes |
SupplierStatusNo | Supplier status which should be assigned to the supplier on this OrgUnit. | no | 00001 | varchar(35) | yes | yes |
PaymentTermsNo | Number of the assigned terms of payment (if managed in Onventis Buyer) | no | 00001 | varchar(35) | yes | yes |
PaymentTerms | Payment term as text (if not managed in Onventis Buyer) | no | 30 days net | nvarchar(100) | yes | yes |
DeliveryTermsCode | Incoterms (number) | no | EXW | nvarchar(50) | yes | yes |
DeliveryTerms | Free house | no | Free house | nvarchar(100) | yes | yes |
DeliveryTermsPlace | Place for delivery term (if Incoterms are used) | no | Reception Building 1 | nvarchar(200) | yes | yes |
PaymentMethodsNo | Number of the assigned payment method | no | 00001 | varchar(35) | yes | yes |
ResponsibleUserGroupNo | Responsible user group/purchasing group | no | 00001 | varchar(35) | yes | yes |
ResponsibleUserNo | Responsible user | no | 00001 | varchar(35) | yes | yes |
OrderProcessingType | Type of purchase order processing workflow
1 = Use standardized workflow The vendor can be assigned a uniform workflow that is always used or different workflows that take effect depending on the account assignment category, etc. Important: |
no | 1 | int | yes | yes |
OrderProcessNo | Number of the assigned purchase order processing workflow if “Use uniform workflows” was selected in the type | no | 00001 | varchar(35) | yes | yes |
MultiOrderProcessNo | Number of the assigned purchase order processing workflows. If there are several order processing worklows, the numbers must be separated with the “|” symbol. Example:
Purchase order processing workflows no. 000001, 000006 and 000004 are to be assigned to the vendor. The default is 000004. The column must be filled as follows: 000001|[S]000004|000006 |
no | 000001|[S]000004|000006 | varchar(1000) | yes | yes |
OrderProcessNrByOrderType | Assign different workflows per order type:
The entries should be formatted as follows: Normal order = 1 Example: Formatting: |
no | 000028$1|000029$3 | varchar(1000) | yes | yes |
OrderProcessNrByCostAllocType | Assign different workflows per account assignment category:
The entries should be formatted as follows: Example: Formatting: |
no | 000028$A|000029$K | varchar(1000) | yes | yes |
AddressNo | Assigned address from the address directory | no | 00001 | varchar(35) | yes | yes |
SupplierNo | Assigned bank details from the bank details list | no | 00001 | varchar(35) | yes | yes |
SupplierNo | Assigned contact from the contact directory | no | 00001 | varchar(35) | yes | yes |
Categories | Category(ies) to be assigned to the supplier. Several entries are separated from each other with a “|” symbol | no | 00001|00002 | nvarchar(250) | yes | yes |
ReleasedMaterialGroupsNo | Approved material groups | no | Mat1|Mat2 | varchar(50) | yes | yes |
RejectedMaterialGroupsNo | Rejected mateial groups | no | Mat1|Mat2 | varchar(50) | yes | yes |
MaterialGroupRemark | Comment on the material groups | no | Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. | ntext | yes | yes |
SapCompCodeSettings
<table>
SapPurchaseOrgSettings
<table>