Kontakt

Ansicht
Dokumentation

/ACCGO/CAS_DPQS_DETS - BAdI: DPQS Data Determination for Settlement

/ACCGO/CAS_DPQS_DETS - BAdI: DPQS Data Determination for Settlement

ABAP Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BADI) provides exit points to be used during the DPQS application process, both for volume schedule and value schedule. This is a single use BAdI that contains the following methods:

  • GET_DEFAULT_VOLUME_SCHEDULE
Determines the volume schedule to be used for Logistics Adjusted Quantity (LAQ) evaluation during commingled and any other scenarios where there isn´t a contract application.
It receives an application item and must return the volume schedule to be used.
  • GET_DEFAULT_VALUE_SCHEDULE
Determines the value schedule to be used for LAQ evaluation during contract application. This method will also determine the value schedule to be used for DPQS premium and discounts during contract settlement.
It receives an application item and the contract being applied. It must return the value schedule information to be used.
  • Schedule ID: Indicates the value schedule to be used.

  • Version Timestamp: Used by the system to select the DPQS version to be used. The latest one which is flagged as released on the same timestamp or earlier is selected as long as its validity dates match too.

  • Keep Standard Determination: Flag this return as abap_true (x), if you wish to keep standard DPQS determination and evaluation for the informed application item and contract.

  • GET_VALUE_SCHEDULE_SETTINGS
Determines the DPQS value schedule settings to be used during value schedule evaluation. If the standard determination was decided in the previous method, this method is not called.
It receives an application item and must operates the following returning parameters:
  • CS_HEADER: This structure is already filled with relevant data for the DPQS header to be used. It is filled with data determined at the method GET_DEFAULT_VALUE_SCHEDULE.

Important parameters to inform are:
- GOV_ANALYSIS: To indicate the relevant governing analysis for the contract application.
- GOV_WEIGHTS: To indicate the relevant governing weights for the contract application.
- GOV_TERM,,: To indicate the governing institution of the analysis and weights.
- OV_FLAG: To indicate if specific characteristics and ranges should be used.
- ET_CHARACTERISTICS: Fill this table with the specific characteristics and configuration you wish to be used during the value schedule evaluation. OV_FLAGof CS_HEADER must be flagged in order for this information to be used.
- ET_RANGES: Fill this table with specific ranges of the characteristics informed to be used during the value schedule evaluation. OV_FLAG of CS_HEADER must be flagged in order for this information to be used.
  • EVALUATE_AT_SETTLEMENT
Returns true ('X') to evaluate at settlement if you wish to re-evaluate DPQS value schedule characteristics and ranges during settlement. If this is returned as true, during settlement evaluation of DPQS premiums and discounts, the system will execute GET_DEFAULT_VALUE_SCHEDULEand GET_VALUE_SCHEDULE_SETTINGSagain, using the returned parameters to calculate DPQS premiums and discounts. This will happen only if the application at hand is already finally applied. Otherwise, if the application is not final, or evaluate at settlement is false, the system will use the returned values by GET_DEFAULT_VALUE_SCHEDULEand GET_VALUE_SCHEDULE_SETTINGSduring contract application. You can control individually if a re-evaluation will happen at settlement, even if you return "evaluate at settlement" as true, if the "keep standard determination" flag of GET_DEFAULT_VALUE_SCHEDULEis returned as true for the input parameters.
These methods are from several places for DPQS evaluation routines.

DPQS master data exists.

For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).

  1. Create a BAdI implementation.
  2. Implement all BAdI methods to keep DPQS evaluation working.
  3. Test the implementation in order to make sure LAQ evaluation for commingled and other unapplied scenarios is working.
  4. Test the implementation in order to make sure LAQ evaluation for applied scenarios is working.
  5. Test the implementation in order to make sure discounts and premiums evaluation during settlement is working.

No example is provided for this BAdI.

This BAdI is under the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development -> Enhancement Framework.

This BAdI uses the interface /ACCGO/IF_ENHANCED_DPQS_DET.

For more information, display the interface in the Class Builder (Transaction SE24).






General Material Data   General Material Data  
This documentation is copyright by SAP AG.

Length: 6613 Date: 20240419 Time: 033129     sap01-206 ( 99 ms )