High- Level Specification

Functional Overview

The functional design of the enhancements describes the scenario(s) where enhancements to existing SAP programs are required.

This document outlines the functional requirements for the direct asset procurement  and capitalization process, which focuses on automating the asset creation process within S/4HANA for direct asset purchases originating from Guided Buying.

Scope and Objectives

Scope

The scope of this enhancement is to implement a Business Add-In (BADI) in S/4HANA that automates the following functions upon receiving a Purchase Order (PO) from Ariba Guided Buying:

• Automatic Asset Creation: For each PO line item with the custom account assignment 'Z', the BADI will automatically create a new asset in S/4HANA.

• Derivation of Asset Data: The BADI will derive key asset master data, such as the cost center (from the WBS element on the PO line) and the asset class (from a pre-defined mapping file) and the plant from the PO item.

• Line Item Splitting: If the PO line item has a quantity greater than one, the BADI will automatically create multiple account assignment in S/4HANA, with each account line linked to a uniquely created asset with a quantity of 1.

• Account Assignment Update: The BADI will automatically change the account assignment category on the PO line item from 'Z' to the standard SAP asset account assignment 'A'.  It will need to be updated to multiple account assignment items, one for each asset with a quantity of 1.  It will also set the partial invoice indicator to 1 for Distribute in Sequence.

• Handling PO Changes: The enhancement will manage changes to the PO quantity:

  • Increase: It will create new assets and line item splits for the increased quantity.

  • Decrease: It will delete the corresponding assets and remove their account lines.

• Handling PO Cancellation: The BADI will automatically delete all assets that were created for a PO if that PO is subsequently cancelled.

Objectives

The key objectives of implementing this enhancement are:

• Automation: Eliminate the need for manual asset creation in S/4HANA for direct asset purchases, reducing a labor-intensive and error-prone process.

• Data Integrity: Ensure that every asset is correctly linked to its corresponding PO, providing a clear audit trail from procurement through to asset management.

• Efficiency: Streamline the end-to-end procurement process by automatically converting a requisition from Ariba Guided Buying into a complete and correct asset record in S/4HANA.

• Compliance: Enforce the correct application of accounting rules (capitalization vs. expense) based on pre-defined thresholds without requiring manual user intervention.

Gap Addressed (Compared to SAP Standard)

The core gap addressed by this enhancement is that SAP's standard functionality does not automatically create individual fixed assets upon the creation of a purchase order.

In standard SAP S/4HANA, a purchase order with an asset account assignment requires assets to be created manually. Often, if a PO line item is for more than one asset, the total value is simply posted to a single asset record.

This enhancement bridges this gap by introducing automated asset creation at the PO stage for each individual item, a capability that is not part of SAP's out-of-the-box functionality. It also adds the sophisticated logic to manage quantity changes and PO cancellations, which standard SAP does not handle automatically in this manner. By leveraging a custom account assignment ('Z') and a BADI, the solution provides the necessary automation and granularity to meet the business's specific requirements for tracking individual assets from the point of procurement.

Assumptions

• User Knowledge: Users are assumed to have the necessary knowledge to select the correct WBS element for direct asset purchases.

• Data Integrity: It is assumed that the CEME file in Ariba Guided Buying and the material group-to-asset class mapping file will be accurately maintained and provided by the R2R team.

• System Configuration: For direct asset purchases in Ariba Guided Buying, the system will only permit the use of  WBS elements flagged as a "Direct Asset" that are both active ( i.e, not closed, not locked, not DLFL and not TECO) and budgeted. These specific WBS elements will be restricted to purchases using the 'Z' account assignment.

• BADI Functionality: The S/4HANA enhancement (BADI) will function as designed, handling asset creation, PO changes, and cancellations without errors.

Dependencies

• Ariba Configuration:

  • Correct setup of the CEME file.

  • Extension of the WBS object in Ariba Buying to include 'Direct Asset flag' and 'Capex/Opex Indicator'.

  • Interface from S/4HANA to Ariba Buying must support these new fields.

• S/4HANA Development:

  • Implementation of the BADI enhancement to support automatic asset creation, PO changes, and PO cancellations.

  • Development of the mapping logic for material group to asset class.

• Data from R2R Team:

  • Provision of the capitalization thresholds.

  • Provision of the material group-to-asset class mapping file.

Security, Integrity and Controls

• Security: Users can only select pre-approved WBS elements that are specifically flagged for direct asset purchases.

• Integrity: The system ensures data integrity by automatically creating assets and linking them directly to the S/4HANA PO. All changes (quantity increases/decreases) and cancellations are handled programmatically to prevent data inconsistencies.

• Controls: The use of an automated BADI ensures that asset creation is standardized and follows the defined business logic, reducing manual errors. The S/4HANA PO number being sent back to Ariba provides an audit trail.

Configuration Requirements

• Ariba:

  • Update CEME file with capitalization thresholds and relevant commodity codes.

  • Configure WBS object to allow filtering of selections to only those flagged as "Direct Asset."

  • Extend the WBS object with two new fields: Direct Asset flag and Capex/Opex Indicator.

• S/4HANA:

  • Implement the BADI enhancement to manage the automatic asset creation process upon PO ceation from Ariba Guided Buying.

  • Configure the material group to asset class mapping.

Language Requirements

This solution will be implemented in English, consistent with the global language standard. No specific language-related requirements are noted.

Special Requirements

• Automated Asset Creation: The core functionality relies on a custom S/4HANA BADI to automatically create a new asset for each capitalized line item quantity. This is a critical technical requirement.

• PO Change Management: The solution must handle scenarios where the PO quantity is increased or decreased, requiring the creation of new assets or the deletion of existing ones, respectively.

• PO Cancellation: A process must be in place to automatically delete all assets created for a PO if the PO itself is cancelled.

• WBS Integration: The solution must be capable of receiving and processing WBS elements from Ariba and using them to derive the cost center for asset creation.

Design Rationale

Functional Requirements

Please refer to the Scope and Objectives section

Proposed Technology to Use

The proposed technology for the S/4HANA enhancement will be an SAP Business Add-In (BADI).

The BADI will be implemented within the inbound processing of Purchase Orders (POs) from Ariba Guided Buying. 

Based on standard SAP practice and similar implementations, a strong candidate for this BADI would be one that is called after the data has been validated but before the PO is saved. A likely candidate is within the BADI_PO_CREATION or a related BADI that allows for manipulation of purchase order data and custom logic before the final database commit. The enhancement will need to be configured to specifically check for the custom account assignment category 'Z' that is sent from Ariba Guide Buying.

The enhancement will perform the following actions:

• Read PO data: The BADI will access the inbound PO data, specifically the line item details, including the quantity, material group, and WBS element.

• Trigger Asset Creation: For each line item with account assignment 'Z', the BADI will call the necessary SAP function modules (e.g., BAPI_FIXEDASSET_CREATE) to create a new asset.

• Derive Asset Details: The BADI will use the material group to look up the correct asset class from the provided mapping table and derive the cost center from the WBS element.

• Update PO: After successful asset creation, the BADI will modify the PO line item, splitting it if necessary and changing the account assignment from 'Z' to 'A' (Asset). It will also link the newly created asset number to the PO line item for traceability.

• Handle Changes and Cancellations: Additional logic will be built into the BADI to handle scenarios where the PO is changed or cancelled, ensuring that assets are either created, removed, or deleted as required.

Data Source Considerations

The proposed S/4HANA enhancement for direct asset procurement relies on key data sources to function correctly. This section outlines where the necessary data originates and how it's used in the process.

1. Ariba Guided Buying (Source System)

• Purchase Requisition (PR) Data: The primary source of all transactional data. This includes details like item descriptions, quantities, and most importantly, the account assignment category ('Z' or 'K') and the WBS element selected by the user. This data is transmitted to S/4HANA via the standard Ariba CIG (Cloud Integration Gateway) interface.

• WBS Elements: Ariba's WBS object will be extended with two new fields: Direct Asset flag and Capex/Opex Indicator. These flags will originate from S/4HANA and be transmitted to Ariba, where they will be used to filter the list of available active WBS elements for direct asset purchases.

2. S/4HANA (Receiving System)

• S/4HANA PO Number: After the PO is created in S/4HANA, the system will generate a unique PO number. This number is then sent back to Ariba to serve as a reference for the user.

• Material Master Data: The material group from the incoming PO line item will be used as a key field for the asset class determination.

3. External Data Sources (Configuration & Mapping)

• CEME File: This file, configured in Ariba, is crucial for the automatic account assignment. It contains the thresholds and commodity mappings that determine whether an item should be capitalized ('Z') or expensed ('K').

• Material Group/Asset Class Mapping File: This mapping table, provided by the R2R team (Alex Bechter), will be stored in a custom S/4HANA table. The BADI will read this table to determine the correct asset class based on the material group of the PO line item, ensuring accurate asset categorization.

• WBS Element Flags: The "Direct Asset" and "Capex/Opex" flags on WBS elements are maintained in S/4HANA and need to be synchronized with Ariba to control user selection options.

In summary, the process relies on a robust flow of data from Ariba to S/4HANA, supplemented by key configuration data managed in both systems and an external mapping file provided by the business. This ensures that the automated asset creation process is both accurate and aligned with business rules.

Data Validation Considerations

The following validation checks will be implemented:

1. WBS Element Validation:

   • In Ariba: The system must ensure that the WBS element selected by the user for a capitalized item is a valid, active, and pre-approved WBS element specifically flagged for direct asset purchases.

   • In S/4HANA: Upon receipt of the Purchase Order (PO) from Ariba, the S/4HANA enhancement (BADI) will perform a final validation to confirm that the WBS element is still valid and open for postings. If the WBS element is invalid, locked, or no longer exists, the PO creation will fail, and a clear error message will be triggered and sent back to Ariba.

2. Material Group and Asset Class Mapping:

   • The system will validate that the material group provided on the PO line item has a corresponding entry in the "material group / asset class" mapping table. If a material group for a capitalized item lacks a corresponding asset class, the asset creation process will be blocked, and an error message will be generated. This ensures that every asset is created with the correct classification from a financial perspective.

3. Quantity and Asset Creation Logic:

   • The BADI must validate that the logic for creating multiple assets based on the line item quantity is executed correctly. It will perform a check to ensure that the number of assets created equals the quantity specified on the PO line item.

   • In the case of a PO change or cancellation, the validation will confirm that the correct number of assets are either created, deleted, or unlinked from the PO to maintain a 1:1 relationship between the physical asset and its representation in S/4HANA.

4. Cost Center Derivation:

   • The system will validate that the cost center derived from the WBS element is a valid and active cost center within the S/4HANA system. If the derived cost center is invalid, the asset creation process will fail. This prevents assets from being created with incorrect or inactive master data.

Custom Tables

Master Data

The standard SAP tables ANKA (Asset Class Definition) and T023 (Material Group Definition) are linked via the maintenance view V_T023_A. This view, which is maintained by the R2R team through standard SAP IMG activities, stores the crucial mapping between a Material Group (MATKL) and its corresponding Asset Class (ANLKL).

When a purchase order is created, the custom BADI will query this table using the material group from the PO line item. This ensures the correct asset class is retrieved, which is vital for automated and consistent asset creation based on the procurement category.

Configuration Table

Selection Screen Enhancement

Since this functionality is automated and triggered by an inbound interface from Ariba Guided Buying, there is no user-facing selection screen.

Processing Logic

The core logic for this process will be implemented within an S/4HANA BADI that is triggered during the inbound creation or change of a Purchase Order (PO) from Ariba. This logic will execute after the standard PO data has been received and validated. The BADI will perform a series of checks and actions based on the PO line item details.

Step-by-Step Logic

1. Read Inbound PO Data: The BADI will first read the incoming PO header and line item data.

2. Iterate Through Line Items: The program will loop through each line item of the PO to check for the custom account assignment.

3. Identify Capitalization Items: For each line item, the system will check if the account assignment category is "Z".

4. Process PO Creation:

   • Validate WBS Element: The system will verify that a valid WBS element is present on the line item.

   • Derive Asset Class: Using the material group from the PO line item, the system will perform a lookup in the pre-configured mapping table (provided by the R2R team) to determine the correct asset class.

   • Derive Cost Center: The cost center required for asset creation will be derived from the "Responsible CC" field of the WBS element provided on the line item.

   • Create Assets: A standard SAP BAPI will be called to create a new asset for each quantity specified on the line item.

   • Update PO Line Item: For each newly created asset, the original line item will be split, and the new asset number will be populated. The account assignment will be changed from "Z" to "A". The WBS element will be retained on the line item.

Logic for PO Changes and Cancellations

The BADI will also contain logic to handle changes to or the cancellation of an existing PO, which is critical for data integrity.

• PO Quantity Increase:

  • The BADI will compare the new PO quantity with the original quantity.

  • For the increased quantity, new assets will be created following the same process as in PO creation.

  • New line item splits will be created to link the new assets.

• PO Quantity Decrease:

  • The BADI will compare the new PO quantity with the original.

  • It will identify the assets associated with the removed quantity.

  • The system will then call a BAPI or function module to delete these non capitalized assets and their corresponding line item splits.

• PO Cancellation:

  • If the PO is cancelled entirely, the BADI will identify all assets linked to that PO.

  • It will then perform a mass deletion of all related assets, ensuring no active, orphaned asset records remain in the system.

Expected Outcomes in Different Scenarios

• Successful Creation: A fully approved PR in Ariba Guided Buying with account assignment "Z" will result in a PO in S/4HANA, the automatic creation of one or more fixed assets, and the PO account assignment category being changed to "A."

• Failed Asset Creation: If the BAPI for asset creation fails (e.g., due to missing configuration), the BADI will prevent the PO from being saved and return an error message to the user in Ariba Guided Buying, ensuring the PO is not finalized without a valid asset.

• PO Quantity Change: The system will dynamically adjust the number of linked assets and line item splits to match the new PO quantity.

• PO Cancellation: The system will automatically delete all associated assets, maintaining a clear audit trail.

Volumetrics

This section outlines the estimated data volumes and frequency for the direct asset procurement process. The numbers provided are initial estimates and should be refined with further analysis and data from the business.

Initial Load Volumes

• WBS Elements: The system requires an initial load of all WBS elements flagged for direct asset purchases from S/4HANA into Ariba Guided Buying. We estimate this to be approximately between 1000 and 3000 records. This load will also include the two new custom fields: "Direct Asset flag" and "Capex/Opex Indicator."

• Material Group to Asset Class Mapping: A one-time load of the mapping file will be required to configure the S/4HANA enhancement. The number of records is estimated to be around 200 to 400 records.

• CEME File Configuration: This involves updating the CEME file with capitalization thresholds and relevant material groups in Ariab Guided Buying. This is a one-time configuration task.

Performance Considerations

Given that the core of this process is an S/4HANA enhancement (BADI) that triggers upon the creation of a Purchase Order (PO), performance is a key consideration. The BADI's execution time is critical as it directly impacts the PO creation and subsequent system response.

The enhancement must be designed to handle concurrent execution. It's expected that multiple users will be able to submit purchase requisitions in Guided Buying, leading to simultaneous inbound PO transmissions to S/4HANA.

• Concurrency: The BADI must be able to be executed by 20 users simultaneously without any lock contention issues or performance degradation. This is a realistic assumption for a mid-sized to large organization.

• Transaction Volume: The solution should perform efficiently even when processing a high volume of transactions. It is assumed that the number of direct asset POs will be low to moderate (e.g., 50-100 POs per day during peak periods). Additionally, the solution must handle cases where a single PO has a high quantity and needs to create multiple assets at once. The BADI execution time should remain consistently low (e.g., under 1-2 seconds per PO).

Error Handling

Upon receipt of the Purchase Order (PO) from Ariba, the S/4HANA enhancement (BADI) will perform a final validation check for two potential failure points:

• User-related Errors (Invalid WBS Element): If the error is due to an invalid or locked WBS element, the PO creation will be blocked, and an error message will be sent to Ariba. The user who created the requisition will be notified and will need to take corrective action, such as selecting a new, valid WBS element. The user can then edit the requisition in Ariba and re-submit it. The re-submission will re-trigger the PO creation process in S/4HANA, which should then complete successfully.

• System-level Errors (BAPI Failure): If the asset creation fails due to a system configuration error (e.g., missing asset class mapping), the initial PO creation attempt will be blocked. The S/4HANA error message will be sent to the responsibleS/4HANA support team to address the S/4HANA configuration issue. Once the issue is resolved, the S/4HANA support team will reprocess the PO in S/4HANA. This re-triggers the BADI enhancement to attempt asset creation again with the corrected data. Upon successful re-processing, the S/4HANA PO is created, the asset is generated, and the PO number is sent back to Ariba.

The entire process is designed to be re-processable. Since no PO is created in S/4HANA during a failed attempt, there is no need for complex S/4HANA rollback or recovery procedures. The system relies on the user or a system administrator to correct the root cause of the error and then re-trigger the process.

Testing

How to Test

Positive Test Cases (Successful Scenarios)

Test Case 1: Single Asset Creation (Quantity = 1)

1. Guided Buying: Create a PR for a laptop with a price of €1,200 and quantity 1.

2. Guided Buying: Select a direct asset WBS element

3. Guided Buying: Submit and approve the PR.

4. S/4HANA Validation:

   • Verify that a new PO is created.

   • Confirm that a new asset is automatically created in S/4HANA.

   • Validate that the PO line item account assignment is A (Asset).

   • Ensure the PO line item is correctly linked to the new asset number.

   • Check that the S/4HANA PO number is returned to Guided Buying.

Test Case 2: Multiple Asset Creation (Quantity > 1)

1. Guided Buying: Create a PR for a desktop computer with a price of €1,500 and quantity 3.

2. Guided Buying: Select a direct asset WBS element

3. Guided Buying: Submit and approve the PR.

4. S/4HANA Validation:

   • Verify that a new PO is created.

   • Confirm that three separate assets are automatically created.

   • Validate that the PO line item has been split into three sub-items.

   • Ensure each sub-item is linked to a unique asset number.

   • Check that the PO line item account assignment is now A.

Test Case 3: Mixed Line Items (Asset and Expensed)

1. Guided Buying: Create a PR with two line items:

   • Line 1: Laptop, price €1,200, quantity 1.

   • Line 2: Mouse, price €50, quantity 1.

2. Guided Buying: Select a direct asset WBS element for the laptop.

3. Guided Buying: Submit and approve the PR.

4. S/4HANA Validation:

   • Verify that a new PO is created.

   • Confirm that one asset is created for the laptop.

   • Ensure the laptop line item account assignment is A and linked to the new asset.

   • Validate that the mouse line item account assignment remains K (Cost Center) and that no new asset is created for it.

Negative Test Cases (Error Scenarios)

Test Case 4: No WBS Element Entered (Error Condition)

1. Guided Buying: Create a PR for a laptop, price €1,200, quantity 1. Do not select a WBS element.

2. Guided Buying: Attempt to submit the PR.

3. Expected Outcome: The system should prevent submission and display an error message prompting the user to select a valid WBS element, as it is a required field for this account assignment.

Test Case 5: WBS Element Not Flaged for Direct Asset

1. Guided Buying: Use a pre-approved WBS element from the Guided Buying interface that is not flagged as a Direct Asset.

2. Guided Buying: Attempt to create a PR for a capitalized item.

3. Expected Outcome: The system should not allow the user to select this WBS element for a direct asset purchase.

Test Case 6: PO Quantity Decrease

1. S/4HANA: Using the PO created in Test Case 2 (3 assets), manually decrease the quantity of the desktop to 1.

2. S/4HANA Validation:

   • Verify that the PO is updated and the quantity is changed to 1.

   • Confirm that two of the three assets previously created are cancelled or marked for deletion.

   • Ensure the remaining PO line item split is linked to the single remaining asset.

Test Case 7: PO Quantity Increase

1. S/4HANA: Using the PO created in Test Case 1 (1 asset), manually increase the quantity of the laptop to 4.

2. S/4HANA Validation:

   • Verify that the PO is updated and the quantity is changed to 4.

   • Confirm that three new assets are created

   • Ensure that line item has 4 splits and each sub-item is linked to a unique asset number.

Test Case 8: PO Cancellation

1. S/4HANA: Using the PO created in Test Case 7 (4 assets), manually cancel the entire PO in S/4HANA.

2. S/4HANA Validation:

   • Verify that the PO is successfully cancelled.

   • Confirm that all three assets previously created for this PO are also cancelled or marked for deletion in the asset master data.

Test Considerations/Dependencies

This section outlines the key considerations and dependencies for a successful test plan. The testing process must be a coordinated effort between the Ariba and S/4HANA teams to ensure end-to-end functionality.

Test Planning Considerations

• End-to-End Testing: The core of the testing must be an end-to-end process, beginning with the creation of the requisition in Guided Buying and concluding with the S/4HANA PO being dispatched. This is crucial as the automation relies on seamless communication between the two systems.

• Sequential Testing: Ariba configuration and the S/4HANA BADI development must be tested independently before proceeding to integrated end-to-end testing.

  • Ariba Testing: The Ariba team should confirm that the CEME file correctly defaults the 'Z' and 'K' account assignments and that the WBS element selection is correctly filtered.

  • S/4HANA Testing: The developer should use a test program to simulate the inbound PO data from Ariba Guided Buying, ensuring the BADI correctly triggers asset creation, links assets, and handles quantity changes and cancellations as per the requirements.

• Regression Testing: The implementation of the BADI should not negatively impact existing, non-asset-related PO processes. Regression tests for standard Guided Buying to S/4HANA PO creation should be performed.

Efficient Testing Strategy

To ensure efficient testing of this component, we should use a controlled, repeatable process with well-defined input data after all unit tests have passed. The developer should maintain a set of test scenarios, including:

1. Standard Asset Purchase: A single line item with a quantity of 1.

2. Multi-Asset Purchase: A single line item with a quantity greater than 1.

3. Mixed PR: A requisition with both capitalized and expensed line items.

4. PO Quantity Decrease: A PO is created and assets are linked. The quantity is then decreased in Guided Buying and the PO is changed in S/4HANA.

5. PO Quantity Increase: A PO is created and assets are linked. The quantity is then increased in Guided Buying and the PO is changed in S/4HANA.

6. PO Cancellation: A PO is created, assets are linked, and then the entire PO is cancelled in Guided Buying.

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