Find a product variant based on options API

Is there in M3 an API, or can be created, to get a product variant (MMS001 item config code = 3 -> VANO) when family item (item config code = 2) and all feature / option combinations are provided?

Use case: in a 3rd party system the user has selected the correct options for the features. The 3rd party system will do an API call within payload the feature/option combinations and the family item. The reply from M3 should be the variant item code. (in a later stadium the item codes are used to create COs via OIS275).

Could not get it to work with CMS100MI as I could not get a proper join between MPDCDF Configuration detail file and MPDVAN Variance number per product.

Built now an API-flow that uses PDS061MI.CrtConfig, multiple times AnswerFeature and finally ConfirmConfig -> M3 will give an error when that variant already exists. Filter out the item code and send back to requester. As last step PDS605MI.DeleteCfg to delete config..

But that is rather slow and does not feel right. Any other option? Thanks.

Find more posts tagged with

Accepted answers

magnus-tallqvist

The performance will be truly horrible with this solution so I do not think you should try it.....The best solution is most likely to sync the MPDCDF table to the external configuration system and build the look-up locally in that system. Might take some more time/effort but there is no silver bullet to do what you are looking for. An alternative is to create a XtendM3 script that finds if there is any stocked variants but then you need to hook that into the external system anyway to send the correct item number so might be a much bigger task in total.

All comments

Rene Bottern

So, are you looking for where a Sub-Contracted Item is included in a Configured BoM?

JuanSz

Hi Rene, only to find the right item code of the finished product.

With PDS060 variants, of the family item, are generated. Just by setting the correct options for the different features. M3 stores these then under an item code <main item>-xxxx. Where xxxx the variant sequence number is. These items have an own cost, price and BOM in PDS001.

The idea is that the 3rd party system an API call can do to answer the question: What is the item code if the car has to be green and with spare-tire for family item C1245. In the request will be the colour and Spare-tire Features value-pairs. The reply of M3 would be: item code C1245-0026. or Item not configured yet.

With PDS061MI/PDS600MI/PDS605MI you either create a new variant item or create a variant item in an order line. In this case we do not want to create anything in M3, just making the inquiry.

Alternatively we could publish each newly created variant via a BOD with the features and options included and send that to the 3rd party system and have them build the logic to find the right item code.

Jérôme Quersin

Did you consider creating a MDBREADMI transaction on MITMAH table (index 54, only work for standard feature though) ?

you could set a Sel transaction based on HMSTYN, HMOPTX, HMOPTZ and HMOPTY

Rene Bottern

Hi Juan, can't you just lookup the Code=3 items through MPDMAT which tells you what the Product# is.
Then use the Product# to find the Configuration.

You can probably create a 'search API' (CMS010/CMS015 with 'Search' checked in CMS015 to allow search on Sub-Tables) to handle this in that case.

JuanSz

Thanks for your reply Jerome. Checked MITMAH and that table is empty.
But it seems that in table MPDCDF the similar info is. I tried to use MDBREADMI on that table but then I get quite some data and multiple iterations are needed.
Selecting from MPDCDF first all configuration that have Colour=Yellow, this returns a dataset of 400 records across different configurations. Need to do the select 12 times for each feature (next is f.e. Spare tire = Yes). Then do MDBREADMI on MPDVAN to find the variants for the family item. Then find in the 14 datasets the CFIN they have in common. This will lead to the correct MPDVAN record field VANO. Tried it with Postman and Excel; now the next step is trying to get it in an API-flow. Performance and limitations in number of records returned remains a concern.

Wish me luck And Thanks again for the inspiration.

JuanSz

Thanks for your reply Rene.
I got stuck in the CMS010/CMS015 alternative as it seems not possible to join MPDCDF Configuration details and MPDVAN Product Variants. None of the indexes of MPDVAN contains CFIN. Tried to find the Configuration header table to add that table to join the others but I cannot find that one. Thoughts?

magnus-tallqvist

The MITMAH table is only used within Fashion industries with their own way to create SKU´s.

magnus-tallqvist

JuanSz

Thanks Magnus. I fully understand what you say over performance. Was just hoping that I missed an API or so. PDS061MI.ConfirmConfig replies < 1 second that for these options variant item already exist.

We indeed did discuss the option to have an (additional) item BOD that contains item info and when a stocked variant also the features and options.
Is there a way to create an order with the family item (via OIS100MI) and then use PDS600MI to configure and set item right? Like it works in the user interface. If that works we do not need the retrieval API at all and we just change the CO creation integration :-)

Copyright © 2025 Infor. All rights reserved.