Products (Manufacturing, Products, Engineering)

Hello IFS Community,  When we regenerate the calendars with the addition of new exceptions to already generated calendar, scheduling/Planning of all the DOP connected Shop Orders and PRs become inaccurate. The only option seems available to correct them to reply on the function “Propagate Date Upstream “. However, this is not practical when there many open DOP orders. I already created a ticket to IFS support, and they wanted me to create a community post . Kindly enhance this in a future release ?  

Hi, We have a customer that needs to sequence manufacturing of multiple parts in for packing and installation. For example:  They need a total 30 x Part P1 and 7 x Part P2 For packing and installation they might to make the parts in the follow quantities. 5 x P1 2 x P2 10 x P1 1 x P2 3 x P1 2 x P2 5 x P1 2 x P2 7 x P1 The finished goods have multiple parts that are both purchased and subassemblies made other shop orders. They aren’t using DOP. The demands for the shop orders are generated by PMRP.The preference is not to split this into multiple shop orders for the sequencing (ie just one shop order for 30 x P1 and one shop order 7 x P2).Another option is that if we do split the final parts into multiple shop orders for sequencing, after the initial run of PMRP, the shop orders for underlying assemblies don’t get split up, also, ie they remain as if we're making 30 x P1 one shop order and 7 x P2 on 2 shop orders instead of 9. Cheers,Craig

Hello everyone,with the page designer, it is possible to add data to a field. In this example, the part description is added to the part number.This is done by adding a VIEW and using the Template address.Where is this template defined?Thanks,Golo  

I have been looking into the new Co-product feature in 25R1 and it seems ideal for our needs except for one major flaw.  Parent part must not be multi-level trackedFor this feature to be of any use to us we would require both the parent part and the co-product to be lot tracked. Even in the example given in the release presentation of two castings made in the same mold it makes no sense to only be able to lot track one of the castings. Can anyone explain the logic behind this? Surely if I am making two products that are equally valuable then I should be able to track them equally?  Will tracking of the parent part be available in future releases?   

Hello all,When we proceed to a revision transfer actions for a Manufactured part, the structure data from the previous revision, such as “Reserve/Issue from Loc” or “Reseve/Issue Method” are lost. Is there a way to preserve these informations when creating a new revision ? Thank you for your help. 

Extending functionality on DOPs – connection of DOP components to operations – mentioned in 25R1. We have SU 25.1.2 + APB released on 2025-01-20. See behavior, seems does not work correctly:DOP – 3 levels, component T-2 is connected to Operation 20 of T-1. The same connection on SO:APB before scheduling – just scheduler by IFS – OKParameters of scheduling in APB:After scheduling in APB – connection to operation 20 ignored:   Thanks in advance.  

Hi, I would like to raise this question in the forum to understand how different users handle the situation described below. I am working with a customer whose BOM structure contains multiple levels sometimes up to seven.When we create a shop order for the top level item and run MRP, shop order requisitions and purchase requisitions for the lower level components are generated automatically. After converting these shop order requisitions into shop orders, is there a way to view all child shop orders linked to the top-level shop order?Essentially, my customer wants to see the related shop orders and the material availability for each of them.We can review the BOM structure using MRP Part Information (Top-Down), but this does not provide a clear view of the shop order hierarchy or the critical path.How would you address this type of requirement? Are there standard functionalities or possible views that could help achieve this?

Hi everyone,We’re currently preparing our migration from IFS Apps 9 to IFS Cloud, and besides the functional transition (e.g., Project Delivery → Deliverables), we’re also exploring the reporting side of the migration.Specifically, we’re looking for experiences from others who have: Migrated from Crystal Reports to IFS Report Studio, and Worked with Report Designer reports in Apps 9. We’re wondering: How did you approach the migration of Crystal Reports — did you rebuild them in Report Studio or use an alternative strategy? How mature and flexible is IFS Report Studio in your experience? What happens to Report Designer reports from Apps 9 — are they still available and functional after migration to IFS Cloud, or do they need to be redeveloped? We’d love to hear from anyone who has hands-on experience or best practices to share around this reporting migration path.Thanks in advance for any insights,Best regards, Jesper

Why do tentative structures show up on the multi level structure tab on the Product Structure page?Part Number 101793 has two product structures:  Rev 1 is buildable and Rev 2 is tentative.Both Rev 1 and Rev 2 show up on the multi level structure.I would have thought that only buildable structures are included in this view.  Any insight into what is and is not included in the multi level structure would be appreciated. Each color represents a component that’s in both Rev 1 and Rev 2 of 101793.  Rev 2 is tentative and I wouldn’t expect it to show up on this view.  

Customer (Apps10 EE) wants to create a document revision without a file and in a field on the document revision enter a link to an external location where the file will reside. I recall doing this before custom fields were readily available, but I cannot recall where in the document revision the link was entered. Anybody have experience with this without using a custom field?

Steps to recreate Shop Order error in IFS Cloud 24R2: Create shop order for a part with lot tracking, close code = Auto Close, and close tolerance > 50. On Shop Order > Lots/Batches, create more than one row and save. My example uses two lot batches. Complete all material issues, guideline sign offs, and all operations up to the final operation on the order. From Shop Floor Workbench, attempt to approve the final operation. In the Approve Operation dialog, enter expiration dates for the Lots/Batches to Receive, then click Finish. Receive error: “The order is closed and it is not possible to add anymore lots to the order”. At this point the SO status = Started, and nothing is received. Navigate to the Shop Order and change one of two things: Change Close Tolerance to <= 49. Change Close Code to Manually Close. Repeat step 4, this time with no error. If option b was used, there is an additional step required to change the Shop Order status to closed. Up to now using IFS1

When we regenerate the calendars with the addition of new exceptions to already generated calendar, scheduling/Planning of all the DOP connected Shop Orders and PRs become inaccurate. The only option seems available to correct them to reply on the function “Propagate Date Upstream “. However, this is not practical when there many open DOP orders. I already created a ticket to IFS support, and they wanted me to create a community post . Kindly enhance this in a future release ?  

Hi, Does anyone know if IFS App 10 has any quality tools for root cause analysis such as:5W 2W5 Why?Pareto analysis?Ishikawa?If so, where and how can I use them?And is the screen (8D) in the attached document part of the App 10 standard? 

Hi, I run Cloud 24R2, it’s not possible to edit a clocking for previous days. What is the setting that prevents that, I get an error. What parameter or setting prevent me from edit, create new or cancel clockings in the past?Second question, can I adjust clocking by set a duration time instead of  start and stop?  

Community, do we have a report or window that will give the same info for window Average Issues/Receipts per Period? if there is a report or browsing widnow out of box that listed the parts in horizontal format that will be great. Thank you.

Hi everyone,I have a question regarding the material constraint in MSO.Our customer asked if there is a way to ensure that MSO checks whether enough input material for a shop order is available. The expectation is: If the required material is available → the shop order should be successfully scheduled (respecting other scheduling rules as well). If the material is not available → the shop order should not be scheduled. To test this, I performed the following steps: I selected an already successfully scheduled shop order in MSO with just one operation step. I went to the Inventory Part Planning Data and set the input material to Always Finite. I issued (consumed) the entire input material for this shop order, so there was no remaining supply. I ran MSO again, expecting that the shop order would no longer be scheduled due to missing material. However, the shop order was still scheduled. The only difference I noticed is that the flag indicating that the material constraint is acti

Hi,we work in multisite environment. We have manufacturing sites A & B. Both sites uses components in production that the other site manufactures. Components are transferred between sites with distribution orders. We have defined in supplier for purchase part supplier manufacturing lead time and site to site parameters transport time. Can someone explain the logic of DO schedules?Case: Shop order is created on site B and it requires component from site A. MRP create first DO from site A to B and then shop order request on site A. It seems that MRP does not take into consideration supplier manufacturing lead time at all but only tries to fullfill site B shop order component need even if component is not available on site A and manufacturing would take X days. What’s the point of supplier manufacturing lead time in case MRP does not use it in calculation?

For a lot controlled item with expiry configured how do you create a rule for allocating by FEFO ? 

In IFS Cloud 22R2 SU3 (and previous versions), there is an issue in the Sales Configurator.On Page Sales Rule for Part, when creating a new Action, e.g. of type ‘Attach Optional’, selecting Value Type ‘Order Info’ will give you the wrong List of Value (LOV) for column Value. Hence it is not possible to select any of the designated values, which should be:- Customer No- Delivery Country for the Customer- Latest Customer Value- Latest Order Value- Sales Group- Sales Part No- Sales Quantity- Sales Unit of Measure- User ID- Supply SiteIt seems like the LOV from Conditions is used instead.Please advise if there is any correction available for this issue.

Hi All, In Cloud 25R2 (we have also checked 24R1) we have raised a Protype Shop Order and on defining a Tentative “Manufacturing” Structure and Routing the system appears to be only pulling through the routing, the structure is left blank. We are putting this down to a bug, but thought i would see if others have experienced this issue. *Please note: this is a Structure Type = Manufacturing, which has a “Tentative” alternate.Its normal behavior for the standard manufacturing structure in tentative to not pull through to a standard manufacturing shop order, but it was my understanding that a “Prototype” Shop Order overrides this and is able to utilise a tentative manufactured structure. It’s like the system is only half applying the logic as it pulls through the “Tentative” manufacturing routing onto the shop order. Thanks in advanceKev

Hello,I would like to confirm whether there is no automated logic behind the Proposed Location field on a manually created Production Schedule line.Is that correct?I am aware that, during automatic creation of Production Schedule lines, the system does assign a Proposed Location — most likely using the same logic applied to Shop Orders, namely: The production line’s outbound location, if the shop order is connected to a production line The outbound location of the last operation’s work center The inventory part’s default location I kindly ask for confirmation of the above, or clarification if my understanding is incorrect.Thank you!

Hi everyone,I’m testing the new Informational Characteristics in 25R1. According to the documentation, they should be usable for calculating values in other elements.However, they don’t show up as selectable fields in the configuration formula.I’ve linked the Informational Characteristics to the Configuration Family as required, but they still don’t appear in the formula setup.Is this expected behavior, or could it be a bug?

Hi All,I am trying to unreserve items that are reserved to a Customer Order Line which is supplied by DOP. The reservation was made by performing DOP Netting in the DOP Header connected to the customer order line. According to the documentation, un-reserving can be done by following steps given below.From the Inventory Sub Tab of the Supply Tab in DOP Order, right click the reserved stock line and choose the Manual Unreserve option. It takes you to Manual Netting from Inventory window. From there Qty Res value can be reduced to unreserve Reserved Quantities.  However, I am getting the error Qty Reserved Can’t be Less Than Qty Delivered.  This is due to Reserved Qty being delivered to Parent Order Is there any work around that I can use to unreserve these reserved items while the DOP Header/Order is still open? 

Dear Friends,Hi,That would be great to help us with attachment file.This issue interrupt our business process and it is an urgent case. Best Regards,Adina 

Hello everyone,We are facing recurring workflow errors in IFS Cloud when users perform updates from the Aurena Native Maintenance Mobile App.ContextWe have a workflow triggered on ActiveWorkOrder when a specific text field (e.g. Directive) is updated.Everything works fine when the update is done from Aurena Web (UAT).However, when the same action is performed from the Mobile App, the transaction fails and appears as “Failed Mobile Transaction” in the Mobility Queue.Observations The workflow executes correctly from the web UI. The workflow fails only from the Mobile App, even for simple actions like updating a text field or adding a document. RowKey is enabled on the entity (ActiveWorkOrder). It seems the mobile event payload is incomplete (some optional fields are missing), which may cause the workflow or trigger to crash. Questions Does the Aurena Native Mobile App send partial payloads when updating an ActiveWorkOrder (only modified fields)? Is it expected that optional field