<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Purchase Orders Archives - Caliach</title>
	<atom:link href="https://caliach.com/article-categories/purchase-orders/feed/" rel="self" type="application/rss+xml" />
	<link>https://caliach.com/article-categories/purchase-orders/</link>
	<description>Manufacturing Software Solutions</description>
	<lastBuildDate>Wed, 27 May 2020 16:38:33 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://caliach.com/wp-content/uploads/2022/11/fav-150x150.png</url>
	<title>Purchase Orders Archives - Caliach</title>
	<link>https://caliach.com/article-categories/purchase-orders/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Purchase Orders: Purchase Order Duplication Options</title>
		<link>https://caliach.com/knowledge-base/wpohdup/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpohdup/</guid>

					<description><![CDATA[<p>Purchase Orders: Purchase Order Duplication Options</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpohdup/">Purchase Orders: Purchase Order Duplication Options</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Purchase Order Duplication Options</h2>
<p id="navline"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Duplication Options</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpohdup.jpg"><img fetchpriority="high" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpohdup.jpg" width="350" height="163" alt="Purchase Order Duplication Options"/></a></p>
<p>Having selected a Purchase Order in the <a href="wpomaint">Purchase Order Maintenance</a> window, you can duplicate it and create a new PO with all line items reproduced with due dates changed to reflect your new requirements. This options window is brought forward. In it you can also choose an historic, already received, purchase order.</p>
<p>If you select the <b>Old received Order</b> option, you must click on the <b>Select</b> button to choose the order you wish to duplicate in the <a href="../pohistory/wpopuhselect">Purchase History PO Selection</a> window. The earliest and latest receipt dates for items will be shown.</p>
<p>You can choose to move the selected order&#8217;s due dates by a number of days, which can optionally be in working days from the Buy Calendar. Alternatively, you can set all items to have a due date on a particular date. The earliest and latest dates will be shown.</p>
<p>Once you confirm with an <b>OK</b> or by pressing the Enter key, a duplicate order will be created.</p>
<p><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> Line Items which are for Job or Work Order Outwork Operations will not be duplicated.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Currently selected order</p>
</td>
<td valign="top">
<p align="left">Choose this option to copy the currently selected PO.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Old received Order</p>
</td>
<td valign="top">
<p align="left">Choose this option to copy a PO that has already been delivered.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Select</p>
</td>
<td valign="top">
<p align="left">Click on this button to select an historic PO.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Move by days:</p>
</td>
<td valign="top">
<p align="left">This option lets you move the PO delivery dates by the number of days you enter alongside.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Days</p>
</td>
<td valign="top">
<p align="left">Enter the number of days that each line item delivery date will be advanced by.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Use Buy calendar</p>
</td>
<td valign="top">
<p align="left">Check this option if you want data advance to be based on the Buy Calendar&#8217;s active days only.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Move to date:</p>
</td>
<td valign="top">
<p align="left">This option lets you move the PO delivery dates to a specific date.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Date</p>
</td>
<td valign="top">
<p align="left">The date that all line items will be set for delivery to.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Purchase Order Number</p>
</td>
<td valign="top">
<p align="left">Indicates the PO that is selected and will be duplicated.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Earliest</p>
</td>
<td valign="top">
<p align="left">The earliest delivery date for items in the selected PO.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Latest</p>
</td>
<td valign="top">
<p align="left">The latest delivery date for items in the selected PO.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Earliest</p>
</td>
<td valign="top">
<p align="left">The earliest delivery date for items in the PO you will create.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Latest</p>
</td>
<td valign="top">
<p align="left">The latest delivery date for items in the PO you will create.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Cancel</p>
</td>
<td valign="top">
<p align="left">Aborts the process currently in session. The keyboard equivalent is the Esc key for Windows computers and Command-.(full stop or period) for the Mac.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">OK</p>
</td>
<td valign="top">
<p align="left">The OK button updates the data you have entered, or confirms the selection and/or processes the function you have called.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../purchases/mpurchorder">&#8211; Purchase Orders Menu</a></li>
<li><a href="../purchases/wpomaint">Purchase Order Maintenance</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 4 Jun 2012 04:48:00.00. Class wPohDup last modified 7 Oct 2015  10:38:38.</p>
<p id="navline"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Duplication Options</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpohdup/">Purchase Orders: Purchase Order Duplication Options</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Purchase Orders: Purchase Order Listing for a Part or Supplier</title>
		<link>https://caliach.com/knowledge-base/wpohlist/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpohlist/</guid>

					<description><![CDATA[<p>Purchase Orders: Purchase Order Listing for a Part or Supplier</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpohlist/">Purchase Orders: Purchase Order Listing for a Part or Supplier</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Purchase Order Listing for a Part or Supplier</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Listing for a Part or Supplier</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpohlist.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpohlist.jpg" width="239" height="177" alt="Purchase Order Listing for a Part or Supplier"/></a></p>
<p>This window opens when you drill-down to a supplier on-order value or a part due from PO/WOs value. It enables you to select an order or RFQ to view.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Supplier Code</p>
</td>
<td valign="top">
<p align="left">Suppliers. Supplier unique code identifier. {SUPFILE.SUPCODE char 6}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Supplier Name</p>
</td>
<td valign="top">
<p align="left">Suppliers. Supplier company name. {SUPFILE.SUPNAME char 40}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Part Number</p>
</td>
<td valign="top">
<p align="left">Parts Master. Part number unique identifier. {PTMFILE.PTMPTNO char 18}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Part Description</p>
</td>
<td valign="top">
<p align="left">Parts Master. Part description. {PTMFILE.PTMDESC char 30}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Document List</p>
</td>
<td valign="top">
<p align="left">All purchase orders and request for quotations for the supplier or part shown above. Double-Click to select an order to view in the <a href="wposhow">Purchase Order or RFQ Details</a> window.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../purchases/wposhow">Purchase Order or RFQ Details</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 8 May 2012 06:21:00.00. Class wPohList last modified 23 Sep 2017  10:51:00.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Listing for a Part or Supplier</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpohlist/">Purchase Orders: Purchase Order Listing for a Part or Supplier</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Purchase Orders: Purchase Order Report Selection</title>
		<link>https://caliach.com/knowledge-base/wpohprint/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpohprint/</guid>

					<description><![CDATA[<p>Purchase Orders: Purchase Order Report Selection</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpohprint/">Purchase Orders: Purchase Order Report Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Purchase Order Report Selection</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Report Selection</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpohprint.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpohprint.jpg" width="341" height="236" alt="Purchase Order Report Selection"/></a></p>
<p>This report setup window provides you with the ability to choose a range of selections, sort order and report types.</p>
<p>You can drag and drop onto the window from the Suppliers ScratchPads to obtain a report of selected suppliers only.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> This window contains fields introduced with version 5 that enable additional search (and sometimes sort controls), such as <b>Adhoc extra where</b>. For more help on their use and examples see the <a href="../sql/introsql">Client-Server SQL Introduction</a> help.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Document Selection</p>
</td>
<td valign="top">
<p align="left">Enter a selection in the <a href="wpohselect">PO Header Selection</a> subwindow.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Sort</p>
</td>
<td valign="top">
<p align="left">Choose the field for the primary sort of parts on the report.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Report Type list</p>
</td>
<td valign="top">
<p align="left">Select a report type. Any custom reports entered in the Settings will appear at the bottom of the list.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Cancel</p>
</td>
<td valign="top">
<p align="left">Aborts the process currently in session. The keyboard equivalent is the Esc key for Windows computers and Command-.(full stop or period) for the Mac.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Print Report</p>
</td>
<td valign="top">
<p align="left">Will cause a report to be printed of the subject matter. Right-click to change the report destination.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../purchases/wpohselect">Purchase Order Header Selection</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 3 Jan 2015 11:01:00.00. Class wPohPrint last modified 17 Oct 2017  04:29:55.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Report Selection</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpohprint/">Purchase Orders: Purchase Order Report Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Purchase Orders: Purchase Order Header Selection</title>
		<link>https://caliach.com/knowledge-base/wpohselect/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpohselect/</guid>

					<description><![CDATA[<p>Purchase Orders: Purchase Order Header Selection</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpohselect/">Purchase Orders: Purchase Order Header Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Purchase Order Header Selection</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Header Selection</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpohselect.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpohselect.jpg" width="290" height="134" alt="PO Header Selection"/></a></p>
<p>This subwindow is used to define the range of criteria for a selection of purchase orders. It is displayed on windows requiring their selection.</p>
<h4>Parent Windows</h4>
<p><a href="wpohprint">Purchase Order Report Selection</a><br />
<a href="../advanced/wlinkmaint">Link System Maintenance</a><br />
<a href="../general/wadhocgraphsmaint#tab2">Graphical Analysis Maintenance &#8211; Graphs Tab</a></p>
<h4>Operation</h4>
<p>Enter data in the data entry boxes to restrict the range of parts. Records must meet all criteria entered to be selected. If the left and/or right data entry boxes are left blank for a particular criteria, parts will be selected between the first and/or last otherwise qualifying part record.  Data entry boxes can be populated by finding a single item using <strong>Keyword Search</strong>, drag and drop from the <a href="../scratch/wscratchsuppliers">Suppliers ScratchPad</a>, or by double-clicking a list item from the <a href="../general/wkwdpopup">Keyword Result</a> window.
</p>
<p>Data records can be obtained using one of the following methods or a combination of them (see Tip below):</p>
<ol>
<li>Enter values into the selection ranges and use the <b>Standard Search</b>. The <a href="../general/msearchsub">context menu</a> provides a Clear Selection function.</li>
<li>Define or use a <b>Custom Search</b>.</li>
<li>Create an <b>Ad Hoc Search Calculation</b> using the <a href="../general/msearchsub">context menu</a> function.</li>
<li><b>Drag-and-drop</b> one or more lines from the Supplier ScratchPad onto the general window area.</li>
<li>Use the <b>ScratchPad Transfer Selected</b> function</li>
<li>Use the <b>KeyWord Search Transfer Selected</b> function</li>
</ol>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> Using an <b><i>Ad Hoc Search Calculation</i></b> (3) overrides any <b><i>Custom Search</i></b> (2) and a Custom Search overrides the <b><i>Standard Search</i></b> (1). In any of the search cases (1, 2 or 3), ScratchPad Transfer and Drag-and-Drop or KeyWord Search Transfer (4, 5 or 6) is <b>combinational</b>, so that records found using any of these methods must <b>also</b> conform to the search criteria adopted.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> This window contains fields introduced with version 5 that enable additional search (and sometimes sort controls), such as <b>Adhoc extra where</b>. For more help on their use and examples see the <a href="../sql/introsql">Client-Server SQL Introduction</a> help.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">From and To</p>
</td>
<td valign="top">
<p align="left">Enter data that restricts the records selected. If left blank, data will be selected from the maximum and minimum extremes in the file. All selections criteria you enter will have to be met by each record processed.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Use custom</p>
</td>
<td valign="top">
<p align="left">To turn on and off the use of the custom search design. A custom search will override the standard search.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Custom search name</p>
</td>
<td valign="top">
<p align="left">The name of the currently selected custom search. To use it click on the checkbox. To change it click on the Custom Search button.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Custom Search</p>
</td>
<td valign="top">
<p align="left">Opens the <a href="../general/wsearchselect">Custom Search Selection</a> window and checks the <strong>Use custom</strong> checkbox.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../general/msearchsub">Search Options Menu</a></li>
<li><a href="../purchases/wpohprint">Purchase Order Report Selection</a></li>
<li><a href="../scratch/wscratchsuppliers">Supplier ScratchPad</a></li>
<li><a href="../general/wkwdpopup">Keyword Result</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 3 Jan 2015 11:01:00.00. Class wPohSelect last modified 10 Oct 2017  11:48:29.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Header Selection</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpohselect/">Purchase Orders: Purchase Order Header Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Purchase Orders: KanBan Purchase Order Entry</title>
		<link>https://caliach.com/knowledge-base/wpokanban/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpokanban/</guid>

					<description><![CDATA[<p>Purchase Orders: KanBan Purchase Order Entry</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpokanban/">Purchase Orders: KanBan Purchase Order Entry</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>KanBan Purchase Order Entry</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; KanBan Purchase Order Entry</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpokanban.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpokanban.jpg" width="437" height="170" alt="KanBan Purchase Order Entry"/></a></p>
<p>This window opens from Process &#8212; Purchase Order &#8212; Create KanBan Orders menu item. While this function opens and operates with the Purchase Order Maintenance window, this is technical and the User does not need to have Purchase Order &#8212; Update PO or RFQ privileges. If the user does not, then the PO Maintenance window will remain inert to the user.</p>
<h4>KanBan Purchase Orders</h4>
<p>KanBan is a concept related to lean and just-in-time (JIT) production. Typically it is implemented for Bulk Issue items that get re-stocked on the basis of the shopfloor stock level dropping to a certain re-order point usually physically identified by a KanBan Card being revealed in the stock bin of the part. The card typically contains a barcode so that the production worker can use the card to directly trigger an order for re-stocking.</p>
<p>This window allows for a single line item PO to be created and printed by scanning a KanBan Card. It also is used to print the KanBan Cards in the first place or re-print them when needed. </p>
<p>The window is deliberately restrictive for use by staff not normally authorised to place Purchase Orders. The part number can be entered by barcode, directly or by clicking on the Parts ScratchPad.</p>
<p>An order can only be created for a part that has a valid Primary Supplier and a Purchase Part record for that supplier, typically with a minimum stock set, otherwise the quantity will be the part&#8217;s re-order level. If there is more than one purchase part record the cheapest will be selected first.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> For a User or Group you can force even more restrictions on the purchase part being used. The option optPOKanBanNoChoice can be set: If set to 1, the user will be forced to accept the best ranked purchase part record. If set to a text, then the purchase-part record with that text (case-insensitive) in the notes will be chosen, then by rank. This allows you to restrict the parts available for KanBan orders.</p>
<p>A message at the bottom of the window reports any problems encountered with a part. If a part can be ordered it will be added to the Print part list, to allow for printing of KanBan Cards.</p>
<p>When a PO is created all normal rules of PO creation will apply as though the user created a PO in the PO Maintenance window. Any anomalies will be reported as normal and the order will not be created if the rules are broken, for example, user limits, supplier limits, etc..</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> If the user has a Setting in Defaults (File &#8212; Preferences &#8212; User Settings) that defaults them to RFQs rather than POs, an RFQ will be created.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Part number</p>
</td>
<td valign="top">
<p align="left">Parts Master. Part number unique identifier. {PTMFILE.PTMPTNO char 18 Idx}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Part description</p>
</td>
<td valign="top">
<p align="left">Parts Master. Part description. {PTMFILE.PTMDESC char 30}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Supplier code</p>
</td>
<td valign="top">
<p align="left">Suppliers. Supplier unique code identifier. {SUPFILE.SUPCODE char 6 Idx}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Supplier name</p>
</td>
<td valign="top">
<p align="left">Suppliers. Supplier company name. {SUPFILE.SUPNAME char 40 Idx}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Alternatives list</p>
</td>
<td valign="top">
<p align="left">Lists all purchase part records for the preferred supplier for the part.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Print part list</p>
</td>
<td valign="top">
<p align="left">Lists parts available for KanBan Card printing. Select those you want to print. Use the delete key to remove selected lines.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Create and Print PO</p>
</td>
<td valign="top">
<p align="left">Click to create a PO for the part/supplier and print it.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Print KanBan Cards</p>
</td>
<td valign="top">
<p align="left">Click to print cards for the selected parts in the list to the left.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../purchases/wpomaint">Purchase Order Maintenance</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 4 Jun 2012 04:48:00.00. Class wPoKanBan last modified 17 Oct 2017  04:29:55.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; KanBan Purchase Order Entry</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpokanban/">Purchase Orders: KanBan Purchase Order Entry</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Purchase Orders: Purchase Order Line Item Maintenance</title>
		<link>https://caliach.com/knowledge-base/wpolmaintsub/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpolmaintsub/</guid>

					<description><![CDATA[<p>Purchase Orders: Purchase Order Line Item Maintenance</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpolmaintsub/">Purchase Orders: Purchase Order Line Item Maintenance</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Purchase Order Line Item Maintenance</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Line Item Maintenance</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpolmaintsub1.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpolmaintsub1.jpg" width="445" height="224" alt="Purchase Order Line Item Maintenance - Item Details pane"/></a></p>
<p>This details subwindow forms part of the <a href="wpomaint">Purchase Order Maintenance</a> window.</p>
<p>A Purchase Order header can exist without line items, however it can not be printed and is not really meaningful. Up to 999 line items can be created for a PO.</p>
<p>You can sort the list of line items in any order by clicking on the appropriate list heading. Sorting by due date will sort the list by date and then part number enabling you to view it as a schedule.</p>
<h4>Purchase Order Line Items</h4>
<p>To add items to the Purchase Order, click on the <b>Add</b> button. The next available line number will be automatically entered. A PO is limited to 999 line items. If the item is a part with a valid Part record, enter it&#8217;s part number or partial number. If the item is not a normal part, leave the Our part number field blank. You can also use Keyword Search, or drag and drop from the Parts ScratchPad. A useful technique is to multiple select parts in the ScratchPad and drag them and drop them on the list. All will be added with appropriate minimum order quantities.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/warning40-28.jpg" width="24" height="24" alt="Warning"/><strong> WARNING:</strong> Once a part number item line has been created and some quantity has been received, the part number can not be changed for that item.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> You can use drag-and-drop in the list to re-order your line items. This can only be done if you have the list sorted by line number (in descending order) <b>and</b> the PO has not had any receipt of goods. When the lines are re-positioned the lines are renumbered starting from 1.</p>
<p>If you are purchasing an operation of a process route for an assembly subject to a Work Order, you must construct a pseudo part number in the form of &#8220;WO-999999-000&#8221;, where 999999 is the full work order number and 000 is the operation number, with leading zeros if required to make 3 characters.</p>
<p>If you are purchasing an operation of a Job, you must construct a pseudo part number in the form of &#8220;JO-999999-000&#8221;, where 999999 is the full Job number and 000 is the line number, with leading zeros if required to make 3 characters.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> For the system to accept an Outwork Operation, the following must be the case:</p>
<ul>
<li>The pseudo part number must be correctly constructed, starting with a WO- or JO-.</li>
<li>There must be a current Work Order or Job with the number you enter.</li>
<li>You must have entered a valid Route Operation or Job Line Number (001 to 999).</li>
<li>For a WO the assembly being manufactured under the Work Order must have a Process Route with an appropriately numbered operation.</li>
<li>The Work Centre assigned to this process route operation or job operation must be flagged as an Outwork Work Centre.</li>
</ul>
<p>After a part number has been entered, the system searches the Purchase Part file for a match for this part number and the PO supplier. If found, details from the Purchase Part record are loaded into the supplier part number, description, buy UoM and buy UoM multiplier fields. If a record is not found in the Purchase Part file, data from the parts master record is used. The Buy UoM will be the same as the Stock UoM with a multiplier of 1.0000. In both cases, you can edit any of the entered data. Any changes will be recorded in the Purchase Part file after the item&#8217;s receipt when the  <i>Update purchase part file on receipt</i> is checked. If you check the <i>MRP to ignore</i> checkbox, the supply this item represents will be ignored in MRP processing.</p>
<p>Additionally, the part&#8217;s Re-order quantity divided by the Buy UoM is provided as default for the Order quantity or, if the item is a WO Outwork Operation, the WO assembly quantity or,if a Job Operation, the Job item quantity. The delivery date defaults to the date calculated from the part&#8217;s lead time and the Buy Calendar. For an Outwork Operation the date is calculated from the operation Lag Time divided by the Work Centre time per day.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/warning40-28.jpg" width="24" height="24" alt="Warning"/><strong> WARNING:</strong> You may find that you can not edit the order quantity below a certain amount. This will be because the Purchase Part record for the Supplier/Part has a zero first cost and an initial cost quantity. Doing this, in effect, enforces a minimum order quantity for this part from this supplier.</p>
<p>The This-purchase cost is, by default, the current material cost for the part. If the part is an Outwork type part, the This-Level Outwork current cost is provided as default. If the item is an outwork operation the operation times and Work Centre rates are used to calculate a default cost. You can change the cost at this time.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/warning40-28.jpg" width="24" height="24" alt="Warning"/><strong> WARNING:</strong> If the System Preferences are set to automatically update and create Purchased Part records on goods receipt, the &#8220;Update PP file on receipt of item&#8221; checkbox will be checked. If left that way the data appearing on the order will be used to update or create a Purchase Part record when a receipt is processed. You should un-check the box to prevent update for this item.</p>
<p>If the our part number field is left blank, all fields must be completed by you from scratch. No fields can be left blank, other than the two part numbers.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/custom40-21.jpg" width="24" height="24" alt="Customisation"/><strong> CUSTOM CAPABILITY:</strong> <b>oCustom1.$PolqtyCheck()</b> can be used to process your own quantity validation or messaging system. It is called if the quantity is changed.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/custom40-21.jpg" width="24" height="24" alt="Customisation"/><strong> CUSTOM CAPABILITY:</strong> <b>oCustom1.$AfterItemAddedToPo()</b> is available to provide additional validation when a part is added.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/warning40-28.jpg" width="24" height="24" alt="Warning"/><strong> WARNING:</strong> You are prevented from deleting, or changing Order quantity or UoM multiplier, if the item has had an outwork kit issued to the supplier.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> You can apply individual parts texts to Purchase Order part items in an alternative manner. If you set <a href="../prefs/woptionslist">option</a> <b>optPODefaultIndivText</b> to &#8216;1&#8217;, &#8216;Y&#8217;, &#8216;Yes&#8217; or &#8216;YES&#8217;, the Individual Text will form a default description for the part rather than an additional text. I.E. When optPODefaultIndivText is set to &#8216;1&#8217;, line item description will default to the individual purchase text for the part when there is no relevant Purchase Part record description. Whenever this options is set, the individual parts texts will NOT be printed on the Purchase Order, as they are when it is not set.</p>
<h4>Outwork Assemblies and Purchase Order Kits</h4>
<p>The part type is significant to a purchase order item.</p>
<p>An <b>Outwork Assembly</b> must be a type &#8216;O&#8217; part. When entered on an order, it&#8217;s kit must be issued before it can be received. The system supports shortages in the kit issue process. To learn more about Outwork Assembly processing see the <a href="wpooutkit">Purchase Order Outwork Kit Review and Processing</a> window.</p>
<p>A <b>Purchase Order Kit</b> must be a type &#8216;P&#8217; part. When entered on an order, it&#8217;s kit components will be assumed to be received rather than the assembly part itself. This process is effectively automatic. You will only see the assembly part on a PO document or any reviews or receiving windows. However, when received or returned the kit components are received or returned and <b>not</b> the assembly. This is similar to a Sales Order Kit only in reverse. The parent is ordered and the components received. There is no variation in the receiving quantities of components, they are only ever received or returned in the BoM quantities for the relevant parent quantity. For the full implications to MRP see the <i>Treatment of Purchase Order Kits</i> section in the <a href="../mrp/mmrp">MRP Menu</a> topic.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> An appropriate use for PO Kits would be if the item you are purchasing comes from the supplier as an assembly which you break down into a number of components that are used in different product sub-assemblies. The mix of components is always fixed and in the same proportion within the parent.</p>
<h4>Window Fields and Buttons</h4>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Items List</p>
</td>
<td valign="top">
<p align="left">All line items will be listed for the Purchase Order that have not been fully received. Click on a line item to show and edit the full details.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Lines</p>
</td>
<td valign="top">
<p align="left">The total number of line items due for delivery.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Total Value of Due Items</p>
</td>
<td valign="top">
<p align="left">The total value of all items listed. Applies to undelivered quantities only.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Add</p>
</td>
<td valign="top">
<p align="left">This will create a new (normally blank) record in the file. You will then be able to enter details for the record.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> You can control which users are permitted to add parts to a purchase order using the Purchase Users field on a part record.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> Control can also be applied to purchasing non-part, work order and job operation items using the system options <b>optPOJobOpUsers</b>, <b>optPONonPartUsers</b> and <b>optPOWoOpUsers</b>.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Copy</p>
</td>
<td valign="top">
<p align="left">This will create a Copy of the current record displayed on the window. You will then be able to change the details.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Delete</p>
</td>
<td valign="top">
<p align="left">Execute this button to permanently remove the currently selected record from the file. If you are permitted to delete the item, you will be asked for confirmation, otherwise an explanation will be given.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> If you remove low numbered lines, you may want to renumber other lines. You can do this by using drag-and-drop in the list to re-order a line item. This can only be done if you have the list sorted by line number (in descending order) <b>and</b> the PO has not had any receipt of goods. When the lines are re-positioned the lines are renumbered starting from 1.</p>
</td>
</tr>
</table>
<p>The window has 3 tab panes.</p>
<p><span class="helpTab"><a href="#tab1">Item Details</a></span> <br />
<span class="helpTab"><a href="#tab2">Additional</a></span> <br />
<span class="helpTab"><a href="#tab3">Planning</a></span> </p>
<h3><a name="tab1" id="tab1"/>Item Details</h3>
<p>Essential base details for the selected order line item.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Part Number</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Our part number. {POLFILE.POLPTNO char 18}</p>
<p>The part number of the part on order. If this field is left blank no default details are provided and it is assumed to be a capital or service item that is not managed in the inventory system. If a part number is entered it must be a pre-defined part in the <a href="../parts/index">Parts</a> section. If it has a Purchase Part record for the Supplier, these details are provided as default. Special provision is made for Job or Work Order Outwork Operations. These are Job or Process Route Operations assigned to an outwork type Work Centre. To order such an operation you construct a pseudo part number in the form of &#8220;WO-NNNNNN-000&#8221; where &#8220;JO-&#8221; indicates a Job and &#8220;WO=&#8221; a WO Operation item, &#8220;NNNNNN&#8221; is the full Job or Work Order number and &#8220;000&#8221; is the Job or Process Route operation number (prefixed with zeros if necessary).</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> You can setup the <b>optPONoEngChange</b> option in <a href="../prefs/wsettings#tab7">Settings Maintenance</a>. If the value is 1, users will be prevented from adding a part which has Engineering-in-Progress set, rather than just being given a warning.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> Normally you are prevented from constructing and outwork operation for a Job or WO unless the Work Center for that operation is an Outwork type. However, you can override this restriction with the <a href="../prefs/woptionslist">option</a> <b>optPOOutOpAllWCs</b>. If set to 1, an operation on a non-outwork work centre can be added to a PO. This enables you to outwork operations normally processed in-house. Such abnormal outwork operations are not subject to the normal updating of costs and are not shown in Capacity Planning WC Mate-To and WC Loading lists and reports.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Part Type</p>
</td>
<td valign="top">
<p align="left">Parts Master. Part type (A,B,M,N,O,P). {PTMFILE.PTMTYPE char 1}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Supplier&#8217;s Part Number</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Supplier part number. {POLFILE.POLSPTN char 18}</p>
<p>Default data for this field is provided from the Purchase Parts record for this Part and this Supplier, if there is a record. It is a useful field for subsequent reviews and report selections.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> If a purchase-part record has been used to populate the PO line item, when you change the supplier&#8217;s part number not known in the purchase-part file, you will be presented with a message: &#8220;Are you changing the purchase part record supplier part number from XXX to YYY? If you click No a new purchase part record will result.&#8221; If you click Yes, when the PO line item is received the purchase-part record will be changed to have the supplier&#8217;s part number YYY. If you click No, a completely new purchase-part will be created for this new supplier&#8217;s part number.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/10013.jpg" width="16" height="16" alt="Show List"/> Show List</p>
</td>
<td valign="top">
<p align="left">Click this button to display a list of alternatives for the field alongside the button. Double-clicking on a list line will enter the value from the list.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> You may have a number of alternative purchase-part records for the same supplier-part combination. Each should have a different supplier part number and can have a different rank value. When you enter a part into a PO the system seeks out any purchase-part records and chooses the one with the lowest rank value and where the rank is the same, the lowest cost. It ignores records where the minimum order quantity rule, if any, is contravened.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Issue</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Part issue reference when part entered on order. {POLFILE.POLISSU char 4}</p>
<p>This field defaults to the current Issue Reference for a Part. You can change it to reflect an alternative to the current issue. It is subject to update in the Masters &#8212; Parts &#8212; Update Issue function.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Description</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Line item description. {POLFILE.POLDESC char 32000}</p>
<p>Default data for this field is provided from the Purchase Parts record for this Part and this Supplier, if there is a record. Otherwise the Part description will be used from the Part file. Additional text can be added. For Job or Work Order Outwork Operations, the default description provides details of the Job or WO. For example, &#8220;Outwork operation 40 for Work Order 000007: 100.000 Each of assy. MET00002 End Bracket for Gb-SC &#8211; Zinc&#8221;.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> The printed descriptive text on the Purchase Order will, in many cases, be more than just the description entered in this field. The following will, if appropriate, be automatically added when the PO is printed:</p>
<ul>
<li><b>Part Items:</b> Any Part individual purchase text.</li>
<li><b>Part Items:</b> Any Part standard purchase text.</li>
<li><b>Part Items:</b> A document in Engineering Data (text, graphic or both) if referenced with the appropriate code in the Part individual purchase text.</li>
<li><b>Outwork Assembly type Part Items:</b> Kit List of the parts to be sent to the supplier for processing.</li>
<li><b>WO Outwork Operations:</b> Any individual or standard instructions for the Process Route Operation of the assembly subject to the WO. Plus Engineering Data if the assembly Part individual purchase text is so coded with the document number.</li>
</ul>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Order Quantity</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Ordered quantity in stock units of measure. {POLFILE.POLQTY number 3dp}</p>
<p>The quantity ordered in Buy UoM. In the PO line item maintenance window an additional Stock UoM quantity is provided. Quantities entered in either will recalculate the other using the Buy UoM Multiplier. If the Ordered Quantity is reduced to the Undelivered Quantity the line item will be deleted.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Purchase Unit or Measure</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Purchase unit of measure. {POLFILE.POLPUUM char 6}</p>
<p>A descriptor for the Supplier&#8217;s Unit of Measure. Default data for this field is provided from the Purchase Parts record for this Part and this Supplier, if there is a record. If no purchase part record exists the Stock UoM is used. The Order quantity and cost relate to the Buy UoM.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Cost</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Cost per purchase unit of measure. {POLFILE.POLCOST number 4dp}</p>
<p>The price charged for the line item by the Supplier per Buy UoM in the currency of the order. Unlike other cost fields, this can be to 4 decimals. The maintenance window shows it in both unit cost and extended value for the entire quantity.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> The default provided for you is as follows:</p>
</p>
<ul>
<li>A normal Part without a Purchase Parts record: The part&#8217;s Current Material Cost multiplied by the Buy UoM Multiplier.</li>
<li>An outwork assembly Part without a Purchase Part record: The part&#8217;s This-Level Outwork Cost multiplied by the Buy UoM Multiplier.</li>
<li>Parts with a Purchase Parts record: The Last Price value from the Purchase Part record or the quantity price if those have been set up.</li>
<li>Job or WO Outwork Operation: ((the operation setup time) times (the work centre setup labour rate plus overhead rate) divided by the work order quantity) plus ((the operation run time) times (the quantity) times (the work centre run labour rate plus overhead rate)).</li>
<li>If the Purchase Order is set for a foreign currency, the above costs will be multiplied by the exchange rate saved for the order at the time of its creation or last currency update. The On-order value in the supplier record always normalises any foreign currency order items into local currency.</li>
</ul>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> You can have a negative cost which provides for supplier bulk discount lines, for example. However, this is only permitted for Non-Part or Non-Stock Part items.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Reference</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. User reference. {POLFILE.POLUSER char 15}</p>
<p>This 15 upper-case character reference can be used for selection in the order items details and purchase history reports. It defaults to the Order Reference. On receipt of the item this reference is saved against the purchase history record and can be used for accounting or other classification reasons.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Delivery Due Date</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Delivery date. {POLFILE.POLDATE date date1980}</p>
<p>The promised or required delivery date for the order line item. In the event of scheduled deliveries of an item. multiple lines must be used. The date is used by MRP to identify when the item will be coming into inventory. It is also used to judge delivery reliability in the analysis of supplier performance.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> Besides individually setting the date of line items, there is a way to set all line items in one go to a particular date or even a date calculated in a custom algorithm. In this case all the above restriction and price calculations are by-passed. This is the process:</p>
<ol>
<li>Right-click on the date field.</li>
<li>Select Date Calculator, or choose that from the ScratchPad main menu.</li>
<li>Calculate a date so it appears in the calculator result (below the Today button).</li>
<li>Click on that result date and drag-and-drop it onto the list of job line items.</li>
</ol>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/custom40-21.jpg" width="24" height="24" alt="Customisation"/><strong> CUSTOM CAPABILITY:</strong> The above date drag-and-drop can be intercepted by <b>oCustom1.$PolDateDrop</b> method which takes the date, document header row and item list as parameters. You could devise a sophisticated re-dating algorithm here to bypass the default behaviour of the drag-and-drop mechanism. There are other possible uses this feature could be put to.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Show Extra Part Text</p>
</td>
<td valign="top">
<p align="left">To show the purchase extra text for part numbered line items. You will be able to change the texts. It opens the <a href="../texts/wtxpedit">Part Purchase Texts</a> window.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Supplier Parts Details</p>
</td>
<td valign="top">
<p align="left">To open the <a href="../purchparts/wpptedit">Purchase Parts Maintenance</a> window.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> If no part line is selected, a list of all purchase parts for the order supplier will be listed. Double-clicking on a subsequent part will add it to the Parts Scratchpad that can be used to drag and drop it back onto the order. This technique can be used before any items have been added to the order.</p>
</td>
</tr>
</table>
<p><a href="#top">Back to top</a></p>
<h3><a name="tab2" id="tab2"/>Additional</h3>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpolmaintsub2.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpolmaintsub2.jpg" width="443" height="124" alt="Purchase Order Line Item Maintenance - Additional pane"/></a></p>
<p>Additional details for the selected order line item.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Order Quantity</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Ordered quantity in stock units of measure. {POLFILE.POLQTY number 3dp}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Buy UoM</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Purchase unit of measure. {POLFILE.POLPUUM char 6}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Undelivered Quantity</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Balance due in purchase unit of measure. {POLFILE.POLBAL number 3dp}</p>
<p>This is an automatically maintained field that shows a value of any outstanding quantity, in Buy UoM, still due for delivery. This provides for multiple deliveries of the line item. If the Ordered Quantity is increased, so will the Undelivered Quantity.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Buy UoM Multiplier</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Multiplier (Stock UM * Multiplier = Purchasing UM). {POLFILE.POLMULT number 4dp}</p>
<p>This is the conversion multiplier to calculate the stock units quantity from the purchase units quantity. Default data for this field is provided from the Purchase Parts record for this Part and this Supplier, if there is a record. The value must be greater than 0.0000 and will be set to 1.0000 for non-part items and when the Buy UoM is syntactically identical to the Stock UoM.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Stock Unit of Measure</p>
</td>
<td valign="top">
<p align="left">Parts Master. Standard stock unit of measure. {PTMFILE.PTMSTUM char 6}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Ordered Quantity in Stock UoM</p>
</td>
<td valign="top">
<p align="left">The quantity ordered in stock units of measure. This will be equal to the ordered quantity in buy units of measure times the buy unit of measure multiplier.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Purchase Account</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. G/L posting account code. {POLFILE.POLACCO char 10}</p>
<p>This field is of specific importance when your program license includes the Ledgers option. It provides for the selection of a purchase type General Ledger account for the posting of the purchase item during supplier invoice verification. However, it can also be used for PO and history report selection. It defaults to the purchase account for the part or the default account for purchases. If you have Ledgers, and no account is entered the default part purchase account will be used. If you do not have Ledgers, you can enter any 10 upper case character code.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong>You can additionally have a list of G/L account group cost centres to select from by using the option <b>optPOShowCostCtrList</b>.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Part Standard Cost</p>
</td>
<td valign="top">
<p align="left">For part number items, this shows the standard material cost for the buy unit of measure.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Part Standard Order Value</p>
</td>
<td valign="top">
<p align="left">The value of the ordered quantity based on the parts standard material cost.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Cost per Buy Unit</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Cost per purchase unit of measure. {POLFILE.POLCOST number 4dp}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Order Value</p>
</td>
<td valign="top">
<p align="left">The ordered quantity value of this purchase line item.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Ordered Date</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Original supplier promised due date. {POLFILE.POLDATO date date1980}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Latest Expected Date</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Latest expected date. {POLFILE.POLDATX date date1980}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Update Purchase Part file on receipt of item</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Purchase part file update on receipt flag. {POLFILE.POLPPTU boolean}</p>
<p>If the System Manager System Preferences have been set to permit automatic update, the checkbox is by default checked for an item with a valid part number. When checked, the Purchase Part record will be updated with the PO item data when received. If there is no record, one will be created. If you un-check this control for a line item, no change to the Purchase Parts file will be made.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">MRP to ignore</p>
</td>
<td valign="top">
<p align="left">Purchase Order Line Items. Ignore in MRP flag. {POLFILE.POLMRP boolean}</p>
<p>Material Requirements Planning takes account of the orders you have placed when assessing the future inventory and when making recommendations for further orders or changes to existing ones. MRP recommends cancelling, pushing and pulling existing Purchase Orders where it assesses such action is needed. In the case of part order line items being placed for parts that will not be the subject of any demand seen by MRP, it will recommend a cancellation of the order item. If you have placed this order for a good reason, this can be annoying and potentially disruptive if the recommendations are followed. If you check the MRP to Ignore option, MRP will ignore the supply that the order implies. MRP results will not show the order receipt and the order quantity will not be included in the predicted stock quantities.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> For order items of Outwork Assembly type parts, MRP will consider the demand for kit parts needed by the supplier for the order, however, it will ignore the projected receipt of the assembly from the supplier. This applies on Requests for Quotation as well.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> You can use this feature to artificially increase the supply temporarily of a component when you do not wish to permanently change the Re-Order Quantity of the part.
</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Outwork Kitted Date</p>
</td>
<td valign="top">
<p align="left">This is not shown on this window but it can be viewed in some line item reports. If the item part is an Outwork Assembly, this date field will contain the date on which outwork kitting was performed, otherwise it will be blank. With ordered outwork assemblies, receipt from the supplier can only occur after kitting.</p>
</td>
</tr>
</table>
<p><a href="#top">Back to top</a></p>
<h3><a name="tab3" id="tab3"/>Planning</h3>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpolmaintsub3.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpolmaintsub3.jpg" width="442" height="125" alt="Purchase Order Line Item Maintenance - Planning pane"/></a></p>
<p>Planning implications of the purchase for a part.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Current Quantities</p>
</td>
<td valign="top">
<p align="left">For details see the <a href="../parts/wptmcurqty">Parts Current Quantity</a> subwindow.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Period Usage</p>
</td>
<td valign="top">
<p align="left">See the <a href="../parts/wptmusage">Parts Usage</a> subwindow for details.</p>
</td>
</tr>
</table>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> Outwork Assemblies will show as Due from W/POs and kit components will be Allocated to WOs until they are issued. PO Kit assemblies, on the other hand, will <b>not</b> show as Due from W/POs but their kit components will, as they are the items that will be received into stock.</p>
<p><a href="#top">Back to top</a></p>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../purchases/wpomaint">Purchase Order Maintenance</a></li>
<li><a href="../parts/wptmcurqty">Parts Current Quantity</a></li>
<li><a href="../parts/wptmusage">Parts Usage</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 4 Jun 2012 04:48:00.00. Class wPolMaintSub last modified 10 Oct 2017  11:48:30.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Line Item Maintenance</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpolmaintsub/">Purchase Orders: Purchase Order Line Item Maintenance</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Purchase Orders: Purchase Order Outwork Items</title>
		<link>https://caliach.com/knowledge-base/wpoloutitems/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpoloutitems/</guid>

					<description><![CDATA[<p>Purchase Orders: Purchase Order Outwork Items</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpoloutitems/">Purchase Orders: Purchase Order Outwork Items</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Purchase Order Outwork Items</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Outwork Items</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpoloutitems.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpoloutitems.jpg" width="364" height="160" alt="Outwork Purchase Order Items"/></a></p>
<p>This window opens by clicking on the <b>View All POs with Outwork Items</b> button on the <a href="wpooutkit">PO Outwork Kit Review and Processing</a> window.</p>
<p>The window lists all Purchase Order line items that are Outwork type parts. Unkitted outwork assemblies will be indicated by having a blank kitted date. Double-click to select and apply a PO to the <a href="wpooutkit">PO Outwork Kit Review and Processing</a> window.</p>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../purchases/wpooutkit">Purchase Order Outwork Kit Review and Processing</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 31 Oct 2001 12:00:00.00. Class wPolOutItems last modified 23 Sep 2017  10:51:01.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Outwork Items</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpoloutitems/">Purchase Orders: Purchase Order Outwork Items</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Purchase Orders: Purchase Order Line Item Report Selection</title>
		<link>https://caliach.com/knowledge-base/wpolprint/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpolprint/</guid>

					<description><![CDATA[<p>Purchase Orders: Purchase Order Line Item Report Selection</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpolprint/">Purchase Orders: Purchase Order Line Item Report Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Purchase Order Line Item Report Selection</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Line Item Report Selection</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpolprint.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpolprint.jpg" width="350" height="268" alt="Purchase Order Item Report Selection"/></a></p>
<p>This report setup window provides you with the ability to choose a range of selections, sort order and report types.</p>
<p>You can drag and drop onto the <b>Print Report</b> button from the Parts or Suppliers ScratchPads to obtain a report of selected parts or suppliers only.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> This window contains fields introduced with version 5 that enable additional search (and sometimes sort controls), such as <b>Adhoc extra where</b>. For more help on their use and examples see the <a href="../sql/introsql">Client-Server SQL Introduction</a> help.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Document Selection</p>
</td>
<td valign="top">
<p align="left">Enter a selection in the <a href="wpolselect">PO Line Item Selection</a> subwindow.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Sort</p>
</td>
<td valign="top">
<p align="left">Choose the field for the primary sort of parts on the report.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Report Type list</p>
</td>
<td valign="top">
<p align="left">Select a report type. Any custom reports entered in the Settings will appear at the bottom of the list.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Monthly</p>
</td>
<td valign="top">
<p align="left">Choose option for Monthly Analysis. This option applies only to Schedule Analysis type reports.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Weekly</p>
</td>
<td valign="top">
<p align="left">Choose option for Weekly Analysis. This option applies only to Schedule Analysis type reports.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Cancel</p>
</td>
<td valign="top">
<p align="left">Aborts the process currently in session. The keyboard equivalent is the Esc key for Windows computers and Command-.(full stop or period) for the Mac.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Print Report</p>
</td>
<td valign="top">
<p align="left">Will cause a report to be printed of the subject matter. Right-click to change the report destination.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../purchases/wpolselect">Purchase Order Line Item Selection</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 3 Jan 2015 11:01:00.00. Class wPolPrint last modified 17 Oct 2017  04:29:55.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Line Item Report Selection</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpolprint/">Purchase Orders: Purchase Order Line Item Report Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Purchase Orders: Purchase Order Line Item Selection</title>
		<link>https://caliach.com/knowledge-base/wpolselect/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpolselect/</guid>

					<description><![CDATA[<p>Purchase Orders: Purchase Order Line Item Selection</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpolselect/">Purchase Orders: Purchase Order Line Item Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Purchase Order Line Item Selection</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Line Item Selection</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpolselect.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpolselect.jpg" width="303" height="165" alt="PO Line Item Selection"/></a></p>
<p>This subwindow is used to define the range criteria for a selection of purchase order line items. It is displayed on windows requiring their selection.</p>
<h4>Parent Windows</h4>
<p><a href="wpolprint">Purchase Order Line Item Report Selection</a><br />
<a href="../advanced/wlinkmaint">Link System Maintenance</a><br />
<a href="../general/wadhocgraphsmaint#tab2">Graphical Analysis Maintenance &#8211; Graphs Tab</a></p>
<h4>Operation</h4>
<p>Enter data in the data entry boxes to restrict the range of parts. Records must meet all criteria entered to be selected. If the left and/or right data entry boxes are left blank for a particular criteria, parts will be selected between the first and/or last otherwise qualifying part record.  Data entry boxes can be populated by finding a single item using <strong>Keyword Search</strong>, drag and drop from the <a href="../scratch/wscratchparts">Parts ScratchPad</a> the <a href="../scratch/wscratchsuppliers">Suppliers ScratchPad</a> or the <a href="../scratch/wscratchgl">Accounts ScratchPad</a>, or by double-clicking a list item from the <a href="../general/wkwdpopup">Keyword Result</a> window.
</p>
<p>Data records can be obtained using one of the following methods or a combination of them (see Tip below):</p>
<ol>
<li>Enter values into the selection ranges and use the <b>Standard Search</b>. The <a href="../general/msearchsub">context menu</a> provides a Clear Selection function.</li>
<li>Define or use a <b>Custom Search</b>.</li>
<li>Create an <b>Ad Hoc Search Calculation</b> using the <a href="../general/msearchsub">context menu</a> function.</li>
<li><b>Drag-and-drop</b> one or more lines from a ScratchPad (or BoM and Where-Used Listing) onto the general window area.</li>
<li>Use the <b>ScratchPad Transfer Selected</b> function</li>
<li>Use the <b>KeyWord Search Transfer Selected</b> function</li>
</ol>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> Using an <b><i>Ad Hoc Search Calculation</i></b> (3) overrides any <b><i>Custom Search</i></b> (2) and a Custom Search overrides the <b><i>Standard Search</i></b> (1). In any of the search cases (1, 2 or 3), ScratchPad Transfer and Drag-and-Drop or KeyWord Search Transfer (4, 5 or 6) is <b>combinational</b>, so that records found using any of these methods must <b>also</b> conform to the search criteria adopted.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-30.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> This window contains fields introduced with version 5 that enable additional search (and sometimes sort controls), such as <b>Adhoc extra where</b>. For more help on their use and examples see the <a href="../sql/introsql">Client-Server SQL Introduction</a> help.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">From and To</p>
</td>
<td valign="top">
<p align="left">Enter data that restricts the records selected. If left blank, data will be selected from the maximum and minimum extremes in the file. All selections criteria you enter will have to be met by each record processed.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Use custom</p>
</td>
<td valign="top">
<p align="left">To turn on and off the use of the custom search design. A custom search will override the standard search.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Custom search name</p>
</td>
<td valign="top">
<p align="left">The name of the currently selected custom search. To use it click on the checkbox. To change it click on the Custom Search button.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Custom Search</p>
</td>
<td valign="top">
<p align="left">Opens the <a href="../general/wsearchselect">Custom Search Selection</a> window and checks the <strong>Use custom</strong> checkbox.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../general/msearchsub">Search Options Menu</a></li>
<li><a href="../purchases/wpolprint">Purchase Order Line Item Report Selection</a></li>
<li><a href="../scratch/wscratchparts">Parts ScratchPad</a></li>
<li><a href="../scratch/wscratchsuppliers">Supplier ScratchPad</a></li>
<li><a href="../scratch/wscratchgl">Accounts ScratchPad</a></li>
<li><a href="../general/wkwdpopup">Keyword Result</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 3 Jan 2015 11:02:00.00. Class wPolSelect last modified 10 Oct 2017  11:48:31.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Line Item Selection</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpolselect/">Purchase Orders: Purchase Order Line Item Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Purchase Orders: Purchase Order Maintenance</title>
		<link>https://caliach.com/knowledge-base/wpomaint/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 16:38:33 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wpomaint/</guid>

					<description><![CDATA[<p>Purchase Orders: Purchase Order Maintenance</p>
<p>The post <a href="https://caliach.com/knowledge-base/wpomaint/">Purchase Orders: Purchase Order Maintenance</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Purchase Order Maintenance</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Maintenance</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpomaint1.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpomaint1.jpg" width="462" height="296" alt="Purchase Order Maintenance - Supplier and Delivery pane"/></a></p>
<p>For an Introduction to Purchase Orders see the <a href="mpurchorder">Purchase Orders Menu</a> topic.</p>
<p>Two files contain the Purchase Order data. Each Purchase Order has a header that contains all information that is general for the PO document as a whole. Associated with a PO are multiple Line Item records that contain details of the specific items under order. The system is self-cleansing in that when items are received from the supplier the associated line items are converted into history records. Hence, PO information on the system only relates to material yet to be received from suppliers.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Purchase Order or RFQ</p>
</td>
<td valign="top">
<p align="left">To print the Purchase Order or RFQ when the order is processed.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Revert to Saved</p>
</td>
<td valign="top">
<p align="left">To revert any changes to the previously saved version.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Save as Shown</p>
</td>
<td valign="top">
<p align="left">To save the changes you have made to the data file.</p>
</td>
</tr>
</table>
<p/>
<h4>Create New PO or RFQ</h4>
<p>When you operate the <b>New Order or RFQ</b> Purchase Order menu function, you are first prompted for a supplier with the <a href="wpurchsup">Supplier Selection</a> window.</p>
<p>The PO maintenance window will be brought forward with no PO Number assigned. When you save the PO, the next available PO number will be assigned to it. The default delivery details, order date and your Transaction ID will be pre-entered. You can change the Delivery Point Code and standard delivery instructions text code. Both must be pre-defined.</p>
<p>You can change the supplier&#8217;s default currency for the order then enter any Special PO Header Text and Entry Comments.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> If you are operating under an MRP environment, you can create Purchase Orders directly from MRP result order recommendations. See the <a href="../mrp/wmrppolist">MRP Purchase Order Recommendations</a> window for details.</p>
<p>If a Supplier has the <b>Do not use</b> flag set, you will not be able to use the Supplier.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> If a supplier has a minimum order value, you can enter this in supplier maintenance and accompany the value with a minimum order rule. If you do this you will be warned when you select the customer and on saving an order that has a value below the supplier&#8217;s minimum order value.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> You can individually limit a user&#8217;s ability to order using a system <a href="../prefs/woptionslist">option</a> <b>optPOUserValueLimits</b>. Enter a  comma separated list made up of UserID, local currency value pairs. E.G. SYS,1000,CR,500 means user SYS is limited to 1000 and CR is limited to 500. Users not listed have no limit. These limits apply to an whole PO and if exceeded the user cannot save the PO and is given a warning message.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> You can impose a PO authorisation procedure using menu security and default settings. Some users can prepare RFQs with only a manager with privileges able to convert them to POs. The <a href="../prefs/woptionslist">option</a> <b>optPORfqToPoInitFix</b> can be set to 1 to prevent the created-by id (POHINIT) being updated to the PO converters ID.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/custom40-21.jpg" width="24" height="24" alt="Customisation"/><strong> CUSTOM CAPABILITY:</strong> You can use the <b>oCustom1.$OnCreatePo</b> method in the OpenVision library to pre-load Purchase Order header fields, such as the reference or texts.</p>
<p>The window has 3 tab panes.</p>
<p><span class="helpTab"><a href="#tab1">Supplier and Delivery</a></span> <br />
<span class="helpTab"><a href="#tab2">Contact Details</a></span> <br />
<span class="helpTab"><a href="#tab3">Line Item Details</a></span> </p>
<h3><a name="tab1" id="tab1"/>Supplier and Delivery</h3>
<p>The order supplier and delivery details.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Supplier Code</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Supplier code. {POHFILE.POHSUPC char 6}</p>
<p>The Supplier must be pre-defined in the <a href="../suppliers/index">Suppliers</a> section. Before the order is created you are required to identify the supplier it is destined for. You can change the supplier after you have created an order, however, not if any line items have been received from it. To do this, either drag and drop a supplier from the <a href="../scratch/wscratchsuppliers">Suppliers ScratchPad</a> or use the <b>Change Order or RFQ Supplier</b> Purchase Order menu function.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Supplier Company Name</p>
</td>
<td valign="top">
<p align="left">Suppliers. Supplier company name. {SUPFILE.SUPNAME char 40}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Purchase Order Number</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Purchase order number. {POHFILE.POHPONO char 6}</p>
<p>By default, the next Purchase Order Number is gained from the System Manager Serial Number Log when you save a newly created PO. This number can not be changed or deleted unless the entire order is deleted.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Request for Quotation</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Request for Quotation (if set to Yes). {POHFILE.POHRELF boolean}</p>
<p>Purchase Orders can be created as Request For Quotation (RFQ) documents. RFQs can be used as documents for supplier bidding purposes. Check the box to make a new Purchase Order a RFQ. An RFQ can be converted into a Purchase Order using the <b>Convert RFQ into Order</b> function on the Purchase Order menu, or you can un-check the checkbox.</p>
<p>With an RFQ the rest of the system effectively ignores line items entered onto it. In other words, part number line items are not recorded in the part&#8217;s  <i>Due from P/WO</i> quantity and do not have PO Preparation inventory history records created. Further, the supplier  <i>On order value</i> does not include RFQ items. RFQ will not be seen in Stock History or  Processing Analysis listings.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/warning40-28.jpg" width="24" height="24" alt="Warning"/><strong> WARNING:</strong> There is an important exception to the general rule that RFQ items are ignored by the rest of the system: MRP Processing WILL see RFQ items as though they were regular Purchase Order items (this can be avoided in the normal way by marking the items as MRP to ignore). This is necessary to ensure that double ordering does not take place and in the normal course of events this is appropriate. If RFQ items were to be ignored as supply, MRP would repeatedly recommend placing new orders, whereas what is required is the conversion of the RFQ into a Purchase Order. RFQ items are distinguished in MRP results with a reference of &#8220;Rnnnnnn&#8221;, as opposed to a Purchase Order that has a reference &#8220;Pnnnnnn&#8221;.</p>
<p>However, there is a circumstance where this approach has to be treated with care:</p>
<p>If an RFQ item is an outwork assembly, MRP will schedule dependant demand for any components needed for it WITHOUT regard for the item&#8217;s MRP to ignore setting. This is fine when you only have one RFQ created for the item (and have not created a number of RFQs to different suppliers as part of a bidding process) and have every intention of converting the RFQ into a Purchase Order. If these conditions are not met, MRP will calculate excess dependant demand for the components.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Reference</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. User reference. {POHFILE.POHUSER char 15}</p>
<p>This 15 upper-case character reference can be used to additionally identify the order in the selection dialogue and order summary reports. It also acts as the default for each order line Item Reference.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Currency</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Currency code (blank = default). {POHFILE.POHCUR char 3}</p>
<p>The currency of values in the PO is set by the currency symbol assigned to the order. If it is a foreign currency, the exchange rate at the time the order was created, or subsequently re-valued, is also stored in the PO header record. When first created, the default currency held against the supplier is applied which you can change if you wish.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Exchange Rate</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Currency rate applicable when order created. {POHFILE.POHRATE number float}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Order Date</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Date of issue of purchase order. {POHFILE.POHDATE date date1980}</p>
<p>This is automatically entered as the current active Buy Calendar date when the order was created. It is used to subsequently calculate ordered lead times.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Creator&#8217;s User Id</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. PO creator&#8217;s initials. {POHFILE.POHINIT char 3}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Delivery Point Code</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Delivery details code. {POHFILE.POHDPC char 2}</p>
<p>A two character code that defines the Delivery address and instructions printed on the Purchase Order. The default code is set in the System Manager <a href="../system/wmcdedit">Company Details Maintenance</a> window. Associated with the DPC is the delivery address and instructions, however, this text is not editable by you while entering a PO. See the <a href="../system/wdeledit">Goods-Inwards Delivery Details Maintenance</a> window for details.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Show</p>
</td>
<td valign="top">
<p align="left">Click this button to display a list of alternatives for the field alongside the button. Double-clicking on a list line will enter the value from the list.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Delivery Point List</p>
</td>
<td valign="top">
<p align="left">Lists all delivery point codes. Double-click on a line to enter it.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Delivery Address</p>
</td>
<td valign="top">
<p align="left">Delivery Details for POs. Delivery name and address. {DELFILE.DELADR char 200}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Delivery Instructions</p>
</td>
<td valign="top">
<p align="left">Delivery Details for POs. Purchase Order delivery instructions text. {DELFILE.DELDETX char 500}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Standard Delivery Text Code</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Delivery instructions std text. {POHFILE.POHTXCD char 4}</p>
<p>Associated with the DPC is a Standard delivery instructions text. This can be changed for a specific order to another Standard Purchasing Text. See the <a href="../texts/wtxtedit">Standard Text Maintenance</a> window for details.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Show</p>
</td>
<td valign="top">
<p align="left">Click this button to display a list of alternatives for the field alongside the button. Double-clicking on a list line will enter the value from the list.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Standard Text List</p>
</td>
<td valign="top">
<p align="left">Lists all purchase standard texts. Double-click on a line to enter it for this delivery details record.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Standard Text</p>
</td>
<td valign="top">
<p align="left">Standard Texts (E,P,S,W). Text. {TXTFILE.TXTTEXT char 10000000}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Header Text</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Special PO header text. {POHFILE.POHPOTX char 10000000}</p>
<p>This field provides for special text that is appended to the header of the PO. This text is printed in addition to any text recorded in the supplier record for the purpose. It can be used for special instructions, for example.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">P.O. Entry Comments</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Order processing office notes and comments. {POHFILE.POHOPCO char 10000000}</p>
<p>This field provides for comment text that is not printed on the PO document. It can be used for special comments such as tracking details or quotation information. The information is available during reviews and is optionally printed on PO reports.</p>
</td>
</tr>
</table>
<p><a href="#top">Back to top</a></p>
<h3><a name="tab2" id="tab2"/>Contact Details</h3>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpomaint2.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpomaint2.jpg" width="449" height="245" alt="Purchase Order Maintenance - Contact Details pane"/></a></p>
<p>Contact details of telephones etc.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Account Number</p>
</td>
<td valign="top">
<p align="left">Suppliers. Supplier&#8217;s account number for the user. {SUPFILE.SUPACNO char 15}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Account Details</p>
</td>
<td valign="top">
<p align="left">Suppliers. Account details with supplier. {SUPFILE.SUPACDE char 40}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Order Limit</p>
</td>
<td valign="top">
<p align="left">Suppliers. On-order value limit (exclusive of tax) in local currency. {SUPFILE.SUPLIMT number 3dp}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Currently On-Order</p>
</td>
<td valign="top">
<p align="left">Suppliers. Current on-order value (exclusive of tax) in local currency. {SUPFILE.SUPORDR number 3dp}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Account Balance</p>
</td>
<td valign="top">
<p align="left">Suppliers. Current account balance in local currency. {SUPFILE.SUPCBAL number 2dp}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left"> </p>
</td>
<td valign="top">
<p align="left"><i>User Defined Fields</i></p>
<p>These fields are available for any use you wish to put them. They are passed to purchase history. They are not otherwise used or reported by the system and are provided for use with custom searches or reports or Ad Hoc reports. There are 4 character fields that are limited to 1, 4, 18, and 30 characters respectively. The field descriptions are set in File &#8212; System Manager &#8212; <a href="../system/wmcdedit#tab2">Company Details Maintenance</a> window Descriptions tab pane.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-27.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> You can selectively get the system to inherit customer record user defined field data onto Purchase Orders. This is done by setting the following system <a href="../prefs/woptionslist">option</a>:</p>
<ul>
<li><b>optPOInheritsUserFields</b></li>
</ul>
<p>The option value is set to 1234, or any combination of those numbers. It will cause those Purchase Order user defined fields to be inherited from the supplier fields.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">User 1</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. User character field 1 (single character). {POHFILE.POHUSE1 char 1}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">User 2</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. User character field 2 (4 characters). {POHFILE.POHUSE2 char 4}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">User 3</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. User character field 3 (18 characters). {POHFILE.POHUSE3 char 18}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">User 4</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. User character field 4 (30 characters). {POHFILE.POHUSE4 char 30}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Source/Factoring address, etc</p>
</td>
<td valign="top">
<p align="left">Shows the selected Order Address. Use the button to change to an alternative Address.</p>
<p>An order can use a supplier&#8217;s additional address to identify one of several supplier branches from which the order is being placed. Alternatively, you can use this to identify on the order a Factoring address.</p>
<p>Right-click on this field to obtain print functions for the currently selected address and contact:</p>
<p><img loading="lazy" decoding="async" src="../customers/graphics/defaultadrmenu.jpg" width="328" height="173" alt="Address and Contact additional context menu functions."/></p>
<p>Print Standard Letter opens the <a href="../market/wmarketletterprint">Standard Letter Selection</a> window and Print 4&#215;4 Label opens the <a href="../market/wmarketlabelpos">4 by 4 Label Position</a> window.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Default supplier address</p>
</td>
<td valign="top">
<p align="left">Select this option to load the default supplier address.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Alternative address</p>
</td>
<td valign="top">
<p align="left">Select this option to choose an alternative address.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Change</p>
</td>
<td valign="top">
<p align="left">To create or select an alternative address that would be applied to this Purchase Order.</p>
<p>An order can use a supplier&#8217;s alternative address to identify one of several supplier branches from which the order is being placed. Alternatively, you can use this to identify on the order a Factoring address. The <a href="../customers/wadrselect">Address Selection</a> window is brought forward.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Contact</p>
</td>
<td valign="top">
<p align="left">The full name of the supplier&#8217;s contact with the given name in brackets.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Incoterm</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Incoterm code (Blank or IDXTYPE=9). {POHFILE.POHINCO char 4}</p>
<p>Incoterms are the internationally agreed method of designating trading transactions which cross national borders. They define the limits of commercial responsibility for the selling party and so clearly define the limits of cost of the delivery of the goods. In the system they are defined in File &#8212; System Manager &#8212; <a href="../system/widxedit">Index Codes</a>. An Incoterm generally requires a parameter which is usually a place or port name. The default Goods-Inwards Delivery Details Incoterm becomes the default for purchase orders.  A Purchase Order Incoterm will be copied to any resulting purchase history.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Incoterm description</p>
</td>
<td valign="top">
<p align="left">Index and Other Codes. Index code, scrap reason, QA test or Incoterm description. {IDXFILE.IDXDESC char 255}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Show</p>
</td>
<td valign="top">
<p align="left">Click this button to display a list of alternatives for the field alongside the button. Double-clicking on a list line will enter the value from the list.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Incoterm Place</p>
</td>
<td valign="top">
<p align="left">Purchase Order Headers. Incoterm parameter (usually a named place or port). {POHFILE.POHINCP char 60}</p>
</td>
</tr>
</table>
<p><a href="#top">Back to top</a></p>
<h3><a name="tab3" id="tab3"/>Line Item Details</h3>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wpomaint3.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wpomaint3.jpg" width="449" height="246" alt="Purchase Order Maintenance - Line Item Details pane"/></a></p>
<p>Line Items of the order. This pane consists entirely of the <a href="wpolmaintsub">Purchase Order Line Item Maintenance</a> subwindow.</p>
<p><a href="#top">Back to top</a></p>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../purchases/mpurchorder">&#8211; Purchase Orders Menu</a></li>
<li><a href="../purchases/wpolmaintsub">Purchase Order Line Item Maintenance</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 4 Jun 2012 04:48:00.00. Class wPoMaint last modified 23 Sep 2017  10:51:00.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-30.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Purchase Orders</a> &gt; Purchase Order Maintenance</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wpomaint/">Purchase Orders: Purchase Order Maintenance</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
