Kontakt

Ansicht
Dokumentation

UAB_FUNC_FIELD - Define Customer-Specific Class Methods for Formulas

UAB_FUNC_FIELD - Define Customer-Specific Class Methods for Formulas

CL_GUI_FRONTEND_SERVICES - Frontend Services   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you can specify the fields that provide the formulas for user-defined class methods and that can be edited by users. These fields are included in the delta costing.

In the Product Design Cost Estimate (PDCE), you can define class methods as formula functions in which you can also map complex business logic.

To ensure the delta costing also includes these fields, you have to define in PDCE whether a costing structure is to be calculated again after you have changed a field value. This means the delta costing is only triggered if the fields offered in formulas or in formula functions have been changed.

PDCE can read these formulas in order to recognize the fields and formula functions that are available direct in the formulas. Further, you have to specify in the PDCE which fields are made available by user-defined class methods.

You have activated the delta costing. You can activate the delta costing in Customizing under Costing Solutions -> Structures -> Activate Delta Costing.

If you define class methods for formulas, and register them in transaction Change Structures (UAST), then you have to enter the fields made available by the class methods in this activity. Otherwise the delta costing cannot be processed correctly.

Enter the class method and the fields that contain these class methods.

For additional information about user-defined formula functions, see the SAP Library under Product Design Cost Estimate -> Standard Costing Logic -> Create Costing Formulas -> User-Defined Functions for Formulas.

You have created class CL_SAMPLE_CLASS with method SAMPLE_METHOD as a formula function. Method SAMPLE_METHOD uses three fields from the data basis 1PDCE as factors to calculate the result.

  • Field /1FB/PROFIT_CTR of object type 1MATERIAL.

  • Field /1FB/CECLS of attribute group 1QTY.

  • Field /1FB/PRICE_BASE of edge type 1LINK.

As the user cannot directly change field /1FB/CECLS, you can only register the other two fields that are used by method SAMPLE_METHOD as follows:

  • Field /1FB/PROFIT_CTR
  • Data basis: 1PDCE

  • Class/Interface: CL_SAMPLE_CLASS

  • Method: SAMPLE_METHOD

  • Meta type: OBJ (object type)

  • Type: 1MATERIAL

  • Field name: /1FB/PROFIT_CTR

  • Field /1FB/PRICE_BASE
  • Data basis: 1PDCE

  • Class: CL_SAMPLE_CLASS

  • Method: SAMPLE_METHOD

  • Meta type: EDG (edge type)

  • Type: 1LINK

  • Field name: /1FB/PRICE_BASE

In transaction Change Structures (UAST), you can check whether a field has been changed or not in the Entry column.






TXBHW - Original Tax Base Amount in Local Currency   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 4150 Date: 20240523 Time: 182717     sap01-206 ( 57 ms )