Last updated on MARCH 18, 2016
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 and later
Information in this document applies to any platform.
If a Vendor is created with a Classification other than 'HCM', Vendor data is NOT being sent to HR. When the Classification is updated to 'HCM', Vendor updates are sent to HR, but there is no Vendor record to update since nothing was sent at Vendor creation.
Every time the User forgets to classify the Vendor at creation as 'HCM', the Vendor has to be cancelled and recreated as HCM, which affects user productivity. It is being requested that when the Classification is updated to 'HCM', the entire Vendor data is sent to HR so that updates are applied correctly.
1. Create a new Vendor in FSCM with Classification other than HCM
2. Verify Vendor does not exist in HCM (only Vendor’s classified as HCM are added to the table)
3. Using the same Vendor, update the Vendor in FSCM with Classification to HCM
4. Verify Vendor still does not exist in HCM (update message was sent but the Vendor does not exist in HCM)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms