COREPOS\pos\parser\parse\Void Class Reference

Inheritance diagram for COREPOS\pos\parser\parse\Void:

Public Member Functions
	check ($str)
	parse ($str)
	voiditem ($item_num, $json)
	voidid ($item_num, $json)
	voidupc ($upc, $json, $item_num=-1)
	doc ()
Public Member Functions inherited from COREPOS\pos\parser\Parser
	check ($str)
	parse ($str)
	default_json ()
	isLast ()
	isFirst ()
	doc ()

Static Public Member Functions
static	adminLoginCallback ($success)
Static Public Member Functions inherited from COREPOS\pos\parser\Parser
static	get_parse_chain ($type='COREPOS\\pos\\parser\\Parser')

Static Public Attributes
static	$adminLoginMsg = 'Void Limit Exceeded. Login to continue.'
static	$adminLoginLevel = 30

Member Function Documentation

COREPOS\pos\parser\parse\Void::voidid	(		$item_num,
			$json
	)

Void record by trans_id

Parameters

$item_num	[int] trans_id
$json	parser return value structure

This marks the specified record as voided and adds an offsetting record also marked voided Neither record can be subsequently modified via voids.

COREPOS\pos\parser\parse\Void::voiditem	(		$item_num,
			$json
	)

Lookup item and decide whether to void by simply reversing the record or by applying product UPC

Parameters

$item_num	localtemptrans.trans_id value to void
$json	parser return value structure

COREPOS\pos\parser\parse\Void::voidupc	(		$upc,
			$json,
			$item_num = -1
	)

Void the given UPC

Parameters

$upc	[string] upc to void. Optionally including quantity and asterisk
$item_num	[int] trans_id of record to void. Optional.
$json	parser return value structure

If the total does not match quantity times unit price, the cashier probably manually specified a quantity i.e., VD{qty}*{upc}. This is probably OK for non-weight items. Each record should be the same and voiding multiple in one line will usually be fine.

---

The documentation for this class was generated from the following file:

• pos/is4c-nf/parser/parse/Void.php