Last updated on 8/31/01
These release notes present information available at the release of SellerXpert 4.1 SP1.
Electronic versions of these release notes and other iPlanet documentation can be found at:
We recommend that you refer to the web site for the latest information prior to installing and setting up your software, and thereafter that you periodically view the most current release notes and manuals.Customer web site: http://iplanetcustomers.com (call iPlanet Support for password) Technical Support web site: http://www.iplanet.com/support/technical_resources/sellerxpert/
Support of Secure Data Transfer Loading of Schema and Data Outside of Installer Change in Selling Company Name and User Login for Sample Data New Business Rules DTD Changes New Characters Supported for XML
The present release also continues to supports non-secure mode. Configuration allows you to use secure mode, non-secure mode, or a combination.
OBIXMLLibrary.dtd, OBIEXTRAXMLLibrary.dtd
PostalAddress is added as an optional field
in the Contact Information.
PostalAddress is made up of AddressLine1,
AddressLine2, AddressLine3, AddressLine4,
AddressLine5, and AddressLine6. This field
is only used in outbound 850 for BuyingParty
and RequisitionParty contacts. These lines
correspond to the six postal address lines that
a user sees when editing postal address using
the Admin interface.
OBIXMLPurchaseOrder.dtd, OBIEXTRAXMLPurchaseOrder.dtd
ShippingCost is added in the POHeader. This
used to go to <charge> inside of
<AllowanceOrCharge>. Now it is consistent
with the presentation of ShippingCharge at the line
level.
< should be replaced by: <
> should be replaced by: >
& should replaced by: &
It is the responsibility of the map or the supplier to do the replacement
for inbound documents. For
outbound documents, SellerXpert does the replacement.
SellerXpert 2.6 | SellerXpert 4.1 and SP1---iPlanet Standards-based Architecture |
HTML templates | Java Server Pages (JSPs) |
Server-side JavaScript | Servlets |
C++ business objects | Java objects + EJBs business objects |
CORBA services | Java services and all iAS extensions |
CORBA components | iAS/J2EE components |
CADIS catalog | RDBMS-based catalog |
Legacy membership | LDAP membership |
Manuals for all iPlanet products can be found at the following web site:Release Notes --- Contains important information on the current release of SellerXpert. Read this document before working with the new release. New for this release. SellerXpert Installation Guide --- Provides instructions for installing the SellerXpert product and its enabling software. This includes instructions for creating schema and loading seed data. It also includes information on configuring secure-mode and non-secure mode for data transfer. Revised for this release. BuyerXpert/SellerXpert Concepts --- Describes the over-all functionality of BuyerXpert and SellerXpert. Read this document if you are unfamiliar with BuyerXpert and/or SellerXpert. Revised for this release. BuyerXpert/SellerXpert Administrator's Guide --- Provides reference information and instructions on administering a fully installed BuyerXpert/SellerXpert system. Admin interface Help --- Provides online guidelines and instructions for administering SellerXpert. Revised for this release. User interface Help --- Provides online guidelines and instructions for using SellerXpert. Revised for this release. Catalog interface Help --- Provides guidelines and instructions for managing catalogs.
http://docs.iplanet.com/docs/manuals/Return to Top of Page
Requirements for SellerXpert 4.1 SP1 |
Solaris 2.6 or 2.8 |
Netscape Navigator 4.7 or Internet Explorer 5.0 |
iPlanet Web Server (iWS), Version 4.1 SP7 |
iPlanet Application Server (iAS), Version 6.0 SP2 |
iPlanet Directory Server, Version 4.12 |
iPlanet Portal Server, Version 3.0 SP2 |
Oracle Server Database 8.1.6 Standard or Enterprise Edition with InterMedia Search Engine |
Oracle Client Server 8.1.6 (if SellerXpert is not installed on the same machine) |
Actuate e.Report Server, Version 4.1 |
Recommended for SellerXpert 4.1 SP1 |
ECXpert 3.5 |
Patches may be required for some of the supporting software. Before installation, it is important to check the release notes for the supporting software to see if patches are required and how to get them. Documentation for iPlanet products can be found at the following web site:
http://docs.iplanet.com/docs/manuals/
Installation instructions are contained in the SellerXpert Installation Guide.
Example 2: FREIGHT_TERM_DEFAULT rule does
not use payment_subtype as a role.
FREIGHT_TERM_DEFAULT rule has PAYMENT_SUBTYPE,
SHIPPING_METHOD,
USER_CREATED_FOR and SELLER_COMPANY as roles,
but it does not use
PAYMENT_SUBTYPE for its evaluation. For example,
if SHIPPING_METHOD is “UPS – 2
Day,” SELLER_COMPANY is “iplanetdemo.com,”
and USER_CREATED_FOR is “bunny1,”
there are two FREIGHT_TERM_DEFAULT rules instances
defined. One rule instance is defined
for PAYMENT_SUBTYPE “Visa” with FREIGHT_TERM
value “Visa Freight Term,” and it's
the most recent. The second rule instance
is defined for PAYMENT_SUBTYPE
“MasterCard” with FREIGHT_TERM value “MasterCard
Freight Term.” In this case, even though
the PAYMENT_SUBTYPE is “MasterCard,” the FREIGHT_TERM_DEFAULT
rule evaluation will
result in “Visa Freight Term,” because it
is the most recent.
Meaningless text displays when you run reports for the first time in a SellerXpert instance, that is, the first time you click the Run Report button in your Reports page. This happens only for Netscape 4.7 running on the Windows NT platform.Solution: Reload the HTML page.
Once catalog data is loaded into the system, catalog views need to be created with the Catalog Manager for the catalog items to be viewable by the users. The largest catalog view that has been successfully created is 300,000 items in a single view.Solution: For larger catalogs, create separate views with less than 300,000 items in each view.
Negotiated price fails to display in the SellerXpert User interface when a time-consuming search is being done (from the SellerXpert User interface) and simultaneously (without any time lag) the Catalog Manager starts browsing before the SellerXpert User interface search shows a result.Solution: Set up independent instances of the iPlanet Application Server (iAS) for SellerXpert and Catalog Manager. That is, install SellerXpert on iAS "A" and use it for front-end users only, then install SellerXpert in iAS "B" and use that one for Catalog Manager tasks only.
Occasionally the Order:CalcTaxFailed error occurs when submitting or viewing a requisition. Usually this happens when there is no corresponding tax rule.Solution: Verify that there is a tax rule for adjustments that are taxable.
If you are in daylight savings time, the follow error may occur:Return to Top of PageSolution: This is just a warning message, and does not adversely affect SellerXpert functionality.WARNING: Database and app server clock are off by -3599319 milliseconds, and the threshold is 600000...
One of the roles used for evaluating the RECEIVING_TOLERANCE rule is user_current. When the rule is evaluated, user_current has an incorrect value when the price model is PriceList.Solution:
For example, when working with Mercury Enterprises data, a user logs in as bunny15. However, when the rule was evaluated, bunny11 was the user. The solution is to set the rule for both of these users.
- Set the user_current to ALL instead of to a specific user when defining the rule value for RECEIVING_TOLERANCE.
- If #1 is not an acceptable solution:
- Identify the user that was specified when the rule was evaluated.
- Set the rule value to include this user in addition to the user who actually logged in.
Currencies that do not have entries in the <ias_root>/seller/seller/config/repository.ntv file do not display correctly if there are too many digits for the display field.Solution: Copy an existing section, such as NLG, and change the name for the currency so that it looks similar to this:
"FRFFmt" NTV {
"datatype" Str "Double",
"separator" Str ",",
"decimal_point" Str ".",
"decimal_places" Int "3",
"trailing_zeros" Bool "true",
"grouping" Int "3",
"negative_sign" Str "-",
"positive_sign" Str "",
"sign_precedes" Bool "true",
},Modify the values as needed for that currency.
When a converted unit price has more than two decimal places, the resulting price seems to be incorrect because the number is rounded to the user-display precision preference. The reason it appears wrong is because quantity * (converted unit price) is not equal to converted (unit price * quantity). According to the European Commission, converted (unit price * quantity) is the correct methodology.
Solution: The computation is actually correct.Return to Top of Page
To improve performance in catalog browsing/pricing, we have removed the PRODUCT role in the pricing model rule. However, the PRODUCT role still exists in the Admin graphical interface. As a consequence, if you defines the value for the role called PRODUCT as anything other than ALL, the role cannot take effect in pricing computations.Solution: For existing rules and any new pricing model rules, set the value for PRODUCT to ALL.
This type of adjustment is an accumulation lookup type of adjustment. The problem occurs because the program does not handle "greater than or equal to." The ranges for the lookup entries must be in this format:0 < source <= number_1
number_1 < source <= number_2
.
.
.
number_i < source <= number_i+1
number_n < source *
Solution: Do not use "greater than
or equal to."
This problem only occurs if you edit the address. The data shows in the Street field as:Return to Top of Pageaddressline1 $ addressline2 $ addressline3 $ addressline4Initially the data is correct in the database and is displayed correctly. However, the data in the database can be corrupted if the delimiters ( $ ) are disrupted.Solution: Be careful to keep the delimiters ( $ ) intact when updating the address.
Solution: There is no workaround at this time.
For both B2B and B2C registration, if a user ID that was in use at one time is deleted, the user ID cannot be re-used.Solution: There is no workaround at this time.
After you delete an order, if you use the browser Back button to reach the screen containing the original order,Return to Top of Page
SellerXpert produces an exception.Soluton: Don't use the browser back button for deleted orders.