MTG681 – Meeting Registrant Badge Generation
This batch
process generates badges or badges and tickets either individually
from the ORD001 screen or in batch from the TRS002 screen. There can be
additional badge requests for spouses or VIPs. Logos and/or barcodes can
be added, various badge types can be defined, and additional badge formats
are available. Badges can be generated for meeting participants only or
for all the meeting registrants with additional badges. Badges fit on
Avery label #5395 (2-1/3" x 3-3/8", laser, removable, 8 per
sheet), #5095 (2-1/3" x 3-3/8", red border, laser, removable,
8 per sheet), or #5895 (2-1/3" x 3-3/8", blue border, laser,
removable, 8 per sheet). Badges are not printed for cancelled, proforma,
or waitlisted orders. In batch mode, it is possible to generate combined
badges and tickets for each registrant with a header ticket, individual
session tickets, and a trailer ticket showing the total number of tickets.
As
of 7.5.2, when both the Parent Product
and Product Code parameters are
set to a product type ‘M’ , ‘COURSE’, and ‘EXAMPROCT’, then the MTG681
process will print tickets for all the product types with number of tickets
printed equal to max_tickets multiplied by quantity purchased. Additionally,
When the Parent Product is set
to a product type ‘M’ , ‘COURSE’, and ‘EXAMPROCT’ and Product
Code is set to ‘S’, then the MTG681 process will print tickets
for session (‘S’ product type) with number of tickets printed equal to
max_tickets multiplied by quantity purchased of the session product.
Parameters
Parameter |
Description |
Required? |
Organization |
The Organization ID for which you want
to run the report. |
Read-only |
Organization Unit |
The Organization Unit ID for which you
want to run the report. |
Read-only |
Parent Product |
The Meeting Code for which the Badges
are to be printed. |
Yes |
Product Code |
Enter the Product Code for the Meeting,
Session, Course, or Exam Product for which badges are to be generated. |
Yes |
Badge Type |
Enter the type of Badge to be printed.
Valid values are:
· "ALL":
This will print "SELF" as well as all the additional
badges defined in order_detail_badge table.
Full Name is mandatory in ORDER_DETAIL_BADGE
table, but not the Personify_Badges module.
· Any
specific badge type: All the badges with badge type as specified
would be printed. Eg : SPOUSE : Will print only the additional
badges defined for SPOUSE.
Options are populated based on the non-fixed
codes defined for the MTG "BADGE_TYPE"
system type. |
Yes |
Print Tickets |
This parameter decides whether to print
badges or combined badges and Tickets. Valid values are : "YES"
:Yes will print Badge as a Ticket Header, a ticket for each session
registered and a Trailer Ticket for all the registrants. "NO"
:Will print only the Badges. No Tickets would be printed for a
session. |
Yes |
Ticket Header |
This parameter is used to print as first
line on each session and trailer tickets. If "Print Tickets"
Parameter is set to 'YES', then this parameter is used to print
as first line on each session and trailer ticket. If left blank,
the default value of Org unit name is selected from app_org_unit
table for input Organization and Organization Unit parameter.
If you do not want anything on first line of ticket, enter NONE. |
No |
Sample Report
