Removing extra view or information from universal work list
Recently my user asked me about the throwing the extra i-view inside a page.
After further investigation it seems like it is not a i-view.
But more like a debug view (in my own understanding)
In the universal Work list it shows extra view like
In the UWL inbox there are
- Logged-On User Information
- Current View Information
- Current Navigation Information
- Current Item Information
In order to hide the debug mode.
Goto
system administration
----> system configuration
----->Universal Worklist & Workflow
---------->Universal Worklist - Administration
------------->Optional Universal Worklist Service Configuration (expand the tray)
Make sure the setting
Display Support Information = false
After further investigation it seems like it is not a i-view.
But more like a debug view (in my own understanding)
In the universal Work list it shows extra view like
In the UWL inbox there are
- Logged-On User Information
- Current View Information
- Current Navigation Information
- Current Item Information
In order to hide the debug mode.
Goto
system administration
----> system configuration
----->Universal Worklist & Workflow
---------->Universal Worklist - Administration
------------->Optional Universal Worklist Service Configuration (expand the tray)
Make sure the setting
Display Support Information = false
Portal HelpLink How to Change
Go to
portal content ->
Portal users ->
Default framework page,
right click and choose edit.
In the editor on the right,
- select masthead iView and choose properties .
- You will find "URL of Help Link"
- You can Key in the new URL for the Help
Useful URL
Wanna compile a section url for me (dummy)
-----------------------------------------------
2009 Aug 13 - http://www.sapabapnotes.blogspot.com/ - link provided by mawarni
2009 Aug 13 - http://www.sapbasisnotes.blogspot.com/ - link provided by mawarni
-----------------------------------------------
2009 Aug 13 - http://www.sapabapnotes.blogspot.com/ - link provided by mawarni
2009 Aug 13 - http://www.sapbasisnotes.blogspot.com/ - link provided by mawarni
2008 Jun 25 How to check position ID
Exercise
1. Tcode (SE16) -> HRP1001 [ObjectType(P),ObjectID(00064744).RSIGN(B),RELAT(008)] Execute
2. Copy the SOBID(51650769)
3. Tcode (OPP01) -> [OBJECTID(51650769)] -> Select POSITION -> Click OverView(button) -> OverView Shift08
4. Check the relationship (z02 - Bussiness Structure (new)) OR (rel ) ( 003 - Legal Structure (old)) There is a OR will have to confirm with user
5. Choose the ORG ID Z02 -> 516 507 68 (answer!)
1. Tcode (SE16) -> HRP1001 [ObjectType(P),ObjectID(00064744).RSIGN(B),RELAT(008)] Execute
2. Copy the SOBID(51650769)
3. Tcode (OPP01) -> [OBJECTID(51650769)] -> Select POSITION -> Click OverView(button) -> OverView Shift08
4. Check the relationship (z02 - Bussiness Structure (new)) OR (rel ) ( 003 - Legal Structure (old)) There is a OR will have to confirm with user
5. Choose the ORG ID Z02 -> 516 507 68 (answer!)
2008 June 25 How to Create BAdi
BAdi For current development
Adviced by Pak Nanang,Wai Meng and Radi.
TCode(TransactionCode)
SE18 - DisplayBAdi
SE19 - CreateBAdi
Deduction is within a standard SAP program there are places we can customized to our own requirements. The places are called user exit.
For my current limited knowledge:-
1. BAdi TCode - se19,se18
2. Dynamic Action
Been guided to do BAdi in two different ways.
1. SE19 -> Create Implementation -> Choose classic BAdi(Select from the list z* find) -> Press Create Impl. -> Choose the new name + The App Name. Then Change and Save the method you modify added.
2. OOAM -> Goto -> Enhancement (this is the place where you can find the list of BAdi related to PMS only so you do not need to search for z*) -> Choose classic BAdi
Why some programmers use se19 instead of ooam this is because they might want to us another BAdi which can do the desire value or behavior.
For the enhancement
The tcode use is
SE19 ( to create ),
OOAM ( to view the layout and put the BAdi inside the PMS form - Functional Changes),
phap_admin_pa ( to execute the app ).
Appcreate ( to run the app but in more web based )
Guide was given by Wai Meng to find the coordinates in the forms ( using the debug mode - create a break point - look into the table (t_body) and find the unique Row and column Id)
Guide given by Pak Nanang was basically on how to create the BAdi and placement.
Guide given by Radi was basically the logic and the place to pin point the score value to be use by the Badi.
----------------------------------------------------
TCODE Picked Up
PFTC_DIS - workflow
SE91 - Message (havent test)
TABLE
T9B03 - The Value and coordinate use by the BAdi
Notes : I could be wrong any SAPIAN out there if i am wrong in any of my post please do voice out Thanks in advance
More How to and Tips :
https://www.sdn.sap.com/irj/sdn/thread?tstart=0&threadID=767077
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1276392,00.html
Adviced by Pak Nanang,Wai Meng and Radi.
TCode(TransactionCode)
SE18 - DisplayBAdi
SE19 - CreateBAdi
Deduction is within a standard SAP program there are places we can customized to our own requirements. The places are called user exit.
For my current limited knowledge:-
1. BAdi TCode - se19,se18
2. Dynamic Action
Been guided to do BAdi in two different ways.
1. SE19 -> Create Implementation -> Choose classic BAdi(Select from the list z* find) -> Press Create Impl. -> Choose the new name + The App Name. Then Change and Save the method you modify added.
2. OOAM -> Goto -> Enhancement (this is the place where you can find the list of BAdi related to PMS only so you do not need to search for z*) -> Choose classic BAdi
Why some programmers use se19 instead of ooam this is because they might want to us another BAdi which can do the desire value or behavior.
For the enhancement
The tcode use is
SE19 ( to create ),
OOAM ( to view the layout and put the BAdi inside the PMS form - Functional Changes),
phap_admin_pa ( to execute the app ).
Appcreate ( to run the app but in more web based )
Guide was given by Wai Meng to find the coordinates in the forms ( using the debug mode - create a break point - look into the table (t_body) and find the unique Row and column Id)
Guide given by Pak Nanang was basically on how to create the BAdi and placement.
Guide given by Radi was basically the logic and the place to pin point the score value to be use by the Badi.
----------------------------------------------------
TCODE Picked Up
PFTC_DIS - workflow
SE91 - Message (havent test)
TABLE
T9B03 - The Value and coordinate use by the BAdi
Notes : I could be wrong any SAPIAN out there if i am wrong in any of my post please do voice out Thanks in advance
More How to and Tips :
https://www.sdn.sap.com/irj/sdn/thread?tstart=0&threadID=767077
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1276392,00.html
PCH Logical Database calling a PNP logical database
Using call Function
Example
proceed = 'Y'.
*CHECK EMPLOYMENT STATUS (ACTION INFOTYPE).
clear i0000. refresh i0000.
call function 'HR_READ_INFOTYPE'
exporting
pernr = temp_02-pfno
infty = '0000'
begda = pchbegda
endda = pchendda
tables
infty_tab = i0000.
loop at i0000.
if empstat <> space and not i0000-stat2 in empstat.
proceed = 'N'.
endif. "empstat <> space and not i0000-stat2 in empstat.
exit.
endloop. "at i0000.
if sy-subrc ne 0.
proceed = 'N'.
endif. "sy-subrc ne 0.
Example
ZDLLBMW001
Information provided by Siti Sarah
Example
proceed = 'Y'.
*CHECK EMPLOYMENT STATUS (ACTION INFOTYPE).
clear i0000. refresh i0000.
call function 'HR_READ_INFOTYPE'
exporting
pernr = temp_02-pfno
infty = '0000'
begda = pchbegda
endda = pchendda
tables
infty_tab = i0000.
loop at i0000.
if empstat <> space and not i0000-stat2 in empstat.
proceed = 'N'.
endif. "empstat <> space and not i0000-stat2 in empstat.
exit.
endloop. "at i0000.
if sy-subrc ne 0.
proceed = 'N'.
endif. "sy-subrc ne 0.
Example
ZDLLBMW001
Information provided by Siti Sarah
SELECTION SCREEN (Variable)
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME
PARAMETERS: zClmty Like zitab-clmty DEFAULT
'3015'.
SELECT-OPTIONS: ZCLMTY FOR ZITAB-CLMTY DEFAULT '3015'. "adh2008 958
The differences between the both selection is that the top is a single value while the one below is a range type of selection.
This has a affect on the SQL or syntax that you are going to use. Example for the one above
START-OF-SELECTION.
SELECT * FROM ZCLAIM_I
WHERE CLMTY EQ zClmty.
SELECT * FROM ZCLAIM_I
WHERE CLMTY IN zClmty.
This information was provided by Miss Koh
PARAMETERS: zClmty Like zitab-clmty DEFAULT
'3015'.
SELECT-OPTIONS: ZCLMTY FOR ZITAB-CLMTY DEFAULT '3015'. "adh2008 958
The differences between the both selection is that the top is a single value while the one below is a range type of selection.
This has a affect on the SQL or syntax that you are going to use. Example for the one above
START-OF-SELECTION.
SELECT * FROM ZCLAIM_I
WHERE CLMTY EQ zClmty.
SELECT * FROM ZCLAIM_I
WHERE CLMTY IN zClmty.
This information was provided by Miss Koh
How to change your ABAP EDITOR
IN SE38
Choose utilities -> Setting
Choose
This new screen is the best where they will give you new screen and there are help every where. Almost like Visual Basic or VBnet. This tips is from SiMou Miss Chin
Choose utilities -> Setting
Choose
- Front-End Editor (New)
- Upper-/Lowercase Cobnversion in Disp Mode
This new screen is the best where they will give you new screen and there are help every where. Almost like Visual Basic or VBnet. This tips is from SiMou Miss Chin
Variable Size and Coordinate
This is a part of declaring variable
gbdat(8) TYPE c VALUE 'Birth Dt',
gbdat(10) TYPE c VALUE 'Birth Dt'
Coordination
MOVE otab-gbdat+6(2) TO o_dsn-gbdat+0(2).
o_dsn-gbdat+2(1) = '/'.
MOVE otab-gbdat+4(2) TO o_dsn-gbdat+3(2).
o_dsn-gbdat+5(1) = '/'.
MOVE otab-gbdat+0(4) TO o_dsn-gbdat+6(4).
This to make sure the data given out is like 31/12/9999
gbdat(8) TYPE c VALUE 'Birth Dt',
gbdat(10) TYPE c VALUE 'Birth Dt'
Coordination
MOVE otab-gbdat+6(2) TO o_dsn-gbdat+0(2).
o_dsn-gbdat+2(1) = '/'.
MOVE otab-gbdat+4(2) TO o_dsn-gbdat+3(2).
o_dsn-gbdat+5(1) = '/'.
MOVE otab-gbdat+0(4) TO o_dsn-gbdat+6(4).
This to make sure the data given out is like 31/12/9999
Append and Sort by SiMou Chin
This is how to append
it_techdate-date = dj_rec-dat01.
it_techdate = dj_rec-dat01.
append it_techdate.
clear it_techdate.
This is how to sort
sort it_techdate by date descending.
loop at it_techdate.
itab-djoined = it_techdate-date.
exit.
endloop.
---------------------------------
changes made
DATA: BEGIN OF dj_temp_rec OCCURS 0,
datejoined LIKE p0000-begda,
END OF dj_temp_rec.
append
dj_temp_rec-datejoined = dj_rec-dat01.
dj_temp_rec = dj_rec-dat01.
append dj_temp_rec.
clear dj_temp_rec.
* itab-djoined = dj_rec-dat01.
* EXIT.
Sorting
sort dj_temp_rec by datejoined descending.
loop at dj_temp_rec.
itab-djoined = dj_temp_rec-datejoined.
exit.
endloop.
it_techdate-date = dj_rec-dat01.
it_techdate = dj_rec-dat01.
append it_techdate.
clear it_techdate.
This is how to sort
sort it_techdate by date descending.
loop at it_techdate.
itab-djoined = it_techdate-date.
exit.
endloop.
---------------------------------
changes made
DATA: BEGIN OF dj_temp_rec OCCURS 0,
datejoined LIKE p0000-begda,
END OF dj_temp_rec.
append
dj_temp_rec-datejoined = dj_rec-dat01.
dj_temp_rec = dj_rec-dat01.
append dj_temp_rec.
clear dj_temp_rec.
* itab-djoined = dj_rec-dat01.
* EXIT.
Sorting
sort dj_temp_rec by datejoined descending.
loop at dj_temp_rec.
itab-djoined = dj_temp_rec-datejoined.
exit.
endloop.
Transaction Codes
Transaction Codes - Explaination
sm21 - logs error
pa03 - payroll lock to release 'period'
smartform - creating smart form
se37 - view program
se38 - change and view program
pa20 - view infotype
pa30 - change and view infotype
spro - change overview
su01 - List ID user
se10 - To see transport number
stms - check transport
se11 - Check table with structure
se16 - Check table
sm21 - logs error
pa03 - payroll lock to release 'period'
smartform - creating smart form
se37 - view program
se38 - change and view program
pa20 - view infotype
pa30 - change and view infotype
spro - change overview
su01 - List ID user
se10 - To see transport number
stms - check transport
se11 - Check table with structure
se16 - Check table