Total Pageviews

Vendors In PeopleSoft

In PeopleSoft parlance all payees are called as Vendors .In recent versions this has been changed to a suitable name called as Suppliers (Active from version 9.2) . PeopleSoft delivered functionality offers us to store so much information about Vendors/Suppliers. Most of the times Suppliers component (Component name -VNDR_ID) will be populated with the following information.

Vendor General Information (Vendor Id, Short name ,Long name , Vendor Status ,Vendor class ,Persistence etc) 
Vendor Address  (Multiple addresses with phone numbers)
Vendor Contacts (Multiple contacts with phone numbers )
Vendor location  (Location , Currency , Currency rate type ..)
Vendor Payment (Payment method, Payment Group code..)

Different ways to bring Vendor Information into PeopleSoft:

  1)  Vendors can be entered through online by using following navigation  
           Main menu - Vendors - Vendor Information - Add/Update - Vendor 

   2) Using VNDR_IMPORT application engine 

VNDR_IMPORT is having some of the limitations and can be used only within the following situations 

-> VNDR_IMPORT process takes the information from flat files, so we need to create so many flat files matching the record structures that we want to populate. This process internally uses File Layouts for data insertion ,  If we are getting all the Vendor data in a single file and wants to use this process then we needs to extract the data into different files by developing an another custom program before getting started.

-> This program does not do any business validations except field edit validations (prompt table edit/no edit). Needs to apply all the validations prior using this AE.

-> Before getting started with this program , We need to do data mapping and store each file with record name . Suppose we are generating a file for Vendor record we need to store the file in App Server as Vendor.txt 

 - > Run Vendor detail listing report , Vendor summary listing report to validate the data

   3)  Using Delivered Component Interface (VNDR_ID_EXCEL) which is created on the top of VNDR_ID component. Loading data through this CI is common as any other data load by using AE+CI combination.

   4) By using IB messaging
We can leverage delivered IB messages, Web services to subscribe and publish data between PeopleSoft modules and third party systems. Delivered messages are


Message Name
Function
VENDOR_SYNC
Incremental publish and subscribe.
VENDOR_FULLSYNC
Full-table publishes and subscribe.
VENDOR_SYNC_EFF
Incremental publish of current effective-dated data.
VENDOR_FULLSYNC_EFF
Full-table publish of current effective-dated data.



1 comment:

  1. Can you please help me if we can have a standard XML format out of Integration Broker or VENDOR_SYNC that can be readily consumed and processed for VENDOR creation. My intention (as an external system) is to give Vendor data in Peoplesoft native format that will need minimal effort on Peoplesoft side to consume. Kindly suggest the best approach?

    ReplyDelete