BPA With Future Start Date Are Not Showing In SSP Catalog When The Sysdate Matches With Future Date
Last updated on NOVEMBER 01, 2016
Applies to:Oracle Fusion Self Service Procurement - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 1.0]
Oracle Fusion Purchasing - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 1.0]
Oracle Fusion Self Service Procurement Cloud Service - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 1.0]
Oracle Fusion Purchasing Cloud Service - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 1.0]
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Procurement Catalog
BPA with future start date are not showing in SSP catalog when the sysdate matches with future date
As per health care client business requirements, BPA will be created with future start date at the header level to ensure that all medical equipment/medicines are available in catalog for requisition creation by internal customers at any point of time. Being a health care sector, it is very much essential to ensure that the medical products should be ordered from SSP during emergency situation as well. By doing this, the expectation is that if the existing BPA expires on a particular day, the next BPA with future date will become valid when we reach the future date and there won't be question of items not being shown in shopping page. But the shopping page does not show the items in the latest BPA even when the system date matches with future date.
BPA with future start date should be showing in SSP catalog when the sysdate matches with future date
The issue can be reproduced at will with the following steps:
1. Create a BPA 1 for an item X with start date as 1-May-15 and end date as 10-May-16
2. Create another BPA 2 for the same item with start date as 11-May-16 and end date as 31-May-17 at the header level. This BPA should be created in advance, say 1-May-16
3. Now items in BPA 1 will be available in the shopping page till 10-May-16. But items in BPA 2 will not be shown in the shopping page on 11-May-16 though the BPA 2 is valid from 11-May-16
When BPA 2 is created with future start date, it does not insert a record in por_items_ctx_hdrs_tlp. When the future start date is reached, there is no mechanism to insert the record into por_items_ctx_hdrs_tlp. Hence it is not showing in SSP though the system date meets the future date of BPA.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms