Buying (Procurement, Demand Planner, ASC, SRM)

Occasionally, there may be a need to cease using and existing supplier; even when there happens to be open POs on them. We are looking to stop a valid supplier from being used for further procurement. Some sort of “status flag”. We have both Purchasing and Finance (AP). We may also need to report on “current inactive suppliers”. Can anyone explain where to complete this activity, please?   Thanks very much.  

We have some parts whose previous months usage is calculated on the first or second day of each month.  How can an issue be done and dated in the previous month for purposes of cost reporting and the General ledger?   Thanks

We are currently running Apps 9.  We have received updated bank information from a supplier (which is paid via ACH).  The original bank information was entered using Address ID 1.  The updated information was entered using Address ID 2 and is marked default.  When we generate the payment information, IFS is pulling in the old bank information (using Address ID 1) rather than the default bank information (Address ID 2).  Has anyone else run into this?

Hi,How can we close a PO (RMB on PO header/line) on the follow example:PO with 1 line with milestones (staged payment). Milestones total amount 100€. Approved and invoiced amount 40€.Now without approving, neither reducing the PO line amount through a Change Order, how can we close the PO?Thanks

We have different manufacturing companies in IFS that are individual legal entities. Companies have Intercompany relations with intersite Order flow handled with MHS messages. Ordering companies order with purchase orders at supplying companies, that sell with customer order. Companies are located on different continents. Transport is done via sea freight with transport lead times from 6 to 10 weeks.For the finance consolidation at year end, we face an issue, that components shipped before year end, that are still in transit at year end, are missing in inventory value for the group. At time of shipment,  customer order is delivered and immediately invoiced. Delivery note is sent with MHS dispatch advice. That means, Supplying company does not have the inventory value anymore. Ordering company has not yet received the purchase order. Therefore, components are not in their inventory value.What is the correct process or setup to handle this scenario from finance perspecti

In Material Requisition screen, how can we know who creates the MR, User NOT the Department?

Currently in system, the authority to view purchase orders(POs) and purchase requisitions(PRs) is controlled by site level access and any user who has the access to a particular site can view the POs & PRs in that site. Is there an option to restrict the view a user has of purchase requisitions and purchase orders, so they can only see the purchase requisitions and orders created by themselves and cannot view ones created by the others? Further, certain privileged users (e.g.-managers) should be able to view the requisitions and orders created by a set of users

Conditional Fields on Purchase Order Lines does not work when trying to make Part description read only based on 'Inventory Part' flag status. (APP9) 1. Go to purchase order window 2. RMB lines > Conditional Fields 3. Select 'Part Description' from the left selection pane 4. Click on 'Add property action' on right side 5. Change property to ' Ready only' 6. Add criterion where Type:1, column:'Inventory part', operator:'=', value:True 7. Click ok and reload window. 8. Add new PO line for an inventory part (where Inventory part is checked) and modify the part description

in APP 9, users are unable to add negative values to additional discount field on sales quotation header, but it is possible to add negative discount on sales quotation line level?

In IFS Applications the warehouse is part of a site which is part of a company. How should I configure the software when there is inventory in a central warehouse which belongs to various Cost Centers, Sites and Companies?

In simple terms, we create a Purchasre Order Change Order (POCO) when we need to make a change to a particular Purchase Order that we are working with. The standard behaviour, even in apps 10 is that when a POCO exists, the user is always asked to make changes via change orders. If you try to make a change on the PO, then the system will give an error, notifying you that no changes are allowed when a POCO is connected, which is a valid error. A customer who is in apps 8, is concerened about this error and they are of the view that this error should not pop-up and the user should be allowed to change the Delivery address under the misc info tab in the supplier window, even if a POCO exists. This is not possible with the standard functionality. However, I found the bug 120640 which addresses this error which comes up when we try to change the delivery address on the PO when a POCO exists. But, it doesn’t seem to make any sense of resolving the issue. It

How ROUNDDIFF +/- (Clearing Positive/ Negative Remaining Stock Value) transactions are created in inventory transactions history. Much appreciate if you could explain this using a business scenario.

Why does not the "Buyer" visible under authorization tab in Purchase Order window, even though an authorization is being fetched? Moreover, an explanation is required for not receiving any email by the "buyer" regarding the authorization when the “NOTIFY_BUYER_PO_AUTH_COMPLETE” event is enabled.

In App 7.5, there is no way of reporting Intrastat for Non Inventory Parts and No Parts in purchasing (importing) them. How can we fix this?

All purchase requisitions allow only Company Owned and Company Rental Asset ownership types, except when created by a process that supports additional types of ownership (such as from IFS/Project or IFS/Project Delivery). Why is ownership "Customer Owned" not available for Purchase requisition lines when Order Code is ‘1- NORMAL’?

PO Authorization is triggered again for all POs when receiving which are already released, irrespective of the date of which the Auth rule is created. How to set an effective date for PO Authorization rules (APP9)? This make users having to authorize old POs again when they receive them even though the Auth rule is intended to authorize future POs.