Concert ABAP Logic in to BADIS

Hi Experts,
I need to extract BW data to a certain location in Application Serve for that i need to use INfo Spoke.
The data(Fields) i need to extract are
Week -Dept-YTD Sales Qty
The below is the logic written for YTD in ABAP(Variable Customer Exit),Could any one please ...please convert or use the same logic as in ABAP can write it in BADIS and also i need to add one more condition to the logic if the YTD sales Qty = 0(Zero) it should not be extracted.
Please convert the logic into BADIS...ask if u need any input parameters and declare any variables as X r Y so that i can modify it accordingly to my requirment
ABAP CODE
WHEN 'ZYTD'.
    CLEAR l_s_range.
    wdate = ww_date.
    weekno = '01'.
    SELECT SINGLE * FROM /bic/pycalday_w
         WHERE /bic/ycalday_w = wdate
         AND objvers = 'A'.
    thisweek = /bic/pycalday_w-/bic/ylwk_w.
    CONCATENATE thisweek(4) weekno INTO firstweek.
    l_s_range-low = firstweek.
    l_s_range-high = thisweek.
    l_s_range-sign = 'I'.
    l_s_range-opt = 'BT'.
    APPEND l_s_range TO e_t_range.
Thanks

Hi Vaidya
Select single will always select the first entry from the source which matched your where condition.
therefore you are not getting all the required data.
WHERE SALESITEM = rp-S_ITEMID AND CALWEEK =
ld_calweek AND PLPLANT EQ rp-S_SOURCE.
according to your logic
it will pick only one record e.g
201021 PI31 REDBACK 999999A 78,850
201021 PI31 FLXAAA 999999A 3154,000
item id = 999999A
plplant = PI31
in this case it will pick only the first record due to select single will fetch only one record (whichever it gets first and which meets your where condition)
You need to change your code logic and need to include more fileds which differentiates one record from another who have same valued as in your present where condition.
Thanks
Navneet

Similar Messages

ABAP Logic in Transformations-Start or Field Routine

Hi Experts,
As i am new to BW Please update me with the ABAP logic i need to implement in Transformation routine...and please advise me wether i can use that as a Start or field routine for a better performance.
Target DSO:
DSO A : Active Table:/BIC/AZDSOA
Fields (ZLOC,ZPAY_ID,ZNPAY_ID,ZOPAY_ID & ZCHG_DTE)
Source DSO
DSO B : Active Table:/BIC/BZDSOA
(ZLOC,ZPAY_ID)
DSO C : Active Table:/BIC/CZDSOA
Fields (ZLOC,ZPAY_ID,ZNPAY_ID & ZCHG_DTE(date))
While Transfering Data from DSO B-->DSO A
It should check DSO C for that ZLOC & ZPAY_ID
If ZCHG_DTE IS Blank then it should pick ZNPAY_ID for that ZLOC & ZPAY_ID from DSO C and update ZNPAY_ID in DSO A
if ZCHG_DTE IS not Blank then it should pick ZPAY_ID for that ZLOC & ZPAY_ID from DSO C and update ZOPAY_ID & ZCHG_DTE in DSO A
ZPAY_ID - Pay ID
ZNPAY_ID -New Pay ID
ZOPAY_ID -Old Pay ID
ZCHG_DTE -Change Date
ZLOC -Location.
Logic in words:
If Change date is Blank then it should pick new pay id for that Location & Pay Id and update NEw pay id field in DSO A
If Change date is not Blank then it should pick pay id for that Location & Pay Id and update old pay id field & change date in DSO A
Please update me with releavent code
Thanks

It must have something to do with your input variables - I ran this FM locally using my DOB and today's date and it worked fine.
make sure your input date types are in the correct format for the FM.

ABAP LOGICAL ERRORS

Expalin about ABAP Logical errors?
Help me sending appropriate link to understand more.
Moderator Message: Read the Rules of Engagement of this forum.
Edited by: kishan P on Dec 27, 2011 9:50 PM

Hi Vinay,
     You can't delete the ABAP Runtime errors. But you can catch the errors using catch exception Statement.
For Example,
Class-based exceptions are handled in the following control structure:
TRY.
...                       " TRY block (application coding)
CATCH cx_... cx_... ...
    ...                     " CATCH block (exception handler)
CATCH cx_... cx_... ...
    ...                     " CATCH block (exception handler)
CLEANUP.
    ...                     " CLEANUP block (cleanup context)
ENDTRY.
Try This Sample Code,
*--EXAMPLE FOR RUNTIME ERROR--
*DATA : VALUE1 TYPE I.
*VALUE1 = 1 / 0.        -
>>>>>> IT MAKES RUN TIME ERROR.
*WRITE : VALUE1.
*-EXAMPLE FOR HOW TO CATCH THE ARITHMETIC ERROR AT THE RUN TIME USING SUBRC----
DATA : VALUE1 TYPE I.
CATCH SYSTEM-EXCEPTIONS ARITHMETIC_ERRORS = 1.
VALUE1 = 1 / 0.
WRITE : VALUE1.
ENDCATCH.
IF SY-SUBRC = 1.
WRITE : ' IT MAKES ERROR'.
ELSE.
WRITE : VALUE1.
ENDIF.
Thanks,
Reward If Helpful.

Abap logic in Transformation End Routine not working correctly

Hi,
I wrote a piece of code but during testing I found out that it doesn't meet my requirement.
Requirement
I want to extract Standard_Cost for all sales items that meets the conditon. but at the moment only the first sales item in the DSO is showing.
I would like the following lines to display in the cube as well since the PLITEM is different.
201021     PI31     REDBACK     999999A     78,850
201021     PI31     FLXAAA     999999A     3154,000
DSO Table
CALWEEK     PLPLANT     PLITEM     SALESITEM     STRDCOST
201020     IN06     FLXAAA     557868B     6308,000
201021     FI24     FLXAAA     557868B     6308,000
201021     FI24     FLXAAA     999999B     0,000
201021     PI31     REDBACK     999999A     78,850
201021     PI31     FLXAAA     999999A     3154,000
InfoCube
SALESITEM PLPLANT       SALESDOC       STRDCOST
999999A     PI31     1100000911         78,850
Abap Logic
Data ld_calweek(6) TYPE n.
Getting the current week based on the system date.
CALL FUNCTION 'DATE_GET_WEEK'
        EXPORTING
          date         = sy-datum
        IMPORTING
          week         = ld_calweek
        EXCEPTIONS
          date_invalid = 1
          OTHERS       = 2.
Data rp TYPE tys_TG_1.
LOOP AT RESULT_PACKAGE INTO rp.
SELECT SINGLE STRDCOST FROM /N/ABC_EFG00 INTO
rp-S_STRDCOST
WHERE SALESITEM = rp-S_ITEMID AND CALWEEK =
ld_calweek AND PLPLANT EQ rp-S_SOURCE.
MODIFY RESULT_PACKAGE FROM rp.
Clear rp.
ENDLOOP.
How do I resolve this
thanks

Hi Vaidya
Select single will always select the first entry from the source which matched your where condition.
therefore you are not getting all the required data.
WHERE SALESITEM = rp-S_ITEMID AND CALWEEK =
ld_calweek AND PLPLANT EQ rp-S_SOURCE.
according to your logic
it will pick only one record e.g
201021 PI31 REDBACK 999999A 78,850
201021 PI31 FLXAAA 999999A 3154,000
item id = 999999A
plplant = PI31
in this case it will pick only the first record due to select single will fetch only one record (whichever it gets first and which meets your where condition)
You need to change your code logic and need to include more fileds which differentiates one record from another who have same valued as in your present where condition.
Thanks
Navneet

Screen goes black, shut the lid for a few minutes, open the lid the turn on chime comes on and the screen comes back to life. The computer itself has continued to update just no screen. After a few minutes goes black again. Is logic board going bad?

Screen goes black, shut the lid for a few minutes, open the lid the turn on chime comes on and the screen comes back to life. The computer itself has continued to update just no screen. After a few minutes goes black again. Is logic board going bad or graphic card issue? Trying to decide if computer is worth repairing as it was made in 2007.

It does sound like you might have a faulty video connection. See if you can make a Genius Bar appointment at your local Apple Store.

How do I know if the logic board is bad?

So the girlfriend dumped a slew of water on her 20 gig 4th gen photo. I've completely disassembled it and THOROUGHLY dried it out and all seems well from that perspective.
So here is what is happening:
- if I plug it into my PB it does not respond, nor does it start to charge
- if I do a "restart" (menu + center button) with it unplugged I get the exclamation point with the battery (low battery indicator)
- if I do a "restart" while it is plugged into the laptop, I get the lightning bolt with a battery (battery is too low to be recognized by computer)
- if I plug it into the regular AC charger, I get the same results
- if I try to "restart" again, the screen goes blank and then the lightening bolt comes back eventually
I opened it up again and took a volt meter and measured that the battery is still good; I get 3.8V I think or something like that from the red and black wires of the battery. Plus this thing is only like 8 months old, so I know the battery isn't bad.
This leads me to believe that the logic board is bad b/c that is what the battery plugs into. The screen must still be ok b/c it looks fine.
So does anybody have any ideas?

OK, so I have answered my own question. I ordered a logic board and put it in. So I know the logic board was bad.
However, now I'm pretty certain the hard drive is bad too as it just spins but won't do anything. I don't even get the folder with the exclamation point- just the big apple like it is booting up.
So I'm looking for a hard drive unless someone has a better idea???

Pl. provide ABAP logic

Can any body help me in providing the logic (ABAP logic-infopackage) for extracting data for 6th month considering sydatum.
Logic should be on Caday.
Example: If I am executing I/P today i.e. 13.01.2012, I should get the data of 01.06.2011 to 30.06.2011.
Please help.
Thanks in Advance.
Maddali VSKP

Hi,
As I am not core ABAPER, I tried below logic in the development. Logic is working fine. I am getting expected results.
DATA: l_cur_month(2) type n,
l_pre_month(2) type n,
l_cur_year(4) type n,
z_ppredat type DATS,
z_ppredat1 type INT1,
z_ppredat2(8) type n,
z_ppredat3(2) type n,
l_pre_year(4) type n.
data: l_idx like sy-tabix.
read table l_t_range with key
       fieldname = 'CALDAY'.
l_idx = sy-tabix.
l_cur_month = sy-datum+4(2).
l_cur_year = sy-datum(4).
l_pre_year = sy-datum(4).
if l_cur_month >= 7.
    l_pre_month = l_cur_month - 7.
endif.
if l_cur_month <= 6.
    l_pre_year = l_cur_year - 1.
    l_pre_month = 12 - ( 7 - l_cur_month ).
endif.
break-point.
concatenate l_pre_year l_pre_month '01'
into z_ppredat.
CALL FUNCTION '/OSP/GET_DAYS_IN_MONTH'
    EXPORTING
      IV_DATE       = z_ppredat
    IMPORTING
      EV_DAYS       = z_ppredat1 .
      z_ppredat3 = z_ppredat1.
concatenate l_pre_year l_pre_month z_ppredat3
into z_ppredat2.
concatenate "l_pre_year l_pre_month z_ppredat1" into z_ppredat2
l_t_range-sign = 'I'.
l_t_range-option = 'BT'.
l_t_range-low = z_ppredat.
l_t_range-high = z_ppredat2.
modify l_t_range index l_idx.
p_subrc = 0.
Request you to help me to validate the logic.
Thanks in Advance,
Maddali VSKP

Abap logic for lookup

Hi all,
I have a requirement where i need to lookup for a value in ods1 and based on that value i should update in ods2. can anyone help me with any abap logic --- is there one for look-up ? any sample code would be really helpful.
~rahul

the following method will give the ODS table name
CALL METHOD cl_rsd_odso=>get_tablnm
                 EXPORTING
                   i_odsobject   = <ods name>
                   i_tabt        = '0'
                 IMPORTING
                   e_tablnm      = ods_tab_name .
do a select from the ODS table to find whether infoobject A is there and get the value and based on that update ods2.
Regards
Raja

BI Content Datasources' ABAP Logic

Dear Friends,
Where and how can I find the BI Content Datasources' ABAP Logic. I am particularly looking for the code for 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM.
Thanks!

Hi,
Go to transaction RSO2 (Generic datasources) in ECC, put the datasource name in the transaction data field and click on display, then you will get a warning message at the bottom of the screen like below:
datasource 2lis_03_bf is extacted using function module mcex_bw_lo_api
likewise you can check for other datasources as well. Go to the function modules in SE37 and check the code there.
Regards,
Murali.

Need of ABAP logic for 0CDFY variable

Hi Everyone,
Iam trying to use the Current Fiscal Year--0CDFY variable in one of query.
I want to know the ABAP logic for that variable.
anyone please help me out
Thankyou
ARUN

This variable brings in the current fiscal year.
If you want to see code behind it than go to Tcode SE37
type in RSVAREXIT_0CDFY and click on disply

I havea 2007Mac Book Pro and a Genius told me that it is "vintage" and that the "logic board" is bad. He removed the hard drive and told me to buy a "sled" to retreive the data. Is it worth trying to fix it so that I don't have to buy a new one?

I have a 2007 Mac Book Pro and a Genius told me that it is "vintage" and that the "logic board" is bad and no longer supported. He removed the hard drive and told me to buy a "sled" to retreive the data. Is it worth trying to fix it so that I don't have to buy a new one? Where should I take it? Thanks.

djgornik,
if the Genius is correct and the logic board is bad, then replacing the logic board would be fairly expensive. What problems are you seeing with your MacBook Pro that caused you to visit the Genius in the first place? Whether it’s worth trying to fix it or not depends on your particular circumstances, such as your willingness to trade time for money in pursuing repair vs. replacement.

How to improve ABAP logics

Hi
How to Improve ABAP logics(Programming) in all areas.
I need guidence from you all. How to start to improve them.
Regards,
Maruti

Hi,
Following are the performance standards need to be following in writing ABAP programs:
1.      Unused/Dead code
Avoid leaving unused code in the program. Either comment out or delete the unused situation. Use program --> check --> extended program to check for the variables, which are not used statically.
2.      Subroutine Usage
For good modularization, the decision of whether or not to execute a subroutine should be made before the subroutine is called. For example:
This is better:
IF f1 NE 0.
PERFORM sub1.
ENDIF.
FORM sub1.
ENDFORM.
Than this:
PERFORM sub1.
FORM sub1.
IF f1 NE 0.
ENDIF.
ENDFORM.
3.      Usage of IF statements
When coding IF tests, nest the testing conditions so that the outer conditions are those which are most likely to fail. For logical expressions with AND , place the mostly likely false first and for the OR, place the mostly likely true first.
Example - nested IF's:
IF (least likely to be true).
    IF (less likely to be true).
     IF (most likely to be true).
     ENDIF.
    ENDIF.
   ENDIF.
Example - IF...ELSEIF...ENDIF :
IF (most likely to be true).
ELSEIF (less likely to be true).
ELSEIF (least likely to be true).
ENDIF.
Example - AND:
   IF (least likely to be true) AND
      (most likely to be true).
   ENDIF.
Example - OR:
        IF (most likely to be true) OR
      (least likely to be true).
4.      CASE vs. nested Ifs
When testing fields "equal to" something, one can use either the nested IF or the CASE statement. The CASE is better for two reasons. It is easier to read and after about five nested IFs the performance of the CASE is more efficient.
5.      MOVE statements
When records a and b have the exact same structure, it is more efficient to MOVE a TO b than to MOVE-CORRESPONDING a TO b.
MOVE BSEG TO *BSEG.
is better than
MOVE-CORRESPONDING BSEG TO *BSEG.
6.      SELECT and SELECT SINGLE
When using the SELECT statement, study the key and always provide as much of the left-most part of the key as possible. If the entire key can be qualified, code a SELECT SINGLE not just a SELECT.   If you are only interested in the first row or there is only one row to be returned, using SELECT SINGLE can increase performance by up to three times.
7.      Small internal tables vs. complete internal tables
In general it is better to minimize the number of fields declared in an internal table. While it may be convenient to declare an internal table using the LIKE command, in most cases, programs will not use all fields in the SAP standard table.
For example:
Instead of this:
data: t_mara like mara occurs 0 with header line.
Use this:
data: begin of t_mara occurs 0,
        matnr like mara-matnr,
        end of t_mara.
8.      Row-level processing and SELECT SINGLE
Similar to the processing of a SELECT-ENDSELECT loop, when calling multiple SELECT-SINGLE commands on a non-buffered table (check Data Dictionary -> Technical Info), you should do the following to improve performance:
o       Use the SELECT into <itab> to buffer the necessary rows in an internal table, then
o       sort the rows by the key fields, then
o       use a READ TABLE WITH KEY ... BINARY SEARCH in place of the SELECT SINGLE command. Note that this only make sense when the table you are buffering is not too large (this decision must be made on a case by case basis).
9.      READing single records of internal tables
When reading a single record in an internal table, the READ TABLE WITH KEY is not a direct READ. This means that if the data is not sorted according to the key, the system must sequentially read the table.   Therefore, you should:
o       SORT the table
o       use READ TABLE WITH KEY BINARY SEARCH for better performance.
10. SORTing internal tables
When SORTing internal tables, specify the fields to SORTed.
SORT ITAB BY FLD1 FLD2.
is more efficient than
SORT ITAB.
11. Number of entries in an internal table
To find out how many entries are in an internal table use DESCRIBE.
DESCRIBE TABLE ITAB LINES CNTLNS.
is more efficient than
LOOP AT ITAB.
CNTLNS = CNTLNS + 1.
ENDLOOP.
12. Performance diagnosis
To diagnose performance problems, it is recommended to use the SAP transaction SE30, ABAP/4 Runtime Analysis. The utility allows statistical analysis of transactions and programs.
13. Nested SELECTs versus table views
Since releASE 4.0, OPEN SQL allows both inner and outer table joins. A nested SELECT loop may be used to accomplish the same concept. However, the performance of nested SELECT loops is very poor in comparison to a join. Hence, to improve performance by a factor of 25x and reduce network load, you should either create a view in the data dictionary then use this view to select data, or code the select using a join.
14. If nested SELECTs must be used
As mentioned previously, performance can be dramatically improved by using views instead of nested SELECTs, however, if this is not possible, then the following example of using an internal table in a nested SELECT can also improve performance by a factor of 5x:
Use this:
form select_good.
data: t_vbak like vbak occurs 0 with header line.
data: t_vbap like vbap occurs 0 with header line.
select * from vbak into table t_vbak up to 200 rows.
select * from vbap
          for all entries in t_vbak
          where vbeln = t_vbak-vbeln.
endselect.
endform.
Instead of this:
form select_bad.
select * from vbak up to 200 rows.
select * from vbap where vbeln = vbak-vbeln.
endselect.
endselect.
endform.
Although using "SELECT...FOR ALL ENTRIES IN..." is generally very fast, you should be aware of the three pitfalls of using it:
Firstly, SAP automatically removes any duplicates from the rest of the retrieved records. Therefore, if you wish to ensure that no qualifying records are discarded, the field list of the inner SELECT must be designed to ensure the retrieved records will contain no duplicates (normally, this would mean including in the list of retrieved fields all of those fields that comprise that table's primary key).
Secondly, if you were able to code "SELECT ... FROM <database table> FOR ALL ENTRIES IN TABLE <itab>" and the internal table <itab> is empty, then all rows from <database table> will be retrieved.
Thirdly, if the internal table supplying the selection criteria (i.e. internal table <itab> in the example "...FOR ALL ENTRIES IN TABLE <itab> ") contains a large number of entries, performance degradation may occur.
15. SELECT * versus SELECTing individual fields
In general, use a SELECT statement specifying a list of fields instead of a SELECT * to reduce network traffic and improve performance. For tables with only a few fields the improvements may be minor, but many SAP tables contain more than 50 fields when the program needs only a few. In the latter case, the performace gains can be substantial. For example:
Use:
select vbeln auart vbtyp from table vbak
into (vbak-vbeln, vbak-auart, vbak-vbtyp)
where ...
Instead of using:
select * from vbak where ...
16. Avoid unnecessary statements
There are a few cases where one command is better than two. For example:
Use:
append <tab_wa> to <tab>.
Instead of:
<tab> = <tab_wa>.
append <tab> (modify <tab>).
And also, use:
if not <tab>[] is initial.
Instead of:
describe table <tab> lines <line_counter>.
if <line_counter> > 0.
17. Copying or appending internal tables
Use this:
<tab2>[] = <tab1>[]. (if <tab2> is empty)
Instead of this:
loop at <tab1>.
append <tab1> to <tab2>.
endloop.
However, if <tab2> is not empty and should not be overwritten, then use:
append lines of <tab1> [from index1] [to index2] to <tab2>.

How can I tell if the logic board is bad?

My mom has a flat-panel iMac (20") that has been refusing to boot since this past weekend. My sister and I tried every trick we could come up with to get it to boot, but the only thing that resulted in anything other than a blinking question mark was powering up while holding the eject button. This caused the computer to boot up from the external firewire hard drive. We were not able to get the disc tray to open, so we couldn't start up from the Hardware Test CD. I have two questions:
Is there a way to physically force the tray to open? (We've tried all the suggestions offered by Apple Support, to no avail, and the iMac has no hole for the old paper-clip trick.)
Is there a way to tell whether the hard drive is dead or the logic board is bad? We strongly suspect it's one or the other.
Flat-panel G4 iMac (20") Mac OS X (10.3.9)

Hello! You have one or two problems and both are likely related. The fact that the cd/dvd drive isn't responding indicates problems with it however it could be related to the hard drive problem. The fact that it will boot from another source indicates that the logic board is ok. If you like to tinker then you might want to consider buying a new computer and using the one with problems to learn more about working on one. I've never been a fan of all-in-one type computers because when component goes out you either in for a difficult job in repairing it yourself or you forfeit the value on the component (s) that are still good. That's why I personally think towers are better long term values. Sure they're not quite as "cool" as the iMac but I'd rather pay for computing power and long term useability. Tom

Have a old macbook 2006 with newer 500 GB seagate Momentus hard drive. I took mac to apple store and they said logic board is bad. Can I purcase another used macbook and install my old seagate hard drive and have saved my information? Thanks for any imput

Have a old macbook 2006 with newer 500 GB seagate Momentus hard drive. I did not backup any docs or pictures. The macbook crashed my fault. I took mac to apple store and they said logic board is bad. Can I purcase another used macbook and install my old seagate hard drive and have saved all my information? Thanks for any imput.

mgott55 wrote:
Can I install my used existing hard drive in a compatible macbook to save everything?
If you need to extract the drive's content you can remove it and install it in a $10 USB enclosure. It will be readable by any recent Mac.

ABAP Logical Database ADA

Hi All, I am quite familiar with Logical Databases but I need to understand the following.
1) I am using LDB ADA, but I want to use my own Selection Screen and not the default one that the LDB provides. I know I must put something in AT SELECTION-SCREEN but am unsure what.
2) Once I get the data, I want to store the data in an internal table - how do I go about doing this? If you can provide a code example that would be great.
Points for any relevant help.

Hi,
A logical database is a special ABAP/4 program which combines the contents of certain database tables. You can link a logical database to an ABAP/4 report program as an attribute. The logical database then supplies the report program with a set of hierarchically structured table lines which can be taken from different database tables.
Logical database structures
There are three defining entities in an SAP logical database. You must be clear on all three in order to create and use one.
Table structure: Your logical database includes data from specified tables in SAP. There is a hierarchy among these tables defined by their foreign keys (all known to SAP), and you are going to define a customized relationship between select tables. This structure is unique and must be defined and saved.
Data selection: You may not want or need every item in the referenced tables that contributes to your customized database. There is a selection screen that permits you to pick and choose.
Database access programming: Once youve defined your logical database, SAP will generate the access subroutines needed to pull the data in the way you want it pulled.
Creating your own logical database
Heres a step-by-step guide:
1) Call up transaction SLDB (or transaction SE36). The path you want is Tools | ABAP Workbench | Development | Programming Environment | Logical Databases. This screen is called Logical Database Builder.
2) Enter an appropriate name in the logical database name field. You have three options on this screen: Create, Display, and Change. Choose Create.
3) Youll be prompted for a short text description of your new logical database. Enter one. Youll then be prompted to specify a development class.
4) Specify a root node, or a parent table, as the basis of your logical database structure. You can now place subsequent tables under the root table as needed to assemble the data object you want. You can access this tree from this point forward, to add additional tables, by selecting that root node and following the path Edit | Node | Create. Once youve saved the structure you define in this step, the system will generate the programming necessary to access your logical database. The best part is you dont have to write a single line of code.
Noted point is we cant add any selection criteria thru our se38 program if you are attaching any LDB to program.Ist of no use.
If you want to change selection criteria to the existing LDB, you have to goto SE36 tcode and provide LDB name and choose "Change" mode by selecting "Selections" Radio button.
declaration of params is different compared to normal se38 program in some aspects.
PARAMETERS :p_curr LIKE bkpf-waers FOR TABLE bkpf OBLIGATORY.
this BKPF table should be one of the node in the "Structure" Radio button.
Thanks
Sivaparvathi
Please reward points if helpful.

Concert ABAP Logic in to BADIS

Similar Messages

Maybe you are looking for