Defining transaction prompts

Transaction prompts define where and in what order the data collection module populates information in the system. You can validate incoming data at the field level, as well as at conditional navigation between prompts.

Referring to the data collection diagram, determine what data to enter, in what sequence it should be gathered, and how to group data for processing to Application Programming Interfaces (APIs). Define data prompts for each barcode transaction type.

If you use GIS functionality, you will need to load GIS assets into the system at the system initialization. Ensure that the GISOBJID is manually assigned for each asset you need to integrate during the system initialization. These manually assigned GISOBJIDs must have values in a range of 0 to 100,000,000. The GISOBJID Sequence Generator begins automatically numbering equipment records that are created through Infor EAM or the GIS system with 100,000,001.

Note: You cannot load a GIS asset into the system with a GISOBJID greater than 100,000,000.

For equipment audits, create scanner prompts with the Interface Type A (Equipment Audits) and L (Equipment Audit Lines).

To define transaction prompts:

  1. Open the Transaction Types form.
  2. Click New Record. The system automatically populates Forms SQL Code.
  3. Transaction Type—Enter the transaction type for which to define prompts. The system automatically populates the transaction type description.
  4. Line—Enter a unique code identifying the prompt/processing definition line within the scanning transaction.
  5. Data Type—Select one of the following options:
    • Alphabetic—Select for alphabetic characters.
    • Computed—Select for the system to automatically make a calculation.
    • Date—Select for the system to prompt for data that has a time component.
    • Fixed—Select to define a fixed value.
    • Numeric—Select for numeric characters.
  6. Prompt Description—Enter the prompt as it is to appear on the scanning device.
  7. Choose one of the following options:
    • Fixed for Data Type—Enter, for Fixed Data, the fixed data value for this prompt. For example, if equipment type will always be Asset, enter A.
    • If you selected Computed for Data Type—Enter, for Computed Data, the SQL command string used for the calculation. Use TKD_PROMPTDATA1, TKD_PTOMPTDATA2, etc., to see the relevant column on the tracking transaction table.
    • If you selected Alphabetic for Data Type—Enter, for Pattern Match, a pattern match. See Step #8 for more information about Pattern Match.
    • If you selected Date for Data Type—Enter, for Date Format Mask, a date format mask. The date format mask should match the data that is being entered in the data collection upload columns.
  8. Pattern Match—Enter the pattern matching to be performed by the scanner. Pattern characters can include the following values:
    • . (period)—Represents a single alphabetical character, A through Z
    • # (pound sign)—Represents any single number, 0 through 9
    • _ (underscore)—Represents any single alphanumeric character, A through Z and 0 through 9
    • % (percent)—Represents a string of alphanumeric characters
    • , (comma)—Represents an OR condition
    • : (colon)—Represents a THROUGH condition
    • Any character(s) or number(s)—Indicates that exact character or number in that position
    • ! any character(s) or number(s)—Indicates data entered should not match what follows the "!"
  9. Archive Column—Enter the column where the system archives transaction data.
  10. Interface Type
    • A (Equipment audits)—Indicates the equipment audit starting point and designates a batch number
    • ADI (Add Details Interface)—Adds comments to a record
    • E (Events (work order) interface)—Creates and updates work orders and activities
    • H (Booked hrs interface)—Books labor hours on a work order activity
    • I (Inventory issues)—Tracks inventory transactions of assets or parts, such as issues, returns, store-to-store movements, etc.
    • IRI (Inspection results interface)—Tracks inspection results
    • L (Equipment audit lines)—Indicates the equipment audit data
    • MANF (Manufacturers interface)—Tracks manufacturer information
    • O (Equipments interface)—Tracks assets, hierarchies, and user attributes
    • PART (Parts interface)—Creates and updates part information
    • PURC (Purchase order interface)—Downloads, creates, and updates purchase orders
    • R (P.O. receipt)—Receives assets and parts with or without a purchase order
    • READ (Readings interface)—Records meter readings
    • REQ (Requisition interface)—Creates and updates requisitions for Goods requested transactions
    • S (Stocktake interface)—Enters physical inventory counts
    • TOUS (Tool usage interface)—Tracks tool usage information
  11. Group Sequence—Enter the sequence in which to group data collection transactions.
  12. Upload Column—Enter the interface column in which to load the data.
  13. Action Code—Enter the action that the selected interface performs on this data.
  14. Prompt Sequence—Enter the chronological order in which this prompt occurs. Do not skip sequence numbers.
  15. Minimum Length—Enter the minimum number of characters required for the data to enter at the prompt. Enter nothing or 0 to make this prompt optional.
  16. Next Prompt—Enter the next prompt to display on the barcode scanner. The maximum number of digits is eight.
  17. Maximum Length—Enter the maximum number of characters required for the data to enter at the prompt.
  18. Dup. Previous Value—Select to duplicate the previous value of the prompt.
  19. If Data Is—Enter branch conditions, as necessary. Branch conditions include the following values:
    • != represents not equal
    • < represents less than
    • <= represents less than or equal to
    • = represents equal to
    • > represents greater than
    • >= represents greater than or equal to
    Note: Infor suggests that you prompt the user once and then use a calculated field for each subsequent time.
  20. Pattern—Enter the pattern of the data collected. You can enter only one pattern.
  21. Go To—Enter the prompt to display if the result of If Data Is and Pattern is true.
    Note: This field is used by Oracle Forms.
  22. Query Code—Enter the query code that defines a lookup for this prompt.
  23. LOV Entity—Enter the entity of the lookup.
  24. Validate File—Enter the filename of an ASCII text file against which to validate entries. The filename must be in DOS format. For example, you can enter a file containing a list of authorized employee codes. When you enter an employee code, the reader accesses the file and validates the scanned code against the employee list.
  25. Lookup Attached—Select to make the lookup defined by SQL Code available. If you do not select this field, the system still validates data against SQL Code, but the lookup is not available.
  26. Not Available—Select to ensure data entered is not in the lookups.
  27. Override—Select to allow users to enter nonvalid data if Not Availableis unselected or to enter valid data if Not Availableis selected.
  28. Print Barcode Label—Select to print a barcode label.
    Note: This field is used by Infor EAM Mobile.
  29. Click Save Record.
    Note: Click Validate to validate the transaction prompt.