1 / 29

SIGConnects/Lite Painfree CIM Formatting

SIGConnects/Lite Painfree CIM Formatting. MFG/PRO Midwest Users Group March 26, 2002. CIM in Review. QAD’s “legacy” mechanism to update MFG/PRO Based on Progress redirection ‘INPUT FROM’ or ‘INPUT THROUGH’ Ability to drive a standard QAD screen programs from a data file. Why use CIM?.

brit
Download Presentation

SIGConnects/Lite Painfree CIM Formatting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SIGConnects/LitePainfree CIM Formatting MFG/PRO Midwest Users Group March 26, 2002

  2. CIM in Review • QAD’s “legacy” mechanism to update MFG/PRO • Based on Progress redirection ‘INPUT FROM’ or ‘INPUT THROUGH’ • Ability to drive a standard QAD screen programs from a data file

  3. Why use CIM? • Retains database integrity • Ensures updates to all associated tables • Complete editing of input data • Same as if entered manually • Any screen can be updated * (*well, almost any!?) • Support from QAD is not compromised • “Easier” upgrades to new releases

  4. CIM Format • Single line of data for each input request • Fields are separated by spaces • Character fields surrounded by quotes (“ ”) • Dates formatted as 99/99/99 • Hyphen (-) acts as TAB key • End of input line acts as GO key • Single period (.) acts as END key • Tilde (~) allows continuation on next line

  5. CIM Data Format Example “1397-04” “ea” “Warble-vane” “ajb” - - “Drawing” “FINGOOD” “AC” “A” - “10000” - - no “Article” 30 90 ~ - no yes yes yes 0 “POQ” 100 - - - - “A” .

  6. Can a function run in CIM? • CIM-able - All screen navigation requires only Tab, Go or End keys • Non-CIM-able - Requires more than Tab, Go or End keys to navigate • Function keys other than Go or End • Scrolling windows that require cursor movement and Enter key • Radio buttons, slider bars, etc

  7. CIM – Not a perfect solution • Unforgivingly ugly file format • Not all functions can be executed • Poor error reporting • Performance concerns • At upgrade, reformatting required whenever the UI changes

  8. SIGConnects/Lite • You define your input file • You map your input to the provided screen definition • You add your edits • SIGConnects/Lite reformats your data ready to CIM

  9. Template-Driven Approach • Screen format • Describes the MFG/PRO screen • Fields • Screen navigation – Go and End keys • Conditional Fields • Input format • Describes your input file • Fields, delimiters, lengths, etc • Template • Binds input format to screen format

  10. SIGConnects Screen Formats Seq Field CC Cnt SIG Data Cnd === ============== == === ======== === 1 pt_part 2 F1 3 lot_serialqty 4 site • Field: used to map from the input definition • CC: designates controls for F1 or F4 • Cnt: number of times the entry repeats • SIGData: sets a variable for use in edit routines or reporting • Cnd: Conditional field

  11. SIGConnects Conditional Fields Seq Field CC Cnt SIG Data Cnd === ============== == === ======== === 23 comment_line1 yes 24 comment_line2 yes Condition comments = “yes” • Enter the expression to check to determine whether input is required.

  12. Screen Definition Libraries • SIG provides over 100 MFG/PRO transactions • Specific to version and letter release • 7.4h through eB • Includes every required field and most common use of a given MFG/PRO program • You can modify screen definitions to support your customizations or specific use

  13. Input Formats – Fixed Position Definition Name: Unpl Rcpt Delimited: no Delimiter: Seq Field Field Label Pos Len === ============ ============ === === 1 pt_part Item 1 18 2 site Plant 22 4 3 lot_serialqty Qty 26 7 • Field: used to map to the screen definition • Label: used for reporting • Pos: starting position of the data • Len: length of the data

  14. Input Formats – Delimited Definition Name: Unpl Rcpt Delimited: yes Delimiter: , Seq Field Field Label === ============ ============ 1 pt_part Item 2 site Plant 3 lot_serialqty Qty • Delimiter: character used to separate input fields • Field: used to map to the screen definition • Label: used for reporting

  15. Templates – Binding Input to Output Template Definition: Unplanned Receipts Multiple Format: Data Transforms: Input Definition: Unpl Receipts - Fixed Output Definition: Receipts - Unplanned • Multiple Format: for complex transactions • Header, line items, trailers, etc • Data Transforms: for editing conditions • Template validation: compares input definition fields to output definition fields

  16. Running a Template Input File Name: c:\lite\in\unplfixed.txt Output File Name: c:\lite\out\unplcim.txt Exception Report File Name: c:\lite\rpt\unpl.rpt Output Format: CIMLoad • Specify file names to process • Output format: CIMLoad or Quickloader • Quickloader is CIM without @@ lines

  17. Data Transforms (Input) (Output) Seq Field Pre-edit Constant Value === ============ ========= ============== 1 pt_part v_item.p 2 reason QC Use • Pre-edit: Progress routine to check incoming data • Constant Value: to set values not on input file

  18. Pre-edit Routines * v_item_1.p - item number must exist */ DEFINE SHARED VARIABLE err_flag AS ... DEFINE SHARED VARIABLE error_msg AS ... DEFINE SHARED VARIABLE current_data AS ... DEFINE SHARED VARIABLE identifier_1 AS ... DEFINE SHARED VARIABLE identifier_2 AS ... FIND FIRST pt_mstr WHERE pt_part = current_data NO-LOCK NO-ERROR. IF NOT AVAILABLE pt_mstr THEN DO: err_flag = TRUE. error_msg = "Item does not exist.“ END. • Current_data is the input data value. • Error_msg will appear on exception report • Identifier fields also appear on exception report.

  19. Pre-edit Routines Can Transform Input * v_plancode.p – reformat planning codes */ DEFINE SHARED VARIABLE err_flag AS ... DEFINE SHARED VARIABLE error_msg AS ... DEFINE SHARED VARIABLE current_data AS ... DEFINE SHARED VARIABLE identifier_1 AS ... DEFINE SHARED VARIABLE identifier_2 AS ... IF current_data = “A”THEN current_data = “POQ”. • Current data can be modified by Pre-edit routine. Or translated into Tab, Go or End keys.

  20. Exception Reports Run 03/23/02 SIGConnects Exception Report Page: 1 Rec# Current Data Key #1 Key #2 Validation Routine ==== ================== ============= =========== ================== 1 22-100ABC v_item_1.p Item does not exist. Totals: 4 Records Processed 1 Errors Recorded 0 Warnings Recorded 1 Records Affected • Each transaction is edited independently. • Errors are excluded from output.

  21. Complex Transactions • For transactions with variable repeating screens • Order header • Multiple line items • Order trailer • Managed with multiple record types on a single input file • Expressed as combination of templates • Specify Multiple Formats on Template Definition • Hint: Define the individual templates first!

  22. Complex Transactions Template Name Control Chars(Preceding) Seq In Ident Control Chars(Following) Dep === ================ ======================== === 1 Sales Header P: no Hdr F: F1 2 Sales Detail P: yes Det F: F1 F4 F4 3 Sales Trailer P: yes Trl F: F1 • Each format requires its own template. • Control Characters define the navigation between formats with preceding or following control codes. • Dependence – Should an error on a previous format cause this format to be bypassed?

  23. Complex Transaction Data Example Hdr::0002000,Bright,03/25/99,Rush Approved Det::22-100,1000,35,45.50,3/25/99,,Red Det::22-4000,1000,3,18.75,3/25/99,, Det::22-230,1000,4,22.50,3/25/99,yes, Trl::UPS 2-Day,43.58 • Each record type has a record identifier with double colons ‘::’ to demark record identifier from data. • Fixed length formats define position 1 as after the double colons.

  24. Automating with SIGConnects/Lite • sigbtch.p for unattended processing • Run parameters from input file maparam.dat /* parameters - 1 - input file name */ /* 2 - template definition name */ /* 3 - output file format */ /* 4 - exception report file name */ /* 5 - output file name */ /* 6 - audit report file name */ /* 7 - version */ /* 8 - release */

  25. How to Get SIGConnects/Lite www.strategic.com • Fill in form with contact information • We email you with access password and download instructions from SIG’s FTP site • You download SIGConnects/Lite and documentation • Install it yourself • Email support group for support

  26. SIGConnects Family • Fully automated interfaces • Runs MFG/PRO software directly • Error suspension, correction, resubmission • Post-processing routines • Background Processor • Q/Linq support • Messaging support • Realtime version

  27. SIGConnects Family • Additional formats • XML • Import/export XML definitions using DTD • Tag and Value • QAD Triplet • Output formatting • Any supported format

  28. SIGConnects Family • Upgrade from SIGConnects/Lite • No reinstallation of software • No loss of SIGConnects/Lite templates or definitions

  29. Strategic Information Group Thank you! Phil Coy VP, Product Development +1 724 251 9861 philc@strategic.com

More Related