Unit + - The Participant Nodel

+-1 Yantra Application Administration Yantra Company Confidential
+-1
© 2002 Yantra Corporation. Proprietary & Confidential.
U
n
i
t

4
:
P
a
r
t
i
c
i
p
a
n
t

M
o
d
e
l
Unit + - The Participant Nodel
+-2 Yantra Application Administration Yantra Company Confidential
+-2
Course Agenda
Unit 1 - !ntroduction
Unit 2 - !nfrastructure
Unit 3 - Presentation Framework
Unit 4 - The Participant Model
Unit 5 - Security and System Nanagement
Unit 6 - Alert Nanagement
Unit 7 - Process Definition
Unit 8 - Product Nanagement
Unit 9 - !nventory Synchronization
Unit 10 - Distributed Order Nanagement
Unit 11 - Payment Processing
Unit 12 - Logistics Nanagement
Unit 13 - Reverse Logistics
Unit + - The Participant Nodel
+-3 Yantra Application Administration Yantra Company Confidential
+-3
Yantra 5x: hanage The Extended
SuppIy ChaIn
Unit + - The Participant Nodel
+-+ Yantra Application Administration Yantra Company Confidential
+-+
UnIt 4: TopIcs
Organizations and Roles
Configure the Hub and Enterprises
Configure Buyers and Sellers
Configure Carriers and
Services
Business Rules
Case Study
Unit + - The Participant Nodel
+-5 Yantra Application Administration Yantra Company Confidential
+-5
UnIt 4: DbjectIves
Create an organization
Assign roles to an organization
Configure the role attributes
After completing this unit, you should be able to:
Unit + - The Participant Nodel
+-6 Yantra Application Administration Yantra Company Confidential
+-6
What Is the PartIcIpant hodeI!
Nethod of defining relationships between
entities in the extended network
Defines a distinct set of business rules for
each entity that will be used to process
transactions
Unit + - The Participant Nodel
+-7 Yantra Application Administration Yantra Company Confidential
+-7
DrganIzatIons û PoIes
Organization
A unique entity that represents one or more
participants
One of the trading partners in the supply chain
or extended network
Role
The part played by the organization
Pre-defined within the Yantra applications
Organizations are assigned at least one role
Lach organization can represent separate companies, di·isions within a single company, a combination
oí the two, or some other participant in the extended supply chain network.
Unit + - The Participant Nodel
+-8 Yantra Application Administration Yantra Company Confidential
+-8
PoIes
Hub
Enterprise
Buyer
Seller
Carrier
Carrier
Seller 1 Seller 2
Buyer 2 Buyer 1
Enterprise 2 Enterprise 1
Hub
Carrier
1he role is the part played by the organization in the extended network. Use these roles to model the
relationships between the players in the implementation.
1he standard \antra applications automatically understand how to use and interact with these íi·e pre-
deíined roles.
Unit + - The Participant Nodel
+-9 Yantra Application Administration Yantra Company Confidential
+-9
PoIes - Hub
Only one Hub per Yantra installation
The organization that owns the implementation
Carrier
Seller 1 Seller 2
Buyer 2 Buyer 1
Enterprise 2 Enterprise 1
Hub
Carrier
1he lub is the o·erall controlling entity being managed by \antra that owns the marketplace.
\hen you initially install \antra, an organization called DLlAUL1 is created and assigned the role oí
lub. 1his is the only organization that can play the role oí the lub. \ou can coníigure all attributes
about the DLlAUL1 organization, but you cannot assign another organization to the lub role.
Unit + - The Participant Nodel
+-10 Yantra Application Administration Yantra Company Confidential
+-10
PoIes - EnterprIses
Enterprise brokers or connects services between
Buyers and Sellers
The Hub org. can also act as an Enterprise
Carrier
Seller 1 Seller 2
Buyer 2 Buyer 1
Enterprise 2 Enterprise 1
Hub
Carrier
Lach Lnterprise can represent diííerent di·isions oí a single company, clients oí a third-party logistics
pro·ider, or diííerent sales channels, among many other scenarios. Lnterprises can own their own
warehouses or distribution centers.
1he Lnterprise is the lower le·el entity íor which \antra is managing the liíecycle oí transactions. It is a
unique business entity operating under the lub. 1he Lnterprise can directly own or contract with
distribution centers, or go through the lub to use the extended network oí Sellers.
Unit + - The Participant Nodel
+-11 Yantra Application Administration Yantra Company Confidential
+-11
Hub vs. EnterprIse
Hub
Has a view into each enterprise's orders and inventory
Enterprise
Each has their own orders and inventory
There is no visibility across to other Enterprise's orders
or inventory
Example:
A 3PL would act as a Hub
Each of their clients would act as an Enterprise
Unit + - The Participant Nodel
+-12 Yantra Application Administration Yantra Company Confidential
+-12
PoIes - ßuyers
Any organization that places orders
End customer that places sales orders
Organization that places purchase orders
Carrier
Seller 1 Seller 2
Buyer 2 Buyer 1
Enterprise 2 Enterprise 1
Hub
Carrier
1he Buyer can represent indi·idual end customers, companies or di·isions placing sales orders, or
companies placing purchase orders, among many other scenarios.
A Buyer may or may not own, or be associated with, their own recei·ing nodes.
Unit + - The Participant Nodel
+-13 Yantra Application Administration Yantra Company Confidential
+-13
PoIes - SeIIers
Any organization that fulfills orders
Can be physical or virtual fulfillment
Carrier
Seller 1 Seller 2
Buyer 2 Buyer 1
Enterprise 2 Enterprise 1
Hub
Carrier
1he Seller is any organization írom which orders can be sourced.
A Seller may or may not own, or be associated with, their own shipping nodes.
Unit + - The Participant Nodel
+-1+ Yantra Application Administration Yantra Company Confidential
+-1+
PoIes - CarrIers
An organization that moves goods between other
organizations in the network
A primary participant in the Logistics Nanagement
process
Carrier
Seller 1 Seller 2
Buyer 2 Buyer 1
Enterprise 2 Enterprise 1
Hub
Carrier
1he Carrier can be a parcel carrier, a truck-load carrier, or a less-than-truckload carrier.
Unit + - The Participant Nodel
+-15 Yantra Application Administration Yantra Company Confidential
+-15
huItIpIe PoIes - ExampIe
Org. 1 -
Buyer
Org. 2 - Enterprise,
Seller, Buyer
1. The end customer places a sales
order with the Enterprise
Org. 3 - Seller
2. The Enterprise sells items to the
Buyer and places a purchase order
with a supplier
Org. + - Carrier
3. The Seller sells items to the
Enterprise
+. The Carrier transports items
Lach organization must ha·e at least one role, but can ha·e more than one role.
Unit + - The Participant Nodel
+-16 Yantra Application Administration Yantra Company Confidential
+-16
CompIex PartIcIpant hodeIs
Furniture Dealer
(Enterprise, Seller, Buyer)
Parcel
Carrier
Hardware
Supplier (Seller)
End Customer (Buyer)
Furniture Naker
(Enterprise, Seller, Buyer)
1. Customer places a custom order for a
dining room cupboard, but wants it
made with non-standard drawer handle
hardware.
2. Dealer places the custom
order with furniture maker,
including the request for
special hardware.
3. Furniture maker has to
special-order the non-
standard drawer hardware.
+. Parcel carrier
delivers special
hardware.
TLfLTL
Carrier
5. TLfLTL
carrier
delivers
piece from
maker.
\antra can model and monitor the relationships between each oí the indi·idual organizations
participating in a gi·en marketplace.
Unit + - The Participant Nodel
+-17 Yantra Application Administration Yantra Company Confidential
+-17
Vendor 0rop ShIp ScenarIo
This scenario represents
an organization that sells
to customers, but which
sources all its inventory
from other vendors
Customer
Seller
Vendor
order
goods
Vendor
Ship Node
Vendor
Ship Node
Vendor
Vendor
Ship Node
Vendor
Ship Node
goods
Buyer
Hub, Enterprise & Seller
Nodes owned by Seller
Seller
Nodes owned by Seller
Seller
Carrier
Carrier
In this scenario, \antra allocates orders directly to the ·endor ship nodes, as the distribution
coníiguration matches items to speciíic shipping nodes.
In addition, \antra processes billing and payment iníormation íor transactions between the Customer
,Buyer, and the Seller ,lub, Lnterprise, and Seller,. \antra does not process billing and payment
iníormation íor transactions conducted between the Seller ,lub, Lnterprise, and Seller, and each oí the
indi·idual ·endors, but \antra pro·ides iníormation about the transactions íor processing done by
external systems and applications.
Unit + - The Participant Nodel
+-18 Yantra Application Administration Yantra Company Confidential
+-18
3PL ScenarIo
This scenario represents a
third-party logistics
provider that manages
orders for its clients using
inventory in the 3PL's own
nodes and inventory from
other vendors.
Customer
3PL Client
Vendor
order
goods
Vendor
Ship Node
Vendor
Ship Node
3PL Client
Buyer
Nodes owned by Seller
3PL
Hub
3PL
Ship Node
3PL
Ship Node
Nodes owned by Hub
Enterprise & Seller
Enterprise & Seller
Seller
Carrier
In this scenario, \antra allocates orders to either the 3PL shipping nodes, or directly to the ·endor ship
nodes, as the distribution coníiguration matches items to speciíic shipping nodes and ·endors based on
client requirements.
Unit + - The Participant Nodel
+-19 Yantra Application Administration Yantra Company Confidential
+-19
DrganIzatIons and PoIes
Configuring Organizations and Roles
1. Configure Hub attributes
2. Create Organization(s)
3. Administering Organization associates their
Organizations to Roles
+. Administering Organization configures other
Role attributes by Organization
The Hub is created as part of the
Yantra installation. You can configure
the Hub attributes, but you cannot
create another Hub.
\hen you initially install \antra, an organization called DLlAUL1 is created and assigned the role oí
lub. 1his is the only organization that can play the role oí the lub. \ou can coníigure all attributes
about the DLlAUL1 organization, but you cannot assign another organization to the lub role.
Organizations can own in·entory, shipping nodes, and,or recei·ing nodes. Users are also associated
with an organization.
Unit + - The Participant Nodel
+-20 Yantra Application Administration Yantra Company Confidential
+-20
DrganIzatIon Search
All work within the Participant Nodel
starts with the Organization Search.
1o create a new organization
1. Select the Platíorm · Participant Modeling menu item.
2. Lnter any search criteria, as required.
3. Click Search. A list oí existing organizations matching your search criteria appears in the Search
Results list.
4. Click Create New to create a new organization. Note that períorming the search íirst is not required
ií you are just creating a new organization.
Note
1o modiíy an existing organization, select the organization in the Search Results and click Details.
Unit + - The Participant Nodel
+-21 Yantra Application Administration Yantra Company Confidential
+-21
Create an DrganIzatIon
Click Create New to create
the initial framework for
your new organization.
1o create a new organization
5. Lnter the Organization Code and Organization Name.
6. Ií applicable, enter the DUNS Number and the Account Number with lub.
¯. Select a Locale írom the drop-down list. \ou can use the Create New button next to the drop-down
list ií you need to create another locale.
8. Click Sa·e.
Unit + - The Participant Nodel
+-22 Yantra Application Administration Yantra Company Confidential
+-22
Hub AttrIbutes
The DEFAULT organization is
the only one that can play the
role of the Hub.
1he DLlAUL1 organization is the lub. 1his organization is created as part oí the \antra installation.
DLlAUL1 is also automatically assigned the role oí an Lnterprise. \hether or not you choose to
implement the Participant Model using DLlAUL1 as an Lnterprise depends on your implementation
requirements.
Note
\ou cannot change the Organization Code írom DLlAUL1. \ou can, howe·er, modiíy the
organization name to something more appropriate to your implementation.
Unit + - The Participant Nodel
+-23 Yantra Application Administration Yantra Company Confidential
+-23
DrganIzatIon ConfIguratIon
Primary !nformation
Payment !nformation
Nodes
Roles 8 Participation
Unit + - The Participant Nodel
+-2+ Yantra Application Administration Yantra Company Confidential
+-2+
Drg. 0etaIIs - PrImary Info
Use the Primary !nfo tab to
enter overall information
about the organization.
Once you click on the Sa·e button to create the íramework oí your new organization, the Organization
Details window opens. Use the Primary Info tab to enter iníormation about the tax status, o·erall
attributes, and addresses íor the organization.
Some Specific Attributes
· Administered By - selects the Lnterprise or lub that has responsibility íor coníiguring this
organization. Initially, this deíaults to the lub or Lnterprise creating the new organization. Oíten
this will be the Lnterprise creating a Buyer or Seller in their network. Ií the Buyer or Seller
wants to participate in multiple Lnterprises, the Administered By` selection should be set to
the lub. 1he Administered By` selection controls only which organization can edit the attributes, it
says nothing about the relationships between organizations.
· Distribution Maintained - speciíy whether or not the organization keeps their rules about
distribution and sourcing within \antra`s coníiguration. 1his checkbox is applicable only to Seller
organizations. Ií this box is not checked and distribution rules are coníigured íor the organization
within \antra, those rules will not be used and distribution decisions may be made outside oí
\antra. lowe·er, ií the checkbox is not checked, \antra continues to source to nodes
belonging to the organization ,in which case outside logic íor distribution may not be required,.
· Inventory Maintained - speciíy whether or not the organization keeps their in·entory iníormation
,quantity a·ailable, current supply and demand, etc., within \antra`s applications. Ií this box is not
checked, in·entory supply and demand updates will not happen within \antra íor this organization.
Unit + - The Participant Nodel
+-25 Yantra Application Administration Yantra Company Confidential
+-25
DrganIzatIon ConfIguratIon
Primary !nformation
Payment !nformation
Nodes
Roles 8 Participation
Unit + - The Participant Nodel
+-26 Yantra Application Administration Yantra Company Confidential
+-26
Drg. AttrIbutes - Payment Info
Use the Payment !nfo tab to
configure billing information for
the organization.
Use the Payment Info tab to coníigure billing iníormation íor the organization including:
· 1he account number oí the organization with the lub
· 1he billing address íor the organization
Unit + - The Participant Nodel
+-27 Yantra Application Administration Yantra Company Confidential
+-27
DrganIzatIon ConfIguratIon
Primary !nformation
Payment !nformation
Nodes
Roles 8 Participation
Unit + - The Participant Nodel
+-28 Yantra Application Administration Yantra Company Confidential
+-28
Drg. AttrIbutes - Nodes
Use the Nodes tab to configure
both shipping and receiving nodes.
Depending on the role that has been set up íor the organization you are coníiguring, you may ha·e to
set up corresponding nodes. A node is an entity that either recei·es in·entory ,a recei·ing node, or ships
in·entory ,a shipping node,. A single organization can ha·e shipping nodes, recei·ing nodes, or both.
Ií the organization is a Buyer, you may set up one or more nodes íor recei·ing in·entory. Ií the
organization is a Seller, you may set up one or more nodes íor shipping in·entory. Ií the organization is
a Lnterprise, you may set up one or more nodes that are shipped írom and deli·ered to.
1o create a node
1. On the Organization Details, go to the Nodes tab.
2. Click Create New.
3. Lnter the Node Name and Description, and select a Locale írom the drop-down list.
4. Select the Acti·e checkbox ií you want this node to be an acti·e and a·ailable participant in the
marketplace. Otherwise, lea·e the checkbox blank.
5. Select the Create Purchase Order checkbox ií you need to send a purchase order to the node beíore
the node can execute on íulíillment requests. 1his primarily applies only when the node is
a separate business entity írom the original organization, such as a drop-ship node.
6. Select the appropriate Interíace type íor the node. 1his speciíies by what means oí communication
the node should be notiíied orders. Ií you select L·ents` to represent a third-party system
you must select an action to trigger when an order is allocated to this node. Ií you select Portal` to
represent the node, you can optionally select an action as well.
Unit + - The Participant Nodel
+-29 Yantra Application Administration Yantra Company Confidential
+-29
Create a Node - FInancIaIs
Use the Financials tab to configure
financial information specific to the
node.
1o create a node
¯. Select the Maintain In·entory Cost checkbox ií this node uses \antra`s íunctionality to track and
match in·entory costs to incoming and outgoing items. ,Note: the node can use \antra`s in·entory
costing íunctionality only ií the node is tracking in·entory le·els within \antra.,
8. Lnter the node`s Lxport License and 1ax Payer ID iníormation as needed.
Unit + - The Participant Nodel
+-30 Yantra Application Administration Yantra Company Confidential
+-30
Create a Node - DperatIons
Use the Operations tab to
configure some of the practices in
use at the node.
Setting up a node`s operations is an important way to deíine some oí the practices carried out at the
node. \ou can set up a node to maintain in·entory and,or handle returns. \ou can also determine
whether or not a node has to manually accept ship ad·ices that are sent to it.
1o create a node
9. Select the 1rack In·entory checkbox ií this node uses \antra`s in·entory management íunctionality
to track in·entory supply le·els íor the items kept at this node. Ií this checkbox is not selected, \antra
will always assume that items associated speciíically with node are always a·ailable íor any demand.
\ou can o·erride this checkbox íor a speciíic item at a speciíic ship node.
10. Use the Return Center checkbox to select whether or not this node acts as a return center íor the
organization and its Lnterprises.
11. Select the Generate BOL Number checkbox ií the node generates its own Bill oí Lading numbers.
\ou can also enter starting iníormation to be included on the BOL. Ií the node needs BOL
numbers, and the checkbox is not selected, the BOL number has to be retrie·ed írom an
external interíace with the carrier.
Unit + - The Participant Nodel
+-31 Yantra Application Administration Yantra Company Confidential
+-31
DrganIzatIon ConfIguratIon
Primary !nformation
Payment !nformation
Nodes
Roles 8 Participation
Unit + - The Participant Nodel
+-32 Yantra Application Administration Yantra Company Confidential
+-32
EnterprIse AttrIbutes - PartIcIpants
Participants configure the
relationship between the
Enterprise and other
organizations.
\hen creating a Buyer, Seller, or Carrier, you deíine in which Lnterprises that organization participates
,the procedure to do so is co·ered later in this unit,. Once you designate the organization as
participating in the Lnterprise, the Lnterprise can select the organization írom the Participants list and
coníigure all oí that organization`s attributes. \hen you remo·e an organization írom the Participants
list, you do not delete the organization itselí - just the relationship between the organization and the
Lnterprise.
1o add a participant to an Lnterprise (from Lnterprise Details)
1. On the Organization Details íor the Lnterprise, go to the Roles & Participation tab.
2. Select the Lnterprise Attributes tab. ,Note: ií the Lnterprise Attributes tab does not appear, the
organization does not play the role oí an Lnterprise.,
3. Select the Participants tab.
4. Click lind Organization 1o Participate.
5. Search íor the organization you wish to add to the Lnterprise.
6. Select the organization and click Add Participants 1o Lnterprise.
Note
A Buyer, Seller, or Carrier can still do business with Lnterprises íor which relationships ha·e not been
coníigured. 1he only standard \antra application that uses the iníormation modeled by these participant
relationships is the Order Lntry application. 1his relationship iníormation is also a·ailable to external
or custom applications ·ia \antra`s API set.
Unit + - The Participant Nodel
+-33 Yantra Application Administration Yantra Company Confidential
+-33
EnterprIse AttrIbutes - CarrIers
Carrier Preferences configures
the relationship between the
Enterprise and the Carrier.
1he Carrier Preíerences section oí the Lnterprise Attributes allows you set up a deíault billing account
between the Lnterprise and the Carrier.
1o enter a default carrier billing account
1. On the Organization Details íor the Lnterprise, go to the Roles & Participation tab.
2. Select the Lnterprise Attributes tab. ,Note: ií the Lnterprise Attributes tab does not appear, the
organization does not play the role oí an Lnterprise.,
3. Select the Carrier Preíerences tab.
4. Click Create New.
5. Select the appropriate Carrier írom the Organization Code drop-down list. \ou can use the button
next to the drop-down list to create a new carrier ií needed.
6. Lnter the Billing Account number.
¯. Click Sa·e.
Note
Any carriers created by an Lnterprise will also be a·ailable to participate in other Lnterprises
A Carrier can still do business with Lnterprises íor which preíerences ha·e not been coníigured. 1he
only standard \antra application that uses the iníormation modeled by these preíerences is the Order
Lntry application. 1his iníormation is also a·ailable to external or custom applications ·ia \antra`s API
set.
Unit + - The Participant Nodel
+-3+ Yantra Application Administration Yantra Company Confidential
+-3+
PrImary EnterprIse
The Primary Enterprise designates the
!nventory and Catalog consolidator if using
the Enterprise model for these functions.
Use the Lnterprises section to select which Lnterprises the organization participates in. 1his iníormation
is used to deíine some oí the Coníigurator drop-down selections.
lrom the selected Lnterprises, choose the Primary Lnterprise írom the drop-down list. 1his drop-down
list is populated only with those Lnterprises that the organization participates in. 1he primary enterprise
is used to identiíy the organization`s in·entory and catalog consolidator, ií the implementation uses an
Lnterprise-le·el In·entory Consolidation and Catalog Model.
Selecting the Primary Lnterprise is separate írom selecting the Administering Organization.
Unit + - The Participant Nodel
+-35 Yantra Application Administration Yantra Company Confidential
+-35
SeIIer AttrIbutes - 0IstrIbutIon
Use Seller Distribution to coníigure how this Seller sources particular items and to set up triggers íor
actions based on in·entory a·ailability. \ou can also coníigure distribution rules by selecting the
Applications · In·entory Synchronization · Distribution menu item.
1he Payment Processing Required checkbox determines whether or not the organization is using
\antra`s payment processing íunctionality. 1his applies only to Lnterprises and Sellers.
Ií the checkbox is not selected, then \antra`s applications will not attempt to process any monetary or
payment transactions íor this organization. 1his requires that custom applications períorm those
payment transactions instead using the order and in·entory data stored within \antra. 1his also means
that íor any organization that does not ha·e the checkbox selected:
· \antra does not generate in·oices
· \antra does not require payment authorizations
· \antra does not store payment iníormation in the database, e·en ií that data is
originally passed as part oí the order
· \antra does not track the payment status oí the order
Note
\ou can also access the Distribution Details írom the Applications · In·entory Synchronization menu.
Unit + - The Participant Nodel
+-36 Yantra Application Administration Yantra Company Confidential
+-36
SeIIer AttrIbutes - Payment Types
Configure the Seller's
options for payment
handling.
Seller Payment 1ypes determines how this Seller will process payment authorizations and settlements as
required.
Note
\antra ignores any coníiguration you do íor Seller Payment 1ypes ií the Payment Processing Required`
checkbox is not selected íor the Seller.
Unit + - The Participant Nodel
+-37 Yantra Application Administration Yantra Company Confidential
+-37
SeIIer AttrIbutes - Payment PuIes
Configure how the Seller
authorizes and settles
payments.
Unit + - The Participant Nodel
+-38 Yantra Application Administration Yantra Company Confidential
+-38
SeIIer AttrIbutes - PrIce Programs
Configure how the Seller
determines the price of goods sold.
Use Seller Price Programs to coníigure the rules íor determining the prices íor items sold by this Seller.
See |vit 11 -Pa,vevt Proce..ivg íor more iníormation about price programs.
Unit + - The Participant Nodel
+-39 Yantra Application Administration Yantra Company Confidential
+-39
SeIIer AttrIbutes - PrIce LIsts
Configure how the Seller
determines item pricing.
Use Seller Price Lists to coníigure the rules íor determining the prices íor items sold by this Seller.
See |vit 11 -Pa,vevt Proce..ivg íor more iníormation about price lists.
Unit + - The Participant Nodel
+-+0 Yantra Application Administration Yantra Company Confidential
+-+0
CarrIer AttrIbutes - CommunIcatIon
Configure how Yantra should
communicate with the Carrier's
host server.
Use Carrier Communication to coníigure how \antra should communicate with this Carrier`s host
ser·ers to download iníormation such as tracking numbers and to upload iníormation such as maniíest
details.
Unit + - The Participant Nodel
+-+1 Yantra Application Administration Yantra Company Confidential
+-+1
CarrIers and ServIces
UPS
USPS
FedEx
Ground
Priority
Express
Standard
Next Day Air
Carriers can be linked to many services
Services can be linked to many carriers
UPS is linked to two carrier ser·ices: Ground and Next Day Air.
USPS is linked to two carrier ser·ices: Priority and Standard.
ledLx is linked to three carrier ser·ices: Priority, Lxpress, and Standard. Note that USPS and ledLx
share two carrier ser·ices.
Unit + - The Participant Nodel
+-+2 Yantra Application Administration Yantra Company Confidential
+-+2
CarrIer AttrIbutes - ServIces
Use the same procedure to configure
TL, LTL, and Parcel Services.
Use the 1L, L1L, and Parcel Ser·ices sections to match ser·ices to a Carrier and coníigure the
relationship.
1o configure a Carrier/service relationship
1. On the Organization Details, go to the Roles & Participation tab.
2. Select the Carrier Attributes tab. ,Note: ií the Carrier Attributes tab does not appear, the
organization does not play the role oí a Carrier.,
3. Select the 1L Ser·ices, L1L Ser·ices, or Parcel Ser·ices tab. Note: \ou must know which is the
appropriate tab beíore coníiguring the relationship.
4. Click Create New.
5. Select a Ser·ice Code írom the drop-down list. 1he button next to the drop-down allows you to
search íor the appropriate Ser·ice Code.
6. Lnter a name and description íor this unique Carrier,ser·ice relationship.
¯. Ií appropriate, enter the Llectronic and lost Codes, which are used to deíine LDI interíaces.
8. Select whether this Carrier,ser·ice relationship can be used íor domestic or international shipping. A
single Carrier,ser·ice relationship cannot be used íor both.
9. Click Sa·e.
Unit + - The Participant Nodel
+-+3 Yantra Application Administration Yantra Company Confidential
+-+3
0omestIc vs. InternatIonaI
A Carrierfservice
relationship can be either
Domestic or !nternational
Cannot be used for both
User must know to select
the appropriate Carrierf
service relationship
Can also be selected
automatically via user exit
A domestic shipment is one where both the shipping address ,oí the shipping node, and the Ship 1o
address are in the same country.
An international shipment is one where the shipping address ,oí the shipping node, and the Ship 1o
address are in diííerent countries.
Unit + - The Participant Nodel
+-++ Yantra Application Administration Yantra Company Confidential
+-++
Create a CarrIer ServIce
Create new services as
needed to represent the
Carrier offerings.
\ou can create new ser·ices to match to Carriers as needed.
1o create a new service
1. Select the Applications · Logistics Management · Carrier Ser·ices menu item. 1his opens the
Carrier Ser·ices list.
2. Click Create New.
3. Lnter the Carrier Ser·ice Code and Description.
4. Click Sa·e.
1he new ser·ice is then a·ailable when coníiguring Carrier Attributes íor an organization.
Unit + - The Participant Nodel
+-+5 Yantra Application Administration Yantra Company Confidential
+-+5
Create a CarrIer DrganIzatIon
When you configure a new organization to
play a Carrier role, you should also
configure:
Nanifest prints or Bill of Lading documents
Shipping labels
Use provided templates as a starting point
Create the services required by the new
Carrier
!ntegrate the parcel, TL, or LTL carriers
Details oí how to add new labels and other documents is co·ered in the \antra product documentation
set. \antra pro·ides some templates íor integrating with the íollowing parcel carriers - ledLx, UPS,
and the United States Postal Ser·ice. Regardless oí the carriers used or the type oí carrier ,parcel, 1L, or
L1L,, howe·er, you will ha·e to integrate \antra with the carriers` systems using \antra`s integration
tools and APIs.
Note
Any speciíic implementation may be required to apply íor compliance and,or certiíication írom the
carrier íor the shipping labels, maniíests, and other printed documents required by the carrier.
Unit + - The Participant Nodel
+-+6 Yantra Application Administration Yantra Company Confidential
+-+6
ßusIness PuIes
Business Rules may contain several Rule Sets
Each rule set consists of different configurations of
the same system and application attributes
Rule Set 1
Rule Set 2
Rule Set 3
Enterprise 1
Enterprise 3
Enterprise 2
Enterprise +
Business
Rules
A rule set deíines the choices and business rules that apply to orders, shipments, load, and in·entory
management. \hile each rule set consists oí the same rules, the coníiguration oí each rule can be
completely diííerent in each rule set. 1his means that the lub and each Lnterprise can ha·e a rule set
that applies speciíically to their orders and business needs.
Lach Lnterprise and the lub has a rule set associated with it. 1hat rule set applies to any transactions,
orders, and in·entory owned by that entity ,Lnterprise or lub,.
Note
1he same rule set may be used íor more than one Lnterprise, or you can create a rule set íor each
Lnterprise.
Unit + - The Participant Nodel
+-+7 Yantra Application Administration Yantra Company Confidential
+-+7
VIew ßusIness PuIes
Access all components of the rule
sets from Business Process.
1o view the business rules
1. Select the Platíorm · Business Process· Business Rules menu item.
2. Lxpand the appropriate rule set.
3. 1o ·iew the details oí a particular rule, select the rule and click Details.
Unit + - The Participant Nodel
+-+8 Yantra Application Administration Yantra Company Confidential
+-+8
ActIve PuIe Set
The active rule set, with the highlighted
icon, is the rule set associated with the
current user's organization.
In the list oí rule sets, one rule set is always marked with a highlighted icon. 1his icon indicates the
acti·e` rule set. 1his is the rule set that applies to the organization associated with the current user.
1he acti·e lub rule set applies to any order or other transaction that is not owned by a speciíic
Lnterprise or is owned by the lub. Any rule sets created by a lub user can be ·iewed, and used, by the
Lnterprise. Or the Lnterprise user can create and use their own rule sets. 1he Lnterprise user cannot,
howe·er, modiíy any attributes about the lub rule sets. Ií the Lnterprise user wants to modiíy an
attribute oí a rule set, he must íirst create a new rule set based on one oí the lub rule sets and then
make the desired modiíications.
1o make a rule set active
1. Select the Platíorm · Business Process · Business Rules menu item.
2. Lxpand the My Rule Sets node in the leít pane.
3. In the leít pane, select the name oí the rule set you want to make acti·e íor the user`s organization.
4. Click Acti·ate Rule Set. 1he highlighted icon now appears next to the new acti·e rule set.
Note
Lach Lnterprise and the lub must always ha·e an acti·e rule set, but only one rule set can be
designated as acti·e íor each organization at any time.
Unit + - The Participant Nodel
+-+9 Yantra Application Administration Yantra Company Confidential
+-+9
Create a New PuIe Set
Click Save As. to create a new rule
set based on the selected one.
All new rule sets must be based on an existing rule set. \antra is installed with the Deíault Rule Set to
get you started. 1he Deíault rule set can be customized as needed.
1o add a new rule set
1. Select the Platíorm · Business Process · Business Rules menu item.
2. Lxpand the My Rule Sets node in the leít pane.
3. In the leít pane, select the name oí the rule set on which you want to base the new rule set.
4. Click Sa·e As.
5. Lnter the rule set name and description.
6. Click Sa·e. 1he new rule set now appears in the rule set list in the leít pane.
Unit + - The Participant Nodel
+-50 Yantra Application Administration Yantra Company Confidential
+-50
IntroductIon to the Case Study
DC!
Owner of the Yantra DCN implementation
Distributes network and business machine
components
Buys parts from various suppliers
Light manufacturing to assemble made-to-order
components
Ships to customers
Recently purchased Digital
Printers, Inc (DP!)
Need to integrate DP! into
DC!'s processes
Unit + - The Participant Nodel
+-51 Yantra Application Administration Yantra Company Confidential
+-51
0CI Extended SuppIy ChaIn
DC! Accessories DC! Network
Components
DC! Business
Components
Naxtor !ngram Nicro Flextronics
Epson
Nenlo Logistics Performance
Systems Worldwide
FedEx UPS
USPS
Enterprises
Carriers
Buyers participating in DCI
Enterprise
Sellers participating in
DCI Enterprise
DC!
DC! Hub (DEFAULT)
General Electric
Specialty Naterials
!ngram Nicro
Unit + - The Participant Nodel
+-52 Yantra Application Administration Yantra Company Confidential
+-52
UnIt 4: PevIew
What is the difference between an
organization and a role?
What are the five roles in Yantra's
Participant Nodel?
What is the purpose of assigning roles to
an organization?
What are some of the key role attributes
that must be configured in the Participant
Nodel?
Unit + - The Participant Nodel
+-53 Yantra Application Administration Yantra Company Confidential
+-53