Failed Disable Messages - Harvard University · Web view4All balance forward object codes are central-only and therefore all journals that reference them must be loaded to Oracle

Handling CSMA Failed Disable Messages (rev 7/29/2015)

1

Failed Disable Message

What it means Actions to take

Active sponsored award associated with this value

The value you are trying to disable appears with a sponsored fund (range 100000-299999) and/or a sponsored activity-subactivity (range 200000-499999) in one or more active 33-digit code combinations (CCIDs).

There are three possible ways to correct this error:

1. Cancel the failed disable request until all transactions related to the sponsored values have been posted and the associated HURIS/GMAS accounts have been closed. Confirm that the sponsored values are at last disabled, and then initiate a new request to disable the non-sponsored value.

2. If the close of the associated GMAS account is imminent, wait for the sponsored strings to be disabled, then resubmit original disable request.

3. Obtain written confirmation that the sponsored CCIDs associated with the failed disable request will not be used again and request that Client Services manually disable them. Resubmit the original failed disable request after confirming that the offending CCIDs are disabled.

1. Run the Disable Impact Report Detail report for the value you are trying to disable, using the current open period as your date parameter. (For example, if your valuefailed the October 7th disable process and you’re running the report on the 8th, October is the current open period.)

2. In the Balances – Sponsored section, find the CCID(s) that caused the disable to fail.

3. If the only sponsored value that has been used with your value is a college work- study fund in the range 100005-100006, you should confirm that all CCIDs have a net actual balance of $0. Correct any non-$0 balances and send an e-mail to Client Services at [email protected], requesting that they disable the CCIDs. Client Services will manually disable the CCIDs and will update the Comments on your CSMA disable request with the text of your e-mail message, the CCIDs they disabled and the disable date. They will then close your ticket confirming that the CCIDs have been disabled. (Skip to Step 9 below)

4. For any other sponsored value, forward the CCIDs and their associated net actual balances as of the latest open period to the department that has been using them and ask them to work with their Asst. Director in the Office of Sponsored Research (OSP) (or, if you are in HMS or SPH, their local Pre-Award office) to determine if the CCIDs must remain open for future transactions.

5. If OSP (or your local Pre-Award office) plans to transact to the strings in the future, you should cancel your disable request until they are no longer required.

6. If OSP (or your local Pre-Award office) is in the process of closing the award with which your value has been used, you should wait until they do so1. By disabling the sponsored values associated with the award, the CCIDs that have been used withyour non-sponsored values will be themselves disabled. Once they are, your resubmitted value will then pass the validation.

7. If OSP (or your local Pre-Award office) does not plan to close the award in the near future, the department should obtain confirmation from them that the strings containing your non-sponsored value will not receive future transactions. This confirmation should be in the form of an e-mail, which they should forward to you as the CoA Authorized Requestor.

8. Forward a copy of the confirmation e-mail to Client Services at [email protected] and request that they disable the CCIDs. Client Services will manually disable the CCIDs and will update the Comments on your CSMA disable

1 OSP feeds sponsored values for disable to CSMA on the 2nd calendar day of each month except June. As long as the account associated with your disable request is closed out in GMAS prior to this date, the requests to disable the sponsored values will be loaded to CSMA in time for the month-end disable process. You can confirm that the disable was successful by re-running your Disable Impact Detail report. If the sponsored strings are now disabled, you may resubmit your request.

mailto:[email protected]



2



request with the text of your e-mail message, the CCIDs they disabled and the disable date. They will then close your ticket confirming that the CCIDs have been disabled.

9. Once you receive the e-mail from Client Services that your ticket is resolved, you can resubmit your disable request. If no more CCIDs containing sponsored values are created with your value between the time you resubmit the request and the month-end close, your value should pass the validation and be disabled.

Fund balances do not meet specific net requirements for fund type

The net actual balances in both dollars and units for the FUND you are trying to disable do not meet the requirements established for the fund type.

All fund disable requests must be reviewed and approved by Financial Accounting & Reporting (FAR) before they are queued for disable by CSMA. Before approving a disable, FAR reviews the fund balances and posts any closing transactions necessary to bring the closing fund balance in line with their disable requirements for the fund.

If the fund has subsequently failed the disable process, one of two things has happened:

1. the closing journal submitted by FAR contained an error, or

2. a new transaction in objects 4000-8999 was posted by the tub, either through a journal or a feed.

In either of the above cases, CSMA will send the response (ACT) notification to FAR for resolution. FAR and the tub will need to work together to correct the imbalance.

Once FAR has verified that the fund once again meets the disable criteria, it will resubmit the request. On resubmit, CSMA will generate an FYI notification to the tub notifying them that this action has taken place.

1. Run the Disable Impact Detail Report in HUDINI for the value you are trying to disable, using the current open period as your date parameter. (For example, if your value failed the October 7th disable process and you’re running the report on the 8th,October is the current open period.)

2. In the Balances - Actuals section, review the fund balances against the object code requirements listed under Fund in the CSMA Validations section of the Disable Guidelines document (available on the CSMA website).

3. If the imbalance in the fund is the result of a newly posted transaction to objects 4000-8999, the tub will need to transfer the transaction to another fund in order to correct the error. Once the error has been corrected, the tub should confirm this by rerunning the Disable Impact Detail Report. If the Disable Impact Report indicates that the fund is ready for disable, the tub should contact FAR via e-mail at karen_o'[email protected] and let them know. The e-mail should contain the value, description, and the CSMA request ID for the failed disable request you have corrected. Note: a forwarded copy of the e-mail version of CSMA’s FYI Failed Disable notification will serve this purpose.

4. If the imbalance in the fund is the result of an error in the original closing journal, FAR will identify the error and the necessary adjustments required, and will post a journal to correct it.

5. FAR will resubmit the fund disable request, generating the FYI notification to the tub.

6. If no new transactions are created with the value between the time FAR resubmits the request and the month-end close, the value should pass the validation and be disabled.


3



One or more CCIDs will balance forward at this level

At year-end, the balance forward process will create a non-$0 transaction to an active CCID that contains the child ORG, FUND, ACTIVITY, SUBACTIVITY, orROOT value you are trying to disable. This transaction will not net to $0 with any existing prior year balances.

While the balance forward process is programmed to temporarily re-enable both values and CCIDs as necessary to post its transactions (and disable them afterwards), in cases of non-$0 balances, this action results in “stranded” balances in disabled balance sheet CCIDs, which continue to carry forward and appear on reports, giving end-users the mistaken impression that funds are available for spending.

1. Run the Disable Impact Detail Report in HUDINI for the value you are trying to disable, using the current open period as your date parameter. (For example, if your value failed the October 7th disable process and you’re running the report on the 8th,October is the current open period.).

2. In the Balance Forward Implications section, review the CCIDs that will be created by the balance forward process at year-end.

3. There are a number of different ways to address this error. Examples of each action listed below are detailed at the end of this document in Appendix A – Handling Balance Forward Disabling Issues:

a. Change the level to which the fund(s) in the projected balance forward strings will post and - if they exist - transfer any prior year balances containing the value to the new level.

b. Transfer prior year balances so that they will net to $0 with the incoming journal line.

c. Transfer current year balances so that the balance-forward process will not produce a journal line containing the value you wish to disable, or,

d. Transfer current year balances so that the balance-forward process produces a journal line that will net to $0 with the amounts showing in an existing balance forward string.

4. Take the appropriate action.

5. Run the Disable Impact Detail Report for the value you are trying to disable.

6. In the Balance Forward Implications section, review the CCIDs that will be created by the balance forward process at year-end. If no CCIDs appear there, your value will pass this validation and be disabled should you resubmit it.

7. From the CSMA Worklist open the failed disable notification for your value and click the Resubmit button to re-queue it for the next month-end disable process.

One or more CCIDs to be created by BF do not exist

At year-end, the balance forward process will create a non-$0 transaction to a new CCID that contains the child ORG, FUND, ACTIVITY, SUBACTIVITY, orROOT value you are trying to disable.

While the balance forward process is programmed to temporarily re-enable both values and CCIDs as necessary to post its transactions (and disable them afterwards), in cases of non-$0 balances, this action

1. Run the Disable Impact Detail Report for the value you are trying to disable, using the current open period as your date parameter. (For example, if yourvalue failed the October 7th disable process and you’re running the report on the 8th, October is the current open period.).

2. In the Balance Forward Implications section, review the CCIDs that will be created by the balance forward process at year-end.

3. There are a number of different ways to address this error. Examples of each action listed below are detailed at the end of this document in Appendix A – Handling


4



results in “stranded” balances in disabled balance sheet CCIDs, which continue to carry forward and appear on reports, giving end-users the mistaken impression that funds are available for spending.

Balance Forward Disabling Issues:

a. Change the level to which the fund(s) in the projected balance forward strings will post and - if they exist - transfer any prior year balances containing the value to the new level.

b. Transfer prior year balances so that they will net to $0 with the incoming journal line.

c. Transfer current year balances so that the balance-forward process will not produce a journal line containing the value you wish to disable, or,

d. Transfer current year balances so that the balance-forward process produces a journal line that will net to $0 with the amounts showing in an existing balance forward string.

4. Take the appropriate action.

5. Run the Disable Impact Detail Report for the value you are trying to disable.

6. In the Balance Forward Implications section, review the CCIDs that will be created by the balance forward process at year-end. If no CCIDs appear there, your value will pass this validation and be disabled should you resubmit it.

7. From the CSMA Worklist open the failed disable notification for your value and click the Resubmit button to re-queue it for the next month-end disable process.

Non-sponsored fund value appears in CCID with sponsored activity

The non-sponsored FUND value you are trying to disable appears with a sponsored activity-subactivity (range 200000-499999) in one or more active 33-digit code combinations (CCIDs).

There are three possible ways to correct this error:

4. Cancel the failed disable request until all transactions related to the sponsored values have been posted and the associated GMAS accounts have been closed. Confirm that the sponsored values are at last disabled, and then initiate a new request to disable the non- sponsored value.

1. Run the Disable Impact Detail report for the value you are trying to disable, using the current open period as your date parameter. (For example, if yourvalue failed the October 7th disable process and you’re running the report on the 8th, October is the current open period.)..

2. In the Balances – Sponsored section, find the CCID(s) that caused the disable to fail.

3. Forward the CCIDs and their associated net actual balances as of the latest open period to the department that has been using them and ask them to work with their Asst. Director in the Office of Sponsored Research (OSP) (or, if you are in HMS or SPH, their local Pre-Award office) to determine if the CCIDs must remain open for future transactions.

4. If OSP (or your local Pre-Award office) plans to transact to the strings in the future,


5



5. If the close of the associated GMAS account is imminent, wait for the sponsored strings to be disabled, then resubmit original disable request.

Obtain written confirmation that the sponsored CCIDs associated with the failed disable request will not be used again and request that Client Services manually disable them. Resubmit the original failed disable request after confirming that the offending CCIDs are disabled.

you should cancel your disable request until they no longer require them.

5. If OSP (or your local Pre-Award office) is in the process of closing the award with which your value has been used, you should wait until they do so2. By disabling thesponsored values associated with the award, the CCIDs that have been used with your non-sponsored values will be themselves disabled. Once they are, your resubmitted value will then pass the validation.

6. If OSP (or your local Pre-Award office) does not plan to close the award in the near future, the department should obtain confirmation from them that the strings containing your non-sponsored value will not receive future transactions. This confirmation should be in the form of an e-mail, which they should forward to you as the CoA Authorized Requestor.

7. Forward a copy of the confirmation e-mail from Step 6 to Client Services at [email protected] and request that they disable the CCIDs. Client Services will manually disable the CCIDs and will update the Comments on your CSMA disable request with the text of your e-mail message, the CCIDs they disabled and the disable date. They will then confirming that the CCIDs have been disabled by closing the Service Now ticket.

8. Once you receive the e-mail from Client Services, you can resubmit your disable request. If no more CCIDs containing sponsored values are created with your value between the time you resubmit the request and the month-end close, your value should pass the validation and be disabled.

Non-zero balances in plant accounts for building root value

As of the current open period, for all CCIDs containing the submitted root value, the sum of the net balance of objects 1200-1240 and the net balance of 1630-1631 do not equal $0 actual, 0.0000 STAT units.

All building root disable requests must be reviewed and approved by Financial Accounting & Reporting (FAR) before they are queued for disable by CSMA. Before approving a disable, FAR reviews the building root balances and posts any closing transactions necessary to bring the closing balance in line with their disable requirements for the

1. Run the Disable Impact Detail Report for the building root value you are trying to disable, using the current open period as your date parameter. (Forexample, if your value failed the October 7th disable process and you’re running the report on the 8th, October is the current open period.)..

2. In the Balances - Actuals section, review the building root’s balances in objects 1200- 1240 and 1630-1631 where the balances do not equal $0.00.

3. If the imbalance is the result of a newly posted transaction, the tub will need to transfer the transaction to another 33-digit string in order to correct the error. Once the error has been corrected, the tub should confirm this by rerunning the Disable Impact Detail Report. If the Disable Impact Report indicates that the activity is ready for disable, the tub should contact FAR and let them know.

2 OSP feeds sponsored values for disable to CSMA on the 2nd calendar day of each month except June. As long as the account associated with your disable request is closed out in GMAS prior to this date, the requests to disable the sponsored values will be loaded to CSMA in time for the month-end disable process. You can confirm that the disable was successful by re-running your Disable Impact Detail report. If the sponsored strings are now disabled, you may resubmit your request.


6



If the root has subsequently failed the disable process, one of two things has happened:

1. the closing journal submitted by FAR contained an error, or

2. a new transaction in objects 1200-1240 or 1630- 1631 was posted by the tub, either through a journal or a feed.

In either of the above cases, CSMA will send the response (ACT) notification to FAR for resolution. FAR and the tub will need to work together to correct the imbalance.

Once FAR has verified that the root once again meets the disable criteria, it will resubmit the request. On resubmit, CSMA will generate an FYI notification to the tub notifying them that this action has taken place.

4. If the imbalance in the building root is the result of an error in the original closing journal, FAR will identify the error and the necessary adjustments required, and will post a journal to correct it.

5. FAR will resubmit the building root disable request.

6. If no new transactions are created with the value between the time FAR resubmits the request and the month-end close, the value should pass the validation and be disabled.

Value in active CVR The ORG value that you are attempting to disable appears in the name of an active org-fund, org- activity, or org-root cross-validation rule (CVR) in Oracle.

Before you can disable the ORG, you must disable the rule and make sure that the range of orgs (if the CVR covers more orgs than the one you are disabling) covered by it are either disabled themselves, or will be covered by another active org- fund or org-activity CVR (or org-root, if required by your local business process).

1. Run the Cross Validation Rules Listing Report, entering ‘%[Org value you are disabling]%’ as the input parameter for the Rule Name and “Enabled” as the input parameter for Rule Status. This report will identify the name of every active CVR that contains the org you are trying to disable.

2. Review the low and high org values covered by the org-fund and org-activity CVR(s) produced by the report.

3. If both the low and high org values are the same as the value you are disabling:

forward a request to disable the CVR to Client Services at [email protected]. The request should reference the CVR rule(s) that you wish to disable in the subject line and indicate the reason you wish the rule disabled in the body (e.g., Please disable above CVR(s) so that CSMA request 255555 to disable org 12345 will pass validation.)

Client Services will process your request on the morning of the month-end close, just prior to the CSMA Disable process, in order to prevent inappropriate transactions from being created in between the time the CVR is disabled and the value is disabled.

4. If the high value is different from the value you are disabling:

Run the Value Finder report to see if there are other active org values in the range covered by the CVR besides the org you plan to disable.



7



If there are other active orgs covered by the CVR (assuming you do not also plan to disable those) you will either need to:

a. create a new org-fund and/or org-activity CVR to cover the other orgs, or

b. extend the range of an existing org-fund and/or org-activity CVR to cover them.

To create a new CVR, you should submit a completed CVR template with the ranges of funds and/or activities to be allowed for the org range to Client Services at [email protected].

To modify an existing CVR, submit a request to [email protected] with the name of the CVR you are modifying or disabling in the subject line.

Once all of the orgs covered by the CVR(s) that reference(s) the org value you plan to disable are safely covered by other rules, you may submit a request to disable the CVR(s) to Client Services at [email protected]. The request should reference the CVR rule(s) that you wish to disable in the subject line and indicate the reason you wish the rule disabled in the body (e.g., Please disable above CVR(s) so that CSMA request 255555 to disable org 12345 will pass validation.)

Client Services will process your request on the morning of the month-end close, just prior to the CSMA Disable process, in order to prevent inappropriate transactions from being created in between the time the CVR is disabled and the value is disabled.


mailto:[email protected]%20



8

Appendix A – Handling Balance Forward Disabling Issues

Scenario 1: Change the level to which the fund will balance forward to avoid a stranded transaction on a disabled CCID (no prior year balance).

1. Failed Disable Request: Faculty Root 123452. Error Message: One or more CCIDs to be created by BF do not exist.

3. Disable Impact Detail Report shows (as of the latest open

period): BALANCESActuals

Net Actual Balance(s): 0.00

BALANCE FORWARD IMPLICATIONSBalance Forward Journal Lines Invalidated by Disabled Value:

Tub Org Obj Fund Act SubAct Root CCID Status STAT Balance USD Balance100 00500 3730 345678 678910 0000 12345 New 275.00

4. Balance Forward Attributes for Funds Used with Disabled Value: Fund 000001 – No Balance Forward attribute populated. Default balance forward level is to Basic Segments (Tub, TLO, and object). Fund 345678 – Balance forward attribute = BOASR – Basic Segments + Org, Activity, Subactivity, + Root

5. Because the faculty member is no longer with the University, the tub doesn’t wish to record a balance for this fund at the level of this root; they would rather have the net balance post to the org and activity. They submit a MODIFY request via CSMA (prior to the next FY close) to change the balance forward attribute from BOASR to BOA. There are no prior year balances to transfer.

6. Once the MODIFY request is uploaded to Oracle and the balance forward attribute is set to BOA, the Disable Impact Report Detail will return no data in the Balance Forward Implications section, because the balance forward journal line for the above transactions will now be 100.00500.3730.345678.678910.0000.00000 and will not include the root value 12345.

7. Unless transactions that will cause additional validation errors post in the meantime, the root value should now pass CSMA Disable validations and, if resubmitted, will be disabled at month-end.

Tub Org Obj Fund Act SubAct Root Enab? STAT Balance USD Balance100 00500 6450 000001 678910 0000 12345 Y 25.00100 00500 4530 345678 678910 0000 12345 Y (300.00)100 00500 6010 345678 678910 0000 12345 Y 400.00100 00500 6250 345678 678910 0000 12345 Y 75.00100 00500 6450 345678 678910 0000 12345 Y 100.00


9

Scenario 2: Change the level to which the fund will balance forward to avoid a stranded transaction on a disabled CCID (prior year balance).

1. Failed Disable Request: Faculty Root 123452. Error Message: One or more CCIDs will balance forward at this level.

3. Disable Impact Detail Report shows (as of the latest open period):

BALANCESActuals



Tub Org Obj Fund Act SubAct Root CCID Status STAT Balance USD Balance100 00500 3730 345678 678909 0000 12345 Enab 100.00100 00500 3730 345678 678910 0000 12345 New 200.00

4. Balance Forward Attributes for Funds Used with Disabled Value: Fund 345678 – Balance forward attribute = BOASR - Basic Segments + Org, Activity, Subactivity, + Root

5. Because the faculty member is no longer with the University, the tub doesn’t wish to record a balance for this fund at the level of this root; they would rather have the net balance post to the org and activity. They submit a MODIFY request via CSMA (prior to the next FY close) to change the balance forward attribute from BOASR to BOA.

6. At year-end, the balance forward will post the balances for the above to the following strings:

Tub Org Obj Fund Act SubAct Root USD Balance100 00500 3730 345678 678909 0000 00000 100.00100 00500 3730 345678 678910 0000 00000 200.00

Tub Org Obj Fund Act SubAct Root Enab? STAT Balance USD Balance100 00500 3730 345678 678909 0000 12345 Y (300.00)100 00500 6450 345678 678909 0000 12345 Y 100.00100 00500 4530 345678 678910 0000 12345 Y (200.00)100 00500 6010 345678 678910 0000 12345 Y 300.00100 00500 6250 345678 678910 0000 12345 Y 60.00100 00500 6450 345678 678910 0000 12345 Y 40.00


10

Scenario 2: Change the level to which the fund will balance forward to avoid a stranded transaction on a disabled CCID (with prior year balance). (continued)

7. While the change to the Balance Forward attribute will change the level to which the current year fund 345678 balances will post, there still the matter of the prior year balance in string 100.00500.3730.345678.678909.0000.12345. Before the request to disable root 12345 is resubmitted that balance must be transferred, or it will be stranded in a disabled CCID once the request is processed by CSMA.

8. In order to transfer the balance to the correct level, the tub should submit an ADI journal to Financial Accounting and Reporting (FAR) at karen_o’[email protected] with the following entries:3

Tub Org Obj Fund Act SubAct Root DR CR100 00500 3730 345678 678909 0000 12345 300.00100 00500 3730 345678 678910 0000 00000 300.00

9. Once CSMA has uploaded the MODIFY request to change the balance forward attribute and the prior year balance forward correction journal has posted, the Balances – Actual section of the Disable Impact Detail Report will show a $0.00 balance for the string 100.00500.3730.345678.678909.0000.12345 and the Balance Forward Implications section will not show any journal lines.

10. Unless transactions that will cause additional validation errors post in the meantime, the root value should now pass CSMA Disable validations and, if resubmitted, will be disabled at month-end.

3All balance forward object codes are central-only and therefore all journals that reference them must be loaded to Oracle by Financial Accounting and Reporting.


11

Scenario 3: Transfer prior year balances so that they will net to $0 with the incoming journal line.

1. Failed Disable Request: Org 123452. Error Message: One or more CCIDs will balance forward at this level.


BALANCESActuals



Tub Org Obj Fund Act SubAct Root CCID Status STAT Balance USD Balance370 12345 3730 345678 000000 0000 00000 Enab (100.00)

4. Balance Forward Attributes for Funds Used with Disabled Value: Fund 345678: No Balance forward attribute. Will balance forward to RG fund type default = BO – Basic Segments + Org

5. The problem here is the existing prior year balance forward credit amount of $200.00 in 370.12345.3730.345678.678910.0000.00000. The current year balance in objects 4530 and 9304 will post to the other existing prior year balance forward in 370.12345.3730.345678.000000.0000.00000, leaving balances in the two CCIDs as follows:

Tub Org Obj Fund Act SubAct Root STAT Balance USD Balance370 12345 3730 345678 000000 0000 00000 200.00370 12345 3730 345678 678910 0000 00000 (200.00)

Tub Org Obj Fund Act SubAct Root Enab? STAT Balance USD Balance370 12345 3730 345678 000000 0000 00000 Y 300.00370 12345 9304 345678 000000 0000 00000 Y (300.00)370 12345 4530 345678 000000 0000 00000 Y (50.00)370 12345 9304 345678 000000 0000 00000 Y 50.00370 12345 3730 345678 678910 0000 00000 Y (200.00)370 12345 9304 345678 678910 0000 00000 Y 200.00


12

6. In order to transfer the balance to the correct level, the tub should submit an ADI journal to Karen O’Rourke in Financial Accounting and Reporting at karen_o’[email protected] with the following entries:4


7. Once the journal has posted the Disable Impact Detail Report - Balance Forward Implications for this org value will not return a journal line because the journal line created by the balance forward process at year-end (370.12345.3730.345678.000000.0000.00000 in the amount of -$100.00) will net out with the existing prior year balance of$100.00 in that CCID.

8. Unless transactions that will cause additional validation errors post in the meantime, the org value should now pass CSMA Disable validations and, if resubmitted, should be disabled at month-end.

4All balance forward object codes are central-only and therefore all journals that reference them must be loaded to Oracle by Financial Accounting and Reporting.

mailto:[email protected]%20


13

Scenario 4: Transfer current year balances so that the balance-forward process will not produce a journal line containing the value you wish to disable.

1. Failed Disable Request: Activity 678910

2. Error Message: One or more CCIDs to be created by BF do not exist.


BALANCESActuals




4. Balance Forward Attributes for Funds Used with Disabled Value: Fund 000002: Balance forward attribute = BOA – Basic Segments + Org + Activity

5. The problem here is that the tub has transacted with the activity they want to disable and a fund (000002) that will balance forward to the level of that activity in the current FY. At year-end, the current year balances in objects 7120 and 8160 will post to a new balance forward string as indicated by the Disable Impact Report.

6. The tub decides to transfer the current FY spending to another activity and posts the following adjusting journal:


7. Once the journal has posted the Disable Impact Detail Report - Balance Forward Implications for this activity value will not return a journal line because the net balance in the income and expense objects for tub 370, org 34567, fund 000002 and activity 678910 will equal $0 and will therefore not generate a balance forward journal line at year-end.


Tub Org Obj Fund Act SubAct Root Enab? STAT Balance USD Balance370 34567 7120 000002 678910 0000 00000 Y 100.00370 34567 8160 000002 678910 0000 00000 Y 200.00


14

Scenario 5: Transfer current year balances so that the balance-forward process produces a journal line that will net to $0 with the amounts showing in an existing balance forward string.

1. Failed Disable Request: Activity 678910

2. Error Message: One or more CCIDs to be created by BF do not exist.


BALANCESActuals




4. Balance Forward Attributes for Funds Used with Disabled Value: Fund 000002: Balance forward attribute = BOA – Basic Segments + Org + Activity

5. The problem here is the existing prior year balance forward credit amount of $300.00 in 255.23450.3710.678910.0000.00000. During the current FY, the tub has been transacting in org 23456 instead of 23450 as they did in the previous FY. The current year balance in objects 8160 and 9302 will post to a new balance forward string in org 23456, leaving “stranded” balances in the two CCIDs as follows:

Tub Org Obj Fund Act SubAct Root STAT Balance USD Balance255 23450 3710 000002 678910 0000 00000 (300.00)255 23456 3710 000002 678910 0000 00000 300.00

6. The tub decides to consolidate the current FY spending in the previous FY’s org 23450 and posts the following adjusting journal:


Tub Org Obj Fund Act SubAct Root Enab? STAT Balance USD Balance255 23450 3710 000002 678910 0000 00000 Y (300.00)255 23456 8160 000002 678910 0000 00000 Y 100.00255 23456 9302 000002 678910 0000 00000 Y 200.00


15

9. Once the journal has posted the Disable Impact Detail Report - Balance Forward Implications for this org value will not return a journal line because the journal line created by the balance forward process at year-end (255.23450.3710.000002.678910.0000.00000 in the amount of $300.00) will net out with the existing prior year balance of ($300.00) in that CCID.


Documents

Failed Disable Messages - Harvard University · Web view4All balance forward object codes are central-only and therefore all journals that reference them must be loaded to Oracle