<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-Leg on Learn Oracle OTM</title><link>https://www.oracle-otm.com/tags/multi-leg/</link><description>Recent content in Multi-Leg on Learn Oracle OTM</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 22 Aug 2020 04:32:00 +0000</lastBuildDate><atom:link href="https://www.oracle-otm.com/tags/multi-leg/index.xml" rel="self" type="application/rss+xml"/><item><title>02 - Itinerary</title><link>https://www.oracle-otm.com/posts/basic-otm-configurations-02-itinerary/</link><pubDate>Sat, 22 Aug 2020 04:32:00 +0000</pubDate><guid>https://www.oracle-otm.com/posts/basic-otm-configurations-02-itinerary/</guid><description>&lt;p&gt;&lt;strong&gt;Itinerary:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; This post is continuation to topic: 01 and these configurations are specific to business scenario mentioned in that post. Link below to that post for quick reference:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.oracle-otm.com/posts/basic-otm-configurations-01-domain-items-locations-and-equipment/"&gt;01 - Domain, Items, Locations, and Equipment&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Define Itineraries as below:&lt;/strong&gt;&lt;/p&gt;
&lt;blockquote class='book-hint '&gt;
&lt;p&gt;&lt;img src="https://www.oracle-otm.com/images/basic-otm-configurations-02-it-img1-f4ab54eb77.png" alt="" /&gt;&lt;/p&gt;
&lt;/blockquote&gt;&lt;blockquote class='book-hint '&gt;
&lt;p&gt;*S=Source Location&lt;/p&gt;
&lt;p&gt;*D=Destination Location&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;Shipment Management &amp;gt; Itinerary Management &amp;gt; Itinerary:&lt;/p&gt;
&lt;blockquote class='book-hint '&gt;
&lt;p&gt;&lt;img src="https://www.oracle-otm.com/images/basic-otm-configurations-02-it-img2-247e7d669f.png" alt="" /&gt;&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;ITIN_A, B and C are single leg itineraries in format similar to below:&lt;/p&gt;</description></item></channel></rss>