Ansicht
Dokumentation

Account Assignment Object for Funds Management and Grants Management (enhanced) ( RELNPY_XX_470_FUNDACC )

PERFORM Short Reference   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Short text

Account Assignment Object for Funds Management and Grants Management (enhanced)

Use

As of SAP R/3 Enterprise Core 4.70 (SAP_HR 470) you can use the component Posting to Accounting to transfer additional account assignment objects from the payroll result to Accounting. You could transfer funds, the fund center, and the commitment item in earlier releases. Now you can use the following account assignment objects:

• Functional area

• Grant

You can enter a date in the system for when the new account assignment objects should be activated for use in Human Resources. This ensures that you do not have to enter the new account assignment objects for retroactive changes with infotype records that already exist. You can store different activation dates for funds, functional area and the grant.

These new account assignment objects do lead to some technical changes to the substitution logic that SAP R/3 uses if it cannot post certain account assignment objects to Accounting.

Transferring account assignment objects for Controlling (CO)

The system response when account assignments for Controlling cannot be posted has fundamentally not changed. For more information, access the SAP Library and choose Human Resources -> Payroll-> Payroll -> Subsequent Activities-> Posting to Accounting -> Technical Aspects -> Substitution Logic for Closed CO Account Assignment Objects.

The only change made is to the check for account assignment objects for posting fixed costs. SAP R/3 checks this account assignment object during the creation of simulation documents and productive posting documents. This check now takes place earlier in the document creation process. This is because SAP R/3 can derive missing account assignment objects of Fund Management (FM) and Grant Managements (GM) from the account assignment objects of Controlling. This means that before this derivation it must be established that SAP R/3 can post all account assignment objects of Controlling. Checking account assignment objects for other postings to Controlling (for example to the master cost center of an employee) was already available in lower released at an earlier point in the document creation process.

If you operate Human Resources and Accounting in separate SAP R/3 systems, the system response also depends on the release status of the Accounting system:

Example

A fixed cost posting on a cost center for overhead costs is transferred as additional account assignment object for funds.

SAP R/3 checks whether it can book the fixed cost center for overhead costs.

• If this is the case, SAP R/3 checks whether it can post the funds:

• System configuration 1: transfer from SAP R/3 Enterprise Core 4.70 (Human Resources) to SAP R/3 Enterprise Core 4.70 (Accounting). If the funds cannot be posted, SAP R/3 uses the derivation rules you define to substitute the funds with a different account assignment object.

• System configuration 2: transfer from SAP_HR 470 (Human Resources) to SAP R/3 4.0B to 4.6C (Accounting). If the funds cannot be posted, SAP R/3 deletes the funds account assignment information and only posts the cost center for the overhead costs.

• If this is not the case, SAP R/3 marks the document lines for this assignment as incorrect. This means that the posting document is also given the stats incorrect and cannot be posted. SAP R/3 outputs the relevant message.

Transferring from account assignment information for objects of Fund Management (FM) and Grants Management (GM)

For posting to Accounting, SAP R/3 can transfer the following account objects for Fund Management and Grants Management. The system response has also changed for account assignment objects that were already available in earlier releases.

• Funds

• Funds center

• Commitment item

• Functional area (new)

• Grant (new)

SAP R/3 checks these account assignment objects during the creation of simulation documents and productive posting documents. If it cannot post individual account assignment objects, or if some objects are missing, the appropriate component of Account enhances the object using derivation rules. We recommend to store account assignment objects in the last derivation rule that the system can always book. In this way you can avoid incorrect posting documents.

Substituting account assignment objects: changes to logging

To limit the number of log lines in a posting document to a sensible amount, the log of substituted account assignment objects for Fund Management and Grants Management has been limited:

Substituted account information		Log
for Controlling		yes
Funds commitment (deleted)		yes
for Fund Management, if incorrect		yes
for Fund Management, if initial		no
for Grants Management, if incorrect		yes
for Grants Management, if initial		no

Posting retroactive accounting results and derivation rules

You cannot delimit the validity period of derivation rules for the substitution of account assignment objects for Funds Managementand Grants Management. SAP R/3 does not document the substitution of account assignment objects in the posting index (tables PPOIX and PPOPX) that is used to post retroactive results. SAP R/3 therefore assumes when posting retroactive results, that the derivation rules have not changes since the original results were posted.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

For more information on derivation rules, access the Implementation Guide (IMG) of Public Sector Management and choose Funds Management Government -> Master Data-> Allocations to Account Assignments from Other Components.

TXBHW - Original Tax Base Amount in Local Currency   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 7970 Date: 20240603 Time: 004003     sap01-206 ( 115 ms )