Runtime error in FMPLLI

[atif_farooq]

Hi :

         While configuring planning layout in FMPLLI i am facing a run time error

Runtime Errors	MESSAGE_TYPE_X
Date and Time	10.05.2012 10:34:56

Short text

The current application triggered a termination with a short dump.

What happened?

	The current application program detected a situation which really
	should not occur. Therefore, a termination with a short dump was
	triggered on purpose by the key word MESSAGE (type X).

Error analysis

	Short text of error message:
	Combination ledger-version not allowed
	Long text of error message:
	Technical information about the message:
	Message class....... "GLPL"
	Number.............. 710
	Variable 1.......... " "
	Variable 2.......... " "
	Variable 3.......... " "
	Variable 4.......... " "

Trigger Location of Runtime Error

	Program	SAPLKPP_FISL    Include                             LKPP_FISLU08    Row                                 66    Module type                         (FUNCTION)    Module Name                         G_PP_DIMENSIONS_FILL ource Code Extract ine  SourceCde   36   37   SET PARAMETER ID 'GLPL_TABNAME' FIELD i_tabname.     "note 214596   38 *   39 ************************************************************************   40 * T8PL01 : fill dimensions   41 ************************************************************************   42 *   43   REFRESH: itkpp0d.   44   CLEAR  : itkpp0d.   45 *   46   SELECT * FROM t8pl01   47        WHERE   48        appl = appl AND   49        subclass = subclass AND   50        tabname  = tabname.   51 MOVE-CORRESPONDING t8pl01 TO itkpp0d.   52 MOVE t8pl01-hierlevel TO itkpp0d-level.   53 APPEND itkpp0d.   54   ENDSELECT.   55   EXPORT itkpp0d TO MEMORY ID 'ITKPP0D'.   56 *
		57 * Check if WERT-dimension is available in the present set of 58 * dimenions. 59 * 60   READ TABLE itkpp0d WITH KEY dim_werte.           "Kein Binary Se 61   IF sy-subrc <> 0. 62     SELECT SINGLE * FROM t8pl00 WHERE 63                     appl     = appl     AND 64                     subclass = subclass AND 65                     tabname  = tabname. >>>     MESSAGE x710(glpl). 67   ENDIF. 68 69 ****************************************************************** 70 * set infos 71 ****************************************************************** 72   REFRESH : set_infos. 73   CLEAR   : set_infos. 74 * 75   LOOP AT itkpp0d. 76 * dimensions for sets 77     CASE itkpp0d-fieldname. 78       WHEN '&KKENNZAHL'. 79       WHEN 'RRCTY'. 80       WHEN 'RVERS'. 81       WHEN 'RYEAR'. 82       WHEN 'POPER'. 83       WHEN 'RBUKRS'. 84       WHEN 'BUKRS'. 85       WHEN 'KOKRS'.

I do not know where it is coming from .Please guide me to solve the issue.

Br

[iklovski · Accepted solution]

Hi Atif,

Try executing GLPLINSTALL transaction and check if the problem is solved.

Regards,

Eli

[atif_farooq]

Hi:

    Thankx a lot Eli. Issue resolved , one more question , i am creating commitment items hierarchy , should i keep the nodes same as per financial statement version defined in FSE1. What should be fund center hierarchy, should it match with cost center hierarchy . Please guide me.

Regards

[iklovski]

Not at all. It could be different. Anyway, commitment items are not always one-to-one replica of your G/L accounts. The same goes for fund centres...

[atif_farooq]

Hi:

   Thanks for you reply...I meant to say suppose i have a node in P& L Operating expenses , many sub nodes fall under it like Admin costs, Selling costs e.t.c .Each of these nodes have more 30 GL accounts attached to them. If i want to set a budget for selling expenses for a quarter then i should create one commitment item named Selling and assign it to the master data of all selling GL accounts. This is what i am trying to ask...In FMCIA if i give proposal fund center, what will be its impact ?

Regards

[iklovski]

Hi,

Indeed, if you have group of G/L expenses, that you want to assign to one commitment item, it's possbile. Keep in mind, that you can have posting on one commitment item, and budget control on another. For example, for your 30 G/Ls, you can still create different commitmet items (if it's useful for your reports), but the budget will be checked on 31st commitment item, which will serve only for this. You can manage this either via budget structure or by working with control objects in AVC.

As for 'proposal fund centre', it's a default fund centre, which will come with posting on this commitment item, if no derivation rule exists.

Regards,

Eli