Product documentation
This webservice returns the basic data per item-warehouse combination.
{{resource}}/api/ArticleCodeMaster
{{resource}}/api/ArticleCodeMaster?page=2
{{resource}}/api/ArticleCodeMaster?lastModifiedDate=30
{{resource}}/api/ArticleCodeMaster?page=1&lastModifiedDate=30
|
Attribute |
Description |
Field type |
Microsoft Dynamics 365 for Finance and Operations field |
Remark |
|
Warehouse |
Warehouse |
String(20) |
Warehouse |
|
|
ArticleCode |
Article code (SKU) |
String(40) |
Released product (Released product variant) |
|
|
CreatedDate |
This field can be used to interface the creation date of an article. |
YYYYMMDD |
Creation date (InventTable) |
|
|
Article Description |
The description related to the unique article code should be entered here. |
String(60) |
Item name (Item name and variant description) |
|
|
UnitPrice |
This is the price (commonly per unit, see below in Price Per) that is used to determine stock value, e.g. average landed cost, average weighted cost, etc. Note: The currency of the value does not matter. |
Num(15,4) |
Cost price Can be site specific. For performance reasons the cached values per date are used. |
In case the cost prices changes during the day, and the export runs before midnight, the price of the start of the day can still be cached. |
|
SalesPrice |
This is the price the sales price for an item. Note: The currency of the value does not matter but should match that in unit price. |
Num(15,4) |
Sales price according to the first valid trade agreement for all customers. If not found, basic sales price. |
|
|
Criterium1 |
These Criteria (conversion factors) are for use in the order generator. If the order generator is not used, the fields can remain empty. Filling them will not disrupt any Slim4 processes. The Criteria are used as multipliers in Slim4. The entry needs to match the unit of measure in which stock is held in Slim4. Typically used criteria are: weight, volume, share in pallet, share per container etc. |
Num(38,15) |
Field mapping |
|
|
Criterium2 |
Idem |
Num(38,15) |
Idem |
|
|
Criterium3 |
Idem |
Num(38,15) |
Idem |
|
|
Criterium4 |
Idem |
Num(38,15) |
Idem |
|
|
Criterium5 |
Idem |
Num(38,15) |
Idem |
|
|
Criterium6 |
Idem |
Num(38,15) |
Idem |
|
|
Criterium7 |
Idem |
Num(38,15) |
Idem |
|
|
Criterium8 |
Idem |
Num(38,15) |
Idem |
|
|
AnalysisCode1 |
These are fields that can be filled with company specific data for which there are no predefined fields in Slim4. The information given in these fields offers the opportunity of splitting the data in Slim4 in the same way as it is split in your ERP. Typical data interfaced are product groups, planner, promotion type, etc. A total of 21 fields can be interfaced. |
String(20) |
Article code master additional data or field mapping |
|
|
AnalysisCode2 |
Idem |
String(20) |
Idem |
|
|
AnalysisCode3 |
Idem |
String(20) |
Idem |
|
|
AnalysisCode4 |
Idem |
String(20) |
Idem |
|
|
AnalysisCode5 |
Idem |
String(20) |
Idem |
|
|
AnalysisCode6 |
Idem |
String(20) |
Idem |
|
|
UDF1 |
These are user defined fields that can be filled with company specific data for which there are no predefined fields in Slim4. The information given in these fields offers the opportunity of splitting the data in Slim4 in the same way as it is split in your ERP. Typical data interfaced are product groups, planner, promotion type, etc. The field layout is configurable in Slim4. The database field is alphanumeric, limited to 255 characters. |
String(40) |
Article code master additional data or field mapping |
Slim4 could process string(255) |
|
UDF2 |
Idem |
String(40) |
Idem |
Idem |
|
UDF3 |
Idem |
String(40) |
Idem |
Idem |
|
UDF4 |
Idem |
String(40) |
Idem |
Idem |
|
UDF5 |
Idem |
String(40) |
Idem |
Idem |
|
UDF6 |
Idem |
String(40) |
Idem |
Idem |
|
UDF7 |
Idem |
String(40) |
Idem |
Idem |
|
UDF8 |
Idem |
String(40) |
Idem |
Idem |
|
UDF9 |
Idem |
String(40) |
Idem |
Idem |
|
UDF10 |
Idem |
String(40) |
Idem |
Idem |
|
UDF11 |
Idem |
String(40) |
Idem |
Idem |
|
UDF12 |
Idem |
String(40) |
Idem |
Idem |
|
UDF13 |
Idem |
String(40) |
Idem |
Idem |
|
UDF14 |
Idem |
String(40) |
Idem |
Idem |
|
UDF15 |
Idem |
String(40) |
Idem |
Idem |
|
ArticleStatus |
The status of the article. Information field. In the past applied in a UDF, now in a dedicated field |
String(100) |
Product life cycle state |
|
|
Barcode |
EAN code, UPC code |
String(20) |
Scannable barcode |
|
|
FefoPercentage |
First expired, first out percentage |
Num(15,2) |
0 |
|
In the field mapping a lot of standard Microsoft Dynamics 365 for Finance and Operations table fields can be mapped to Citeria 1-8, Analysis code 1-6, User defined fields 1-15.
If not specified in the field mapping, Analysis code 1-6 and User defined fields 1-15 can be filled in Article code master additional data: