Hi Norman,
stop playing with AT NEW, AT LAST ... you will lost your mind (and your time).
if your fields look like that : FIELD1 FIELD2 FIELD3
1. AT NEW FIELD1 ==> You will not see the content of FIELD2 & FIELD3 (you will find stars)
2. AT NEW FIELD2, FIELD2 don't change, but FIELD1 change, you will stop ..
forget that statement 
regards
Fred
Hi,
there is a lot of discution about that, the keywords are : dynamic table & ALV grid
regards
Fred
Hi Leonard,
As per SAP note 1633399,
-Prevention of conflicts between current packages and the already installed Vistex packages. The installation will not be successful without creating and executing the following program in the installation system: ZBC_VISTEX_60D_CONFLICT_FIX. The program source code can be found at the very end of this note section in Appendix A.
You will need to transport or create this program in your other systems as these steps will need to be performed before installation each time. This program can be run any time before the installation begins.
A. Create Program: ZBC_VISTEX_60D_CONFLICT_FIX
B. Execute Program: ZBC_VISTEX_60D_CONFLICT_FIX
(no parameters to fill)
Hope this helps.
Regards,
Deepak Kori
Hi Harikrishna,
Try this code....
INITIALIZATION.
TYPES : BEGINOF TY_MARD,
MATNR TYPE MARD-MATNR,
WERKS TYPE MARD-WERKS,
LGORT TYPE MARD-LGORT,
ENDOF TY_MARD,
BEGINOF TY_MARA,
MATNR TYPE MARA-MATNR,
ERSDA TYPE MARA-ERSDA,
ERNAM TYPE MARA-ERNAM,
MTART TYPE MARA-MTART,
MATKL TYPE MARA-MATKL,
ENDOF TY_MARA,
BEGINOF TY_MAKT,
MATNR TYPE MAKT-MATNR,
SPRAS TYPE MAKT-SPRAS,
MAKTX TYPE MAKT-MAKTX,
ENDOF TY_MAKT,
BEGINOF TY_FINAL,
MATNR TYPE MARA-MATNR,
ERSDA TYPE MARA-ERSDA,
ERNAM TYPE MARA-ERNAM,
MTART TYPE MARA-MTART,
MATKL TYPE MARA-MATKL,
WERKS TYPE MARD-WERKS,
LGORT TYPE MARD-LGORT,
SPRAS TYPE MAKT-SPRAS,
MAKTX TYPE MAKT-MAKTX,
ENDOF TY_FINAL.
***** THE INITIALIZATION PART CREATING WORKAREA AND INTERNAL TABLE*****
DATA : W_MARD TYPE TY_MARD,
I_MARD TYPETABLEOF TY_MARD,
W_MARA TYPE TY_MARA,
I_MARA TYPETABLEOF TY_MARA,
W_MAKT TYPE TY_MAKT,
I_MAKT TYPETABLEOF TY_MAKT,
W_FINAL TYPE TY_FINAL,
I_FINAL TYPETABLEOF TY_FINAL.
**************************START-OF-SELECTION.**************************
START-OF-SELECTION.
*************************GET INPUT FROM USER***************************
PARAMETER : PLANT TYPE MARD-WERKS,
STLOC TYPE MARD-LGORT.
****SELECT DATA FROM DATABASE INTO INTERNAL TABLES*********************
**SELECT FROM MARD THE REQUIRED FIELDS FOR THE GIVEN INPUT*************
SELECT MATNR WERKS LGORT
FROM MARD
INTOTABLE I_MARD
WHERE WERKS = PLANT AND LGORT = STLOC.
*****CHECK IF RECORDS ARE FETCHED IF NO EXIT OUT OF THE PROGRAM********
IF SY-SUBRC <> 0.
WRITE'NO RECORDS'.
EXIT.
ELSE.
***IF RECORDS ARE FETCHED FROM FRIST TABLE*****************************
****FETCH RELATED RECORDS FROM NEXT TABLE******************************
SELECT MATNR ERSDA ERNAM MTART MATKL
FROM MARA
INTOTABLE I_MARA
FORALL ENTRIES IN I_MARD
WHERE MATNR = I_MARD-MATNR.
IF SY-SUBRC <> 0.
WRITE'NO MASTER DATA'.
STOP.
ELSE.
SELECT MATNR SPRAS MAKTX
FROM MAKT
INTOTABLE I_MAKT
FORALL ENTRIES IN I_MARA
WHERE MATNR = I_MARA-MATNR AND SPRAS = 'E'.
ENDIF.
ENDIF.
*****READ FROM INTERNAL TABLE FOR OUTPUT ******************************
LOOPAT I_MARA INTO W_MARA.
ATFIRST.
WRITE : SY-ULINE(100),
/1 SY-VLINE,
25'EXAMPLE INTERACTIVE REPORT',
100 SY-VLINE,
/ SY-ULINE(100),
/1 SY-VLINE,
2 'MATERIAL NUMBER' ,
20 SY-VLINE,
22'CREATION DATE',
40 SY-VLINE,
42'USER NAME',
60 SY-VLINE,
62'MATERIAL TYPE',
80 SY-VLINE,
82'MATERIAL GROUP',
100 SY-VLINE,
/ SY-ULINE(100).
ENDAT.
ONCHANGEOF W_MARA-MATNR.
READTABLE I_MARD INTO W_MARD WITHKEY MATNR = W_MARA-MATNR.
ENDON.
WRITE :/1 SY-VLINE,
2 W_MARA-MATNR ,
20 SY-VLINE,
22 W_MARA-ERSDA,
40 SY-VLINE,
42 W_MARA-ERNAM,
60 SY-VLINE,
62 W_MARA-MTART,
80 SY-VLINE,
82 W_MARA-MATKL,
100 SY-VLINE.
HIDE W_MARA-MATNR.
CLEAR W_MARA-MATNR.
WRITE: / SY-ULINE(100).
ENDLOOP.
*****************END-OF-SELECTION.*************************************
END-OF-SELECTION.
****MOVING VALUES IN TO FINAL INTERNAL TABLE **************************
LOOPAT I_MARA INTO W_MARA.
ONCHANGEOF W_MARA-MATNR.
READTABLE I_MAKT INTO W_MAKT WITHKEY MATNR = W_MARA-MATNR.
READTABLE I_MARD INTO W_MARD WITHKEY MATNR = W_MARA-MATNR.
ENDON.
W_FINAL-MATNR = W_MARA-MATNR.
W_FINAL-ERSDA = W_MARA-ERSDA.
W_FINAL-ERNAM = W_MARA-ERNAM.
W_FINAL-MTART = W_MARA-MTART.
W_FINAL-MATKL = W_MARA-MATKL.
W_FINAL-WERKS = W_MARD-WERKS.
W_FINAL-LGORT = W_MARD-LGORT.
W_FINAL-SPRAS = W_MAKT-SPRAS.
W_FINAL-MAKTX = W_MAKT-MAKTX.
APPEND W_FINAL TO I_FINAL.
ENDLOOP.
********AT LINE-SELECTION EVENT TRIGERING INTERACTIVE REPORTING.*******
ATLINE-SELECTION.
CASE SY-LSIND.
WHEN1.
**DISPLAY OUTPUT IN NEW SCREEN AT LINE SELECTION BY USER MOUSE CLICK **
WRITE: / W_MARA-MATNR COLOR2.
READTABLE I_FINAL INTO W_FINAL WITHKEY MATNR = W_MARA-MATNR SPRAS = 'EN'.
ULINE1(200).
WRITE : /1 SY-VLINE,
75'EXAMPLE INTERACTIVE REPORT',
200 SY-VLINE,
SY-ULINE(200),
/1 SY-VLINE,
2 'MATERIAL NUMBER' ,
20 SY-VLINE,
22'CREATION DATE',
40 SY-VLINE,
42'USER NAME',
60 SY-VLINE,
62'MATERIAL TYPE',
80 SY-VLINE,
82'MATERIAL GROUP',
100 SY-VLINE,
102'PLANT NUMBER',
120 SY-VLINE,
122'STORAG LOCATION',
140 SY-VLINE,
142'LANGUAGE',
160 SY-VLINE,
162'DESCRIPTION',
200 SY-VLINE,
/ SY-ULINE(200).
WRITE :/1 SY-VLINE,
2 W_FINAL-MATNR ,
20 SY-VLINE,
22 W_FINAL-ERSDA,
40 SY-VLINE,
42 W_FINAL-ERNAM,
60 SY-VLINE,
62 W_FINAL-MTART,
80 SY-VLINE,
82 W_FINAL-MATKL,
100 SY-VLINE,
102 W_FINAL-WERKS,
120 SY-VLINE,
122 W_FINAL-LGORT,
140 SY-VLINE,
142 W_FINAL-SPRAS,
160 SY-VLINE,
162 W_FINAL-MAKTX,
200 SY-VLINE,
/ SY-ULINE(200).
CLEAR W_MARA-MATNR.
ENDCASE.
Hi Andrew,
Yes you got it right.
Regards.
Rajen
Dear Experts
With Regards
Dinesh Kumar
Hi Doug,
When you plan to upgrade to EHP6, you need to first check whether your system is ready for EHP6 upgrade. Whether your database and OS is compatible for upgrade.
When you start the upgrade to EHP6 you may use solution manager for generating the stack file which will take care of all the pre-requisite patches from EHP1 - EHP5 as well as compatible kernel.
Hope this helps.
Regards,
Deepak Kori
Hi Malikarjun,
See this code, it will be helpful.
*Type pools declaration for ALV
TYPE-POOLS: SLIS. " ALV Global Types
*data declaration for dynamic internal table and alv
DATA: L_STRUCTURE TYPEREFTODATA,
L_TABLE TYPEREFTODATA,
STRUC_DESC TYPEREFTO CL_ABAP_STRUCTDESCR,
LT_LAYOUT TYPE SLIS_LAYOUT_ALV,
LS_LVC_FIELDCATALOGUE TYPE LVC_S_FCAT,
LT_LVC_FIELDCATALOGUE TYPE LVC_T_FCAT,
LS_FIELDCATALOGUE TYPE SLIS_FIELDCAT_ALV,
LT_FIELDCATALOGUE TYPE SLIS_T_FIELDCAT_ALV.
*field symbols declaration
FIELD-SYMBOLS :
<IT_TABLE> TYPESTANDARDTABLE,
<DYN_STR> TYPEANY,
<STR_COMP> TYPE ABAP_COMPDESCR.
*declarations for grid title
DATA : T1(30),
T2(10),
T3(50).
*selection screen declaration for table input
PARAMETERS : P_TABLE LIKE DD02L-TABNAME.
*initialization event
INITIALIZATION.
*start of selection event
START-OF-SELECTION.
*texts for grid title
T1 = 'Dynamic ALV display for table'.
T2 = P_TABLE.
CONCATENATE T1 T2 INTO T3 SEPARATEDBY SPACE.
* Dynamic creation of a structure
CREATEDATA L_STRUCTURE TYPE (P_TABLE).
ASSIGN L_STRUCTURE->* TO<DYN_STR>.
* Fields Structure
STRUC_DESC ?= CL_ABAP_TYPEDESCR=>DESCRIBE_BY_DATA( <DYN_STR> ).
LOOPAT STRUC_DESC->COMPONENTS ASSIGNING<STR_COMP>.
* Build Fieldcatalog
LS_LVC_FIELDCATALOGUE-FIELDNAME = <STR_COMP>-NAME.
LS_LVC_FIELDCATALOGUE-REF_TABLE = P_TABLE.
APPEND LS_LVC_FIELDCATALOGUE TO LT_LVC_FIELDCATALOGUE.
* Build Fieldcatalog
LS_FIELDCATALOGUE-FIELDNAME = <STR_COMP>-NAME.
LS_FIELDCATALOGUE-REF_TABNAME = P_TABLE.
APPEND LS_FIELDCATALOGUE TO LT_FIELDCATALOGUE.
ENDLOOP.
* Create internal table dynamic
CALLMETHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
EXPORTING
IT_FIELDCATALOG = LT_LVC_FIELDCATALOGUE
IMPORTING
EP_TABLE = L_TABLE.
ASSIGN L_TABLE->* TO<IT_TABLE>.
* Read data from the table selected.
SELECT * FROM (P_TABLE)
INTO CORRESPONDING FIELDSOFTABLE<IT_TABLE>.
* ALV Layout
LT_LAYOUT-ZEBRA = 'X'.
LT_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
LT_LAYOUT-WINDOW_TITLEBAR = T3.
*ALV output
CALLFUNCTION'REUSE_ALV_GRID_DISPLAY'
EXPORTING
IS_LAYOUT = LT_LAYOUT
IT_FIELDCAT = LT_FIELDCATALOGUE
TABLES
T_OUTTAB = <IT_TABLE>
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Regards,
Ramesh.T
Have you activated Stock Transfer Inspection Type (08) for that material??
If not, while doing 563 movement, you will get error message as Change the inspection stock of material 10100510250002 in QM only (Message no. QA495).
Check the Inspection lot in QA32 for 08 Inspection lot origin.
Hi,
There are 2 options of creating a inspection plan with reference
The first one means that you are just copying the header, operations and MIC etc..from the existing group (ABC). The group is used as reference and will not be copied to the new group (EFG)
The second option means that you are directly assigning the material to that group (ABC). So the system will not create a new group (EFG).
Regards,
Krishna Chandra
Hi Barthelemy,
As per Accounting Standard, if impairment is happened then the depreciation for the future periods will be based on the revalued figure. So if you do unplanned depreciation the gross block will not change and thereby future depreciation will be wrong.
For example Asset value is 100000 useful life 10 years, after two years Depreciable value is 80000 and now imapirment is happened and the revalue is 40000, impairment loss for current year is 40000 and depreciation for the balance 8 years is 5000. If you post unplanned depreciation for 40000 it takes care of current year requirement but depreciation for the next year will be 10000 which is wrong.
Hope it helps for Justin.
Dear Johannes,
Please check your framework page has been assigned to a portal desktop(Ajax or classic).
Regards,
Vinod
Run SE38 program UJA_INITIALIZE_BUI_PST
(I realize this is a super late reply but someone else may be looking)
Did you run the activate content program with a user that has SAP_ALL as it suggests?
Has the BW Source system been replicated/restored? Your screen implies a basic/ recently installed system just for BPC. Some basic config for BW may need to be done...can you manually create an infoobject?
The /CPMB/IOBJGEN folder is actually empty after ENVIRONMENTSHELL is generated in SP02, but there should be a /CPMB/IOBJGEN folder created with cubes and content.
-Dave Samuels
Dear All,
I am able to create leave in Fiori app,
There was some issue with trusted RFC.
Thanks to all.
Regards,
Vijay M
Dear SD Experts
When I'm doing a Order-Related billing, the Higher level item in the BOM is not appearing in the billing document.
Pls advise how to rectify this problem. Thanks in advance.
Please check this link and see if it helps:
http://www.rowsix.net/about/downloads/HR2006_Bankston_AcceleratePayday.pdf
Regards
Hi
fyi i have sneaky suspicion you opened this in the wrong type discussion...
Good luck
a
Dear Purna J.,
Please go through the following note and check whether it is helpful:
917950 - SAP NetWeaver 2004s: Setting Up BEx Web.
Also, please don´t use report RSPOR_SETUP for configuration check
between ABAP and Java for SAP NetWeaver 2004s.
The report has been replaced by the support desk tool.
Please have a look at note '937697 - Usage of
SAP NetWeaver BI Diagnostics & Support Desk Tool'
RSPOR_SETUP is obsolete in BI 7.x release and Supportdesk tool should
be used in 7.x release.
Please check the Support Desk Tool as per the note 937697 and if you find
any RED signals in the file systeminfo.txt included in the file
supportdesk.zip, please correct it as per the Solution mentioned
there and check if it helps.
Also keep a note of the following:
Please check the following link:
http://help.sap.com/saphelp_nwpi71
/helpdata/en/45/61d5aaa0546628e10000000a1553f6/frameset.htm
"With SAP NetWeaver 7.1, the Visual Administrator (VA) is replaced by
the SAP NetWeaver Administrator, that is, all relevant functions of
the VA are available in the SAP NetWeaver Administrator.
The VA is no longer delivered as of SAP NetWeaver 7.1. "
The interface is a little bit different now, but the installation
steps still follow the same logic as SAP NetWeaver 2004s.
You can use manual steps to set up integration as per note 917950.
Also, please note that Patch Level 0 is not supported for
BI Java components as per the following note:
1789842 - Patch Level 0 for BI Java Installation
Please do look at the note 1789842 for details.
Thanks & Regards,
Sapna
Hi Varun,
Do you use some sort of logon script for user logon ? Can you share the screenshot of user's screen ?
Regards,
SUJIT
