Background : This is one of the outbound SCM extract object used in our fusion cloud integration . Oracle BICC was used to extract the vendor and vendor site details
( Bulk and Incremental)
Requirement : Integration requirement was to extract the vendor and vendor site details for a given BU and integrate the same to <Third Party> .
Build Details : Created oracle vendor extract using BICC with 2 extract programs (Bulk and Incremental). Incremental vendor extarct data is based on last update data .
FLOW : Oracle fusion cloud =>UCM =>OIC => <Third Party>
Version : 21 A
Few Tool Limitations/Issues/Highlights :
1) View objects were not available for Vendor : We have used vendor sites veiw object since it has satisfied all our extract columns requirements.
(If View Objects are not available , what all the other options ? A) Request for vew object with BICC support team? B) Extract header view Object in the staging at destination
and update all the Line View Objects one by one sequencially? )
2) Enable and Disable Vendors/Vendor Sites not reflected in the incremental data for the future enables vendors/sites :
After analysis we found that , issue was with enabled check box was not a database item so it is not updating the last_update_date for the future enabled vendor/vendor sites data.
3)Filtering Condition : Not able to do dynamic filter condition based on the parameter values .
4)Parameter Options : Not able to customize and pass the filter condition to the view objects to filter the data.
Note : Oracle development team is working on the feasible solutions on above mentioned points.
Design : Bulk and Incremental
Bulk Upload:
Bulk Upload will be initial upload from oracle procurement to <third Party>, where all the vendor and vendor location definitions are exported to UCM in
XML format through BICC that is inbuilt functionality of Oracle Cloud. The selection of the vendor in the procurement module is done using BICC filters.
The business may choose to import records based on the filter as per business requirement. Only Active vendors in the system are part of the integration.
A few examples of attributes that will be passed to <third Party> in this integration are Vendor Name, Legal Entity, Business Unit, Location Details,
supplier end dates, supplier site status, supplier site code, supplierid, suppliersiteid etc. Procurement cloud Schema will need a mapping with <third Party>,
and each field attribute will be mapped to the corresponding value in OIC. These values will have a DVM for mapping between <Third Party> and procurement cloud.
Filter Conditions:
__DATASTORE__.BUShortCode=’US1 Business Unit’
AND (__DATASTORE__.SupplierEndDateActive IS NULL
OR __DATASTORE__.SupplierEndDateActive>CURRENT_DATE)
AND __DATASTORE__.SupplierSiteStatus=’ACTIVE’
AND ( __DATASTORE__.SupplierSitePurchasingSiteFlag=’Y’ OR __DATASTORE__.SupplierSitePaySiteFlag=’Y’)
Filtering Criteria descriptions
Business Unit Name : Update the business unit name as per the implementation requirement/setup.
SupplierEndDateActive IS NULL : Active Supplier data
SupplierEndDateActive> Current Date : All future end dated supplier data
SupplierSitePurchasingSiteFlag=’Y’ OR SupplierSitePaySiteFlag=’Y’ : Bulk extract would filter enabled records of purchasing site flag OR supplier site pay site flag .
In this Vendor extract run bulk and incremental job run design/mapping is based on the view object “FscmTopModelAM.PrcPozPublicViewAM.SupplierSitePVO”
Please note Bulk and Incremental job definition should have the same number of columns . OIC integration will fail if there is any mismatch in the columns.
Attached document Vendor and Vendor Sites Extract using BICC
Field Details : Please check attached document.
Setups in BICC : Please check attached document.
Design of Extract : Please check attached document.
Export/Import/Installation Procedures : Please check attached document.