Latest version of SAP BI and PI Systems,Kernal Upgrade in Dual Stack

Q-:What are latest version of SAP BI and PI systems
can I install BI system using the dump 'ehp1 for NW 7.3'?
can I install PI system using the dump 'ehp1 for NW 7.3'?

Ans-: you use the same DVDs for BI and PI on NW 7.3 EhP1. SAPinst will give you a list of available options to install and PI is one of them. This is new for NW 7.3. With NW 7.0 and 7.1, there was a separate DVD kit for PI
As per my understanding, It is
BI- EhP1 for NW 7.3
PI - PI 7.3

Q
How to start SAP Installation master in AIX. I have moved to current directory and ./sapinst. But it's giving following error.

iaextract.c :440: error opening archive file /oracle/ZIM/IM_AIX_PPC64/ ./sapinst

Ans-:There are three cases what you try to solve this problem
1-:Have you uncar the Installation master DVD
2-: Check permission and ownership of the directory. Make sure that directory has execute permission.
3-:uploaded zip file to server and unzipped it on machine and started sapinst.

Q-:Kernel upgrade on Dual Stack system, do we need to perform it using JSPM or 'usual' kernel upgrade process will suffice?

and if it is from JSPM then why we require to do it using JSPM, any specific reason behind it?

Ans-: You can perform the kernel upgrade using JSPM or using the standard file copy method.

No difference
Do this through JSPM as this takes care of shutting down both stacks.

Q-: Transaction MB51 runs for a long time on mkfb table
ans-: Check your indices on MKPF.

If possible rebuilt them. In our case suddenly MB51 start to
underperform... very badly, from 15 min to 2 hours.
Our basis rebuilt the indices (don't know if all of them or one in
particular) and that made the difference.
BTW, we just have a year and 2 months of data so the reconstruction of
indices did the job in our case.

However be aware that if your data is large, index reconstruction might not
solve your problem int that case check SAP Notes 1598760, 1550000, 1516684,
that in short, pass create some fields of MKPF to MSEG so there is no need
for a join between these two tables by only using MSEG.
That is harder to implement but is seems to the way to go if really have
lots of data.

Q-:tcode st02 shows red entry for SWAP PROGRAM, SWAP SCREEN & SWAP GENERIC KEY.

Ans-:
Important measurement is the HitRatio. If the HitRatio is greater than 96% you do not really have a problem
Look for the memory related parameters post the values for
ztta/roll_area
ztta/roll_first
ztta/short_area
rdisp/ROLL_SHM
rdisp/PG_SHM
rdisp/PG_LOCAL
em/initial_size_MB
em/blocksize_KB
em/address_space_MB
ztta/roll_extension
abap/heap_area_dia
abap/heap_area_nondia
abap/heap_area_total
abap/heaplimit