Transport between BI 32bit OS and BI 64bit OS

We are in the process of migrating our current 32bit BI 7.0 to 64bit .
While migrating it will happen that our ie. Dev will be migrated to 64bit , but we may have development that we need to migrate to Prdn thru QAS that will both be @ 32bit OS.
Is this possible?
Thanks
Maria

Ok, yes, in SQL going from 32 to 64 can be done also using detach/attach procedure as per note 666805 but it is just a matter of taste.
I don´t think you will face any problem at all in mixed environments using SQL server, Oracle is more complex and don´t have any problem (my personal experience). Remember that comunications won´t have nothing to do with 32 or 64 bits, also transports are import procedures so if you do move SQL doing export/import procedure, a transport for sure won´t have any problem either.
Just keep all systems at the same SP level, kernel will be different but if you keep tp and R3trans at similar levels you won´t have problems
Good luck
Edited by: AC on Jan 22, 2009 4:13 PM

Similar Messages

I have installed the patch for output. it still doesn't work i am running windows 8.1 i have tryed the 32bit patch and the 64bit patch it still will not show up in workspace.

I am running Windows 8.1 i have installed the 32bit patch and the 64bit patch and neither one works. there is nothing in the workspace folder to delete. HELP!!! college student and campus running mac computers.

I am having the exact same problem and have tried everyone thing it is driving me crazy if you hear of anything that works let me know i would be very grateful.

Uninstall labview 32bit version and keep 64bit version

How do I uninstall the 32bit version of LV2009 and keep the 64bit version operational?
Solved!
Go to Solution.

Labview 64bit and 32 bit versions are indipendent. It is important to note that not all modules are 64 bit compatible.
Below are a few web pages with FAQs on the differences between labview 64bit and 32 bit.
http://zone.ni.com/devzone/cda/tut/p/id/10339
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98?OpenDocument

Documentation if 32bit client and 64bit client can coexist on 64bit system

Dear all,
I have read that I am not the first guy how try to install a 32bit client and a 64bit client (multiple homes) on 64bit system, but I still couldn't find something about this issue in the official Oracle Documentation.
Can anybody please give me a hint or a link where I can find something written in the official Oracle Documentation if a 32bit client and a 64Bit client can coexist on 64Bit system ...
Thanks in advance!

Could not find anything in official documentation (may be my search is not comprehensive enough).
However, you can just get in touch with Oracle support (I don't know if you need to raise SR for this) and ask them if it will work. To my knowledge, it would work under 32 bit emulation mode but results cannot be guaranteed.

Re: Satellite A200-1DY: Is there difference between BIOS 32bit & 64bit

I have Satellite A200 laptop and i have a doubt and is if there are diferences between Vista 32 and 64 Bios. Or is the same Bios?
My question is because in the last days i installed Home Premiun 64bit but my Bios is for Vista 32bit but every works fine on laptop.
Should i change the Bios for 64bits or should i let 32 bits Bios?
thanks

Hi again ;)
I think there is a difference between both BIOS versions; 32bit and 64bit but please dont ask me what the difference exactly is. ;)
I didnt find any details regarding the differences.
I assume the BIOS 64bit supports some advantages of the 64bit CPUs and the 64bit software but this is only a assumption
However, I think you dont need to switch to the 64bit BIOS version if your notebook run stable and trouble free using the 32bit version.
Greetings

Help me i cant install itunes on my windows 7 enterprise i try installing 32bit and it says that i need the 64bit but then in need the 32bit to use the 64bit please help!!!!

help me i cant install itunes on my windows 7 enterprise i try installing 32bit and it says that i need the 64bit but then in need the 32bit to use the 64bit please help

Hi there,
I would recommend taking a look at the troubleshooting steps found in the article below.
Trouble installing iTunes or QuickTime for Windows
http://support.apple.com/kb/HT1926
-Griff W.

Diff between stock transfer order and stock transport order

pls any body tell me diff between stock transfer order and stock transport order .is both are use for same pursose?pls explain

Check
very imp stock transfer and stock transport order

Difference between work bench request and transport of copies

hi-- what is the difference between wrokbench request and transport of copies. when it comes to overwrite originals etc. thanks
i am transporting from production to development and i need to make transport of copies of that workbench request, why i need to do this?

Workbench request - created in the 'source system' where the object was first created. Each object has a 'source system' attribute (table TADIR).
Copies - When transporting from a system other than the 'source system'.
The basic idea is that the 'source system' is the place where an object shall be changed (using a workbench request), while copies can be moved from other systems as well. You can ofcourse override this check.

Automation of transports between DVL and QAS environments

Hi,
Does anyone know how to automate the transports between the DVL and QAS environment ? When we release a transport in the DVL environment, we would like this transport to be copied in the QAS environement automatically, without having to copy it manually from DVL to QAS.
Thanks,
Julien

Hi
if this is generally about transporting PI content through the landscape then your solution is very likely to use CTS as transport system for PI. Further information can be found on https://wiki.sdn.sap.com/wiki/display/SL/SoftwareChangeManagement
Especially the section 'What is CTS' and 'SAP NetWeaver Exchange Infrastructure (XI / PI)' will be interesting.
If you are already using CTS and the question is if and how the automation can be configured then the answer is: yes, it can and it has to be done in the same way as for ordinary ABAP transport - even for PI content - via a scheduling.
Regards
Frank
Edited by: Frank Misch on Apr 29, 2009 4:31 PM

Difference between Netweaver 7 SR2 and Netweaver 7 SR3

Guys,
Can anyone tell me the difference between Netweaver 7 SR2 and Netweaver 7 SR3, I have a question out with SAP regarding the supportability of SCM 5.1 on Windows 2008.
The response I got back was that SCM 5.1 is based on Netweaver 7 SR2, but it was my understanding that the SR designation was for the level of support packs and kernel upon vanilla installation. Have I missed something fundamental, because my SCM installation is patched to the highest level and therefore surpasses the patch and kernel levels provided by Netweaver 7 SR3.
TIA
Chris

Hello Chris,
The main difference between these releases is the initial SP level that comes with each media kit:
NetWeaver 7.0 SR3: 14
NetWeaver 7.0 SR2: 9
NetWeaver 7.0 SR1: 6
For more details, you can check note:
#789220 Support Package level for NetWeaver Installations/Upgrades
Other differences relate to the (new) installer with some bugs corrections and a few additional features and restrictions:
- the Unicode restriction in SR3: "Only Unicode support for new installations" - "Every newly installed SAP system is a Unicode system. However, non-Unicode is still supported for copied and upgraded systems." So a new install based on SR3 must be UNICODE. On the other way, if you upgrade your, say, SR1 system to SR3, you can still run it NON-UNICODE.
- SR3 supports only 64bit new installs on the Central Instance. However, if you need to add dialog instances (application servers), they can be 32bit ones (albeit 64bit is always recommended). When upgrading your system from SR1 to SR3 (for example), you can skip this restriction. That is, you can keep your CI in 32bit, although this is highly not recommended.
A common workaround for these restrictions (if you want to keep your system NON-UNICODE and/or if you want to keep it 32bit) is to:
1) Install a SAP NetWeaver 7.0 SR2 (SAP ERP 2005 SR2, SAP CRM 5.0 SR2, SAP SCM 5.0 SR2, SAP SRM 5.0 SR2) system.
2) Patch this system to SAP NetWeaver 7.0 SR3 (SAP ERP 6.0, SAP CRM 5.0 SR3, SAP SCM 5.0 SR3, SAP SRM 5.0 SR3).
There are more features / restrictions on the installation guides for SR3 in section: "1.1 New Features"
Also, there is many more minor differences like, for example, that you can only install a SAP system in a Windows 2008 from NetWeaver 7.0 SR3 and up - see note #1054740.
I hope this information helps.
Best regards,
Tomas Black

What are differences between the target tablespace and the source tablespac

The IMPDP command create so manay errors. But the EXAMPLE tablespace is transported to the target database successfully. It seems that the transported tablespace is no difference with the source tablespace.
Why create so many errors?
How to avoid these errors?
What are differences between the target tablespace and the source tablespace?
Is this datapump action really successfull?
Thw following is the log output:
[oracle@hostp ~]$ impdp system/oracle dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Import: Release 10.2.0.1.0 - Production on Sunday, 28 September, 2008 18:08:31
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM"."SYS_IMPORT_TABLESPACE_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_TABLESPACE_01": system/******** dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "OE"."CUSTOMERS" ("CUSTOMER_ID" NUMBER(6,0), "CUST_FIRST_NAME" VARCHAR2(20) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE, "CUST_LAST_NAME" VARCHAR2(20) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE, "CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" , "PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" , "NLS_LANGUAGE" VARCHAR2(3), "NLS_TERRITORY" VARCHAR2(30), "CREDIT_LIMIT" NUMBER(9,2), "CUST_EMAIL" VARCHAR2(30), "ACCOUNT_MGR_ID" NU
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "IX"."ORDERS_QUEUETABLE" ("Q_NAME" VARCHAR2(30), "MSGID" RAW(16), "CORRID" VARCHAR2(128), "PRIORITY" NUMBER, "STATE" NUMBER, "DELAY" TIMESTAMP (6), "EXPIRATION" NUMBER, "TIME_MANAGER_INFO" TIMESTAMP (6), "LOCAL_ORDER_NO" NUMBER, "CHAIN_NO" NUMBER, "CSCN" NUMBER, "DSCN" NUMBER, "ENQ_TIME" TIMESTAMP (6), "ENQ_UID" VARCHAR2(30), "ENQ_TID" VARCHAR2(30), "DEQ_TIME" TIMESTAMP (6), "DEQ_UID" VARCHAR2(30), "DEQ_
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "SH"."CUSTOMERS" 9.850 MB 55500 rows
. . imported "SH"."SUPPLEMENTARY_DEMOGRAPHICS" 695.9 KB 4500 rows
. . imported "OE"."PRODUCT_DESCRIPTIONS" 2.379 MB 8640 rows
. . imported "SH"."SALES":"SALES_Q4_2001" 2.257 MB 69749 rows
. . imported "SH"."SALES":"SALES_Q1_1999" 2.070 MB 64186 rows
. . imported "SH"."SALES":"SALES_Q3_2001" 2.129 MB 65769 rows
. . imported "SH"."SALES":"SALES_Q1_2000" 2.011 MB 62197 rows
. . imported "SH"."SALES":"SALES_Q1_2001" 1.964 MB 60608 rows
. . imported "SH"."SALES":"SALES_Q2_2001" 2.050 MB 63292 rows
. . imported "SH"."SALES":"SALES_Q3_1999" 2.166 MB 67138 rows
Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "EXAM_03"
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_LNAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_EMAIL_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"PM"."PRINTMEDIA_PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_CREDIT_LIMIT_MAX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_ID_MIN" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"PM"."PRINTMEDIA__PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type CONSTRAINT:"IX"."SYS_C005192" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUSTOMERS_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_LNAME_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_EMAIL_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"PM"."PRINTMEDIA_PK" creation failed
Processing object type TABLE_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39112: Dependent object type REF_CONSTRAINT:"OE"."CUSTOMERS_ACCOUNT_MANAGER_FK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
ALTER TABLE "OE"."ORDERS" ADD CONSTRAINT "ORDERS_CUSTOMER_ID_FK" FOREIGN KEY ("CUSTOMER_ID") REFERENCES "OE"."CUSTOMERS" ("CUSTOMER_ID") ON DELETE SET NULL ENABLE
ORA-39112: Dependent object type REF_CONSTRAINT:"PM"."PRINTMEDIA_FK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUST_UPPER_NAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_UPPER_NAME_IX" creation failed
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
ORA-39112: Dependent object type PROCACT_INSTANCE skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
BEGIN
SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_SIGNATURE_TABLE('AQ$_ORDERS_QUEUETABLE_G');COMMIT; END;
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCDEPOBJ
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_V" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_N" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_R" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_E" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Job "SYSTEM"."SYS_IMPORT_TABLESPACE_01" completed with 63 error(s) at 18:09:14

Short of trying to then reverse-engineer the objects that are in the dump file (I believe Data Pump export files contain some XML representations of DDL in addition to various binary bits, making it potentially possible to try to scan the dump file for the object definitions), I would tend to assume that the export didn't include those type definitions.
Since it looks like you're trying to set up the sample schemas, is there a reason that you wouldn't just run the sample schema setup scripts on the destination database? Why are you using Data Pump in the first place?
Justin

How to get the link between mara, ausp, cawn and cawnt tables

hello ABAPERS
i have got a requiremet in that i have to get the relation .
how to get the link between mara, ausp, cawn and cawnt tables and also type how can we get link between char value and char description in cawn and cawnt tables through ausp and mara tables.
I would be very thankful for ur help in advance.
Thanks & Regards.
soni

Hi,
Sample report using the linkage between tables;
report batch_char no standard page heading
                          line-size 132
                          line-count 58(1)
                          message-id mm.
       Report by Batch Characteristic                                *
Description          : Report by Batch Characteristic                *
Declaration for Tables
tables: mara,    " Material Master
        mard,    " Storage Location Data for Material
        t001w,   " Plants/Branches
        t001l,   " Storage Locations
        cabn,    " Characteristics
        inob.    " Link between Internal Number and Object
Declaration for Constants
constants : c_klart like ausp-klart value '023',     " Class Type
            c_obtab like inob-obtab value 'MCH1',    " Database Table
            c_flag type c          value 'X',       " Flag
            c_c23   type i          value '23',      " Ratio
Constants for Ratio Categories
            c_13    type p decimals 2 value '13.00', " For Ratio 13
            c_1499 type p decimals 2 value '14.99', " For Ratio 14.99
            c_15    type p decimals 2 value '15.00', " For Ratio 15
            c_1699 type p decimals 2 value '16.99', " For Ratio 16.99
            c_17    type p decimals 2 value '17.00', " For Ratio 17
            c_1899 type p decimals 2 value '18.99', " For Ratio 18.99
            c_19    type p decimals 2 value '19.00', " For Ratio 19
            c_2099 type p decimals 2 value '20.99', " For Ratio 20.99
            c_21    type p decimals 2 value '21.00', " For Ratio 21
            c_2299 type p decimals 2 value '22.99', " For Ratio 22.99
            c_23    type p decimals 2 value '23.00', " For Ratio 23
            c_g23(4) type c value '>=23',            " For Ratio >=23
            c_ratio(5) value 'RATIO',                  " For Ratio
Constants for Storing Selected item field information
            c_cursor1(15) value 'I_OUTPUT1-MEINS',   " For Selected Base
                                                     " Unit of Measure
            c_cursor2(15) value 'I_OUTPUT1-MATNR',   " For Selected Base
                                                     " Material Number
            c_cursor3(15) value 'I_OUTPUT1-MAKTX',   " For Selected Base
                                                     " Material Des.
            c_cursor4(15) value 'I_OUTPUT1-CLABS',   "For Selected Base
                                                     " Stock Value
            c_cursor5(15) value 'I_OUTPUT1-ATFLV',   " For Selected Base
                                                    " Char.Value (Ratio)
            c_cursor6(5) value 'C_G23'.
Declaration for Global Variables
data : g_exit type c,                            " Flag
       g_clabs1(16) type c,                       " Quantity
       g_clabs(18) type c,                       " Quantity
       g_cursor(15) type c,                       " Cursor field name
       g_matnr     type mara-matnr,               " Material Number
       g_werks     type mchb-werks,               " Plant
       g_atinn(30) type c.                        " Character.
Declaration for Internal tables
Internal table to hold Batch Stock data
data : begin of i_mchb occurs 0,
         matnr like mchb-matnr,      " Material Number
         werks like mchb-werks,      " Plant
         lgort like mchb-lgort,      " Storage Location
         charg like mchb-charg,      " Batch Number
         clabs like mchb-clabs,      " Stock Value
         meins like mara-meins,      " Unit of measure
         atflo like ausp-atflv,      " Char.Value (Ratio)
         atflv like ausp-atflv,      " Char.Value (Ratio)
       end of i_mchb.
Internal table to hold Secondary List data
data : begin of i_mchb1 occurs 0,
         werks like mchb-werks,      " Plant
         matnr like mchb-matnr,      " Material Number
         lgort like mchb-lgort,      " Storage Location
         charg like mchb-charg,      " Batch Number
         atinn like ausp-atinn,      " Char.Value
         clabs like mchb-clabs,      " Stock Value
         atflo like ausp-atflv,      " Char.Value (Ratio)
         atflv like ausp-atflv,      " Char.Value (Ratio)
       end of i_mchb1.
Internal table to get the Plant Name
data : begin of i_plant occurs 0,
         werks like t001w-werks,     " Plant
         name1 like t001w-name1,     " Name
       end of i_plant.
Internal table to get the Material Description
data : begin of i_makt occurs 0,
         matnr like makt-matnr,      " Material
         maktx like makt-maktx,     " Description
       end of i_makt.
Internal table to hold AUSP data
data : begin of i_ausp occurs 0,
         objek like ausp-objek,      " Object No
         atinn like cabn-atinn,      " Characteric value
         atflv like ausp-atflv,      " Characteristic Value
       end of i_ausp.
Internal table to hold output data
data : begin of i_output occurs 0,
         atinn like cabn-atinn,      " Characteric value
         werks like mchb-werks,      " Plant
         matnr like mchb-matnr,      " Material Number
         atnam like cabn-atnam,      " Characteristic
         atflv like ausp-atflv,      " Char.Value (Ratio)
         name1 like t001w-name1,     " Plant Description
         maktx like makt-maktx,      " Material Description
         clabs like mchb-clabs,      " Stock Value
         meins like mara-meins,      " Base Unit of Measure
       end of i_output.
Internal table to hold final Output data
data : begin of i_output1 occurs 0,
         atinn like cabn-atinn,      " Characteric value
         werks like mchb-werks,      " Plant
         matnr like mchb-matnr,      " Material Number
         atnam like cabn-atnam,      " Characteristic
         atflv(32) type c,           " Char.Value (Ratio)
         name1 like t001w-name1,     " Plant Description
         maktx like makt-maktx,      " Material Description
         clabs like mchb-clabs,      " Stock Value
         meins like mara-meins,      " Base Unit of Measure
       end of i_output1.
       Selection screen
selection-screen begin of block b1 with frame title text-001.
select-options: s_werks for t001w-werks obligatory, " Plant
                s_lgort for t001l-lgort,             " Stor.Location
                s_matnr for mara-matnr obligatory, " Material No
                s_atinn for cabn-atinn.              " Character.
selection-screen end of block b1.
At selection screen
at selection-screen.
Validation of Selection Screen Fields
perform validate_screen.
Start of selection
start-of-selection.
Get the Material and Batch Stock data from MARA and MCHB Tables
perform get_mat_stock_data.
Get the Material Group Text and Plant Name from T023T and T001W Tables
perform get_plant_grp_data.
Append the data into final Output Internal Table after getting the
Characteristic Values data from INOB and AUSP Tables
perform append_final_data.
Processing if the Characteristics contain 'RATIO'
perform collect_ratio.
End-of-Page
end-of-page.
write /1(125) sy-uline.
End of selection
end-of-selection.
if g_exit <> c_flag.
Display the Report Output data
    perform display_report.
endif.
Top-of-Page
top-of-page.
Write the Report and Column Headings
perform get_headings.
at line-selection
at line-selection.
if sy-lsind = 1.
    perform display_batch.
endif.
Top of page during line-selection
top-of-page during line-selection.
perform heading_seclist.
      Form validate_screen
Validation of Selection Screen fields
form validate_screen.
Validation of Plant
clear t001w.
if not s_werks[] is initial.
    select werks
      into t001w-werks
      from t001w
      up to 1 rows
      where werks in s_werks.
    endselect.
    if sy-subrc <> 0.
      message e899 with 'Enter Valid Plant'(002).
    endif.
endif.
Validation of Material Number
clear mara.
if not s_matnr[] is initial.
    select matnr
      into mara-matnr
      from mara
      up to 1 rows
      where matnr in s_matnr.
    endselect.
    if sy-subrc <> 0.
      message e899 with 'Enter Valid Material'(003).
    endif.
endif.
Validation of Storage Location
clear t001l.
if not s_lgort[] is initial.
    select lgort
      into t001l-lgort
      from t001l
      up to 1 rows
      where lgort in s_lgort.
    endselect.
    if sy-subrc <> 0.
      message e899 with 'Enter Valid Storage Location'(004).
    endif.
endif.
Validation of Characteristic Value
clear cabn.
if not s_atinn[] is initial.
    select atinn
      into cabn-atinn
      from cabn
      up to 1 rows
      where atinn in s_atinn.
    endselect.
    if sy-subrc <> 0.
      message e899 with 'Enter Valid Characteristic Value'(005).
    endif.
endif.
Validation of Plant, Material and Storage Location
clear mard.
select matnr werks lgort
    into (mard-matnr, mard-werks, mard-lgort)
    from mard
    up to 1 rows
    where matnr in s_matnr and
          werks in s_werks and
          lgort in s_lgort.
endselect.
if sy-subrc <> 0.
    message e899 with 'No Data found for the Selection Criteria'(006).
endif.
endform.                          "validate_screen
*&      Form get_headings
Write the Report and Column Headings
form get_headings.
data: l_repid type sy-repid.
l_repid = sy-repid.
call function 'Y_STANDARD_HEADING'
       exporting
            repid    = l_repid
            heading1 = sy-title.
write:/1(125) sy-uline.
format color col_heading on.
write : /1 sy-vline, 2(18)   'Material Number'(008) centered,
          20 sy-vline, 21(40) 'Material Description'(011) centered,
          61 sy-vline, 62(22) 'Ratio'(009) centered,
          84 sy-vline, 85(18) 'Quantity'(010) centered,
         103 sy-vline, 104(20) 'Base Unit of Measure'(015) centered,
         125 sy-vline.
write:/1(125) sy-uline.
format color off.
endform.                    "get_headings
*&      Form get_mat_stock_data
Get the Material and Batch Stock data from MARA and MCHB Tables
form get_mat_stock_data.
clear: i_mchb,i_output, i_output1.
refresh: i_mchb,i_output, i_output1.
select a~matnr       " Material Number
         b~werks       " Plant
         b~lgort       " Storage Location
         b~charg       " Batch Number
         b~clabs       " Stock Value
         a~meins       " Base Unit of Measure
      into table i_mchb
      from mara as a inner join mchb as b
      on amatnr eq bmatnr
      where b~matnr in s_matnr and
            b~werks in s_werks and
            b~lgort in s_lgort.
if sy-subrc <> 0.
    g_exit = c_flag.
    message s899 with 'No Data found for the Selection Criteria'(006).
    stop.
endif.
sort i_mchb by matnr werks lgort charg.
endform.                    " get_mat_stock_data
*&      Form get_plant_grp_data
Get the Material Group Text and Plant Name from T023T and T001W
form get_plant_grp_data.
if not i_mchb[] is initial.
Get the Plant Description from t001w Table
    clear i_plant.
    refresh i_plant.
    select werks      " Plant
           name1      " Name
      into table i_plant
      from t001w
      for all entries in i_mchb
      where werks = i_mchb-werks.
Get the Material Description from MAKT Table
    clear i_makt.
    refresh i_makt.
    select matnr      " Material number
           maktx      " Material Description
      into table i_makt
      from makt
      for all entries in i_mchb
      where matnr = i_mchb-matnr and
            spras = sy-langu.
    sort i_plant by werks.
    delete adjacent duplicates from i_plant comparing werks.
    sort i_makt by matnr.
    delete adjacent duplicates from i_makt comparing matnr.
endif.
endform.                   "form get_plant_grp_data.
*&      Form append_final_data
Append the data into final Internal Table
form append_final_data.
data : l_matbatch(28),
         l_tabix like sy-tabix.
if not i_mchb[] is initial.
    loop at i_mchb.
      l_tabix = sy-tabix.
      clear l_matbatch.
      concatenate i_mchb-matnr i_mchb-charg into l_matbatch.
      move-corresponding i_mchb to i_output.
Get the Plant Description from i_plant Table
        read table i_plant with key werks = i_mchb-werks binary search.
        if sy-subrc = 0.
          i_output-name1 = i_plant-name1.
        endif.
Get the Material Description from i_makt Table
      read table i_makt with key matnr = i_mchb-matnr binary search.
      if sy-subrc = 0.
        i_output-maktx = i_makt-maktx.
      endif.
Get the Characteristic Values data from INOB and AUSP Tables
      clear inob.
      select single cuobj from inob
          into inob-cuobj
          where klart = c_klart and
                obtab = c_obtab and
                objek = l_matbatch.
      if sy-subrc = 0.
        select objek
               atinn
               atflv
           from ausp
           into table i_ausp
           where objek = inob-cuobj and
                 atinn in s_atinn   and
                 klart = c_klart.
        sort i_ausp by objek atinn.
        loop at i_ausp.
          clear cabn.
          select single atinn atnam from cabn
                     into (cabn-atinn,cabn-atnam)
                     where atinn = i_ausp-atinn.
          if sy-subrc = 0.
If the ratio value is between 13-14.99, display 13
            if cabn-atnam cs c_ratio.
              if i_ausp-atflv between c_13 and c_1499.
                i_mchb-atflo = i_ausp-atflv.
                i_mchb-atflv = c_13.
If the ratio value is between 15-16.99, display 15
              elseif i_ausp-atflv between c_15 and c_1699.
                i_mchb-atflo = i_ausp-atflv.
                i_mchb-atflv = c_15.
If the ratio value is between 17-18.99, display 17
              elseif i_ausp-atflv between c_17 and c_1899.
                i_mchb-atflo = i_ausp-atflv.
                i_mchb-atflv = c_17.
If the ratio value is between 19-20.99, display 19
              elseif i_ausp-atflv between c_19 and c_2099.
                i_mchb-atflo = i_ausp-atflv.
                i_mchb-atflv = c_19.
If the ratio value is between 21-22.99, display 21
              elseif i_ausp-atflv between c_21 and c_2299.
                i_mchb-atflo = i_ausp-atflv.
                i_mchb-atflv = c_21.
If the ratio value is greater than or equal to 23, display 23
              elseif i_ausp-atflv >= c_23.
                i_mchb-atflo = i_ausp-atflv.
                i_mchb-atflv = c_23.
              endif.           " Condition for RATIO values
            else.              " If characteristic does contain RATIO
              i_mchb-atflv = i_ausp-atflv.
            endif.
            i_output-atinn = cabn-atinn.
            i_output-atnam = cabn-atnam.
            i_output-atflv = i_ausp-atflv.
            i_mchb1-matnr = i_mchb-matnr.
            i_mchb1-werks = i_mchb-werks.
            i_mchb1-lgort = i_mchb-lgort.
            i_mchb1-charg = i_mchb-charg.
            i_mchb1-clabs = i_mchb-clabs.
            i_mchb1-atinn = i_ausp-atinn.
            i_mchb1-atflo = i_mchb-atflv.
            i_mchb1-atflv = i_ausp-atflv.
            append : i_output, i_mchb1.
            clear i_mchb1.
            modify i_mchb index l_tabix transporting atflo atflv .
          endif.
        endloop.
      endif.
    endloop.
endif.
Checking whether the table is filled or not
if not i_output[] is initial.
    sort i_output by atinn werks matnr atflv.
else.
    g_exit = c_flag.
    message s899 with 'No Data found for the Selection Criteria'(006).
endif.
Delete the records where RATIO is less than 13.
delete i_output where atnam cs c_ratio and atflv lt c_13.
endform.                    "append_final_data
*&      Form display_report
Display the Report Output data
form display_report.
data: l_tabix like sy-tabix.
loop at i_output1.
    l_tabix = sy-tabix.
At new Characteristic
     at new atinn.
      read table i_output1 index l_tabix.
      format color 1 intensified on.
      write: /1 sy-vline, 2(20) 'Characteristic Name:'(007),
             23(40) i_output1-atnam,
             125 sy-vline.
      format color off.
      format color 4 intensified on.
      write: /1 sy-vline, 2(20) 'Plant Name         :'(022),
             23(4) i_output1-werks, 29(30) i_output1-name1,
             125 sy-vline.
      format color off.
      write /1(125) sy-uline.
    endat.
    clear: g_clabs, g_clabs1.
    format color col_normal.
    write :/1 sy-vline, 2(18)   i_output1-matnr,
           20 sy-vline, 21(40) i_output1-maktx,
           61 sy-vline.
    if i_output1-atflv = c_c23.
      write: 62(22) c_g23 centered.
    else.
      shift i_output1-atflv left deleting leading space.
      write: 62(22) i_output1-atflv centered.
    endif.
    write: 84     sy-vline,
           103     sy-vline,
           110(5) i_output1-meins.
If the quantity value is negative
    if i_output1-clabs ge 0.
      write: 85(18) i_output1-clabs unit i_mchb-meins,
            125     sy-vline.
    else.
      i_output1-clabs = - i_output1-clabs.
      write i_output1-clabs unit i_mchb-meins to g_clabs1.
      condense g_clabs1.
      concatenate '(' g_clabs1 ')' into g_clabs separated by space.
      write: 85(18) g_clabs right-justified,
           125 sy-vline.
    endif.
    format color off.
    hide : i_output1.
    new-line.
At end of material
    at end of matnr.
      sum.
      move : i_output1-matnr to g_matnr.
      format color 3 intensified on.
      write /1(125) sy-uline.
      write :/1 sy-vline, 2(25) 'Total for Material      :'(012),
             28(18) g_matnr.
      if i_output1-clabs ge 0.
        write: 85(18) i_output1-clabs unit i_mchb-meins,
        125 sy-vline.
      else.
        i_output1-clabs = - i_output1-clabs.
        write i_output1-clabs unit i_mchb-meins to g_clabs1.
        condense g_clabs1.
        concatenate '(' g_clabs1 ')' into g_clabs separated by space.
        write: 85(18) g_clabs right-justified,
             125 sy-vline.
      endif.
      write: 125 sy-vline.
      format color off.
      write /1(125) sy-uline.
    endat.
At end of plant
    at end of werks.
      sum.
      move : i_output1-werks to g_werks.
      format color 3 intensified off.
      write :/1 sy-vline, 2(25) 'Total for Plant          :'(013),
             28(4) g_werks.
      if i_output1-clabs ge 0.
        write: 85(18) i_output1-clabs unit i_mchb-meins,
        125 sy-vline.
      else.
        i_output1-clabs = - i_output1-clabs.
        write i_output1-clabs unit i_mchb-meins to g_clabs1.
        condense g_clabs1.
        concatenate '(' g_clabs1 ')' into g_clabs separated by space.
        write: 85(18) g_clabs right-justified,
             125 sy-vline.
      endif.
      format color off.
      write /1(125) sy-uline.
    endat.
At end of characteristic
    at end of atinn.
      read table i_output1 index l_tabix.
      sum.
      format color 3 intensified on.
      write :/1 sy-vline, 2(25) 'Total for Characteristic:'(014),
             28(25) i_output1-atnam.
      if i_output1-clabs ge 0.
        write: 85(18) i_output1-clabs unit i_mchb-meins,
        125 sy-vline.
      else.
        i_output1-clabs = - i_output1-clabs.
        write i_output1-clabs unit i_mchb-meins to g_clabs1.
        condense g_clabs1.
        concatenate '(' g_clabs1 ')' into g_clabs separated by space.
        write: 85(18) g_clabs right-justified,
             125 sy-vline.
      endif.
      format color off.
      write /1(125) sy-uline.
    endat.
endloop.
endform.                    " display_report
*&      Form DISPLAY_BATCH
     Display the batch details for the seclected material            *
form display_batch.
Get the batch details for the selected material
get cursor field g_cursor.
if g_cursor = c_cursor1 or
     g_cursor = c_cursor2 or
     g_cursor = c_cursor3 or
     g_cursor = c_cursor4 or
     g_cursor = c_cursor5 or
     g_cursor = c_cursor6.
    format color 3.
    write: /1 sy-vline,
            2(17) 'Material Number :'(020),
           20(17) i_output1-matnr,
           94 sy-vline.
    format color off.
    write /1(94) sy-uline.
    loop at i_mchb1 where matnr = i_output1-matnr and
                          atinn = i_output1-atinn and
                          atflo = i_output1-atflv.
      format color col_normal.
      shift i_mchb1-charg left deleting leading '0'.
      write :/1 sy-vline, 2(16) i_mchb1-lgort centered,
             18 sy-vline, 19(17) i_mchb1-charg centered,
             36 sy-vline.
      if i_output1-atnam cs c_ratio.
        write: 37(29) i_mchb1-atflv
                       exponent 0 decimals 2 centered.
      else.
        write : 37(29) i_mchb1-atflv
                      exponent 0 decimals 0 centered.
      endif.
      write : 66 sy-vline, 67(27) i_mchb1-clabs unit i_mchb-meins,
              94 sy-vline.
      format color off.
    endloop.
    write /1(94) sy-uline.
else.
    message s899 with 'Invalid cursor position'(016).
    exit.
endif.
endform.                    " DISPLAY_BATCH
*&      Form HEADING_SECLIST
      Write the Column Headings for Interactive Report
form heading_seclist.
write /1(94) sy-uline.
format color col_heading on.
write :/1 sy-vline, 2(16) 'Storage Location'(021),
         18 sy-vline, 19(17) 'Batch Number'(017) centered,
         36 sy-vline, 37(29) 'Characteristic Value'(018) centered,
         66 sy-vline, 67(27) 'Quantity'(019) centered,
         94 sy-vline.
write /1(94) sy-uline.
format color off.
endform.                    " HEADING_SECLIST
*&      Form COLLECT_RATIO
      Display the Characteristic ratio data
form collect_ratio.
loop at i_output.
    clear g_atinn.
    i_output1-atinn = i_output-atinn.
    i_output1-atnam = i_output-atnam .
    i_output1-werks = i_output-werks.
    i_output1-name1 = i_output-name1.
    i_output1-matnr = i_output-matnr.
    i_output1-maktx = i_output-maktx.
    i_output1-clabs = i_output-clabs.
    i_output1-meins = i_output-meins.
    call function 'CONVERSION_EXIT_ATINN_OUTPUT'
         exporting
              input = i_output-atinn
         importing
              output = g_atinn.
    if g_atinn cs c_ratio.
If the ratio value is between 13-14.99, display 13
      if i_output-atflv between c_13 and c_1499.
        i_output1-atflv = c_13.
If the ratio value is between 15-16.99, display 15
      elseif i_output-atflv between c_15 and c_1699.
        i_output1-atflv = c_15.
If the ratio value is between 17-18.99, display 17
      elseif i_output-atflv between c_17 and c_1899.
        i_output1-atflv = c_17.
If the ratio value is between 19-20.99, display 19
      elseif i_output-atflv between c_19 and c_2099.
        i_output1-atflv = c_19.
If the ratio value is between 21-22.99, display 21
      elseif i_output-atflv between c_21 and c_2299.
        i_output1-atflv = c_21.
If the ratio value is greater than or equal to 23, display 23
      elseif i_output-atflv >= c_23.
        i_output1-atflv = c_23.
      endif.
      write i_output1-atflv to i_output1-atflv .
    else.
      write i_output-atflv to i_output1-atflv exponent 0 decimals 0.
    endif.
    collect i_output1.
    clear   i_output1.
endloop.
sort i_output1 by atinn werks matnr atflv.
endform.                    " COLLECT_RATIO
Reward if useful..
Regards,
Anji

Trying to use a java 32bit program in Arch 64bit

After giving up some time ago, I decided once more to try to run a commercial 32bit Java application in my Arch 64bit. The same program runs fine in a vm with Ubuntu 64bit. Also, I installed bin32-jre from aur and I messed up the jre.sh and jdk.sh scripts in /etc/profile.d/ and made it work, but then my native Java 64 bit programs won't run.
To sum up, is there a way to achieve the same Java compatibility that Ubuntu offers? What libs or packages do I have to install and how should I configure them to run every java program, no matter if it is 32 or 64 bit?
Thanks.

Awebb wrote:
Java applications are compiled to bytecode. This bytecode is interpreted by the JRE to run on your specific environment. I don't see how a Java application could be either "32bit" or "64bit". This is the big benefit of Java: Write your code, compile it and run it on every machine that has Java installed.
Let's try to run your "32bit Java application" on 64bit JRE. What errors do you encounter that make you think you need a different environment?
Truth is that things are not so simple. This application uses the SWT toolkit for its interface and has other dependencies besides jre (gtk is one for sure). I would be very grateful if you could download the fully functional demo version from here http://www.wordfast.com/zip/2.4.0.1/lin … nux.tar.gz and give it a try. If you can't do that, I can provide some logs. I am sure the problem is not how Java behaves but the way this app is developed and packaged. I have bought a license some years ago, but I still haven't managed to run it properly on any of my Arch machines and I just wait for the devs to take some action on this issue. I have also asked for help, but it seems that they take for granted that their Linux users use distros with mixed libs (like Ubuntu).
Anyways, thx for your reply.

Relationship between ERPi metadata rules and Data load rules

I am using version 11.1.1.3 to load EBS data to ERPi and then to FDM. I have created a Metadata rule where I have assigned a ledger from the Source Accounting Entities. I have also created a Data Load rule that references the same ledger as the metadata rule. I have about 50 ledgers that I have to integrate so I have added the source adapters that reference the Data Load rule.
My question is... What is the relation between the Meatdata rule and the Data load rule with the ledger? If you can specify only one Ledger per metadata rule, then how does FDM know to use another metadata rule with another ledger attached to it? Thanks!!!

Aksik
1 How freequently this activation problem occurs. If it is one time replicate the datasource and activate thetransfer structure( But in general as you know activation of transfer structure should be done automatically after transport of the object)
2 One thing for difference of time is environmental as you know in production system so many jobs will run at the same time so obiously system performance will be slow compare to Dev System. In your case both the systems are performing equally. You said in dev system for 50000 records half an hour and in production 200000 records 2hrs so records are more in Production system and it took longer time. If it is really causing problem then you have to do some performance activities.
Hope this helps
Thnaks
Sat

Transport between different releases

Hi,
Is it possible to have transports between two server with different releases,
one is on 701 and other is on 700,
pls advise.
Thanks

Hello Irfan,
Transport of customizing between diffeent releases is NOT supported. Also generated objects, which were generated by customizing, should NOT be transported between different releases.
SAP objects may NOT be transported between different releases (e.g. a table in an old release could have less fields than in the newer release and thus such a transport might delete data or if an abap calls a function module and in new release have one parameter more,then you get syntax errors if you transport only one of them from a system with the old release, ...).
So data loss and severe inconsistencies can happen if you transport SAP objects between different releases, or between systems with same release but different support package level or between systems with different addons or different add-on versions etc.
For pure customer objects (e.g. Z-tables, Z-programs, Y-tables, y-programs or objects in customer name space) it might be ok to transport them. But if e.g. your Z-table uses an SAP data element which has maybe been changed in the new release or does maybe no more exist, you can also get problems during transport of your z-table.
Data loss and severe inconsistencies can happen if you transport SAP objects between different releases, or between systems with same release but different support package level or between systems with different addons or different add-on versions etc.
Please check the following:
1090842   Composite note: Transport across several releases
1089083   Transports between Basis Releases 7.0* and 7.1*
556734    FAQ Transport: Setup and further information
Pay attention to point 5 and 6.
5. Are transports possible between systems with different Support Package versions?
6. Are transports possible between different R/3 releases?
Best Regards
Niraj

Transport between BI 32bit OS and BI 64bit OS

Similar Messages

Maybe you are looking for