Closed as fixed if next.
When multiple delivery patterns have been specified for a nominee, the logic inside the method "GenerateFinancialComponents.getNomineesForComponents()" does not always correctly consider a null date when calculating the end date to apply to the financial components
No current workaround
WHEN MULTIPLE DELIVERY PATTERNS ARE SPECIFIED FOR A NOMINEE A FINANCIAL COMPONENT CAN BE GENERATED WITH NO END DATE
APAR was included in release 126.96.36.199 Please see release Notes: http://www-01.ibm.com/support/docview.wss?uid=swg27045969 PO00399, CS-10813, SPMP-6050 - Financial Component End date is not getting populated when multiple delivery patterns have been specified for a nominee This issue is no longer reproducible. In the latest version of Cúram, multiple product delivery patterns are supported and the end date for the Financial components are updated corrected for a product delivery case with multiple product delivery patterns.
Reported component name
CURAM SOCIAL PG
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels