This bucket may be restricted by system administrators.
Input Arguments
| Arg# | Name | Description |
| 3 | | Required. Constant 'retailmax.elink.sale.fetch' |
| 9 | | Predicates to select data to return. |
Output Fields
This bucket returns an ARAY packet, and zero or more DATS packets for each result sale.
The fields on the DATS packet for each sale are:
| Arg# | Name | Description |
| f100 | | The Fieldpine sale#. This is a unique non zero number. |
| Field | Present by Default | Predicates | Description |
| f101 | Yes | No | Completed Date/Time |
| f108 | Yes | No | Phase. A coded number indicating the state/type of sale. See table below. |
| f109 | Yes | No | Start Date/Time |
| f115 | Yes | No | Teller Id |
| f117 | Yes | No | Customer Id |
| f125 | Yes | No | Location |
| f130 | No | Yes | External Sale #. External Sale Ids must be able to be encoded in XML strings. They are typically stored in 32 byte database fields. |
| 600 | No | No |
Online Sale Receipt URL. |
| 601 | No | No |
Will Print indicator. (Active Sales only) |
Sale Phases
Sale phases indicate the overall state of a sale. Not all "sales" stored in the database relate to true completed
sales, some represent returns, active sales, parked sales or even deleted sales stored for audit purposes.
| Phase | Description |
| 0 | An active sale |
| 1 | A normally completed historic sale record |
| 5 | Parked sale. Held in limbo, not complete but not active on screens either. |
| 8 | Stock writeoff. Not all systems create sales to hold stock writeoffs. |
| 200 | Sale awaiting stock picking. Typically used by online web sales, which will insert a sale in this phase
to indicate that stock picking is required |
| 10000 | Deleted sale held for audit purposes |
| |
Fieldpine can add sale phases without warning.
Examples
/gnap/buck?3=retailmax.elink.sale.totals&9=f100,0,82837262
Fetch detail of sale# 82837262
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<DATS>
<f100>82837262</f100>
<f101>2011|01|07|14|32|25</f101>
...
</DATS>
