Hi @Devni Panduwawala ,In IFS application IEE client Shop order visualizer views, even though you could create a custom menu, It will not be available on the RMB pop up menu as a quick access menu item. This is mainly due to the fact that Shop order visualizer windows are ‘Feature Contents’ where dummyLU s are used.A Container Tab Form Window is used to create a window with tabs for multiple independent data sources. The Container Tab Form Window itself is not bound to a data source. The content of each tab must be a window of its own. Container Tab Form Windows are typically used for grouping of basic data windows.Therefore, this could be considered as a limitation in the IFS application IEE client from the framework perspective.
Aurena client's search pane does not filter in this manner.Search experience in Aurena is completely different. Aurena search pane, a reference attribute's advance mode works independently and does not depend on other search field values.Once you perform the search all search results are taken into account.
As per the standard behavior of the application, the intention of using a catch quantity is for a scenario where there is no direct mapping between the inventory UOM and the Catch UOM. Therefore, it’s the intended behavior of the application to enter the catch quantities manually within a function like shop order split.
IFS Application 10 UPD8 onwards, P6 EPPM 18.8 and OPG 18.8 are supported, and the connectivity will be made through the IFS Provider for Oracle Primavera Gateway (PROOPG) integration. Regarding the last question, PROOPG solution will support any OS which IFS and Primavera can be installed on.
APB will schedule the Shop orders as it finds them on the database, and it will not sequence the shop orders according to the product structure or the manual pegging. Please note that APB is not a material planning engine, but a production scheduling tool. But APB considers material availability with the parameters set accordingly.When you set the need date/ earliest start date for all shop orders in one specific day, APB will fetch the shop orders as it queries the orders from the database, regardless of the pegging or the product structure. And as per the Work center resource availability shop orders will be scheduled. Also, when Dispatch rule is set as none, sorting orders into any order is not applicable. Using Dynamic order processing (DOP), might be helpful with this situation.Additionally, for ‘Always Finite’ material to be available for scheduling, it should have on hand stock or open supply arriving before a certain date. After that date, the operations could be scheduled. El
This print Barcode Label from Shop Order will Print a barcode, which is including the Serial number and other relevant information.Even from the same Shop Order Window, you can run Print Barcode Labels function over and over again and it will generate a new Barcode for the same Serial Number.I checked the same function in Inventory Part in Stock and there also possible to Print many Barcode labels with different IDs for the same Serial number in a Location. So Print Barcode labels function Prints a New Barcode label if performed from the Shop order.But if you do not need to generate new Barcode ID, then the way is to Print from the Inventory part Barcode analysis window. It supposed to reuse the existing Barcode ID and do a re-print.
“Site window> Manufacturing Tab> Shop floor Reporting settings> Override employee cost checkbox” If this is check box is checked, you get the Cost based on the Costs of Labor Class in the Operation defined in routing. If you Uncheck this option and Run the flow, you should get the Cost from the Labor Class connected to the reporting Employee or from HR if Costs have been defined in HR.
The “Shop Order work in progress Report” standard functionality does not give the user an opportunity to define a date range or an 'as of date'. Report runs & fetch data at the executed time itself. (Manually/scheduled) Hence, there is a possibility to have slight changes in the WIP values on the report, and GL analysis window, due to the dynamic nature of the data. Instead, you may assess the feasibility to create & use a custom report (or customized functionality) to fetch Shop order WIP for a defined date range. Or any other criteria that you use to filter out the data on GL analysis window.
Regarding the system connection checkbox. There are two types of activity connections: manual connections and system connections. Manual connections are created by using the Connect/Disconnect Object menu option in Project Navigator/Connections, or by manually connecting the object to the activity using the Project Connection/Connect to Activity menu option on the object itself. System connections will occur in following situations: • When objects are created and connected directly from the project, such as a Project Miscellaneous Demand or Task created on the activity. • When objects already connected to the activity create new objects, such as a miscellaneous demand creating a Purchase Requisition line, a Work Order creating a Purchase Order, or a Purchase Requisition line creating a Purchase Order. • When transactions are posted with the project ID and activity sequence number, such as the transaction when registering time IFS/Project Reporting or the manual voucher row when creat
Planning method K refers to imaginary parts and it could be use in-between steps in manufacturing such as in assembly stage. Even though this part is imaginary and can never be kept in stock, in assembly stage this part could be used to get an idea about its components which are connected. In Project Deliverables, phantom parts with planning method K are allowed in the structure and material plans gives the idea about the connected components or materials. Proceeding with the material plans are restricted as the parts with planning method K are only imaginary parts. That is the standard behavior of the system. Therefore, for the reported scenario if the user needs to proceed without the material and shipment plans it could be advised the Non-Material item type instead of the phantom part of planning method K.
In reserve and backflush Visualization we can have 2 aspects to look at the situation.Reserve BackflushWhen you look at the “Reservation Hierarchy” which is the default setting, since the Connected Availability Control ID is having “NO Auto Reservation” you do not see the qty available in the corresponding location for reservation. But for the same Shop Order Material Line we can see the Backflush Hierarchy by changing the Dropdown option in the header. There we see the qty in the corresponding Location is also available, because “Order Issue” Attribute in the Availability Control ID is = Order Issue. Since the Qty Available in the Workbench is the Qty Available for Reserve/ Issue we get the highest value here because Qty of 2 is available for Issue.You may use the "Reserve/ Issue from” option in the Inventory Part> manufacturing tab. So for a Particular part, it can be automatically Reserved / issued only from the Specified location Type.E,g, If Only from Floor Stock is selected,
Under Sales contract/ General Information, there is a toggle 'Copy Contract Item Tax'. If this toggle is ON, then only when you create an AFP it will copy the taxes defined in sales contract line items to AFP items. If the toggle is turned off, when creating AFP, the tax codes defined in the sales contract items are not copied to AFP, and the system will re-fetch tax codes to AFP based on the central tax fetching logic. Please turn on this toggle if you want the sales contract item tax codes to be copied to AFP.
When a shop order is closed with a SODIFF entry & re- opened for some reason, counter SODIFF +/- entries are generated. And again upon closing, new SODIFF entry is created. Say a shop order is closed with a SODIFF- entry, When the Shop order is re-opened a SODIFF+ entry is generated. It will act as the exact opposite of the initially created SODIFF- entry. The Accounting postings will be the exact opposite credit/Debit entries of the initially created SODIFF- record. Once the Shop order is closed again, another SODIFF- entry similar to initially created SODIFF- entry will be created with exact same postings.
Regarding the Advanced planning board, APB is not a material planning engine, but a production scheduling tool. But APB considers material availability with the parameters set accordingly. That means on hand stock or supply orders should be available for always finite material to be scheduled. Even available, APB will schedule the Shop orders as it finds them on the database, and it will not sequence the shop orders according to the product structure or the manual pegging. If the business scenario demands material scheduling, supplies has to be planned by MRP. MRP will consider product structure levels when it runs MRP low level coding calculation. So, in this scenario, first you need to get the supply sub-assemblies in order which could be done by running MRP. And then plan the material using action messages on MRP. Then you could use APB to align the schedule accordingly. When you set the need date/ earliest start date for all shop orders in one specific day, APB will fetch the sho
When it comes to purchase parts at the receipt, arrival transactions of FIFO parts do not show Material Overheads and General Overheads unlike inventory parts with Standard Cost valuation method, which is why some cost buckets are not appearing on the cost detail tab. This is the known behavior for FIFO parts. As per the Design, the system ignores certain types of cost types; Labor, Machine and Outside cost buckets in the arrival transaction since they are only applicable to manufacturing processes and not meaningful for purchasing processes. In contrast, the transaction fetches any delivery overheads corresponding to cost element 141, which are applicable for parts being purchased. This is how the application has been designed and it explains why all the overheads except Delivery OHs are missing from the transaction. If Part Cost has not been calculated and established according to preferred cost buckets prior to receiving the parts, then the default material cost bucket 110 shows u
The reported error “PL/SQL: numeric or value error: character string buffer too small” occurs when the assigned value exceeds the length of the variable.the reported error probably occurs due to following reasons. 1. Variable length of local_attr_ in New & Modify methods of MRP_PART_ACTION_NOTE_API is 1000. The value assigned to the variable exceeds the mentioned length.- This has been fixed in APP10 by increasing the variable length to 5000.2. Variable length of po_attr_ and note_attr_ in Reschedule_According_To_Mrp of MRP_PART_ACTION_API is 2000. The value assigned to the variable exceeds the mentioned length.- This has been fixed in IFSAPP10 by clearing any existing data of variable po_attr_ and note_attr during each iteration.
In IFS Apps 10 version, from the voucher side there is only one voucher which is created and then one project connection. There is no one to one mapping between the project transaction connections and the voucher connection at this point. So, it maps the first project transaction connection with the voucher connection, and this appears to be a delimitation in the current design. The best way to solve this problem would be to change the way that the voucher is created. i.e. Creating separate voucher rows for the different transactions as required.
Once the required amount is sent to the Handling Unit, then connection to the order is disconnected and this is the intended functionality. Since only one order can be connected to a Handling unit at a particular time, it is important to disconnect it from the order once the planned qty is stored in the Handling unit through the connected order. Then only the Handling unit can be connected to another Order to fill the remaining Quantity if available. If you need to trace what order sent material to a specific Handling Unit, it can be done by searching for the Handling Unit in the Inventory Transaction History.
A custom context which is developed within the IFS application may or may not have an impact with a service upgrade. That depends on the changes implemented on the upgrade being relevant with the customized entities on the custom context. Kindly note that, it is a technical limitation within the IFS Application that the custom configurations/contexts are not upgraded automatically with the service upgrade. However, after any upgrade a system user can log in to the ‘Page configurations’ window and check for any custom configurations that are affected. And the application is allowing you to “rebase the configurations” if there are any impacted areas. You can read more about this on IFS Application technical documentation Tailoring guide> Configuration> Client side configurations -Aurena page designer> Rebase client configurations. https://docs.ifs.com/techdocs/22r2/040_tailoring/225_configuration/200_client_configurations/400_rebase_configurations/
The LOV for “To Location” in WaDaCo “PROCESS_TRANSPORT_TASK_PART” process, is included only the To Location which is mentioned in the transport task. The user is allowed to enter a different location by scanning or entering the value manually. So, this gives the user the option to clearly see the To Location which was planned for a particular transport task while giving the option to enter a different location as well if there’s any requirement for that.I think that’s the main reason for the system to be designed this way
Hi Udanee,The project activity scheduling using the Gantt chart should ideally arrange the activity start dates considering the predecessor /successor activities. I think you can route a support case with IFS unified support regarding this, Regards,Dinudu Kankanamge.Senior Consultant - IFS Unified support.
Hi ,have you attempted Create collective invoices function for this?IFS Cloud DocumentationBr,Dinudu KankanamgeIFS Unified Support.
Hi Sangitha, Usually Purchase Lead time is not considered in the required date field on a project demand. It usually shows the end date of the activity. If you could elaborate the places where you have defined the lead times and the nature of the project demand, using a actual/simulated example in IFS Application client, we could clarify the details further. Thanks & Best regards,Dinudu Kankanamge.IFS Unified Support.
HI NicKhos,Usually “part Revision” is a numeric value which starts from 1 and increments. If you are using the engineering parts, “Engineering revision” can be an Alpha numeric value, and it can be visualized on the part revision screen as a separate field ‘Eng Rev”Hope this helps.Regards,Dinudu KankanamgeIFS Unified Support.
Hi Sangitha,For the required date for the miscellaneous demand is the early finish date for the connected activity minus the offset. This field is automatically updated when the early finish date of the activity or the offset is changed.I believe you can look into the possibility of a custom field/Customization, if the business demands the required date to be planned based on the lead times.Regards,Dinudu.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
