* Weblog- RFID Scenario Installation—Installation *
If you have done your planning and preparation well, we can start the install of the SAP RFID scenario installation.
First download RFID-Enabled Supply Chain Execution Master Guide. PDF at http://service.sap.com/ibc .This is the first document we should read. We follow this master Guide to install the RFID scenario.
For the Backend system we can choose SAP ECC5.0, SAP R3470 or SAP R 34.6c. The difference is that if you install SAP ECC5.0, you do not need to install the Add-On AUTOID_INT_200_470 (AUTOID_ INT_200_ 46C) on the SAP R/3 Enterprise Server.
** In our labs’ installation, we chose R/3470, and AII2.1, SCM4.0 and XI3.0.
* Backend Option SAP R/3 Enterprise: Implementation Sequence *
* 1 * Installation/Integration of* SAP R/3 Enterprise 4.7x200: *
Install R/3 is an easy job, and I did not meet any difficulties, but there are some bugs or support packages I had to handle.
1) We use SQL server 2000 and we are planning to install a Unicode system, so you must install corrected MSSQL Collation (patching SQL2000_KB810185_8_00_0929.exe and INSTCOLL.exe), see* note<strong></strong> 600027*
2) After finishing install R/3 4.7, the igswd.exe can not start, and apply notes 824281 to solve this problem.
3) BTW, R/3 470 is running on WAS ABAP 6.20. And if you choose Unicode installation, use WAS620 Unicode kernel, and after installation, doing Unicode post-Installation first (*note 544623) *
2 Applying at least *SAP BASIS SP 37 *and SAP APPL SP 09 for the SAP R/3 Enterprise Server.
1) This is very important step; I strongly recommend that patching to the highest level of SAP R/3 SP (SAP kernel SP, BASIS SP, APPL SP).
2) Note 97620 tell you how to patch and the patching sequence.
3) Use tcode ”sgen” to compile ABAP code.
3 Install *Add-On AUTOID_INT_200_470 *on the SAP R/3 Enterprise Server.
1) Install Add-On according to *SAP Note 728372 *
2) Apply *SAP Note 689793 *
3) After install add-on AUTOID-INT for R/3, you can customize RFID in R/3. See SPRO IMG à logistic general à Supply Chain Planning Interface à Auto-ID backend integration.
* *
4 Installation/Integration of an *SAP Web AS 6.40 ABAP and Java system Support * 5 Installation/Integration of *SAP Exchange Infrastructure 3.0 SP05 or higher *Install the component * SAP Exchange Infrastructure. *
1) Just Follow the XI installation guide, and choose XI Adapter engine or XI plan J2SE Adapter engine, our installation choose Xi Adapter engine, and so we install another WAS J2EE Only.
2) If you meet errors in configuring java Web Start to use XI ID and IR, search the sap notes. This is a place which may cause some time.
Logon into XI ABAP system as “XISUPER”
Using tcode “sxmb_ifr” to start web browser to using IR and ID
6 Installation of the current *System Landscape Directory (SLD) content *on the SLD 
* *
7 Configuration of SAP Exchange Infrastructure 3.0 SP05 or higher
Configure the system as described in the guide below. System readiness can be
checked as described in SAP Note 817920.
Follow the Installation guide and notes.
8 Installation of *XI Content AUTO-ID 2.1 *on the SAP Exchange Infrastructure host.
1). Download this XI Content at: service.sap.com/swdc à Download à
Support Packages and Patches Entry by Application Group -> SAP
Application Components à SAP Auto-ID Infrastructure à SAP AII 2.1 à XI
Content AUTO-ID 2.1
2). Import the downloaded XI Content files as described in *SAP Note 705541. *
* *
XI integration Builder à XI Content Auto-ID 2.1
* *
9 Installation of *XI Content AUTOID_INT_200_470 *on the SAP Exchange Infrastructure host.
1). Download this XI Content at: service.sap.com/swdc à Download à
Support Packages and Patches à Entry by Application Group à SAP
Application Components à SAP Auto-ID Infrastructure à SAP AII 2.1
2). Import the downloaded XI Content files as described in *SAP Note 705541. *
Master Guide RFID-enabled supply chain execution
XI integration Builder à XI Content AutoID_INT_200_470
* *
10 Installation/Integration of an *SAP Web AS 6.40 ABAP and Java system Support *
* Package Stack 5 or higher * (J2EE Add-In) as prerequisite for the SAP Auto-ID Infrastructure 2.1 Add-On.
1) Install Java add-in after step 11 install Add-On SAP Auto-ID Infrastructure 2.1.
11 Installation of *Add-On SAP Auto-ID Infrastructure 2.1 *on the SAP Web AS 6.40 ABAP and Java system.
1) Apply SAP Note 777426 toinstall SAP Auto-ID Infrastructure 2.1.
2) We should install Add-On SAP Auto-ID Infrastructure 2.1 before client copy and install J2EE Add-In in step 10.
3) Because it is a Scenario installation, we’d better use the same SLD as configure in XI Installation.
4) Apply note 796216 to finish patching SAP AUTO-ID Infrastructure 2.1 Support Packages
5) AII 2.1 Java installation file and guide is in AII CD CD51030653, not in service.sap.com/instguides.
12 Optional: Installation of * SAP SCM Event Management *environment.
See section Implementation Sequence: Optional SAP SCM Event Management [ on
page 27 ]
1) Installation of *SAP R/3 Plug-In *2004.1 (or higher) on the Backend:
See *SAP Note 704564 *( R/3 Plug-In: Installation Delta-Upgrade PI 2004.1) and SAP
Service Marketplace at: service.sap.com/r3-plug-in
2) Installation of *SAP SCM server 4.1 *
SAP SCM
3) Installation of *XI Content *for SAP SCM 4.1 (consists of: XI Content SCM 4.1 / XI
Content SCM Basis 4.1 ) on the SAP Exchange Infrastructure host.
Import the downloaded XI Content files as described in *SAP Note 705541. *
4 Installation of * SAP SCM - Web Communication Layer 4.1 *
SAP SCM WCL
13 At end, If you install all the system in one server so the *SAPMMC *will look like WAS java port: default is 5<SID>00
Visual admin port: default is 5<SID>04
* BW *
WAS ABAP640 has BW. So if you installation WAS ABAP 640, you have already install BW, all you have do is copy a client from 000, and configure this client as BW client.
*SAP license *
If you do not have SAP license, you WAS java will stop 30 minute after server start. So install the server as soon as possible.
* Error: Operating system call recv failed (10054) *
* I couldn't solve this error by SAP notes and you can see details in this SDN. *
**
