Table 93-2 - Product Restriction Policy.
- This article presents the fields of the restriction policy integration layout. To better understand the policies, see our article on Product Restriction Policy.
- To carry out this integration, you must send the information together with:
- This layout is an updated version of the Layout “Table 93 - Product Restriction Policy” which has been deprecated and will be discontinued. Basically in this new layout we have the “code” field that was not present in the previous layout.
To delete records from this layout you can use the Layout “Table 402 - Deletion of Product Restriction Policies”.
| Order | Field Description | Format and Size | Required | Version | Note |
| 1 | Table Identifier (IDENTIFICADOR) | FIXO=93-2 | Yes | 4.47 | |
| 2 | Code (code) | Varchar(30) | Yes | 4.47 | Record code in the ERP. This field is the key for including, updating and deleting records. |
| 3 | Product code (codProduto) | Text (30) | Yes | 4.47 | |
| 4 | Seller code (codVendedor) | Integer (10) | No | 4.47 | |
| 5 | Branch Code (codFilial) | Text (15) | Yes | 4.47 | |
| 6 | Customer Code (codCliente) | Integer (10) | No | 4.47 | Customer Code Customer |
| 7 | Behavior (behavior) | Integer (1) | No | 4.47 | 1 - Hidden |
| 8 | Reason for Blocking (motivoBloqueio) | Varchar (500) | No | 4.47 | The value of this field is only used when Behavior=2 - Blocked, but even then it is not mandatory. This field is the message that will appear on the screen when the user tries to add the product to the order. |
Registration Example:
93-2|100001|0100|8|050|1598|2|Product blocked for sale|