Kontakt

Ansicht
Dokumentation

REFX_RECD_CONDITION - Specify Defaults and Perform Consistency Check per Condition

REFX_RECD_CONDITION - Specify Defaults and Perform Consistency Check per Condition

ROGBILLS - Synchronize billing plans   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

You can use this Business Add-In (BAdI) to influence the standard behavior of conditions.

The following methods of the BAdI are called automatically when the condition is being processed:

  • CHECK_ALL
This method is called when the user chooses the Check pushbutton.
The returned messages (CT_MESSAGE parameter) are displayed in the same list as the messages from standard processing.
The ID_ACTIVITY parameter specifies if the object is currently in create mode (01) or change mode (02).
  • MODIFY_DUEDATE
This method is called when calculation entries are updated.
By modifying the parameter CD_DUEDATEUP modifying the parameter CD_DUEDATEUP, you have the option of adjusting the due date for follow-up postings that was set manually.
  • GET_ADJUSTMENT_RULE
The method is called when conditions are created.
If the method returns an adjustment rule (parameter CD_ADJMRULE), then the system searches for or creates this adjustment rule in the contract or rental object and assigns it to the condition.
If the CF_ADJMRULE_NEW parameter is set, then a new adjustment rule is created.
If you want to always exclude a condition from automatic adjustment, then set the CF_NOT_ADJUSTABLE parameter.
  • GET_TAKE_ADJUSTMENT_RULE
This method controls how a default value is provided (parameter CF_TAKE_ADJMRULE) for the adjustment rule transfer indicator when proposed conditions are added.
  • GET_LOCK_CONTEXT
You can use this method to lock conditions to being changed, as follows:
  • CF_LOCKED: Locks input fields (exception: memo)

  • CF_COPY_LOCKED: Prevents the condition from being copied

  • CF_DELETE_LOCKED: Prevents the condition from being deleted

  • EF_BOOK_UNLOCK_LOCKED: Prevents the removal of posting locks

  • CD_XLOCKED: Specifies the reason for the lock in text form (for display when condition changed)

Using table CT_UNLOCK_FIELD, you can exclude individual fields from being locked:
  • CONDVALIDFROM: Condition start date

  • CONDVALIDTO: Condition end date

  • CALCRULE: Calculation formula

  • DISTRULE: Distribution formula

  • DUEDATEUP: Due date of follow-up posting

  • TERMNOPY: Posting term

  • TERMNORH: Frequency term

  • TERMNOOA: Organizational assignment term

  • TERMNOAJ: Adjustment term

  • TERMNOSR: Sales rule term

  • TERMNOMR: Peak sales rule term

  • TERMNOPYSCS: Service charge settlement posting term

  • TERMNOPYSCSACT: Service charge settlement posting term active/inactive

  • UNITPRICE : unit price

  • CONDCURR: Currency

  • CHECK_ALL, GET_ADJUSTMENT_RULE and GET_LOCK_CONTEXT
    The data of the condition is available in these methods in the IS_CONDITION parameter.
    In addition, the IO_OBJEKT parameter specifies the object that has the condition (contract or rental object).
  • GET_BEHAVIOR_CONTEXT
    This method controls if the CFPOSTINGFROM field is ready for input: 'DATE 1ST POSTING' for the condition using the parameter 'CF_DISABLE_CFPOSTINGFROM'. The data of the condition is available in the IO_CONDITION parameter.
  • SET_DERIVATION_FIELDS
    Using this method, you can fill your customer-specific additional fields of the structure 'RECDDERIVATEIONFIELDS' for the derivation of the condition group. The object that has the condition is available in the parameter IO_OBJEKT. For more information about this topic, see Define Derivation Steps

Note

When implementing the BAdI, you are not allowed to use statements that affect the interface, such as direct output of messages using the statement MESSAGE.

Notes for Developers






rdisp/max_wprun_time - Maximum work process run time   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 6862 Date: 20240523 Time: 203755     sap01-206 ( 69 ms )