Presentation on theme: "“What’s new from R6 to R7, to R9 ……”"— Presentation transcript:
1“What’s new from R6 to R7, to R9 ……” The Latest in XA PM – R9“What’s new from R6 to R7, to R9 ……”XA Procurement ManagementRod Fortson – CISTECH, IncSr. XA Process Consultant & Certified IFM/AM, Costing & ERP“The Mapics Experts”
2PM – New functions Application Settings Code File Maintenance/Master filesPurge/Reports/Mass Update item LevelBuyer – Item RevisionsEPDM- Item Revision / Implementation StatusEnhanced Vendor MaintenancePurchase Request and Requests (with History)Online PO VarianceAttachments & maintenance history to historyShip NoticesDebit Memo’sPO Tasks – IDF Level 1 Options
9PO Variance and Print Reports Send – Confirmation TABHTML/PDF or Text File – Output Tab
10Quotation Requests & Contracts Analysis Reports Send – Confirmation TABHTML/PDF or Text File – Output Tab
11Item Revisions for a Buyer The Buyer Items option in the Buyers object now displays item revisions, including the current revision and other revisions for each item. For example, from a buyer in Procurement Management (PM), users can now see a list of all items assigned to that buyer and all revisions of those items.
12Item Status – Impact on PM With Release 9, every item revision must have an implementation status.An implementation status can be assigned to more than one item revision.The Release to purchasing attribute controls whether a requisition or purchase order can be created for an item revision.The Procurement Management (PM) application uses this status code to determine whether a requisition or purchase order can be created for an item revision.If the Release to purchasing status is set to Yes, the purchase order creation for the item revision can proceed. If set to No, the purchase order create function cannot process the item revision.The Release to purchasing attribute provides an additional level of control for which revision of an item is eligible for purchase.
13EPDM – Item Revision Changes which could impact Purchasing Stocking UM /Enterprise Item - All revisions of an item within an enterprise will use the same unit of measure for stocking the item.Inventory code/Enterprise Item -All revisions of an item within an enterprise will be the same classification in inventory.Unit Cost Default /Site (default value) -The unit cost can vary by revision between and within sites for this item. For convenience, the Unit Cost Default value of the current revision is stored at the Site Item level.Batch/lot control /Site -All revisions of an item within a site will have the same batch/lot control setting.Discrete allocations /Site -All revisions of an item within a site will have the same discrete allocations setting.Inspect-on-receipt /Site -All revisions of an item within a site will have the same inspect-on-receipt setting.Item type /Site (in some cases) For item types 1-9, the value can vary by revision. The default value is stored at the Item Site level. 0 must be same.QC (shelf life) /Site- All revisions of an item within a site will have the same QC valueShelf life days /Site - The default value is stored at the Item Site level, but the value can be overridden within revisions.
15Vendor ContactsMany Contacts for VendorMain in Vendor Master
16Vendor Enhanced Security Two new field security categories have been added to maintain separation of duties. The VNDPUR category controls which users are authorized to more than forty PO-related fields in the Vendor object. Another category, PAYMENT, controls about two dozen payment-related fields in the PO and related objects. This field security applies only to the client, not the legacy (green screen) functions. Companies desiring this feature will need to set up security so that the only way for users to maintain vendors, vendor items, POs, buyers and items is through the client.
19Add Color Schemes to Views by Row or Column Any PO over $10,000 is highlighted
20Add Color Schemes to Views by Row or Column Any PO over $10,000 is highlightedand the Purchase price is less than $1.
21Purchasing – New Purchase Request Object Purchase Order RequestCreate/Maintain options
22Purchase Requests New object on main browser Ties together requisitionsLike a headerHandle requisitions as a groupMakes entering and tracking requisitions easierPurchase RequestBuyer: John DoeWhs: AtlantaREQ1 123A 10 Apr 1ITEMQTYDATEApr 8Apr 8Apr 1Apr 6Priority: 1Contract: 123
23Purchase Requests From the requisitions Overall status All/Some/None
25RequisitionsPurchase Request items are requisitions
26Purchase Request details card Default values for new requisitions added to this Purchase RequestRequisitions
27Benefits Purchase Request is for the requisitioner, not the buyer No change to buyer’s processManage and track requisitions as a groupFor order, job, contractQuick glance shows statusDrill-down to see more
28PO Variance Now online Choose among comparisons Inquire into it any time from PO or PO HistoryCan still print reportChoose among comparisonsStandard vs. Actual vs. Expected
31Purchasing – New Debit Memo Object Purchase Order Item Debit MemoDisplay/Change optionsVendor Return created from Scheduled receipts/ Creates Debit Memo
32Shipment NoticesA Shipment Notice is an Advance Ship Notice (ASN) from your vendor of what you can expectin an upcoming shipment. It may have one or more line items, from one or more purchase orders, and can optionally describe what items are in one or more containers. Since an ASN is what the vendor actually shipped, it makes it much easier to receive a shipment. Instead of looking up POs and doing partial receipts, receiving personnel can simply receive by ASN--the whole thing, one container at a time, or item-by-item.The system knows what PO line items quantities were shipped, so the PO data is updated properly as receipts are processed.
34Shipment Notice Detail Select from different tabs to viewInformation or take an action
35PO History (Through PM) Move attachments to historyHistory order has same attachments open order didMove maintenance history to historyHistory shows evolution of POPOHistPOHist
36IDF PURCHASING TASK OBJECT The IDF Level 1 interface streamlines the access between Power-Link applications and the XA applications.
37IDF FUNCTIONALITY- XA Development Framework Provides an integrated flow for users when working with information in both Power-Link and in the functions previously only accessible in the XA legacy applications.Provides access to the IDF Level 1 tasks related to that application or to the Power-Link functions on the application card.Allows a user to enter information or to select the options required to perform the task.An IDF Level 1 application window contains the icons users click to start specific tasks. XA organizes the icons in groups of related tasks. Each task icon starts a specific task.The IDF Level 1 windows cannot be customized in the same way that Power-Link windows can. Also, some advanced Power-Link functions, such as broadcasting and receiving information among application windows or attaching outside files to application records, are not available for IDF Level 1 functions.IDF Level 1 does provide an Additional Tasks feature that allows users to add frequently used options to the IDF Level 1 application windows through the Menu Maintenance function in Cross Application Support