How to use Production Monitoring & Control to Process Inventory Transactions

1. How to use Production Monitoring & Control to Process Inventory Transactions Customize your transactions but use XA to update the database

2. What is PM&C? • Production Monitoring and Control (PM&C) is the application that allows for bar code reporting of Inventory Management, Repetitive and PC&C (labor) transactions • If your company wants to use Bar Code to report transactions, they must buy or write software to collect the transactions • With PM&C, standard XA documents will print with bar codes

3. TRDATA File • All transactions scanned are added to the TRDATA file in the AMTLIB • The data queue works as a type of alarm to notify the U-Job (Unattached Job) that transactions have been added to the TRDATA file • The U-Job will take the transactions and update the database using XA programs

4. Turnaround Numbers • When printing bar codes on documents, XA does not bar code order number, item number, etc. Instead, it creates a unique ‘turnaround’ number for each record that can be scanned/reported • When the turnaround number is scanned all of the order/file information is brought into the transaction

5. Turnaround Number Format • In the various files where turnaround numbers exist, the Turnaround Number is broken into 3 sections: • Designator: 2 character that designates the type of file/record • SYSCTL number: 7 character number retrieved from the System Control file • Check digit: 1 character unique number used to prevent duplicate turnaround numbers

6. Designator Codes • 01 Manufacturing Order Header (MOMAST) • 02 Manufacturing Order Components (MODATA) • 03 Manufacturing Order Operations (MOROUT) • 04 Manufacturing Order Miscellaneous Detail (MOMISC) • 05 Purchase Order Master (POMAST) • 06 Purchase Order Blanket Release (POBLKT) • 07 Purchase Order Item (POITEM) • 08 Replenishment (RPLMNT) • 09 Reserved • 10 Reserved • 11 Location Quantity (SLQNTY) • 12 QC Transaction • 13 CO Pick Header (MBCLREP) • 14 CO Pick Release (MBCNREP) • 15 MM Count Group Detail (IVCTDT)

7. Questions?

8. Employee Master • Every transaction requires an Employee Badge number • This number must be a valid Employee in the Employee Master file • If your company uses XA Payroll, Employee Master is created in the Payroll application • All transactions written to TRDATA must include a valid Employee number in the transaction • An Employee Master requires a Work Schedule number

9. PM&C – Schedules & Employees • A work schedule defines the times for a work shift, breaks & lunch • A work schedule is required in the Employee Master file • Employee numbers are required for transactions written to TRDATA • PM&C inquiry allows for inquiry of all transactions with by Employee number

10. PM&C - Schedules

11. Work Schedule Fields • Shift Start/Stop • If the same value is entered in the Early & Late, then the actual clock in time is used on a TA (Time & Attendance) transaction • If there is a time range between Early & Late and the employee clocks in during that range, then the Standard is assigned to the TA • Even if your company is not using PM&C for TA transactions, a Work Schedule must be created to add Employees

12. Employee Master Screen

13. Employee Master Required Fields • Employee Number • Employee Name • Multi-Job (always set to Yes) • Shift • Schedule • Address • Always leave ‘Terminate Date’ blank (zero’s). Any date in this field flags the Employee as Terminated

14. Questions?

15. Processing Transactions • If you are creating your own transactions to populate TRDATA follow these steps: • Hold the PM&C U-jobs in CAS • Key the transaction in PM&C • Query the TRDATA file (AMTLIB) to see the fields/record layout for the file • Write your program to populate the same fields as the keyed transaction • Release the U-job to verify that the transaction will post

16. Processing Transactions • Inventory Management and Repetitive transactions are posted immediately • Order records updated • On Hand/location records updated • Transaction History updated • Labor transactions • Quantity Complete/Scrapped updated immediately • Labor Hours updated with Select & Edit job

20. Transaction Status Codes There are 3 ACREC fields in TRDATA:      ACREC  - When a transaction is entered through data collection or through keyboard entry, it is set to a Y.  If the transaction is in error or deactivated it is set to N.      ACRECP - If Y, the record has been posted.  If a transaction is either a TA or an Inventory transaction, the transaction is posted immediately, so ACRECP gets updated with a Y.  It is blank if an ON or OF has a TSTAT of 2. If a transaction has been deactivated, it is N.      ACRECS - Set to same value as ACRECP when a MAPICS backup has run.  If ACRECS is Y, the record cannot be changed... to make corrections, deactivate the transaction, and add a new record with correct data.

21. TRDATA Status Codes • The values of TSTAT, QUEUE, and EXFLG in TRDATA keep track of what processes the transaction has been through: • TSTAT = 1 QUEUE = 0 Transaction in error (eg date not valid, MRP generation active) • TSTAT = 2  QUEUE = 1 New transaction, waiting to be posted by unattached job • TSTAT = 2  QUEUE = 0  Transaction is in error • TSTAT = 3  EXFLG = 0   Transaction has passed initial edits/posting, is waiting to be processed by Select and Edit • TSTAT = 3  EXFLG = 1   Transaction has been processed by the Select and Edit, waiting for Prepare • TSTAT = 5                     Transaction has been through the Prepare processSELYN is also set to 1 when a transaction is selected

22. Select and Edit

23. Select and Edit • Select & Edit is a required job that will: • Update the status code fields of the transaction • If the transactions are PC&C labor transactions (Job ON or OF), update MO Operation with time • Produce a report of all transactions or error transactions only • Transaction number will be displayed for each transaction printed • Transaction number is used in ‘Maintain Transactions’ to correct error transactions

24. Correcting Transactions

25. Correcting Transactions

26. Employee Activity Inquiry

27. Employee Activity Inquiry • If a transaction is highlighted, it is in error • Move the cursor to that transaction and press the Enter key • Transaction will be displayed and can be: • Corrected (change field and press Enter) • Used to see error (no changes and press Enter) • Deleted (F20)

28. Prepare Transactions • All transactions that have updated the data base and been selected (with the ‘Select & Edit’ job) need to be prepared • Run the ‘Prepare’ Job to update the status code to 5 • All transactions with a status of ‘5’ will be deleted from TRDATA when an XA backup is run

29. Questions?

30. Cistech Transactions • If you don’t want to write your own programs to collect transactions, Cistech has written RF transaction collection for IM, Rep and MM (cycle count) transactions • RF gun must have 5250 emulation

31. Cistech Transactions • Each Employee has a profile to determine what transactions will appear for the transaction • Each Employee can set defaults to determine what fields are displayed on the RF device (optional fields only) • ‘Hooks’ in receiving transactions can call label print programs (i.e. TL Ashford)

32. Employee Transaction Screen

33. RM Transaction Screen

34. Location Inquiry

35. TRDATA Inquiry

36. Cistech Transaction Info • Transactions are sold: • Individually ($1,500/transaction) • Or as a full package of all transactions ($12,000) • 90 day support complementary • Annual support available

37. Summary • Create Work Shifts and Employees before using PM&C • Write transactions to the TRDATA file in the AMTLIB • Allow XA to use U-jobs to process transactions • Run ‘Select & Edit’ job daily to discover error transactions • Correct errors and re-select

38. Summary • Run the Prepare job to change the status of selected transactions • XA Backup will delete prepared transactions from TRDATA • TRDATA is a powerful tool to use to process transactions