{"id":1679,"date":"2017-08-11T14:07:57","date_gmt":"2017-08-11T13:07:57","guid":{"rendered":"http:\/\/vger.datos.co.uk\/ClientKnowledgebase\/?p=1679"},"modified":"2017-08-11T14:07:57","modified_gmt":"2017-08-11T13:07:57","slug":"how-to-set-up-a-traceability-profile","status":"publish","type":"post","link":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/?p=1679","title":{"rendered":"How to set up a Traceability Profile"},"content":{"rendered":"<p>Traceability Profiles allow the system to record traceability information (batch numbers, use by and pack dates etc&#8230;) as a product flows from Goods in, through Production to dispatch at Goods Out.<\/p>\n<p>In order to know what traceability information should be recorded for a product, the system allows Traceability Profiles to be set up against the product groups.<\/p>\n<h2>Creating a Traceability Profile<\/h2>\n<p>The main Traceability Profile setup program is located under the &#8216;General Setups&#8217; menu in Product Setup. (An Additional Traceability Profile setup for production templaste is located in the Production Template program)<\/p>\n<p>To load the Traceability Profile setup program,<\/p>\n<ol>\n<li>From the Operations menu load Product Setup by clicking on Product Management -&gt; Product Setup<\/li>\n<li>Then, from the Product Setup program, click on &#8216;General Settings&#8217; -&gt; &#8216;Traceability&#8217;<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-53 aligncenter\" src=\"http:\/\/vger.datos.co.uk\/ClientKnowledgebase\/wp-content\/uploads\/2017\/04\/ProductGeneralSetupsTraceability.png\" alt=\"\" width=\"174\" height=\"141\" \/><\/p>\n<ol start=\"3\">\n<li>This will load the Traceability Profile setup program.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1681 aligncenter\" src=\"http:\/\/vger.datos.co.uk\/ClientKnowledgebase\/wp-content\/uploads\/2017\/08\/TraceabilityProfileSetupProgram.png\" alt=\"\" width=\"714\" height=\"528\" \/><\/p>\n<ol>\n<li>Clear any loaded data by clicking in the &#8216;Trace Profile Code&#8217; field and pressing F5<\/li>\n<li>Enter in the new Traceabilty Profile Code and Description.<\/li>\n<li>Click on the Save button at the tome of the screen, press F2, or click in to one of the detail grids to save the header.<\/li>\n<\/ol>\n<p>Now that the header has been saved we can add trace codes to the various input grids. <a href=\"http:\/\/vger.datos.co.uk\/ClientKnowledgebase\/?p=47\">For information on setting up trace codes, click here.<\/a><\/p>\n<p>There are various sections for traceability input. These are,<\/p>\n<ul>\n<li><strong>Goods In Input<\/strong> &#8211; anything entered here will be required when booking in purchase orders<\/li>\n<li><strong>Production Input<\/strong> &#8211; anything entered here will be required when producing products through jobs<\/li>\n<li><strong>Dispatch Inpu<\/strong>t &#8211; anything entered here will be required when allocating product to sales order through Good Out<\/li>\n<li><strong>Freezer Input<\/strong> &#8211; Currently for reference only when freezing products.<\/li>\n<li><strong>Off Site Input<\/strong> &#8211; currently for reference only when sending stock to an offsite location<\/li>\n<\/ul>\n<p>To enter a trace code against a traceability section,<\/p>\n<ol>\n<li>Click in to the next empty row in the grid<\/li>\n<li>Enter in a sequence number in to the Seq column. The sequence number determines the order that the trace codes will appear in Factory<\/li>\n<li>Select the Code from the Trace Code popup by pressing the pop up button or pressing F4<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1685 aligncenter\" style=\"font-size: 16px;\" src=\"http:\/\/vger.datos.co.uk\/ClientKnowledgebase\/wp-content\/uploads\/2017\/08\/TraceProfileSetupGrid.png\" alt=\"\" width=\"682\" height=\"342\" \/><\/p>\n<ol start=\"4\">\n<li>Tab to across to finish the line and save<\/li>\n<li>To delete a line, select it on the grid and press F2.<\/li>\n<\/ol>\n<p>In this way enter in the required trace codes to each section<\/p>\n<p>The &#8216;Entry Type&#8217; field at the bottom of the windows shows the entry type required for the trace code item.<\/p>\n<p>If the entry type is &#8216;Date&#8217; there are some additional options.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1686 aligncenter\" src=\"http:\/\/vger.datos.co.uk\/ClientKnowledgebase\/wp-content\/uploads\/2017\/08\/TraceProfileSetupGridDateTraceCode.png\" alt=\"\" width=\"673\" height=\"304\" \/><\/p>\n<ul>\n<li><strong>Date Based On\u00a0<\/strong>&#8211; This allows the date in this section to be based on the date for a previous section or &#8216;TODAY&#8217;. If based on a previous section, the date entered will be copied to this trace item. e.g. a kill date from the goods in section could be copied to a kill date in the production section. If this is blank the date will not be defaulted and will require entry by an operator<\/li>\n<li><strong>Shelf Days\u00a0<\/strong>&#8211; Setting this will add the appropriate numbers of days on to the initial date. The options here are taken from the internal and external shelf days in Product Setup<\/li>\n<li><strong>+\/- Days\u00a0<\/strong>&#8211; Setting a +\/- number of days will add this number of days on to the final date.<\/li>\n<\/ul>\n<h3>Editing an existing Traceability Profile<\/h3>\n<p>To edit an existing Traceability Profile,<\/p>\n<ol>\n<li>Click in to the Trace Profile Code field and press F5 to clear any current data<\/li>\n<li>Press F4 or use the popup button to load the Traceability Profile.<\/li>\n<li>Simply make any changes necessary to the requires traceability sections.<\/li>\n<\/ol>\n<h3>Copying an existing Traceability Profile<\/h3>\n<p>Instead of setting a traceability profile up from scratch, a Traceability Profile can be created by copying another.<\/p>\n<p>To copy a Traceability Profile,<\/p>\n<ol>\n<li>Click in to the Trace Profile Code field and press F5 to clear any current data.<\/li>\n<li>Press F4 or use the popup button to load the Traceability Profile to be copied<\/li>\n<li>Click on the Wizard icon\u00a0<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-1689\" src=\"http:\/\/vger.datos.co.uk\/ClientKnowledgebase\/wp-content\/uploads\/2017\/08\/WizardIcon.png\" alt=\"\" width=\"42\" height=\"44\" \/>\u00a0. This will load the Copy Trace Wizard.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1688 aligncenter\" src=\"http:\/\/vger.datos.co.uk\/ClientKnowledgebase\/wp-content\/uploads\/2017\/08\/TraceProfileSetupCopyProfile.png\" alt=\"\" width=\"558\" height=\"462\" \/><\/p>\n<ol start=\"4\">\n<li>Now, simply enter in the new Trace Profile Code and Description.<\/li>\n<li>The Options section allows the complete trace profile to be copied or an individual trace section.<\/li>\n<li>Click on the save icon to create the new Traceability Profile.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Traceability Profiles allow the system to record traceability information (batch numbers, use by and pack dates etc&#8230;) as a product flows from Goods in, through Production to dispatch at Goods Out. In order to know what traceability information should be recorded for a product, the system allows Traceability Profiles to be set up against the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,5,20],"tags":[59,217],"class_list":["post-1679","post","type-post","status-publish","format-standard","hentry","category-howtofactory","category-howtoguides","category-howtooffice","tag-traceability","tag-profile"],"_links":{"self":[{"href":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/index.php?rest_route=\/wp\/v2\/posts\/1679","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1679"}],"version-history":[{"count":0,"href":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/index.php?rest_route=\/wp\/v2\/posts\/1679\/revisions"}],"wp:attachment":[{"href":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1679"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1679"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vger.datos.co.uk\/Clientknowledgebase\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1679"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}