ABAP: How to read application server name in abap

We can see the list of all application servers via SM51 txn.

It's very easy to find the Application server host name and you can find the same using the SYST parameters( SY-HOST).

But at times, there are requirements to show/display the actual name of the application server.

Here is a simple code for the same using C Functions within ABAP.

  call 'C_SAPGPARAM' id 'NAME'  field 'rdisp/myname'

                                     id 'VALUE' field lv_current_server.

Cheers,

Sandeep 

ABAP: Count number of code lines in METHODS

As you know it's pretty easy to count the no. of code lines for Include/Module/Report programs, you have to simply use statement READ REPORT and you are done.

But in case of counting the code lines in class methods it's a bit.

The same can be achieved by following simple steps:

1.     Do a select on TADIR for the class name as obj_name and build the object range with 'I' 'EQ' and low as 'CLAS'.

2.     Find all the class include using FM: SEO_CLASS_GET_METHOD_INCLUDES ( pass clskey = clsname)

e.g CALL FUNCTION 'SEO_CLASS_GET_METHOD_INCLUDES'

           EXPORTING
            clskey                       = is_class_key
          IMPORTING
            includes                     = it_class_incl
          EXCEPTIONS
            _internal_class_not_existing = 1
            OTHERS                       = 2.
        IF sy-subrc <> 0.
          CONTINUE.
        ENDIF.

3.     Build  the sub_name internal table using it_class_incl-cpdkey-cpdname.

4.     Get the source code using FM : SEO_METHOD_GET_SOURCE

e.g  CALL FUNCTION 'SEO_METHOD_GET_SOURCE'

        EXPORTING
          mtdkey                              = is_class_cmp
        IMPORTING
          source_expanded                     = it_class_code
        EXCEPTIONS
          _internal_method_not_existing       = 1
          _internal_class_not_existing        = 2
          version_not_existing                = 3
          inactive_new                        = 4
          inactive_deleted                    = 5
          OTHERS                              = 6.
      IF sy-subrc <> 0.
        CONTINUE.
      ENDIF.

5.     After this you have the source code in lt-class_code and do a COUNT.

e.g       is_result-count = LINES( it_class_code ). "initial count
      LOOP AT it_class_code ASSIGNING .
        IF  IS INITIAL.
          DELETE it_class_code.
        ELSE.
          IF (1) = '*'.
            DELETE it_class_code.
          ENDIF.
        ENDIF.
      ENDLOOP.
       is_result-count_check = LINES( it_class_code ). " without comments
      LOOP AT it_class_code ASSIGNING .
        FIND '.' IN .
        IF sy-subrc <> 0.
          FIND ',' IN .
          IF sy-subrc <> 0.
            DELETE it_class_code.
          ENDIF.
        ENDIF.
      ENDLOOP.

  is_result-count_check_final = LINES( it_class_code )."final count 

Cheers,
Sandeep 

ABAP: Append structure to a table and status is “partially active”

Most often at customer sites one can get in trouble as they want to enhance a table and at times the length of table fields is more than what SAP supports and the appended structure is not activating fully in other words... "partially active" status.

The limit for field length mentioned is 4030 bytes as of basis release 620 SP25.

Even though it has partially active status we can add data and retrieve data from database but its flag an error "inconsistency persist".


In such situations the below tips can make life easy :

You can either execute report TOUCHTAB - Generate Program After Structure Changes in R/3 Repository to bump the limit whatever your database supports

OR

Change the DB Constants for Tables  using report RADTBCON.

Note:  As per SAP, "We recommend that you do not extend it any further than this. See note 636217. For detailed information, see note 355898 (Restrictions for transparent tables)".

Hope this helps.

Cheers,
Sandeep

ABAP: Store and read data from clusters

Hello,

Here is a simple program to store and read data from the clsuter.

* Create a transperant table , copy structure of table INDX.

DATA: it_info TYPE string,
      is_key(4) .

it_info = 'Test to save data to INDX'.
is_key = 'TEST'.

* Export to DB clsuter
EXPORT   gs_info    FROM it_info
         TO DATABASE zsandy_test(sy)
         ID is_key.

CLEAR it_info.

* Import from DB cluster.
IMPORT gs_info     = it_info
         FROM DATABASE zsandy_test(sy)
         ID is_key.

WRITE:/ it_info. " this will show the record which is inserted with EXPORT

This is for the beginners :)

Cheers,
Sandeep

IMG extenisons in SPRO

The following steps would help you add a node to SPRO:

1. Node creation:

- Use transaction S_IMG_EXTENSION and select the IMG structure that youu want to extend.

- Create a new enhancement and select the same and click on option ENHANCE STRUCTURE.

- Navigate to the point where you need the node and click on icon create activity

- Give the IMG ACTIVITY ID and NAME .

- Provide an ID and name in the tab MAINTAIN OBJECTS and give the object description in the same.

- Eg : If a maintenace view, enter the customizing object name as the view name, type as V and the transaction as SM30 and save.

2. Add supporting help documentation for the node:

-Use the tab DOCUMENTATION and create a document. I

- To insert hyperlinks in the documentation which are mapped to the data element documentation (same as SAP standard).

-Use LINK option in the INSERT menu in the documentation window.

-Select ‘Data element’ option from the drop down

-Provide the data element name to create the hyperlink.

Important Txns in Archive for Abapers

You always wonder what Archive is all about and where abapers are asked to pitch-in , well here is short list of transactions which might help you to start with.

AS_AFB : Archive file browser

AS_ADMIN : Archive Administration

AOBJ : view maintenance for archive objects

SARA : Archive administation

SARI : Archive info. system - central management

ALO1 : search for documents with relationships inc archive

To check the info structure for a session : SARI-> customizing->provide archive info. -> check Technical data ( this is a structure in db)

FM: KASH_ARCHIVE_DATA_OBJECT_SHOW to check archive files data

How large can and should the lock table be configured?

For release 4.0 the default size for the lock table is 4 MB. For medium-sized systems this value is absolutely sufficient. As of 4.6, it appears that a size of 10-20 MB is required for some background jobs, and a size of 32-200 MB may be required for large systems, although this is the exception. As a lock table that is too small causes transaction terminations, but resources for the lock table are relatively low, a size of 20 MB should be specified initially. no further changes are generally required to the layout of the shared memories with this size (except for AIX 32 bit). You can enter this setting using the profile parameter: enque/table_size = 20000

You can monitor the lock table in transaction SM12 via the menu option "Extras -> Statistics".

The lock table is a shared memory, not a database table.

ABAP: How to debug a program which is running in an endless loop

Imagine your program is running in an endless loop and you need to analyze its behavior. In such situations you can force the running program into the debugger simply by setting a session breakpoint in a second ABAP Editor. In Utilities->Settings...->Debugging just choose the Session breakpoint active immed. option. When you activate this option, all (running and waiting) sessions of your logon session immediately inherit all session breakpoints set in any of those sessions. It is recommended that you activate this option in development environments.

ALV : Drag and Drop on rows

REPORT zalv_dragndrop.


*Structure declaration for T016T


TYPES : BEGIN OF ty_t016t,


brsch TYPE brsch,


brtxt TYPE text1_016t,


spras TYPE spras,


END OF ty_t016t.


*Work area and internal table for T016T


DATA : it_t016t TYPE STANDARD TABLE OF ty_t016t,


wa_t016t TYPE ty_t016t.


*class declaration


CLASS lcl_objdragdropapp DEFINITION DEFERRED.


*data declarations for alv


DATA: c_dragdropapp TYPE REF TO lcl_objdragdropapp,


c_dockingcont TYPE REF TO cl_gui_docking_container,


c_alv TYPE REF TO cl_gui_alv_grid,


* reference variable to CL_DRAGDROP:


c_dragdropalv TYPE REF TO cl_dragdrop,


it_layout TYPE lvc_s_layo,


it_fcat TYPE lvc_t_fcat. "Field catalogue


*declarations for handle event


DATA: effect TYPE i,


handle_alv TYPE i.


*start of selection event


START-OF-SELECTION.


*select data


PERFORM fetch_data.


*ALV output


PERFORM alv_output.


* Class definitions and method implementation for drag and drop


CLASS lcl_dragdrop DEFINITION.


PUBLIC SECTION.


DATA: wa TYPE ty_t016t,


index TYPE i. "Index of Line to be moved


ENDCLASS. "LCL_DRAGDROP DEFINITION


*Application class definition


CLASS lcl_objdragdropapp DEFINITION.


PUBLIC SECTION.


METHODS:


*Handling Event Drag


handle_alv_drag


FOR EVENT ondrag


OF cl_gui_alv_grid


IMPORTING e_row e_column e_dragdropobj,


*Handling event DROP


handle_alv_drop


FOR EVENT ondrop


OF cl_gui_alv_grid


IMPORTING e_row e_column e_dragdropobj.


ENDCLASS. "LCL_objdragdropapp DEFINITION


*Application class implementation


CLASS lcl_objdragdropapp IMPLEMENTATION.


* OnDrag event is used to 'fetch' information from the drag source.


METHOD handle_alv_drag.


DATA: dataobj TYPE REF TO lcl_dragdrop,


line TYPE ty_t016t.


* Read dragged row


READ TABLE it_t016t INDEX e_row-index INTO line.


* create and fill dataobject for events ONDROP


CREATE OBJECT dataobj.


* Remembering row index to move a line


MOVE e_row-index TO dataobj->index.


* store the dragged line.


READ TABLE it_t016t INTO dataobj->wa INDEX e_row-index.


* Assigning data object to the refering event parameter


e_dragdropobj->object = dataobj.


ENDMETHOD. "HANDLE_ALV_DRAG


*Event handler for event 'OnDrop'. This event is used


*to use your dragged information in combination with your drop source.


METHOD handle_alv_drop.


DATA: dataobj TYPE REF TO lcl_dragdrop,


drop_index TYPE i,


stable TYPE lvc_s_stbl.


* Refresh Alv Grid Control without scrolling


stable-row = 'X'.


stable-col = 'X'.


* Catch-Statement to ensure the drag&drop-Operation is aborted properly.


CATCH SYSTEM-EXCEPTIONS move_cast_error = 1.


dataobj ?= e_dragdropobj->object.


DELETE it_t016t INDEX dataobj->index.


INSERT dataobj->wa INTO it_t016t INDEX e_row-index.


*Refreshing the ALV


CALL METHOD c_alv->refresh_table_display


EXPORTING


i_soft_refresh = 'X'


is_stable = stable.


ENDCATCH.


IF sy-subrc <> 0.


* If anything went wrong aborting the drag and drop operation:


CALL METHOD e_dragdropobj->abort.


ENDIF.


ENDMETHOD. "HANDLE_ALV_DROP


ENDCLASS. "LCL_objdragdropapp IMPLEMENTATION


*&---------------------------------------------------------------------*


*& Form alv_output


*&---------------------------------------------------------------------*


FORM alv_output .


CALL SCREEN 600.


ENDFORM. " alv_output


** Calling the ALV screen with custom container


*On this statement double click it takes you to the screen painter SE51.


*Enter the attributes


*Create a Custom container and name it CC_CONT and OK code as OK_CODE.


*Save check and Activate the screen painter.


*Now a normal screen with number 600 is created which holds the ALV grid.


* PBO of the actual screen ,Here we can give a title and customized menus


*&---------------------------------------------------------------------*


*& Module STATUS_0600 OUTPUT


*&---------------------------------------------------------------------*
MODULE status_0600 OUTPUT.


* SET PF-STATUS 'xxxxxxxx'.


* SET TITLEBAR 'xxx'.


IF c_alv IS INITIAL.


PERFORM alv_controls.


ENDIF.


ENDMODULE. " STATUS_0600 OUTPUT


*&---------------------------------------------------------------------*


*& Form alv_CONTROLS


*&---------------------------------------------------------------------*


FORM alv_controls.


* create docking container for alv control


CREATE OBJECT c_dockingcont


EXPORTING


dynnr = '600'


extension = 300


side = cl_gui_docking_container=>dock_at_top.


* create alv control


CREATE OBJECT c_alv


EXPORTING i_parent = c_dockingcont.


* create the application object to handle the ABAP Objects Events


CREATE OBJECT c_dragdropapp.


* Events alv control


*For Dragging


SET HANDLER c_dragdropapp->handle_alv_drag FOR c_alv.


*For Dropping


SET HANDLER c_dragdropapp->handle_alv_drop FOR c_alv.


* build tree nodes for drag&drop


PERFORM build_handle.


* Fieldcatalogue for ALV


PERFORM alv_build_fieldcat.


* ALV attributes FOR LAYOUT


PERFORM alv_report_layout.


* Call ALV GRID


CALL METHOD c_alv->set_table_for_first_display


EXPORTING


is_layout = it_layout


CHANGING


it_outtab = it_t016t


it_fieldcatalog = it_fcat


EXCEPTIONS


invalid_parameter_combination = 1


program_error = 2


too_many_lines = 3


OTHERS = 4.


IF sy-subrc <> 0.


MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno


WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.


ENDIF.


ENDFORM. "ALV_CONTROLS


*&---------------------------------------------------------------------*


*& Form build_handle


*&---------------------------------------------------------------------*
FORM build_handle.


* define a drag & Drop behaviour for the whole grid


CREATE OBJECT c_dragdropalv.


effect = cl_dragdrop=>move + cl_dragdrop=>copy.


CALL METHOD c_dragdropalv->add


EXPORTING


flavor = 'Line'


dragsrc = 'X'


droptarget = 'X'


effect = effect.


*getting the handle for drag and drop


CALL METHOD c_dragdropalv->get_handle


IMPORTING


handle = handle_alv.


ENDFORM. " build_handle


*&---------------------------------------------------------------------*


*& Form fetch_data


*&---------------------------------------------------------------------*
FORM fetch_data .


* select and display data from t016


SELECT brtxt brsch spras FROM t016t INTO CORRESPONDING FIELDS OF TABLE it_t016t


WHERE spras = 'EN'.


ENDFORM. " fetch_data


*&---------------------------------------------------------------------*


*& Form alv_report_layout


*&---------------------------------------------------------------------*
FORM alv_report_layout .


it_layout-grid_title = 'ALV Drag Drop'.


* provide handle to alv control to all rows for same drag & drop behaviour


it_layout-s_dragdrop-row_ddid = handle_alv.


ENDFORM. " alv_report_layout


*&---------------------------------------------------------------------*


*& Form alv_build_fieldcat


*&---------------------------------------------------------------------*
FORM alv_build_fieldcat .


DATA lv_fldcat TYPE lvc_s_fcat.


CLEAR lv_fldcat.


lv_fldcat-row_pos = '1'.


lv_fldcat-col_pos = '1'.


lv_fldcat-fieldname = 'BRSCH'.


lv_fldcat-tabname = 'IT_T016T'.


lv_fldcat-outputlen = 8.


lv_fldcat-scrtext_m = 'Industry'.


APPEND lv_fldcat TO it_fcat.


CLEAR lv_fldcat.


lv_fldcat-row_pos = '1'.


lv_fldcat-col_pos = '2'.


lv_fldcat-fieldname = 'BRTXT'.


lv_fldcat-tabname = 'IT_T016T'.


lv_fldcat-outputlen = 15.


lv_fldcat-scrtext_m = 'Description'.


APPEND lv_fldcat TO it_fcat.


CLEAR lv_fldcat.


ENDFORM. " alv_build_fieldcat


* PAI module of the screen created. In case we use an interactive ALV or


*for additional functionalities we can create OK codes


*and based on the user command we can do the coding.


*&---------------------------------------------------------------------*


*& Module USER_COMMAND_0600 INPUT


*&---------------------------------------------------------------------*

MODULE user_command_0600 INPUT.


ENDMODULE. " USER_COMMAND_0600 INPUT

FI: Important T-Codes in FI

1. CHART OF ACCOUNTS


0BY7 = Copy chart of accounts.

2.FISCAL YEAR VARIANTS

OB29=define fiscal year variants

OBB0=define posting periods variants

3.COMPANY CODE CONFIGURATION

OX02=company code creation

OBY6=define company code global parameters

EC01=copy company code

OY01=define countries

OB22=define parallel currencies

4.BUSSINESS AREAS

OX03=define business areas

GGB0=define validations

OB28=activate FI validations

5.FUNCTIONAL AREAS.

OKBD=define functional areas.

GGB1=define substitution

GS01=create sets

OBBZ=create functional area substitution

6.SALES AND USE TAX.

OBBG=assign country to tax calculation procedure

OBCO=specify structure for the jurisdriction code

OBCP=define tax jurisdiction codes

FTXP=define codes on tax and purchases

OBCL=define tax code for non-taxable transactions

GENERAL LEDGER

1. CHART OF ACCOUNTS.

OBD4=define account groups.

FSP3=chart of account display

OB53=define retained earnings account

OB15=define sample account rule types

FSK2=define data transfer rules

OB67=allocate company codes to rule types

FSM1=create sample accounts

FS01=create G/L accounts master records

2. COPYING AND TRANSPORTING G/L ACCOUNTS.

OB49=transport chart of accounts

OBY2=copy company codes

OBC4=define field status groups

3.POSITION KEY CONFIGURATION.

OB41=define position key configuration.

4. AUTOMATIC ACCOUNT DETERMINATION.

FBKP=configure auto act determination

OBY0=define tax accounts auto act assignement

OBYA=define cross company code

5.FINANCIAL STATEMENT VERSION.

OB58=define financial statement version

6.G/L DISPLAY CONFIGURATION.

O7Z3=define line layouts

OBVU=add special fields

O7S7=define sort variants

O7R1=define total variants

7.TOLERENCE GROUPS.

OBAY=define tolerance groups

OB57=allocate isers to tolerance groups

8.NUMBER RANGES AND DOCUMENT TYPES

FBN1=define FI number ranges

OBA7=define FI document types

OBU1=define document types and posting keys

O7E6=define fast entry screen

ACCOUNTS PAYABLE A/P

1. HOUSE BANKS AND ACCOUNTS

FI12=define house banks

FCH1=define check lots

FCHV=define void reason codes

2. PAYMENT PROGRAM CONFIGURATION

FBZP=payment program configuration

3. VENDOR MASTER DATA

OBD=3define vendor groups

XKN1=create number ranges for vendor account groups

OBAJ=assign number ranges to vendor groups

FK15=copy vendor master records

FK16=important vendor master records

ACCOUNTS RESIVEABLR A/R

1. TERMS OF PAYMENTS AND INTEREST CALCULATION

OBB8=define terms of payments

OB46=define interest calculation types

OB82=make the interest indicator avail to interest run program

OBAC=define reference interest rates

OB81=assign reference interest rates to interest indicators

OBV1=interest calculations account assignment

2. REASON CODES.

OBBE=define reason codes

OBCR=define reason codes conversion version

OBCS=map external reason codes to internal reason codes

3. DEFAULT ACCOUNT ASSIGNMENT

OBXL=assign G/L account to reason codes

OBX1=cash discount accounts

4. OVERALL A/R AND EMPLOYEE TOLERENCES

OBA3=define customer tolerance groups

5. CREDIT MANAGEMENT

OB45=define credit control areas

OB01=define credit risk categories

OB02=define credit representative groups

OB51=assign employee credit representitive groups

OB39=define days in arrears calculation

6. CUSTOMER MASTER RECORDS.

OBD2=define customer groups

ACCOUNTS RESIVEABLR A/R

1. TERMS OF PAYMENTS AND INTEREST CALCULATION

OBB8=define terms of payments

OB46=define interest calculation types

OB82=make the interest indicator avail to interest run program

OBAC=define reference interest rates

OB81=assign reference interest rates to interest indicators

OBV1=interest calculations account assignment

2. REASON CODES.

OBBE=define reason codes

OBCR=define reason codes conversion version

OBCS=map external reason codes to internal reason codes

3. DEFAULT ACCOUNT ASSIGNMENT

OBXL=assign G/L account to reason codes

OBX1=cash discount accounts

4. OVERALL A/R AND EMPLOYEE TOLERENCES

OBA3=define customer tolerance groups

5. CREDIT MANAGEMENT

OB45=define credit control areas

OB01=define credit risk categories

OB02=define credit representative groups

OB51=assign employee credit representitive groups

OB39=define days in arrears calculation

6. CUSTOMER MASTER RECORDS.

OBD2=define customer groups

CONTROLLING ENTERPRISE STRUCTURE

1. CONTROLLING AREAS

OX06=controlling area maintenance

OKKP=activate relative CO components within

Controlling area

KANK=maintain number ranges

2. OPERATING CONCERNS

KEP8=maintain operating concerns

OKEQ=version configuration screen

COST ELEMENT ACCOUNTIN

1. AUTOMATIC COST ELEMENT CREATION

OKB2= automatic cost element creation

OKB3= creation of the cost elements

Creation batch run session

SM35= execution of the cost element creation

batch input session

2. MANUAL COST ELEMENT CREATION

KA06= seacondry cost element creation

KA01= primary cost element creation

3. IMPUTED COSTS

KSAZ= manual overhead costing sheet

Creation for imputed cost calculation

4. RECONCILATION LEDGER

KALA= activate the reconciliation ledger

OKKP= assignment of the reconciliation

Table to the controlling area

OBYB= maintain the CO-FI automatic account

Assignment configuration

OK13= assignment to the reconciliation ledger

Document number range

COST CENTER ACCOUNTING

1. C.C.ACCOUNTING STANDARD HIERACHRY

KSH2= C.C.A standard hierachry maint creation.

2. CO AREAS P.C.A MAINT.

OKES= maint the PCA CO area settings

OK59= creating the dummy profit center

3. COST CENTER BASICS

OKA2= cost center category maint

OKEG= maint of the time based fields

KS01=creating/main the cost center M. records

4. ACTIVITY TYPES STATSTICAL KEY FIGURE

KK01=creation / maint of statistical key figs

KVA5= activity independent key figs

KV06= creation of an allocation cost elements

OKEI= time based field maint for activity types

OKL01= creation maint of activity types

5. ASSESMENT –DISTRIBUTION AND REPORTING

KCAV= maint of the allocation character for the sender /receiver

KA06= creation/maint of the assessment cost element

KSWI= creation of the cost center reporting

KSV1= creation of the cost center distribution

KSU1= creation of the cost center assessment

6. COST CENTER ACCOUNTING PLANNING

KP97= copy planning for cost center accounting

KPU1=creation of the plan revaluation

KP65= creation of the cost planning layout

KP34=planning profile creation

OKB9=maint of the CO automatic account

INTERNAL ORDER ACCOUNTING

1. ORDER SETTELEMENT CONFIGURATION

KA01= primary cost element

KA06= secondary cost elements

OK06= settlement structure

OKEV= origin source structure

OK07= settlement profile

SNUM= maintain number range assignment

2. ORDER PLANNING AND BUDGITING

OKEQ= maintain CO versions

OKOS= define planning profile for overall value planning

OKOB= define budget profile

OK14= maintain budget manager

OPTK= define exempt cost element for availability control

KANK= maint number range assignment

OK11= maint number range for planning/ budgeting objects

3. INTERNAL ORDER STATUS MANAGEMENT

KOT2= define order status management

KOV2= define transaction groups

OK02= define status profile

BS52= define authorization keys

4. ORDER TYPE DEVELOPMENT

KOT2= define order types

PROFITABILITY ANALYSIS

1. OPERATION CONCERN DEVELOPMENTS

KEAO= maintain operation concerns

2. CHARACHTERISTIC DERICATION

KE4K= maint derivation

KE04= create derivation structure

KE05= change derivation structure

KE06= display derivation structure

KES1=maintain CO-PA master data

KE07= create derivation rules

KE08= change derivation rules

3. ASSIGNING VALUES TO VALUE FIELDS

KE41=assign condition types to value fields

KE4M= assign SD quantity fields to value fields

KE4W= reset value fields

KEI1= define PA settlement structure

KEU1= create CO-PA cost center assessment

KEV2= change CO-PA cost center assessment

4. CO-PA PLANNING

OKEQ= maintain plan versions

KEF1= define planning revaluation

KE14= create planning layouts

KE15= change planning layouts

KE16= display planning layouts

KP34= define planning profiles

KE4D= define external data transfer structure

KE4Z= define assignment groups

KE4E= define field assignment

KEN2= define plan number ranges

5. ACTIVITY CO-PA

KEKK= assign controlling areas to operating concerns

KEN1= define number ranges to actual postings

6. CO-PA REPORTING

KER1= define report line structure

KE34= create forms

KE35= change forms

KE36= display forms

KE31= create CO-PA reports

KE32= change CO-PA repots

KE33= display CO-PA reports

7. CO-PA TRANSPORTS

KE3I= create CO-PA transports

PROFIT CENTER ACCOUNTING

1. BASIC SETTINGS AND MASTER DATA REVIEW

OKE5= maintain controlling area setups

1KE1=analyze settings

OKE4= update settings

OKE7= maintain time based fields

2. ASSIGNEMENT IN PCA

1KEB= perform fast assignment

OKEM= sales order sub creation

OKEL= sales order dist sub creation

1KE4= PCA assignment monitor

3. ACTUAL POSTING MAINTAINANCE

1KEF= set control parameters for actual postings

GCBX= define document types for actual postings

OKB9= maintain default account assignment

3KEH= maintain add. Bal. sheet and P&L acts.

2KET= activate balance carry format for CO-PA

4. PCA PLANNING

OKEQ= maintain controlling versions

GCBA= define documents types for plan postings

GS01= set maintenance for plan parameters creation

GP41= create plan parameters for plan postings

KE62= copy data to plan

INVESTEMENT MANAGEMENT

1. PROGRAMS TYPES, INVESTEMENT MEASURES

AND INVESTMENT PROFILE

OIT3= define program types

OITA= define investment profiles

2. I.M PLANNING AND BUDGETING PROFILES

OIP1= define investment management plan profile

OIB1= define IM budget profile

OIT5= assign actual value to budget category

OK11= define IM management plan profile