Post BI 7.0 Technical Upgrade warning in Data Basis

Hi,
We have carried out technical upgrade to BI 7.0 . After upgrade, there were some inconsistency in Data basis which was removed thru System Synchronization program. Similarly consolidation area and source data basis also are consistent after saving.
However, when I carry out CHECK (right click and check) on Data Basis, it is throwing warning message for 0BCS_REFYR (master data) and 0BCS_DPER (master data)
The error message for one of them is re-produced below:
Critical change in content: InfoObject 0BCS_DPER (master data)
Message no. UCM0143
Diagnosis
Field Life of Depreciation (Amortization) in Periods is used in the data model of data basis Data basis ISB. The corresponding InfoObject 0BCS_DPER belongs to SAP BW Content, which is delivered with the consolidation system. However, the current definition of the InfoObject does not coincide with the delivered version.
In this case, the attribute With Master Data has been changed in the InfoObject definition. This change puts the consistency of the consolidation data model at risk.
Procedure
Adjust the definition of InfoObject 0BCS_DPER accordingly.
Always avoid changing InfoObjects that are delivered in SAP BW Content.
We have not made any changes to infoobject whatsoever. Please advise how to reslove this.
All BCS functions are working normally.
Best Regards,
UR

Warning Message is reproduced below:
''Critical change in content: InfoObject 0BCS_DPER (master data)
Message no. UCM0143
Diagnosis
Field Life of Depreciation (Amortization) in Periods is used in the data model of
data basis Data basis ISB. The corresponding InfoObject 0BCS_DPER belongs
to SAP BW Content, which is delivered with the consolidation system. However,
the current definition of the InfoObject does not coincide with the delivered version.
In this case, the attribute With Master Data has been changed in the
InfoObject definition. This change puts the consistency of the
consolidation data model at risk.
Procedure
Adjust the definition of InfoObject 0BCS_DPER accordingly.
Always avoid changing InfoObjects that are delivered in SAP BW Content
Best Regards,
UR

Similar Messages

Warning codes generated in UCCHECK   - Technical Upgrade - 4.0b to ECC 6.0

Hi SDN'ers ,
I am currently working on Technical Upgrade project from 4.0 b system to ECC 6.0 system . I am facing a
problem relating to the analysis of the warnings displayed whehn we run the UCCHECK for the client inventory by
checking the "Display lines that cannot be analyzed statically" option under the Selection-screen block
"Statements that cannot be analyzed statically" .Based on the warning codes generated during UCCHECK, they can
be classified into 12 different categories given below in the list ( Viz. ABB,MESSAGEG!C,MESSAGEG!D......MESSAGEG!P).The same are given below in the end
I want to know
- Which are the warning codes which need resolution so that the program does not encounter any runtime
errors or during Integration testing ?
- Do all the offset related errors (For example ;variable A = B+offset(length)
or variable A+offset(length) = B ) need resolution so that the program gives no runtime error.
- Also, do all statements where length is calculated using STRLEN also need changes ? I have seen offset length related warnings come under MESSAGEG!M warning code.
The objective of this is to make sure that the upgraded system ECC 6.0 in Australia ,when rolled out to
non-English speaking geographies in APAc such as Malaysia,Japan or China would only need translations and no ABAP Coding effort even when using languages such as Japanese which have double byte characters.
S.No.     Error Code     Message
1     ABB     Syntax Check Aborted
     ABB Total
2     MESSAGEG!C      check at runtime. at runtime.
           statement because of untyped or generic operands. It can only carry out this
          The system could not perform a static convertibility check on the current
     MESSAGEG!C Total
3     MESSAGEG!D      out this check at runtime. It can only carry out this check at runtime.
           to a table line because of untyped or generic operands. It can only carry out
          The system could not perform a static check on convertibility from a work area
     MESSAGEG!D Total
4     MESSAGEG!E      check at runtime. at runtime.
           defined by a "DATA" statement. .
           statement because of untyped or generic operands. It can only carry out this
          Field "ELEMENTN" is unknown. It is neither in one of the specified tables nor
          The system could not perform a static comparability check on the current
     MESSAGEG!E Total
5     MESSAGEG!F      operand "<FELD1>" for the current statement. .
     MESSAGEG!F Total
6     MESSAGEG!G      current statement on incompletely typed operand "<DATA>". .
     MESSAGEG!G Total
7     MESSAGEG!H      for the incompletely typed operand "<S>". . - - - - - - - - -
          The system cannot perform a static check on a character-type field data type
     MESSAGEG!H Total
8     MESSAGEG!I      incompletely-typed operand "<A>" in the current statement. .
          The system cannot perform a static check on a character-type data type for the
     MESSAGEG!I Total
9     MESSAGEG!J      "<%_1_SYSINI>" in the current statement to check whether the operand can be
          The system cannot perform a static check on incompletely-typed operand "VALUE"
     MESSAGEG!J Total
Early response wil be highly appreciated.

Hi Karthik
>
> 1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
>
SPDD is done in Upgrade ->Phase ACT_700
> 2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
>
At ACT_700 phase stop the upgrade and take a backup of the DB and the PUT<DIR> before starting the SPDD activity.
Make sure there are no pending tp request. Either release them or delete them.
All phase need to be completed successfully in PREPARE, before starting UPGRADE
Cheers
Shaji
Edited by: Shaji Jacob on May 5, 2008 9:23 PM

Issues during technical upgrade from version 4.6C to ECC 6.0

Dear All,
We have done a technical upgrade from version 4.6C to ECC 6.0 and encountered following issues -
In the t-code ABZE (acquisition with in house production) there is a check-box for reversal posting on screen with version 4.6C. However, this field is missing in ECC 6.0. Why so?
In the report s_alr_87012327, there is a field "only with creation block" in version 4.6C. However, this field is missing in ECC 6.0. Why so?
Request to kindly suggest the alternative to carry out the same in ECC 6.0.
Thanks in advance.
Regards,
Dhawal

Hi Akshya,
Please find answers below.
1) 4.6c is NON-UNICODE system, Can I upgrade it into ECC 6.0 UNICODE system?
Yes you can.
If you are on a single code page system then you can give a gap between your uprade and unicode conversion. There is no problem with the singlecode upgrade and conversion.
But if your system is MDMP then you will have to do the CUUC method that is both upgrade and unicode conversion together. Though you can give a gap and sign an disclaimer with SAP it is still not recomended way.
2) 4.6c does not have any ITS system installed. If we upgrade it to ECC6.0 ABAP only, then Can I activate WAS internal ITS?
Yes you can activate it.
3) 4.6c does not have any JAVA stack. When I upgrade it to ECC 6.0, can I upgrade it to dual stack (ABAP+JAVA)? If yes, then how?
After the upgrade and unicode conversion you can install the java stack.
Regards,
Ravi.

Technical upgrade from 4.7 to ECC 6.0

Experts,
1.We need to make Technical upgrade in HR from 4.7 to ECC 6.0 with OM,PA, -ve Time,Payroll, Recruitment (other Modules also upgraded).Kindly let us know what will haeepen for the following .
A.Configrations in SPRO
B.Previous database (Cluster table for previous Time and payroll run)
C.Master data of employees which is stored in Infotypes
2.Also Kindly let us know is there anything we need to take care after moving from 4.7 to 6.0

Hi Kumar,
Basically there needs to be a Transport established between 4.7 and ECC6.00 Version . You can create Transport request for those tables whose value remain same in 4.7 nad ECC6.00 But for tables having changes you need to create the Configuration.
1 more method applied by organization is a client copy of tables.
My suggestion would be like this :
1. Compare and Update Tables (from Configuration Handbook)
Pay Frequency
Define Period Modifiers
V_T549R
Define Date Modifiers
V_T549L
Check Payroll Accounting Area
V_T549A
Pay Scale Structure
Define EE Subgroup Grouping for PCR and Collective Agreement Provision (CAP)
V_503_B
Check Pay Scale Type
V_T510A
Check Pay Scale Area
V_T510G
Check Assignment of Payscale Structure to Enterprise Structure
V_001P_C
Define Default for Pay Scale Data
Feature - TARIF
Setup payroll period for Collective Agreement Provision
V_T510W
Revise Pay Scale Groups and Levels
V_T510
Enterprise Structure for Wage Type Model
T539A
Feature - LGMST
Revise Default Wage Types
V_T539A - already tested
Define Valuation of Base Wage Types
V_T539J
Legacy Data Transfer
T558B
T558D
Define Periods for import
T558B - already tested
Rates of Pay
T512W
Pay Scale Allowance Group
V_T7INA1
Assign Pay Scale Groupings for Allowances
V_T7INA3
Define Basic Codes
V_T7INB4
Statutory
Define Trust Details for Provident Fund
V_T7INF1
Assign Company Rates for Provident Fund
V_T7INF5
Define PF Trust Validity Period
V_T7INF7
Maintain Contribution Details for Provident Fund
Feature: 40EPF
V_T7INF3
Define Contribution Type for Statutory rates for Provident Fund
V_T7INF3 - already tested
Employees' State Insurance
V_511P_B
V_T511P
Maintain Number of Working Days in a Month
V_511K_B
V_T511K
Define Personnel Area and Subarea Groupings for ESI
V_T7INE1
Assign ESI Groupings for Personnel Area and Subarea
V_7IN0P_ESI
Maintain Contribution Rates for ESI
V_T7INE3
Assign Universal Contribution Groupings for Universal Contribution Type
V_T7INOP_ALL
Assign slab code for Universal Contribution Grouping
V_T7INU1
Assign Slab code and other parameters for each state of a universal type
V_T7INU3
Assign contribution Value for each slab
V_T7INU5
Maintain Eligibility Details for Superannuation
Feature - 40SAN
Tax and Professional Tax
Define Professional Tax Grouping Details
V_T7INP1
Maintain Method and Form Layout for Ptax Groupings
T596F
Maintain Re-Computation Behaviour of Tax related
Feature - 40MWT
Maintain Schema for Exemption on Medical Reimbursement / Insurance
V_T7INT9
Maintain Schema for Exemption of Child education and hostel allowance
V_T511K - already tested
V_T7INT9 - already tested
Bonus Act
T511K - already tested
T511P - already tested
One Time Bonus Tax
Copy Wage Types
V_T7INT9 - already tested
V_T7INA9
Define Compensation Area Feature
Feature - CAREA
Assign organizational assignment to Compensation Groups
Feature - CMGRP
Maintain Variant for Payroll Simulation
Feature - 16CVA
Maintain Payslip Variant
Feature - 16EVA
HRA/CLA/LTA
Define Accomodation Types
V_T7INT7
Company Loans
Maintain Loans Grouping
Feature - 40LGR
Mantain Loans Eligibility Checks and Limits
Feature - 40 LGR - already tested
Banking
Setup House Banks
V_T012
Bank Account
V_T012K
Define Sending Banks
Feature - DTAKT
Check Text Keys for Payment Transactions
V_T520S
General Ledger
Define Employee Grouping Account Determination
Feature - PPMOD
Define Symbolic Accounts
V_T52EK
V_T52EZ
2. Compare and Update Genaral Tables
1     T512W
2     T511K
3     T511P
4     TCURR
5     T030
2a. Compare and Update Additioanl PY-IN Tables
1     T7INTN TAN Number Maintainence
2     T7INA1 Pay scale grouping for allowances
3     T7INA3 Associating pay parameters to pay scale grouping
4     T7INA5 Wage type model for pay scale grouping for allowances
5     T7INA7 Reimbursements Allowances and Perks - base slabs
6     T7INA9 Reimbursement allowances perks - eligibility and calculation
7     T7INAA Salary year for pay scale grouping for allowances
8     T7INB1 Basic Wages
9     T7INB4 Basic Codes
10     T7INB5 Basic Codes for Allowance Groups
11     T7INB7 Basic slabs
12     T7INB8 Appraisal Criteria
13     T7INB9 Increment criteria
14     T7INC1 Car types master
15     T7INC3 Type and age eligibility for car schemes(COCS/OYCS)
16     T7INC5 Perk valuation for cars
17     T7INC7 Amount and number eligibility for car schemes(COCS/OYCS)
18     T7INC9 Conveyance allowance eligibilty
19     T7INCA Codes for Conveyance types
20     T7IND1 Dearness allowance consumer price index master
21     T7IND3 Dearness allowance consumer price index value
22     T7IND5 Dearness allowance basic slab details
23     T7IND7 Dearness allowance calculation rules
24     T7IND9 Dearness allowance consumer price index slabs
25     T7INE1 Personnel area / subarea grouping for employees' state ins.
26     T7INE3 Employees' state insurance contribution rates
27     T7INF1 Trust Master
28     T7INF3 Statutory rates for Provident fund
29     T7INF5 Company rates for Provident Fund
30     T7INF7 Trust details
31     T7ING1 Gratuity Details Maintenance
32     T7ING3 Gratuity ID Maintenance
33     T7ING5 Gratuity ID and Related Wage Types
34     T7INI0 Investment category limits
35     T7INI2 Investment technical description and text
36     T7INI4 Investment details
37     T7INI5 Sub section description
38     T7INI7 Sub section limit
39     T7INI8 Sub division description
40     T7INI9 Sub division details
41     T7INIA Deduction wage type for Sec 88
42     T7INIC Deduction wage type for Sec 80
43     T7INJ1 Section 24 Deduction Details Maintenance
44     T7INJ3 HR-IN: Loans Eligibility checks and limits
45     T7INJ5 HR-IN: Loans Dusbursement Schedule
46     T7INJ6 HR-IN : Loan Tranche Disbursement: Text for Events Code
47     T7INL1 Leave validation for LTA
48     T7INO1 One day salary deduction
49     T7INP1 Professional tax grouping details
50     T7INP3 Method and form layout for states
51     T7INP4 Professional tax slab amounts
52     T7INR1 Housing code for taxation
53     T7INR3 Percentage/amount for housing related constant
54     T7INR5 Housing related statutory constants for taxation
55     T7INR7 Codes for Housing Types
56     T7INR9 City category for housing type
57     T7INS1 Superannuation Details Maintenance
58     T7INS3 Superannuation ID
59     T7INS5 Superannuation-Wagetype Details
60     T7INT1 Slab codes for taxation
61     T7INT3 Taxation slabs
62     T7INT5 Personnel subarea grouping for Tax
63     T7INT7 Tax codes for tax exemptions
64     T7INT9 Taxability of wage types
65     T7INU1 State for Universal Grouping
66     T7INU3 Slab Codes for States
67     T7INU5 Contribution Value for Each Slab
68     T7INW1 Personnel area/subarea grouping for LWF
69     T7INW3 Labour welfare fund rates
70     T7INY1 Recovery of rounding off amounts
71     T7INZ1 Factor for retiral benefits
72     T7INZ3 Period of notice codes
3. Compare Payroll Schemas
1     Compare ECC5- to ECC6 standard schemas
2     Compare ECC5- to ECC6 customised schemas
4. Compare Personnel Calculation Rules (PCR)
1     Compare ECC5- to ECC6 standard PCR's
2     Compare ECC5- to ECC6 customised PCR's
B. Payroll Process
1     Generic Payroll Process
1.1     Simulate Payroll
1.2     Release Payroll
1.3     Start Payroll
1.4     Check result
1.5     Corrections
1.6     Remuneration statement
1.7     Simulate and test FI/CO postings
1.8     Simulate and Test Preliminary DME
1.9     Run Preliminary DME Program
2     Create a live posting run and create FI documents
C. Regression Testing (Variance Monitor)
1     Compare Payroll Results
Create a Excel with these contents and fill them up by saying the percentage of similarity and completetion.
Please let me know if this is usefull
Regards,
Prabha

BW Technical UpGrade

please search the forums before posting
Hi Experts,
Currently we are working on SAP BW 3.5 and my company is planning for BI 7.0 technical upgrade , can any one let me know what does we do in the technical upgrade - is it mostly related to Basis?? what should be done from BW Perspective.
Regards
Subbu

Hi Friend,
Check these:
[SAP BI Upgrade|http://service.sap.com/upgrade-bi]
[SAP NetWeaver 7.0 BI Upgrade Specifics|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742]
Regards
Hemant Khemani

11.5.10.2 to R12.1.1 upgrade : AutoPatch warning : Product Data File $APPL_TOP/admin/*prod.txt does not exist for product

Hello Sir,
OS version : AIX 6.1
DB version : 11.2.0.3
EBS version : 11.5.10.2
As a part of 11.5.10.2 to R12.1.1 upgrade, I am applying merged patch (9179588:R12.AD.B) with 9477107:R12.AD.B and patch 7461070(R12.AD.B.1 upgrade driver).
I can see AutoPatch warning messages during adpatch session as below so I have not yet started this merged patch. Please suggest.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drix10:/fmstop/patches/R1211AD/merge>adpatch
                     Copyright (c) 2002 Oracle Corporation
                        Redwood Shores, California, USA
                         Oracle Applications AutoPatch
                                 Version 12.0.0
NOTE: You may not use this utility for custom development
      unless you have written permission from Oracle Corporation.
Attention: AutoPatch no longer checks for unapplied pre-requisite patches.
You must use OAM Patch Wizard for this feature. Alternatively, you can
review the README for pre-requisite information.
Your default directory is '/fmstop/r12apps/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ?
AutoPatch records your AutoPatch session in a text file
you specify. Enter your AutoPatch log file name or press [Return]
to accept the default file name shown in brackets.
Filename [adpatch.log] : adpatch_u_merged_R12AD11.log
You can be notified by email if a failure occurs.
Do you wish to activate this feature [No] ?
Please enter the batchsize [1000] : 2000
Please enter the name of the Oracle Applications System that this
APPL_TOP belongs to.
The Applications System name must be unique across all Oracle
Applications Systems at your site, must be from 1 to 30 characters
long, may only contain alphanumeric and underscore characters,
and must start with a letter.
Sample Applications System names are: "prod", "test", "demo" and
"Development_2".
Applications System Name [FMSTEST] : FMSTEST *
NOTE: If you do not currently have certain types of files installed
in this APPL_TOP, you may not be able to perform certain tasks.
Example 1: If you don't have files used for installing or upgrading
the database installed in this area, you cannot install or upgrade
the database from this APPL_TOP.
Example 2: If you don't have forms files installed in this area, you cannot
generate them or run them from this APPL_TOP.
Example 3: If you don't have concurrent program files installed in this area,
you cannot relink concurrent programs or generate reports from this APPL_TOP.
Do you currently have files used for installing or upgrading the database
installed in this APPL_TOP [YES] ? YES *
Do you currently have Java and HTML files for HTML-based functionality
installed in this APPL_TOP [YES] ? YES *
Do you currently have Oracle Applications forms files installed
in this APPL_TOP [YES] ? YES *
Do you currently have concurrent program files installed
in this APPL_TOP [YES] ? YES *
Please enter the name Oracle Applications will use to identify this APPL_TOP.
The APPL_TOP name you select must be unique within an Oracle Applications
System, must be from 1 to 30 characters long, may only contain
alphanumeric and underscore characters, and must start with a letter.
Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".
APPL_TOP Name [drix10] : drix10 *
You are about to apply a patch to the installation of Oracle Applications
in your ORACLE database 'FMSTEST'
using ORACLE executables in '/fmstop/r12apps/apps/tech_st/10.1.2'.
Is this the correct database [Yes] ?
AutoPatch needs the password for your 'SYSTEM' ORACLE schema
in order to determine your installation configuration.
Enter the password for your 'SYSTEM' ORACLE schema:
The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS
Enter the ORACLE password of Application Object Library [APPS] :
AutoPatch is verifying your username/password.
The status of various features in this run of AutoPatch is:
                                           <-Feature version in->
Feature                          Active?   APPLTOP    Data model    Flags
CHECKFILE                        Yes       1          1             Y N N Y N Y
PREREQ                           Yes       6          6             Y N N Y N Y
CONCURRENT_SESSIONS              No        2          2             Y Y N Y Y N
PATCH_TIMING                     Yes       2          2             Y N N Y N Y
PATCH_HIST_IN_DB                 Yes       6          6             Y N N Y N Y
SCHEMA_SWAP                      Yes       1          1             Y N N Y Y Y
JAVA_WORKER                      No        1          -1            Y N N Y N N
CODELEVEL                        No        1          -1            Y N N Y N N
Identifier for the current session is 2987
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/eaaprod.txt
does not exist for product "eaa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/abmprod.txt
does not exist for product "abm".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/evmprod.txt
does not exist for product "evm".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ipdprod.txt
does not exist for product "ipd".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/zfaprod.txt
does not exist for product "zfa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/zsaprod.txt
does not exist for product "zsa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/cssprod.txt
does not exist for product "css".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/meprod.txt
does not exist for product "me".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/xnmprod.txt
does not exist for product "xnm".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/xncprod.txt
does not exist for product "xnc".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/xnsprod.txt
does not exist for product "xns".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/fptprod.txt
does not exist for product "fpt".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/okrprod.txt
does not exist for product "okr".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/cueprod.txt
does not exist for product "cue".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ibaprod.txt
does not exist for product "iba".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ozpprod.txt
does not exist for product "ozp".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ozsprod.txt
does not exist for product "ozs".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/rlaprod.txt
does not exist for product "rla".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/vehprod.txt
does not exist for product "veh".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/rhxprod.txt
does not exist for product "rhx".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/imtprod.txt
does not exist for product "imt".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ahmprod.txt
does not exist for product "ahm".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/okbprod.txt
does not exist for product "okb".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/okoprod.txt
does not exist for product "oko".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/xniprod.txt
does not exist for product "xni".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/jtsprod.txt
does not exist for product "jts".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/amfprod.txt
does not exist for product "amf".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/cunprod.txt
does not exist for product "cun".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
Reading database to see what industry is currently installed.
Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:
Code   Language                                Status
US     American English                        Base
Your base language will be AMERICAN.
Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.
Reading database for information about how products depend on each other.
Reading topfile.txt ...
Saving product information.
Trying to obtain a lock...
Attempting to instantiate the current-view snapshot...
No baseline bug-fixes info available. Will attempt next time.
     **************** S T A R T   O F   U P L O A D ****************
Start date: Sun Aug 04 2013 18:45:12
0 "left over" javaupdates.txt files uploaded to DB: Sun Aug 04 2013 18:45:12
0 patches uploaded from the ADPSV format patch history files: Sun Aug 04 2013 18:45:12
Uploading information about files copied during the previous runs ...
0 "left over" filescopied_<session_id>.txt files uploaded to DB: Sun Aug 04 2013 18:45:12
     ****************** E N D   O F   U P L O A D ******************
End date: Sun Aug 04 2013 18:45:12
Enter the directory where your Oracle Applications patch has been unloaded
The default directory is [/fmstop/patches/R1211AD/merge] :
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I checked under 11i $APPL_TOP/admin directory, I can see only one izuprod.txt file apart from applprod.txt.
drix10:/fmstop/fmstest/fmstestappl/admin>ls -lrt *prod.txt
-rwxr-xr-x    1 appltest dba          231650 Oct 30 2004 applprod.txt
-rwxr-xr-x    1 appltest dba            4966 Sep 21 2007 izuprod.txt
R12 code tree is newly installed so there is only applprod.txt
drix10:/fmstop/r12apps/apps/apps_st/appl/admin>ls -lrt *prod.txt
-rwxr-xr-x    1 appltest dba          226340 Jul 29 15:19 applprod.txt
Please suggest if I can ignore these warning to proceed with applying merged patch.

Technical Upgrade of the system from R/3 4.6 to ECC 6.0

Hi all i have a query regaring system upgrade:
Currently i have 2 systems R/3 4.6: Development(D1), Quality(Q1).
Now this systems needs to be upgraded to ECC 6.0.
First the D1 is going to be copied to a new development(D2).
Then D2 will be upgraded to ECC 6.0.
Here a unicode check and other required modification (code compatibility) to
all the customizing and workbench objects is to be done.
Now a copy of Q1 is to be done in new Quality(Q2).
My requirement is to determine all the transported requests from D1 to Q1 and
then transport the same from D2 to Q2 so that the unidcode complaint objects are transported and they overwrite in the new quality system.
Is this process feasible? If yes, How?
If anyone has worked on technical upgrade project, please suggest?
If any other information is required pls mention.

hi.
it sounds quite complicate for me...
you do not need to upgrade D2 to ECC 6.0 to be able to do the unicode checks. when you go to transaction se38 and select the report Z* you will find something like "unicode checks active" in the properties. if you enable them and check the reports you will find the problems regarding unicode...
i think there is another problem too. what are you doing with the unicode-enabled transports on system D2? you transport them to Q2 and what else? Are you transporting them to D1 too? If yes it is possible that you will overwrite the originals on D1 (it depends on your settings on system D2).
hope my answer helps...
regards,
martin

Technical Upgrade from R/3 4.6 to ECC 6.0

Hi all i have a query regaring system upgrade:
Currently i have 2 systems R/3 4.6: Development(D1), Quality(Q1).
Now this systems needs to be upgraded to ECC 6.0.
First the D1 is going to be copied to a new development(D2).
Then D2 will be upgraded to ECC 6.0.
Here a unicode check and other required modification (code compatibility) to
all the customizing and workbench objects is to be done.
Now a copy of Q1 is to be done in new Quality(Q2).
My requirement is to determine all the transported requests from D1 to Q1 and
then transport the same from D2 to Q2 so that the unidcode complaint objects are transported and they overwrite in the new quality system.
Is this process feasible? If yes, How?
Please suggest.

Hi Himansu,
I am making the assumption that you will as the final step upgrade your production to ECC 6.0 and then transport the Unicode corrected ABAP's from your Q2 environment into Prod, and then D2 and Q2 will become your new production support path while D1 and Q1 is removed. Is this assumption correct?
If so, then the next assumption for your plan is your reason for doing this is to keep the production support path D1->Q1->P1 intact while you are performing the upgrade and Unicode program testing in D2 and Q2.
I am also assuming that you are not doing a unicode upgrade/conversion at the same time, you are just making the code Unicode compliant to prepare for a future Unicode upgrade.
If so your plan will work just fine. To say it a little differently, here are the steps
1. Copy D1 to D2
2. Upgrade D2 to ECC 6.0
3. Run UCCHECK to test your code for compliance and to identify objects that need remediation
4. Fix the code that need fixing, and put it in transports with Q2 as your target system
5. Copy Q1 to Q2
6. Upgrade Q2 to ECC 6.0
7. Transport the converted code from step #4 to Q2
8. Perform thorough acceptance testing of the converted code
Now you can plan for your production cutover. While the above steps occurred, you either had a freeze on any changes to the production landscape, or you manually captured changes that was done in D1 in D2. The upgrade project is complex in itself and will need significant user testing assuming that it is only a technical upgrade with no additional or modified functionality.
If your D2 and Q2 was kept in sync, you can now upgrade your P1 system to ECC 6.0 (no need to copy), and configure your transport routes so that D2 and Q2 are now the new production support systems, then you transport the items in step #4 above from Q2 to the upgraded P1.
Regards
John
[SAP Unicode|http://www.sapunicodeupgrade.com|SAP Unicode]

Technical upgrade from 4.6C MDMP system to ECC 6.0 using CU & UC approach

Hi SAP Experts,
We are embarking on a project for Technical upgrade from SAP R/3 4.6C MDMP system to ECC 6.0 using the CU & UC approach for our Asian operations (comprising of India, Japan, Taiwan & Singapore).
Please share with me the Best Practices you followed in your projects, checklists, DOs, DONTs, typical problems you encountered and the possible safeguards, any other useful information, etc.
Since very little information is available from Organizations who have used the CU & UC upgrade approach successfully, I am raising this in SDN to share your experiences during the Technical upgrade.
All useful information will be surely awarded with suitable points.
Looking for your invaluable inputs which will be a BIG help for our project.
Best regards,
Rajaram

Hello Rajaram!:
It's a very big project, that you have to do in a lot of steps........
If you want sent me a email with the problems and you want.
Regards,
Alfredo.

Issues during technical upgrade from 4.6c to ecc 6.0

Hi
We are doing a technical upgrade from 4.6C to ECC 6.0. Some transactions in QM module when tested in ECC 6.0 test client give a abap termination message (or dump) and certain transactions like qs42,46, qa18, qs34 etc do not get executed (error = no entry foound for......) and similarly in PP-PI module transactions like C203 have similar problems, even though master data does exist. What should I look for? Can somebody pl. give details on configuration checks and the OSS notes from a functional point of view for a technical upgrade?
For certain transactions I get the error message - "Central system of distribution SM-P06CLNT430_TRUSTED is unreachable RFC destination SM_P06CLNT430_Trusted does not exist" - what does this mean?
thanks
BE

Hi,
1. Have you done successfull installation from 4.6C to ECC 6.0 at the time of PrePare ans SAPUP?
2. Check SP' for QM and PP-PI modules from http://service.sap.com/sp-stacks.
3. Configure RFC connections correctly, SM_<SID>CLNT<No>_Trusted automatically created, not manually.
http://service.sap.com/notes --> search for RFC trusted connections for Ecc 6.0
http://service.sap.com/upgrade.
Regards,
Srini Nookala

Technical Upgrade from XI 3.0 to PI 7.1

Hi,
My client is going for Technical Upgrade from XI 3.0 to PI 7.1 not fresh installation. They are asking for How best we can achieve this. I have gone through Decision making document and upgrade document from SAP. Apart from which please provide me the valuable Inputs like what measures we need to take care before and after upgrade as an XI developer. In our project about 90% of interfaces are having java mapping. will there be any changes to be done after upgrade.
I already gone through below link
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8085e299-718c-2a10-de94-928f62b763ce
https://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/40a0868a-9d40-2b10-8cb4-8e0c53b56655&overridelayout=true
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40a0868a-9d40-2b10-8cb4-8e0c53b56655
Thanks in advance
Venkatesh

you can use this document as your base - http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8085e299-718c-2a10-de94-928f62b763ce?quicklink=index&overridelayout=true
do an upgrade from XI 3.0 to PI 7.1
java mappings will still continue to work.
But you might have to modify some graphical mapping, java proxies and modules if any

Technical upgrade from 4.6c to 6.0ecc with unicode conversion

Hi Experts,
Can you explain me technical upgrade from 4.6c to 6.0ecc with Unicode conversion.
if u got any notes pls send it to [email protected]
vijay

Check these links. Search SDN with Term "Upgradation" you will get lot of links
http://help.sap.com/saphelp_nw04/helpdata/en/16/4b3c88170e11d6999d00508b6b8b11/frameset.htm
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0f9f37c-be11-2a10-3baf-d5d7de5fb78d
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/system%2blandscape%2bconversion
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/project%2bplanning%2b-%2bmdmp%2bsystem
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/communication%2binterfaces
Message was edited by: Jason Lax (Removed link to deleted content)

Config. comparision for technical upgrade

Hi ,
We are upgrading from 4.6c to ECC 6.0 ,this is a technical upgrade .
Do we need to compare the config. of 4.6c to ecc 6.0 ?
If yes then how do we go about it ?

Dear kedar landge,
Hope this helps you.
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh

Technical Upgrade & Testing

We are doing technical upgrade from 4.6C to ECC 6.0.
After we are through with the SPDD and SPAU modificaitons in the development environment, do we need to Functional Unit Test (by unit test, I mean complete fucntionality test) in there for all the objects in these SPAU and SPDD lists?
Or is there any other way I can get all the programs tested. I am asking cause we have about 3000 objects in the SPAU list and we need to work on the modifications within a span of 3-4 weeks only!
Any help is appreciated.

Hello Anand,
When upgrading from 4.6c to ECC 6 I would recommend complete functional unit test for all your company's business processes. This should include some kind of regression testing to ensure that existing functionality still works as well as the functionality that may have changed as indicated by the objects on the SPAU and SPDD lists.
Having said that I understand the reality of a short implementaion time. You may need to narrow your testing focus to just critical business processes. Or you could use SPAU to identify where major changes have occured. Either way this is not a support pack but a major upgrade and testing will be extensve.
I know that this is not a great help. Hope the upgrade goes well.
Regards
Greg Kern,

What production downtime should we expect during the technical upgrade?

Hi,
We are planning for a Upgrade from 4.7 to ECC 600, i need to know how can we able to calculate the downtime for the upgrade?
Thanks.

The production downtime is the period during the technical upgrade when the production system is out of service. The downtime period depends on various factors such as hardware power and size of the tables to be migrated, and is therefore contingent on each individual situation. SAP upgrade technology provides you with two strategy options: downtime-minimized strategy and
Resource-minimized strategy.
Characteristics of the downtime-minimized strategy:
Shorter production downtime
Parallel operation of production system and shadow system that enables the execution of as many upgrade tasks as possible during the uptime of the production system
Higher demand on system resources
Characteristics of the Resource-minimized strategy:
No parallel operation of production system and shadow system
Lower demand on system resources
Increased production downtime
SAP recommends that you perform the upgrade using the downtime-minimized strategy if a short production downtime is required.
For more details refer
http://service.sap.com/instguides
http://service.sap.com/erp
http://service.sap.com/erp-inst
Hope this will help you, do revert if you need further details.
Best Regards,
Sachin.

Post BI 7.0 Technical Upgrade warning in Data Basis

Similar Messages

Maybe you are looking for