Manual copyright © 2019 WilloWare Incorporated. All rights reserved. Your right to copy this documentation is limited by copyright law and the terms of the software license agreement. Only the software licensee may use this documentation. Making unauthorized copies, adaptations, compilations, or accessing the web-based version by direct linking, or sharing the web-based version with unlicensed users, or making derivative works for commercial distribution or other use is prohibited, and constitutes a punishable violation of the law.
Great Plains, Dynamics, and Dynamics GP are either registered trademarks or trademarks of Great Plains Software, Inc. in the United States and/or other countries. Great Plains Software, Inc. is a wholly-owned subsidiary of Microsoft Corporation. The names of actual companies and products mentioned herein may be trademarks or registered marks – in the United States and/or other countries – of their respective owners. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.
WilloWare Incorporated disclaims any warranty regarding the examples contained in this documentation, including the warranties of merchantability and fitness for a particular purpose.
Limitation of liability
The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by WilloWare Incorporated. WilloWare Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in this manual. Neither WilloWare Incorporated nor anyone else who has been involved in the creation, production or delivery of this documentation shall be liable for any indirect, incidental, special, exemplary or consequential damages, including but not limited to any loss of anticipated profit or benefits, resulting from the use of this documentation or sample code.
Use of this product is covered by a license agreement provided with the software product. If you have any questions, please call WilloWare Incorporated at 866-33-WILLO, or email email@example.com.
The installation process for all WilloWare products is identical. Please review the general installation instructions at www.willoware.com/install.
The Installation routine will automatically create a Security Task called IPT, and a Security Role called IPT.
The Task will have access to all windows in Item Process Tracking, and the Task will be assigned to the Role.
To give a user access to Item Process Tracking you can either assign the Task to an existing Role, or assign the new IPT Role to a user.
Do NOT modify the IPT Security Task. Each time an update is installed for Item Process Tracking it will recreate the Task to ensure it has access to everything in the suite, and any changes will be lost.
The About window in your WilloWare product or customization can be located by going Help >> About Microsoft Dynamics GP:
The Dynamics GP Help button is the blue question mark in the upper-right-hand corner of the main GP window.
Then go to Additional >> select your WilloWare product:
When contacting WilloWare Support, you may be asked to provide the information from this window. You can copy-paste the text directly out of the window, or automatically create an email containing the information by clicking the “Email to WilloWare” link.
The About window provides of information about the installed WilloWare product, the status of the installation, and server configuration.
The first section displays your Site Name and the build information of the software. The registration key contains the Site Name. A mismatch between the Site Name shown in GP (which is displayed in this window), and the Site Name used to generate your registration key, is a common cause of registration failure. You can copy-paste the Site Name from this window into an email to ensure we have the correct Site Name.
What version do I have installed? The complete version number is Major Version & Minor Version & Build Number. For example: 16.0.6.
The next section displays the status of the software on the current client, and a list of your company databases and the status of the software in each company.
Installation Status: when a new version of your WilloWare software is installed, it will update the build information in a tracking table in the database. If the version information stored in the database is different than the version information contained in the software on the GP client, the Installation Status message will alert you. The client could have a newer version (in which case you need to run the Installation routine inside GP to update the server), or the client could have an older version (in which case you need to install the latest build on the GP client), or the versions match.
Company Status: during installation you select which companies you want to enable. If the software is Enabled for a company, the product navigation will be added to menus, and other functionality will be active. If the software is Disabled, it will be “invisible” inside that company.
The next section displays the DYNAMICS.SET file from the GP client.
This tells you the name of the SET file (which is helpful if you use multiple SET files), and information about each module loaded on the client. This list can be rather long. Towards the end of the SET file section you will find paths to each of the product files:
This information is helpful when attempting to locate modified forms and reports dictionaries. Note that the path information occurs in groups of three, listing the path to the application dictionary, the forms, and then the reports.
The next section shows database information for each database on the server.
The DYNAMICS database (or named System Database), and your Company Databases are the important entries. In particular, pay attention to the Sort Order information. Normally SQL Server is configured for Dynamics GP with case-insensitivity. This mean that “ITEM”, “Item” and “item” are all treated as the same word. If your database is CASE-SENSITIVE, please be sure to mention this when contacting support. It is very important.
The final section of the About window displays version information for WilloWare Internal Resources.
This is information we use when troubleshooting, or updating the product to ensure you have the most up-to-date functionality.
WilloWare products and customizations use the same About window. When the window is opened by “SA” or “DYNSA”, WilloWare Products have additional options on the Help menu (shown below).
The About window provides access to the Installation Window and Registration Window.
Enter your Dynamics GP Registration Keys before attempting to register your WilloWare software.
WilloWare software is fully functional in Fabrikam without entering registration keys. It will also be fully functional with or without keys in any <TEST> Company Database. You must put <TEST> into the Company Name. The <TEST> company feature allows you to test other features of WilloWare software without changing your live company registration keys.
Navigation: Tools >> Setup >> System >> Registration
From the Dynamics GP Registration window, select Additional >> Register GP PowerPack (or the name of your WilloWare software, such as MFG PowerPack or LabelLink).
The Registration window is identical for all WilloWare products. The example below uses GP PowerPack.
If you purchased your GP License from Microsoft, and your Site Name (see the GP Registration Window) matches your Organization’s Name, select “Based on Site Name”.
If you are hosted, and your Site Name is the name of your Hosting Company, select “Based on SQL Instance”. If you have access to SQL Management Studio, you can retrieve the SQL Instance Name by running this query in any database:
If the Registration Window shows the “wrong” SQL Instance name, the server may have been created from an image and the SQL Server not renamed correctly. Please see these instructions on Microsoft Technet for more information:
NOTE: if the link does not work, Google the phrase above to find the article
Depending on the Key Type, this field will display either the Site Name from the GP Registration window, or the SQL Server Instance name. You can copy the text from this field and email it to WilloWare to assist in generating the correct registration key.
GET KEY ONLINE
You can retrieve the key electronically by clicking the Get Key Online button. You can only have one active, electronic key at any given time. When you request a new key (i.e. for the latest version of GP), it will replace the older version of the electronic key. This does not mean the older version of the software will stop working. However, if you click Get Key Online in the older version of GP, it will retrieve the new key, which will be invalid for the old version of GP.
If you Get Key Online, skip down to Key Validation below.
You when purchased the software you received a Registration File. For example:
This file is NOT human-readable. It is imported into the software by the Registration window.
To import the Registration Key File, click the Folder button.
Click the OPEN button.
On the Registration window, click VALIDATE.
There are several pieces of information checked when you click Validate (or Get Key Online), and errors will be displayed if any of the checks fail. It checks the “KEY” value (i.e. information coded in the registration key) to the “GP” value (i.e. the GP Site Name, Version Number, Product ID, etc). If all of the validations pass (green checkbox), click SAVE.
Site Name: The Registration window will check that either the Site Name, or the SQL Instance name, matches the information provided to WilloWare.
Version: checks that the Major Build Number of software you requested from WilloWare matches the Dynamics GP version. If you requested GP2015 but are installing GP2016, it will create a Version Error because the Key will be for GP2015.
Product ID: checks that the WilloWare software your purchased is what is installed. Each product has a 4-digit Product ID provided by Microsoft. If you purchased GP PowerPack, but installed LabelLink, it will create a Product ID error.
Software Version: checks that the WilloWare software version matches the GP version. If you installed GP PowerPack for GP2015 into a GP2016 system, it will generate a Software Version error.
Expiration: for temporary keys, or yearly license keys, a check is performed to validate that the expiration date encoded in the key is a date in the future. WilloWare software regularly checks the Expiration Date, and when the key expires, it will disable the module.
Item Process Tracking, IPT, is designed to address the need to record specific information about an item, or a process on or with the item, when that item is used on a specific type of transaction. For example, it can be used when receiving an item on a Service RMA to record the condition of the returned item and several return process steps. Or, IPT might be used when receiving an item on a Manufacturing Order to record a post-production checklist. IPT could also be used during Sales Invoicing to record that packing/prepping steps were completed.
The “set of data fields” to be collected and “steps to be completed” for an item on a GP transaction are collectively called a Data Sheet. A Data Sheet is similar to an Excel workbook with a list of fields to be filled-out.
Think of a Data Sheet as an empty template—it has the fields you want to record, and perhaps instructions on what to do.
A Data Sheet is a collection of user-defined fields which need to be recorded for an Item when the item appears on a specific type of transaction. IPT supports two general types of fields on a Data Sheet:
- Attributes are “observed” characteristics, such as a name or date or assessment of grade
- Variables are “measured” characteristics which are always numeric
Each Data Sheet is assigned to one, and only one, type GP transaction, such as an RMA. Each Data Sheet is also linked to one or more Items. The result tells the IPT module that, for example, when 128 SDRAM in on a PO Receipt, use Data Sheet “PO RECEIPT”.
You can have an unlimited number of Data Sheets assigned to each GP Transaction Type, so if each class of Items needs different data recorded or processes performed, you can create on Data Sheet for each class of items.
These transaction types are supported:
- Inventory Adjustment / Variance
- Inventory Transfer
- Manufacturing Component Issue
- Manufacturing Order
- Manufacturing Receipt
- PO Receipt
- RMA (Service Module)
- Sales Invoice
- Sales Order
- Sales Return
When an Item is used on a transaction where the transaction and item are assigned to the same Data Sheet, IPT creates a Data Record. The Data Record is a numbered copy of the Data Sheet created for that specific GP transaction and Item Number.
Think of a Data Record as a copy of the empty template. In a paper-based system, the Data Record is a photo-copy of the Data Sheet. This is the copy you will write on to record information.
The Data Record is where you enter the information required for an item. When completed, the Data Record is “posted”, or moved to history, where it is no longer editable.
Setting up IPT is done in the following order:
Record Numbers: set up numbering sequences for each of the GP Transactions where you will record information about your items. Each GP Transaction must have a different numbering sequence.
Data Sheets: At a minimum you will need to create one Data Sheet for each GP Transaction you want to support with IPT. If different items, or groups of items, require different data collection or processes for a given GP transaction, you will need to create more than one Data Sheet for that GP transaction.
Item-Data Sheet Maintenance: An Item can be assigned to multiple Data Sheets per GP transaction, and a Data Sheet can be linked to multiple items. An Item might have several Data Sheets for Manufacturing, where different data needs to be recorded on three different sequences. The same item might have another Data Sheet for when it is returned on an RMA.
Routings: this optional setup can be used to direct the Data Recording task to specific users. When Routings are enabled, a GP Reminder will be auto-created when a GP transaction is entered where the transaction and item are linked to a Data Sheet.
Record Numbers are document numbers for each Dynamics GP Transaction where you will use IPT. For example, if you will record an Item Data Record for RMA’s and Manufacturing Orders, you need to create Record Numbers for those two transactions. The other transactions can be left blank.
NAVIGATION: Tools >> Setup >> Inventory >> IPT Setup
Enable PO Rev – Data Sheet Rev Link: if you have WilloWare’s Manufacturing PowerPack installed, this option will be available, otherwise the checkbox will be locked. The PO Rev Link checks the Rev Level of an item on a PO Line when it is received and attempts to create a Data Record using the assigned Rev Level.
For example, if the PO Line Rev for an item is 1.2, but the current Data Sheet Rev is 2.0, the Data Record will be created using the 1.2 version of the Data Sheet.
If IPT Routings are used, and a Data Record is created automatically when the PO Receipt is posted, the Data Record will be created using the PO Rev (if it matches an existing Data Sheet Rev). If no matching rev can be found, the Data Record will be created using the current rev of the Data Sheet.
When manually entering a Data Record where the Source Document is a PO Receipt, if the PO Line Rev matches a non-current Data Sheet, you will be prompted to choose if you want to create the Data Record using the PO Rev, the Current Rev, or to manually pick a different rev.
Record Numbers: Make sure that each numbering sequence is unique (i.e. do not use IPT0001 for each transaction type) and has enough zeros in the number to allow for future use (i.e. IPT 001 only allows 999 transactions). You only need to provide Record Numbers for transactions you will use in IPT.
8.Data Sheet Maintenance
Data Sheet Maintenance is used to create/maintain the list of fields to be recorded for an item when it appears on a GP transaction.
NAVIGATION: Cards >> Inventory >> Data Sheet Maintenance
COPY: See the section Copying a Data Sheet.
Data Sheet ID: Enter an ID to identify the Data Sheet.
Data Sheet ID Note: IPT makes use of Notes to provide additional information on the reports. The Data Sheet Note will print at the top of the Datasheet report, and also on the Data Record report.
Description: Provide a description for the Data Sheet
Source Doc: Each Data Sheet can be assigned to only one transaction. If the same information needs to be recorded on another transaction, you will have to create a second Data Sheet. See the section below on Coping a Data Sheet.
Version: The Version Number is a required field. By default, all new Data Sheets will be set to 1. You can change this to a different value if needed. This is an alphanumeric field.
If you change the Version Number on an existing Data Sheet, you will be asked:
Do you want to store a Revision of the current Data Sheet?
If you answer YES, see section below about Versioning a Data Sheet.
If you answer NO, you will be asked:
Do you still want to change the Version Number?
If you answer NO again the Version Number will revert back to the original value.
If you answer YES, the new Version Number will be used without saving the prior version to history.
Add Attribute: Click this button to open the Attribute Maintenance window. See the section Attribute Maintenance for more information.
Add Variable: Click this button to open the Variable Maintenance window. See the section Variable Maintenance for more information.
Edit: Edit an existing Attribute or Variable either by selecting it in the tree-view then clicking Edit, or by double-clicking it in the treeview.
When you change the Version Number on an existing Data Sheet you will be asked if you want to store a revision of the Data Sheet. A revision is a complete, un-editable copy of the Data Sheet:
- The Data Sheet header is copied and moved into the revision tables. If a note is attached to the Data Sheet, it is copied to a new note attached to the revisioned Data Sheet.
- The Data Sheet Attributes and Variables are copied and moved into the revision tables. Any notes attached to an Attribute or Variable is copied and attached to the revisioned Attribute/Variable.
- For “String – Lookup” type Attributes, the list of allowed lookup values is also copied and stored with the revision.
Because the notes are copied from the Data Sheet, the Attributes and the Variables, a revisioned Data Sheet will reflect the complete record at the time the revision was made.
IPT also controls whether or not Notes are editable. For example, the DS Note is editable on the Maintenance window, but is NOT editable when the same DS is viewed in the Inquiry window. This will be discussed further where the note locking is applied.
The historical versions are viewable in the Data Sheet Inquiry window (as is the current version).
An entire Data Sheet can be copied to create a new Data Sheet. The new Data Sheet will default to a Version Number of 1.
To copy a Data Sheet:
- Select an existing Data Sheet
- Click the Copy button
Enter a new Data Sheet ID, then click OK
The DS Note, and any Attribute or Variable Notes will be copied to the new Data Sheet. The note will contain the same information as the original note, but it is a new note attached to the new Data Sheet/Attribute/Variable.
Attributes are observed, qualitative attributes of an item or process. For example, COLOR could be an attribute if it is recorded as RED or BLUE. However, it could also be a variable if the wavelength of emitted light is recorded as 650nm or 475nm.
Attribute ID: Enter an ID for the Attribute. An Attribute ID cannot be repeated on a Data Sheet.
Notes Button: The NOTE button can be used to store a longer description for the Attribute. For example, it can be used to record instructions on how to observe and record the attribute. The notes will print on the Datasheet and Datarecord reports, and will be available in the Data Record Entry window.
Description: Enter a description for the Attribute. The description will appear as the “prompt” in the Data Record Entry window, so a Description like “Enter Agent ID” may be preferable to just “Agent ID”.
Position Number: By default, the system will set the Position Number to the next available increment of 10. If you have entered 10, 20, and 30, you can insert a new Attribute at 11 by keying in Position Number 11 when creating a new Attribute.
Use Position to control where Attributes and Variables appear in the Plan. NOTE: Attributes and Variables cannot have overlapping Position numbers. IPT will warn you if a Position Number you manually entered overlaps with an existing Position Number.
Type: The Type controls the datatype used for the field. The options are:
- Checkbox: The Data Record Entry window will show the Attribute Description and provide a checkbox.
- Date: The Data Record Entry window will show the Attribute Description and a date field.
- String – Free Type: The Data Record Entry window will show the Attribute Description and a blank, 50-character string field.
- String – Lookup: When Lookup is selected, the Lookup Values button becomes enabled. For Lookup fields you must also create a list of allowed values. The Data Record Entry window will allow the user to type in one of the pre-defined values or select a valid value from a Lookup. Invalid entries will not be accepted.
- Customer Number: The Data Record Entry window will display a Customer Number field. The user can type-in a valid Customer Number or select one from the Lookup.
- Serial / Lot Number: The Data Record Entry window will display a Lot Number field. The Lot Number lookup will show ALL Lot Numbers for the Item on the Data Record Entry window.
- User ID: The Data Record Entry window will display a User ID field. The user can enter a valid User ID or select one from the Lookup.
- Vendor ID: The Data Record Entry window will display a Vendor ID field. The user can enter a valid Vendor ID or select one from the Lookup.
Variables are properties that are measured. For example, COLOR would be a variable if the wavelength of emitted light is measured, such as 650nm or 475nm. However, it could also be an attribute if the color is observed and as RED or BLUE.
Variable ID: Enter an ID for the Variable. Each ID can be used only once on a Data Sheet.
Variable ID Note: Use the note to provide detailed instructions or additional information. The note will print on the Datasheet and Datarecord reports, and will be available on the Data Record Entry window.
Description: Enter a description for the Variable. The description will appear as the “prompt” in the Data Record Entry window, so a Description like “Run CPU Benchmark” may be preferable to just “CPU Score”.
Decimals Places: Defines the precision of the measurement.
The fields below Decimal Places provide for recording user-defined reference values. The labels and values will appear in Inspection Entry. For example, as shown above, these fields might record the expected Min/Max values of the CPU Benchmark and the Unit of Measure (GHz). These fields are informational. The Data Record Entry window will allow entering ANY value above, below, or between the values entered here.
9.Data Sheet Inquiry
Data Sheet Inquiry is a view-only version of Data Sheet Maintenance. It provides a non-editable way to view all current and historical versions of Data Sheets.
NAVIGATION: Inquiry >> Inventory >> Data Sheet Inquiry
All notes attached to the Data Sheet, Attributes and Variables will be opened in a view-only window.
Assign Items to Data Sheets with Item-Data Sheet Maintenance.
NAVIGATION: Cards >> Inventory >> Item-Data Sheet Maintenance
After creating Data Sheets, they must be assigned to Items. An Item can have more than one Data Sheet. For example, there could be three different Data Sheets to record information at three steps during manufacturing, and also an RMA Data Sheet for returns.
Select an Item Number then add Data Sheets to the item in the scrolling window.
DELETE will remove all Data Sheets from the Item. The Item is not deleted.
A single Data Sheet can be deleted from the Item by selecting it in the scrolling window, then clicking Edit >> Delete Row.
Routings integrate with the transactions supported by IPT to (1) automatically generate a Data Record when an Item is used on a Transaction where the two are linked by a Data Sheet, and (2) automatically create a Task in the user’s Reminders List.
Navigation: Tools >> Setup >> Inventory >> IPT Routing Setup
For most GP transactions IPT Routings will automatically create a Data Record for an item when the transaction is posted or moved to history. This will occur for the following:
- Inventory Transaction or Transfer posted
- Sales Order completed and moved to history
- Sales Invoice posted
- Sales Return Posted
- Service RMA posted in RMA Receiving
- PO Receipt posted
One exception is Manufacturing Orders. When the MO is created it will generate a Data Record.
IPT Routings will automatically add a Reminder to the “New User” when the transaction is posted. If a “Complete User” is also specified they will receive a Reminder when the Complete checkbox is marked on the Data Record Entry window.
Double-clicking on a Reminder opens the Task window, and from there the Data Record Entry window can be opened by clicking the Zoom To link.
Marking Complete on the Data Record Entry window also marks the Task complete.
12.Data Record Entry
Navigation: Transactions >> Inventory >> Data Record Entry
Data Record Entry is used to create a Data Record. A Data Record is a snapshot of the Data Sheet assigned to an Item-Transaction into which data can be entered. If the Data Sheet is an empty template, the Data Record is a copy of the template that you will record information on.
The Data Record Number is the document number for each Data Record. It is generated automatically after you have entered the following fields:
- Document Source
- Source Document
- Item Number
- Data Sheet ID
- Data Sheet Version Number – the next Data Record Number will be generated after you select the Data Sheet’s Version Number.
Exiting Data Records can be viewed by entering the Data Record Number, or by selecting one from the lookup.
Document Source: the GP Transaction Location. Options are:
- Inventory Adjustment (open/history)
- Inventory Transaction (open/history)
- Mfg Component Issue Transaction
- Mfg Order
- Mfg Receipt
- PO Receipt (open/history)
- Sales Invoice (open/history)
- Sales Order (open/history)
- Sales Return (open/history)
Source Document: select the GP source document number. Use the ORIGIN drop-down box to select Open or History.
Routing Sequence: For Manufacturing Orders you can also link to a specific Routing Sequence. Routing Sequence is not required.
Item Number: Enter an Item Number, or select one from the Lookup. The Item Number must exist on the selected transaction. The Lookup will show only Item Numbers from the selected transaction.
Data Sheet ID: Enter a Data Sheet ID, or select one from the Lookup. The Data Sheet ID must belong to the selected Document Source (i.e. PO Receipt) and be assigned to the selected Item Number. The Lookup will show only Data Sheets for the selected Item Number and Transaction.
If the Item-Transaction has only one associated Data Sheet, that Data Sheet ID will fill-in automatically after selecting the Item Number. If multiple Data Sheets are available, the Data Sheet Lookup will open automatically.
If the Item does not have a Data Sheet assigned for the Document Source, you will not be able to continue. New Item-Data Sheet assignments cannot be made from this window.
Version: select the Data Sheet Version you want to use for the Data Record. The current version will always be the first option in the drop-down list. All historical revisions are listed below the current version. Once you select a version, IPT will generate the next Data Record Number, and the version becomes locked. Version cannot be changed.
If you select an incorrect version you need to delete, or void, the document and start over.
See IPT Setup for information about PO Rev Link. If this feature is enabled, IPT will ask if you want to use the PO Rev version of the Data Sheet if:
- The document is a PO Receipt
- The Item has a PO Rev specified on the PO that is being received
- The PO Rev matches an existing Data Sheet version
When a Data Record has been created using a non-current Data Sheet version, a yellow warning sign will appear next to the Version.
Data Record Number: The Data Record Number will populate automatically when all of the above required fields have been entered. At this point the Data Sheet will be copied to the Data Record.
Date: The date will default to the User Date.
Quantity: this field is informational and is not used by the system.
POSTING: Posting a Data Record moves it to history. Historical Data Records are not editable. They can be viewed in the Data Record Inquiry window. When you click the Post button you will be asked if you are ready to move the document to history. The Data Record must be marked Complete or Void before it can be Posted.
COMPLETE: If the Data Record was generated automatically through the IPT Routing functionality, marking Complete sets the User’s Task for the Data Record to DONE. If there is another person on the Routing, marking Complete also adds a Task for the next User on the Routing.
Notes: IPT controls whether or not a note is opened in a ‘view only’ mode, or an editable mode. On the Data Record Entry window all notes attached to the Data Sheet will be non-editable. This includes the Data Sheet note, and all Attribute and Variable notes. Since these notes are attached to the master record (and not the Data Sheet), they will open in a ‘view only’ Note Window.
Notes attached to the Data Record (the Data Record notes, and all Data Record Line notes) will be editable.
The Datarecord Report can be printed to create a Data Entry Form. An example of the Datarecord report is shown below.
The Note attached to the Data Record (the note button to the right of the Data Record Number field) is displayed in Section A.
The Note attached to the Data Sheet (the note button to the right of Data Sheet ID) is displayed in Section B.
The Attribute or Variable Note (the Note attached to the Attribute or Variable ID in their respective maintenance windows) displays in Section C.
The Data Record Line Note displays in Section D.
The Result recorded for the Attribute/Variable is shown in Section E.
The AV column displays “A” if the row is an Attribute, and “V” if the row is a Variable.
Click the Attributes or Variables view buttons to access the respective data fields. Click into a line to enter data for that field.
Once you have clicked into the detail entry view, you can enter data for that field and scroll between fields by using the Back and Next buttons.
The Variable or Attribute note is accessed through note button A, above. Attribute or Variable notes provide additional information about the Attribute or Variable, or provide instructions. These notes are opened in a ‘view only’ note window.
The Data Record Line note is accessed through note button B, above. Use the Line notes to record additional information about the process of recording or observing the selecting Attribute or Variable. These notes are editable.
Click the Summary button to return to the view that displays all of the Attributes or Variables.
NOTE: The Attributes and Variables are contained on separate “pages”, which are accessed by clicking the Attributes button or Variables button.
13.Data Record Inquiry
Navigation: Inquiry >> Inventory >> Data Record Inquiry
The Data Record Inquiry window is view only, and provides access to both open and posted Data Records.
All notes opened from the Inquiry window will be opened in a view-only window. No changes can be made to the Data Record from this window.
Source Document Zoom: the blue arrow to the right of Source Document will open the selected document. Since the document may have moved from an Open transaction to a Historical transaction (i.e. it was posted), the zoom may not open the document. Try changing the Origin from Open to History, then click the zoom button again.
14.Tables and Views
|W5435DS||Data Sheet Header. Stores the current version of Data Sheets.|
|W5435DSAttribs||Data Sheet Attributes. Stores the current version of Attributes.|
|W5435DSVars||Data Sheet Variables. Stores the current version of Variables.|
|W5435LOV||Stores Attribute ‘lookup values’|
|W5435DSRev||Data Sheet Header Revision. Stores historical revisions of Data Sheets.|
|W5435DSAttribsRev||Data Sheet Attributes Revision. Stores historical revisions of Attributes.|
|W5435DSVarsRev||Data Sheet Variables Revision. Stores historical revisions of Variables.|
|W5435LOVRev||Stores revisioned Attribute ‘lookup values’|
|W5435DR||Data Record Header|
|W5435DRAttribs||Data Record Attributes|
|W5435DRVars||Data Record Variables|
|W5435DRHx||Data Record Header – History|
|W5435DRAttribsHx||Data Record Attributes – History|
|W5435DRVarsHx||Data Record Attributes – History|
|wvDSHdr||SQL View of all Data Sheet Headers|
|wvDSDetail||SQL View of all Data Sheet Attributes and Variables|
|wvDRHdr||SQL View of all Data Records (open and history)|
|wvDRDetail||SQL View of all Data Record Attributes and Variables (open and history)|