How To Fix SUP016 - FUND CHANGE IS POSSIBLE ONLY AT THE START OF NEW

SAP Error Message - Details

• Message type: E = Error

• Message class: SUP - Message class for superannuation fund maintenance

• Message number: 016

• Message text: FUND CHANGE IS POSSIBLE ONLY AT THE START OF NEW

What causes this issue?

<ZH>System Behaviour In Case of Fund Change Mid Way Through a Payroll
Period</>
From one SGC fund to another SGC fund
The system does not allow retrospective change of contribution from one
SGC fund to another. However, you can retrospectively create a record.
You can also retrospectively discontinue an existing record.
From SGC fund to Non-SGC fund
Delimit SGC funds only at the end of the month, when changing
contribution from SGC fund to Non-SGC fund. This is to ensure that the
SGC funds record exists till the end of the month for calculation of
contributions.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

<ZH>Example</>
An employee on weekly payroll has the following contributions:
Employee contribution: 4%
Company contribution: 9%
Fund: SGC
At the end of pay period 2, employee changes contribution from SGC to
non-SGC fund.
The new contribution details are as follows:
Employee contribution: 3%
Company contribution: 10%
Fund: Non-SGC
The last monthly pay period for which employee contributed towards the
SGC fund is period 4.
To ensure accurate calculation of contribution for the employee, execute
the following steps:
Create Superannuation Aust. infotype (0220) record, valid from the start
of pay period 3 for Non-SGC fund 2, with company contribution of 10% and
employee contribution of 3%. The record is valid up to 31/12/9999.
Create Superannuation Aust. infotype (0220) record, valid from the start
of pay period 3 for SGC fund 1. Specify company contribution of 9% and
no employee contribution. This record should only be valid until the
end of the month. Creation of this record automatically delimits the
previous record for SGC fund 1 to the end of pay period 2. The employee
contribution is removed from the new record to prevent the employee
contribution being paid to both the SGC fund and the Non-SGC fund that
is a contribution of 3% + 4%.
For an employee's superable earnings of AUD 1000 per pay period,
following contributions are calculated for each of the pay periods:
Period 1:
SGC fund 1 Employee contribution AUD 1000 * 4% = AUD 40
Period 2:
SGC fund 1 Employee contribution AUD 1000 * 4% = AUD 40
Period 3:
Non SGC fund 2 employee contribution AUD 1000 * 3% = AUD 30
Non SGC fund 2 company contribution AUD 1000 * 10% = AUD 100
Period 4:
Non SGC fund 2 employee contribution AUD 1000 * 3% = AUD 30
Non SGC fund 2 company contribution AUD 1000 * 10% = AUD 100
SGC fund 1 company contribution (AUD 4000 * 9%) - AUD 200 = AUD 160
AUD 200 is the amount already contributed by the company to Non-SGC
funds.
From Non-SGC fund to SGC fund
When transferring from a Non-SGC fund to an SGC fund, there is no
restriction on when the Non-SGC fund can be delimited. The system will
calculate the SGC contribution at the end of the month, taking into
account all superable earnings for the month (assuming both funds have
the same OTE wage type defined) and any amounts already contributed to
Non-SGC funds.
In case you delimit the first fund, the system does not allow
retrospective change of contribution from one fund to another. This is
applicable to both SGC and Non-SGC funds.

System Response

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SUP016 - FUND CHANGE IS POSSIBLE ONLY AT THE START OF NEW ?

  The SAP error message SUP016, which states "FUND CHANGE IS POSSIBLE ONLY AT THE START OF NEW," typically occurs in the context of fund management or budgetary control within SAP. This error indicates that a change to the fund (or budget) cannot be made at the current point in the process because it is not the beginning of a new fiscal period or budget cycle.
  Cause:
  
  Timing of Fund Change: The error arises when a user attempts to change the fund in a transaction that is not at the start of a new fiscal year or budget period. Fund changes are often restricted to ensure proper financial control and reporting.
  Configuration Settings: The system may be configured to only allow fund changes at specific times, such as the beginning of a new fiscal year or when a new budget is being established.
  Transaction Context: The specific transaction being executed may not allow for fund changes due to its nature or the current state of the budget.
  
  Solution:
  
  Check Timing: Ensure that you are attempting to make the fund change at the appropriate time, typically at the start of a new fiscal year or budget period.
  Review Configuration: Consult with your SAP administrator or financial controller to understand the configuration settings related to fund management. They may need to adjust settings if fund changes are required outside of the standard periods.
  Use Correct Transactions: Make sure you are using the correct transaction codes for making fund changes. Some transactions may have restrictions that others do not.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on fund management and the timing of changes.
  Seek Support: If the issue persists, consider reaching out to SAP support or your internal IT support team for further assistance.
  
  Related Information:
  
  SAP Modules: This error is commonly encountered in modules related to Public Sector Management (PSM) or Controlling (CO).
  Fiscal Year Variant: Understanding the fiscal year variant and how it is configured in your SAP system can provide insights into when fund changes are permissible.
  User Roles and Authorizations: Ensure that the user attempting the fund change has the necessary authorizations to perform such actions.
  
  By addressing the timing and configuration aspects, you should be able to resolve the SUP016 error effectively.