Issues during upgrade - SPDD

Hi,
We are doing the upgrade from SAP R3 4.6C to ERP 6.0, during SPDD phase we are getting errors while adjusting table VBAP. If you go to tcode SE14 there it is not allowing us to activate and adjust database. While activating the table it throws the error message as "Table VBAP could not be activated - E- Table VBAP ( error adjusting the database)"
Thanks in advnace.

Hi,
Have you compared as what changes were made to the VBAP in 4.6C.
Also can you tell what is the long text of the message.
regards,
Atish

Similar Messages

Theme issues during upgrade - EP 6 to EP 7

Dear experts,
We recently did an upgrade from EP 6 to EP 7. We are using the EFP to host some websites. Now we have an issue that in one of the sites we have a TLN iview that do not take the theme. The theme looks fine in other couple of sites we have hosted similarly.
Can someone suggest what could I do to fix this?
I have tried reimporting the Iview from an old EP6 system. Also I tried recreating the iview. I have no clue as why we do not have theme in this particlular iview.
Hope somebody has a clue. Do we have any document about the known issues while upgrading from EP6 to EP7?
regards,
Noufal

The issue was with the masthead iview. Seems the masthead file was corrupted during transport.
Thanks,
Noufal

Critical Issues during upgrade

Hi All,
I am in the middle of Peopletools upgrade from PT8.49 to 8.52. However, i am getting below issues -
1. Step: Copying the PPLTLS84CUR Project
===============================
Queries Application Upgrade Copy started:
File: <Directories>\peopletools\src\pssys\qdmupd.cppSQL error. Stmt #: 728 Error Position: 0 Return: 805 - ORA-00001: unique constraint (SYSADM.PS_PSQRYSELECT) violated
Failed SQL stmt:INSERT INTO PSQRYSELECT (OPRID, QRYNAME, SELNUM, SELECTTYPE, PARENTSELNUM, RCDCOUNT, FLDCOUNT, CRTCOUNT, HAVECRTCOUNT, QRYDISTINCT) VALUES (:1,:2,:3,:4,:5,:6,:7,:8,:9,:10)
Internal Error: invalid transaction handle instance passed from SamSetSqlProc 0: 28217 vs 0
Internal Error: invalid transaction handle instance passed from AddBufBind 0: 28217 vs 0
Internal Error: invalid transaction handle instance passed from SamExec 0: 28217 vs 0
Internal Error: invalid transaction handle instance passed from SamSetSqlProc 0: 28217 vs
===============================
2. While building the projects:
===============================
PNLGROUP_SRCH - Query view has invalid syntax or it does not exist. ==> this error occures 55 peopletools views.
===============================
Please help with your expertise.
Thanks in advance.

Hi,
Can you try running SYSAUDIT to check data integrity, perhaps in your pre-upgrade env some data got invalid in the Query tables, due to manually updating the database tools tables.
See peoplebooks for possible errors and solutions.
PeopleBooks > PeopleTools 8.52: Data Management > Ensuring Data Integrity > Running SYSAUDIT > Query Integrity

Performance Issues during Upgrade of EBS from 11.5.10.2 to 12.1.1

Hi,
We're upgrading our EBS , from Rel 11.5.10.2 to 12.1.1.
We're stuck , while running script ar120bnk.sql (ran more than 20 Hours) :
Regarding the tables involved in this Process :
select owner , table_name,num_rows,last_analyzed,sample_size
from dba_tables
where table_name in
'RA_CUSTOMER_TRX_ALL',
'RA_CUST_TRX_LINE_GL_DIST_ALL',
'XLA_UPGRADE_DATES',
'AR_SYSTEM_PARAMETERS_ALL',
'RA_CUST_TRX_TYPES_ALL',
'RA_CUST_TRX_LINE_GL_DIST_ALL',
'XLA_TRANSACTION_ENTITIES_UPG')
AR RA_CUSTOMER_TRX_ALL 55,540,740 04/02/2012 12:41:56 5554074
AR RA_CUST_TRX_LINE_GL_DIST_ALL 380,513,830 04/02/2012 13:54:12 38051383
AR RA_CUST_TRX_TYPES_ALL 90 04/02/2012 14:04:54 90
AR AR_SYSTEM_PARAMETERS_ALL 6 04/02/2012 12:19:49 6
XLA XLA_UPGRADE_DATES 4 05/02/2012 17:12:57 4
As you can see: RA_CUST_TRX_LINE_GL_DIST_ALL is more tan 380 million rows !
and RA_CUSTOMER_TRX_ALL is more than 55 million rows.
We have more huge tables in the AR schema , and we would like to know if we are unique customer
with huge AR schema objects , and if NOT how come that we are getting stuck on threed statment in
AR schema.
Bellow an output of all the objects that have more than 10 million rows in AR schema :
select owner , table_name,to_char(num_rows,'999,999,999') ,last_analyzed
from dba_tables
where owner = 'AR'
and num_rows > 10000000
order by num_rows desc nulls last
AR AR_DISTRIBUTIONS_ALL 408,567,520 04/02/2012 11:49:57
AR RA_CUST_TRX_LINE_GL_DIST_ALL 380,513,830 04/02/2012 13:54:12
AR MLOG$_AR_CASH_RECEIPTS_ALL 310,777,690 04/02/2012 12:30:33
AR RA_CUSTOMER_TRX_LINES_ALL 260,211,090 04/02/2012 13:30:26
AR AR_RECEIVABLE_APPLICATIONS_ALL 166,834,930 04/02/2012 12:16:54
AR MLOG$_RA_CUSTOMER_TRX_ALL 150,962,980 04/02/2012 12:33:23
AR AR_CASH_RECEIPT_HISTORY_ALL 145,737,410 04/02/2012 11:40:31
AR RA_CUST_TRX_LINE_SALESREPS_ALL 130,287,580 04/02/2012 14:03:54
AR AR_PAYMENT_SCHEDULES_ALL 108,652,480 04/02/2012 12:05:32
AR RA_CUSTOMER_TRX_ALL 55,540,740 04/02/2012 12:41:56
AR AR_CASH_RECEIPTS_ALL 53,182,340 04/02/2012 11:29:53
AR AR_DOC_SEQUENCE_AUDIT 52,865,150 04/02/2012 11:52:46
AR RA_MC_TRX_LINE_GL_DIST 17,317,730 04/02/2012 14:05:18
AR AR_MC_DISTRIBUTIONS_ALL 13,037,030 04/02/2012 11:53:35
AR AR_MC_RECEIVABLE_APPS 12,672,050 04/02/2012 11:53:57
AR AR_TRX_SUMMARY 12,457,560 04/02/2012 12:20:16
AR RA_CUST_RECEIPT_METHODS 11,105,750 04/02/2012 13:35:38
AR HZ_ORGANIZATION_PROFILES 10,271,640 04/02/2012 12:24:44
How to Upgrade AR tables whith Huge amount of Datas ( > 50 Millions Rows ) ?

Hi,
Dont worry, you are not the only one even we have one customer whose AR_DISTRIBUTIONS_ALL table is 80 GB now and i can even do select count(*) for this table.
We had to keep this much data for business requirements, but i wonder if this is a bug or users mistake.
Due to this we are facing seruios performance issues for AR reports and raised SRs but no resolution yet. And this guy who is assigned to us is reall ynot been helpful to fix the issue.
Although we did not upgrade for this customer, but we migrated from 11.5.9 to R12.1.1 by re-implementation. But all these increasing size of these tables happened after migration.
And i believe most of the time in your upgrade is going to building the indexes. You can ask Oracle if they can edit the driver file to skip building the indxes and rebuild them after upgrade. But again it will also take time.
Another option for you is to "Archive and Purge the data" as per chapter 10 of
11i Receivables user guide.
http://docs.oracle.com/cd/B25284_01/current/acrobat/115arug.zip
Thanks
Edited by: EBSDBA on Feb 8, 2012 10:04 PM

Report writer issue during upgrade from 4.6 to ecc6

Hi all,
On generating report of report writer through GR5G (we are regenerating because we were getting dump for this report after up gradation from 4.6c to ecc6)we found one syntax error. The error is in auto generated program we can see that error but cant fix it as it needs a key and maybe that might not also be the right method to resolve is as auto generated codes should not be touched . So what would I like to ask is how can error come in auto generated program and how do I fix it (error is in data declaration QUOTDATE_MAX(08) TYPE C VALUE '). Here u can see that instead of only is used there is no closing inverted comma.

Hi,
You need to make sure that all your delta queues are empty before the upgrade.
In case of logistics make sure all v3 jobs are stopped and extract queues are empty.
After the upgrade make sure that the source systems are mapped and working correctly. Check that your delta queues are conneted to the correct BW system.
You need to test all your extractors as they might have changed (check release notes). Test delta loads to make sure they are working properly.
Cheers,
Kedar

Report writer issue during upgrade to ecc6

Hi all,
On generating report of report writer through GR5G (we are regenerating because we were getting dump for this report after up gradation from 4.6c to ecc6)we found one syntax error. The error is in auto generated program we can see that error but cant fix it as it needs a key and maybe that might not also be the right method to resolve it as auto generated codes should not be touched . So what would I like to ask is how can error come in auto generated program and how do I fix it (error is in data declaration QUOTDATE_MAX(08) TYPE C VALUE '). Here u can see that instead of only is used there is no closing inverted comma.

Hi all,
On generating report of report writer through GR5G (we are regenerating because we were getting dump for this report after up gradation from 4.6c to ecc6)we found one syntax error. The error is in auto generated program we can see that error but cant fix it as it needs a key and maybe that might not also be the right method to resolve it as auto generated codes should not be touched . So what would I like to ask is how can error come in auto generated program and how do I fix it (error is in data declaration QUOTDATE_MAX(08) TYPE C VALUE '). Here u can see that instead of only is used there is no closing inverted comma.

Disck Space not enough during upgrade CUCM 9.1(2)SU1 to 9.1(2)SU2a

Hi,
I face an issues during upgrade my current CUCM 9.1(2)SU1 to 9.1(2)SU2a, it show with this error message "There is not enough disk space in the common partition to perform the upgrade, for steps to resolve this condition please refer to CUCM 9.1(1) release notes or view defect CSCuc63312 in bug toolkit on Cisco.com". I had check the bug id and got 2 way to do it:-
1. reduce the amount of traces on the system, but I not ready want to do this
2. install a COP file name: ciscocm.free_common_space_v1.0.cop.sgn
If I select option 2, will it have any risk? Is it mean 9.1(2) - inactive version will be clear out from disk space or it will clear out 2 version - active and inactive version from disk space?
I need have some advice on this before I perform.
Thanks.

Hi,
As per the following link
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/9_1_1/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91_chapter_011.html
You will not be able to switch to the previous version after the COP file is installed. For example, if you are upgrading from Cisco Unified Communications Manager 9.0(1) to Cisco Unified Communications Manager 9.1(1) and the previous version is Cisco Unified Communications Manager 8.6, the COP file clears the space by removing the 8.6 version data that resides in the common partition. So after you apply the COP file, you will not be able to switch to the 8.6 version."
Additionally, regarding the first option, if you do not want to reduce the tracing levels you can still delete some old traces using RTMT which gives you an option of deleting the traces from the server as well as transferring / downloading them to your pc simultaneously by checking the 'delete from server' option on last page of log file collection option.
HTH
Manish

Public Sector: Will this have any issues during Siebel upgrade?

Hello,
We are using Siebel Public Sector application (Case Management) in our product.
Every contact who is Primary under a Contact will be associated to a Master Case. If there is no master case associated with primary contact, siebel will create a new master case. In other words, Contact to Master Case is 1:1 relationship.
We are in the process of developing a new requirement where in a Contact can be linked to one or more Master Cases (1:M). Since this is deviates Siebel OOB feature we do not want to change it.
Instead, we have created a new custom stand-alone Table (which mimics OOB Master Case columns) and a "New Custom BC".
Created a link betwen Contact BC and New Custom BC (Id -> Par Row Id).
In "New Custom BC", field called "Master Case Number" has a dynamic picklist based on OOB "PUB Master Case" BC.
For other field we have mapped using pickmaps.
Our requirement is met but our only question is "Will this have any issues during Siebel upgrade?"
Quick responses will be very helpful.

Thank you for your reply. I only see three versions of Adobe Reader available for Windows XP SP3 at the Adobe site
http://get.adobe.com/reader/otherversions
In doing some research, it seems there were some issues if you skipped an update but I did not find any information (only other queries) as to my original question of compatibility. Also, how can we access the older file if it won't open in 10.1.2?
Can I load 10.1.2 in addition to their older version to check and see what will or will not open correctly before I uninstall the older version? I don't want to load the new version and then have them not be able to access a needed file...

Find button issue in tool bar during upgrade from 4.6c to ECC 6

Hi All,
I came across one issue during the upgarde.
In new system ECC 6:
When i run the transaction IW51 then give the notification type SE(service notificaton) and then hit enter key.
It leads to next screen there enter the value in the FUNCTIONAL lOCATION field some ex 9000004 and
opposite to that field there is a structure list icon.
Clicking that icon it leads to a structure list.
My issue is: the FIND button and FIND NEXT button are disabled in the menu bar.I need the both buttons to be active
When i seen in old system i.e 4.6c
FIND button and FIND NEXT button are active.
I made little change in the new system in include MIHIXF82 as shown below.
SET PF-STATUS 'MAIN' ."EXCLUDING gt_excl_tab.
I commented the EXCLUDING gt_excl_tab.
Now FIND button and FIND NEXT button is active but when i click the FIND button there is no pop up is displayed.
Usually pop up is displayed when we click FIND button in that we can enter the value which we have to find out.
Regards
Jai
Edited by: Jayanth16 on Jan 28, 2010 8:07 AM

Hi,
In that program gui status MAIN is used.
When i see that gui status and in FUNCTION KEYS the FIND button and FIND NEXT button
the function codes are in orange color.Remaing BACK,EXIT,and CANCEL button function code are in white color.
Whether the orange color indicates is in inactive mode?
If so how can i activate those Function codes?
Regards
Jai

Could you pls give the details about the Unicode conversion during Upgrade

Hi,
Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
Waiting for quick response
Best Regards,
Padhy

Hi,
These are the few points i gathered during my upgradation project.
Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
So it is advised to keep a back-up of the existing system.
Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
Version Upgrade involves the following Steps.
Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
First copy the entire E4B system into the E1B System which is created for Version 4.7.
Apply the Version 4.7 CD provided by SAP over the E1B System.
Now check whether all the functionalities that was in E4B system works fine with E1B system also.
Thus the Version Upgrade involves two steps.
1. SAP Upgradation with the help of the CD
2. Manual Upgradation.
1. SAP Upgradation with the help of the CD
This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
2. Manual Upgradation.
This Manual Upgradation involves
2.1 Upgradation of Standard Objects
2.1.1 SPAU Objects
2.1.2 SPDD Objects
2.2 Upgradation of Custom Objects.
Upgradation of Custom Objects can be placed under the following three categories.
Unicode Compliance
Retrofit
Upgrade
Please Find below some of the common Unicode Errors and their solutions
1. Error:
In case of Translate Error; Dangerous use of Translate in Multilingual system.
Correction:
To correct the Error occurring on TRANSLATE statement use this additional statement before the Translate statement.
SET LOCALE LANGUAGE sy-langu.
This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is sy-langu, i.e. the log on language of the user.
2. Error:
In case of Open Dataset Error; Encoding Addition must be included.
Correction:
This Error occurs only when the MODE is TEXT.
To correct the Error occurring on OPEN DATASET statement use this statement instead.
OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
Where: dataset_name NAME OF THE DATASET.
Access INPUT or OUTPUT or APPENDING or UPDATE.
DEFAULT - Corresponds to UTF-8 in UNICODE systems &
NON_UNICODE in NON-UNICODE systems.
3. Error:
In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; Function module UPLOAD is flagged as obsolete.
Correction:
The FM GUI_DOWNLOAD/UPLOAD is used.
The variations to be made in the parameters of the FM:
1. Filename It must be of STRING type.
2. Filetype DAT is not used any longer, instead ASC is used.
3. Field Separator The default value SPACE is used, incase for a TAB separated file X can be used.
4. Error:
In case of CURRENCY/UNIT Addition Error; Use addition CURRENCY/UNIT when outputting.
Correction:
The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
To correct this error follow the following method:
WRITE: /3 'TOTAL',' ', TOTAL.
WRITE: /3 TOTAL, , TOTAL CURRENCY 2. --- Where 2is the Currency Key for Getting 2 decimal places.
5. Error:
In case of TYPE X Error; Variable must be of C, N, D, T or STRING type.
Correction:
We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
So the method to be followed is:-
1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
2. Declare the variable as Type C, and use the method UCCP(XXXX) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute HORIZONTAL_TAB of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
E.g.:
i) *DATA: TAB TYPE X VALUE 09, Tab character
CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
ii) * DATA: CHAR TYPE X VALUE 160.
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA CHAR TYPE C.
CHAR = CL_ABAP_CONV_IN_CE=>UCCP(00AO).
(Here 00A0 is the Hexadecimal equivalent of the decimal 160).
3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
E.g.:
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA : LF(2) TYPE X VALUE 'F5CD'.
DATA : BEGIN OF LF,
A1 TYPE C,
A2 TYPE C,
END OF LF.
LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
6. Error:
In case of the Character -Error; The Character -cant appear in names in Unicode Programs.
Correction:
The Character -(Hyphen) appearing in Variable names is replaced by the character _ (Under Score) for Unicode/Upgrade Compliance.
E.g.:
*wk-belnr LIKE bkpf-belnr,
*wk-xblnr LIKE bkpf-xblnr,
*wk-date LIKE sy-datum,
*wk-wrbtr LIKE bseg-wrbtr,
*wk-name1 LIKE lfa1-name1,
*wk-voucher(8) TYPE c.
wk_belnr LIKE bkpf-belnr,
wk_xblnr LIKE bkpf-xblnr,
wk_date LIKE sy-datum,
wk_wrbtr LIKE bseg-wrbtr,
wk_name1 LIKE lfa1-name1,
wk_voucher(8) TYPE c.
7. Error:
In case of The SUBMIT-TO-SAP-SPOOL Error; you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition.
Correction:
1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
2. Call the FM GET_PRINT_PARAMETERS:
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
3. Use the SUBMIT-TO-SAP-SPOOL statement.
E.g.:
     submit zrppt500
     using selection-set 'AUTO3'
     with res_no eq lo_rsnum
     with sreserv in preserv
     to sap-spool destination p_dest
     immediately 'X'. "print immediate
DATA: print_parameters type pri_params,
archive_parameters type arc_params,
valid_flag(1) type c.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
Submit zrppt500
Using selection-set 'AUTO3'
With res_no eq lo_rsnum
with sreserv in preserv
to sap-spool
SPOOL PARAMETERS PRINT_PARAMETERS
ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
WITHOUT SPOOL DYNPRO.
8. Error:
In case of Message Error; Number of WITH fields and number of Place Holders are not same .
Correction:
Split the statement after WITH into the same number as the place holder for that Message ID.
E.g.:
1. * MESSAGE E045.
MESSAGE E045 WITH '' ''.
2. in program ZIPI0801
     Start of change for ECC6
     message e398(00) with 'Could not find access sequence'
     'for condition type:'
     p_ptype.
message e398(00) with 'Could not find '
'access sequence'
'for condition type:'
p_ptype.
     End of change made for ECC6
9. Error:
In case of Move between 2 different Structures; The structures are not mutually convertible in a Unicode program.
Correction:
Make both the Data Types compatible and then assign the contents.
E.g.:
The statement move retainage_text to temp_text. Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
10. Error:
In case of no description found; add a GUI title.
Correction:
In this type of error gui title is generally missing so add a GUI title to the module pool.
11. Error:
In case of writing internal or transparent table
Correction:
Write individual fields.
E.g.:
WRITE: / EXT. --> EXT should be a character type field
WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
12. Error:
In case of combination reference table/field S541-UMMENGE does not exist
Correction:
Was due to error in reference table S541. TABLE S541 has errors
1)Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)
2)Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)
Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
And that of ZMKCODE (from ZACCODE to ATTR8)
13. Error:
In case of KEY does not exist
Correction:
The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
14. Error:
Incase of WRITE statement, Literals that take more than one line is not permitted in Unicode systems.
Correction: To correct this error, we need to align the spaces accordingly so that the statement doesnt go beyond the line.
15. Error:
Incase of Data statement, The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect..
Correction: To correct this error, instead of like in the Data statement, use type.
16. Error:
Incase of DESCRIBE statement, DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.
Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
CHARACTER MODE is added when the data object is of flat/ character type.
BYTE MODE is added when the data object is a deep structure.
Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
LENGTH clen IN CHARACTER MODE.
Where blen and clen must be of type I.
17. Error:
Incase of DO-LOOP Error, In Do loop range addition needed
Correction:
An internal tables is declared and the two fields (VARYING field and NEXT field) were
Included inside the internal table
E.g.: In program SAPMZP02
DO 11 TIMES
     VARYING STATION_STATE FROM STATION1 NEXT STATION2. ECC6
CASE SYST-INDEX.
WHEN 1
STATION_STATE = STATION1.
WHEN 2
STATION_STATE = STATION2.
WHEN 3
STATION_STATE = STATION3.
WHEN 4
STATION_STATE = STATION4.
WHEN 5
STATION_STATE = STATION5.
WHEN 6
STATION_STATE = STATION6.
WHEN 7
STATION_STATE = STATION7.
WHEN 8
STATION_STATE = STATION8.
WHEN 9
STATION_STATE = STATION9.
WHEN 10
STATION_STATE = STATION10.
WHEN 11
STATION_STATE = STATION11.
18. Error:
Incase of the parameter QUEUE-ID Error, QUEUE-ID is neither a parameter nor a select option in program rsbdcbtc.
Correction:
The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
E.g.: In program Z_CARRIER_EDI_INTERFACE
     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
19. Error:
Incase of EPC Error, Field symbol <TOT_FLD> is not assigned to a field .
Correction:
This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
The OS Note - 1036943 needs to be applied.
Error:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
Correct:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
Error:
Constants : c_tab type x value '09' .
Correct:
Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
Error:
Data : begin of output_options occurs 0 . Include structure ssfcompop.
Data : end of output_options .
Correct:
Data : output_options type standard table of ssfcompop with header line .
Error:
PARAMETERS : NAST TYPE NAST .
Correct:
PARAMETERS : NAST TYPE NAST NO-DISPLAY .
Replace WS_DOWNLOAD and WS_UPLOAD by
GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
Issue:
Moving data from one structure to another structure if those two structures are not compatible
Solution:
we should use move-corresponding or field by filed we need to move it.
If database structures are different in 4.6c and ECC6.0,
Then we should go with append structure concept.
While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
Also Check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
Reward points if helpful.
Regards,
Ramya

[Forum FAQ] SkyDrive synchronization issue after upgrading to Windows 8.1

After Windows 8.1 released, users may encounter the issues about syncing files in SkyDrive. There are the error messages you may find:
Error 0xS00705B4: This operation returned because the timeout period expired
Sorry, the action couldn't be completed because the file hasn't finished uploading. Try again later
Error 80070490: element is not found.
Many SkyDrive folders in library like SkyDrive [1], SkyDrive [2] …
We just would like to point out some possible causes of this issue and give you some suggestions to troubleshoot it.
Cause:
Location was messed up during upgrade.
Pending uploading or downloading task blocked in synchronization.
SkyDrive was hang.
GPO blocked the syncing behavior
The user profile folder was relocated after upgrading.
How to fix:
Suggestions 1: Checking the consistence of locations on both registry key and SkyDrive properties:
Right click SkyDrive -> Properties -> Location tab
Open regedit.exe, locate to the following key and check the location.
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\SkyDrive
Suggestion 2: For many SkyDrive
folders:
Check which one can be explored properly with right files and relocate the SkyDrive folder via changing the settings in
suggestion 1.
Or create a new folder for relocating SkyDrive’s.
Suggestion 3: End the Skydrive.exe process and restart in command or disconnect and reconnect your MS account in SkyDrive to clear the pending task:
Press Win+R to open run, and type following commands one by one:
%windir%\system32\skydrive.exe /shutdown
%windir%\system32\skydrive.exe
Log off your MS account in SkyDrive and log in again to check the issue.
Suggestion 4: Check the GPO settings in both gpedit.msc and regedit.exe:
In GPO: If User Configuration –> Administrative Templates
–> Desktop -> Prohibit User from manually redirecting Profile Folders
is enabled, please disable it. Don’t forget to force update the policy changes: run command
gpupdate /force as admin.
In regedit: if DisablePersonalDirChange is set to 1 under
HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer, please change it to 0 and start the SkyDrive to check the results.
At the end, we can’t assure that these suggestions can fix all such
issues. If you need further help, it’s ok to feedback here or submit a new thread with the
SkyDrive.exe.err.**.log under C:\Users\[Your name]\AppData\Local\Microsoft\SkyDrive\logs
uploaded for research.

I wrote a blog post back in January which describes a similar issue with the SkyDrive / OneDrive app in Windows 8.1 and how to resolve it at
http://richardjgreen.net/roaming-profiles-windows-8-1-skydrive-app/.
Hope this helps somebody.
Richard Green | MCSA 2012, MCSE 2003, MCTS Desktop Virtualization, VCP5-DV http://richardjgreen.net

Error while runnning autoconfig on apps tier during upgrade

Hi,
Error while runnning autoconfig on apps tier during upgrade from 11.5.9 to 11.5.10.2
below is the error message.
Enter the APPS user password :
The log file for this session is located at: /u01/app/tinst/tinstappl/admin/TINST_dba5/log/05031134/adconfig.log
AutoConfig is configuring the Applications environment...
AutoConfig will consider the custom templates if present.
Using APPL_TOP location : /u01/app/tinst/tinstappl
Classpath : /u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/jre/lib/rt.jar:/u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/lib/dt.jar:/u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/lib/tools.jar:/u01/app/tinst/tinstcomn/java/appsborg2.zip:/u01/app/tinst/tinstcomn/java
Using Context file : /u01/app/tinst/tinstappl/admin/TINST_dba5.xml
Context Value Management will now update the Context file
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/OracleDriver
at oracle.apps.ad.util.DBUtil.registerDriver(DBUtil.java:153)
at oracle.apps.ad.util.DBUtil.<init>(DBUtil.java:102)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.getDBConnection(FileSysDBCtxMerge.java:759)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.initializeParams(FileSysDBCtxMerge.java:147)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.setParams(FileSysDBCtxMerge.java:128)
at oracle.apps.ad.context.CtxValueMgt.mergeCustomInFiles(CtxValueMgt.java:1762)
at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:1579)
at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:709)
Caused by: java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 8 more
ERROR: Context Value Management Failed.
Terminate.
The logfile for this session is located at:
/u01/app/tinst/tinstappl/admin/TINST_dba5/log/05031134/adconfig.log
Please let me know your suggestions to resolve this issue.
Regards,
Sreenivasulu.

Hi,
DB tier autoconfig was successfully completed.
We have already checked the above mentioned metalink ID's, but still the issue is same.
Can you please advice any other solutions.
Regards,
Sreenivasulu.

Error during Upgrade from 4.6c to ECC 6.0

Hi All,
We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table. Please kindly help as early as possible. The upgrade process is stuck.
Regards
Anil Kumar K

Hi Anil,
Is this issue fixed? Can i know how you fixed it?
replied to your message Re: How to adopt the index changes during upgrade.
Thanks,
Somar

Issue installing/upgrading to ITunes 10.6.1.7

Im having an Issue installing/upgrading to iTunes 10.6.1.7 When upgrading it would not istall and tell me to go to Tools>Download manual. I also had an issue with my IPod touch not showing up in iTuens all of a sudden. So figuring the two problems were related I uninstalled iTunes (cleaned my itues folder in my C drive also) with hopes installing it fresh would work and now when I install 10.6.1.7 I get the following in a pop-up window "The installer encountered errors before iTunes could be configured. Errors occurred during installation. Your system has not been modified. Please run the installer again, or click Finish to exit."
Anyone know what the issue is?

Try the following steps:
1. Go to Microsoft website to fix install and Unistall problems. Click "Run now" from Fix it to remove all iTunes & related installer files:
http://support.microsoft.com/mats/Program_Install_and_Uninstall
Be aware that Windows Installer CleanUp Utility will not remove the actual program from your computer. However, it will remove the installation files so that you can start the installation, upgrade, or uninstall over.
2. You should remove all instances of iTunes and the rest of the components listed below:
it may be necessary to remove all traces of iTunes, QuickTime, and related software components from your computer before reinstalling iTunes.
Use the Control Panel to uninstall iTunes and related software components in the following order:
iTunes
QuickTime
Apple Software Update
Apple Mobile Device Support
Bonjour
Apple Application Support
Follow the instructions from Apple article listed here: http://support.apple.com/kb/HT1923 to remove all components
3. Reboot your computer. Next, download iTunes from here:http://www.apple.com/itunes/download/ and install from scratch

Can we activate Classic General Ledger in ECC6.0 during upgrade from 4.6C

Dear SAP Gurus,
Greetings
My Client's technical team had upgraded their system from 4.6C to ECC6.0 and they had activated classic GL instead of New GL. And they had also activated classic withholding tax in place of Extended Withholding tax.
They are facing some error during posting of transactions (like generation of excise invoices, posting of WHT transactions, etc.) I told that it can be a reason of not activating New GL.
Is my understanding correct...?? Can we activate classic GL during upgrade from 4.6C to ECC6.0...??
In case of a new client built (with ECC6.0), can we activate the classic GL instead of the New GL..??
Does the system will work correctly in the long run if they had activated classic GL and classic WHT...??
Please clarify. Thanks in advance for your time and efforts
Regards,
Chaps
P.S. Points will be awarded for answers !!

Hi,
I think that you should read long text of OSS note 999614 carfully and you are
aware of the fact that you will have additional migration efforts in
case you need to migrate to new G/L later on.
In case you are convinced that this is the best way please feel free
to deactivate new G/L as described in note 999614.
Please make sure that you deactivate new G/L in all clients of your
new system in case there were already client copies done.
Yes this is possible and I would not automatically assume that
error during posting of transactions are due to New GL not being activated.
Note 756146 documents the issue and possible repercussions
of using Classic GL.
In the case of a new installation the new G/L accounting
is active by default in ERP. In principle, the use
of the classic GL is also possible for new customers, however,
SAP does not recommend it since this requires an additional
migration expense in later years.
Regards,
Aidan

Issues during upgrade - SPDD

Similar Messages

Maybe you are looking for