X

News and information to ensure your investment in PeopleSoft continues to power your organization to success.

Universal Identifiers as Delivered functionality in PeopleSoft

Tadipatri Sudarsan
Product Strategy Manager

Implementation of GS1 standards has become a very high priority area for the Healthcare industry. This necessitated implementation of “Global Trade Identification Numbers (GTIN)” for the Inventory Items and Non-Inventory Items in the Healthcare industry. PeopleSoft has recognized this need and delivered functionality for the users to implement GTIN and other global numbering schemes for their business organizations.

GTIN is not the only Universal Identifier supported by PeopleSoft. There are several other Identifier Types used across many different industries. To cite few HIBC, SKU, UK, HI and more. To support this functionality PeopleSoft has designed functionality to allow multiple Universal Item Types under which multiple Identification Numbers could be entered and associated in the Item Master for Items.

Delivered Universal Item Identifier functionality was designed to  accommodate the need for alternate Item ID's in industry and geography, thus removing the need for customizations.

PeopleSoft is designed to allow users to add UPN Types using the following navigation:

Items>Define controls>Universal Item Id Types 

These UPN Types are associated to UPN IDs  defined for at the level of:

ITEM>UOM>Manufacturer> Manufacturing Item ID>UPN TYPE. UPN Type = GTIN is taken as example to further explain how various Item Identifiers can be leveraged in PeopleSoft transactions in this Blog.

To implement GTIN, users would use the UPN Type of GTIN which is delivered as system data by PeopleSoft. For existing or new Items, users would link the GTIN IDs using the navigation:

Item definitions >Manufacturers> GTIN 

The GTIN for an Item is distinct for each Unit of Measure (UOM) and the same can be defined in the Item Definition page. Once this setup of GTINs is done, the system then can default the GTIN in several downstream transactions. Here are some functionality tips that may help users remove the need for customization of GTINs in their Item Definitions.

•At the Item Definition, UPN-Type defaulting rules can be set up so that system prefills the default UPN Types and IDs.

•By defining different GTINs for different UOMs of Items, the system can default the appropriate GTINs while doing Procure-to-Pay transactions.

•Users can search for Items by using UPN Types and UPN IDs as search criteria. In addition, user can also populate Items in transaction lines by selecting UPN IDs.

•In PI-30, GTIN values default onto Requisitions, Purchase Orders, Receipts and Vouchers for each Item, so users do not have to be concerned with doing a manual entry. If the UOM or Manufacturer Information for any line is changed, the system refreshes and defaults the appropriate GTIN value to match the new set of values. When creating Purchase Orders the system would consolidate multiple Requisitions and release POs with a different ordering UOM and defaulting the appropriate GTIN onto the PO lines, removing the need for manually entry.

•When transactions are subsequently viewed, users would be able to see the GTINs referenced for each Item.

•In the Procure-to-Pay Business, beginning with Requisition to Payments the applications ensure the right GTINs for each line item are visible if delivered functionality is implemented.

•Furthermore, if using scanners for receiving activities, we have enabled the Parsing of Barcodes such that it recognizes the GTIN while handling their inventory.

We are currently evaluating, where GTIN and other Universal Item Identifier visibility is desired. We would welcome any feedback you may have as to where you believe this should be enabled over and above the recently delivered capabilities. 

Please direct your input to my email: sudarshan.tadipatri@oracle.com

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha