Delivery Vs Invoice Data Source !

Question

Hi
We are facing an issue with our On time report. We have to get the nr of days between two dates which is Est Goods Movement Date - Act goods movement Date
If it gives 0 which is Ontime   ,  <0 then its an Early  , > 0 then Late...
I have both the dates available in my delivery data source 2LIS_12_VCITM  and the Invoice amount I want to show from invoice data source 2LIS_13_VDITM . I dont see the dates in my 2LIS_13_VDITM.
We have separate cubes for deliveries and Invoices and deliveris only have qty and invoice has value....these both cubes are combined in a multi cube. Can anybody give me an idea of how to get the dates in my Invoice cube ?
Do I need to create a DSO to merge delivery and Invoice data ?
without the date fields I cant get my Ontime report and with dates from Delivery data source I cant show the invoice amount...
Please advice...

Answer 1

Hi Sam,
Follow the below precedure for implementing virtual characteristics:
BW: Virtual characteristics and key figures in Reporting
Enhancement: RSR00002
With this enhancement, you can define and evaluate user-specific virtual
characteristics and key figures.
Components
The components for the enhancement are the function modules
EXIT_SAPMRSRU_001 and EXIT_SAPMRSRU_999.
Using enhancement 001
You must firstly define the characteristics, or key figures within the
InfoCube.
You deposit the customer-specific code in include reports. The include
ZXRSRU02 is intended for function module EXIT_SAPMRSRU_001. In this
include, the fields still to be processed must be listed. The name of a
characteristic in field CHANM and of the processing mode in the field
MODE is located in the table E_T_CHANM. Characteristics can either be
processed reading (constant RRKE_C_MODE-READ) or writing (constant
RRKE_C_MODE-NO_SELECTION). Table E_T_KYFNM contains the name for the key
figures to be processed.
In the include ZXRSRTOP, a global variable must be created for each
InfoCube for each characteristic. Field information for the structure to
be changed is stored in these variables. The name of the variables is
formed from the prefix G_POS_, the name of the InfoCube,_ and the name
of the InfoObject all together.
In the include ZXRSRZZZ, a form (routine) must be created for every
InfoCube. The name of this form must be made up of USER_ and the
technical name of the InfoCube. The specific code for the virtual
characteristics, or key figures, for this InfoCube is stored in this
form. The individuals fields of the structure C_S_DATA to be changed are
accessed using field symbols.
You should note that the data records transferred can be on a different
aggregation level depending on read procedure and drilldown. Moreover,
compound information is not automatically changed with compounded
characteristics after changing a higher-level characterisic. In
addition, the compound characteristic must also be defined in the mode
RRKE_C_MODE-NO_SELECTION.
Furthermore, the fiscal year (0FISCYEAR), the fiscal year period
(0FISCPER) and the fiscal year variant (0FISCVARNT) cannot be read or
changed in the enhancement.
Using enhancement 999
Enhancement 999 may not be changed. Calling up serves to update
information via the structure C_S_DATA. This functionality is completely
taken over by form USER_INIT_GLOBALS.
Example
InfoCube DEMOCUBE has the characteristic PRODUCT PRICE_TP and the key
figure ACT_PRICE and QUANTITY. In the enhancement, the product from the
current price for PRODUCT and the key figure QUANTITY should be
determined. If successful, the characteristic PRICE_TP should contain
the characteristic value '1'.
The include ZXRSRU02: Definition
***INCLUDE ZXRSRU02
DATA: L_S_CHANM TYPE RRKE_S_CHANM.
CASE I_S_RKB1D-INFOCUBE.
WHEN 'DEMOCUBE'.
L_S_CHANM-CHANM = 'PRODUCT'.
L_S_CHANM-MODE = RRKE_C_MODE-READ.
APPEND L_S_CHANM TO E_T_CHANM.
L_S_CHANM-CHANM = 'PRICE_TP'.
L_S_CHANM-MODE = RRKE_C_MODE-NO_SELETION.
APPEND L_S_CHANM TO E_T_CHANM.
APPEND 'ACT_PRICE' TO E_T_KYFNM.
APPEND 'QUANTITY' TO E_T_KYFNM.
ENDCASE.
The include ZXRSRTOP: global data
***INCLUDE ZXRSRTOP .
DATA: G_POS_DEMOCUBE_PRODUCT TYPE I.
DATA: G_POS_DEMOCUBE_PRICE_TP TYPE I.
DATA: G_POS_DEMOCUBE_ACT_PRICE TYPE I.
DATA: G_POS_DEMOCUBE_QUANTITY TYPE I.
Das Include ZXRSRZZZ: Changing the data
***INCLUDE ZXRSRZZZ .
FORM USER_DEMOCUBE USING I_S_RKB1D TYPE RSR_S_RKB1D
CHANGING C_S_DATA TYPE ANY.
FIELD-SYMBOLS <L_PRODUCT>.
FIELD-SYMBOLS <L_PRICE_TP>.
FIELD-SYMBOLS <L_ACT_PRICE>.
FIELD-SYMBOLS <L_QUANTITY>.
ASSIGN COMPONENT G_POS_DEMOCUBE_PRODUCT
OF STRUCTURE C_S_DATA TO <L_PRODUCT>.
ASSIGN COMPONENT G_POS_DEMOCUBE_PRICE_TP
OF STRUCTURE C_S_DATA TO <L_PRICE_TP>.
ASSIGN COMPONENT G_POS_DEMOCUBE_ACT_PRICE
OF STRUCTURE C_S_DATA TO <L_ACT_PRICE>.
ASSIGN COMPONENT G_POS_DEMOCUBE_QUANTITY
OF STRUCTURE C_S_DATA TO <L_QUANTITY>.
Routine to get the price
PERFORM GET_PRICE USING <L_PRODUCT>
CHANGING <L_ACT_PRICE>.
IF <L_ACT_PRICE> GT 0.
<L_ACT_PRICE> = <L_ACT_PRICE> * <L_QUANTITY>.
<L_PRICE_TP> = '1'.
ENDIF.
ENDFORM.
use the below link for understaning in detail:
Virtual Characteristic
DONT FORGET TO ASSING POINTS IF IT IS HELPFUL.
Regards,
S P.