Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


Account :

JIRA : OLE-2341
Intent

  • To remove Account Fringe Benefit, Fringe Benefit COA Code, Fringe benefit Acct Number, Higher Ed Func Code, CFDA Number ,Budget Record Level Code,External Encumbrance Sufficient Funds Check, Internal Encumbrance Sufficient Funds Check, Pre-Encumbrance SufficientFundsCheck,Building Campus, Building Code from the accounts UI.
  • To Remove the Contracts And Grants tab and Indirect Cost Recovery Tab from UI.
  • To Make Campus Code,Account Postal, City, State, Street,Account Type Code,Account Supervisor, Account Manager, Account income Guideline Text,Account Purpose Text as optional.
  • To add new fields University Account Number as required.
  • To add new tab for Stewardship Requirement and LegacyFundCode.


Participants
Account.java

  • Extends PersistableBusinessObject Base and implements Inactivateable
  • This contains the getter and setter for the newly added fields.

Account.xml

  • This is the Data Dictionary File for Account.java
  • This defines the property name and provide the appropriate values in the Attribute Definition Bean and helps us to do validation in the screen
  • Here we define the look up fields, inquiry fields and the results fields to be displayed in the screen

AccountSimpleMaintenanceDocument.xml

  • This is the maintenance document for Account document
  • In this we define our document type name and fields to be displayed while creating a new document.

AccountRule.Java

  • This is used for the purpose of validations for the fields in the Account.Java


ojb-coa.xml

  • This is used to map the account fields to the database.
  • We have to add the new column for storing the university number in the account table.

StewardshipRequirement.java

  • Extends Persistable Business Object and implements Inactivatable.
  • This contains the getter and setter for the fields.

StewardshipRequirement.xml

  • This is the Data Dictionary File for Account.java
  • This defines the property name and provide the appropriate values in the Attribute Definition Bean and helps us to do validation in the screen
  • Here we define the look up fields, inquiry fields and the results fields to be displayed in the screen

StewardshipRequirementMaintenanceDocument.xml

  • This is the maintenance Document for Stewardship Requirement Document.
  • In this we define our document type name and fields to be displayed while creating a new document.

LegacyFundCode.java

  • Extends Persistable Business Object and implements Inactivatable.
  • This contains the getter and setter for the fields.

LegacyFundCode.xml

  • This is the Data Dictionary File for Account.java
  • This defines the property name and provide the appropriate values in the Attribute Definition Bean and helps us to do validation in the screen
  • Here we define the look up fields, inquiry fields and the results fields to be displayed in the screen

LegacyFundCodeMaintenanceDocument.xml

  • This is the maintenance Document for Stewardship Requirement Document.
  • In this we define our document type name and fields to be displayed while creating a new document.

Ojb-select.xml

  • This is used to map the Stewardship Requirement fields to the database.
  • Here we have to add the class descriptor for the stewardship Requirement and LegacyFund Code.

Data Modelling

  • Adding the column OLE_UNIV_ACCT_NBR in the table CA_ACCOUNT_T for University Account Number based on the artifact 13.
  • Creating new table for stewardship Requirement (OLE_CA_ACCT_STWD_T)And for LegacyFundCode(OLE_CA_ACCT_LGCY_LMS_FND_T) based on the artifact 13.


Object Screen Enhancements:

JIRA : OLE-2345
Intent :
Remove element from Object UI:

  1. Historic Financial Object Code.
  2. Budget Aggregation Code.
  3. Mandatory transfer or elimination.
  4. Federal Funded Code.
  5. Next Year object Code.
  6. Object Sub Type Code.


Participants

  1. Need to remove (hide) the fields from UI as per requirement.

ObjectCodeMaintenanceDocument.xml:
Modify this file to hide Historic Financial Object Code, Budget Aggregation Code, Mandatory transfer or elimination, Federal Funded Code, Object Sub Type Code and Next Year object Code when creating new Object Code and editing the existing object code.
Following attributes need to be commented.

  1. financialObjectSubTypeCode
  2. financialBudgetAggregationCd
  3. finObjMandatoryTrnfrelimCd
  4. financialFederalFundedCode
  5. nextYearFinancialObjectCode
  6. historicalFinancialObjectCode


ObjectCode.xml:
Modify this file to hide Object Sub Type Code, hide Historic Financial Object Code and Budget Aggregation Code on search page.
Following attributes need to be commented.

  1. financialObjectSubTypeCode
  2. historicalFinancialObjectCode
  3. financialBudgetAggregationCd




ObjectCodeRule.java
ProcessObjectCodeRules ().
IsLegalBudgetAggregationCode (budgetAggregationCode): Comment this rule as Budget Aggregation Code is not mandatory.

Collaborations
NA
Configuration/Usage
NA
Data modeling
As per Artifact 13 Mapping Document Table Involved: CA_OBJECT_CODE_T
Need to make following columns as required="FALSE". Need to modify validation rules to make these fields as required="FALSE"

      1. FIN_OBJ_SUB_TYP_CD (Not mentioned in Redwood COA Handoff Document, but mentioned in Artifact 13 Mapping Document)
      2. FOBJ_BDGT_AGGR_CD
      3. FOBJ_MNXFR_ELIM_CD
      4. FIN_FED_FUNDED_CD
      5. HIST_FIN_OBJECT_CD (Not mentioned in Artifact 13 Mapping Document, but mentioned in mentioned in Redwood COA Handoff Document)
      6. NXT_YR_FIN_OBJ_CD (Not mentioned in Artifact 13 Mapping Document, but mentioned in Redwood COA Handoff Document).

Tests
In ObjectCodeServiceTest.java following test cases need to be modified.

      1. testBudgetAggregationCodeRetrieval()
      2. testMandatoryTransferEliminationCodeRetrieval()
      3. testFederalFundedCodeRetrieval()


Issues
NA

Organization Screen Enhancements:

JIRA : OLE-2344
Intent
Make optional on UI (rules, remove asterisk*):

  1. Organization manager
  2. Responsibility Center Code
  3. Organization Physical Campus Code
  4. Organization Default Account Number
  5. Organization address line 1
  6. Organization Postal Code
  7. Organization Country Code.


Remove Complete Tabs & Elements:

  1. Plant Accounts (new tab in KFS 5.0 per http://reg.kfs.kuali.org/kfs-reg);
  2. Edit HRMS tab


Participants

  1. Need to remove (hide) the fields from UI as per requirement.

OrganizationMaintenanceDocument.xml
To Remove Plant Account & Edit HRMS Tabs, comment the following bean references
OrganizationMaintenanceDocument-EditPlantAccounts
OrganizationMaintenanceDocument-EditHRMSUnit.
To make Organization manager, Responsibility Center Code, Organization Physical Campus Code, Organization Default Account Number, Organization address line 1, Organization Postal Code and Organization Country Code as optional , remove required="true" from the following attributes.

  1. organizationManagerUniversalId
  2. organizationManagerUniversal.principalName
  3. organizationPhysicalCampusCode
  4. organizationLine1Address
  5. organizationCountryCode
  6. organizationZipCode

OrgRule.java:
Comment the rules which are not required after the changes

  1. isPlantAuthorized()
  2. checkDefaultAccountNumber()
  3. checkHrmsOrgRules()
  4. checkPlantAttributes()



Collaborations
NA
Configuration/Usage
NA
Data modeling
Artifact 13 Mapping Document does not have the mappings for Organization.
Tables involved as per the requirement given in Redwood Handoff Document and JIRA No. OLE-2344
CA_ORG_T and CA_ORG_EXTNS_T

  1. ORG_MGR_UNVL_ID (make optional)
  2. RC_CD (make optional)
  3. ORG_PHYS_CMP_CD (make optional)
  4. ORG_DFLT_ACCT_NBR (make optional)
  5. ORG_LN1_ADDR (make optional)
  6. ORG_ZIP_CD (make optional)
  7. ORG_CNTRY_CD (make optional)



Tests
Test Cases in the following test case files should pass, after the changes done as per requirement.

  1. OrganizationService2Test.java
  2. OrgRuleTest.java


Issues :
Plant Accounts (new tab in KFS 5.0 per http://reg.kfs.kuali.org/kfs-reg) mentioned in the requirement is not available in the Screen.

SubAccount:

JIRA : OLE-2343
Intend:
To remove some of the elements and tabs in the sub-account Create New, Edit, Search result and Inquiry screens. The following are the list

  1. Remove element "Sub Account Type Code" (Note: Default the value as 'EX' to the same field) in Create New, Edit, Search results and Inquiry screens.
  2. Remove complete Edit CG Cost Sharing, Edit CG ICR, Indirect Cost Recovery Accounts for Details Tabs and its Elements of Edit CG Cost Sharing, Edit CG ICR and Indirect Cost Recovery Accounts in Create New and Edit screens.

Participants:

  1. SubAccountMaintenanceDocument.xml
  2. SubAccount.xml
  3. Configuration.properties
  4. SubAccount.java


SubAccountMaintenanceDocument.xml:

    • In order to remove the element "Sub Account Type Code" from create new and edit screens of Sub-Accounting screen comment out the bean id
      • a21SubAccount.subAccountTypeCode


    • In order to remove the Edit CG Cost Sharing, Edit CG ICR, Indirect Cost Recovery Accounts for Details tabs from create new and edit screens of Sub-Accounting comment out the following bean reference list in the bean id SubAccountMaintenanceDocument-parentBean
      • SubAccountMaintenanceDocument-EditCGCostSharing
      • SubAccountMaintenanceDocument-EditCGICR
      • SubAccountMaintenanceDocument-IndirectCostRecoveryAccounts


SubAccount.xml:

    • In order to remove the Sub-Account Type Code from the search result comment out the "a21SubAccount.subAccountTypeCode" under property "resultFields".
    • In order to remove the Sub-Account Type Code from the inquiry comment out the "a21SubAccount.subAccountTypeCode" under property "inquiryFields".


Configuration.properties:

    • Create a property field 'SUBACCOUNT_TYPE_CODE' with value 'EX'.


SubAccount.java:

    • Get the sub-account type code value from the configuration.properties and set it to the a21SubAccount.setSubAccountTypeCode() as default.


Collaborations:
Configuration/Usage:
Configuration.properties:

    • Create a property field 'SUBACCOUNT_TYPE_CODE' with value 'EX'.


Data modeling:
CA_SUB_ACCT_T, CA_A21_SUB_ACCT_T
Tests:
NA
Issues:
NA

Stewardship Requirement:

JIRA : OLE-2342
Intent
To create new maintenance document and add to Maintenance Menu with following document format

  • Stewardship Type
  • Note/attachments and normal maintenance doc tabs


Participants
OleStewardshipRequirement.java

  • Extends PersistableBusinessObjectBase and implements Inactivateable
  • This class contains getter and setter method for the variables.

OleStewardshipRequirement.xml

  • This is a Data Dictionary File for OleStewardshipRequirement.java
  • Define property name and appropriate value in the Attribute Definition Bean. This helps us to do validation and property for UI screen.
  • Define lookup fields, inquiry fields and result fields for UI screen.

OleStewardshipRequirementMaintenanceDocument.xml

  • In this xml we configure document type name, required fields and defining the properties to display in create new UI.

oleChartOfAccounts.tag

  • Define link name for UI screen.
  • URL for this maintenance document should be configured in this tag .

ojb-select.xml

  • Need to add class-descriptor for OleStewardshipRequirement.java
  • Define table name, column name and attribute name for strong and restoring values from database table(OLE_CA_ACCT_STWD_TYP_T).




ChartSimpleMaintenanceDocuments.xml

  • We have to add Stewardship document type in this xml.
  • We have to ingest this xml in to XML ingester for new document creation.


Script.sql

  • As per Artifact 13, Need to create table (OLE_CA_ACCT_STWD_TYP_T) with following columns.

OLE_STWD_TYP_ID – Primary Key
OLE_STWD_TYP
ROW_ACT_IND






Collaborations
Search


show search



perform search get search results
show results

Tests
OleStewardshipRequirementTest

  • testSave

Tests by creating a record in OleStewardshipRequirement and saves in database.

  • testSearch

Tests by searching existing record in database.

T-Restricted Account Numbers:

JIRA : OLE-2356
Intent
"Account Restricted Status Code" of "R-Restricted" or "T-Temporarily Restricted" prohibit use of Account in PURAP documents, REQS, PO, POA, PREQ and other PO docs, with error messages. "R- Restricted" does not have an expiration date (no date expiration, account blocked from use).For "T- Temporarily Restricted", we need to add system functions and notifications as an Action List item to the Fiscal Officer on the account at the time of "Account Restricted Status Date" to notify the Fiscal Officer to extend the "Account Restricted Status Date" or "Approve" removing the Restricted status and date, and return the status to "U --Unrestricted". All changes above should be captured in the Route Log and Notes tabs as audit trail for these changes.




References:

https://jira.kuali.org/browse/OLE-2356

Participants
AccountRule

  • Extends IndirectCostRecoveryAccountsRule.

CheckAccountRestrictedStatusDateIsGreaterThanCurrentDate ()

  • returns Boolean.
  • Validates the AccountRestrictedStatusDate which should be greater than the currentDate if AccountRestrictedStatusCode is 'T' which is Temporary-Restricted, if not it just displays the error message.



HasTemporaryRestrictedStatusCodeButRestrictedStatusDateisGreaterThanCurrentDate ()

  • returns Boolean.
  • This method called by testCase AccountRuleTest.
  • Validates the passed AccountRestrictedStatusDate is greater than the currentDate or not when AccountRestrictedStatusCode is 'T' which is Temporary-Restricted.


AccountTemporaryRestrictedStep

  • Extends AbstractStep.

Execute()

  • Returns Boolean.
  • This method gets all the Temporary Restricted Accounts details and checks the status date with current date, if status date is same as the current date it will notify Fiscal Officer to approve the account by making status code as Un-Restricted or extend the status date.


Spring-select

  • Define a bean id for AccountTemporaryRestrictedNotify.

Example:
<bean id="accountTemporaryRestrictedNotify" class="org.kuali.ole.select.batch.AccountTemporaryRestrictedNotify" parent="step">
</bean>

  • Assign job to schedule descriptor for the step.



Example:
<property name="jobNames">
<list>
<value>accountTemporaryRestrictedNotifyJob</value>
</list>
</property>
<bean id="accountTemporaryRestrictedNotifyJob"
parent="scheduledJobDescriptor">
<property name="steps">
<list>
<ref bean="accountTemporaryRestrictedNotify"/>
</list>
</property>
</bean>

Tests
AccountRuleTest

  • Extends ChartRuleTestBase.

TestHasTemporaryRestrictedStatusCodeButRestrictedStatusDateisGreaterThanCurrentDate ()

  • Tests whether AccountRestrictedStatusDate is greater than the CurrentDate.



  • No labels

Operated as a Community Resource by the Open Library Foundation