CIMPLICITY4. POMS.xsd Schema
Gathered .xml files are the source that is evaluated and goes through the Product Order Management System (POMS) once the trigger for the first RCO site, $OMV_ORDER, is initiated.
An XML schema file, POMS.xsd, defines the order entry interface to POMS. This schema is used for validating XMLT output before it is accepted for processing by POMS.
POMS.xsd is the required schema definition for the .xml order files. This file is located in the ...\Program Files\Proficy\Proficy CIMPLICITY\POMS directory and defines the various elements and attributes constitute an XML-based order that the Plant Order Management System (POMS) accepts.
XML-based orders are the translated XML files that XMLT generates as output.
Note: You do not code with POMS elements. XMLT automatically creates translated files that incorporate these elements. The description below is provided for debugging purposes only. For information on XMLT and XMLT Element Types see XMLT Schema .
<?xml version="1.0"?>
<Schema name="POMS" xmlns="urn:schemas-microsoft-com:xml-data"
xmlns:dt="urn:schemas-microsoft-com:datatypes" >
<AttributeType name="AN" dt:type="string"/>
<AttributeType name="GN" dt:type="string"/>
<AttributeType name="IT" dt:type="string"/>
<AttributeType name="Id" dt:type="string"/>
<ElementType name="A" dt:type="string" model="closed">
<attribute type="AN" required="yes"/>
</ElementType>
<ElementType name="R" content="eltOnly" model="closed">
<element type="A" maxOccurs="*"/>
</ElementType>
<ElementType name="G" content="eltOnly" model="closed">
<attribute type="GN" required="yes"/>
<element type="R" maxOccurs="*"/>
</ElementType>
<ElementType name="I" content="eltOnly" model="closed">
<attribute type="IT" required="yes"/>
<attribute type="Id" required="yes"/>
<element type="G" maxOccurs="*"/>
</ElementType>
<ElementType name="File" content="eltOnly" order="one" model="open">
<element type="I" minOccurs="0" maxOccurs="*"/>
<element type="G" minOccurs="0" maxOccurs="*"/>
</ElementType>
</Schema>POMS Element Types
These elements appear in the XMLT output file, i.e. the file that POMS takes as its input.
| Element type | Description | ||
| File | File header for the POMS XML order file (XMLT output file). Note: This file may contain one order or multiple orders depending on the configuration of the File Element Type in the translation XML file based on XMLT.xsd. | ||
| Content: | eltOnly | ||
| Order: | One | ||
| Model: | Open | ||
| Attribute Types: | |||
| Element Types: | I | Optional | |
| G | Optional | ||
| Related Elements : | |||
| Example | |||
| An File element with a Date attribute: <File Date="030930">. . . </File> | |||
| I | Item element for an order item. Note: The Item Type (IT) must be defined in the TADB and PRT databases before POMS can process the order. | ||
| Content: | mixed | Note: Text content, i.e. Item Type, must be all uppercase. | |
| Order: | |||
| Model: | Closed | ||
| Attribute Types: | IT | ||
| Id | |||
| Element Types: | G | Optional | |
| Related Elements: | File | ||
Example
Item:.
<I IT="ORDER" Id="ABC12345X67890">
<G GN="Order">
<R>
<A AN="PIN">ABC12345X67890AAP2AFWAUVB0ABVCA2H83CFBE1RCWIDGET</A>
<A AN="SeqAttrib">000120001</A>
</R>
</G>
</I>
|
|||
| G |
Group element.
|
||
| Content: | eltOnly | ||
| Order: | |||
| Model: | Closed | ||
| Attribute Types: | |||
| Element Types: | R | ||
| Related Elements: | File | ||
Example
A nested group associated with an order item:
<I IT="ORDER" Id="ABC12345X67890">
<G GN="Order Card">
<R>
<A AN="PIN">ABC12345X67890AAP2AFWAUVB0ABVCA2H83CFBE1RCWIDGET</A>
<A AN="SeqAttrib">000120001</A>
</R>
</G>
</I>
Group data for TADB parts lookup tables:
<File Date="20030311">
<G GN="Installed Parts">
<R>
<A AN="PartNo"105427/>
<A AN="Description">Warehouse Part for Assy 101</A>
</R>
</G>
<G GN="Peripheral Parts">
<R>
<A AN="OEMPartNo"105427/>
<A AN="Description">Outsourced Part for Assy 101</A>
</R>
</G>
</F>
|
|||
| R | Record element. This element contains one or more A elements (TADB group attributes). | ||
| Content: | eltOnly | ||
| Order: | |||
| Model: | Closed | ||
| Attribute Types: | |||
| Elements Types: | A | ||
| Related Elements: | File | ||
Example
A group associated with an order item:
<I IT="ORDER" Id="ABC12345X67890">
<G GN="Order Card">
<R>
<A AN="PIN">ABC12345X67890AAP2AFWAUVB0ABVCA2H83CFBE1RCWIDGET</A>
<A AN="SeqAttrib">000120001</A>
</R>
</G>
</I>
|
|||
| A | Attribute element (TADB group attribute). | ||
| Content: | Text Only | ||
| dt:type: | String | ||
| Order: | |||
| Model: | Closed | ||
| Attribute Types: | AN | ||
| Element Types: | |||
| Related Elements: | R | ||
Examples
An TADB attribute:
<R>
<A AN="OEMPartNo"105427/>
<A AN="Description">Outsourced Part for Assy 101</A>
</R>
|
|||
POMS Attribute Types
These attributes appear in POMS elements within the XMLT output file, i.e. the file that POMS takes as its input.
| Attribute Type | ||
| AN | Attribute name. | |
| dt:type | String | |
| Length | Up to 40 characters. | |
| Default | ||
| Example | ||
| <A AN="Description">Outsourced Part for Assy 101</A> | ||
| GN | Group name. | |
| dt:type | String | |
| Length | ||
| Default | ||
| Example | ||
| <G GN="Order Card"> | ||
| IT | Item Type (Item Type ID). | |
| dt:type | String | |
| Length | ||
| Default | ||
| Example | ||
| <I IT="ORDER" Id="ABC12345X67890"> | ||
| Id | Item ID. | |
| dt:type | String | |
| Length | ||
| Default | . | |
| Example | ||
| <I IT="ORDER" Id="ABC12345X67890"> | ||
