Ansicht
Dokumentation

FIN_PRED_SWITCH_SIM - Deactivation of Standard Creation of Predictive Journal Entries

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Process Simulation Document Preparation (FI-PRA-PRA) component for predictive accounting.

You can use this BAdI to deactivate the standard simulation and creation of predictive journal entries. Instead, you can create the predictive journal entries using an external interface.

By default, when a sales order is created and predictive accounting is active, the system simulates and creates the predictive journal entries for the follow-on goods issue and billing document in the prediction ledger. An implementation of this Business Add-In (BAdI) is called by predictive accounting after a sales order has been created in the system.

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

The logic of your BAdI implementation must be stable, which means that it always returns the same result for a given set of import parameters.

The BAdI has the following import parameters:

• SOURCEREFERENCEDOCUMENTTYPE

Contains a value to identify the type of the source document that will trigger the creation of the predictive journal entries. For sales orders, the value must be VBAK.

• SOURCEREFERENCEDOCUMENTLOGSYS

Contains a value for the logical system of the source document.

• SOURCEREFERENCEDOCUMENTCNTXT

Contains a value for the organizational unit of the source document.

• SOURCEREFERENCEDOCUMENT

Contains a value to reference the source document.

• ORIGINALREFERENCEDOCUMENTTYPE

Contains a value to identify the type of the original document for which predictive journal entries are to be created. For goods issues, the value must be MKPF. For billing documents, the value must be VBRK.

Note:If you implement this BAdI to create predictive journal entries for goods issues, we recommend that you also implement the FIN_PRED_SWITCH_RED_CL BAdI to reduce them. The same is true for billing documents, you should also implement both BAdIs for this document type.

The BAdI contains the following changing parameter:

• ISSIMULATEDBYAPI

Contains the result of your custom logic.

The CL_FINS_PRED_SWITCH_SIM_EX example BAdI implementation shows you how to implement your own custom logic to deactivate the standard creation depending on the sales order type. The parameter ISSIMULATEDBYAPI must be filled with the expected result.

General Material Data   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 3769 Date: 20240523 Time: 204916     sap01-206 ( 60 ms )