Ansicht
Dokumentation

IFW_MODEL_ENHANCE - BAdI: Supply of Additional Fields for IFW Report

Fill RESBD Structure from EBP Component Structure   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

This BAdI can be used to enhance the data presented on the UI of the report Invoice Forecasting Worklist with additional information. The enhancement of the UI has to be done in two steps:

1. Enhance the UI itself, for example with an additional field.
2. Reimplement or enhance the existing UI classes.

After this work is done, this BAdI comes into play and can be used to supply values to the additional or new fields on the UI. The following three methods can be used for that:

• Method SUPPLY_ADD_UI_FIELDS: This provides the flexibility to determine and supply additional values for the IFW UI.

• Method GET_HEADER_INV_DUE_DATE: This can be used to determine the Invoice Due Date at Header level different to the standard logic. The Invoice Due data is only available on invoice item level, therefore, in standard, the invoice due data on UI worklist level is determined based on invoice type and invoice category.

• Method MERGE_INVOICE_FOR_UI: This has an impact on the merge logic of items of a differential invoice merged into one compressed UI result. In standard the UI presents only merged results. In this BAdI method, it is possible to implement different merge logic. The merge logic is only executed if an invoice was physically created in MIRO or VF01 using differential invoicing. All forecasting records are already merged during the invoice forecasting run.

Precondition for implementing the method SUPPLY_ADD_UI_FIELDS is that the UI was successfully extended to store additional values.

The other two methods can be used if the customer wants to execute a different logic to that in the SAP standard without any precondition.

Behavior of standard logic for UI merging:

The standard UI merge logic is used if a final or delta invoice was created in the corresponding transactions of MM/SD. Depending on price changes, this invoice can contain debit or credit records representing the original value and the new value. The UI merge puts these records together into a delta record.

Behavior of standard logic for determining the header invoice due date:

The standard logic determines an aggregated invoice due date on UI worklist level, based on the invoice type and invoice category.

Fill RESBD Structure from EBP Component Structure   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 2496 Date: 20240607 Time: 034238     sap01-206 ( 53 ms )