Chapter 2   Configuring Access


This chapter provides instructions for setting up access to your BuyerXpert/SellerXpert system and configuring buyer for ECXpert.

---

Note	The information in this chapter is based on the assumption that you have already read the BuyerXpert/SellerXpert Concepts and Release Notes.

---

This chapter contains following sections:

• About Configuring Access

• Administrator's Access Tasks

• Configuring BuyerXpert/SellerXpert for Outbound Documents

• Configuring BuyerXpert/SellerXpert for Inbound Documents

• Configuring Business Rules

• Requirements for Inbound EDI Documents

• Deployment Issues

  
  

  ---

  Note	An asterisk (*) at the beginning of a chapter name/heading or at the end of a line indicates that the material applies to BuyerXpert only.

  ---

  
  

About Configuring Access

---

BuyerXpert/SellerXpert has the flexibility to write out XML files in different formats. The XML file can be in OBI 3.0 (draft) standard format or non-OBI format depending on how your business rules are set up. ECXpert and BuyerXpert/SellerXpert communicate through the NFS file system.

The BuyerXpert/SellerXpert software is shipped with maps that convert between OBI 3.0 (draft) and EDI 3040 standards. This chapter discusses integration between BuyerXpert/SellerXpert and ECXpert for both outbound and inbound BuyerXpert/SellerXpert documents.

The following types of EDI documents are supported by BuyerXpert/SellerXpert:

• 850—Purchase order (PO)

• 860—Change order (CO)

• 850—Order request (OR)*

• 855—Acknowledgement of order receipt (Ack)

• 856—Advance shipment notice (ASN)

• 865—Acknowledgement of order change (Change Ack)

Figure 2-1 shows the process flow between BuyerXpert and ECXpert.

Figure 2-1    Process Flow between BuyerXpert and ECXpert

Administrator's Access Tasks

---

Some of the procedures for administering access are contained in this administrator's guide and some are contained in the Admin interface help. Table 2-1 contains a list of common access tasks. The right-hand column provides information about where to find instructions, guidelines, or tools for performing that task.

Table 2-1    Administrator's Access Tasks 

Task	Location of Instructions/Guidelines/Tools
Configure for outbound documents.	Configuring BuyerXpert/SellerXpert for Outbound Documents section ECXpert Administration Guide
Configure ECXpert. Includes setting up members, training partnerships, maps, service lists, and custom services	Configuring BuyerXpert/SellerXpert for Inbound Documents section
Configure associated business rules.	Configuring Business Rules section Chapter 5 "Setting Up Business Rules" BuyerXpert/SellerXpert Admin interface
Observe requirements for inbound EDI documents.	Requirements for Inbound EDI Documents section
Review issues to be aware of for deployment.	Deployment Issues section

Configuring BuyerXpert/SellerXpert for Outbound Documents

---

Figure 2-2 shows the process flow for outbound documents.

Figure 2-2    Outbound Documents Process Flow

The data submitted to ECXpert needs to have a header record (HREC) and a trailer record (TREC). The header record has twelve fields, some of which are optional. The key fields are:

• Sender Qualifier

• Sender ID

• Receiver Qualifier

• Receiver ID

• Document Type.

Example of a Header Record
HREC**|ZZ|buyer|ZZ|seller|AOL000000001155|X|003040|850|OEPO

Example of a Trailer Record
TREC**

For details on the header record format, see the ECXpert Site Administrator's Guide.

The submitToECX_850.sh script (and the submitToECX_860.sh script) first normalizes the XML file, then adds the header record and trailer record, depending on the partnership agreement. Then the ECXpert submit command is called.

All configuration, including email configuration, can be done using the config_xdoc.pl script, which is located in the BuyerXpert/SellerXpert NASROOT/buyer/sample_data/xdoc/scripts directory.

Configuring BuyerXpert/SellerXpert for Inbound Documents

---

Figure 2-3 shows the process flow for inbound documents.

Figure 2-3    Inbound Documents Process Flow

The xdocin.sh script and java class wakeBuyer.class/wakeSeller.class are located in this ECXpert directory: $ECXHOME/bin.

The xdocin.sh scripts calls the wakeBuyer.class/wakeSeller.class and passes three arguments to wakeBuyer:

• Buyer server name

• Buyer server port

• XDOC data file name

The wakeBuyer class wakes servlet ReadInTest in BuyerXpert/SellerXpert, at which point the xdocin.sh script is set up as a service in ECXpert.

The files can be copied to their respective directories using the config_xdoc_in.pl script, which is located in the following BuyerXpert/SellerXpert directory: iASROOT/buyer/sample_data/xdoc/scripts.

Configuring ECXpert

Before you run the script, there are a number of set up tasks required so that ECXpert can interface with BuyerXpert/SellerXpert to route documents between sellers and the BuyerXpert/SellerXpert system.

These tasks include:

• Defining ECXpert Members

• Defining Trading Partnerships

• Setting Up Maps

• Defining a Custom Service

• Defining Service Lists

Defining ECXpert Members

You must define the following members in ECXpert:

• A member representing each buyer organization

• A member representing each seller organization
  

  ---

  Note	Member names must match the names specified in the EDI SENDER and EDI RECEIVER rules.

  ---

  
  

For the sample data provided with BuyerXpert/SellerXpert to work, you must create the following member organizations:

• mercury

• staples

Defining Trading Partnerships

For members to exchange information using ECXpert, a trading partnership must be set up specifying the details of the exchange. A trading partnership specifies:

• Who is sending

• Who is receiving

• What type of information is involved

• How the information is to be sent and received at each end

Table 2-2 lists the entries required for sample data to work.

Table 2-2    Required Trading Partnership 

Sender	Receiver	Document	Direction	Map	doc_type
mercury	staples	PO	Outbound	B850ECX35V34O.sun	850
mercury	staples	Change	Outbound	B860ECX35V34O.sun	860
staples	mercury	Order Request*	Inbound	B850ECX35V34I.sun	850
staples	mercury	Ack	Inbound	B855ECX35V34I.sun	855
staples	mercury	ASN	Inbound	B856ECX35V34I.sun	856
staples	mercury	Change Ack	Inbound	B865ECX35V34I.sun	865

Setting Up Maps

Run the config_xdoc._in.pl script to set up maps to the correct directory for ECXpert to pick up.

Defining a Custom Service

To perform a service that is not built into ECXpert, you can define a custom service. BuyerXpert/SellerXpert ships with scripts that perform services that BuyerXpert/SellerXpert requires but that ECXpert does not provide

Table 2-3 lists the custom services needed to make sample data work.

Table 2-3    Required Custom Services 

Script	Description	Service Name
xdocin_850.sh	inbound 850 staples->mercury*	inbound850
xdocin_855.sh	inbound 855 staples->mercury	inbound855
xdocin_856.sh	inbound 856 staples->mercury	inbound856
xdocin_865.sh	inbound 865 staples->mercury	inbound865

Defining Service Lists

In ECXpert, a service is a particular type of processing to be performed. Service lists indicate what services ECXpert is to perform on the transactions.

Table 2-4 lists the service lists required for the sample data to work.

Table 2-4    Required Service Lists 

Sender	Receiver	Document	doc_type	Service List
mercury	staples	PO	850	parse, translate, ..
mercury	staples	Change	860	parse, translate, ..
staples	mercury	Order request*	850	parse, translate,inbound850
staples	mercury	Ack	855	parse, translate,inbound855
staples	mercury	ASN	856	parse, translate,inbound856
staples	mercury	Change Ack	865	parse, translate,inbound865

Configuring Business Rules

---

The following BuyerXpert/SellerXpert business rules are associated with access and transmission:

• EDI Sender

• EDI Receiver

• EDI Document

• OBI Compliant

• Auto Submit*

• XMIT Currency

These business rules must be set up for every buyer organization, and can be accessed in the Transmission Rules category of the Admin interface. For additional information on business rules, refer to Chapter 5 "Setting Up Business Rules."

EDI Sender Rule

The name of the sender should match the name of the member in ECXpert. Enter this name for both Purchase Order and Order Change documents.

EDI Receiver

The name of the sender should match the name of the member in ECXpert. Enter this name for both Purchase Order and Order Change documents.

EDI Document

The name of the sender should match the doc_type in ECXpert. Enter 850 for Purchase Order and 860 for Order Change documents.

*OBI Compliant

Set this rule to True if you want BuyerXpert/SellerXpert to write out non-OBI compliant XML files.

Auto Submit

Set this to True if you want BuyerXpert/SellerXpert to automatically submit an incoming Purchase Order (850) document to approval.

XMIT Currency

Set this rule if you want BuyerXpert/SellerXpert to transmit the Purchase Order document (outbound 850) in a currency different from common currency.

---

Note	Verify that the conversion between this currency and common currency already exists in the buyer organization conversion table.

---

Requirements for Inbound EDI Documents

---

The following guidelines should be followed by the seller when transmitting an inbound document:

• All inbound documents should include the buyer organization name and seller organization name. The names should already exist in the database of the buyer organization.

  For OBI2.1, it is N1*BY and N1*SE.

• All inbound documents should include the requisitioner's login name.

  For OBI2.1, it is N1*EY

  For OBI3.0, put it into the email field of BuyingParty Contact

• For an Order Request document, the seller organization address must be used as the send-to location.*

• The buyer organization address will not be processed. The buyer organization address should already exist in the buyer database.

• For the ASN document, the seller organization should provide a carrier reference number so the requisitioner can track the shipping process.*

• In an Order Request document, Total Monetary Amount (AMT) is required, not optional.

Deployment Issues

---

• File system access between the BuyerXpert/SellerXpert machine and ECXpert system must be read/write enabled. Also, the directory structure should be the same.

• The default scripts shipped with BuyerXpert/SellerXpert do not authenticate ECXpert. Therefore, the members must be made trusted.

• For outbound documents, the mapping from XML to EDI works only if you are using an OBI-COMPLIANT model.

• If you run the config_xdoc.pl script to configure BuyerXpert/SellerXpert for ECXpert, you will have the same header record for all partnerships. You can however, customize the header records in the deployed directory.

• Java (JDK 1.1 or higher) and Perl (5.0 or higher) must be in the environment.