SAP ABAP Data Element COO_FOMFN (CO obj. planning: FM name to fill appl.-spec. messages)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KPLA (Package) Cost Accounting, planning RK-S
Basic Data
Data Element COO_FOMFN
Short Description CO obj. planning: FM name to fill appl.-spec. messages  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type FUNCNAME    
Data Type CHAR   Character String 
Length 30    
Decimal Places 0    
Output Length 30    
Value Table TFDIR    
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 0   
Medium 0   
Long 0   
Heading 0   
Documentation

Definition

FUNCTION '<COO_FOMFN>'
IMPORTING
I_PGEBIET LIKE KPPT-PGEBIET
TABLES
T_KPP0SM STRUCTURE KPP0SM

  1. The function module parameter is necessary/unnecessary according to whether the application is to transfer the messages for the planning processor, or issue its own messages to the cost centers affected.
  2. The function module name <COO_FOMFN> is freely definable.
  3. Parameter I_PGEBIET contains the current planning area.
  4. Table parameter T_KPP0SM should be filled through the application. Almost all messages with the Identifier K9 can be replaced with your own. Above all, it is worth replacing the messages from inconsistent layouts, as you can set a reference to the maintenance transactions for your own messages in the long text.
    You should consider replacing the following layout messages:
    • K9 152
    • K9 153
    • K9 154
    • K9 159

History
Last changed by/on SAP  19960124 
SAP Release Created in