Table 270 - Cities Policy by Seller
This article presents the fields of the integration layout of the Cities Policy by Seller table. To better understand how this policy works, see the article Cities Policy by Seller
| Order | Field Description | Format and Size | Required | Version | Note |
|---|---|---|---|---|---|
| 1 | Table Identifier | FIXO=270 (3) | Yes | 5.23 | Table identifier. |
| 2 | Code (code) | Text(20) | Yes | 5.23 | ERP Policy Code |
| 2 | Seller Code (codVendedor) | Integer (11) | Yes | 5.23 | Seller code |
| 3 | City code (codCidade) | Integer (11) | Yes | 5.23 | City code |
| 4 | Behavior(behavior) | Integer (1) | Yes | 5.23 | Options: 1 = Allow 2 = Block It makes no sense to mix the two types for the same seller, as one approach already completely determines access. However, different sellers can use different approaches as needed. Examples:
|
| 5 | Active (active) | Integer(1) | Yes | 5.23 | 1 = Yes 0 = No |
Registration Example: 270|11|01|3550308|1|1 270|12|01|3518800|1|1