We have defined a query in BW in CO-OM-CCA area. This query has the rows defined with cost element InfoObject (0COSTELMNT), restricted with a hierarchy. As time characteristic, it has fiscal year / period InfoObject (0FISCPER).
We want to jump from this query to transaction S_ALR_87013611 (Cost centers: Actual / Plan / Variance). We have defined it in transaction RSBBS (with InfoSource 0CO_OM_CCA_9), and we are using the user-exists EXIT_SAPLRSBBS_001 and EXIT_SAPLRSBBS_002, to populate parameters and select options in a R/3 selection screen (report of R/3). The problem is that when the fields are mapped to R/3 some of them are not populated in the selection screen. There are two types of problems:
The first, for example, when we select a node of the hierarchy, the mapping between this value and R/3 field (Cost element group - RKSB1-KAGRU) is correct. However, when we select an individual value (a unique cost elemenT), the user-exist is not able to map it correctly to R/3 field (Cost element - COSP-KSTAR). The first field is a parameter, and the second one is a select-option.
The second: the query has fiscal year period as time characteristic. However, R/3 report has three parameters: fiscal year, from period and to period. We have tried to separate the fiscal year period (for example, 012.2001) in three different fields: fiscal year (in example, 2001), from period (in example, 12) and to period (in example, 12). Besides, but the system always gives the same value (fiscal year = 2003, from period = 1 and to period = 12).
We want to jump from this query to transaction S_ALR_87013611 (Cost centers: Actual / Plan / Variance). We have defined it in transaction RSBBS (with InfoSource 0CO_OM_CCA_9), and we are using the user-exists EXIT_SAPLRSBBS_001 and EXIT_SAPLRSBBS_002, to populate parameters and select options in a R/3 selection screen (report of R/3). The problem is that when the fields are mapped to R/3 some of them are not populated in the selection screen. There are two types of problems:
The first, for example, when we select a node of the hierarchy, the mapping between this value and R/3 field (Cost element group - RKSB1-KAGRU) is correct. However, when we select an individual value (a unique cost elemenT), the user-exist is not able to map it correctly to R/3 field (Cost element - COSP-KSTAR). The first field is a parameter, and the second one is a select-option.
The second: the query has fiscal year period as time characteristic. However, R/3 report has three parameters: fiscal year, from period and to period. We have tried to separate the fiscal year period (for example, 012.2001) in three different fields: fiscal year (in example, 2001), from period (in example, 12) and to period (in example, 12). Besides, but the system always gives the same value (fiscal year = 2003, from period = 1 and to period = 12).