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
10 = Running
20 = Failed
30 = Successful

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

Email

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
3 = Assign different workflows
4 = Use account assignment category-specific workflow
6 = Different workflows per order type

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:
The setting of organizational unit-specific order processing processes is now possible via the worksheet OrgUnitSpecific in the column OrderProcessNr and the setting no. 2 here is therefore obsolete.

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:
Purchase order processing workflow number$Order type abbreviation

Normal order = 1
Service order = 2
Frame order = 3

Example:
Workflow no. 000028 should apply to normal orders
Workflow no. 000029 should apply to blanket orders

Formatting:
000028$1|000029$3

no

000028$1|000029$3

varchar(1000)

yes

yes

OrderProcessNrByCostAllocType

Assign different workflows per account assignment category:

The entries should be formatted as follows:
Purchase order processing workflow number$Account assignment type abbreviation

Example:
Workflow no. 000028 is to apply to purchase orders with account assignment category A.
Workflow no. 000029 is to apply to purchase orders with account assignment category K.

Formatting:
000028$A|000029$K

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