SAP ABAP Data Element COO_CCPFN (CO obj. planning: FM name to check components)
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_CCPFN
Short Description CO obj. planning: FM name to check components  
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  
Medium  
Long  
Heading  
Documentation

Definition

FUNCTION '<COO_CCPFN>'
IMPORTING
I_PGEBIET LIKE KPPT-PGEBIET
I_KOKRS LIKE TKA01-KOKRS
I_CCSS STRUCTURE CCSS
EXPORTING
E_SUBRC LIKE SYST-SUBRC
E_MESG STRUCTURE MESG

  1. The function module parameter is necessary/unnecessary according to whether the application will carry out component checks or not. Most CO applications have active indicators in table TKA00. Function modules are called up by fiscal year.
  2. Parameter I_PGEBIET contains the current planning area.
  3. Parameter I_KOKRS contains the set controlling area.
  4. Parameter I_CCSS contains all information from tables TKA07 and TKA00, which exist in the CCSS structure.
    These CCSS fields are filled within the validation exit for the version (LGUMDF15).
  5. Parameter E_SUBRC is set through the application and displays whether everything is correct (E_SUBRC=0), or not (E_SUBRC>0).
  6. Parameter E_MESG is used in the case of errors to transfer messages. These messages are then collected and can be displayed using the function "Error log ->" "Combinations..." within planning.

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