<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GLOGOWNER on Learn Oracle OTM</title><link>https://www.oracle-otm.com/tags/glogowner/</link><description>Recent content in GLOGOWNER on Learn Oracle OTM</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 02 May 2016 16:34:00 +0000</lastBuildDate><atom:link href="https://www.oracle-otm.com/tags/glogowner/index.xml" rel="self" type="application/rss+xml"/><item><title>OTM Domains, Standard Schema and Data Dictionary</title><link>https://www.oracle-otm.com/posts/otm-domains-standard-schema-and-data-dictionary/</link><pubDate>Mon, 02 May 2016 16:34:00 +0000</pubDate><guid>https://www.oracle-otm.com/posts/otm-domains-standard-schema-and-data-dictionary/</guid><description>&lt;p&gt;&lt;strong&gt;Domains:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;OTM Data is organized into domains. Each domain is like grouping of data / business transactions based on the different business units with in the same organization.&lt;/p&gt;
&lt;p&gt;If there is a corporation with logistics requirements across various business units like &amp;ldquo;Merchandise Shipping&amp;rdquo;, &amp;ldquo;Food and Beverages&amp;rdquo;, etc - you typically create one domain for each of these business units so that users and their roles can be tied to each business unit. User/role tied to a particular domain can only access data for their specific domain/business unit. Also advantage with domains is that customization specific to a business unit can be better controlled/maintained. For example, OTM Agents(workflows) with custom code can be developed specific to each domain so they they trigger only for transactions within that domain.&lt;/p&gt;</description></item></channel></rss>