Business Scenario

In SAP Project System, projects often distinguish between CAPEX and OPEX costs by using dedicated WBS elements.

For example:

• WBS Element A → CAPEX
• WBS Element B → OPEX

When integrating these costs into SAP EPPM Financial Planning, the business requirement is frequently to display CAPEX and OPEX costs in separate financial planning categories.

The challenge is that for both WBS elements cost will appear with the same Cost Element or Cost Center/Activity Type.

Since the standard EPPM aggregation logic only considers these dimensions, both costs would be aggregated into the same financial planning category.

By introducing custom value types, additional business logic can be incorporated into the financial integration process.

Implementation

1. Create Custom Value Types 

The first step is to define custom value types. A value type represents the origin or classification of financial data within the integration between Controlling and Portfolio Management.

Custom value types can be maintained in the Portfolio Management Financial and Controlling Integration customizing ( Integration with Other SAP Components -> SAP Portfolio and Project Management -> Portfolio Management -> Customize Portf. and Proj. Mgmt Value Type ). In case your SAP EPPM and SAP Project System are runnin on 2 different instances, please configure the custom value types on both.

For the CAPEX/OPEX scenario, two custom value types can be introduced:

These value types will later replace the standard value type during data transfer.

2. Maintain Integration Customizing

The next step is to maintain the integration customizing that maps the custom value types to the corresponding View–Category–Group combinations.

Separate entries must be created for each custom value type.

3. Implementation of BAdI RPM_FICO_INT

The final step is to implement BAdI RPM_FICO_INT.

This enhancement allows the value type to be modified during the financial integration process.

For actual costs, the method:

IF_EX_RPM_FICO_INTF~CONVERT_BW_WBS_COST

can be used.

Depending on the integration scenario, other methods of the same BAdI may be more appropriate.

Example Logic:

For each entry in CT_COST_OBJECT_DATA:

1. Read the assigned WBS element
2. Determine whether the WBS belongs to CAPEX or OPEX.
3. Use an identifier such as:

• WBS numbering conventions
• User-defined fields
• Project attributes
• Object class

Example:

• WBS PRJ-100-C→ Value Type ZC
• WBS PRJ-100-O → Value Type ZO

After the value type has been changed, the standard integration framework processes the data according to the customizing maintained in step 2.

Result

After implementing the enhancement, financial data is automatically aggregated into the correct:

No additional enhancements or reporting logic are required.

The standard EPPM financial planning functionality can therefore be extended to support business-specific dimensions such as CAPEX/OPEX while preserving the standard aggregation mechanism.

Conclusion

Custom value types provide a flexible way to enrich the standard SAP EPPM financial integration process.

By combining:

• Custom value types
• Integration customizing
• BAdI RPM_FICO_INT

organizations can introduce additional financial dimensions that are not covered by the standard cost element and cost center logic.

Although this article uses a CAPEX/OPEX split as an example, the same approach can be applied to other business requirements, such as:

• Investment categories
• Business units
• Funding sources
• Other customer-specific reporting dimensions