Equipment Tracking Requisition

Use this service to import Equipment Tracking Requisitions information.

WSDL: AddET_Requisition.jws

Method: AddET_Requisition

Enhanced Authentication

Underlying File Maintenance

Prior to importing Equipment Tracking Requisitions information, the following file maintenance areas must be completed:

  • System Administration > Installation > Equipment Tracking

  • System Administration > Installation > Inventory Control

  • System Administration > Installation > Equipment Tracking > Transaction Code Maintenance

  • System Administration > Installation > Equipment Control > Equipment Code Maintenance

  • System Administration > Installation > Inventory Control > Inventory Item File Maintenance

  • System Administration > Installation > Inventory Control > Warehouse File Maintenance

  • System Administration > Installation > Inventory Control > G/L Department File Maintenance

  • System Administration > Installation > General Ledger > G/L Master File Maintenance

  • System Administration > Installation > Job Cost > Jobs

  • System Administration > Installation > Job Cost > Job Phases

  • System Administration > Installation > Job Cost > Cost Type File Maintenance

  • System Administration > Security > Operator Maintenance

Assumptions and Dependencies

  • The Equipment Tracking Requisition web service updates the History tables automatically due to how they are created in Spectrum using the 'Continue' logic and bypasses the Data Entry tables. **WARNING**

  • The Equipment Tracking Requisition web service checks the Historical SQL tables to define whether or not to create a new Requisition or to add detail lines to an existing Requisition based on the required fields matching. The data is appended to an existing Requisition only.

  • The Equipment Tracking Requisition header contains the following fields which must match in order to add detail lines to the History table. **WARNING** If all fields match in History they will be added as detail lines.

    • Company_Code

    • Tool_Requisition_Number

    • Transaction_Code

    • Job_Company_Code

    • Job_Number

    • Site_ID

    • Requistition_Date

    • Expected_Billing_Period

  • If the Tool_Requisition_Number exists in the standard Data Entry table then it will not be created.

  • If the Tool_Requisition_Number exists in History but none of the other required fields needed for the Requisition header match, then the service will prevent the information from being added.

  • The import has a record limit of 990 records per Equipment Requisition and the service will prevent any additional detail lines to be added.

  • If the Company_Code is blank then use the Authorization ID default value.

  • The Tool_Requisition_Number and Transaction_Code are required fields.

  • The Transaction_Code defines whether or not the requisition will be for a Job or Site.

  • The Expected_Billing_Period field defaults from the Installation option if defined and not supplied in the record.

  • The Inventory Item must exist for the defined warehouse.

  • Inventory Non-stock items cannot be created.

  • When an Equipment item exists on a current Equipment Tracking Requisition the system automatically creates the 'Return' within Spectrum using the next available Requisition number based on the Installation setting. Therefore if you have defined that number to be used within the web service an error will be returned because that number has already been used.

  • Equipment Tracking Requisitions are not created when Physical Inventory is in progress.

  • For Intercompany Equipment Tracking Requisitions

    • The options and setup must be completed on the company Inventory and/or Equipment Control Installation screens.

    • Available for requisitions with direct cost transaction codes (that is, Job deployment type for Transaction Code) and defined in the Equipment's primary company.

  • The Quantity field logic

    • Required for a requisition that has a defined Item_Code.

    • Some requisitions that have a define Equipment_Code require the Quantity to be populated.

  • The Expected_Billing_Period field logic

    • This is not a required field.

    • If field is blank then it will defaults from the Equipment Tracking Installation unless NONE is selected then it will be blank.

  • The Notes and Message fields will be truncated if they exceed the Max character length.

Field Descriptions

Use the table below for reference when using this service. The Authorization_ID and GUID elements are not shown on the Spectrum Excel Office Add-in templates for data entry points.

Excel

 Element Name Description Req Type Max Format Validation
Authorization_ID Authorization ID to access the server YES Text 20 Data Exchange Installation Screen
GUID Unique reference number created by programming Text 36 ** See GUID definition

B

 Company_Code Company Code Text 3 Valid Company in Spectrum. Defaults from the Authorization ID if not populated.

C

 Tool_Requisition_Number Requisition YES Text 7 ** See Assumptions and Dependencies for multiple detail line logic. Requisition History Table ( defines whether or not to add as a detail line or create new)

D

 Transaction_Code Transaction Code YES Text 5 Code defines whether it's a job or site requisition. ** See Assumptions and Dependencies for multiple detail line logic. Equipment Tracking Transaction Code

E

 Job_Company_Code Issue to Job Company Code Text 3 Used for Multi-company requisition feature for Job type Transaction Codes. If blank or option not selected use the Company_Code field for Job Transaction codes. ** See Assumptions and Dependencies for multiple detail line logic. Inventory Control or Equipment Control installation option for Multi-company requisition is defined. Valid Company in Spectrum.

F

 Job_Number Job Text 10 If defined then Site_ID must be blank and Transaction_Code is for Job type. ** See Assumptions and Dependencies for multiple detail line logic. Valid Job in defined Job_Company_Code otherwise valid for defined Company_Code

G

 Site_ID Site Text 10 If defined then Job_Number must be blank and Transaction_Code is for Non-job type. Must have an active status. ** See Assumptions and Dependencies for multiple detail line logic. Work Order Site File Maintenance

H

 Requisition_Date Requisition date Date 10 Enter as: MM/DD/CCYY (for example, 01/05/2010). Use Current Date for Equipment Tracking module if blank. ** See Assumptions and Dependencies for multiple detail line logic. Must be within the Equipment Tracking min/max dates.

I

 Expected_Billing_Period Minimum billing period Text 1 D(aily), W(eekly), M(onthly) or blank only. If blank then use the selected default installation setting. ** See Assumptions and Dependencies for multiple detail line logic. ** See Assumptions and Dependencies

J

 Notes Notes Text 1000

K

 Item_Code Item Text 15 If defined then Equipment_Code must be blank. Inventory Item Maintenance

L

 Equipment_Code Equipment Text 10 If defined then Item_Code must be blank. Equipment Code Maintenance

M

 Phase_Code Phase Text 20 Defaults from Item_Code if left blank. Phase File Maintenance

N

 Cost_Type Cost type Text 3 Defaults from Item_code if left blank. Validates to the defined GL_Debit_Account for direct job cost. Cost Type Maintenance

O

 Yard_Or_Warehouse Text 10 Used for Inventory Type only. Warehouse must be defined for Item_Code field. If blank defaults from Inventory Control Installation screen. Warehouse File Maintenance

P

 Quantity Quantity Numeric 9 Allows negative. Whole numbers only. **See Assumptions and Dependencies

Q

 Message Message Text 30 Detail line message