We are having some purchase requisition line status not changing to “PO CREATED” after it is released and PO is created. Sometimes we need to change the Supplier then the requisition will go into “ Authorization Required” status. For some reason, when that Approval of the requisition is done again, the requisition header will move back into “Authorized” status. That is when the planner doesn’t have the ability to re-Release the requisition. Is this the reason the line status hangs in status “ Released” forever even if a PO is created? IFS help notes:The selected purchase requisition lines are converted into a purchase order. The requisition lines are added to an existing purchase order, or a new purchase order is created. The status on the requisition header is updated from Released or Authorized to Closed when all the requisition lines are converted. The requisition line status is updated to PO Created.
I am creating PM Actions for each of my functional objects that need a yearly Preventative Maintenance done but system will only create for current year. (We have IFS9 version)I am using the Separate PM Action:Under General Tab- enter start date 6/15/2021 as DAY start unit then Interval of 1 and Interval Unit as YEAR. Yes is the Generatable Then on another PM I added a Calendar ID that we use for 1st shift to not have IFs schedule or generate a WO on a holiday or weekend. BUT still nothing is created for other years like 2022, 2023, 2024 etc.why?? Does the revision need to be checked off and I have to create new PM for all my objects every year?
When setting up the Competence Requirements like Groups, Scale and Elements: Seems to be a required field that is required called Competency Point. We are not understanding the reasoning of why or how to set up the numbers correctly.We are on IFS9
Is there an work around step that we can do to count back in to inventory of a SN object and not have to create a new SN* object?I believe the reason for our stockroom doing this is due to the time lapse where shop floor held part that was needing rework for month then closed out the shop order. Which in turn make it difficult for us to move that SN part. Any thoughts?
We have part numbers that contain symbols like + but when we scan the barcodes IFS does not recognize the + so is this a set up or IFS incapable?
I am looking at shop order statuses daily and coming across many negative values which makes it difficult to find product and report accurately. Is there a method of restricting buyoffs in IFS if the quantity being signed off is greater than the executable quantity in that Op? See below: 6 units were never “moved” in IFS from Solder, but inspection was able to sign them off on their op in advance. This happens often when multiple kits are being worked together (which is to say, all the time). Secondary long-term question: Ideally, I would be interested to know if these three traceable data collections on op buyoffs are possible in IFS:When serialized, a data entry to input the serial number(s) being moved, maybe in the same pop-up that quantity is typically entered. In addition to or perhaps replacing our limited test analysis, and searchable after signoff. The material & lot used on that op, with a warning if the wrong consumable part number was selected to be used on an assembly
When we scrap wip from a Mfg shop order we run into a few problems:We can’t re-use any of the material/components that are still good from the parent part we had to scrap. when we go to receive the finished products left on the Shop Order we sometimes get message about not enough material due to some scrapping of another finished product.
We are creating Shipments and doing the Approval then Finalize of Shipments. The Part serial history does show “Delivered on customer order ***” but the Ownership is still Company. How can we bring back a part for repair if the ownership never changes? Is this the correct process for shipments?
When a new employee is created, is there a way to populate the employee’s Job Specification Elements in under Employee>Qualifications>Competencies section without assigning any dates? The way the system is set up now, it automatically assigns the date the Job Specification is assigned. This is confusing when reviewing the employee’s list of Elements – it makes it appear as though the employee has already been trained, when in fact – they have not. Is this where the Competency Point values come into play?
Already have an account? Login
No account yet? Create an account
Enter your username or 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.
