Regarding fields...

where could i find the following fields..
GROSS SALES, CREDIT RETURNS, GROSS WEIGHT FOR CURRENT YEAR .
with regards,
Badrinath

Try statistics : transaction MCSI
BR, Jacek

Similar Messages

Filter the Regarding field on Activity

Can we use addCustomFilter method on Regarding control on Activity form? I would like to filter the cases listed under Regarding field based on the role of logged in user.
Regards,
Yogesh

Please Refer below link :
http://blogs.msdn.com/b/shraddha_dhingra/archive/2013/12/21/addpresearch-and-addcustomfilter-in-crm-2013.aspx
http://mscrmshop.blogspot.in/2013/10/addcustomfilter-method-for-lookup.html

Regarding Field Missing in Dso Transformation

Hi
Folks
I am facing the issue like
In Datasouce to DSO transformation i can see the 55 objects in DSO table, and in DSO to Cube Transformation i can see 54 fields in DSO table, one field is missing , the object 0TXTSH(short discription) is mapped to field 0TXZ01in DS to DSO transformation.
so How can i get the field in DSO to Cube transformation.??
any settings have to be change???
waiting for yours Valuable answers
Regards
Anand

Hi,
Please identify the object and check it whether it is an attribute or a characteristic, if it is attribute only disable that option then check it.
Regards,
Srinivas

Re: URGENT: - REGARDING FIELD IN TABLES

HI
I am using transaction code MB5B and i am getting d data but i want to search d field among d tables where amount in currency field(dmbtr) present in bsim or bseg table ,but i want to have dat field which use to display d calculation of d field (dbmtr),plz hel me out its urgent... he or sh will be rewarded...

Hi,
Please verify these internal tables in the program.
DATA: BEGIN OF MAT_SUM OCCURS 100,
 DMBTR(09) type p decimals 3,
DATA: BEGIN OF MAT_SUM_BUK OCCURS 100,
 DMBTR(09) type p decimals 3,
DATA: BEGIN OF MAT_WEG OCCURS 100,
 DMBTR(09) type p decimals 3,
DATA: BEGIN OF MAT_WEG_BUK OCCURS 100,
 DMBTR(09) type p decimals 3,
types : begin of stype_bsim_lean,
 dmbtr like bsim-dmbtr,
TYPES : BEGIN OF STYPE_MSEG_LEAN,
 DMBTR LIKE MSEG-DMBTR,
DATA: BEGIN OF IMSWEG OCCURS 1000,
 DMBTR LIKE MSEG-DMBTR,
I think these are the tables used to sum up the dmbtr.
I think dmbtr is taken from bsim and mseg.Dmbtr id taken from bsim because of the adjustments in finance module..
Reward points if helpful,
Regards,
jinesh.

Re: URGENT: - REGARDING FIELD

HI
I am using transaction code MB5B and i am getting d data but i want to search d field among d tables where amount in currency field(dmbtr) present in bsim or bseg table ,but i want to have dat field which use to display d calculation of d field (dbmtr),plz hel me out its urgent... he or sh will be rewarded...

Hi,
Please verify these internal tables in the program.
DATA: BEGIN OF MAT_SUM OCCURS 100,
 DMBTR(09) type p decimals 3,
DATA: BEGIN OF MAT_SUM_BUK OCCURS 100,
 DMBTR(09) type p decimals 3,
DATA: BEGIN OF MAT_WEG OCCURS 100,
 DMBTR(09) type p decimals 3,
DATA: BEGIN OF MAT_WEG_BUK OCCURS 100,
 DMBTR(09) type p decimals 3,
types : begin of stype_bsim_lean,
 dmbtr like bsim-dmbtr,
TYPES : BEGIN OF STYPE_MSEG_LEAN,
 DMBTR LIKE MSEG-DMBTR,
DATA: BEGIN OF IMSWEG OCCURS 1000,
 DMBTR LIKE MSEG-DMBTR,
I think these are the tables used to sum up the dmbtr.
I think dmbtr is taken from bsim and mseg.Dmbtr id taken from bsim because of the adjustments in finance module..
Reward points if helpful,
Regards,
jinesh.

Regarding fields for Purchase order

can any body help what are the fields reqiured to develop a p.o report to display the change date,user name,time,p.o name and vendor code.

Hi
see the sample report for the fieldnames and other logic
all the PO info is there here.
*& Report ZMM_PO_REPORT
REPORT ZMM_PO_REPORT message-Id yb
 NO STANDARD PAGE HEADING
 LINE-COUNT 60(1)
 LINE-SIZE 230.
 D A T A B A S E T A B L E S D E C L A R A T I O N
TABLES: lfa1, " Vendor Master
 t161, " PO Doc Types
 t024, " Purchase Groups
 ekko. " PO Header
 T Y P E S D E C L A R A T I O N S
Purchase Orders Main Structure
TYPES: BEGIN OF s_po,
 ebeln TYPE ebeln, " PO No.
 ebelp TYPE ebelp, " PO Item
 bstyp TYPE bstyp, " PO Category
 bukrs TYPE bukrs, " Company Code
 bsart TYPE bbsrt, " PO Type
 lifnr TYPE lifnr, " Vendor No
 ekgrp TYPE bkgrp, " Purchase Group
 waers TYPE waers, " Currency
 bedat TYPE etbdt, " PO Date
 txz01 TYPE txz01, " Material Text
 werks TYPE ewerk, " Plant
 lgort TYPE lgort_d, " Storage Location
 matkl TYPE matkl, " Material Group
 menge TYPE bamng, " PR Quantity
 meins TYPE bamei, " UOM
 bprme TYPE bbprm, " Price Unit
 netpr TYPE netpr, " Net price
 peinh TYPE peinh, " Price Unit UOM
 pstyp TYPE pstyp, " Item Category
 knttp TYPE knttp, " Account Assignment Category
 END OF s_po.
Purchase Orders History Structure
TYPES: BEGIN OF s_account,
 ebeln TYPE ebeln, " PO No.
 ebelp TYPE ebelp, " PO Item
 gjahr TYPE mjahr, " Fiscal Year
 belnr TYPE mblnr, " PO Invoice No
 menge TYPE menge_d, " PR Quantity
 wrbtr TYPE wrbtr, " Price in Local Currency
 dmbtr TYPE dmbtr, " Price in Foreign Currency
 waers TYPE waers, " Currency
 shkzg TYPE shkzg, " Dr/Cr Indicator
 END OF s_account.
Purchase Orders History Structure(Item Sum)
TYPES: BEGIN OF s_inv_sum,
 ebeln TYPE ebeln, " PO No.
 ebelp TYPE ebelp, " PO Item
 menge TYPE menge_d, " PR Quantity
 wrbtr TYPE wrbtr, " Price in Foreign Currency
 waers TYPE waers, " Currency
 END OF s_inv_sum.
Purchase Orders Main Structure
TYPES: BEGIN OF s_rep,
 lifnr TYPE lifnr, " Vendor No
 ebeln TYPE ebeln, " PO No.
 ebelp TYPE ebelp, " PO Item
 bstyp TYPE bstyp, " PO Category
 bsart TYPE bbsrt, " PO Type
 ekgrp TYPE bkgrp, " Purchase Group
 waers TYPE waers, " Currency
 bedat TYPE etbdt, " PO Date
 txz01 TYPE txz01, " Material Text
 werks TYPE ewerk, " Plant
 lgort TYPE lgort_d, " Storage Location
 matkl TYPE matkl, " Material Group
 menge TYPE bamng, " PR Quantity
 meins TYPE bamei, " UOM
 bprme TYPE bbprm, " Price Unit
 netpr TYPE netpr, " Net price
 peinh TYPE peinh, " Price Unit UOM
 pstyp TYPE pstyp, " Item Category
 knttp TYPE knttp, " Account Assignment Category
 name1 TYPE name1, " Plant
 orewr TYPE netpr, " To be Invoiced Price
 curr TYPE waers, " Inv Doc Currency
 END OF s_rep.
 D A T A D E C L A R A T I O N S
DATA: gv_title1 TYPE sylisel, " Report title
 gv_dial. " Color flag
 C O N S T A N T S D E C L A R A T I O N S
CONSTANTS: c_x VALUE 'X', " Flag X
 c_h VALUE 'H', " Debit
 c_vgabe TYPE vgabe VALUE '2'. " Transaction Type
 I N T E R N A L T A B L E S D E C L A R A T I O N S
DATA: i_po TYPE STANDARD TABLE OF s_po WITH HEADER LINE,
 " Purchase Order
 i_inv TYPE STANDARD TABLE OF s_inv_sum WITH HEADER LINE,
 " PO Invoice Values
 i_rep TYPE STANDARD TABLE OF s_rep WITH HEADER LINE,
 " PO Invoice Values
 i_ekbe TYPE STANDARD TABLE OF s_account WITH HEADER LINE.
 " PO Invoice Values
 S E L E C T I O N S C R E E N *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_lifnr FOR lfa1-lifnr MATCHCODE OBJECT kred,
 s_ebeln FOR ekko-ebeln MATCHCODE OBJECT mekk,
 s_bsart FOR t161-bsart,
 s_ekgrp FOR t024-ekgrp,
 s_bedat FOR ekko-bedat.
SELECTION-SCREEN END OF BLOCK b1.
 I N I T I A L I Z A T I O N *
INITIALIZATION.
 A T S E L E C T I O N - S C R E E N *
AT SELECTION-SCREEN.
Validate the screen fields
PERFORM validate_screen.
 S T A R T - O F - S E L E C T I O N *
START-OF-SELECTION.
Fetch main data
PERFORM fetch_data.
 T O P - O F - P A G E *
TOP-OF-PAGE.
Header of the List
PERFORM header.
 E N D - O F - P A G E *
Footer
END-OF-PAGE.
ULINE.
 E N D - O F - S E L E C T I O N *
END-OF-SELECTION.
Display the Report Output data
PERFORM display_data.
At Line-Selection
AT LINE-SELECTION.
When double clicked on EBELN display the details of Purchase Doc
PERFORM line_sel.
*& Form validate_screen
Validation of Selection Screen fields
FORM validate_screen .
Validation of Vendor Number
CLEAR lfa1-lifnr.
IF NOT s_lifnr[] IS INITIAL.
 SELECT lifnr UP TO 1 ROWS
 INTO lfa1-lifnr
 FROM lfa1
 WHERE lifnr IN s_lifnr.
 ENDSELECT.
 IF sy-subrc <> 0.
 MESSAGE e000 WITH 'Invalid Vendor'(002).
 ENDIF.
ENDIF.
Validation of PO Number
CLEAR ekko-ebeln.
IF NOT s_ebeln[] IS INITIAL.
 SELECT ebeln UP TO 1 ROWS
 INTO ekko-ebeln
 FROM ekko
 WHERE ebeln IN s_ebeln.
 ENDSELECT.
 IF sy-subrc <> 0.
 MESSAGE e000 WITH 'Invalid Document Number'(003).
 ENDIF.
ENDIF.
Validation of PO Document Type
CLEAR t161-bsart.
IF NOT s_bsart[] IS INITIAL.
 SELECT bsart UP TO 1 ROWS
 INTO t161-bsart
 FROM t161
 WHERE bsart IN s_bsart.
 ENDSELECT.
 IF sy-subrc <> 0.
 MESSAGE e000 WITH 'Invalid Purchase Document Type'(004).
 ENDIF.
ENDIF.
Validation of Purchasing Group
CLEAR t024-ekgrp.
IF NOT s_ekgrp[] IS INITIAL.
 SELECT ekgrp UP TO 1 ROWS
 INTO t024-ekgrp
 FROM t024
 WHERE ekgrp IN s_ekgrp.
 ENDSELECT.
 IF sy-subrc <> 0.
 MESSAGE e000 WITH 'Invalid Purchasing Group'(005).
 ENDIF.
ENDIF.
ENDFORM. " validate_screen
*& Form fetch_data
Fetching the PO related data from Database Tables
FORM fetch_data .
CLEAR i_po.
REFRESH i_po.
SELECT a~ebeln " PO No.
 b~ebelp " PO Item
 a~bstyp " PO Category
 a~bukrs " Company Code
 a~bsart " PO Type
 a~lifnr " Vendor No
 a~ekgrp " Purchase Group
 a~waers " Currency
 a~bedat " PO Date
 b~txz01 " Material Text
 b~werks " Plant
 b~lgort " Storage Location
 b~matkl " Material Group
 b~menge " PR Quantity
 b~meins " UOM
 b~bprme " Price Unit
 b~netpr " Net price
 b~peinh " Price Unit UOM
 b~pstyp " Item Category
 b~knttp " Account Assignment Category
 INTO TABLE i_po
 FROM ekko AS a JOIN ekpo AS b
 ON a~ebeln = b~ebeln
 WHERE a~ebeln IN s_ebeln AND
 a~lifnr IN s_lifnr AND
 a~ekgrp IN s_ekgrp AND
 a~bsart IN s_bsart AND
 a~bedat IN s_bedat.
SORT i_po BY ebeln ebelp.
break-point.
IF NOT i_po[] IS INITIAL.
Fetch the PO History/Invoice Details from EKBE Table
 CLEAR i_ekbe.
 REFRESH i_ekbe.
 SELECT ebeln " PO No.
 ebelp " PO Item
 gjahr " Fiscal Year
 belnr " PO Invoice No
 menge " PR Quantity
 wrbtr " Price in Local Currency
 dmbtr " Price in Foreign Currency
 waers " Currency
 shkzg " Dr/Cr Indicator
 INTO TABLE i_ekbe
 FROM ekbe
 FOR ALL ENTRIES IN i_po
 WHERE ebeln = i_po-ebeln AND
 ebelp = i_po-ebelp AND
 vgabe = c_vgabe.
 IF sy-subrc = 0.
 SORT i_ekbe BY ebeln ebelp.
 LOOP AT i_ekbe.
 IF i_ekbe-shkzg = c_h.
 i_ekbe-wrbtr = i_ekbe-wrbtr * -1.
 ENDIF.
 MODIFY i_ekbe.
 ENDLOOP.
break-point.
Sum up the Item wise Invoice totals
 LOOP AT i_ekbe.
 AT END OF ebelp.
 READ TABLE i_ekbe INDEX sy-tabix.
 SUM.
 MOVE-CORRESPONDING i_ekbe TO i_inv.
 APPEND i_inv.
 ENDAT.
 CLEAR i_inv.
 ENDLOOP.
 SORT i_inv BY ebeln ebelp.
 break-point.
 ENDIF.
ENDIF.
Move the Vendor Name and Invoice Values to I_rep Internal Table
LOOP AT i_po.
 MOVE-CORRESPONDING i_po TO i_rep.
 CLEAR i_inv.
 READ TABLE i_inv WITH KEY ebeln = i_po-ebeln
 ebelp = i_po-ebelp.
 IF sy-subrc = 0.
 i_rep-orewr = ( i_po-menge - i_inv-menge ) * i_po-netpr.
 i_rep-curr = i_inv-waers.
 ELSE.
 i_rep-orewr = i_po-menge * i_po-netpr.
 i_rep-curr = i_po-waers.
 ENDIF.
break-point.
Get the Vendor Name
 CLEAR lfa1-name1.
 SELECT SINGLE name1 FROM lfa1 INTO lfa1-name1
 WHERE lifnr = i_po-lifnr.
 IF sy-subrc = 0.
 i_rep-name1 = lfa1-name1.
 ENDIF.
 APPEND i_rep.
 CLEAR i_rep.
 break-point.
ENDLOOP.
SORT i_rep BY lifnr ebeln ebelp.
DELETE i_rep WHERE orewr LE 0.
break-point.
ENDFORM. " fetch_data
*& Form display_data
Display the Report Output data
FORM display_data .
DATA: lv_flag, " New Flag
 lv_rec TYPE i. " No of Records
CLEAR lv_rec.
IF i_rep[] IS INITIAL.
 MESSAGE e000 WITH 'No Data found'(022).
ELSE.
 LOOP AT i_rep.
Toggle Color
 PERFORM toggle_color.
 IF lv_flag <> space.
 NEW-LINE.
 ENDIF.
At New Purchase Document
 AT NEW ebeln.
 WRITE:/1 sy-vline, 2(10) i_rep-ebeln INTENSIFIED OFF.
 lv_flag = c_x.
 lv_rec = lv_rec + 1.
 ENDAT.
 WRITE: 1 sy-vline,
 12 sy-vline,13(4) i_rep-bsart,
 17 sy-vline,18(10) i_rep-lifnr,
 28 sy-vline,29(35) i_rep-name1,
 64 sy-vline,65(4) i_rep-ekgrp,
 69 sy-vline,70(10) i_rep-bedat,
 80 sy-vline,81(5) i_rep-ebelp,
 86 sy-vline,87(40) i_rep-txz01,
 127 sy-vline,128(9) i_rep-matkl,
 137 sy-vline,138(1) i_rep-pstyp,
 139 sy-vline,140(1) i_rep-knttp,
 141 sy-vline,142(4) i_rep-werks,
 146 sy-vline,147(4) i_rep-lgort,
 151 sy-vline,152(13) i_rep-menge UNIT i_rep-meins,
 165 sy-vline,166(3) i_rep-meins,
 169 sy-vline,170(15) i_rep-netpr CURRENCY i_rep-waers,
 185 sy-vline,186(4) i_rep-waers,
 190 sy-vline,191(5) i_rep-peinh,
 196 sy-vline,197(4) i_rep-bprme,
 201 sy-vline,202(15) i_rep-orewr CURRENCY i_rep-curr,
 217 sy-vline,218(4) i_rep-curr,
 222 sy-vline,223(7) i_rep-bstyp centered,
 230 sy-vline.
 NEW-LINE.
 hide: i_rep-ebeln.
 ENDLOOP.
 ULINE.
 FORMAT COLOR OFF.
 WRITE : /2 'Total Number of Purchasing Documents:'(025) COLOR 3,
 lv_rec COLOR 3.
ENDIF.
ENDFORM. " display_data
*& Form header
Write the Report Header
FORM header .
FORMAT RESET.
header
WRITE:/1(230) 'LIST OF PURCHASE DOCUMENTS PER VENDOR'(006) CENTERED.
SKIP.
FORMAT COLOR COL_HEADING.
ULINE.
WRITE:/1 sy-vline,2(10) 'Pur.Doc.No'(006) CENTERED,
 12 sy-vline,13(4) 'Type'(007),
 17 sy-vline,18(10) 'Vendor'(008) CENTERED,
 28 sy-vline,29(35) 'Name'(009) CENTERED,
 64 sy-vline,65(4) 'PGrp'(010) CENTERED,
 69 sy-vline,70(10) 'Doc.Date'(012) CENTERED,
 80 sy-vline,81(5) 'Item'(011),
 86 sy-vline,87(40) 'Material Short Text'(024) CENTERED,
 127 sy-vline,128(9) 'Mat.Group'(013),
 137 sy-vline,138(1) 'I',
 139 sy-vline,140(1) 'A',
 141 sy-vline,142(4) 'Plnt'(014),
 146 sy-vline,147(4) 'SLoc'(015),
 151 sy-vline,152(13) 'Quantity'(016) CENTERED,
 165 sy-vline,166(3) 'UoM'(017),
 169 sy-vline,170(15) 'Net Value'(018) CENTERED,
 185 sy-vline,186(4) 'Curr'(019),
 190 sy-vline,191(5) 'Per'(020),
 196 sy-vline,197(4) 'Unit'(021),
 201 sy-vline,202(15) 'To be Invoiced'(023) CENTERED,
 217 sy-vline,218(4) 'Curr'(019),
 222 sy-vline,223(7) 'Doc.Cat'(026),
 230 sy-vline.
ULINE.
ENDFORM. " header
*& Form toggle_color
This routine alters the color of the records in the list
FORM toggle_color.
IF gv_dial = space.
 FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
 gv_dial = c_x.
ELSE.
 FORMAT COLOR 1 INTENSIFIED OFF.
 CLEAR gv_dial.
ENDIF.
ENDFORM. " toggle_color
*& Form LINE_SEL
*When double clicked on EBELN field display the details of Purchase Doc
FORM line_sel.
CASE sy-lsind.
 WHEN '1'.
 DATA: lv_field(20),
 lv_value(10),
 lv_bstyp like i_rep-bstyp.
 clear: lv_bstyp,lv_value, lv_field.
 GET CURSOR FIELD lv_field VALUE lv_value.
 IF lv_field = 'I_REP-EBELN'.
 IF NOT lv_value IS INITIAL.
 READ LINE sy-index FIELD VALUE i_rep-bstyp
 INTO lv_bstyp.
 READ CURRENT LINE FIELD VALUE i_rep-bstyp INTO lv_bstyp.
 if lv_bstyp = 'F'.
 SET PARAMETER ID 'BES' FIELD lv_value.
 CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
 elseif ( lv_bstyp = 'K' or lv_bstyp = 'L' ).
 SET PARAMETER ID 'VRT' FIELD lv_value.
 CALL TRANSACTION 'ME33' AND SKIP FIRST SCREEN.
 elseif lv_bstyp = 'A'.
 SET PARAMETER ID 'ANF' FIELD lv_value.
 CALL TRANSACTION 'ME43' AND SKIP FIRST SCREEN.
 endif.
 ENDIF.
 ENDIF.
ENDCASE.
ENDFORM. " line_sel
Regards
Anji

Query regarding fields in the material master

Hi Gurus,
We have a requirement where client wants to know the relevance of u201CBasic data textu201D and u201Cinspection textu201D tabs in material master (these appear when we click on additional data tab in material master) and also if we maintain text in these fields for a material where it will be reflected? for e.g where/in what transactions can we see these text appearing.
Please let me know the relevance of these two fields and where these can be reflected. It would be nice if you can also tell me the tables and fields for these two.
Regards,
Krishna Mohan

Hello
This text are maintained in tables STXH and STXL.
For fetch this texts use FM READ_TEXT with parameters:
ID = 'GRUN' - for Basic data text
ID = 'PRUE' - for inspection text
and for both texts
LANGUAGE = sy-langu
NAME = material number (with leading zeros)
OBJECT = 'MATERIAL'

Regarding field extracts

Hi to all,
What are the field extracts and conversion exit in ABAP.
Thanks..

Hi,
You are asking about the EXTRACT statement in ABAP.
it is used in the context of Field Groups: when the data is huge, internal tables are not useful
so we use field groups and use the commands like HEADER, EXTRACT, GET etc.
see the sample code:
REPORT demo_extract.
NODES: spfli, sflight.
FIELD-GROUPS: header, flight_info, flight_date.
START-OF-SELECTION.
INSERT: spfli-carrid spfli-connid sflight-fldate
            INTO header,
          spfli-cityfrom spfli-cityto
            INTO flight_info.
GET spfli.
EXTRACT flight_info.
GET sflight.
EXTRACT flight_date.
END-OF-SELECTION.
SORT STABLE.
LOOP.
    AT FIRST.
      WRITE / 'Flight list'.
      ULINE.
    ENDAT.
    AT flight_info WITH flight_date.
      WRITE: / spfli-carrid , spfli-connid, sflight-fldate,
               spfli-cityfrom, spfli-cityto.
    ENDAT.
    AT flight_date.
      WRITE: / spfli-carrid , spfli-connid, sflight-fldate.
    ENDAT.
    AT LAST.
      ULINE.
      WRITE: cnt(spfli-carrid), 'Airlines'.
      ULINE.
    ENDAT.
ENDLOOP.
Conversion exits are used to pass the values correctly to the fun modules, for ex:
Kunnr field value is '64564', but the fun module wont take as it is: you have to pass '0000064564', to convert this we use conversion exits for the fields.
reward if useful
regards,
ANJI

Regarding Field Symbols

Hi All,
 Im selecting values into an internal table say ' 0001...0010 ' and i have concatenated prefix with 'PA' to them (which will be PA0001 ... PA0010 )
and appened in the internal table.
Now based on this values in the internal table say PA0001...PA0010 (which are table names) I have to select an entry say PERNR into another internal table.
Please help me to solve this using Field symbols Points will be regarded fully if found usefull.
Thanks,
Sarath.C

Hi Sarath,
if your tables PA0001 ....PA0010 have different structures, use something like:
DATA: ref_itab TYPE REF TO data.
FIELD-SYMBOLS: <fs_itab> TYPE ANY TABLE.
 DATA: BEGIN OF itab OCCURS 0,
 tabname TYPE tabname,
 ref_itab TYPE REF TO data.
DATA: END OF itab.
 FIELD-SYMBOLS: <fs_wa_itab> LIKE itab.
 DATA: wa_itab LIKE itab.
 CLEAR wa_itab.
MOVE 'ZKG00001' TO wa_itab-tabname.
APPEND wa_itab TO itab.
 CLEAR wa_itab.
MOVE 'ZKGPERIOD' TO wa_itab-tabname.
APPEND wa_itab TO itab.
 LOOP AT itab ASSIGNING <fs_wa_itab>.
CLEAR ref_itab.
 CREATE DATA ref_itab TYPE STANDARD TABLE OF (<fs_wa_itab>-tabname)
 WITH DEFAULT KEY.
<fs_wa_itab>-ref_itab = ref_itab.
ASSIGN ref_itab->* TO <fs_itab>.
 SELECT * FROM (<fs_wa_itab>-tabname) INTO TABLE <fs_itab>
 UP TO 10 ROWS.
ENDLOOP.
Kind regards
Henner

Queries regarding fields in Bid invitation

Hi,
I am in bid invitation screen -> Header data -> Documents section. If I attach a document I can see the following buttons.
check-out, check-in, check in new version, terminate check-out, edit description, delete, activate.
what purpose does the check-in, check-out & check in new version serve ?? I am bit confused on this...please guide.Also is there any link where I can get info about these fields ?
Regards,
Rajeshree

Hi Rajeshree,
This is a new doc management feature of SRM 5.0.
You can now create versions, lock the document for local modification (check-in/out).
This requires an applet.
You can de-activate it in SPRO.
Rgds
Christophe
PS: please reward points for helpful answers

Regarding field likp-anzpk updation

hi experts,
in my requirement i have to update the field (likp-anzpk) in vl02n transaction with total no packages based on the total line
items weight , but i found in some of the threads , that the field will be updated automatically when the packaging functionality
is once activated ,
i asked my client abt it ,they said that they r not activated packaging functionality.
is there any other way to update this field , i tried writing code in badi LE_SHP_DELIVERY_PROC and in method
IF_EX_LE_SHP_DELIVERY_PROC~SAVE_DOCUMENT_PREPARE , but it is useless
pls suggest me on this if there is any other way.\
thanks.

hi break point,
my clients actual requirement was , he creates stock transfer advice (STA) against the PO using the transaction
VL10B , the moment STA was created ,he was asking for the field likp-anzpk has to be updated when he go to
display mode to VL02N, when he double clicks on the generated STA no from VL10B.
i have tried in the method BEFORE SAVE AND PUBLISH DOCUMENT,it was executing when the user pressed SAVE
button in VL02N ,
can any body pls suggest which method i have to use to update the field likp-anzpk immediately when the STA was created
from VL10B before the display of the sta in vl02n.
let me know that any USER-EXIT or BADI exists to fullfill this req
regards\
maheshlap

Regarding Field Lengths

Hi All,
Suppose My Scenario is to Send the Vendor Details From SAP ECC To File.
Here In ECC we have the Fields with Field Lengths with 20 Char , But in the File We have the Fields with Field Lengths with 10 Char.
So in this case Is the Data will be Posted to File Successfully OR Any Error will Come
How To do this in Mapping Time
Regards
Vamsi

Hey,
Don't complicate.
Just in FCC set NameA.fixedLengthTooShortHandling
= Ignore / Cut. Depending on the requirement.
Ignore:Ignore means that the system applies the value completely, regardless of it being too long.
Cut:Cut means that a value is shortened to the maximum permitted length
Further reference.
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Cheers,
*RAJ*

Regarding fields on FIAR

hi frnds
Im working on FIAR,I have got a report and im told to work on fields.I will list the fields can someone
help me in finding the extractor for the fields
Beg Balance
New
Paid
Write Off
All Report
End Balance
Diff Between End/All
% Paid
Reg NSF Accts
RTCHK
Further Action
Fraud Accts
Total Accts
YTD Avg
these are the fields.How to find the extractor for it.Please help me out
thank you

Hi sivaram,
Check with a FI-AR analyst. Those are company specific fields, not general fields. Check help.sap.com for FI-AR datasources and also try best practices.
Hope this helps.
Regards,
Diego

Regarding field VBUP-PKSTA (Packing status of an item)

Helo All,
Can anybody tell me from where does the field PKSTA in table VBUP gets populated?
This is regarding packing status of item.
Thanks in advance.

Thanks for your reply.
But when delivery is created, the field is populated from VBUP-PKSTA (Packing status).
My question is how entry is made in this table VBUP?
Is it when we create any master data or during any config?
Thanks.

REGARDING FIELDS & tables

Hi Experts ,
Please tell me how to get some field from cluster table like" KONV with transparent table like "VBAP, VBAK" IN same internal table.
thanks & regards,
Ashish

Hi,
Welcome to SDN.
Try doing this ....
1). Goto se12 and display the table BSEG
2). Click on the Delivery & Maintenanace tab
3). Double click on the Pool/Cluster field
4). On the next screen do a where used list
You will find all the related tables.
Regards

Regarding fields...

Similar Messages

Maybe you are looking for