390 likes | 412 Views
TPCx Version 11.0. Steve Heister Helen Robie. Objectives. Review 11.0 New Features Review features available to Trading Partners Review features available only to P21 Administrators. Rationalization Enhancements. Rationalized Failed Requests Disable Automatic Rationalization
E N D
TPCx Version 11.0 • . Steve Heister Helen Robie
Objectives • Review 11.0 New Features • Review features available to Trading Partners • Review features available only to P21 Administrators
Rationalization Enhancements • Rationalized Failed Requests • Disable Automatic Rationalization • Add Key Fields to Re-Rationalization List
Rationalizing Failed Requests • View details of Failed Rationalization Requests • Compare failures to items stored at the Hub • Manually match failed item to Hub item to rationalize
Rationalizing Failed Requests • Select Manufacturer to view failed request submitted against
Rationalizing Failed Requests • Search for unmatched items to rationalize • Sort by Item Code, Part Number, UPC, or Description
Rationalizing Failed Requests • Select Unmatched Items
Rationalizing Failed Requests • View items selected to rationalize • Remove Items you don’t wish to rationalize • Submit to perform rationalization
Disable Automatic Rationalization • Only available in Partner Management • Admin can disable automatic rationalization for a Trading Partner with a specific manufacturer
Add Key Fields to Re-Rationalization List • Edit of Key Field sends a delete request and a re-rationalization request • Prior to this version, only ‘Item ID’ edits would trigger these actions • This feature adds ‘UPC Number’ and ‘Supplier Part Number’ fields to Key Field List • Now the edit of all three of these fields triggers the above actions
Dead Stock Enhancements • Un-Post Dead Stock
Un-Post Dead Stock • Select Parameters to review dead stock items to un-post • Select the items that should be un-posted • Documents are then sent to the spoke system, by vendor, containing all items to be un-posted
Document Management Enhancements • Human Readable Transaction Reports/Emails • Enhanced FTP Flexibility • FTP and Outbound Trackers • Consolidation of Document Tracking Parameters
Human Readable Transaction Reports/Emails • The Hub now sends automated alert e-mails with a hyperlink to the document stored on the hub. • Replaces File Attachments & detail added to the body of emails • Making user click on link & log into TPCx before viewing documents provides more secure communication
Human Readable Transaction Reports/Emails • Company Profile/Document Support • Specify email recipient contact for each document type sent from a specific originating Trading Partner • Can also set up default contacts to receive specific documents when sent from any Trading Partner • Specify contact for Hub Unsupported Documents
Human Readable Transaction Reports/Emails • Document Box • View Human Readable version of all documents from Document Box • Print Human Readable version to PDF • Save Human Readable version to .txt file
Enhanced FTP Flexibility • FTP Screen moved to Relationship Level of Partner Management • Relationship Summary Screen now includes an indicator if there is FTP information on file • New FTP Parameter Screen • Accessed when selecting a Relationship w/ FTP information • Store FTP Parameters at the relationship level • Parameters dictate FTP specifications for documents sent from Originator to Recipient
FTP and AS2 Outbound Trackers • New FTP Outbound Tracker Screen • View Status of outbound FTP documents • Resubmit FTP documents • AS2 Outbound Tracker now allows you to select several documents at once for deletion • Automatic email now sent to assigned contact for failed FTP and AS2 documents
Consolidation of Document Tracking Parameter Pages • Prior to this version, the Document Tracking parameters were displayed on multiple pages • User would need to click on the ‘Next’ button to progress through set up screens • The new feature consolidated all of the parameters on to one screen allowing Document Tracking setup/editing to be done with fewer keystrokes
EDI Mapper Enhancements • Testing website maps within the website itself
Projx#19147: Testing Website Maps • Allows you to submit document and view result document • Does NOT translate itemcodes
Accessing new test function • Map must be deployed to see “Test” button
Using new function • Provide name of file on local system as input (X12, XML, …) • When testing X12, provide X12 format, not XEDI
Using new function • Resulting document presented in listbox • Use “Save” to save a copy of the test result document
TPCx for Non-P21 Distributors • Allowing Non-P21 Distributors (No-Spoke Folks) to use TPCx
Projx#21071: “No-Spoke Folks” • For any type of partner that has no business system for us to communicate with: • Manufacturer, Distributor, Marketplace, etc. • Can be members of TPCx but don’t have to be
Projx#21071: “No-Spoke Folks” • Let’s take a look at how “No-Spoke” partners participate in various TPCx functions… • Pricing Service – Not allowed • Trading Partner Administration • Item Rationalization and Item Maintenance (AMU, Dead Stock, etc) • Relationships • GetPA • EDI
Trading Partner Administration • No MQSeries queues • No “override” queues either • No P21 Customer ID • No System Number • May or may not be “inventory hosted” • Must be inventory hosted to use GetPA
Item Rationalization • Create Request – uploads file rather than querying business system • Normal XML request created from uploaded contents • Flows through system and DCTool normally • Requires customer approval (Review Request) • No response document sent to customer system
Item Maintenance • No automatic AMU Query • New web page “Create Maintenance Request” uploads file to create UPDATE_HUB_REQUEST • Good for: • DEADDATA (Dead Stock) • USAGE (AMU) • HOSTEDDATAUPDATE (Update hosted item details) • Normal XML request created from uploaded contents – flows through system normally • No response document sent to customer system
Relationships • Can have relationships – can even initiate them • Do not “rationalize” relationships (no vendor/customer codes)
GetPA • “No Spoke” partner must use inventory hosting for their items to appear in GetPA • When GetPA response is generated for hosted item, message gives “freshness” date
EDI • TPCx transmits EDI documents through: • MQSeries • AS/2 • FTP • AS/2 and FTP don’t require a business system to trade • Partners who use a VAN don’t require a business system to trade
EDI • When a “No Spoke” partners doesn’t use a VAN and doesn’t use AS/2 or FTP: • They can receive documents via document tracking (Projx#17510) that came through TPCx hub • They cannot send documents to TPCx hub
Download These Slides • On the network: \\p21bfs\EducationalServices\Read\WBT\Class_Slides\InternalTraining\TPCx\OverviewTPCx11.ppt • If you’re viewing this class via WBT… • Click the ‘Class Notes’ button, found in the Links menu at the top of the Participant app