IBM Support

IV88631: INCORRECTLY ASSOCIATING FUNDING ALLOCATIONS TO MULTIPLE CAPITAL PROJECTS BECAUSE THE NAME IS THE SAME

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Detailed steps to reproduce the Issue
    
    1. Create a Funding Source
    2. Create a Program
    3. Allocate funds from the funding source in step 1 to the
    program in step 2, (Financials tab of Program record)
    4. Create two capital projects with identical Names, the rest
    of the project information does not seem to matter, as long as
    the names are identical, which in Florida PROD you can do
    without issue or error.
    5. On the Program again, add those two projects to the program.
    6. Back on the Project, on the Budget tab, Funding Allocations
    section, add Funding for the first project from the Fund that
    you created on the program.
    7. Once the funding has been allocated to the project, save the
    project.
    8. Open the second project you created with the same name. On
    the Budget tab, Funding Allocations section, add additional
    funding to this project, from the same Funding Source.
    9. Once the funding has been allocated to the project, save the
    project.
    10. Open the 1st project back up, and you will see the funding
    you just added to Project 2 is also on Project 1.
    11. It does not create duplicate allocation records, but rather
    associated the allocation to both projects, causing it to
    appear in both Project Fund Allocation sections.
    

Local fix

  • N/A
    

Problem summary

  • Incorrectly associating funding allocations to multiple Capital
    Projects
    Allocating funds to Capital Projects will no longer incorrectly
    duplicate the allocation to other Capital Projects of the same
    name.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IV88631

  • Reported component name

    TRI CAP PROJECT

  • Reported component ID

    5725F25CM

  • Reported release

    A41

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-24

  • Closed date

    2016-09-29

  • Last modified date

    2016-09-29

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • None
    999
    

Fix information

Applicable component levels

  • RA51 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A41","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
30 March 2022