http://community.altiusconsulting.com/blogs/jamesrothwell/archive/2008/12/02/branding-your-sap-bw7-0-portal-and-web-templates-with-portal-themes.aspx

How to transport SAP portal Theme

Create a transport package by going to SystemAdmin->Transport->Transport Package->export.After creating a transport package add Your Theme,defualt framework to the package created and transport it.



Source taken from sdn website
https://forums.sdn.sap.com/thread.jspa?threadID=271644&tstart=0

The Little SE80 of Horrors

REad this! Good for us SE80-ER
The past Three entries today was given by my colleague CYC

This is really true....

Source
Ps: this is not what i write but from the author above which i put into the blog.
Below is 100% quoted from the source

Random ramblings of an obsolete programmer

No - I don't think that people are getting dumber as time progresses. But I do think that we are some how not helping the next generation of developers to improve up on what the people who went before them left behind. And this includes ABAP developers.  When I say "we" - I specifically exclude the smart ones who didn't jump into the holes and avoided the temptations. So all the good and smart people - the stuff below is not about you, and don't get offended.

 

Some of you might know that I started my SAP career as an ABAP developer. I have no claims to have been in the league of Thomas Jung or Rich Heilman :) . But I believe I was an above-average programmer. As my career progressed, I moved on to other things - BW, SEM, SD, CRM and so on, but never did leave the "dark side". And I have been actively mentoring several consultants over the past years, many of whom have ABAP as their core skill. It is my discussions with my mentees that primarily prompted me to write this blog.

 

In my first SAP project - the server had 500 GB hard disk, and 1 GB RAM. This supported 25 users in a small manufacturng company. The desktops all had 32MB t0 64MB RAM, and something older than the pentium processor. This meant we had to think really hard about the code we created - anything inefficient would never get past the QA box. And we did not have a QA team - the developers could see for themselves when their code was terrible - and would go right back to re-designing the code. There was no code-inspector in the workbench either :) . Of course traces etc were available, and well utilized. Our team leads used to have competitions on who in their team would write the most efficient programs.

 

Most of us knew some other language before we learnt ABAP. And amongst my peer group at the time - the most common "first language" was C, and Dennis Ritchie was (and still is) God. One of the biggest gripes we had about ABAP was that it did not give us the flexibility that C gave (countless arguments about sort algorithms in C and then a simple SORT command in ABAP). This background in C ( the other popular one was LISP, which unfortunately I never got to learn), and the hardware limitations must have played a significant role in how our coding styles evolved.

 

ABAP programs mostly followed a procedural paradigm when I started. And then at some point, the OO paradigm started to kick in. By this time, I had started to lead ABAP teams. It was an awfully difficult time for developers to adapt - and people developed a hybrid style. If you had to maintain programs that were developed in this era - my sympathies are with you. Coincidentally, processors had become more powerful, and memory had become cheaper (though not as much as it is today). As a consequence - we had much more powerful servers and PCs, and as a result, we did not have to worry too much about algorithm efficiencies to get the same performance as before.

 

I did not realize the harm that had set on us, at the time - we just got habituated to write mediocre code. As moore's law kept proving itself as time progressed, we started going more and more backward in programming. The pathetic part is that we never realized this in time. Since we did not have to worry about quality to the extreme extent like before, we used the time to develop more and more programs and functionality. Dreadful as it might sound - quantity won over quality. We even slacked on peer reviews of code, that used to be second nature for us not that long ago. I believe that this also partly contributed to a decrease in the standard of training that new developers recieved. You no longer needed an internship to start your SAP career - a 6 week training course became a very acceptable entry criteria for developers.

 

Evidently, I was not the only team lead who realized this. And voila - SAP projects all over started having QA teams who started inspecting code formally. A lot of clients with big SAP footprint started having inhouse QA teams for it, and consulting companies started selling this as a service. I do believe that this helped some - things did get a bit better, but not for long.  If you do anything en-masse, you have to standardize. And QA process became standardized too - and along with the good, came the bad. A lot of QA people I have come to know,  barring a few exceptions, just go through a checklist mechanically, and do not take the time to understand the actual algorithm and offer meaningful suggestions. This is something a developer can do for his own code - and I am not sure if this type of QA really adds a lot of incrememental value.

 

I have been debating the solution for these issues for a while now - and here are some of the things we seem to get some consensus on.

 

1. Don't just train new crop of developers in just ABAP - also educate them in good software engineering practices. It might also be a good idea to train them in a second language if they don't know it by the time they learn ABAP. It is hard to improve when you have nothing to compare against :)

 

2. Have better benchmarks - somehow show the developer how much better his programs could be. ( A friend of mine, if he has his way, would like to have a QA box which is much less powerful than production for developers to get their code better).

 

3. Have a compulsory internship with a good senior developer, before some one is allowed to work independently as a developer.

 

4. Encourage senior developers to take turns and lead the QA teams, and don't let any one be in QA role for very long.

 

 5. Encourage debates on programming practices - do not blindly follow something without getting a solid understanding of the arguments for and against. For example -  Offlate, I have not seen many developers who argue against OO as a development paradigm. Infact, the prevailing sentiment is very much against the old procedural paradigms. However, I have heard and read several interesting conversations where people tore the OO paradigm to pieces. It is less important on which side of the debate you are positioned - the important part is to participate, and expand your thinking.

 

I have one other area that is close to my heart, that I wanted to bring up here - the maintainability of the code we develop. However, I guess I have over stayed the welcome for one web log, so I will defer that to another day.

 

So, what do you folks think?

SAP Naming convention....

Hmm all this while I was wondering the REAL naming convention.... but alas.
my colleague CYC huhu as usual provided.....
as below
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15304

You are not a developer...

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/10415
Read this article my friends...
Provided by my colleague Chin yoon Chan...

What she said is true... VERY trueeeeee

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

Passing a value to another controller

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5368%3Fpage%3Dlast%26x-maxdepth%3D0
http://help.sap.com/saphelp_nw70/helpdata/en/cb/40193c45f9fa13e10000000a114084/content.htm

http://forums.sdn.sap.com/message.jspa?messageID=5639015
https://forums.sdn.sap.com/message.jspa?messageID=5963473

Portal Front End : WebDynpro or BSP application in iview not working

1. Please do an activation using back end - using transaction CODE "SICF"
2. After activation please do refresh portal.
* this is the common error where we normally have after deploying NEW program

Guided procedure

Recently we was given a task to detect the error after thepathces.
But it seems that the error was some how adesign brought by the PAST.

Anyway to debug the error you will need this few access.
Roles : -
Content Admind
Guided Procedure -> Design Time and Administrator.

Error found.  This object is being locked by XXXuser.
Solution. Go to
Guided Procedure -> Administrator.
Unlock Object. Try to find the Object development to unlock

Error Page different from what it is supposed to be
Solution. Go to
Guided Procedure -> Design Time.
Click on the "Callable Object"
"Object Defination" Tab
and choose the correct HTML.

Notes: in order to make the changes reflected please do the activation from branches up to the highest.


Problem. (Error No Active Process Found)
The problem was the Activated processes was not found.
Solution:
Goto Guided Procedure -> Life and Work Events - MY -> Marriage -> Marriage Process (looks lika gears) -> click open
Goto Tab -> Instantiation ( click on the arrow button to go to the tab )
Copy the Process ID.

Then Go to portal Content
-> Content Provided by SAP\End User Content\Employee Self-Service\Custom Content\Life and Work Events
Open the "Iview" (Marriage)
Find the field "Application Parameters"
And change the process.template.id; eg. (process.template.id=88394210FCBB11DCC1F000145EC7373A&process.autostart=true)

--------------------------------------------------------

Error. The navigation on the left is not correct add or remove
Solution
Goto Guided Procedure -> Life and Work Events - MY -> Birth Deceased -> Birth Deceased Process (looks lika gears) -> click open
Goto Tab -> Roles, Click on the pencil to go to EDIT MODE
To delete . Click on the select the callable object ( looks like one jigsaw ).
To Add . Click on add branch and then select the callable object
Save and active everything from branches to parent.

Error. The pages kept going to page "initiate instances"
Solution.
Goto Guided Procedure -> Life and Work Events - MY -> Birth Deceased -> Birth Deceased Process (looks lika gears) -> click open
Goto Tab -> Roles, Click on the pencil to go to EDIT MODE
Select role type -> "initiator".
Save and activate

PC0 to enter GL

Infotype 41, infotype 0

Basically i am still new to abap / SAP.
All i know to access this two info to get the PA20 Transaction code
action type (0)
and
assigment Date (41)

while debugging for a program this is to get the hire date and rehiring date.

* warning this notes may not be correct :D

Problem encounter

Recently i was assigned a task to create a custom made help page.
The steps takaen :
1. SE80.
2. Create a BSP.
3. Create iview
4. enable the masthead.
5. Put all mime inside.including all the pages.

Trasport from dev to test was A-OK
But when transported to production there seems to be a probblem which i am unablet to solve at the moment

after googling and doing some research. The pages i have found ask us to

 Assigning MIME Objects to a Transport Request under Structure linkOther Functions.
Link : http://help.sap.com/saphelp_webas630/helpdata/en/46/bb182fab4811d4968100a0c94260a5/content.htm

which leads to ask us to

Select the required directory, subdirectory, or individual MIME objets in the browser of the MIME Repository and choose Write Transport Request in the context menu.
Link : http://saphelp.border-states.com/EN/46/bb1841ab4811d4968100a0c94260a5/frameset.htm

Which i am going to try tomorrow with my user.

that's all for now

WorkFlow Transaction

SWi1 - To check workflow item

How to disable or enable the help link in masthead iView

Refer to this link on how to go to masthead Iview
Show Link in Masthead: Help < NO >

* To disable or enable the help link on the top frame of the portl
The actual location of the iview

Portal Content
+ Content Provided by SAP
+ Admin Interfaces
+ Admin iView Templates
+ Portal Editors
 Masthead

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

Sequence to deploy EPA Files

Doing portal front end sometimes can be confusing.
But what we have learned that most of the time we need to properly package the EPA in order not to haywire it.
Ok straight to the point.

Normally we create (in sequences) the element / object
iview -> page -> workset -> Roles

So during the packaging
iviews and pages
It is best to put the iviews and pages together as we are directly changing it. We can deploy as much as we want.

Work Set n Roles
Each of them are to be package separately cause major changes are to be reflected in it.

Ps:/ this is my exp or should i say the level of understanding. Please do comment if i am wrong. And would glady change.. ^^

Creating PDF Form

TCODE : SFP
1. Create In sequence
- Interface
- FORM (adobe Life Cycle is needed to design the forms)

=========================================================
note sorry guys for the no posting from now onward when ever i have anything about sap i will surely put it here. Take care! ^^

Selfnote (please ignore this is for my daily notes)
---------------------------------------------------
Flexi Benefits
TCodes
SM31
SE16N

ZZ_WDA_FSA_B001_MOD Interface
ZZ_F_FSA_B002 Form