SAP ABAP IMG Activity SIMG_FMFG_CCRMESSG (BAdI: Customizing CCR Expired Vendor Messaging)
Hierarchy
☛ EA-PS (Software Component) SAP Enterprise Extension Public Services
   ⤷ PSM-FG (Application Component) Functions for U.S. Federal Government
     ⤷ FMFG_CCR_E (Package) Interface to Central Contractor Registry (CCR)
IMG Activity
ID SIMG_FMFG_CCRMESSG BAdI: Customizing CCR Expired Vendor Messaging  
Transaction Code S_AEN_10000971   (empty) 
Created on 20050406    
Customizing Attributes SIMG_FMFG_CCRMESSG   BAdI: Customizing CCR Expired Vendor Messaging 
Customizing Activity SIMG_FMFG_CCRMESSG   BAdI: Customizing CCR Expired Vendor Messaging 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FMFG_CCR_MESSAGE_CUS    

Use

Implement enhancement point FMFG_CCR_MESSAGE_CUST enables you to to overwrite hard coded default message types when handling messaging during CCR vendor status validation. These default message types are hard-coded in enhancement FM_DOCUMENT_VALIDATION implementation.

If FMFG_CCR_MESSAGE_CUST is implemented, these default message types can be overwritten with custom message types which can be set based on a transaction type, user ID, and so on. It is also possible to add new validations and custom messages - for example, that a given vendor expires in one week.

Note that values set up in this implementation are overwritten, when applicable, by messages configured in table T100C if the configured messages have a lower severity level. For example, an error (type "E") is overwritten by a warning (type "W"), but the reverse would not be the case. If no corresponding entries exist in table T100C, the custom message types are the ones used.

Requirements

Standard settings

Activities

After you call up the IMG activity, a dialog box appears.

  1. In the dialog box, enter a name for the enhancement implementation, Short Text and Composite Enhancement Implementation. If no Composite exists, create a new one by choosing Create button.
  2. Save your entries, and assign the implementation to a development class.
  3. Click on BAdI tab and choose the Create BAdI button.
  4. In the dialog box, enter BAdI Definition, BAdI Implementation, Implementation Class and description, then press Enter.
  5. In the left panel on the next screen, expand implementation node and double-click on entry Class.
  6. Place the cursor on the method, and double-click to enter method processing.
  7. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod. Note that sample implementation is copied automatically.
  8. Save and activate all the objects.

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
SIMG_FMFG_CCRMESSG US USA
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050407 
SAP Release Created in 600