Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8851

Re: Caluculate only on and after start month

$
0
0

Hi Gersh,

 

Here's the additional information:

 

(a)Test script using RUNLOGIC

 

*START_BADI RUNLOGIC_PH

 

 

//Data Set is defined by BADI Parameters, not by Application content

QUERY = OFF

//If set to OFF the script is executed in Simulation mode, i.e. it doesn't write back data

WRITE = ON

//Do not execute validation check of the underlying "called" script

VALIDATION = OFF

//No additional information will be in the output log (this can be set to ON in case of testing)

DEBUG = OFF

 

 

//Script to be called

LOGIC = SET_SUM.LGF

 

 

//This script can be located in a different AppSet and/or Application

//APPSET = <YOUR_APPSET>

//APP = <YOUR_APPLICATION>

 

 

//Defines Data Set to run the script on

 

 

//Dimension on which the Data Set will be split

CHANGED = TIME

 

 

*END_BADI

 

(b)Script as receiver (SET_SUM.LGF)

*XDIM_MEMBERSET CURRENCY_RPT = LC

*XDIM_MEMBERSET ACCOUNT_SAL = QTY

 

 

*WHEN U_PRODUCT_SAL.COUNT_KBN

*IS 1 //SUM_QTY

*REC(ACCOUNT_SAL = SUM_QTY, EXPRESSION = 0)

*ELSE

*REC(ACCOUNT_SAL = SUM_QTY, EXPRESSION = %VALUE%)

*ENDWHEN

 

 

*COMMIT

 

(c) When I ran script (a) on UJKT, Internal error occured:

WS000001.JPG

ST22 showed following log:

 

Category               ABAP Programming Error

Runtime Errors         UNCAUGHT_EXCEPTION

Except.                CX_SY_STRUCT_COMP_NAME

ABAP Program           CL_UJA_APPLICATION============CP

Application Component  EPM-BPC-NW-ADM

Date and Time          2014/09/21 13:34:32

 

 

 

 

 

 

Short Text

     An exception has occurred that was not caught.

 

 

 

 

 

 

What happened?

     Exception 'CX_SY_STRUCT_COMP_NAME' was raised, but it was not caught anywhere

      along the

     call hierarchy.

 

 

     Since exceptions represent error situations, and this error was not

     adequately responded to, ABAP program 'CL_ABAP_STRUCTDESCR===========CP' had

      to be terminated.

 

 

 

 

 

 

Error analysis

    An exception has occurred which is explained in more detail below. The

    exception is assigned to class 'CX_SY_STRUCT_COMP_NAME' and was not caught in

     procedure

    "IF_UJA_APPLICATION_DATA~CREATE_DATA_REF" "(METHOD)", nor was it propagated by

     a RAISING clause.

    Since the caller of the procedure could not have anticipated this

    exception, the current program was terminated.

    The reason for the exception is:

    Multiple Specification of the Name 'CATEGORY' as a Component Name (Component 6)

 

(d) SE19: What are these? Isn't the RUNLOGIC BADI already supported in  10.1NW?

 

WS000003.JPG

 

Best regards,

Masa


Viewing all articles
Browse latest Browse all 8851

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>