Support pack level issue in Standard Finance Program.

Hi Everyone,
                i have an issue which is related to Finance. Actually, Finance People are Using a Standard Report (FS10N) - GL Account Line item display. There,Vendor and Customer Details are not displayed (Customer/Vedor Filed is empty) for the normal GL Account. But for the Reconsalation GL accounts they are able to see.
               For this issue SAP released an SNOTE 1107639 and correction delivered in SAP_APPL support pack 12.And we already applied it in the system and our current SAP_APPL level is 14. Though it is already available why the problem is still persist. Another thing is, for the same issue there is another SNOTE 1034354 which guides to enhancement thro' some BADI work in standard program.
              My question is that if the correction is available in a patch and that is imported as well in to system without any error then it should resolving the problem.but in this case why it does not work out or what could be the reason behind this. As a Basis admin i would like to know.
Thanks&Regards,
Siva

Hi Siva,
Your query is obsolutely acceptable...
After supportpack update some times database will not be synchronised with the new updates.
and more over it seems there is a complete issue with SAP side.... there is only one option in u r hand now just restart the system.but please make sure to take the down time...and check whether the correction is working or not..if not then no luck u need to contact SAP global team and ask them why the corrections are not working properly..
Regards,
Srini

Similar Messages

Support Pack Level Upgrade in BI 7.0

Hi all,
Can anyone let me know what are the possible issues that would occur after upgrading support pack level in BI 7.0.
As far as I know a BI consultant would participate in the upgrade activities like BI objects check, SPAU, query check, etc. Can anyone let me know if there are are any other activities to be performed.
I would appreciate your help.
Thanks,
Sunny.

Hi
There is any customer specific development done by SAP in the previous system. If so, the time to act is just after the pre upgrade study only. The customer would only want to retain the customer specific module developed by SAP. We need to get SAPu2019s intervention in the project before we start the upgrade. SAP would develop certain patches to be run on the previous system to capture all the customer specific development and then they would run some patches on ECC system u2013 this would release the customer specific development in the new system (ECC./BI). This is a very crucial and important check of the step. If not taken care of at the proper time, it might hamper the Customer Specific development on the new system.
It is to be assured that the new system is at the latest stack level for ABAP, XI, BI etc before we start the SPDD and SPAU phase
Only one request is to be made for SPDD. For SPAU too, only one request should be made.
Previous system sandbox should be available for reference during the entire upgrade project and should not be scrapped before the Go Live.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/304b9de6-f84f-2b10-94af-e5ff7461c18c
http://www.thespot4sap.com/upgrade_guide_v2.pdf
Hope it helps.

SAP R/3 4.6 B Support pack level for AIX 5.2

Hi,
We have upgraded O.S version from AIX 4.3 to AIX 5.2. Here our environment is SAP R/3 4.6B and DB oracle 8.1.7.
My question: Do we apply any support pack to the system after support pack upgrade. Please find the below support pack level for our current system.
SAP_BASIS      46B           0054    SAPKB46B54
SAP_ABA         46B           0054    SAPKA46B54
SAP_APPL       46B           0054    SAPKH46B54
SAP_HR           46B           0000        -
ST-PI            2005_1_46B    0003    SAPKITLQC3
Please request the feedback.
Thanks & Regards,
Narayana Murthy.

Do we apply any support pack to the system after O.S upgrade ?
( Correction for the below posted mail)

Suggested Support Pack Level for ECC 6.0 Upgrade - Target

Hi ,
Can someone give us the suggested support pack level for the ECC 6.0 system after the upgrade.
Our current patch level is:
SAP_ABA     700     0012     SAPKA70012
SAP_BASIS     700     0012     SAPKB70012
PI_BASIS     2005_1_700     0012     SAPKIPYJ7C
ST-PI     2005_1_700     0003     SAPKITLQI3
SAP_BW     700     0014     SAPKW70014
SAP_AP     700     0009     SAPKNA7009
SAP_APPL     600     0010     SAPKH60010
SAP_HR     600     0013     SAPKE60013
EA-IPPE     400     0008     SAPKGPID08
EA-APPL     600     0008     SAPKGPAD08
EA-DFPS     600     0008     SAPKGPDD08
EA-FINSERV     600     0008     SAPKGPFD08
EA-GLTRADE     600     0008     SAPKGPGD08
EA-HR     600     0013     SAPKGPHD13
EA-PS     600     0008     SAPKGPPD08
EA-RETAIL     600     0008     SAPKGPRD08
FINBASIS     600     0008     SAPK-60008INFINBASIS
ECC-DIMP     600     0008     SAPK-60008INECCDIMP
ERECRUIT     600     0008     SAPK-60008INERECRUIT
FI-CA     600     0008     SAPK-60008INFICA
FI-CAX     600     0008     SAPK-60008INFICAX
INSURANCE     600     0008     SAPK-60008ININSURANC
IS-CWM     600     0008     SAPK-60008INISCWM
IS-H     600     0008     SAPK-60008INISH
IS-M     600     0008     SAPK-60008INISM
SEM-BW     600     0008     SAPKGS6008
IS-OIL     600     0008     SAPK-60008INISOIL
IS-PS-CA     600     0008     SAPK-60008INISPSCA
IS-UT     600     0008     SAPK-60008INISUT
LSOFE     600     0008     SAPK-60008INLSOFE
IRMIPM     30B     0005     SAPK-30BI7INIRM
IRMGLB     30B     0005     SAPK-30BG7INIRM
ST-A/PI     01K_ECC600     0000     -
GSCDMC     600     0001     SAPK-60001INGSCDMC
RCMGT     601     0001     SAPK-60101INRCMGT
Thanks
Senthil

Hi Senthil,
of course it is always recommended to use the newest Support Package Stack,
but if your system (your business processes) are working fine, I would recommend you to
import support package only then when you have an error or you want to have a special fiunctionality.
Some customers play support packages into the system only twice a year, because the business processes
should be tested after the sp import.
Kind regards
Imre Takácsi-Nagy
Senior Support Consultant II.
SAP Global Support Center Austria
Netweaver WEB Application Server ABAP / JAVA

Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007

What should be the Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007?
Regards,
Rajesh Banka

>
Rajesh Banka wrote:
> What should be the Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007?
>
> Regards,
> Rajesh Banka
Hi Rajesh,
Please see the note '833438', it explains which pack is required in this scenario.
"You cannont connect ERP (R/3) releases lower than 4.6C to CRM 5.0.
All subsequent CRM releases (5.0 or higher) cannot be connected to ERP lower
than (R/3) 4.6C.
These types of system landscapes are not supported by SAP.
If you are using CRM 5.0, you must have implemented Plug-in PI 2004.1
Support Package 10 and, provided you have Basis Release 620 or higher, you
must import PI_BASIS 2005.1 in R/3. --> After you have imported these
plug-ins"
Thanks,
Nitin Sharma

How to check for the prerequisite Support pack level

We are planning to upgrade from 4.7 to ECC6..How can check ,what is minimum support pack level that needs to be maintained in 4.7 for the upgrdade to ECC6.
Can i check this in Servrice markrt place .if so please let me know where to check
Thanks

Hello,
I am sure you will find relevant information in the link below.
https://websmp207.sap-ag.de/upgrade
Regards,
Manoj Chintawar

Support Pack level for upgrade

Hi All,
We are upgrading from R/3 4.7 to ECC 6.0, can anybody provide me Support Pack level for SAP_ABA, SAP_BASIS etc. before starting upgrade.
I have gone through lot of OSS notes but not getting exact SP level.
Regards,
Sachin

I depends on
- what upgrade package you use (SR1, SR2, SR3)
- the SP level of the source system
The upgrade guide tells you the minimum SP level needed to do the upgrade.
If you use the new CD/DVD set, the system will be upgraded to SP 12 (BASIS, ABA, SAP_APPL).
If you backup your wage tables before the upgrade (as described in the installation guide) you can also go to the highes SP level for SAP_HR.
Markus

Different Support Pack Levels

Hi experts, we are running a federated portal network, between our BI Portal with a ABAP daat source and our EP Portal which is your standard ldap data source. We are looking at implementing ESS MSS or XSS into our portal landscape.
I understand from SAP that i will need to install SP21 onto our portal systems to get the XSS business packages. But our BI team are dragging there heels about wanting to upgarde the BI Portal. I understand that the xss implementation creates a second node in a federated portal network that you will derive all your content from.
What are the implications/problems we may have if we upgarde our EP Portal to SP21 but leave our BI Portal on SP19 or 20??
Will it still work, connectivity wise and RDL wise?? Or will it just corrupt the whole thing???

The best possible scenario is to have the consumer and all the producer portals on the same version and SP level. However, this might not be possible to maintain at all times in landscapes were you have multiple producer portals.
Should you have a version difference, the general recommendation is to have your consumer portal at a higher SP level than your producers. All the portals should be on 7.0 version.
Please see the following link and SAP note 1295662 for more information on version Interoperability in FPN:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/45/76322bf0020dece10000000a11466f/frameset.htm
Thanks,
Shanti

Support Pack upgrade issue: Request deletion dose not work on CUBE

Hi Gurus,
We recently had a support package upgrade from SAPBW701 SP6 to SAPBW702 SP7.
We have an Info package request stuck in yellow state for DSO Load in HR Data.
We manually made it red and are trying to delete it manually/by creating a variant for Delete target contents in the process chain. It is not getting deleted.
Rather if we use the Delete target contents variant previously created before the support package upgrade, it works fine.
Please help me if any one can suggest any SAP NOTE or some other solution if possible.
Thanks in advance,
Sourabh Deo

Hi,
i think you have made it to red in request tab and tried deleting. Actually , you have to make the QM status red in Dataload monitor by double clicking the TOTAl technical status.
After the above activity, then try deleting.
I don't think its a Service Pack problem.
Regards,
Suman

Release 600, Level 11 (support pack SAPKGPAD11) vs Release 604, Level 03 (s

Hi,
We are moving into the SAP ECC enviroment and need to understand the difference between the 2 Support Packs Release 600, Level 11 (support pack SAPKGPAD11) vs Release 604, Level 03 (support pack SAPK-60403INEAAPPL).
Can anyone give us an indication in terms of functionality what we should be looking out for? During the testing we already came across and issue regarding double invoicing but this was fixed with a OSS note.
From a coding, functionality, intergration and process perspective,how do we know what the differences are? Is there a document that lists these difference as a quick comparison between the two releases.
Thanks in advance

Hi,
There is lot of difference btween 2. ECC System with EHP4 (Release 604 Level 3), ECC package will be on 604 release and level represents the support pack level of 604 release. If your system is on this level then it means that your system is with Enhancement packages but if your ECC components are on release 600 then it is without Enhancement packages.
Enhancement packages has been delivered a lot of new things like New GL etc. More information for what extra features ECC 6.0 with EHP4 has: can be checked on http://service.sap.com/erp-ehp.
To take your system from 600 release to 604 release requires a lot of effort because you have to upgrade your system to bring at this release.
Thanks
Sunny

We want to finalize a support pack strategy any pointers?

Hi,
We want to finalize on the support pack application policy for our company. Currently we are on ECC 6.0 Support Pack 8. We have a new SAP installation. Can you please suggest some blogs or articles that elaborate on what is a good support pack application policy. i.e how frequently should we apply the support packs, compatibility issues, what all things we need to test after applying the support pack etc.
Thanks for reading.

Hi,
Support packs are basically the Program/Object Corrections & Modifications.There is no hard rule on when to apply the support packs but it always best to be with the latest (latest -1) support pack.This way you will be safe from all the know issues and will have all the new functionalities.The important thing to note while applying the support pack is to decide whether you want to maintain the modifications to the standard objects (if any) or not? a functional testing is advisable.
Regards,
Sam

Support Pack upgrade error in Import Phase

Hello,
Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
Could you please help me on this? I tried and still searching solution for this..But no luck...
Os is : AIX and
Log File:                /usr/sap/trans/log/SAPIB70013.xxx
Main import
Transport request   : SAPKB70013
System              : xxxx
tp path             : tp
Version and release: 372.04.71 700
child process 934006 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_report_interface
fcode:      CLOSE_LINE_MODE
tabname:    SOURCE
len (char): 40
key:        CL_OBJECT_COLLECTION==========CT
retcode:    1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1212554 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_report_interface
fcode:      CLOSE_LINE_MODE
tabname:    SOURCE
len (char): 40
key:        CL_WDR_APPLICATION_WINDOW=====CT
retcode:    1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1171520 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_report_interface
fcode:      CLOSE_LINE_MODE
tabname:    SOURCE
len (char): 40
key:        CL_WDY_MD_EVENT_SOURCE========CI
retcode:    1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1331412 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_xrtab
fcode:      RT_MI_LOAD
tabname:    ECSCR_DATA
len (char): 106
key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
retcode:    1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
child process 1310922 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_xrtab
fcode:      RT_MI_END
tabname:    WDY_APP_PROPERTY
len (char): 64
key:        DEMO_UIEL_DROPDOWN_BY_IDX     DEMO_VIEW
retcode:    1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 018446 - 999999 not imported because the child processes died for unknown reason
child process 1310924 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_report_interface
fcode:      CLOSE_LINE_MODE
tabname:    SOURCE
len (char): 40
key:        CL_WDY_MD_OUTGOING_EVENT======CT
retcode:    1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1286192 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function:   db_xrtab
fcode:      RT_MI_LOAD
tabname:    ECSCR_DATA
len (char): 106
key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
retcode:    1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 009158 - 018411 not imported because the child processes died for unknown reason
import portion 018412 - 018527 not imported because the child processes died for unknown reason
import portion 018528 - 999999 not imported because the child processes died for unknown reason
sap_dext called with msgnr 1:
db call info -
function:   db_xrtab
fcode:      RT_MI_LOAD
tabname:    ECSCR_DATA
len (char): 106
key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
retcode:    1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
Main import
End date and time : 20100909034914
Ended with return code: ===> 12 <===
     |   ######################################
Thanks and Regards,
Sankar
SAP BASIS Consultant

Hi,
Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
Runtime Errors         CALL_FUNCTION_NOT_FOUND
Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          10.09.2010 09:41:37
Short text
     Function module "POSS_UIREQ_OPT_SUBMIT" not found.
What happened?
     The function module "POSS_UIREQ_OPT_SUBMIT" is called,
     but cannot be found in the library.
     Error in the ABAP Application Program
     The current ABAP program "SAPLSTXC" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
      not caught in
     procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The program "SAPLSTXC" contains the CALL FUNCTION statement.
     The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
     No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
     All function modules are listed in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Pay particular attenti
    upper/lower case and underscores ("_").
    or
b) Transport error
c) In the case of an enqueue/dequeue module,
    the lock object may not have been activated
    (ABAP/4 Dictionary).
When i tried to check function module it is not there..
Could you please help on this?
Regards,
Sankar Basis Consultant

Support Pack Status not updated in System Component Information

Hi Experts,
We have installed ECC 6.0 with Ehp3 and AFS 603 on AIX 6.1 and db6 V 9.1. We recently added the Vistex Incentive and Payback Module and Vistex Global Functions Add Ons. After the base install the Support pack 1-4 were applied for both Vistex components. For IRMGLB the status screen (System/Status) shows the SP highest Level = 03, while in SPAM screen it shows that Support Pack for for the Component IRMGLB is imported successfully.Because of this we can not apply the remaining Support Packs. For the other component (IRMIPM) Support Pack level 04 is correctly displayed.
Any idea what are we missing? Any help is greatly appreciated.
Thanks
Suhail

For future referers, Vistex says its a known issue.
Hello,
It is a known issue but it would not impact any of the functionality.
It can only be fixed in the subsequent release with conjunction with
SAP.
Thanks,
Vistex Support

Support Pack Upgrade to 10 to 23

Hi Experts,
Currently I am wokring on the BW3.5 versiowith support pack 10n. Recently our basis team upgrade the support pack 23(BW component) in source system which is a SRM system.I would like to know that will that be any mismatch issue occur between BW & SRM system. Details furnished below. Advance Thanks.
BW system Current Support Pack Level::
SAP_BW 350 Support pack level: 0010 Highest pack level : SAPKW35010
SRM System Current Support Pack Level::(BW software component):
SAP_BW 350 Support pack level: 0023 Highest pack level : SAPKW35023
Thanks,
RR

Hello Ragu,
This kind of scenario is exists in practice.
Normally I dont see that you will have lot of issue other than the support pack related.
In my practive, I have BI 7.0 system which is connected to 4.6 system as well as EHP1 system. EHP1 system is recently updagrade but still we can use out BW system normally.
For all the issues - your regression tests will give more clarity of the kind of issue that you can face.
For me You need to check whether the RFC is properly maintain and then relicated all the data sources once again followed by activation of transfer structures.
For more information on this you can also check the forum on the known issues of the respective stack.
Hope this helps.
Murali

Support Packs in Solution manager

Hi,
I have a query, when I am going to select patches through maintenance optimizer for solution manager I can see the source and target stack level at SMP and when I am putting the source stack(17) and the target stack as latest, solution manager 7.0 EHP 1-23 and going further for download it shows the support packs corresponding to release 701 but not to 700, as my current support pack level for solman is 16(release 700) and I can see there are support pack level up to 21 for release 700, I am confused why it is not taking account the remaining patches for 700 or can I switch directly to 701 and apply the support packs corresponding to release 701.
Regards,
Mridul

Dear Mirdul,
Check SAP note 1169247. In which it is mentioned that:
ABAP stack requirements
      You can start the SAINT update from any Solution Manager 7.0 ABAP Stack.
Java stack requirements
      A direct JSPM update to Solution Manager 7.0 Java Stack 18 and higher is not possible from some of the Java stacks. Therefore, proceed as follows: First, use the JSPM update to update the Java stack only to Solution Manager 7.0 Java stack 17 and then update to the relevant Solution Manager 7.0 Enhancement Package 1 Java stack.
      Take the numbering into account: Solution Manager 7.0 Java stack 17 contains NetWeaver 7.0 Java stack 16.
Also, check point number 5 in that.
I think now it will be clear.
Thanks
Sunny
Edited by: Sunny Pahuja on May 13, 2010 6:10 PM

Support pack level issue in Standard Finance Program.

Similar Messages

Maybe you are looking for