Table 71 - Sale Action
- This article presents the fields of the sales actions integration layout. To better understand the concept behind sales actions, see our article on Sales Action Concept.
- To carry out this integration it is necessary to send the information together with the tables:
| Order | Field Description | Format and Size | Required | Version | Note |
| 1 | Table Identifier (IDENTIFICADOR) | FIXO=71 (2) | Yes | 2.23 | |
| 2 | Sales Action ID (idAcaoVenda) | Integer (10) | Yes | 2.23 | Demander Web Record ID |
| 3 | Unique ID of the Sales Action (uniqueID) | Text (50) | Yes | 2.23 | Unique registry identifier, generated by the Android application. |
| 4 | Order ID (idPedido) | Integer (10) | No | 3.4 | Identifier of which order made this Sale Action |
| 5 | Seller Code (codVendedor) | Integer (10) | Yes | 2.23 | |
| 6 | Date and Time (dataHora) | DateTime | Yes | 2.23 | |
| 7 | Customer’s CPF or CNPJ (cpfCnpjCliente) | Text (20) | Yes | 2.23 | |
| 8 | Customer Code (codCliente) | Integer (10) | Yes | 2.23 | If you are a new customer (registered by the seller) it is sent “0”, and you need to consider the field “cpfCnpjCliente” |
| 9 | No action taken (nenhumAcaoRealizada) | Integer (1) | Yes | 2.23 | 1 - No action was taken; 0 - Some action was performed |
| 10 | Customer UniqueID (uniqueIdCliente) | Text (50) | Yes | 2.23 | Customer’s Unique Identifier on Demander |
| 11 | Order Number (numPedido) | Integer (10) | No | 3.4 |
Registration Example:
71|158073|AC-1-1617806441150|10569561|1|2021-04-07 11:40:41|25.993.658/0001-72|5634|0|31135634238183|204|