HelloReusing older revisions can be done by copying the older revision to a new revision with a non conflicting validity period. Updating revision numbers is tricky and risky as the functionality is not designed to support your requirement.Have you tried using alternates? This will allow to reuse ratios which have been used before, allow easier switch between different BOMs, and remove the hassle of phasing out older revisions (and the build up of revisions). Even though this could build up a number of alternates, reusability of alternates within the valid time of the revision could slow down the build up.Furthermore, you can use the rules with ‘minimum lot size based qty’ to change the alternate automatically depending on the volume (lot size). If there is a definite and logical way that decides the ratios, then it is possible to consider Configuration Structures as well.Above are some options that can be used. But without knowing the exact business scenario it is not easy to make rec
HelloI did a quick test and it worked for me. I followed steps belowCreated Manufactured part and a purchased part as a component of it (both dop) Created a control plan for the manufactured part and made it active Created a dop header for the manufactured part and released it Created a shop order manually for the manufactured part Released both shop orders“Shop Order Analysis” command was available in both instances in the operations tab in the shop order.Things to try outRefresh the page Go to report operations page and check whether the command is available in that page Do share how things worked out :) DOP connected shop orderOperations tab of dop connected shop orderOperations tab of non-DOP connected shop order
@ChamilaW these are the parameters we are using. Hi @camoncrief , Unfortunately the behavior I saw are from the added features mentioned by majose. Therefore, my assumption of similarity between App10 and 8 is faulty. As he mentioned, “in Apps8 we just don’t have this “mechanics” within IFS Master Scheduling. :-(“. I’m Sorry about the inconvenience caused :/ Kit Part MS LEVEL 1: Kit Component MS LEVEL 1:
Did a quick test in App10 (where I don’t expect changes for behavior in MS) and got following resultsKit, with 2 components (all manufactured with buildable structures) Planning method G for Kit and Kit Component 1, order cover days=30, no SS or Min LS for simplicity MS L1 part defined for Kit and Kit component 1 (DTF,PTF=5,10) Demands and forecasts KIT component forecast on Today+16 days, qty 50 KIT forecast on Today +15 days, qty 40 KIT component customer order on Today+14 days, qty 45 KIT customer order on Today+14 days, qty 35 Ran MS L1 for KIT Ran MS L2 for KIT componentProposals created for total qty of 170 on relevant daysRan MS L1 for KIT for Today+7 days to simulate the situation when proposals are within DTF and PTF Ran MS L1 for KIT component for Today+7 days to simulate the situation when proposals are within DTF and PTF Total requirement for component (including MS forecast and demand for KIT) is catered by SORs. However, there are many parameters which are not specifi
I have a dataset with following details, made some tweaks and ran your flow.Manufactured part with one component Routing has 1 operation, MRF=40h, work center average capacity=8h (site manuf calendar, all work center calendars are 24*7) Routing made buildable, lead time calculated and updated on routing alternate Also run cumulative lead time calculation with update setting on (if everything is fine upto this point, manufacturing tab in inventory part shows cumulative lead time and manufacturing lead time as 5) Material requisition for top part due on Next Friday +10 days (a Monday) Ran MRPCreated SOR has SO start date as Next Friday+5 days (a Wednesday) which is 5 days apart from due date So the calculation is done correctly. I however, did not quite understand “problem with Shop Order requisition due dates relative to shop order start dates” but i assumed we’re talking about SOR due dates and start dates. My pointers are,check calendars check work center average capacity check wheth
There is no direct data setup to achieve this in the core application. However, It is possible to setup a sales rule to call a custom method.What you see in the LOV (see screenshot) are the 5 demo methods shipped with CFGRUL. Demo methods can be a good inspiration to write a method to calculate weight/volume.component - cfgrulutility package - ConfigSalesRuleExternalYou have to add to the view and implement the logic in plsql file.
I will also go through some of the things discussed here... In our setup - we have some parts we both buy (Purchase) and build (Manufacture). What we figured out is (and this applies to both Apps8 and Apps10) The inventory part type determines your default supply process - but doesn’t lock it in. You can add a Purchased Part to a Manufactured part You can add a Manufactured structure to a Purchased (not purchased raw) part If you normally build something - but need to buy it Create a purchased part and supplier for purchase part Create the PO I can’t remember if you can use supply code PO Transit or PO Direct on a manufactured part. In our scenario, we were always building something we normally buy. If you need to - you can manually peg the customer order line to the PO If you want to build a purchased part and want to peg the shop order to the customer order line, you have to use supply code Invent Order and manually peg. You can’t use supply code shop order. Hope this helps
Following are 2 answers which were posted for a similar question Assuming the requirement is to run a manufactured part through the purchasing process, you can change the Part Type of the inventory part to “Purchased” and save. This will create a product structure header with type “Purchase” and a purchase part. If the main sourcing method of the part is to manufacture it, change the Part Type back to “Manufactured” (this will not remove the purchase part, thus it will still allow purchasing of the item). As explained by @ChamilaW it is fine to both manufacture and purchase the same part in IFS. The part type can be seen as a default. Important to remember however is to use a cost template for the part that captures both manufactured and purchase costs. For the part cost calculation you have an option on the cost template to use either manufactured or externally acquired (purchase) costs
But that wouldn’t work ? It is 3 different parts in one box? Which has 3 different part Numbers. e.g. part no 1 is the kit (containing 3 parts) part no 2 is one of the parts inside part 1 part no 3 is one of the parts inside part 1 part no 4 is one of the parts inside part 1 i am not familiar with your part structure, but it sounds like something detached parts could handle. That said i have not tried it out myself. just seen that detached parts are “containing” other parts and would look like the obvious use for “kits” Thanks Julian, I did miss the part about three unique parts.
Define a new unit of measure, say “KIT3” for a kit of 3 pcs, with the base UoM as pcs/PCS/EA and conversion factor as 3. Set the inventory part UoM as the base UoM above Set the UoM in Supplier for Purchase Part as the defined UoM (KIT3), set the cost for a kit. Raise the purchase order for 1KIT3 Receive PO, cost per unit will be cost of kit/3 Hope this helps
Assuming the requirement is to run a manufactured part through the purchasing process, you can change the Part Type of the inventory part to “Purchased” and save. This will create a product structure header with type “Purchase” and a purchase part. If the main sourcing method of the part is to manufacture it, change the Part Type back to “Manufactured” (this will not remove the purchase part, thus it will still allow purchasing of the item).
Consider a scenario where one sub assembly(assume it has one component part) is used in two products which are having demands. Now the MRP demand for the sub assembly component can come from both products. Once MRP is run, in MRP part information pages, you may notice the tree navigator (opens up when you click on Expand in the record selector). Bottom up, and Top down pages has the one difference, which is the direction of tree structure population. In Bottom up, you can move up in the product structure investigating demands for the part. In top down, you can move down in the product structure investigating how supplies are planned for the components. When clicked on tree nodes, you can view MRP part information for that specific part selected in the tree navigator.
Setting of DTF is based on manufacturing lead time and PTF is based on cumulative lead time. When a forecast is put in between the DTF and PTF, it is an unexpected requirement for planning process due to reasons like components not being planned to do the production before the forecast date. Therefore, system will create a proposal for the practically possible closest working day (i.e. first day after the PTF. MRP can plan components against this proposal). When you run MS on/for the following day, created proposal will cross the PTF, and it will get fixed.
I’m afraid you cannot do it in the core application. Currently the system does not maintain timestamped records of structure alternate state changes (tentative→ buildable etc.). When referred at a later point in time, records should not exist with parent structures having unavailable (not phased in) components at that point of time. Ensuring above is done by restricting such records being entered using the error message.
You can try setting MS Level 1 Part as, Create S/P request = Do Not Create S/P Req. This will allow the forecast consumption without creating shop orders/requisitions For components, Run MRP to get the component supplies created When CO is not released, Forecast is consumed. No shop order created. After MRP run, component supplies are created for MS Supplies. When CO is released Forecast is consumed. Shop Order Created as CO is released. MRP creates component supplies against the shop order and MS Child.
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.
