Chapter 5
Setting Up Business Rules
This chapter describes the BuyerXpert/SellerXpert business rules and how to use them. It explains what a rule is and how to modify the rules to configure your SellerXpert implementation.
|
Note
|
The information in this chapter is based on the assumption that you have already read Concepts and Release Notes.
|
This chapter contains the following sections:
About Business Rules
Business rules are configurable, generalized statements that control the flow and behavior of BuyerXpert/SellerXpert. Business rules determine privileges, acceptable processes, relationships between BuyerXpert/SellerXpert participants, and defaults. The business rules semantics are not as complex as a full programming language, so you do not need to have programming experience to perform typical configurations.
To illustrate how a rule works, the following example rule instance, named LINE_DISCOUNT, is referred to in this section:
Buyer==AOL & Seller==Sun & Product==Computers => Line Discount=10%
This example rule is made up of a number of elements that state if the buyer organization is AOL, the seller is Sun, and the product is computers, BuyerXpert/SellerXpert will apply a 10% line discount to an order.
Rule Elements
A business rule consists of the following elements:
Rule Name
A rule name identifies a rule, for example LINE_DISCOUNT.
Applicability Condition
The applicability condition specifies when to apply a rule. An applicability condition is actually a set of equality constraints over a set of roles that are evaluated during conflict resolution.
Example
Buyer==AOL & Seller==Sun & Product==Computers
If the buyer organization is AOL and the seller is Sun and the product is Computers, the rule is applicable. All applicability conditions have this form.
Business Roles
Business roles are part of an applicability condition and identify the valid roles for a rule. In the preceding example, the business roles are Buyer, Seller, and Product.
Specified Value
Each rule has a specified value, which in its simplest form is a constant value.
Line Discount==10%
The specified value is a line discount of 10%.
Sometimes you may need to specify a value by using a variable to reference another value.
Receiving Location==Ship to Location
The specified value is equal to the ship to location value.
Conflict Resolution Strategies
BuyerXpert/SellerXpert provides conflict resolution strategies to resolves conflicts when multiple rules are applicable for a given situation. There are four conflict resolution strategies:
Role Ordering Resolution
In role ordering resolution, BuyerXpert/SellerXpert resolves conflicts between applicable rules to the first role. If there are multiple rules with identical values for the first role, BuyerXpert/SellerXpert uses the second role to resolve the conflict, and so forth.
For example:
Buyer==AOL & Product==All => Discount=5%
Buyer==AOL & Product==Computers => Discount=10%
In this example, if an AOL buyer wants to purchase a computer, both rules apply. The first role (buyer) is identical for both rules, so BuyerXpert/SellerXpert uses the second role (product) to resolve the conflict between the rules. The discount applied is 10%.
Inheritance Resolution
For inheritance resolution of parent-child conflicts, BuyerXpert/SellerXpert evaluates the rules from more specific to less specific and applies the inheritance resolution strategy associated with each rule instance.
For example:
Buyer==AOL & Resolution==Union => Discount=1
Buyer==Netscape & Resolution==PreferSpecific => Discount=2
Buyer==APD & Resolution==Union => Discount=3
In this example, APD is the most specific rule in the hierarchy, so BuyerXpert/SellerXpert evaluates it first. Its resolution strategy is union, so BuyerXpert/SellerXpert considers the next applicable rule in the hierarchy. The Netscape rule specifies that its value (PreferSpecific) should be used in place of any previous values, so the final rule for AOL is not considered. The discount applied is the set [3,2].
DAG Resolution
If the inheritance tree for a role is actually a Directed Acyclic Graph (DAG), there is no clear ordering specified for sibling rules. In this example, BuyerXpert/SellerXpert evaluates each rule globally with all instances of the rule.
For example:
Product==Computers => Discount=5%
Product==DomesticItems & Resolution==MostRecent => Discount=10%
In this example the buyer wants to purchase a domestic computer and both rules have the same applicability condition. The second rule includes the conflict resolution value MostRecent, so BuyerXpert/SellerXpert uses this value to select the second rule. The discount applied is 10%.
Duplicate Resolution
If there are multiple rules with identical applicability conditions, BuyerXpert/SellerXpert evaluates the duplicate resolution strategy associated with each rule globally.
For example:
Product==Computers & Buyer==AOL & Resolution==Highest=> Discount=10%
Product==Computers & Buyer==APD & Resolution==Highest=> Discount=5%
In this example, the applicability conditions for the rules are identical, so there are duplicate values for discount which cannot be decided on the basis of the applicability conditions alone. BuyerXpert/SellerXpert evaluates the resolution values select the first rule. The discount applied is 10%.
When there are conflicts between rules, BuyerXpert/SellerXpert determines which rule prevails by applying the conflict resolution strategies listed in Table 5-1.
Table 5-1 Conflict Resolution Strategies
|
Rule Conflict
|
Resolution Strategy
|
BuyerXpert/SellerXpert Action
|
|
Conflict with different roles
|
Role ordering resolution
|
Conflicts between applicable rules resolve to the first role. For multiple rules with identical roles for the first role, resolves to the second role, and so forth.
|
|
Parent-child conflict
|
Inheritance resolution
|
Starts with most specific rule and applies the inheritance resolution strategy associated with each rule.
|
|
Sibling conflict
|
DAG Resolution
|
Globally applies Directed Acyclic Graph (DAG) resolution strategy associated with each rule.
|
|
Multiple rules with identical applicability conditions
|
Duplicate resolution
|
Globally applies the duplicate resolution strategy associated with each rule.
|
Conflict Resolution Values
Each business rule has conflict resolution values that indicate how BuyerXpert/SellerXpert resolves situations when multiple rules are applicable for a given situation. There are six conflict resolution values: HIGHEST, LOWEST, PREFER_SPECIFIC, MOST_RECENT, UNION, and INTERSECTION.
For example:
Buyer==AOL & Resolution==Union ==> Discount=5%
In this example, the conflict resolution value is union.
Table 5-2 explains the conflict resolution values and provides examples of each.
Table 5-2 Conflict Resolution Values
|
Conflict Resolution Value
|
SellerXpert Action
|
Example
|
Result
|
|
HIGHEST
|
Selects the rule with the highest value.
|
Rule1: line discount = 3%
Rule2: line discount = 5%
Rule3: line discount = 10%
|
SellerXpert selects line discount = 10% because it is the highest value.
|
|
LOWEST
|
Selects the rule with the lowest value.
|
Rule1: line discount = 3%
Rule2: line discount = 5%
|
SellerXpert selects line discount = 3% because it is the lowest value.
|
|
PREFER_SPECIFIC
|
Selects the rule with the most specific value in a hierarchy.
|
Rule1: currency = USD for organization
Rule2: currency = EURO for current user
|
SellerXpert selects currency = EURO for the most specific value in the hierarchy (current user).
|
|
MOST_RECENT
|
Selects the rule with the most recent value.
|
Rule1: currency = USD for organization is set 11/10/00.
Rule2: currency = EURO for current user is set 11/15/00.
|
SellerXpert selects currency = EURO because it is the most recently updated value.
|
|
UNION
|
Selects the combination of the values.
|
Rule1: credit card = [visa]
Rule2: credit card = [amex]
|
SellerXpert selects credit card = [visa;amex].
|
|
INTERSECTION
|
Selects the intersection of the values.
|
Rule1: credit card = [visa;amex]
Rule2: credit card = [visa;mc]
|
SellerXpert selects credit card = visa. If there are no common elements, returns NULL.
|
Administrator's Rules Tasks
A full set of business rules is supplied with BuyerXpert/SellerXpert. If the supplied configurations work for the business model of your company, you can use the rules as they stand, but this is unlikely. Your job as administrator is to configure the BuyerXpert/SellerXpert business rules to support the particular business practices of your organization.
Usually sample data is loaded into BuyerXpert/SellerXpert during implementation, which provides you with a set of business rules data to modify for your organization. After you have gathered your organization-specific data and set up your resources, you are ready to set up your rules.
Table 5-3 contains a list of business rule tasks. The right-hand column provides information about where to find instructions, guidelines, or tools for performing that task.
All the rules tables are contained in Table 5-5 through Table 5-39.
Modifying Rules
BuyerXpert/SellerXpert provides two methods for modifying rules:
Modifying Rules Using the Admin Interface
The BuyerXpert/SellerXpert Admin interface allows you to modify individual rules.
|
Note
|
There are dependencies between rules. For example, a user that has organization privileges may also be granted other privileges.
|
Rules created at the organization level can be administered by the orgadmin. Some rules define user preferences (preferred language, display currency) and can be administered by a self admin.
Follow these guidelines to modify a business rule using the Admin interface (field and procedure details are contained in Help):
Select the area you want, such as Pricing.
Select the type of rule you want to add or edit, such as Tax Rules.
Select Line Item.
Select the particular rule you want to add or edit.
-
For example, select GROUP_FREIGHT_TAX_RULE.
Follow procedures in Help to complete the task.
Modifying Rules Using the Import Utility
Like other resources, rules can also be updated using the Import utility. If the Import utility is used, you must explicitly specify which organization the resource belongs to. In the case of user preferences, you must also specify if the resource is owned by a particular user.
Instructions for creating an import data file and using the Import utility are contained in Chapter 8 "Importing Data."
BuyerXpert/SellerXpert Rules List
Table 5-4 lists the BuyerXpert/SellerXpert business rules alphabetically by category and includes the following information:
Category—Business rule category
Rule Name—Business rule name used in the import utility (not the rule name used in the graphical administrative interface).
Value Type—Allowable values are boolean, integer, string, and NTV. NTVs store name, type, and value data and are generally used for setting and obtaining values.
NTV Value Details—Lists detail values for NTV value types.
Table 5-4 BuyerXpert/SellerXpert Rules Listed by Category (1 of 6)
|
Rule Category
|
Rule Name
|
Value Type
|
NTV Value Details
|
|
Accounting Code Rules
|
|
|
ACCNT_CODE_EXTAPI_SERVER
|
String
|
|
|
|
ACCNT_CODE_MODEL
|
String
|
|
|
Additional Information Rules
|
|
|
LINE_ITEM_ADDITION_INFO_STRUCT
|
String
|
|
|
Approval Rules
|
|
|
APPROVAL_LIMIT
|
NTV
|
APPROVAL_LIMIT_CURRENCY
|
|
|
APP_MATRIX_TYPES
|
String
|
|
|
|
CAN_DELETE_APPROVER
|
Boolean
|
|
|
|
CAN_ESCALATE_APPROVER
|
Boolean
|
|
|
|
CAN_RECEIVE_EMAIL_NOTIFICATION
|
Boolean
|
|
|
|
ESCALATION_MODEL
|
String
|
|
|
|
PURCHASE_APPROVAL_PROCESS_
DEFAULT
|
String
|
|
|
|
REMINDER
|
NTV
|
REMINDER_LIMIT
|
|
Commodity Code Rules
|
|
|
COMMODITY_CODE_MODEL
|
String
|
|
|
|
COMMODITY_CODE_EXTAPI_SERVER
|
String
|
|
|
|
COMMODITY_CODE_MAP_MODEL
|
String
|
|
|
|
COMMODITY_CODE_MAP_EXTAPI_SERVER
|
String
|
|
|
Company Rules
|
|
|
SELLER_COMPANIES
|
String
|
|
|
|
BUYER_COMPANIES
|
String
|
|
|
|
SHIPPER_COMPANIES
|
String
|
|
|
Contract Rules
|
|
|
CONTRACT_DEFAULT
|
String
|
|
|
|
CONTRACT_LIST
|
String
|
|
|
|
CONTRACT_ADMIN
|
String
|
|
|
Currency Rules
|
|
|
COMMON_CURRENCY
|
String
|
|
|
|
CURRENCY_CONVERSION_TABLE
|
String
|
|
|
|
CURRENCY_RATE_FREEZE_MODEL
|
String
|
|
|
|
DISPLAY_CURRENCY_DEFAULT
|
String
|
|
|
|
DISPLAY_CURRENCY_LIST
|
String
|
|
|
|
DISPLAY_CURRENCY_PRECISION
|
Integer
|
|
|
Discount Charge Rules
|
|
|
GROUP_ADJUSTMENTS
|
String
|
|
|
|
LINE_ADJUSTMENTS
|
String
|
|
|
|
MAX_ADJ_LIMIT
|
NTV
|
MAX_LINE_DISCOUNT;
MAX_LINE_MARKUP
|
|
Invoice Matching Rules
|
|
|
INVOICE_MATCHING_ALGORITHM
|
String
|
|
|
|
ALLOWED_TO_PAY_INVOICE
|
Boolean
|
|
|
|
PAYMENT_VOUCHER_CURRENCY
|
Integer
|
|
|
|
INVOICING_USER
|
String
|
|
|
Locale Rule
|
|
|
PREFERRED_LOCALE
|
String
|
|
|
Location Rules
|
|
|
BILLTO_LOCATION_DEFAULT
|
String
|
|
|
|
BILLTO_LOCATION_LIST
|
String
|
|
|
|
CONTACT_BILLTO_DEFAULT
|
String
|
|
|
|
CONTACT_BILLTO_LIST
|
String
|
|
|
|
CONTACT_PAYTO_DEFAULT
|
String
|
|
|
|
CONTACT_PAYTO_LIST
|
String
|
|
|
|
CONTACT_SENDTO_DEFAULT
|
String
|
|
|
|
CONTACT_SENDTO_LIST
|
String
|
|
|
|
CONTACT_SHIPFROM_DEFAULT
|
String
|
|
|
|
CONTACT_SHIPFROM_LIST
|
String
|
|
|
|
CONTACT_SHIPTO_DEFAULT
|
String
|
|
|
|
CONTACT_SHIPTO_LIST
|
String
|
|
|
|
PAYTO_LOCATION_DEFAULT
|
String
|
|
|
|
PAYTO_LOCATION_LIST
|
String
|
|
|
|
SEND_TO_LOCATION_DEFAULT
|
String
|
|
|
|
SEND_TO_LOCATION_LIST
|
String
|
|
|
|
SHIPFROM_LOCATION_DEFAULT
|
String
|
|
|
|
SHIPFROM_LOCATION_LIST
|
String
|
|
|
|
SHIPTO_LOCATION_DEFAULT
|
String
|
|
|
|
SHIPTO_LOCATION_LIST
|
String
|
|
|
Order Entry Rules
|
|
|
LG_NUMBER
|
NTV
|
PREFIX; SEQUENCE_NAME;
SUFFIX
|
|
|
REQUISITION_GLOBAL_TEMPLATES
|
String
|
|
|
|
ORDER_GLOBAL_TEMPLATES
|
String
|
|
|
Payment Rules
|
|
|
PAYMENT_SUBTYPE_DEFAULT
|
NTV
|
MAX;MIN;METHOD
|
|
|
PAYMENT_SUBTYPE_LIST
|
NTV
|
MAX;MIN;METHOD
|
|
|
PAYMENT_TERMS_DEFAULT
|
String
|
|
|
|
PAYMENT_TERMS_LIST
|
String
|
|
|
|
CAN_OVERRIDE_PRICE
|
Boolean
|
|
|
|
PAYMENT_PROCESSING_METHOD
|
String
|
|
|
Pricing Rules
|
|
|
PRICE_ADDITIONAL_PRECISION
|
Integer
|
|
|
|
PRICE_ADJUSTMENTS
|
String
|
|
|
|
PRICELIST
|
NTV
|
PRICELIST;
PRICELIST_DEFAULT_COLUMN;
PRICE_COLUMN_LOWEST_CHOICE;
PRICE_COLUMN_LOOKUP
|
|
|
PRICELIST_DISCOUNT_MARKUP
|
String
|
|
|
|
PRICING_MODEL
|
String
|
|
|
|
CAN_OVERRIDE_PRICE
|
Boolean
|
|
|
|
PRICING_EXTAPI_SETTINGS
|
String
|
|
|
Quality Entry Rule
|
|
|
QUALITY_ENTRY_FORM
|
String
|
|
|
Receiving Rules
|
|
|
RECEIVING_TOLERANCE
|
NTV
|
OVER_WARNING_PERCENT;
UNDER_RECEIVE_PERCENT
|
|
|
RECEIVING_TOLERANCE_PRECISION
|
Integer
|
|
|
|
CAN_RECEIVE
|
Boolean
|
|
|
Reports Rules
|
|
|
CAN_VIEW_ADMIN_REPORTS
|
Boolean
|
|
|
|
CAN_VIEW_MANAGER_REPORTS
|
Boolean
|
|
|
|
CAN_VIEW_SUPERADMIN_REPORTS
|
Boolean
|
|
|
|
CAN_VIEW_USER_REPORTS
|
Boolean
|
|
|
Sales Quote Rules
|
|
|
SALES_QUOTE_TC
|
String
|
|
|
|
SALES_QUOTE_VALID_DAYS
|
Integer
|
|
|
Security Rules
|
|
|
ALLOW_PASSWORD_LOGIN
|
Boolean
|
|
|
|
CAN_SET_OWNER
|
Boolean
|
|
|
Shipping Rules
|
|
|
FREIGHT_TERM_DEFAULT
|
String
|
|
|
|
FREIGHT_TERM_LIST
|
String
|
|
|
|
GROUP_LEVEL_SHIPPING_CHARGE
|
String
|
|
|
|
LINE_LEVEL_SHIPPING_CHARGE
|
String
|
|
|
|
SHIPPING_METHOD_DEFAULT
|
String
|
|
|
|
SHIPPING_METHOD_LIST
|
String
|
|
|
Tax Rules
|
|
|
CUSTOMER_TAXABILITY
|
NTV
|
CUSTOMER_TAX_CERTIFICATE_ID
|
|
|
GROUP_DCAP_TAX_TABLE
|
String
|
|
|
|
GROUP_FREIGHT_TAX_TABLE
|
String
|
|
|
|
LINE_DCAP_TAX_TABLE
|
NTV
|
LINE_FREIGHT_TAX_TABLE;
PRODUCT_TAXABILITY;
TAX_MODEL;
TAX_TABLE
|
|
|
TAX_CODE
|
String
|
|
|
Timecard Rules
|
|
|
CAN_CREATE_TIMECARD
|
Boolean
|
|
|
|
TIMECARD_APPROVAL_PROCESS_DEFAULT
|
String
|
|
|
Transmission Rules
|
|
|
XMIT_DOCUMENT
|
NTV
|
ORDER_CHANGE
|
|
|
XMIT_RECEIVER
|
NTV
|
ORDER_CHANGE
|
|
|
XMIT_SENDER
|
NTV
|
ORDER_CHANGE
|
|
|
XMIT_CURRENCY
|
String
|
|
|
|
OBI_COMPLIANT
|
Boolean
|
|
|
|
AUTO_SUBMIT
|
Boolean
|
|
|
UDF Rule
|
|
|
UDF_DEFAULT_VALUE
|
String
|
|
|
Unit Conversion Rules
|
|
|
QUANTITY_CONVERSION_TABLE
|
String
|
|
|
|
QUANTITY_PRECISION
|
Integer
|
|
|
|
WEIGHT_CONVERSION_TABLE
|
String
|
|
|
|
WEIGHT_PRECISION
|
Integer
|
|
*Accounting Code Rules
Select Accounting Code Rules to access the accounting code rules from the BuyerXpert graphical administrative interface.
The accounting code rules are:
Accounting Code Model (ACCNT_CODE_MODEL) — Specifies the accounting code model.
Accounting Code External API Server (ACCNT_CODE_EXTAPI_SERVER) — Specifies the accounting code external API server.
*Accounting Code Rules Conflict Resolution
Table 5-5 describes how BuyerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-5 Accounting Code Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
ACCNT_CODE_MODEL
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
ACCNT_CODE_EXTAPI_
SERVER
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
UDF_DEFAULT_VALUE
|
String
|
USER_CREATED_FOR;
UDF
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Additional Information Rule
Select Order Processing> Line Item Additional Information to access the AIF rule from the BuyerXpert/SellerXpert graphical administrative interface.
The additional information field (AIF) rule is:
Line Item Additional Info (LINE_ITEM_ADDITION_INFO_STRUCT) — Indicates that you can add additional information to a line item.
Additional Information Rule Conflict Resolution
Table 5-1 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-6 Additional Information Rule
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
LINE_ITEM_ADDITION_
INFO_STRUCT
|
String
|
SELLER_COMPANY;
PRODUCT;
USER_CREATED_FOR
|
UNION
|
UNION
|
UNION
|
*Approval Rules
Select Approvals>Approval Rules to access the approval rules from the BuyerXpert graphical administrative interface.
The approval rules are:
Approval Limit (APPROVAL_LIMIT) — Specifies approval limits. This rule contains the following NTV value:
APPROVAL_LIMIT_CURRENCY — Defines approved currency limit.
Approval Matrix Types (APP_MATRIX_TYPES) — Lists the approval matrix types.
Can Delete Approver (CAN_DELETE_APPROVER) — Provides permission to delete an approver.
Can Escalate Approver (CAN_ESCALATE_APPROVER) — Indicates that you can escalate an approver.
Can Receive Email Notification (CAN_RECEIVE_EMAIL_NOTIFICATION) — Indicates that you can receive email notification.
Escalation Model (ESCALATION_MODEL) — Describes how to escalate order approvals.
Default Purchase Approval Process (PURCHASE__APPROVAL_PROCESS_DEFAULT) — Defines the default purchase approval process.
Reminder (REMINDER) — Specifies reminder interval in minutes. This rule contains the following NTV value:
REMINDER__LIMIT — Specifies reminder limit.
*Approval Rules Conflict Resolution
Table 5-7 describes how BuyerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-7 Approval Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
APPROVAL_LIMIT
|
NTV
|
APPROVER
|
PREFER_SPECIFIC
|
LOWEST
|
LOWEST
|
|
APP_MATRIX_TYPES
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
UNION
|
|
CAN_DELETE_APPROVER
|
Boolean
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CAN_ESCALATE_
APPROVER
|
Boolean
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CAN_RECEIVE_EMAIL_
NOTIFICATION
|
Boolean
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
ESCALATION_MODEL
|
String
|
USER_CREATED_FOR;
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
PURCHASE_APPROVAL_
PROCESS_DEFAULT
|
String
|
USER_CREATED_FOR;
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
REMINDER
|
NTV
|
APPROVER
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
*Commodity Code Rules
Select Commodity Code Rules to access the commodity code rules from the BuyerXpert graphical administrative interface.
The commodity code rules are:
Commodity Code Model (COMMODITY_CODE_MODEL) — Specifies the commodity code model.
Commodity Code External API Server (COMMODITY_CODE_EXTAPI_SERVER) — Specifies the commodity code external API server.
Commodity Code Mapping Model (COMMODITY_CODE_EXTAPI_SERVER) — Specifies the commodity code mapping model.
Commodity Code Mapping External API Server (COMMODITY_CODE_MAP_EXTAPI_SERVER) — Specifies the commodity code external API server.
*Commodity Code Rules Conflict Resolution
Table 5-8 describes how BuyerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-8 Commodity Code Rules
|
Rule
Name
|
Value Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
COMMODITY_CODE_
MODEL
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
COMMODITY_CODE_
EXTAPI_SERVER
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
COMMODITY_CODE
MAP_MODEL
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
COMMODITY_CODE_
MAP_EXTAPI_SERVER
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Company Rule
Select Rules for Companies to access the company rule from the BuyerXpert/SellerXpert graphical administrative interface.
The company rule is:
Seller Company (SELLER_COMPANIES) — Indicates the seller company.
Company Rule Conflict Resolution
Table 5-9 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-9 Company Rules Conflict Resolution
|
Rule
Name
|
Value Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
SELLER_COMPANIES
|
String
|
USER_CREATED_FOR
|
UNION
|
UNION
|
UNION
|
*Contract Rules
Select Contracts>Contract Rules to access the contract rules from the BuyerXpert graphical administrative interface.
The contract rules are:
Default Contract (CONTRACT_DEFAULT) — Defines the default contract.
Contract List (CONTRACT_LIST) — Specifies the contract list.
Contract Admin (CONTRACT_ADMIN) — Specifies the contract administrator.
Contract Rules Conflict Resolution
Table 5-10 describes how BuyerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-10 Contract Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
CONTRACT_DEFAULT
|
String
|
PRODUCT;
SELLER_COMPANY;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
UNION
|
UNION
|
|
CONTRACT_LIST
|
String
|
PRODUCT;
SELLER_COMPANY;
USER_CREATED_FOR
|
UNION
|
UNION
|
UNION
|
|
CONTRACT_ADMIN
|
String
|
PRODUCT;
SELLER_COMPANY;
USER_CURRENT
|
PREFER_SPECIFIC
|
UNION
|
UNION
|
Currency Rules
Select Order Processing>Currency Rules to access the currency conversion rules from the BuyerXpert/SellerXpert graphical administrative interface.
The currency conversion rules are:
Common Currency (COMMON_CURRENCY) — Describes the common currency to use for an order.
Currency Conversion Table (CURRENCY_CONVERSION_TABLE) — Describes the currency conversion table.
Currency Rate Freeze Model (CURRENCY_RATE_FREEZE_MODEL) — Defines the currency freeze rate.
Default Display Currency (DEFAULT_DISPLAY_CURRENCY) — Defines the default display currency.
Display Currency List (DISPLAY_CURRENCY_LIST) — Defines the display currency list.
Display Currency Precision (DISPLAY_CURRENCY_PRECISION) — Defines the display currency precision.
Currency Rules Conflict Resolution
Table 5-11 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-11 Currency Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
COMMON_CURRENCY
|
String
|
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CURRENCY_CONVERSION_
TABLE
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY
|
PREFER_SPECIFIC
|
LOWEST
|
LOWEST
|
|
CURRENCY_RATE_FREEZE_
MODEL
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
DISPLAY_CURRENCY_
DEFAULT
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
HIGHEST
|
HIGHEST
|
|
DISPLAY_CURRENCY_
LIST
|
String
|
USER_CURRENT
|
UNION
|
UNION
|
UNION
|
|
DISPLAY_CURRENCY_
PRECISION
|
Integer
|
USER_CURRENT;
CURRENCY_UNIT
|
PREFER_SPECIFIC
|
HIGHEST
|
HIGHEST
|
Discount Charge Rules
Select Pricing>Shipping Rules to access the discount charge rules from the BuyerXpert/SellerXpert graphical administrative interface.
The discount adjustments rules are:
Group Adjustment (GROUP_ADJUSTMENTS) — Specifies group discount charges.
Line Adjustment (LINE_ADJUSTMENTS) — Specifies line item discounts.
Maximum Adjustment Limit — Specifies the maximum adjustment level. This rule contains the following NTV value:
MAX_LINE_MARKUP — Specifies maximum line item markup.
Discount Charge Rules Conflict Resolution
Table 5-12 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-12 Discount Charge Rule Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
GROUP_ADJUSTMENTS
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT;
PRICELIST;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY;
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
SHIP_FROM_LOCATION;
SHIP_TO_LOCATION
|
UNION
|
UNION
|
UNION
|
|
LINE_ADJUSTMENTS
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT;
PRICELIST;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY;
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
SHIP_FROM_LOCATION;
SHIP_TO_LOCATION
|
UNION
|
UNION
|
UNION
|
|
MAX_ADJ_LIMIT
|
NTV
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT;
PRICELIST;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY;
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
SHIP_FROM_LOCATION;
SHIP_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
*Invoice Matching Rules
Select Invoice Matching Rules to access the invoice matching rules from the BuyerXpert/SellerXpert graphical administrative interface.
The invoice matching rules are:
Invoice Matching Algorithm (INVOICE_MATCHING_ALGORITHM) — Allows you to customize the invoice matching process. The string defined here can be accessed in the iPlanet Process Manager and used to customize the invoice matching routine.
Allowed to Pay Invoice (ALLOWED_TO_PAY_INVOICE) — Determines if the Pay Anyway button is available in the invoice matching user interface.
Payment Voucher Currency (PAYMENT_VOUCHER_CURRENCY) — Specifies the currency to use when creating payment voucher XML documents.
Invoicing User (INVOICE_USER) — Specifies a user environment to use to execute the invoice matching algorithm process, because the invoice matching process is not started directly through a user interface. The invoice matching process starts automatically when an invoice is received.
*Invoice Matching Rules Conflict Resolution
Table 5-13 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-13 Invoice Matching Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
INVOICE_MATCHING_
ALGORITHM
|
String
|
PRODUCT;
SELLER_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
ALLOWED_TO_PAY_
INVOICE
|
Boolean
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
PAYMENT_VOUCHER_
CURRENCY
|
Integer
|
USER_CREATED_FOR;
SELLER_COMPANY;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
INVOICE_USER
|
String
|
SELLER_COMPANY;
BUYER_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Locale Rule
Select Rules for Locales to access the local rule from the BuyerXpert/SellerXpert graphical administrative interface.
The locale rule is:
Preferred Locale (PREFERRED_LOCALE) — Indicates the preferred locale (country) to use.
Locale Rule Conflict Resolution
Table 5-14 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-14 Locale Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
PREFERRED_LOCALE
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Location Rules
Select Location>Location Rules to access the bill to location rules from the BuyerXpert/SellerXpert graphical administrative interface.
The BuyerXpert/SellerXpert location rules are:
Bill to Location Rules
Select Location>Bill To Location Rules to access the location rules from the BuyerXpert/SellerXpert graphical administrative interface.
The bill to location rules are:
Default Bill to Location (BILLTO_LOCATION_DEFAULT) — Defines the default bill to location for an order.
Bill to Location List (BILLTO_LOCATION_LIST) — Specifies the bill to location list.
Default Bill to Contact (CONTACT_BILLTO_DEFAULT) — Defines the default bill to contact person for an order.
Bill to Contact List (BILLTO_CONTACT_LIST) — Specifies the bill to location contact person list.
Bill to Location Rules Conflict Resolution
Table 5-15 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-15 Bill to Location Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
BILL_TO_LOCATION_
DEFAULTS
|
String
|
USER_CREATED_FOR;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
BILL_TO_LOCATION_
LIST
|
String
|
USER_CREATED_FOR;
SEND_TO_LOCATION
|
UNION
|
UNION
|
UNION
|
|
CONTACT_BILL_TO_
DEFAULT
|
String
|
USER_CREATED_FOR;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CONTACT_BILL_TO_
LIST
|
String
|
USER_CREATED_FOR;
SEND_TO_LOCATION
|
UNION
|
UNION
|
UNION
|
Ship to Location Rules
Select Location>Ship To Location Rules to access the ship to location rules from the BuyerXpert/SellerXpert graphical administrative interface.
The ship to location rules are:
Default Ship to Location (SHIPTO_LOCATION_DEFAULT) — Specifies ship to location default.
Ship to Location List (SHIPTO_LOCATION_LIST) — Specifies ship to location list.
Default Ship to Contact (CONTACT_SHIPTO_DEFAULT) — Specifies the default contact person for ship to location.
Ship to Contact List (CONTACT_SHIPTO_LIST) — Specifies the contact person list for ship to location.
Ship to Location Conflict Resolution
Table 5-16 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-16 Ship to Location Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
CONTACT_SHIPTO_
DEFAULT
|
String
|
USER_CREATED_FOR;
SHIPTO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CONTACT_SHIPTO_
LIST
|
String
|
USER_CREATED_FOR;
SHIPTO_LOCATION
|
UNION
|
UNION
|
UNION
|
|
SHIPTO_LOCATION_
DEFAULT
|
String
|
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
SHIPTO_LOCATION_
LIST
|
String
|
USER_CREATED_FOR;
SHIPTO_LOCATION
|
UNION
|
UNION
|
UNION
|
Ship From Location Rules
Select Location>Ship From Location Rules to access the ship from location rules from the BuyerXpert/SellerXpert graphical administrative interface.
The ship from location rules are:
Default Ship from Location (SHIPFROM_LOCATION_DEFAULT) — Specifies ship from location default.
Ship from Location List (SHIPFROM_LOCATION_LIST) — Specifies ship to location list.
Default Ship from Contact (CONTACT_SHIPFROM_DEFAULT) — Specifies default contact person for ship to location.
Ship from Contact List (CONTACT_SHIPFROM_LIST) — Specifies contact person list for ship to location.
Ship From Location Conflict Resolution
Table 5-17 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-17 Ship From Location Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
SHIPFROM_LOCATION_
DEFAULT
|
String
|
SELLER_COMPANY;
PRODUCT;
SHIPTO_LOCATION;
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
SHIPFROM_LOCATION_
LIST
|
String
|
SELLER_COMPANY;
PRODUCT;
SHIPTO_LOCATION;
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
USER_CREATED_FOR
|
UNION
|
UNION
|
UNION
|
|
CONTACT_SHIPFROM_
DEFAULT
|
String
|
SELLER_COMPANY;
PRODUCT;
SHIP_FROM_LOCATION;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CONTACT_SHIPFROM__
LIST
|
String
|
SELLER_COMPANY;
PRODUCT;
SHIP_FROM_LOCATION;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY;
USER_CREATED_FOR
|
UNION
|
UNION
|
UNION
|
Pay to Location Rules
Select Location>Pay to Location Rules to access the pay to location rules from the BuyerXpert/SellerXpert graphical administrative interface.
The pay to location rules are:
Default Pay to Location (PAYTO_LOCATION_DEFAULT) — Specifies pay to location default.
Pay to Location List (PAYTO_LOCATION_LIST) — Specifies default pay to location list.
Default Pay to Contact (CONTACT_PAYTO_DEFAULT) — Specifies default contact person for pay to location.
Pay to Contact List (CONTACT_PAYTO_LIST) — Specifies default contact person list for pay to location.
Pay to Location Conflict Resolution
Table 5-18 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-18 Pay to Location Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
PAYTO_LOCATION_
DEFAULT
|
String
|
USER_CREATED_FOR;
PAYTO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
PAYTO_LOCATION_
LIST
|
String
|
USER_CREATED_FOR;
PAYTO_LOCATION
|
UNION
|
UNION
|
UNION
|
|
CONTACT_PAYTO_
DEFAULT
|
String
|
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CONTACT_PAYTO__
LIST
|
String
|
USER_CREATED_FOR;
SHIPTO_LOCATION
|
UNION
|
UNION
|
UNION
|
Send to Location Rules
Select Location>Send to Location Rules to access the send to location rules from the BuyerXpert/SellerXpert graphical administrative interface.
The send to location rules are:
Default Send to Location (SENDTO_LOCATION_DEFAULT) — Specifies send to location default.
Send to Location List (SENDTO_LOCATION_LIST) — Specifies send to location list.
Default Send to Contact (CONTACT_SENDTO_DEFAULT) — Specifies default contact person for send to location.
Send to Contact List (CONTACT_SENDTO_LIST) — Specifies send to location contact person list.
Send to Location Conflict Resolution
Table 5-19 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-19 Send to Location Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
SENDTO_LOCATION_
DEFAULT
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
SENDTO_LOCATION_
LIST
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT
|
UNION
|
UNION
|
UNION
|
|
CONTACT_SENDTO_
DEFAULT
|
String
|
SEND_TO_LOCATION;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CONTACT_SENDTO_
LIST
|
String
|
SEND_TO_LOCATION;
USER_CREATED_FOR
|
UNION
|
UNION
|
UNION
|
Order Entry Rules
Select Order Processing> Rules for Order Entry to access the order entry rules from the BuyerXpert/SellerXpert graphical administrative interface.
The order entry rules are:.
Line Grouping Number (LG_NUMBER) — Specifies the number of lines in a purchase order. This rule contains the following NTV values:
PREFIX — Specifies purchase order prefix.
SEQUENCE_NAME— Specifies purchase sequence name.
SUFFIX — Specifies purchase order suffix.
Global Template for Requisition (REQUISITION_GLOBAL_TEMPLATES) — Specifies global templates to use creating requisitions.
Global Template for Orders (ORDER_GLOBAL_TEMPLATES) — Specifies global templates to use creating orders.
Order Entry Rules Conflict Resolution
Table 5-20 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-20 Order Entry Rules
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
LG_NUMBER
|
NTV
|
LGU_NAME;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
REQUISITION_GLOBAL_
TEMPLATES
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
ORDER_GLOBAL_
TEMPLATES
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Payment Rules
BuyerXpert/SellerXpert provides the following payment rules:
Payment Types Business Rules
Select Payments>Payment Types to access the payment subtype rules from the BuyerXpert/SellerXpert graphical administrative interface.
The payment subtypes business rules are:
Default Payment Subtype (PAYMENT_SUBTYPE_DEFAULT) — Specifies the default payment subtypes. This rule contains the following NTV values:
MAX— Specifies the maximum payment subtype.
MIN — Specifies the minimum payment subtype.
METHOD — Specifies the payment subtype method.
Payment Subtypes List (PAYMENT_SUBTYPE_LIST) — Specifies the payment subtypes list. This rule contains the following NTV values:
MAX— Specifies the maximum payment subtype.
MIN — Specifies the minimum payment subtype.
METHOD — Specifies the payment subtype method.
-
To set multiple values, such as multiple credit cards, for a payment subtype list rule instance you must define multiple instances. You can not define them as part of one instance. However, it is possible to set multiple values with other list rules.
-
You can use the payment type or payment subtype as a value for the payment subtype.
Payment Types Rules Conflict Resolution Table
Table 5-21 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-21 Payment Types Conflict Resolution Table
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
PAYMENT_SUBTYPE_
DEFAULT
|
NTV
|
USER_CREATED_FOR;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
PAYMENT_SUBTYPE_
LIST
|
NTV
|
USER_CREATED_FOR;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Payment Terms Business Rules
Select Payments>Payment Rules to access the payment terms rules from the BuyerXpert/SellerXpert graphical administrative interface.
The payment terms business rules are:
Default Payment Terms (PAYMENT_TERMS_DEFAULT) — Specifies the default payment terms.
Payment Terms List (PAYMENT_TERMS_LIST) — Specifies the payment terms list.
Payment Processing Methods for Orders (PAYMENT_PROCESSING_ METHOD— Specifies the kinds of payments (credit cards, bank account, and so on).
Payment Terms Rules Conflict Resolution Table
Table 5-22 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values
Table 5-22 Payment Terms Conflict Resolution Table
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
PAYMENT_TERMS_
DEFAULT
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
PAYMENT_TERMS_LIST
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
SEND_TO_LOCATION
|
UNION
|
UNION
|
UNION
|
|
PAYMENT_PROCESSING_METHODS_ORDERS
|
String
|
BUYER_COMPANY; SELLER_COMPANY; PAYMENT_TYPE
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Pricing Rules
Select Pricing>Pricing Rules to access the pricing rules from the BuyerXpert/SellerXpert graphical administrative interface.
The pricing rules are:
Price Additional Precision (PRICE_ADDITIONAL_PRECISION) — Indicates decimal places to use for price adjustments.
Price Adjustment (PRICE_ADJUSTMENTS) — Indicates discounts, charges, allowable decimal places beyond the default, or promotional (DCAP) price adjustment to use.
PriceList (PRICELIST) — Defines the pricelist to use. This rule contains the following NTV values:
PRICE_COLUMN_LOWEST_CHOICE — Picks the lowest price as the look up price.
PRICELIST — Defines the pricelist to use.
PRICELIST_COLUMN_LOOKUP — Identifies look up table to use for determining price look up column.
PRICELIST_DEFAULT_COLUMN — Identifies default pricelist column to use.
PriceList Discount Markup (PRICELIST_DISCOUNT_ MARKUP) — Determines pricelist discount markup to use when the product price model uses discount price.
Pricing Model (PRICING_MODEL) — Indicates default price models. Values are CATALOG, PRICELIST, USER_ESTIMATE.
Can Override Price (CAN_OVERRIDE_PRICE) — Allows you to override a price.
Pricing External API Settings (PRICING_EXTAPI_SETTINGS —
Pricing Rules Conflict Resolution
Table 5-1 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-23 Pricing Rules Conflict Resolution
|
Rule Name
|
Value Type
|
Role Ordering Resolution
|
Inheritance Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
PRICE_ADDITIONAL_
PRECISION
|
Integer
|
CURRENCY_UNIT;
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
HIGHEST
|
HIGHEST
|
|
PRICE_ADJUSTMENTS
|
String
|
SELLER_COMPANY;
PRODUCT;
PRICELIST;
USER_CREATED_FOR
|
UNION
|
MOST_RECENT
|
UNION
|
|
PRICELIST
|
NTV
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT
|
INTERSECTION
|
MOST_RECENT
|
UNION
|
|
PRICELIST_DISCOUNT_
MARKUP
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
PRICING_MODEL
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CAN_OVERRIDE_PRICE
|
Boolean
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
PRICING_EXTAPI_
SETTINGS
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Quality Entry Rule
Select Quality Entry Rules to access the quality entry rule from the BuyerXpert/SellerXpert graphical administrative interface.
The quality entry rule is:
Quality Entry Form (QUALITY_ENTRY_FORM) — Indicates that you can add a quality entry form.
Quality Entry Rule Conflict Resolution
Table 5-24 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-24 Quality Entry Rule
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
QUALITY_ENTRY_FORM
|
String
|
PRODUCT;
SELLER_COMPANY;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
*Receiving Rules
Select Receiving Rules to access the receiving rules from the BuyerXpert/SellerXpert graphical administrative interface.
The receiving rules are:
Receiving Tolerance (RECEIVING_TOLERANCE) — Describes the receiving rules tolerances. This rule contains the following NTV values:
Receiving Tolerance Precision (RECEIVING_TOLERANCE_PRECISION) — Specifies permissible variation that is allowed over the ordered amount.
Can Receive (CAN_RECEIVE) — Indicates who can receive an order.
*Receiving Rules Conflict Resolution
Table 5-25 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-25 Receiving Rules
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
RECEIVING_TOLERANCE
|
NTV
|
PRODUCT;
SELLER_COMPANY;
USER_CURRENT
|
PREFER_SPECIFIC
|
LOWEST
|
LOWEST
|
|
RECEIVING_TOLERANCE_
PRECISION
|
Integer
|
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
LOWEST
|
LOWEST
|
|
CAN_RECEIVE
|
Boolean
|
USER_CURRENT;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Reports Rules
Select Rules for Reports to access the report rules from the BuyerXpert/SellerXpert graphical administrative interface.
Report rules allow you to product reports at the user, manager, orgadmin, or superadmin level. Each report requires different levels of access permission.
The report rules are:
Can View User Reports (CAN_VIEW_USER_REPORTS) — Indicates you have permission to view user reports.
Can View Manager Reports (CAN_VIEW_MANAGER_REPORTS) — Indicates you have permission to view manager reports.
Can View Admin Reports (CAN_VIEW_ADMIN_REPORTS) — Indicates you have permission to view orgadmin reports.
Can View SuperAdmin Reports (CAN_VIEW_SUPERADMIN_REPORTS) — Indicates you have permission to view superadmin reports.
Reports Rules Conflict Resolution
Table 5-26 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-26 Reports Rules Conflict Resolution
|
Field Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
CAN_VIEW_USER_
REPORTS
|
Boolean
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CAN_VIEW_MANAGER_
REPORTS
|
Boolean
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CAN_VIEW_ADMIN_
REPORTS
|
Boolean
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CAN_VIEW_SUPERADMIN_
REPORTS
|
Boolean
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Sales Quote Rules
Select > to access the sales quote rules from the SellerXpert graphical administrative interface.
The sales quote rules are:
Sales Quote Terms and Conditions (SALES_QUOTE_TC) — Enables the terms and conditions file to be accessed based on the user.
Sales Quote Valid Days (SALES_QUOTE_VALID_DAYS) — Indicates the number of days which the sales quote is valid.
Sales Quote Rules Conflict Resolution
Table 5-28 describes how SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-27 Sales Quote Rules Conflict Resolution
|
Rule
Name
|
Valid
Roles
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
SALES_QUOTE_TC
|
String
|
USER_CREATED_FOR;
HOST_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
SALES_QUOTE_VALID_DAYS
|
Integer
|
USER_CREATED_FOR;
HOST_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Security Rules
Select General Info>Security Rules to access the security rules from the BuyerXpert/SellerXpert graphical administrative interface.
The security rules are:
Security Rules Conflict Resolution
Table 5-28 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-28 Security Rules Conflict Resolution
|
Rule
Name
|
Valid
Roles
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
ALLOW_PASSWORD_
LOGIN
|
Boolean
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CAN_SET_OWNER
|
Boolean
|
USER_CURRENT;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Shipping Rules
Select Shipping>Shipping Rules or Pricing>Shipping Rules to access the shipping rules from the BuyerXpert/SellerXpert graphical administrative interface.
The shipping rules are:
Default Freight Terms (FREIGHT_TERM_DEFAULT) — Specifies default freight terms and conditions for an order.
Freight Terms List (FREIGHT_TERM_LIST) — Indicates freight terms and conditions to use for an order.
Group Level Shipping Charge (GROUP_LEVEL_SHIPPING_CHARGE) — Specifies group level shipping charge.
Line Level Shipping Charge (LINE_LEVEL_SHIPPING_CHARGE) — Specifies line level shipping charge.
Default Shipping Method (SHIPPING_METHOD_DEFAULT) — Specifies default shipping method.
Shipping Method List (SHIPPING_METHOD_LIST) — Specifies default shipping method.
Shipping Rules Conflict Resolution
Table 5-1 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Shipping Rules Conflict Resolution
Table 5-29 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-29 Shipping Rules Conflict Resolution
|
Rule
Name
|
Value Type
|
Role
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
FREIGHT_TERM_
DEFAULT
|
String
|
PAYMENT_SUBTYPE;
SHIPPING_METHOD;
USER_CREATED_FOR;
SELLER_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
FREIGHT_TERM_LIST
|
String
|
PAYMENT_SUBTYPE;
SHIPPING_METHOD;
USER_CREATED_FOR;
SELLER_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
GROUP_LEVEL_
SHIPPING_CHARGE
|
String
|
SELLER_COMPANY;
PRODUCT;
CARRIER_COMPANY;
SHIP_FROM_LOCATION;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY;
SHIP_TO_LOCATION:
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
UNION
|
UNION
|
|
LINE_LEVEL_SHIPPING_
CHARGE
|
String
|
SELLER_COMPANY;
PRODUCT;
CARRIER_COMPANY;
SHIP_FROM_LOCATION;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY;
SHIP_TO_LOCATION:
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
USER_CREATED_FOR
|
UNION
|
UNION
|
UNION
|
|
SHIPPING_METHOD_
DEFAULT
|
String
|
SHIP_FROM_LOCATION;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY;
SHIP_TO_LOCATION:
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
USER_CREATED_FOR
SELLER_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
SHIPPING_METHOD_LIST
|
String
|
SHIP_FROM_LOCATION;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY;
SHIP_TO_LOCATION:
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
USER_CREATED_FOR;
SELLER_COMPANY
|
UNION
|
UNION
|
UNION
|
Tax Rules
Select Pricing>Tax Rules to access the taxation rules from the BuyerXpert/SellerXpert graphical administrative interface.
The taxation rules are:
Customer Taxability (CUSTOMER_TAXABILITY) — Indicates a customer's tax status. This rule contains the following NTV value:
CUSTOMER_TAX_CERTIFICATE_ID — Customer's tax certificate ID.
Group DCAP Taxability Table (GROUP_DCAP_TAX_TABLE) — Tax table for group discounts, charges, allowances, and promotions (DCAPs) tax rates.
Group Freight Taxability Table (GROUP_FREIGHT_TAX_ TABLE) — Tax table for group freight tax rates.
Line Item Tax (LINE_DCAP_TAX_TABLE) — Tax table for line item discounts, charges, allowances, and promotions (DCAPs). This rule contains the following NTV values:
LINE_FREIGHT_TAX_TABLE — Tax table for line item freight charges.
PRODUCT_TAXABILITY — Indicates whether a product is taxable.
TAX_MODEL — Determines the tax model and adjustment table to use for a specific order or customer.
TAX TABLE — Specifies tax table to use.
Tax Code (TAX_ CODE) — Identifies the tax code to use for a specific order or customer.
Tax Rules Conflict Resolution
Table 5-30 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-30 Taxation Rules Conflict Resolution
|
Rule Name
|
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
CUSTOMER_
TAXABILITY
|
NTV
|
SELLER_COMPANY;
PRODUCT;
USER_CREATED_FOR;
SHIP_TO_LOCATION;
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
SHIP_FROM_LOCATION;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
GROUP_DCAP_TAX_
TABLE
|
String
|
USER_CREATED_FOR;
DCAP_ADJUSTMENT;
SELLER_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
GROUP_FREIGHT_
TAX_TABLE
|
String
|
USER_CREATED_FOR;
FREIGHT_ADJUSTMENT;
SELLER_COMPANY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
TAX_CODE
|
String
|
SELLER_COMPANY;
PRODUCT;
USER_CREATED_FOR;
SHIP_TO_LOCATION;
SHIPTO_REGION;
SHIPTO_MAJOR_
LOCALITY;
SHIP_FROM_LOCATION;
SHIPFROM_REGION;
SHIPFROM_MAJOR_
LOCALITY
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
*Timecard Rules
Select Timecard>Timecard Rules to access the timecard rules from the BuyerXpert graphical administrative interface.
The timecard rules are:
*Timecard Rules Conflict Resolution
Table 5-31 describes how BuyerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-31 Timecard Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
TIMECARD_APPROVAL
|
Boolean
|
USER_CREATED_FOR;
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
CAN_CREATE_TIMECARD
|
String
|
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Transmission Rules
Select Transmission Rules to access the transmission rules from the BuyerXpert/SellerXpert graphical administrative interface.
The transmission rules are used to transmit EDI documents. The rules include:
EDI Document Rule
Select Transmission Rules>EDI Document to access the EDI document rule from the BuyerXpert/SellerXpert graphical administrative interface.
The EDI document rules is:
EDI Document (XMIT_DOCUMENT) — Describes how to transmit EDI documents. This rule contains the following NTV value:
ORDER_CHANGE — Specifies EDI document format to use for transmitting order changes.
EDI Document Rules Conflict Resolution
Table 5-32 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-32 EDI Document Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
XMIT_DOCUMENT
|
NTV
|
USER_CREATED_FOR;
SELLER_COMPANY;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
EDI Receiver Rule
Select Transmission Rules>EDI Receiver to access the EDI receiver rule from the BuyerXpert/SellerXpert graphical administrative interface.
The EDI receiver rules is:
EDI Receiver (XMIT_RECEIVER) — Describes how to receive EDI documents. This rule contains the following NTV value:
ORDER_CHANGE — Specifies EDI document format to use for receiving order changes.
EDI Receiver Rules Conflict Resolution
Table 5-33 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-33 EDI Receiver Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
XMIT_RECEIVER
|
NTV
|
USER_CREATED_FOR;
SELLER_COMPANY;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
EDI Sender Rule
Select Transmission Rules>EDI Sender to access the EDI sender rule from the BuyerXpert/SellerXpert graphical administrative interface.
The EDI sender rule is:
EDI Sender (XMIT_SENDER)— Describes how to send EDI documents. Required attributes are:
ORDER_CHANGE — Specifies EDI sender format to use for transmitting order changes.
EDI Sender Rule Conflict Resolution
Table 5-34 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-34 EDI Sender Rule Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
XMIT_SENDER
|
NTV
|
USER_CREATED_FOR;
SELLER_COMPANY;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
EDI Currency Rule
Select Transmission Rules>EDI Currency to access the EDI currency rule from the BuyerXpert/SellerXpert graphical administrative interface.
The EDI currency rule is:
EDI Currency (XMIT_CURRENCY)— Defines the currency to use for an EDI document.
EDI Currency Rule Conflict Resolution
Table 5-35 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-35 EDI Currency Rule Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
XMIT_CURRENCY
|
String
|
USER_CREATED_FOR;
SELLER_COMPANY;
SEND_TO_LOCATION
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
*OBI Compliant Rule
Select Transmission Rules>OBI Compliant to access the OBI compliant rule from the BuyerXpert/SellerXpert graphical administrative interface.
The OBI compliant rule is:
OBI Compliant (OBI_COMPLIANT) — Indicates a document is OBI compliant.
*OBI Compliant Rule Conflict Resolution
Table 5-36 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-36 OBI Compliant Rule Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
OBI_COMPLIANT
|
Boolean
|
SELLER_COMPANY;
USER_CREATED_FOR
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
EDI Auto Submit Rule
Select Transmission Rules>Auto Submit to access the auto submit rule from the BuyerXpert/SellerXpert graphical administrative interface.
The auto submit rule is:
Auto Submit (AUTO_SUBMIT) — Indicates if you can automatically submit an EDI document.
Auto Submit Rule Conflict Resolution
Table 5-37 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-37 EDI Auto Submit Rule Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
AUTO_SUBMIT
|
Boolean
|
USER_CREATED_FOR;
USER_CURRENT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
AIF (UDF) Rule
Select Accounting Code Rules to access the UDF (also known as AIF, additional information field) rule from the BuyerXpert/SellerXpert graphical administrative interface.
UDF Default Value (UDF_DEFAULT_VALUE) — Specifies the default UDF accounting code value.
UDF Rule Conflict Resolution
Table 5-5 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-38 UDF Rule Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
UDF_DEFAULT_VALUE
|
String
|
USER_CREATED_FOR;
UDF
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
Unit Conversion Rules
Select Order Processing>Unit Conversion Rules to access the unit conversion rules from the BuyerXpert/SellerXpert graphical administrative interface.
The unit conversion rules are:
Quantity Conversion Table (QUANTITY_CONVERSION_TABLE) — Describes the quantity conversion table.
Quantity Precision (QUANTITY_PRECISION) — Specifies the quantity precision.
Weight Conversion Table (WEIGHT_CONVERSION_TABLE) — Describes the quantity conversion table.
Weight Precision (WEIGHT_PRECISION) — Specifies the weight precision.
Unit Conversion Rules Conflict Resolution
Table 5-39 describes how BuyerXpert/SellerXpert resolves conflicts when multiple rules apply for a given situation. See "Conflict Resolution Strategies" for definitions of the columns used in the table and the allowable conflict resolution values.
Table 5-39 Unit Conversion Rules Conflict Resolution
|
Rule
Name
|
Value
Type
|
Role Ordering
Resolution
|
Inheritance
Resolution
|
DAG
Resolution
|
Duplicate
Resolution
|
|
QUANTITY_CONVERSION_
TABLE
|
String
|
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
QUANTITY_PRECISION
|
String
|
QUANTITY_UNIT;
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
LOWEST
|
LOWEST
|
|
WEIGHT_CONVERSION_
TABLE
|
String
|
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
MOST_RECENT
|
MOST_RECENT
|
|
WEIGHT_PRECISION
|
Integer
|
WEIGHT_UNIT;
SELLER_COMPANY;
PRODUCT
|
PREFER_SPECIFIC
|
HIGHEST
|
HIGHEST
|