Unit 10- Distributed Order Nanagement

10-1 Yantra Application Administration Yantra Company Confidential

10-1
2002 Yantra Corporation. Proprietary & Confidential.
U
n
i
t

1
0
:
D
i
s
t
r
i
b
u
t
e
d

O
r
d
e
r

M
a
n
a
g
e
m
e
n
t
Unit 10- Distributed Order Nanagement
10-2 Yantra Application Administration Yantra Company Confidential
10-2
Course Agenda
Unit 1 - !ntroduction
Unit 2 - !nfrastructure
Unit 3 - Presentation Framework
Unit + - The Participant Nodel
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 Management
Unit 11 - Payment Processing
Unit 12 - Logistics Nanagement
Unit 13 - Reverse Logistics
Unit 10- Distributed Order Nanagement
10-3 Yantra Application Administration Yantra Company Confidential
10-3
UnIt 10: TopIcs
Order Definitions
Standard Order Fulfillment Process
Negotiation Process
Order Nodifications
Order Nonitor
Unit 10- Distributed Order Nanagement
10-+ Yantra Application Administration Yantra Company Confidential
10-+
UnIt 10: DbjectIves
Define the default order types
Build distribution rules to define which shipping
nodes carry specific items
Configure schedule rules based on business
needs
List the steps in negotiating order fulfillment
on Yantra
Define the steps for controlling order
modifications
Build order monitoring rules
After completing this unit, you should be able to:
Unit 10- Distributed Order Nanagement
10-5 Yantra Application Administration Yantra Company Confidential
10-5
Yantra 0IstrIbuted Drder hgmt
HighIy configurabIe for aII order
types and processes
SaIes, Purchase, Service,
ScheduIes, Forecast / PIanned,
Quotes, RepIenishment
Manage, monitor orders across
inter-enterprise processes
Distributed fuIfiIIment, Merge-in-
transit, MuIti-stage fuIfiIIment,
Configured Products.
MuIti-enterprise order aggregation
and muIti-channeI order capture
GIobaI ATP and ruIes-based sourcing
Order coIIaboration
RoIe-based visibiIity
Manage Order Processes CompIex Commerce Network
SeII /
Buy
Order FuIfiII
DeIiver/
Receive
Service
Unit 10- Distributed Order Nanagement
10-6 Yantra Application Administration Yantra Company Confidential
10-6
Order Nonitor
Standard Order Fulfillment Process
Order Nodifications
0IstrIbuted Drder hanagement
Document Concepts
Document Parts
Creating Documents
Tiered and N Tiered Documents
Creating Tiered Documents
Deal.
Negotiation Process
Unit 10- Distributed Order Nanagement
10-7 Yantra Application Administration Yantra Company Confidential
10-7
What Is a 0ocument!
Document-
A tool used to communicate specifics of a
transaction between two parties
A Yantra system entity that is guided
through a defined process
A term which is typically
synonymous with an order"
in some of the process types
Notes:
Unit 10- Distributed Order Nanagement
10-8 Yantra Application Administration Yantra Company Confidential
10-8
Parts of a 0ocument
Document
Line 1
Document
Header
c
o
n
t
a
in
s
contains
c
o
n
t
a
i
n
s
Line Type
!tem !D
UON
Product Class
Quantity
Status
Pricing
Ship To
!nstructions
Shipping 8 Handling
Document Type
Ship To f Bill To
Driving Date
!nstructions
Shipping 8 Handling
Status
CurrencyfExchange Rate
Document
Line 2
Document
Line 3
In \antra, a document is made up o document lines. All conirmed documents hae a minimum o one
document line. 1he number o document lines is determined by the number o unique Item IDs.
Attributes o each document line include:
line 1ype
Item ID, unit o measure, and quantity
Status
Pricing inormation
Attributes that can be stored at either the document leel ,i they apply to all document lines, or at the
document line leel ,i they apply only to that document line, include:
Ship 1o inormation
Instructions ,such as git wrapping,
Shipping and handling costs
Attributes that only exist at the document header leel include:
Document 1ype
Driing Date
Bill 1o inormation
Unit 10- Distributed Order Nanagement
10-9 Yantra Application Administration Yantra Company Confidential
10-9
CreatIng 0ocuments
Documents can be either:
User initiated- a CSR actively
interacting with an order capture
system
OR
System !nitiated- the system is
configured to recognize that an
order needs to be generated
Most documents are created in \antra ia interaces to other systems, such as a web store ront or order
planning application. 1his interace is done through a call to the appropriate API. 1he API then
automatically creates all the appropriate data records within \antra so that the order and inentory
management process can begin.
Unit 10- Distributed Order Nanagement
10-10 Yantra Application Administration Yantra Company Confidential
10-10
CreatIng InItIaI 0ocuments
Whether User !nitiated or System
!nitiated, each method involves calling a
transaction through an AP! within the
appropriate repository to create the
document.
Unit 10- Distributed Order Nanagement
10-11 Yantra Application Administration Yantra Company Confidential
10-11
CreatIng 0ocuments
!nitial Documents with Order as a
Base Document Type can be
either:
Draft Document
OR
Confirmed Document
Which document gets created
depends upon the transaction
that gets called.
\ou cannot create a Drat Order Document or Shipments or Loads because they do not hae an
Order` Base Document 1ype.
Unit 10- Distributed Order Nanagement
10-12 Yantra Application Administration Yantra Company Confidential
10-12
What Is a 0raft 0ocument!
A Draft Document is:
A Document that is in the process of having its
elements defined (ie the who's, what's,
where's, terms, andfor quantities
may not be firm enough to actually
proceed to the formal confirmation
into an order requiring fulfillment)
An order-like entity known by the
system which can be recalled and
modified as and when necessary
Notes:
A Drat Order Document:
May or may not hae document lines
May or may not hae pricing associated with it
May or may not hae item alidation done
No alidation done against Bill 1o ield
No alidation or completeness o payment inormation
No eect on Book amount in \lS_ClARGL_1RANSAC1ION table
will not hae changes audited
Unit 10- Distributed Order Nanagement
10-13 Yantra Application Administration Yantra Company Confidential
10-13
What Is a ConfIrmed 0ocument!
A Confirmed Document is:
A document that has most of it's elements
defined (ie the who's, what's,
where's, terms, andfor quantities may be firm
enough to actually proceed to the next
processing step)
Requires at minimum
valid Bill To
At least one document line
C
r
e
a
t
e
d
Notes:
Unit 10- Distributed Order Nanagement
10-1+ Yantra Application Administration Yantra Company Confidential
10-1+
TIered Drders
Sales Orders Purchase Orders Return Orders Exchange Orders Sales Orders Service Orders
A Sales Order that
generates a Service
Order
Tiered Order- an order that is created from or as a
result of another order's line(s):
A Sales Order that
generates a Purchase
Order
A Return Order that
generates an Exchange
Order
created automatically based on the definition of a business
process and the status of the parent order
establishes links or relationships between the parent order
and the child order which may require maintenance and
monitoring
kvt kvt kvt kvt
Unit 10- Distributed Order Nanagement
10-15 Yantra Application Administration Yantra Company Confidential
10-15
N-TIered Drders
N Tiered Order- an order which has `N' # of
Tiered orders associated with it thereby requiring
`N' # of relationships to be maintained and
potentially monitored.
kvt kvt kvt kvt
Unit 10- Distributed Order Nanagement
10-16 Yantra Application Administration Yantra Company Confidential
10-16
TIered Drder Types
Tiered Order Types:
Chained Order-
A tiered order is defined as Chained" if
the tiered order must finish it's fulfillment process
before it's parent order can be considered fulfilled.
(example: an order is placed with an enterprise which
then, in turn, creates a purchase order with a dropship
supplier to get the order fulfilled directly to customer.)
Derived Order-
A tiered order is defined as Derived" if the
tiered order does not have to finish it's fulfillment
process before it's parent order can be considered
fulfilled. (example: a Purchase order is created based
on a Planned Order)
kvt kvt kvt kvt
Chained ~ Designed to complete ulilment. Once a chained order is created or a line, all inentory
updates are done only or the parent order
Deried ~ Parent order processes do not depend on this type o order ,or example an exchange
order, or purchase order rom planned order,. Due to this dierence multiple deried orders can
come rom single order lines.
Deried order is used to allow greater lexibility or drop ship suppliers by giing drop ship orders
their own independently conigured worklow. Sales Order is created and then goes into awaiting
chaining status to get a PO created. Once created, the chained order is sent down to the supplier
and ollow it`s own pre-deined process. Statuses are propagated back up to the parent order. Drop
ship status conigured when organization is created so system knows that certain parameters need to
be met when releasing orders or shipment ,such as only shipped i ulilled rom single node and
chained order will be created,.
Lines can be grouped rom arious orders to create one chained order. 1hey need to hae the same
Buyer Org and Lnterprise.
Inentory updates are drien by the Chained order until completion. ,seller org inentory,. 1his
includes generating inoices or example.
Unit 10- Distributed Order Nanagement
10-17 Yantra Application Administration Yantra Company Confidential
10-17
ChaIned Drders
Chained Orders
Used in any process where the child order is
dependent on the parent and where the parent
must know the result of the child order
any order change or order status information is
propagated from the parent to child and child to
parent, respectively
Lines can be grouped from various orders
to create one chained order. They need to
have the same Buyer Org and Enterprise.
kvt kvt kvt kvt
An Order can hae only one chained order per unit in the parent order as chained orders are created
to complete the ulillment o the parent order.
Unit 10- Distributed Order Nanagement
10-18 Yantra Application Administration Yantra Company Confidential
10-18
0erIved Drders
Derived Orders
Used in any process where the child order is
NOT dependent on the parent.
Once the Child Order is created the
parent and child are processed
independently. However, the relationship
between the two is maintained.
By default, derived orders do not propagate
order or status information from a child to a
parent but can be configured to do so
kvt kvt kvt kvt
Deried ~ Parent order processes do not depend on this type o order ,or example an exchange order,
or ulilment order rom planned order,. Due to this dierence multiple deried orders can come rom
single order lines. 1ypically, the lie cycle o parent order is already oer by the time a deried order is
created out o it.
Lines can be grouped rom arious orders to create one deried order. 1hey need to hae the same
Buyer Org and Lnterprise.
Unit 10- Distributed Order Nanagement
10-19 Yantra Application Administration Yantra Company Confidential
10-19
Parts of a TIered 0ocument
Document
Header
c
o
n
ta
in
s
contains
c
o
n
t
a
i
n
s
Document
Line 2
Document
Line 3
Document
Header Document
Line 1
Parent Header
Parent Line
Child Header 1
contains
Child Line
Document
Header Document
Line 1
Child Header 2
contains
Child Line
Document
Line 1
Unit 10- Distributed Order Nanagement
10-20 Yantra Application Administration Yantra Company Confidential
10-20
CreatIng TIered 0ocuments
Chained Document Creation
Can be set as a selling organization level attribute
Can be set as part of a greater business process
Derived Document Creation
set as part of a business process using either:
Push Nodel
Pull Nodel
Unit 10- Distributed Order Nanagement
10-21 Yantra Application Administration Yantra Company Confidential
10-21
ChaIned Drder CreatIon by PoIe
!f an Organization requires a Chained Order
to be created when they are selected as the
selling organization, the Requires Chained
Order option must be checked for that
Organization. The lines requiring chaining
can either be added to an existing chained
order or created as a new chained order.
kvt kvt kvt kvt
User Lxits:
determineChainedOrderlorConsolidation
lor each order, the lines can either be added to an existing chained order or created as a new chained
order. By deault a new order is created.
beoreOrderCreate
Used to update cost and billing parameters or the chained order.
Unit 10- Distributed Order Nanagement
10-22 Yantra Application Administration Yantra Company Confidential
10-22
ChaIned Drder CreatIon by Process
kvt kvt kvt kvt
!n this example, when the Chained Order Create
transaction is invoked, the system knows to create a
new chained order in the form of a Purchase Order
Document. Additional transactions and document
types can be configured and linked appropriately to
support unique business processes.
Place configured transactions where required in the pipeline or
make them available as an action through the user interface.
Configure Listeners for status propagation.
Purchase Order, by deault, is set up as the chained order document type or the Sales Order.
Deault 1emplates Control:
Inormation Carried orward rom Parent leader to Chained leader
ChainedOrderDocument1ype1emplate Coniguration
Inormation Carried orward rom Parent Lines to Chained Lines
ChainedOrderDeault1emplate
Consolidation o Parent Lines to Chained Lines
ChainedOrderConsolidation1emplate
ChainedOrderDeault 1emplate is chosen based on the coniguration or the Document 1ype o
the parent order
\hich Chained Order 1emplate Document 1ype ,0004, is chosen is based on the conigurations
or the Chained Order`s Buyer ,the Sales Order`s Seller,, Lnterprise, Seller ,the Drop Ship Supplier,
combination or the Chained Order document type.
ChainedOrderConsolidation 1emplate allows grouping based on Order Line Attributes. 1here is a
user exit built in to the system which allows or adding new order lines to existing chained orders
Unit 10- Distributed Order Nanagement
10-23 Yantra Application Administration Yantra Company Confidential
10-23
0erIved Drder CreatIon by Process
kvt kvt kvt kvt
!n this example, when the !nclude !n Return transaction is
invoked, the system knows to create a new derived order in
the form of a Return Order Document.
Place configured transactions where required in the
pipeline or make them available as an action through
the user interface. Configure listeners for status
propagation.
Return Order Document, by deault, is set up as the deried order document type or the Include
In Return transaction.
Unit 10- Distributed Order Nanagement
10-2+ Yantra Application Administration Yantra Company Confidential
10-2+
0erIved Drder CreatIon
Creating Derived Orders-Push Model
Example: an exchange order being derived from
a return order
The Parent Order's Pipeline's (ie.Reverse Logistics
Pipeline) CREATE_DERIVED_ORDER transaction uses the
appropriate instance of CREATE_ORDER transaction of the
Derived Order's Pipeline (ie. Order Fulfillment Pipeline) to
create the new derived order.
Create_ Derived_Order
Create_Order
Parent Pipeline
Derived Order's Pipeline
Only speciic statuses are conigured in the parent pipeline to be aailable or deriing an
order.
Unit 10- Distributed Order Nanagement
10-25 Yantra Application Administration Yantra Company Confidential
10-25
0erIved Drder CreatIon
Creating Derived Orders-Pull Model
Example: a return order being derived from a
shipped sales order
The Deriving Order Pipeline's (ie.Reverse Logistics
Pipeline) CREATE_ORDER transaction uses the appropriate
instance of INCLUDE_IN_DERIVED_ORDER transaction
of the parent order's pipeline (ie. Order Fulfillment Pipeline)
to move quantities from the parent order to the new derived
order.
Create_ Order
Include_in_Derived_Order
Deriving Pipeline
Parent Pipeline
Only speciic statuses are conigured in the parent pipeline to be aailable or deriing an
order.
Unit 10- Distributed Order Nanagement
10-26 Yantra Application Administration Yantra Company Confidential
10-26
Standard Order Fulfillment Process
Order Fulfillment Pipeline
Special Order Statuses
Schedule and Release Transactions
Distribution Rules and Schedule Rules
Node Determination
Order Nonitor
Order Nodifications
0IstrIbuted Drder hanagement
Documents
Negotiation Process
Order
N
o
d
e
1
Node 2
Unit 10- Distributed Order Nanagement
10-27 Yantra Application Administration Yantra Company Confidential
10-27
SaIes Drder 0ocument Type
Sales Order-
Used in the Order Fulfillment process type
Used to support a transaction between a
buyer and seller as primary participants
Order is tracked and viewed in Yantra with
the Seller as the primary participant.
Notes:
Unit 10- Distributed Order Nanagement
10-28 Yantra Application Administration Yantra Company Confidential
10-28
Drder FuIfIIIment Process Type
Confirm
Draft
Order
Schedule
Order
Created
Send
Release
Start
Negotiation -
Order
Receive
Negotiation -
Order
Ready To
Negotiate
ReIease
Being
Negotiated
ReIeased
ReIease
Accepted
Portal
node?
Create
Draft
Order
Draft Order Created
Create
Order
Created
Reserved
Release
Order
ScheduIed
This pipeline focuses on the
creation and movement of
the Sales Order document
type through it's respective
process.
Deal.
Unit 10- Distributed Order Nanagement
10-29 Yantra Application Administration Yantra Company Confidential
10-29
3. Yantra creates order;
order is now visible to
users at the Hub and
Enterprise levels
CreatIng SaIes Drders
Front End Application
ServerfYantra Console
1. Buyer places order via front
end applicationfConsole
Yantra
Application
Server
Create
Order
AP!
2. Front end calls AP! on
Yantra application
server
Create
Draft Order
AP!
OR
Unit 10- Distributed Order Nanagement
10-30 Yantra Application Administration Yantra Company Confidential
10-30
Yantra Drder Entry
Fill Quantity
Unit 10- Distributed Order Nanagement
10-31 Yantra Application Administration Yantra Company Confidential
10-31
Yantra DE addIng IInes
Unit 10- Distributed Order Nanagement
10-32 Yantra Application Administration Yantra Company Confidential
10-32
Yantra DE addIng IInes
Unit 10- Distributed Order Nanagement
10-33 Yantra Application Administration Yantra Company Confidential
10-33
Yantra DE-addIng order attrIbutes
Unit 10- Distributed Order Nanagement
10-3+ Yantra Application Administration Yantra Company Confidential
10-3+
Yantra DE- addIng InstructIons
Unit 10- Distributed Order Nanagement
10-35 Yantra Application Administration Yantra Company Confidential
10-35
Yantra DE-addIng Notes
Unit 10- Distributed Order Nanagement
10-36 Yantra Application Administration Yantra Company Confidential
10-36
Yantra DE-LIne Item 0ependency
Line Item Dependency
Ship-together
Deliver-together
Unit 10- Distributed Order Nanagement
10-37 Yantra Application Administration Yantra Company Confidential
10-37
Yantra DE-0ynamIc Dh 0efInItIon
Unit 10- Distributed Order Nanagement
10-38 Yantra Application Administration Yantra Company Confidential
10-38
Drder FuIfIIIment Statuses
Once created, a document and its associated
document lines will pass through many statuses
available within its process type.
Remember that the order leel status is always a summary o the indiidual order line statuses.
Unit 10- Distributed Order Nanagement
10-39 Yantra Application Administration Yantra Company Confidential
10-39
SpecIaI 0ocument LeveI Statuses
Status
'Partially' Summary document status seen
on Console when individual lines
are in different statuses
Held Document status represented
Console by lock icon
Remember that the order leel status is always a summary o the indiidual order line statuses.
Unit 10- Distributed Order Nanagement
10-+0 Yantra Application Administration Yantra Company Confidential
10-+0
'PartIaIIy' Status
!f multiple document lines are in different
statuses
Appears at document level on console
Document line
1 status =
Sent To Node
Document line
2 status =
Shipped
Document status
= Partially
Shipped
I an order has multiple order lines in dierent statuses, then the order status ,which is a summary o
order line statuses, will be Partially` in a status. 1he status that appears ater Partially` at the order leel
is the status o the order line that has progressed urthest in the order ulillment process.
Lxample
An order has two order lines. One order line has a status o Sent 1o Node and the other order line has a
status o Shipped. Because the Shipped order line is the one that has progressed urthest in the
ulillment process, the order status shows Partially Shipped on the console.
1his could happen i the order was split among two ship nodes. One o these ship nodes had already
shipped their order release, but the other ship node has not yet een picked up the ship adice
notiication.
Unit 10- Distributed Order Nanagement
10-+1 Yantra Application Administration Yantra Company Confidential
10-+1
HeId 0ocument Status - ExampIe
Document stays at current status until Hold is
released
Document shows usual status on Console with
addition of the `Lock' icon
Example:
Order is Created but credit card is returned
unauthorized
Place order in Held status for further verification
Does not continue in fulfillment process until Hold is released
after resolution of problem
Order console shows order status as Reserved, but with a
lock" icon
Unit 10- Distributed Order Nanagement
10-+2 Yantra Application Administration Yantra Company Confidential
10-+2
ScheduIe TransactIon
The program that schedules and soft
allocates order line(s) to specific shipping
node(s) based on the defined driving date for
an order.
Typically follows the Order Create transaction
Schedule
Scheduled (1500)
Backordered (1300)
Awaiting Chained Order Creation (1600)
Release
Released
kvt kvt kvt kvt
Schedule - Schedule is run immediately ater order create. 1he transaction uses schedule rule, line-item
dependencies and drie dates ,deliery or ship dates,. Order lines can be scheduled to internal Ship
nodes or external Ship Nodes ,creates chained order, or external organization ,certain criteria hae to be
met or this to occur,. 1he Schedule process is reersible. It is designed to support looking ahead or
inentory. Orders can be put into automated scheduling process which submits them to scheduling at a
speciied date. At coniguration, an enterprise speciies scheduling days, and any orders that all within
that period when the scheduler runs will be scheduled. I an order is sourced rom an external node, the
order is automatically chained. such that all lead times etc are calculated by the speciied drier date.
Outcomes o Schedule:
Scheduled ,1500, - I line can be scheduled
Backordered ,1300, - I line cannot be scheduled
Awaiting Chained Order Creation ,1600, - I line is scheduled to ship rom an organization requiring
chained order creation
Driing Date is either the required ship date ,the date on which the order needs to leae the node, or
the required Deliery date ,the date on which the order needs to arrie to the ship to address, At a
document leel you are able to speciy what the driing date or the document is such that all lead times
etc. are calculated drien o o the appropriate date.
Unit 10- Distributed Order Nanagement
10-+3 Yantra Application Administration Yantra Company Confidential
10-+3
ScheduIe and PeIease Programs
You can run the Schedule or Release
program through the U! or you can schedule
them to run periodically.
Unit 10- Distributed Order Nanagement
10-++ Yantra Application Administration Yantra Company Confidential
10-++
ScheduIe TransactIon
Order
200-123
000-909
200-+23
Order
Schedule
Order
Schedule
1
000-909
+
200-+23
2
200-123
DC!-Reno
DC!-Rose
Order
Lines
Order Schedule
Lines
Once \antra has determined which ship nodes,organizations ulill which order lines, ia the Schedule
program. \hen the Release transaction is executed, the order is broken up into Order Releases. 1here
is one order release or eery ship node,organization used to ulill the order lines. Lach Order Release
is assigned a 4 which a supplier uses as a reerence or his portion o the ulillment obligation.
In each order release, there is one Order Release Line or each order line assigned to the ship node.
Generally, there are an equal number o order lines and order release lines, and there will neer be ewer
order release lines than order lines.
1he order release and order release line contain the same inormation aailable in the order and order
lines, with the addition o ship node, organization inormation.
Unit 10- Distributed Order Nanagement
10-+5 Yantra Application Administration Yantra Company Confidential
10-+5
SeIIers and ShIppIng DptIons
Hub
{default)
DCI DCI-ACC DCI-BusComp
DCI-Reno
DCI-Rose
DCI-Sing
200-123 (1)
200-523 (1)
000-909 (2)
300-991 (+)
200-123 (2)
000-909 (3)
000-999 (3)
Organization
keeping
Inventory
External to
Yantra
000-909
000-999
Associate each shipping node,organization with items. Use priorities to decide the shipping
node,organization to use or ulillment i multiple entities can supply the same item.
\antra assigns an order release to the shipping node with the lower priority ,which is the higher
number, only i the irst shipping node,organization is out o stock or is otherwise unable to ulill the
order release.
Use an ALL` sourcing rule as a catch-all so that \antra knows how to source or items not explicitly
deined in the other sourcing rules. An ALL` sourcing rule will direct any item not speciied by a higher
priority sourcing rule to a speciic ship node.,organization.
Unit 10- Distributed Order Nanagement
10-+6 Yantra Application Administration Yantra Company Confidential
10-+6
Node SeIectIon
Distribution Rules and Schedule Rules work
together with a defined driving date to determine
which ship nodesforganizations will fulfill which
orders
weighting attributes can be assigned to distribution
and geography parameters to determine their
relative importance
Geography (optional)
Schedule Rules
Distribution Rules
Choose to completely oerride Console`s internal logic or ship node determination by using one o the
user exits to determine the appropriate ship node external to \antra.
Unit 10- Distributed Order Nanagement
10-+7 Yantra Application Administration Yantra Company Confidential
10-+7
What are 0IstrIbutIon PuIes!
Distribution rules are:
Nappings of items to one or more ship
nodesforganizations
Defined at an Organization Level
An order line attribute
A method of controlling the view to ATP
Unit 10- Distributed Order Nanagement
10-+8 Yantra Application Administration Yantra Company Confidential
10-+8
0IstrIbutIon PuIe
Distribution Rule
An Organization can:
create multiple distribution rules and look up
inventory based on any of these rules.
include other organizations which keep
inventory external to Yantra in your distribution
rules.
specify the effective date range for a
distribution rule line to aid in gauging applicability
against driving date.
specify distribution rule at line level. Used to
determine ship nodefsource from organization at
schedule time. Can set a default.
pz pz pz pz
orderCreate API support s
A Distribution Rule ID to be passed at line leel.
I it is not passed then it becomes deaulted rom Seller organization`s
Deault_Distribution_Rule_ID
getDistributionSetup API supports:
Optional Parameters:
Distribution Rule ID
llag - Look across all nodes
Unit 10- Distributed Order Nanagement
10-+9 Yantra Application Administration Yantra Company Confidential
10-+9
SpecIfy a 0IstrIbutIon Strategy
Use the Distribution Naintained checkbox
when configuring an Organization to specify
whether or not it uses Yantra's distribution
strategy for node selection.
Unit 10- Distributed Order Nanagement
10-50 Yantra Application Administration Yantra Company Confidential
10-50
Create a 0IstrIbutIon PuIe
Select the Organization you want
to build Distribution Rules for and
on the Seller Attributes tab, click
the Create New button.
1o create a new Distribution rule
1. Select Distribution rom the Inentory Management menu.
2. Create a Distribution rule by choosing Create New Rule. 1he Distribution Details window displays.
3. Conigure the Setup Selection to apply this rule to all items at the Ship Node or just a selected item at
the Ship Node.
4. Lnter an Item ID, Lectie dates, Ship Node, and Priority.
5. Lnter the Item Name at Ship Node based on what the supplier`s name or the item is.
6. Choose Sae.
Unit 10- Distributed Order Nanagement
10-51 Yantra Application Administration Yantra Company Confidential
10-51
0IstrIbutIon PuIe Set-up
Nultiple Distribution
Rules
Specify
Effective
Dates
!nclude other organizations
keeping inventory external
to Yantra.
Unit 10- Distributed Order Nanagement
10-52 Yantra Application Administration Yantra Company Confidential
10-52
Create an ALL 0IstrIbutIon PuIe
Use the ALL Distribution Rule as
a `catch-all' so that Console can
fulfill any order line.
Use the ALL` sourcing rule as a catch-all so that \antra knows how to source or items not explicitly
deined in the other sourcing rules. An ALL` sourcing rule will direct any item not speciied by a higher
priority sourcing rule to a speciic ship node.
Unit 10- Distributed Order Nanagement
10-53 Yantra Application Administration Yantra Company Confidential
10-53
What Is a ScheduIe PuIe!
Determines to which shipping node or
organization an order is assigned based on
Order Driving date, lead time, and optimization
considerations
How tofwhether to split orders
What to do if inventory is not fully available
Configured in the !nventory rule set
Should have one default rule in each rule set
Schedule Rule is an order header attribute
Each order for an Enterprise can have a different
assigned rule
1he Schedule 1ransaction uses Schedule Rules when it runs to schedule inentory or orders. \ou can
hae one schedule or all orders or associate a speciic Schedule Rule with an order. 1his allows the
lexibility o haing dierent schedule rules based on dierent requirements.
Schedule Rules are part o the rule sets associated to an Lnterprise, so each Lnterprise can hae multiple
schedule rules that are unique to that Lnterprise. Schedule Rule is an order leel attribute, so each order
with a dierent Schedule Rule could hae dierent settings or each o these ields. In the end, the
shipping node,organization with the lowest 4 priority setting ,highest business priority, is selected to
ulill an order.
Unit 10- Distributed Order Nanagement
10-5+ Yantra Application Administration Yantra Company Confidential
10-5+
AssIgn ScheduIe PuIe
Three means of assigning a
schedule rule to an order:
1. Schedule rule is passed as
part of order data when
creating order
2. Planner selects
schedule rule through
Console
Order
3. !f Schedule rule is not
assigned by other means,
Console uses the default
SYSTEN Schedule rule
Unit 10- Distributed Order Nanagement
10-55 Yantra Application Administration Yantra Company Confidential
10-55
ScheduIe PuIe-WeIghtIngs
Specify whether or not to use geography when determining the
ship node for an order. Assign weightings to Distribution Rules
against geography when considering the list of eligible ship
nodes.
Use Geography - I checked, \antra uses geographical location to re-sort the list o ship
nodes,organizations. I not checked, the list o ship nodes,organizations is prioritized solely based on
the Distribution Rules coniguration. \antra uses the weightings only i this box is checked.
Note
Setting Distribution Priority to 0` implies the use o just geography to determine a ship node. I using
only Distribution Rules, and not geography, uncheck the Use Geography checkbox.
Unit 10- Distributed Order Nanagement
10-56 Yantra Application Administration Yantra Company Confidential
10-56
ScheduIe by Ceography ExampIes
Harness Ship node:
- Priority= 1 in Distribution Rules
- 2000 miles from customer
Arc Equipment Ship node:
- Priority= 2 in Distribution Rules
- 1000 miles from customer
Buyer places order for one WAN switch:
Example 1:
Weightings in Schedule Rule: Distribution = 2000 , Geography = 1
{Src) 1 * 2000 = 2000
{Geo) 2000 * 1 = 2000
4000
{Src) 2 * 2000 = 4000
{Geo) 1000 * 1 = 1000
5000
Example 2:
Change Weightings in Schedule Rule to Distribution = 500 , Geography = 1
{Src) 1 * 500 = 500
{Geo) 2000 * 1 = 2000
2500
{Src) 2 * 500 = 1000
{Geo) 1000 * 1 = 1000
2000
Harness gets the order
Arc gets the order
Note
\antra determines the geographical distance between two points by using a zip code table in the
database that maps each zip code or postal code to a latitude and longitude. Scripts are proided with
the \antra installation to populate this table.
Unit 10- Distributed Order Nanagement
10-57 Yantra Application Administration Yantra Company Confidential
10-57
ScheduIe PuIe -Lead TImes
Schedule Lead Time parameter
defines the # of days before driving
date the scheduler should pick up
orders for processing.
Allowed Shipment Delay parameter
defines the # of days a line can be
delayed automatically if it cannot
be scheduled to meet the specified
driving date.
Unit 10- Distributed Order Nanagement
10-58 Yantra Application Administration Yantra Company Confidential
10-58
ScheduIe PuIe-DptImIzatIon
Select an appropriate optimization
method for the Schedule Transaction
to use when determining options for
fulfillment.
Unit 10- Distributed Order Nanagement
10-59 Yantra Application Administration Yantra Company Confidential
10-59
ScheduIe PuIe-Preferences
Specify scheduling preferences for an order when determining
the ship node such as whether all inventory for an order must be
available in order to process the shipment and what to do in the
case of inventory shortage.
Determine Ship Node Lxternally - I checked, \antra compiles the prioritized list o all appropriate
ship nodes,organizations and passes this inormation to an external system ia a user exit. \antra
expects the external system to pass back the name o the ship node,organization that should be
assigned to the order. I not checked, \antra will determine which ship node should be assigned to each
order.
Reprocess for Backorder - Indicates a decimal period in days, ater which backorders are reprocessed
by the schedule background program.
Unit 10- Distributed Order Nanagement
10-60 Yantra Application Administration Yantra Company Confidential
10-60
Inventory Shortage
Backorders vS Cancels
Backorders
!nventory is not available either at
schedule time or at outbound fulfillment
time
Order is reprocessed when inventory is
available
Cancels
Order is not picked up for fulfillment
A Node user cannot cancel an order
Backorders
\hen inentory is aailable, a backordered order is picked up at the Schedule stage and goes through
the order ulillment process rom there.
Cancels
Orders are cancelled or the ollowing reasons, among many others:
Customer request
Item is discontinued
Account is raudulent
Unit 10- Distributed Order Nanagement
10-61 Yantra Application Administration Yantra Company Confidential
10-61
ackorders vs. CanceIs
You can backorder at these levels:
Order Line
Order Release
Order Release Line
You can cancel at these levels:
Order
Order Line
Order Release
Order Release Line
\ou backorder:
At the Order Line leel i the line is backordered beore it is sent to a ship node
At the Order Release leel i you backorder an entire order release ater it is sent to a ship node
At the Order Release Line leel i you backorder just part o an order release ater it is sent to a ship
node
\ou cancel:
At the Order leel i the entire order is cancelled beore it is sent to a ship node
At the Order Line leel i an indiidual line is cancelled beore it is sent to a ship node
At the Order Release leel i you cancel an entire order release ater it is sent to a ship node
At the Order Release Line leel i you cancel just part o an order release ater it is sent to a ship node
Unit 10- Distributed Order Nanagement
10-62 Yantra Application Administration Yantra Company Confidential
10-62
CanceIs and ackorders
CancelJbackorder Also cancelsJbackorders
this level these levels
Order (cancel only) Order Line(s), Order Schedule Lines,
Order Release(s), Order Release
Line(s)
Order Line Corresponding Order Schedule Lines,
Release(s) and Order Release Line(s)
Order Release Order Release Line(s) and
component Order Line(s)
Order Release Line Component Order Line(s)
1he backorder process is not appropriate at the order leel because backordering applies only to
indiidual item IDs, not to an order header.
Generally modiications and cancellations are not perormed post order release as the communication
o such an eent to a node requires extremely tight integrations to be sure that the backordering or
cancellation is executed by the node.
Unit 10- Distributed Order Nanagement
10-63 Yantra Application Administration Yantra Company Confidential
10-63
ScheduIe PuIe
Ship
Complete?
Order is Scheduled only if all lines can
be fulfilled currently
Order lines that can be fulfilled are
Scheduled even if other lines can't be
fulfilled currently
checked
not
checked
Line Ship
Complete?
Order line is Scheduled only if the
entire line can be fulfilled currently
Order line is Scheduled even if inventory
is available only for partial fulfillment
checked
not
checked
I Ship Complete is checked, you do not need to check Line Ship Complete. Checking Ship Complete
implicitly includes Line Ship Complete.
Note
1hese options do not determine how the order is diided across ship nodes. \antra considers the pool
o inentory across all ship nodes when determining i these constraints can be met.
Unit 10- Distributed Order Nanagement
10-6+ Yantra Application Administration Yantra Company Confidential
10-6+
ScheduIe PuIe
Ship from
Single
Node?
Order is Scheduled only if all lines are
currently available at a single ship
node
Order lines that can be fulfilled are
Scheduled even if other lines can't be
fulfilled currently; the order can be split
across ship nodes
checked
not
checked
Line Ship
from Single
Node?
Order line is Scheduled only if the
entire line is currently available at a
single ship node
Order line is Scheduled even if inventory
is available only for partial fulfillment;
the line can be split across ship nodes
checked
not
checked
Checking Ship rom Single Node implicitly includes Ship Complete. Checking Line Ship rom Single
Node implicitly includes Line Ship Complete.
Note
I Ship rom Single Node is checked and Line Ship rom Single Node is not checked, schedule does not
honor Ship rom Single Node. Lines can then be shipped rom dierent ship nodes. So, i you want to
Ship rom Single Node, you must also check Line Ship rom Single Node.
Unit 10- Distributed Order Nanagement
10-65 Yantra Application Administration Yantra Company Confidential
10-65
ScheduIe PuIe
Cancel
Order for
!nventory
Shortage?
!f inventory is not available, cancel the
order
!f inventory is not available, backorder
the order
checked
not
checked
Unit 10- Distributed Order Nanagement
10-66 Yantra Application Administration Yantra Company Confidential
10-66
0efauIt ScheduIe PuIe
The SYSTEN rule is always the default
schedule rule. The properties of this
rule can be modified.
1o modify the default Schedule Rule
1. Select the Platorm Process Modeling Business Rules menu item.
2. Open the appropriate rule set and select Order lulillment 1ransactions.
3. Click Details.
4. Go to the Schedule tab.
5. Select the S\S1LM Schedule rule.
6. Click Details.
. Modiy any o the attributes as appropriate.
8. Click Sae in the Schedule Rule Details window.
9. Click Sae in the 1ransaction Rules window.
1o add another Schedule rule, just click Add New Rule in the search results list.
Note
1he Schedule Rule name is what needs to be passed as part o create order data i you wish to use an
alternate Schedule Rule.
Unit 10- Distributed Order Nanagement
10-67 Yantra Application Administration Yantra Company Confidential
10-67
0etermIne ShIp Nodes
1. Based on item availability create a
list of options defining ship
nodesforganizations that can
fulfill the order.
2. Define geographical location and
check weighting of Distribution
vs. Geographical priority from
schedule rule
Geographical distance based
between Ship Node or Org to Ship
To addresses
1he initial list includes all ship nodes that currently hae the items in stock and is based on the
distribution rules ,the distribution strategy,.
Using geographical location as a actor is optional. Choose to sort this list o ship nodes solely based on
Distribution Rule priority instead.
1he geographical location is based on longitude,latitude associated with zip codes. Console includes a
set o standard zip codes and longitude,latitude associations, in the orm o a database script, that can
be used to determine ship nodes all, or in part, by geography.
Unit 10- Distributed Order Nanagement
10-68 Yantra Application Administration Yantra Company Confidential
10-68
0etermIne ShIp Nodes
3. Apply other Schedule Rule
constraints to find first
appropriate ship node
Applied at a Ship To level
!f using geography
Nust all inventory be available
immediately?
Can order be split across multiple
ship nodes?
Optimize on Date? Shipments?
Line !tem Dependencies, Fill Qty
I using geographical location as a actor, all order lines are grouped together by the Ship 1o address.
\ithin these Ship 1o groupings, the additional Schedule Rule constraints are applied.
Unit 10- Distributed Order Nanagement
10-69 Yantra Application Administration Yantra Company Confidential
10-69
PeIease TransactIon
The program that hard allocates inventory
from and sends notification to the node.
Noves demand from scheduled to allocated
Release -creates releases, and sends order releases to
the node
Schedule
Scheduled (1500)
Backordered (1300)
Awaiting Chained Order Creation (1600)
Release
Released
kvt kvt kvt kvt
Release - Release is run much nearer to the actual ship date. 1he actual date is conigured at set up
,usually x amount o days beore driing date,. Inentory is checked again and demand is moed rom
scheduled to allocated. A scheduled eent is triggered which notiies the ship node o the impending
shipment. lill percentage and release date are both considered at this point. \ou can also ask the system
to run possible scenarios o release.
Driing Date is either the required ship date ,the date on which the order needs to leae the node, or
the required Deliery date ,the date on which the order needs to arrie to the ship to address, At a
document leel you are able to speciy what the driing date or the document is such that all lead times
etc. are calculated drien o o the appropriate date.
Unit 10- Distributed Order Nanagement
10-70 Yantra Application Administration Yantra Company Confidential
10-70
Types of NotIfIcatIons
Yantra
Application
Console
WNS
3
rd
Party
System
Records directly written to Yantra
database tables so that orders are
available to appropriate Console
users.
Release background program
processes orders for WNS ship nodes
and creates appropriate order data in
WNS interface tables.
Order Releases sent according to
Action associated with ship node in
the ship node configuration.
Unit 10- Distributed Order Nanagement
10-71 Yantra Application Administration Yantra Company Confidential
10-71
ShIp AdvIce Interface - PevIew
Use the !nterface section of the node
details to specify how Yantra should send
Ship Advices to this node.
Note
I you select the Lents` interace or a 3
rd
party ship node system, then you must also select an Action
rom the Action Name drop-down list. 1he action ,conigured in the 1ransactions console, tells \antra
how to communicate with the 3
rd
party system ,email, ax, LDI, etc., at the ship node.
See |vit - Proce.. Defivitiov or inormation about creating actions.
Unit 10- Distributed Order Nanagement
10-72 Yantra Application Administration Yantra Company Confidential
10-72
Drder Process - ConsoIe Node
Console
node?
Download
Release
Sent To
Node
Pack
Being
Picked
Confirm
Shipment
Packed
Unit 10- Distributed Order Nanagement
10-73 Yantra Application Administration Yantra Company Confidential
10-73
ShIp ConfIrm from WhS or 3
rd
Party
Ship Confirm
program
WNS
!nterface
Tables
3
rd
Party
System
Yantra
5x
!mport
Tables
WNS
Once \MS has shipped an order, the shipment details are written to the \MS interace tables. Once a
3
rd
party system has shipped a \antra 5x order, the shipment details are written to the \antra5x import
tables. A Ship Conirm background program reads the data and creates the appropriate shipment
records in the \antra database.
Note
1here are two Ship Conirm background programs - one to read the \MS interace tables and another
to process records in the \antra import tables or 3
rd
party system records.
Unit 10- Distributed Order Nanagement
10-7+ Yantra Application Administration Yantra Company Confidential
10-7+
Standard Order Fulfillment Process
Order Nonitor
Order Nodifications
0IstrIbuted Drder hanagement
Document Definitions
Negotiation
Process Definition
Negotiation Pipeline
Negotiation Nonitor
Unit 10- Distributed Order Nanagement
10-75 Yantra Application Administration Yantra Company Confidential
10-75
Drder NegotIatIon Process
1. Business Process dictates
WHEN a negotiation is
required.
2. Seller reviews the order. !f the
Seller cannot fulfill the order, it is
rejected with suggested changes
Order
3. Review and renegotiate
the order by changing the
price, dates, or
quantity.
Order
Order
+. Seller reviews the modified
order and negotiation
history
Note
Sellers can break a line up to propose multiple dierent shipme nts ,additional quantity,ship date`
combinations,.
Unit 10- Distributed Order Nanagement
10-76 Yantra Application Administration Yantra Company Confidential
10-76
How Is NegotIatIon Supported!
Process type allowing participants to
negotiate on the details of a transaction
Operates on a document level
Can be used by any
process type at any point
in its process
Two possible process
outcomes
Acceptance
Rejection
1he order contains all inormation about all items, the Buyer, payments, etc.
1he release is the part o an order designated or ulillment at a speciic shipping node.
Unit 10- Distributed Order Nanagement
10-77 Yantra Application Administration Yantra Company Confidential
10-77
UsIng the NegotIatIon PIpeIInes
Order Fulfillment
Pipeline
Order Fulfillment
Pipeline continued
Negotiation Pipeline
Use the Negotiation pipeline by
stepping out of and then back
into the originating pipeline.
Add the Start Negotiation,Receie Negotiation transactions at any point in the pipeline
Receie Negotiation directly ollows Start Negotiation in the originating pipeline
Aailable at Order leels
Receie Negotiation has three possible output statuses to eed back to the originating pipeline:
Accepted
Backordered
Cancelled
Unit 10- Distributed Order Nanagement
10-78 Yantra Application Administration Yantra Company Confidential
10-78
NegotIatIon Process 0efInItIon
Any transaction can start the
negotiation process.
1. 1he Start Negotiation transaction is called.
2. A separate process starts which creates the negotiation with parameters and data speciic to the
originating transaction and document type.
3. Oers and counter-oers go back and orth between the Initiator and the Negotiator.
4. 1he participants reach an outcome ,accept or reject, or the negotiation.
5. 1he outcome is relayed back to the original document, along with any modiied data ,new price,
quantity, etc.,, ia the Receie Negotiation transaction.
6. \orklow continues based on the negotiation outcome. Note: Once the Start Negotiation
transaction is called, the worklow will not continue until an outcome is returned.
Unit 10- Distributed Order Nanagement
10-79 Yantra Application Administration Yantra Company Confidential
10-79
NegotIatIon TransactIon Process
Start
Negotiation
Create
Document
Accept Reject
Create
Negotiation
Order
Create
Negotiator
Response
Create
!nitiator
Response
Offer
Counter
Accept or
Reject
S
u
b
-
p
r
o
c
e
s
s
Negotiation Pipeline
Receive
Negotiation
O
utcom
e
Originating Pipeline
Unit 10- Distributed Order Nanagement
10-80 Yantra Application Administration Yantra Company Confidential
10-80
honItor NegotIatIons
What is the Negotiation Nonitor?
Scheduled background program
Watches how long a negotiation has been in a
particular status
Watches for negotiation
expiration date
Raises alerts
Unit 10- Distributed Order Nanagement
10-81 Yantra Application Administration Yantra Company Confidential
10-81
Pricing and Taxes, and Charges
Order Definitions
Standard Order Fulfillment Process
Order Nonitor
0IstrIbuted Drder hanagement
Order Nodifications
When and How to Nodify
Nodification Audit Trail
Nodifications Rules
Nodification Permissions
Negotiation Process
Unit 10- Distributed Order Nanagement
10-82 Yantra Application Administration Yantra Company Confidential
10-82
ConsoIe: Drder hodIfIcatIons
CSRsfPlannersfNode users can use the
Console to:
Nodify Document at the customer's request
Nodify Document to correct problems
Any changes are reflected in the Audit tab
including:
Date
Nodified by
Nodification Type
Reason
Lxamples of order modifications
Manually allocate an order
Change addresses
Change order quantity
Add special instructions
Manually hold or release an order
Unit 10- Distributed Order Nanagement
10-83 Yantra Application Administration Yantra Company Confidential
10-83
What Happens on hodIfIcatIon!
Order
Modification
1. Update
the
database
2. Create
order audit
entry
3. Raise
appropriate
events
Update the database - write the new inormation to the correct tables and records in the database so
that the inormation is saed.
Create order audit entry - create an entry in the log that tracks who made what modiication to which
order, and when that modiication occurred.
Raise appropriate events - \antra can be conigured so that when an order is modiied, an eent is
triggered to perorm an action. lor example, you may want to conigure \antra so that eery time
someone changes the Ship 1o address on an order ,the eent`,, an email is sent to the customer to
conirm the change ,the action`,.
Unit 10- Distributed Order Nanagement
10-8+ Yantra Application Administration Yantra Company Confidential
10-8+
ackground hodIfIcatIons
Nodifications can be done:
Nanually via Console
Automatically via background programs
change" AP!'s
Allows possibility to expose document modification
functionality to customers via web site or other
systems via interface
Some examples o change` API`s:
changeOrder API
changeOrderStatus API
ChangeOrderSchedule API
changeRelease API
splitLine API
Unit 10- Distributed Order Nanagement
10-85 Yantra Application Administration Yantra Company Confidential
10-85
What are hodIfIcatIon PuIes!
Document Type specific settings
Not just for a particular user or
group of users
Apply to all possible Document
modifications
via Console
via background programs using AP!
Unit 10- Distributed Order Nanagement
10-86 Yantra Application Administration Yantra Company Confidential
10-86
hodIfIcatIons
Configure allowed modifications based
on your business requirements
Nodifications are comprised of:
Nodification Type
Nodification Level
Order Statuses
Type
Level
Status
Modiication type, modiication leel, and order status orm a three dimensional matrix in which the
allowed modiications are conigured.
Unit 10- Distributed Order Nanagement
10-87 Yantra Application Administration Yantra Company Confidential
10-87
ConfIgure hodIfIcatIons
Add Nodification Types to support business
requirements. Yantra adds any extended
order status to each list in Order Nodification
Rules automatically.
Nodification
Level
Nodification
Type
lor attribute modiications, the system determines which modiication type to use in the ollowing
ashion:
lirst, looks or a system deined modiication type
1hen, looks or a custom modiication type
linally, the modiication type O1lLR is used.
Unit 10- Distributed Order Nanagement
10-88 Yantra Application Administration Yantra Company Confidential
10-88
hodIfIcatIon LeveIs and DptIons
All modifications are actually validated at
the order line and order release line level
!f your make a
modification at. Then validation is at.
Order level Order Line and Order Release Line level
Order Line level Order Line and Order Release Line level
Order Release level Order Release Line level
Order Release Line Order Release Line level
level
I you make a modiication at the order or order line leel but the order is not yet released, then only the
order line is used or alidation because the order release line does not exist.
I the modiication ails alidation, then \antra does not allow the modiication to be carried out. 1he
alidation must pass beore you can modiy an order.
Unit 10- Distributed Order Nanagement
10-89 Yantra Application Administration Yantra Company Confidential
10-89
hodIfIcatIon PermIssIons
Nodification Rules work together with
Group level permissions to determine
modification access
Nodification Rules
Group Level Permissions
Unit 10- Distributed Order Nanagement
10-90 Yantra Application Administration Yantra Company Confidential
10-90
hodIfIcatIon PermIssIons
Control Group Nodification
Permissions by controlling access
to entities within a view and then
modifications within that view for
specific attributes.
Unit 10- Distributed Order Nanagement
10-91 Yantra Application Administration Yantra Company Confidential
10-91
Drder hodIfIcatIon DverrIde
Can set specific user
groups to be able to do
disallowed order
modifications
Set via user group
permissions
Override for
Nodifications item
\ou may not want to gie most users permission to oerride the order modiication settings. Generally,
this eature is made aailable to users at a superisory leel only so that they can consider the
implications o oerriding the system settings beore proceeding.
Unit 10- Distributed Order Nanagement
10-92 Yantra Application Administration Yantra Company Confidential
10-92
PequIred PermIssIons for NegotIatIon
These modifications must be allowed for
negotiation initiators to do fulfillment
negotiations with suppliers:
1. Quantity change
2. Cost change
3. Requested Ship Date change
Unit 10- Distributed Order Nanagement
10-93 Yantra Application Administration Yantra Company Confidential
10-93
Pricing and Taxes, and Charges
Order Definitions
Order Nodifications
Standard Order Fulfillment Process
0IstrIbuted Drder hanagement
Order Nonitor
Unit 10- Distributed Order Nanagement
10-9+ Yantra Application Administration Yantra Company Confidential
10-9+
honItor Drder Ages
What is the Order Nonitor?
Scheduled background program
Watches how long an order has been in a
particular status
Raises alerts
Conditional age thresholds
for each order status
Lxample
\ou want to know i it takes more than some number o hours or ship nodes to reiew orders ,which
moes orders rom status Awaiting Acceptance to Rejected,Sent 1o Node,, but you hae dierent
tolerances or dierent ship nodes. 1he order monitor can be set so that any order at one Supplier that
stays in Awaiting Acceptance status or too long, say 24 hours, generates an action, but any order at
another Supplier has only 8 hours beore an action is generated.
Unit 10- Distributed Order Nanagement
10-95 Yantra Application Administration Yantra Company Confidential
10-95
SpecIfy Drder honItorIng PuIes
The Rule Set selected in Organization
Details determines the order aging
strategy to use.
Unit 10- Distributed Order Nanagement
10-96 Yantra Application Administration Yantra Company Confidential
10-96
PrIorIty Drder AgIng - ExampIe
Awaiting
Acceptance
No
Age1 = 2+ hrs
Age2 = +8 hrs
Age1 = 72 hrs
Send exception
to planner
Send Email to
ship node
Reallocate order
to another node
No action
required
Yes Ship Node=
DC!,
Priority 2?
Ship Node=
DC!-ACC,
Priority 1?
Yes
No
Age1 = 8 hrs
Age2 = 2+ hrs
Age1 = +8 hrs
Send Email to
ship node
Send Email to
enterprise
Send exception
to planner
Done
\hen the Order Monitor background program runs, it analyzes each order and checks to see i \antra
has a condition or that order`s status that the order matches. I the order does match a condition in the
order aging rules, then \antra executes the associated aging actions or that condition.
Unit 10- Distributed Order Nanagement
10-97 Yantra Application Administration Yantra Company Confidential
10-97
AgIng an Drder Status
The Order Nonitor uses the age
constraints to notify you when an
order stays in a specific status for
too long.
1o create order monitoring rules for an Lnterprise
1. Select Platorm Business Process Process Modeling.
2. Click the Statuses tab.
3. Select the Status or which you want to create a rule.
4. Click the Details button.
5. Click the Conditions tab.
6. Drag Conditions into the work area.
. Right click. Select Action Add Monitor Node
8. Click the Actions tab
9. Drag the desired action into the work area.
10. Sae.
I the user creating the rule is a lub user, they are creating the lub order monitoring rules. I the user
creating the rule is an Lnterprise user, they are creating the Lnterprise order monitoring rules.
Unit 10- Distributed Order Nanagement
10-98 Yantra Application Administration Yantra Company Confidential
10-98
0eIayed ShIpment honItorIng
All document lines have an Expected Time
of Shipment (ETS)
Based on order date and time to process order
!f order is not shipped by ETS, order monitor
can generate a Delayed Shipment" error
Delayed Shipment" order continues
progression through the order fulfillment
process
Note
\ou do not see the status Delayed Shipment` on the order console. 1his status is internal to the \antra
application.
Unit 10- Distributed Order Nanagement
10-99 Yantra Application Administration Yantra Company Confidential
10-99
0eIayed ShIpment honItorIng
Order has ETS of 3f31f2002 and has
status of Released. Today is +f6f2002.
Does not change the order status seen on
consoles
Order continues to the next step in the
fulfillment process (Sent to Node)
Can trigger an event or flag to notify you that
shipment is delayed
Lxpected 1ime o Shipment is automatically generated once the order is allocated. 1his date can also be
manually modiied.
Console generates the Lxpected 1ime o Shipment using the ollowing ormula:
L1S ~ Current Date - Processing 1ime ,see |vit 1 - vrevtor, ,vcbroviatiov or inormation about
processing time,
Unit 10- Distributed Order Nanagement
10-100 Yantra Application Administration Yantra Company Confidential
10-100
UnIt 10: PevIew
What is a document?
What is the difference between a chained and a
derived document?
How do you define which shipping nodes stock
which items?
What are some of the attributes you can
configure in Schedule Rule?
What are the steps for negotiating order
fulfillment within Yantra?
How can you relate the order modification rules
to your business needs?
Unit 10- Distributed Order Nanagement
10-101 Yantra Application Administration Yantra Company Confidential
10-101