Kontakt

Ansicht
Dokumentation

POAC_CLD_BADI_LIFEEV - Change the result of the lifetime event check

POAC_CLD_BADI_LIFEEV - Change the result of the lifetime event check

ROGBILLS - Synchronize billing plans   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in Accruals for Purchase Orders (FI-GL-GL-POA) and is intended to be used in a Cloud edition only.

You can use this BAdI to change the result of the lifetime event check. This check evaluates specific properties of a purchase order or purchase order item to determine whether an accrual object should be created, changed or deleted. Another possible result is that the purchase order item should be ignored i.e. no accrual object will be created. One of the properties to be checked is the 'Delivery Complete' indicator of a purchase order item.

The BAdI interface method is CHANGE_LIFETIME_EVENT_CHECK.

To create translatable texts, go to the tile Custom Business Objects, and choose the tab Custom Code Lists. You can find details about how to implement custom code lists in the comments of the example implementation.

Inbound parameters:

  • PURCHASEORDER
    This input parameter provides the purchase order header information. The key field is PURCHASEORDER.
  • PURCHASEORDERITEMS
    This input parameter provides the purchase order item information. The key fields are PURCHASEORDER and PURCHASEORDERITEM.
  • PURCHASEORDERACCOUNTING
    This input parameter provides account assignment information for an item in a purchase order. The key fields are PURCHASEORDER, PURCHASEORDERITEM, and ACCOUNTASSIGNMENTNUMBER.
  • CUSTOMIZINGFOUND
    This input parameter indicates if an accrual object would be generated based on customizing.
  • ACTIVITY
    The input parameter ACTIVITY provides the intended activity. Possible values are:
    '01' = create, '02' = change, '03' = display, '06' = delete
  • IN_CHECKRESULT
    The input parameter provides the original result of the lifetime event check. The possible values and their meaning are:
  • 0 or constant IF_POAC_LIFETIME_EVENT=>GC_CHECK_RESULT_MODIFY:
    This returncode means that an accrual object should be created or changed.

  • 1 or constant IF_POAC_LIFETIME_EVENT=>GC_CHECK_RESULT_IGNORE:
    This returncode means that no accrual object should be created (=ignored).

  • 2 or constant IF_POAC_LIFETIME_EVENT=>GC_CHECK_RESULT_DELETE:
    This returncode means that an existing accrual object should be deleted

The abovementioned key fields are used for the foreign key relationships.

Outbound parameters:

  • OUT_CHECKRESULT
    The output parameter provides the modified result of the lifetime event check. The possible values and their meaning are:
  • 0 or constant IF_POAC_LIFETIME_EVENT=>GC_CHECK_RESULT_MODIFY:
    This returncode means that an accrual object should be created or changed.

  • 1 or constant IF_POAC_LIFETIME_EVENT=>GC_CHECK_RESULT_IGNORE:
    This returncode means that no accrual object should be created (=ignored).

  • 2 or constant IF_POAC_LIFETIME_EVENT=>GC_CHECK_RESULT_DELETE:
    This returncode means that an existing accrual object should be deleted

  • Note: The output parameter OUT_CHECKRESULT must be filled. Copy the original value from IN_CHECKRESULT to OUT_CHECKRESULT if there are no changes.

A simple sample implementation is available that illustrates the intended use of the BAdI. This implementation changes the result to value 0 (create/change), in case the check result was 1 (ignore).






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Material Data  
This documentation is copyright by SAP AG.

Length: 3995 Date: 20240523 Time: 194859     sap01-206 ( 50 ms )