Hi Cindy,I seems to not understand the case, it all starts with a purchase requisition on the Work Oder for an non-inventory part. From the purchase requisition a purchase order is created.Then the non-inventory part arrives and we get a cost line on the work task, this line is seen as a preliminary cost on the work task and we don’t handle the accountings on the work task for it, it is there to facilitate for early invoicing of the customer.Then the supplier invoice comes and we handles the M93 from the invoice and repost it to TP3.I’m not following as this is as it was in IFS Application 9 also with the use of Cost Sold service with T3 on the supplier invoice cost./Hans
Hi, I don’t recall all the details of Apps8 in my head so I don’t have the exact names of the fields in application, but in general it is like following:The flow begins when planning the material on the Work Order, here we get the planned cost retrieved from Inventory using the current inventory cost. This is our best estimate of coming cost.Then by issuing parts on the Work Order we will get the real cost from the Inventory transaction for the Issue of the part.Then we transfer lines from Work Order to Customer Order for invoicing we transfer the cost we have on the Work Order to the Customer Order.
Hi, my take on this without deep check is that the location customer address is allowed together the customer on the Service Request. Test with adding the customer on the service request and see what’ happening.
Yes, there is something strange on how the address is collected from the Location.
Hi, intended functionality is that material lines for pure purchase parts is to create a purchase of that part, but it is not implemented yet for the request and is a known limitation, plan for now is to get it delivered for IFS Cloud 22r2.
Hi, this is a defect that should be reported to Support, the overtake with TP3 is always to take place. Report it thru normal support.
Service Contracts is for the traditional Work Order Based service, then Request contracts is for the new Request Management service. But there is actually more than similarities, they are both built on the same foundation./Hans
Hi, This is not specific for the question in this topic but a more general question related to Pre-posting and the posting control.For functionality in general we try to “Isolate” the majority of the users from the accounting as something that just happened by using posting controls for automatically building the code string according to rules, this also reduces risk for users to select wrong code part values. On work tasks the primary use of Pre-posting is to handle the cost center and Fixed asset object stated on the Equipment.From my side I see two base cases here when manual pre-posting is needed on work tasks, 1, when the needed accounting info is missing on equipment’s. 2, when there is missing posting rule possibilities for automation or the control data not can be found thru the work task. The first is most a matter of data setup, but the second is much more interesting for me as here we have a good possibility for improvements, so I would really want to learn about the situati
There should not be any difference for this as I know it.Report the issue to support for deeper investigation./Hans
Hi,If I got it correct there is one part that is issued that might be warranty, and another that not is warranty?As the all material accountings on a work tasks all uses the same posting control there is good way to handle it on the same work task.What you can do is to put all costs that might be covered by the warranty on one Work Task and the rest of the costs on another. Then you can set up the from Apps10 new Reposting/WIP functionality to handle the posting control by Cost Codes.Short version(more info in documentation):Set up Cost Codes to handle Warranties, preferably to have a WIP handling as Preliminary Warranty costs.Connect the Warranty Part Work Task to a Warranty.The issue cost will now be WIP accounted for as Preliminary Warranty costs(if not WIP is used they will be direct accounted for as warranty costs).When the WIP reversal occurs the cost will be reposted as Warranty Costs.If the parts not is considered as warranty covered remove the Warranty connection from the Work
The manual way to do this is to add a Fixed price Planning line on one Work Task, this line should get “Work Order Invoice Type” set to “Fixed Line”. This will result in a Sales line for the charge.Then to automate this there is a need to set up a Custom Event for the first work task on the Work Order to add this line.If all Work Orders is on Service Contract you can set up a Work Task Template with a planning as above and connect this Work Task Template to all Services in the Execution Tab./Hans
As said above, category objects was intended for Service. Scenario is that the objects at the customer changes over time and you don’t always get the new objects for registration in equipment and contracts when they appear at customer site. If you then have a category object on the Contract you can use any object on the Service Request to be covered by the Contract, this also means that there is need for manual validation that the object on the service request is the of the type covered by the category object. If it is an object we don’t know about it can be registered in the service request registration or by the technician at customer site doing the work.Also there is a scenario that service company don’t want to keep track of the objects at all and then keep the category object on the service request thru the process, in this scenario you have no good handling of reclamations and similar on the work done as you don’t have recording for the actual object.For doing work on known equip
The CO have to be in state Invoiced/closed and the Invoice have to be in state Posted Auth, Paid Posted or Partly Paid Posted. /Hans
Base thinking here is that the time is not consumed in the future, same as you cannot do a material transactions into the future. And if the resource is an employee in the company I cannot see that someone would authorize time that is to be performed in the future.What is the business scenario for this need?Problems might come in authorizing and transferring postings to GL, and there might be other things also as general rule has been that no transactions is in the future so no validations for future transactions has been needed to be implemented.
Hi, the logic behind this is that Pre-posting overtakes everything, meaning values retrieved by control types is replaced with the pre-posting.The mechanism here for creating the code string for the postings is to first process the control types to get all defined values from there, this includes control type “Copy from Source”, after this the values from the pre-posting is set to the code string overriding the values that already might be there.
Base is that you can set the deliver address for a customer on the Parties Tab on the Equipment Object.Now we don't take this to as the delivery address for Periodic invoicing, but seems like a fair request to be added as future enhancement.Also the location and address of the equipment address can be from the customer that is to be invoice but it could also be from other customers, or be just a pure location address, and as the delivery address is used for tax handling it need to be a customer specific Address. So my take on this would be to add a delivery address on the Periodic price line to be defaulted from Equipment on the contract but possible to alter. We also need to consider the fact that an service line on the contract can have multiple equipment with their own addresses.
Hi,In the planning the cost amount is a calculated column from the saved quantity and unit cost.On the transaction the unit cost is a calculated column from the saved quantity and cost amount.The cost retrieval from things like Resources, material, purchase parts, etc. is always per unit, so that is then also applied to planning manual Expense and External planning.Then for the reporting the cost amount is calculated, rounded according to accounting currency, and saved on the transaction and used for accounting, so this is the actual amount used in GL./Hans
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.
