The advantages of the use of Application Package PeopleCode

Recently we had to make quite some customizations in Vanilla PeopleCode in the ePerformance module of HCM. In this case we decided to use an Application Package. We decided to put all our code for the modifications in a class. This worked out quite elegant.
We created a component object in the PostBuild PeopleCode of the Component.

Example:

    import KP_EP_FUNCTIONS:BonusSheetCalc;

    &oBonusSheetCalc = create KP_EP_FUNCTIONS:BonusSheetCalc(&sBonusStat);

In the private section we could put all the variables, which we would put normally as component variables. Example:

   private

   instance boolean &bBnsMtxChg;
   instance boolean &bEditStat;
   instance Rowset &rsBnsShtTgtDpt;

Then at every piece of PeopleCode where we need to use one of the methods, we only needed to put the declaration of the component object and all the defined methods and variables are then available:

   Component object &oBonusSheetCalc;
   &oBonusSheetCalc.SavePreChange(EP_APPR.PERIOD_BEGIN_DT, &PushButton);

There is a disadvantage though. If you are working in a project with several people, then only person can work on the Application Package at a time.

 Viewed 5957 times by 1733 visitors

Posted by: Rob van Steensel (3 post(s)).