Table 75 - Level 1 Pricing Policy
Available at:
- This article presents the fields of the Level 1 Pricing Policy integration layout . To better understand Pricing policies and their Levels, before integrating this table, consult our article and learn about the logic that Demander uses to evaluate and apply pricing policies in Price Policy Resolution.
- To carry out this integration, you must send the information together with:
| Order | Field Description | Format and Size | Required | Version | Note |
| 1 | Table Identifier (IDENTIFICADOR) | FIXO=75 (2) | Yes | 4.18 | |
| 2 | Pricing Policy Code Level 1 (code) | Integer (10) | Yes | 4.18 | |
| 3 | Ranking (ranking) | Integer (10) | Yes | 4.18 | The Ranking is decisive for the application of policiesunderstand better here! Determines the position of the policy. Ex. A policy with ranking 100 will be considered before a policy with ranking 120. |
| 4 | Sequence (sequence) | Integer (10) | Yes | 4.18 | The sequence is decisive for the application of policiesunderstand better here! Determines the ranking sequence. Ex. Two policies with ranking 100, one is sequence 1 and the other sequence 2. Sequence 1 will be considered first and then sequence 2. |
| 5 | Description (description) | Text (50) | Yes | 4.18 | Description free. |
| 6 | Effective Date (dataInicioVigencia) | Date | Yes | 4.18 | Pricing Policy Effective Date. (YYYY-MM-DD). Understand theEffective Period of Policies |
| 7 | Effective Date (dataFimVigencia) | Date | Yes | 4.18 | End Date Validity of the Pricing Policy. (YYYY-MM-DD) Understand thePeriod of validity of the policies |
| 8 | Type 1 (type1) | Text (30) | Yes | 4.18 | NOTE: Only one option per type. BranchUnit(information in the order), Seller(information in the order), Customer(information in the order), Status(information in the order that must be informed through the Customer, field 25 -Table 18), GroupProduct(product information that must be informed through field 3 -Table 15), Product(product information), Customer Type(information in the order that must be informed through the Customer, field 61-Table 18) in the order), Segment(information in the order), ProductSegment(information in the product that must be informed through field 30 -Table 15). Shipping Type(information in the order). products) RuleConfigurator(Product-specific rule) OrderType(Order type) NetWeight(Net weight of the product or order) GrossWeight(Gross weight of the product or order) |
| 9 | Type 2 (type2) | Text (30) | No | 4.18 | NOTE: Only one option per type. BranchUnit, Seller, Customer, State, ProductGroup, Product, CustomerType, SalesDivision, PriceList, PaymentCondition, PaymentForm, Segment, ProductSegment, Quantity, ShippingType, TotalOrderValue, ConfiguratorRule, OrderType, NetWeight, GrossWeight. |
| 10 | Type 3 (type3) | Text (30) | No | 4.18 | NOTE: Only one option per type. BranchUnit, Seller, Customer, State, ProductGroup, Product, CustomerType, SalesDivision, PriceList, PaymentCondition, PaymentForm, Segment, ProductSegment, Quantity, ShippingType, TotalOrderValue, ConfiguratorRule, OrderType, NetWeight, GrossWeight. |
| 11 | Type 4 (type4) | Text (30) | No | 4.18 | NOTE: Only one option per type. BranchUnit, Seller, Customer, State, ProductGroup, Product, CustomerType, SalesDivision, PriceList, PaymentCondition, PaymentForm, Segment, ProductSegment, Quantity, ShippingType, TotalOrderAmount, ConfiguratorRule, OrderType, NetWeight, GrossWeight. |
| 12 | Type 5 (type5) | Text (30) | No | 4.18 | NOTE: Only one option per type. BranchUnit, Seller, Customer, State, ProductGroup, Product, CustomerType, SalesDivision, PriceList, PaymentCondition, PaymentForm, Segment, ProductSegment, Quantity, ShippingType, TotalOrderValue, ConfiguratorRule, OrderType, NetWeight, GrossWeight. |
| 13 | Type 6 (type6) | Text (30) | No | 4.18 | NOTE: Only one option per type. BranchUnit, Seller, Customer, State, ProductGroup, Product, CustomerType, SalesDivision, PriceList, PaymentCondition, PaymentForm, Segment, ProductSegment, Quantity, ShippingType, TotalOrderValue, ConfiguratorRule, OrderType, NetWeight, GrossWeight. |
| 14 | Application (application) | Integer (10) | Yes | 4.18 | Determines where the policy will be applied. 1 - Item 2 - Request |
| 15 | Policy Type (tipoPolitica) | Text (1) | No | 5.13.0 | Defines the policy type. Send:
|
| 16 | jsonConfig | Text (255) | No | 5.13.0 | Used internally (Imported only) |
Registration Example:
75|405|90|2|Policy Level 1|2009-03-01|2999-04-12|BranchUnit|Segment|State||||2|