1 / 6

Infor Warehouse Mobility Transaction Programming

Infor Warehouse Mobility Transaction Programming. Kiran Madduri, Infor. Architecture. Proven architecture with over 350+ customers worldwide. Multi Form Transaction . A IWM Transaction is a collection of Forms . A typical form size is 16 rows and 20 columns.

orenda
Download Presentation

Infor Warehouse Mobility Transaction Programming

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. Infor Warehouse Mobility Transaction Programming Kiran Madduri, Infor

  2. Architecture Proven architecture with over 350+ customers worldwide

  3. Multi Form Transaction • A IWM Transaction is a collection of Forms. • A typical form size is 16 rows and 20 columns. • Device Type Setup – Define the screen size. • Multi Forms – In case if all the fields don’t field in the screen definition. • Navigation of Forms – Transfer control from one form to another • Data Handling in Multi Form Transaction

  4. Barcode Prefixes • Prefixes can be either setup based on Field ID or Field data type • Prefixes are defined in global_param_list.xml • Prefixes can be made mandatory.

  5. Multi-Part Barcode Handling • Also called as Concatenated Barcode. • Need to be defined and configured for each transaction • Need to be defined in <TransactionName>BarcodeList.xml. This file should reside in the same directory as Transaction XML file.

  6. Transaction Parameters • Also called as Concatenated Barcode. • Need to be defined and configured for each transaction • Need to be defined in <TransactionName>BarcodeList.xml. This file should reside in the same directory as Transaction XML file.

More Related