Kontakt

Ansicht
Dokumentation

ISAUTO_MRER - BAdI: Enhanced Evaluated Receipt Settlement (Automotive)

ISAUTO_MRER - BAdI: Enhanced Evaluated Receipt Settlement (Automotive)

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

You can use this Business Add-In (BAdI) to control Evaluated Receipt Settlement (ERS).

This BAdI is used in the application component Self-Billing Outbound (IS-A-SBO).

This BAdI consists of the following methods:

  • Change the data per settlement item (CHANGE_DATA)
  • Change the header/item fields of the invoice document (CHANGE_PREPARED_DATA)
  • Calculate the surcharge value (CHANGE_HSC_VALUE)
  • Data formatting and check (READ_REFERENCE_DATA)
  • Split limit for document selection (CHANGE_SPLIT_LIMIT)

This BAdI is called at different times, for example, during data formatting for credit memo or invoice creation (from purchase order history, purchasing document item or header, worklist (EKRS) or before the invoice or credit memo data is posted.

The BAdI is not active as a default.

The BAdI is not filter-dependent and not reusable.

This BAdI replaces the following Customer Exits in the enhancement MRER0001 as of DIMP 4.71:

  • EXIT_RMMR1MRR_001 Enhanced Auto ERS: Change the Values per Settlement
is replaced by the method CHANGE_DATA
  • EXIT_RMMR1MRR_002 Enhanced Auto ERS: Change Header/Item Fields
is replaced by the method CHANGE_PREPARED_DATA
  • EXIT_RMMR1MRR_003 Enhanced Auto ERS: Calculate the Surcharge Value
is replaced by the method CHANGE_HSC_VALUE

These methods are called using the default coding as long as the BAdI is not implemented.

If you want to implement the BAdI then you can:

  • Call the current Customer Exit in the BAdI method or
  • Implement the BAdI method

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.

To call default coding choose Goto → Default Coding.

Methods
Change the Data per Settlement Item (CHANGE_DATA)
Change the Header/Item Fields of the Invoice Document (CHANGE_PREPARED_DATA)
Calculate the Surcharge Value (CHANGE_HSC_VALUE)
Data Formatting and Check (READ_REFERENCE_DATA)
Split Limit for Document Selection (CHANGE_SPLIT_LIMIT)






CL_GUI_FRONTEND_SERVICES - Frontend Services   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 5288 Date: 20240523 Time: 192459     sap01-206 ( 61 ms )