SAP ABAP IMG Activity MRM_ITEM_CUSTFIELDS (BAdI to Change Customer's Own Fields)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ MM-IV-LIV (Application Component) Logistics Invoice Verification
     ⤷ MRM_BADI (Package) Business Add-Ins in Invoice Verification
IMG Activity
ID MRM_ITEM_CUSTFIELDS BAdI to Change Customer's Own Fields  
Transaction Code S_AC0_52000865   (empty) 
Created on 20050406    
Customizing Attributes MRM_ITEM_CUSTFIELDS   BAdI to Change Customer's Own Fields 
Customizing Activity MRM_ITEM_CUSTFIELDS   BAdI to Change Customer's Own Fields 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name MRM_ITEM_CUSTFIELDS    

Use

This Business Add-In is used in the component MM-IV.

You can use it to change customers' own fields in vendor invoices.

You can use the Business Add-In (BAdI) MRM_ITEM_CUSTFIELDS to integrate a subscreen of your own at item level to process customers' own data. The Customer Include CI_DRSEG_CUST is available for customers' own fields. The structure DRSEG_CI contains the fields C_RBLGP (document item in invoice document), C_KOART (account type), and Customer Include CI_DRSEG_CUST. The structure DRSEG_CI is already contained in the structures DRSEG (invoice item (dialog processing)), MMCR_FRSEG and MMCR_RBMA. If you wish to save customers' own fields to the database, you must attach these fields in an APPEND structure to the corresponding database table (RSEG, RBDRSEG, RBMA). For G/L account lines, add an APPEND structure with the customer's own fields to the structure COBL_MRM. The customer's own fields then also exist in the database table RBCO.

The customer's own fields can be processed on a separate subscreen during online invoice verification with the aid of the Business Add-In MRM_ITEM_CUSTFIELDS. The following data is available for this purpose:

  • Transaction type (Create, Change...)
  • Invoice document header
  • Invoice document items (items with PO reference, items with G/L account posting, items with material posting)

Note:
In the case of automatic transactions, the customer's own fields cannot be populated.

Requirements

To implement this BAdI, you need ABAP knowledge to create the subscreen and for the flow logic.

Standard settings

The Business Add-In cannot be used multiple times.

The Business Add-In is not filter-dependent.

There is no default implementation.

Example:
WKA_ITEM_CUSTFIELDS is available as an example of an implementation.

Further information:

Documentation of BAdI method:
TABPAGE_LABEL_SET

Documentation of BAdI method:
CUSTOMDATA_MODIFY

Documentation of BAdI method:
INVOICE_DATA_TRANSFER

Documentation of BAdI method:
CUSTOM_DATA_TRANSFER

Documentation of BAdI method:
CUSTOM_DATA_GET

Documentation of BAdI method:
INVOICE_DATA_GET

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG MRM_ITEM_CUSTFIELDS 0 HLA0001544 Logistics Invoice Verification 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050406 
SAP Release Created in 600