Hi Daniel,

Have you checked the MRP Action Proposals page?

When MRP tries to create a shop order requisition and can’t find a buildable/plannable structure it creates the action message:

Not Buildable

or

No Alternate (found)

Checkout what MRP messages you have! I bet you for example have “tons” of No Demand Exists and quite a few of Need Orders.

But perhaps I should take it literally ~ fails => you mean “MRP crashes”?

Then - checkout Background Jobs - Details, there you could hopefully can get a hint. Or IFS Support should be able to help you if you provide a good screenshot of the output here.

Cheers,

Mats

Hi Daniel,

Normally these details are shown in the Background Job / Error Information section or within the Status section.

Do you have a specific example of a data condition/missing data which results in an MRP failure where this information is not visible in Background Jobs?

Thanks!

Hello Mats, Hello Richard,

Today, I went through this topic with a colleague from the specialist department. We built an example in which a product does not have an approved bill of materials (BOM). The customer order was created and released, and a selective MRP run for this product was initiated. In the MRP action proposals, we received the message "Not Buildable." Unfortunately, it’s not clear in the background jobs why this cannot be created.

In our example, we obviously know the cause of the error, but it would generally be helpful to know if the system encounters a condition during program execution that is unfulfillable. This would ideally appear somewhere as an error message, so we don’t have to check each individual point in the product to ensure everything is properly maintained for the MRP, in case something was overlooked.

Alternatively, a lobby or similar feature would also help, which could inform us in advance if there are items needing data maintenance to be MRP-ready. I have also attached a few screenshots of the MRP action proposals and the background job, along with its details, which unfortunately contain no error messages either.

Hi,

Thanks for the detailed feedback and examples.

I think you will need to use a combination of the MRP Action Proposals and Background Jobs Status details to capture all of the details you are looking for.  As you say, this could be achieved using some saved searches (which could also be made visible as Lobby Elements) or otherwise show the data as a consolidated report so you can focus on any exceptions.

As Mats says, you will also see any ‘crashes’ in the Background Jobs Error Information section.

I think the same sort of ‘Lobby or Report’ approach could also work for making sure that the data is ‘MRP-ready’ in advance of any MRP run.

I hope this helps.

Hi Richard,

Thank you very much for your response; it was really helpful. I’m currently building a corresponding lobby where the individual MRP proposals are grouped according to the thematic areas listed in the documentation. However, I’ve encountered a small technical issue. I reviewed the technical documentation on how to create navigation from a lobby element. I wanted to navigate directly to the MRP Action Proposals using the part number and the MRP message and then filter based on both values.

The setup worked perfectly for the part number, but when I added the MRP message, it resulted in a "Bad URI" error, even though I followed the guidelines on addressing a List of Values (LoV). Interestingly, when I confirm the error, my filters are correctly applied. I can then click on "Search," and the results show exactly what I was aiming for. I'm just wondering what I might be doing wrong to prevent it from automatically filtering.

I’ve attached a few screenshots—maybe you or a colleague have an idea on what might be causing this.

Thank you very much in advance!

Best regards,
Daniel

This is the Lobby List Element:

Error Message: 

IFS Web Version: 24.1.5.20241010043720.0
Date: 2024-10-31T08:29:57.174Z

---------------------------------------------------------------------------

MrpActionProposals/List (server error)
Malformed Request.
Error details: r{"code":"SYNTAX","message":"The URI is malformed."}]

Request Id: 3fa774ae-2ae9-4675-ace5-e04c287335d7
Url: https://company.url.com/main/ifsapplications/projection/v1/MrpActionProposalsHandling.svc/MrpPartActionSet?$filter=(PartNo%20eq%20%27RA-LENKER%27%20and%20MrpMessageCondition%20eq%20IfsApp.MrpActionProposalsHandling.MrpMessageCondition%27Not%20Buildable%27)&$orderby=Contract,PartNo&$select=PartNo,PartDescription,MrpMessageCondition,MrpSource,OrderNo,MrpSourceDb,MrpMessageConditionDb,LineNo,ReleaseNo,LineItemNoNvlHandled,Contract,UnitMeas,SupplyQty,ActivitySeq,PartActionSeq,TypeCode,MrpAppliedDate,MrpStartDate,StartDate,OrderDueDate,MinOrderQty,MaxOrderQty,MulOrderQty,StdLotSize,NullHandledProjectId,OrderRequisitionDb,TypeCodeDb,Revision,LowLevel,StatusDb,ScheduleDirectionDb,Objgrants,PlannerBuyer,PlanningMethod,MrpType,MrpRunDate,VendorNo,Status,LineItemNo,OrderCode,ScheduleDirection,DemandQty,NegProjOnhandDate,MrpEventDate,PlannedDeliveryDate,RequiredMinusApplied,RequiredMinusAppliedWd,InventoryValue,WipHoldingCost,TotalOrderValue,SafetyStock,SafetyLeadTime,AvailableQty,MrpActionTaken,ActionNote,DemandWithinUnprotectedLeadTime,luname,keyref&$expand=ActivityRef($select=ActivityNo,luname,keyref)&$skip=0&$top=25

---------------------------------------------------------------------------

Hi Daniel,

Apologies for the delayed response.

I think you should raise a ticket with IFS Support so that this issue can be investigated in more detail.

Best Regards,

Richard