High- Level Specification

Parameter	Value
Application System	SAP S/4HANA - CUI instanceSAP S/4HANA - China instance SAP S/4HANA - Rest of World instance
Business Process Reference	10.02.04.01. Manage Project Settlement and Closure

Functional Overview

Over time, many PPM items and SAP Project System (PS) projects reach completion or become inactive but remain open in the system. This leads to administrative inefficiencies, a cluttered project portfolio, and potential compliance risks. To address these challenges, this enhancement proposes the automation of idle project closure. To address these issues, this enhancement introduces a program supporting 2 scheduled processes to manage idle projects and assets:

1. Projects Closure (Quarterly)

Run on a quarterly basis to identify inactive or idle projects, which have not been set to Closed status. The program will attempt to automatically close these projects if all closure criteria are met. If a project cannot be closed due to outstanding issues (such as open balances or commitments), the system will notify the responsible Financial Controller for further review and action. 

2. Pending Closure AuC (Monthly)

Run on a monthly basis to identify any idle Assets under Construction (AuC). The program will generate a consolidated notification listing all such AuCs that require attention and send it to the Asset Manager, enabling timely follow-up and resolution.

Scope and Objectives

This enhancement specifically targets SAP Project System (PS) projects that meet the following both criteria:

• Project status is either "Technically Completed" (TECO)
• No financial transactions have occurred for the past six months.

The scope includes:

• Assessment of whether these projects can be fully closed in the system.
• Notification to the responsible Financial Controller if closure is not possible due to outstanding issues (e.g., open balances or commitments).
• Notification for regular review of idle Assets under Construction (AuC) to the Asset Manager.

The objectives are: 

• Minimize erroneous postings by preventing transactions on inactive projects
• Optimize reporting by ensuring only active and relevant projects appear as open
• Maintain good data hygiene by keeping project data accurate, 
• Highlighting non capitalized costs and POs or WOs left open.

Process Flow Diagram

1. Inactive Project Closure Review
   (for SAP PS projects with no transactions for 6 months and status TECO)

2. Idle Asset Under Construction (AuC) Monitoring
(for periodic review and notification of AuCs with no recent activity)

Insert the flowchart and fill in the steps

Assumptions

Describe any assumptions that have been made in the process of completing this design. What functionality is expected of configuration or other developments that pass information to this development and/ or retrieve the information processed by it (performance, triggers, exceptions, etc.)

Dependencies

ERP-167 Sync Project Person Responsible & Applicant with HR Positions

ERP-174 Synch Status from PPM Item to PS Project/WBS

ERP-87 Automate Asset & Settlement Rule Creation - Workflow

Security, Integrity and Controls

To detail the security requirements for processing this enhancement, any data integrity issues associated with the object and the teams that will be responsible for processing the object, i.e. authorization/roles required to who can execute the enhancements, etc.

- Custom Tables, enhancement, transaction codes, programs, Web Dynpro Application, Code Data Services (CDS), Open Data Protocol (OData), BI reports, and Functional Modules need to have at least one authority check either standard or custom. (custom should be an exception)

- All custom tables will be maintained in a certain Authorization Group (example: ZFIN, etc.)

- In the case of transaction codes an additional check other than the object S_TCODE is required. You can use SU24 to find the related authorization objects to check.

All other WRICEFs

- If the authorization check is already performed in the calling Programs, this section can be filled as “Follow calling programs authorization check” (example : BADI to redirect DMS to OpenText, in which the calling Manage Purchase requisition Fiori App already performed authorization check)

- If the authorization check is not checked in any of the development, this section should be filled with the proposed authorization check. You can refer to SU24 to see the standard authorization objects. (example: full custom Fiori App to enable user to download/upload the project plan)

Configuration Requirements

Specify the configuration requirements for this object. Like in case of substitution/ routine specify the configuration needed

Language Requirements

Specify the language requirements for this object. Specify the required language and type of translation, like labels, data.

Special Requirements

Specify any special requirements or considerations that may impact the enhancement based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China

If the enhancement interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.

Design Rationale

Functional Requirements

This section describes the business process and decision logic for managing inactive SAP PS projects and idle Assets under Construction (AuCs). It outlines the key steps and criteria used to identify, review, and act on inactive projects and assets.
Please note that technical implementation details are provided separately in the Processing Logic section.

1. Scheduled Processing

• The program runs in two modes:
  1. Inactive Project Closure Review: Conducted quarterly to identify and process inactive projects.
  2. Idle AuC Monitoring: Conducted monthly to identify and report on idle Assets under Construction.
• The period of inactivity (default: six months) can be adjusted as needed (input parameter).
• The program offers a test mode execution, which will issue a report with all the projects that can be closed and the ones that cannot. List the different reasons preventing the closure. See job log details in Handling Error section.

2. Inactive Project Closure Review

2.1. Identification of Inactive SAP PS Projects

• • The program identifies SAP PS projects that are no longer active, marked as “Technically Completed” TECO
  • Projects used solely for statistical or intercompany recharge purposes are excluded from this review.
  • Only projects and WBS elements with no recorded activity (actuals or commitments) in the past X months are considered inactive and subject to further review. X = Inactivity period. 

2.2 Closure Criteria Review:

1. 1. Attempt to close the WBS elements. Closure is only possible if all of the following conditions are met:

      • Outstanding Time Transfer Check: Confirm that all time bookings have been fully transferred to the relevant WBS elements
      • No open purchase orders or purchase requisitions
      • No open process or work orders
      • All linked assets under construction are fully capitalized or settled
      • The WBS element has a zero balance
      • No Capitalization date maintained on WBS element is the future

   2. Project Closure Action:

      • If all conditions are satisfied, the project status is set to closed. If the project is linked to a portfolio management item, its status is also updated to “Close.”
      • If any condition is not met, the project remains open and the reasons are documented in a notification to the Financial Controller (see section 4).

3. Idle AuC Monitoring

For each AuC assigned to a WBS element project:

• Identify any AuCs that have not been fully capitalized or settled.
• Identify last activity (posting) date.
• If last activity date > Inactivity period and outstanding balance exist, send a consolidated notification to the Asset Manager (see section 4).

4. Notifications

• Inactive Project Closure:
  Financial Controllers receive a consolidated notification listing:

  • Projects that were successfully closed
  • Projects that could not be closed, with reasons for each (e.g., open commitments, pending time transfers, unsettled assets)
  • Guidance on next steps and the date of the next scheduled review

• Idle AuC Monitoring:
  Asset Managers receive a notification listing all identified idle AuCs, including relevant details and recommended actions.

• If a responsible recipient cannot be identified, the issue is logged for further investigation.

• See Processing logic for rules to derive email recipients. 

Proposed Technology to Use

Typically, an enhancement will be based on an existing SAP BADI / user exit. If this is the case, please provide the proposed details of the BADI / user exit.

Data Source Considerations

Include an overview of the source. Can be deleted if not needed.

Data Validation Considerations

Include an overview of the data validation requirement. Can be deleted if not needed.

Custom Tables

If any custom configuration tables are required, which will be read by the enhancement logic, then specify them here. Can be deleted if not needed.

Master Data

<Title Custom Table 1>

<Include an overview of the table and what it’s used for>

Configuration Table

Title Configuration Table 1

Include an overview of the table and what it’s used for

Selection Screen Enhancement

This section will give the details on the selection screen parameters, parameter type and whether it’s obligatory or not. This section can be used to define the Import Export parameters for Function Module or User Exit or Screens. Can be deleted if not needed.

Processing Logic

This section defines the detailed step-by-step logic implemented within the BAdI/User Exit to process the data received from the standard SAP program and database retrieval. It explains the operations performed on the data, the expected outcomes in different scenarios and how the system should behave in response to specific conditions.

1. Scheduled Processing

The program can be executed in 2 modes: 

1. Inactive project closure review: The identification and processing of inactive projects must occur quarterly.
2. Idle AuC Monitoring: The identification and reporting of idle AuCs must occur monthly.

The Inactivity period (defined as 6 months in this FS) is set as an input parameter. 

2. Inactive project closure review

For each identified inactive project, the program:

2.1.Identification of Inactive SAP PS Projects

• • The program identify SAP PS projects with:
    • status TECO: 
      • JEST: Object Status (stores status information for objects like projects and WBS) STAT field = TECO
      • PROJ: Project Definition (main project header data)
      • Join the 2 tables to keep only project definitions.
      • Result: List of project definitions (IDs) that are TECO.
    • Exclude PS project with Project profile = PROJ-PROFL

• • Check that no transactions for the past 6 months: no Actuals nor Commitment posted on all of the related WBS elements. 

2.2 Checks if no outstanding time transfer 

All time booking is transferred to the WBS element (Time booked and time transfer completed).

Check table CATSCO

RPROJ = WBS element = Project id followed by * to obtain all WBS elements for a given project definition (Example, if the project id = A.000004, then search all RPROJ values starting with A.000004); 

TRANSFERRED = " "

If any records with Transferred = " ", then some records are still expected to be transferred. The project cannot be closed. ==> Step 2.5.

2.3 Attempt to set the project status to CLSD (Closed). If 2.2 is successful, simulate a SAP PS Project status change to Closed. If not the below closure criteria are met, the system will prevent the closure and issue an error message.

*If Purchase requisitions are not replicated from Ariba to S4, no check at project closure is done. 

Before performing any actual status changes, the system will simulate the project closure using the following BAPIs:

• • BAPI_PS_INITIALIZATION – to initialize the PS environment

  • BAPI_BUS2054_SET_STATUS – to set the WBS/project status 

  • BAPI_PS_PRECOMMIT – to check for errors prior to commit

In this simulation mode, no status changes are saved. The purpose is solely to detect whether any of the above closure conditions are not fulfilled. If a condition fails, the corresponding error messages returned by the BAPIs will be captured and reported in the notification issued.

2.4 If all the above criteria (2.1 and 2.2) are met, meaning that the project closure simulation reported no errors, the project can be closed:

• • • If the SAP PS project is related to a PPM id, the PPM item status be updated:
      • If PPM Item status = TECO/Cancelled => change PPM Item status to Closed/Cancelled.
      • If PPM Item status = TECO => change PPM item status to Closed. 

Check project id exist in /RPM/ITEM_D field ITEM_D

Function Module /RPM/ITEM_CHANGE - This function module allows to change attributes of a PPM item, including its status.

The status change to Close on the PPM item will be replicated to the SAP PS project. 

• • • Else set the SAP PS project to status CLSD.
    • A consolidated notification is sent to the Financial Controller. See section 4.

2.5 If condition 2.1 and/or 2.2 are not fulfilled, the project will not be closed. 

 Check if the Capitalization date (PRPS-USR08)

• • If Capitalization date is maintained as a date in the future ==> No notification is necessary for this project
  • Else, a notification will be issued for this project.

Notifications detailed in section 5 will be issued.

3. Idle AuC Monitoring

3.1. Identifying AuC Related to WBS
Use ANLA fields:
ANLN1 (Asset Number)
ANLN2 (Asset Subnumber)
POSNR (WBS Element)
ANLKL (Asset Class — to filter for AuC)
Filter where ANLKL corresponds to your AuC asset class and POSNR matches your WBS element.

3.2. Checking for the last Activity (identifying dormant AuC)
Use BUDAT (Posting Date) in ACDOCA.
If there are no entries for the asset in the last X months (X= Inactivity period), it meets inactivity criterion.

3.3. Checking Capitalization/Settlement
Analyze postings in ACDOCA for the asset to determine if it’s fully capitalized or settled.

Use FM FI_AA_VALUES_CALCULATE to determine if the calculated balance is zero, which indicates full settlement.

If there are still open balances or no settlement/capitalization postings, the asset is not fully settled.

3.4 If AuCs not fully capitalized/settled, send a notification to Asset Manager. Details in section 4. 

4. Notification

4.1. Inactive project closure review: 

A consolidated notification for each Financial Controllers highlighting: 

• • • • Projects that were closed by the program
      • Projects that could not be closed and the reasons.

Template email: 

Subject: Inactive Project Closure Review Results – [Processing Date]

Dear [Financial Controller, see section 4.3 for deriving Financial Controller],

As part of the regular review of inactive projects (PS status TECO and no activity in the past [Inactivity period] months), please find below the summary of closure attempts performed on [Processing Date].

1- Projects Successfully Closed

The following projects were successfully closed:

2- Projects Not Closed

The following projects could not be closed. 

*In this case the notification does not display the SAP error message, as no error is generated. Please use the mentioned reason. This occurs if condition 3.1 is valid.

Please review the reasons and take the necessary actions (e.g., settle balances, close orders, resolve AuC issues) to enable closure in the next review cycle.

Next scheduled review: [Next Review Date]

4.2 Idle AuC Monitoring:

A consolidated notification highlighting all the AuC which have not been 

Email template: 

Subject: Consolidated List of Idle Assets Under Construction (AuC) – [Processing Date]

Dear [Asset Manager, see section 4.3 for deriving Asset Manager],

As part of the periodic review of inactive AuC, the following Assets have been identified as inactive (no activity in the past [Inactivity period] months) and are not fully capitalized or settled.

Please review the list below and take appropriate action to settle or capitalize these assets as needed.

4.3 Deriving email recipients

• • • Financial controller: Financial controller position is stored in table PRPS, field ASTNR. From the position ID the SAP Personal ID can be derived through table HRP1001. Then obtain the email address through PA0105.
    • Asset Manager: Refer to FS ERP-87 Automate Asset & Settlement Rule Creation - Workflow.

4.4 Handling notification errors (No recipient derived)

If email recipients cannot be identified, no notification is sent, error is shown in the job error log report. 

Volumetrics

Unknown.

Performance Considerations

Specify if there are any specific performance factors that need to be taken into consideration during development i.e. enhancement must be able to be executed by 10 users at the same time, etc.

Error Handling

The job log report should:

• Record the execution details of the program, including start and end times and selection criteria (Inactivity period).
• Log the number of objects processed (e.g., number of projects with TECO status found).
• List SAP PS projects successfully closed
• List PPM items successfully closed
• List SAP PS projects not closed and provide reason (error or pending timesheet transfer)
• Capture any errors encountered during execution.
• Provide an overview of the notifications sent (recipient, successful or failed)

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

Appendix

Custom Authorization Group Naming Convention

This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log