GETWA_NOT_ASSIGNED--method BUILD_TIMEID_DICTIONARY.--Short dump

[Former Member]

Team-

I'm running FXtrans..(BPC NW 7.5 sp4)

it is execute (Simulating) fine(UJKT) with no errors...but when i try to execute it is short dumping with the above message...

*RUN_PROGRAM CURR_CONVERSION

CATEGORY = %CATEGORY_SET%

RPTCURRENCY = %RPTCURRENCY_SET%

TIME = %TIME_SET%

RATEENTITYDIM= GLOBAL

OTHER = [COMPANY=%COMPANY_SET%]

*ENDRUN_PROGRAM

The question i have is.. would we manually input the TiMEID of time dimension or let the system build it...leave it blank?

and also any idea on where things might be falling apart.

Or do you think this error is unrelated to the FXTrans logic i'm trying to run

the Dump says..it is failing @ line 20

method BUILD_TIMEID_DICTIONARY.

data: ls_timeid_dict type s_timeid_dict

, ls_dimension type s_dimension

, lr_data type ref to data

.

field-SYMBOLS: <lt_dim> type STANDARD TABLE

, <ls_dim> type any

, <l_id> type any

, <l_tid> type any

.

clear dts_timeid_dict.

READ TABLE dt_dimension into ls_dimension with key name = d_dim_time.

ASSIGN ls_dimension-r_t_member->* to <lt_dim>.

CREATE DATA lr_data like line of <lt_dim>.

ASSIGN lr_data->* to <ls_dim>.

ASSIGN COMPONENT gc_s_field-id OF STRUCTURE <ls_dim> to <l_id>.

ASSIGN COMPONENT gc_s_field-timeid OF STRUCTURE <ls_dim> to <l_tid>.

LOOP AT <lt_dim> into <ls_dim>.

bold CHECK <l_id> is NOT INITIAL and <l_tid> is not INITIAL.bold

ls_timeid_dict-dim_id = <l_id>.

ls_timeid_dict-internal_timeid = <l_tid>.

insert ls_timeid_dict into table dts_timeid_dict.

ENDLOOP.

endmethod.

I have configured all the necessary properties as per the white paper..

thanks.

TD

Edited by: TylerD0 on Jan 26, 2011 5:18 PM

[former_member190501 · Accepted solution]

Hi,

We can maintain Time IDs manually as follows :(should be uinque number for each member)

Time              TimeID
2005.APR	20050400
2005.AUG	20050800
2005.DEC	20051200
2005.FEB	20050200
2005.JAN	20050100
2005.JUL	20050700
2005.JUN	20050600
2005.MAR	20050300
2005.MAY	20050500
2005.NOV	20051100
2005.OCT	20051000
2005.Q1	10000002
2005.Q2	10000003
2005.Q3	10000004
2005.Q4	10000005
2005.SEP	20050900
2005.TOTAL	10000001

hope it helps...

regards,

Raju

[Former Member · Accepted solution]

Thanks Raju-

there was a compliance issue with the ABAP and .Net patches which was causing the shortdumps..

thnks.