Connecting Jco and ECC

Hi Gurus,
I just changed the ECC client 100 to 200 in Jco connections but Portal is not communicating with backend ECC clent 200. Please advice.
Regards
Francis.

Hi,
Changing the Joc connection is not working. Therefore I created a Jco connection again. It's working fine. I'm closing this forum.
Thanks
Francis

Similar Messages

RFC connection BI and ECC 6.0

Hi
I am trying to connect BI and ECC 6.0 at home on two different virtual machines for data extraction and practicing delta management ( they are on the same virtual network).
I am following these steps :
Step-by-step procedure to connect BI with ECCu2026
Define the logical system in R/3 using the transaction code SALE in both the systems (ECC and BI)
Assign Logical System to a client using transaction code SCC4 in both the systems (ECC and BI)
Setup the RFC Destination using transaction code SM59 in both the systems (ECC and BI)
Hit Transaction BD64 and Click Create model view - Enter the Short text u2013 Enter the Technical name u2013 Hit Execute - Distribution Model will be created and the technical name of the distribution model will be listed
Place the cursor on model created and and click Add message type button on the top right corner
Enter sender and receiver system IDs and select the correct message type assigned to the correct system
Distribute this model using Edit u2013 Model View u2013 Distribute
Select the receiver of the model view and proceed to distribute the model
Please note that the distribution of data model is not required to repeat in BI system as this step automatically replicates settings in BI
You have to generate partner profile for each system with which your system communicate using BD82
Outbound records are created in the partner profile for each outgoing message and inbound records are created for each incoming messages
You can view the partner profiles generated using the transaction code WE20
Message Types:
RSRQST: This message type is send by BI to R/3 while loading any data. This gives information about the data source, selection condition and other BI settings to R/3. As and when a load is started in BI, RSRQST message type is sent to R/3 requesting for data.
RSINFO: Once R/3 receives RSRQST message from BI, it sends an acknowledgment message type to BI informing about the status of the request. That is whether the request can be handled or not by R/3. It also gives information about how many data packages are being send and what is the total number of records extracted for the given data source and selection.
RSSEND: After sending a positive acknowledgement to BI, R/3 starts the extraction job and starts collecting data in data IDocs. This message type carries the actual data with it into the BI system.
My question is that : Do i know need to create three model views for these three message types?? Are these steps sufficient?
Please let me know if some other things needs to be followed or U know more simpler way to RFC connect so that I can pull data from ECC into BI and practice delta management.
Thanks
Edited by: max.sap on Apr 28, 2011 8:24 AM

Hi Niru,
Have you created a
[RFC destination in NW Administrator?|http://help.sap.com/saphelp_nwce10/helpdata/en/5a/97a066223e440b8ead3da027b17d9e/frameset.htm]. Have you created a [BI System connection?|http://help.sap.com/saphelp_nwce10/helpdata/en/7e/6dbcea3700452195e3bddaa47c5906/frameset.htm]
Best regards,
Dharmi

Cofig guide for connecting CRM and R3 system

Can anyone provide full cofiguration guide for connecting CRM and R3 system from end to end.
also complete information about bdocs settings in Adminstration console.
regards,
Sunil

Hi
Please follow the link
http://help.sap.com/saap/sap_bp/CRM_701_XX/Html/index.htm
then go to the following hyperlinks
B01: CRM Generation
B09: CRM Customizing Replication
C03: CRM Master Data Replication
Meticulous follow these three documents then you will be able to connect CRM AND ECC systems and will be able to perdorm initial load of customers, materials etc
please let me know if you have any issues
thanks
Ananda kumar karri

RFC connection error between BW 3.5 and ECC 6.0

Hi gurus,
We've defined an RFC destination between BW 3.5 and ECC 6.0. Connection test (SM59) is ok, but authorization one fails and ALEREMOTE users block. These users on both systems have good profiles. We look ST22 and find a runtime error on CALL_FUNCTION_REMOTE_ERROR. We've cleaned source system on BW and RFC destination and we've created one more time, but error doesn't disappear. We've looked OSS but don't find anything.
Any idea? Is there any other place (users, RFC) where we have to change user password on system?
Thanks a lot!
Regards,
Iván.
Edited by: Iván Cabezas Castillo on Nov 6, 2009 12:09 PM

Solved!
This is because of the incompatibility of password handling between
640 and 700 systems.
We have to use a maximum 8 character long password with only capital letters (numbers are also allowed) for the user "ALEREMOTE".
1. Change the password for the user in SAP R/3.
2. Maintain the password in SAP BW for the RFC destination (transaction SM59 - Logon/Security tab)
3. Authorization test is now successful.
(SM59 - Test - Authorization).
Regards!

Connectivity between SAP ECC system and SAP BI

Connectivity between SAP ECC system and SAP BI
Hi BI-experts!
I would like to load e.g. transaction data from SAP ECC system into SAP BI system.
The Loading process is hanging in processing step u201CSERVICE APIu201D.
The process in hanging in status "yellow" and then changed after a while to status u201Credu201D.
[0FI_AR_4 |http://www.file-upload.net/view-1447743/0FI_AR_4.jpg.html ]
The following steps within Load process are yellow and then red:
Extraction (messages): Missing messages
Missing message: Request received
Missing message: Number of sent records
Missing message: Selection completed
Transfer (IDocs and TRFC): Missing messages or warnings
Request IDoc : Application document posted (is green)
Data Package 1 : arrived in BW ; Processing : 2nd processing step not yet finished
Info IDoc 1 : sent, not arrived ; Data passed to port OK
Info IDoc 2 : sent, not arrived ; Data passed to port OK
Info IDoc 3 : sent, not arrived ; Data passed to port OK
Info IDoc 4 : sent, not arrived ; Data passed to port OK
Subseq. processing (messages) : Missing messages
Missing message: Subseq. processing completed
DataStore Activation (Change Log) : not yet activated
Question:
Can some one tell me whether my distribution model or other settings are wrong?
I created 2 distribution model (BD64), one from SAP BW system and other from SAP BI system with message types RSRQST, RSINFO, RSSEND
Thank you very much!

Hi Holger.
this issue is related to the RFC but not the one which is communicating from BI to R/3 rather the one which is communicating from R/3 to BI follow these steps.
1. check your BI system logical name from the myself source system.
2. go the ECC and run the transaction sm59
3. go the ABAP Connection folder and search for your RFC which name would be by default as per your BI logical system name.
4. double click it and edit it now check whether the Target hostname or ip is OK.
5. In the logon tab check the client number User and password settings.
Save it and test it with both Connection Test and Remote Logon.
if every thing work fine i hope your problem will be solved.
kind regards,
Zeeshan

XI Dev. connected to ECC Dev and ECC Qas

Hello Folks,
I have a question -
We have 2 XI systems: Development, and Production (no QAS)
And 3 ECC systems: Dev, Qas and Prd.
Now we have the XI Dev connected to the ECC Dev.
I'd like to know if it's possible to also connect the XI Dev System to the ECC Qas system.
I mean, to create the RFC dest. in both systems, a new Business System for ECC QAS; and all the necessary config.... and if it won't take problems when we have to transport the Interfaces from DEV to PRD.
Thanx in advance.
Juan

Hi juan,
just be carefull when you add you QUA config in ID and then when you will transport...
1. in your ID, when will define the config with QUA, do NOT ADD the object to your Scenario.... if for the transport you choose the option "Transport all objects of my Scenario"... else you will have a problem in Prod because of the system QUA. Indeed with transport DEV become PROD but your ECC QUA cannot become ...
2. when you will transport to your PI prod :
- check my first point or use option "Transport by selecting each objects" and choose only object linked link to your DEV.
- delete also the Condition option (if you have one) in the Receiver Determination if in th receivers list you have DEV and QUA.... because after the transport the ECC QUA become nothing.
So yes we can. There is no technical issue.... if you do properly the things !!
Regards.
Mickael

Connection Between Solution Manager and ECC

Dear Techies,
I would like to install SAP Solution Manager in one laptop and ECC on another laptop. Both the laptops have very good configuration in terms of operating system (both have server editions) , RAM ( 8GB each) and Hard Drive ( 600 GB each). Once the installation is completed, is there any way that I can establish connection between both the laptops over the same internet/wifi ? I would like to ensure connection is established successfully and data transfer is happening between both the systems. Many thanks for your answers in advance.

Hi Arun,
Please check below -
Create A Quick Ad Hoc Wireless Network Connection Between Two Computers In Windows 7/Vista
Best Regards,
Tanmeya

Connection between JCo and XI

Hello,
I want to establish a connection between an external java program which uses JCo to XI. However, it doesn't work. I'm not able to get a connection between java program and XI.
Can anybody help me in this case?

Hi Dinh,
Here is a sample code I used to test the communication calling function module THPOPUP.
client = JCO.createClient( ...);
// Open the connection
client.connect();
// Get the attributes of the connection
JCO.Attributes attributes = client.getAttributes();
boolean is_backend_unicode = attributes.getPartnerCodepage().equals("4102") ||
attributes.getPartnerCodepage().equals("4103");
// Create metadata definition of the input parameter list
JCO.MetaData input_md = new JCO.MetaData("INPUT");
input_md.addInfo("CLIENT", JCO.TYPE_CHAR, 255, 255 * (is_backend_unicode? 2 : 1 ),-1, 0, null, null, 0, null, null);
input_md.addInfo("USER", JCO.TYPE_CHAR, 255, 255 * (is_backend_unicode? 2 : 1 ),-1, 0, null, null, 0, null, null);
input_md.addInfo("MESSAGE", JCO.TYPE_CHAR, 255, 255 * (is_backend_unicode? 2 : 1 ),-1, 0, null, null, 0, null, null);
// Create the input parameter list from the metadata object
JCO.ParameterList input = JCO.createParameterList(input_md);
// Set the first (and only) input parameter
input.setValue("020", "CLIENT");
input.setValue("USERNAME", "USER");
input.setValue("TEST MESSAGE", "MESSAGE");
// Create metadata definition of the output parameter list
JCO.MetaData output_md = new JCO.MetaData("OUTPUT");
// Create the output parameter list from the metadata object
JCO.ParameterList output = JCO.createParameterList(output_md);
// Call the function
client.execute("TH_POPUP", input, output);
I suggest you to have a look at the sample code named Example1 that is delivered with jco library.
Probably there are also higher level functionality to send the idoc via jco (that hide you the call to that function module), using something like IDOC.create() or IDOC.send() but I have never used them because when I worked in this kind of scenario I had to call a RFC, not to send and idoc, via jco.
Instead I sent Idoc to XI from a non sap system that was built on RFC sdk (similar to jco) and we posted IDOCs to XI via function module IDOC_INBOUND_ASYNCRONOUS.
Dinh, the reason why the Idoc will be sent to the application layer of XI (SXMB_MONI) and not to the below ALE layer (WE05) is that in XI any call to the function module IDOC_INBOUND_ASYNCRONOUS is catched by the application layer.
Consider that when an SAP system has to send an IDoc to another SAP system it calls as well that function module (IDOC_INBOUND_ASYNCRONOUS) to send the IDoc
So once you call that function module the idoc is created in XI and is a normal XI IDoc scenario.
Hope it clarify your doubts,
Kind Regards,
Sergio

What is the difference between version 4.7 EE and ECC 6.0 in SD module.

Hi SAP Gurus,
what are the features in 4.7 EE version in general.
what are the features in ECC 6.0 version in general.
then give me the exact difference between version 4.7 EE and ECC 6.0 in SD module.
if u give the information, then u will get the rewards.
Regards,
somu.

Hi Somu,
These are additional enhancements avialble in ECC6.0 other than that remaining same as 4.7E
1.E-Commerce:- SAP ERP provides powerful e-commerce capabilities that can be expanded in an easy, cost-effective manner in line with business growth. Organizations can run a complete sales process on the Internet, and provide business-to-business (B2B) and business-to-consumer (B2C) customers with personalized and interactive online self-services.
2.Mobile Sales for Handhelds:-SAP ERP enables sales professionals to access front- and back-office business processes and to manage critical sales activities in the field using standard PDAs or other handheld devices (including those with bar code scanners). In this area, SAP ERP provides the following functions:- Customer managementWith SAP ERP, sales professionals may enter, view, and modify detailed customer information, and view sales order history for each customer.- Sales order managementSAP ERP enables sales staff to take sales orders via bar code scanners; search, create, and modify sales orders; and list or sort sales order partners.- Material managementSupport for material management for mobile sales enables staff to view material lists or details for a specific material, search material, and display customer-specific prices.
3.Resource-Related Down Payments and Billing:-- Supports creation of down-payment requests analogous to the functions offered by resource-related billing- Enables organizations to bill the requesting company code for services provided via a resource-related billing document.
4.SAP Beverage Functions Available for the Consumer Products Industry:- As of SAP ERP Central Component (SAP ECC) 5.00, the following functions from the SAP beverage industry solution are available for the consumer products industry:* SAP ECC 5.00, consumer products (EA-CP 500)- Material sorting- Extra charge- Empties management- Part load lift orders- Pendulum list indirect sales- Sales returns- Excise duty* SAP ECC 5.00, supply chain management extension (EA-SCM 500)- Direct store delivery back-end- Master data- Visit control- Transportation planning (including loading units, aggregation categories)- Vehicle space optimization- Output control (including valuated delivery note)- Route accounting (including tour data entry, cash payer, route settlement)* SAP ECC 5.00, industry-specific sales enhancements (EA-ISSE 500)- Extended rebate processing.
5.Credit Management:-Integrating sales and distribution (SD) credit management with SAP Credit Management application:With SAP ERP 6.0 application, you can also use SAP Credit Management in SAP Financial Supply Chain Management set of applications (FIN-FSCM-CR) to perform all credit checks and commitment updates for all areas of sales (SD-BF-CM). In SAP Credit Management, you can update the data from multiple systems. This enables you to execute credit checks with consistent data in distributed systems, too. Furthermore, you can connect to external credit information providers by extensible markup language (XML) interfaces. Alternatively, you can continue to use SD Credit Management (SD-BF-CM).
6.E-Commerce: Catalog Management :-As of SAP ERP 6.0 application, you must carry out product catalog replication from your ERP solution to the Text Retrieval and Information Extraction (TREX) server for use in the Web shop, using the report ISA_CATALOG_REPLICATION.
7.E-Commerce: Quotation and Order Management:- Order creation with reference to a contract that has been displayed* Lock of sales documents to avoid concurrent access during the order change process* Display of bills of material in the shopping basket* Free goods processing* Processing of grid products for the SAP Apparel and Footwear application* One-step business order processing* Selection of multiple transaction types in the shopping basket* Credit card support in business-to-business (B2B) Web shop* Material number format conversion* Maintenance of delivery priority in the shopping basket (B2B)* Document search for all documents across all sales areas* Interprocess communication-characteristic value display in basket and order confirmation
8.E-Commerce: Selling Over eBay:-Creation and management of product listings on eBay leverages the e-commerce order management and fulfillment capabilities of the SAP ERP application by easily tying existing tax, pricing, shipping, and payment configurations to post-auction processing. Enhancements in 2005: * You can use the business-to-consumer (B2C) checkout instead of the eBay checkout. With the B2C checkout, you can maximize cross-selling and up-selling opportunities by leveraging B2C functionality, determine tax and shipping using the elaborate methodologies available through condition techniques in SAP ERP 6.0. * E-mail notification scenario: winner notification to keep the auction winner updated with the status of the auction and of his or her order * Monitoring through features such as single-activity trace (SAT), heartbeat, and logging * Creation and publishing of multiple-item auctions and manual retraction of winners
9.E-Commerce: User Management:-- Web-based user management for business-to-business internet users - Assignment of authorization roles to users in web-based user management - Automatic migration of SU05 to SU01 internet users
10.Enterprise Services in Sales Order Management:-Please check in the Enterprise Services Workplace site which enterprise services are available for sales order management on the SAP Developer Network site (www.sdn.sap.com).
11.Internet Pricing and Configurator (IPC):-The IPC is enhanced and integrated to allow configuration within the sales documents of the SAP ERP application reusing existing model data while leveraging its improved functionality and advanced user interface within SAP ERP.
12.Price Catalog (PRICAT): Inbound Processing (Retail):-Inbound message processing of PRICAT essages:As of SAP ERP Central Component enterprise extension retail 6.0 (EA-RET 600) component, you can create and change article data automatically, or in an interface for mass data handling. The system takes both single and generic articles and bills of material and prices into account.
13.Rebate Condition Records Using Scales:-As of SAP ERP 6.0 application, you can set up rebate agreements so that the scale base value and the rebate scale level is derived from the total sales volume of multiple condition records. You do this by grouping condition records in the rebate agreement.
14.SAP Role: Internal Sales Representative:-SAP role internal sales representativeThis role delivers all the functions to fulfill the requirements of an internal sales representative. This includes tasks such as answering phone calls from customers and prospective customers, processing incoming inquiries and sales orders, and preparing quotations and sales contracts.Target groupThe responsibilities of an internal sales representative (or customer service representative) include the following:- Answering phone calls from customers and prospective customers- Answering product, price, and order status related questions- Processing incoming inquiries and sales orders- Preparing quotations and sales contracts- Taking sales orders and ensuring successful order processing for example, taking care of the completeness of sales documents, releasing delivery-blocked orders, and so on - Support for the outside sales force for example, checking on quotations, updating customer master data, and so on- Preparing reports and sales analyses for the sales manager and the sales teamWork overview This work center gives you an overview of your daily work and gives you easy access to your most important tasks. Sales documents This work center allows you to work on all your sales documents. You can create and maintain inquiries, quotations, sales orders, sales contracts, scheduling agreements, and billing documents. Order fulfillment This work center allows you to monitor order fulfillment. You can display deliveries, backorders, and shipments, and can check product availability.Master data This work center enables you to work on all your master data. You can create and maintain business partners, customer agreements, prices and conditions, and products.
I hope it will help you
Regards,
Murali.

Installing XSS (ESS and MSS) on EP 7 and ECC 5.0 (and ECC 6.0)

Hello,
I need to install XSS (ESS and MSS) on EP 7.0 SP9 and ECC 5.0 and also on ECC 6.0.
I do NOT know what steps I need to perform (installations & configurations).
Could anyone please help me ?
Is the procedure different between ECC 5.0 and ECC 6.0 ?
Please, help.
Kind regards,
Gil

Hello Gil,
1) As I wrote in my second posting, I think I installed the EP 7.0 correctly for XSS and the BP ERP for ERP2005.
Where can I find what configurations I need to undertake and what patches I should install so the XSS and the BP will work correctly ? (that is besides getting error messages when using an XSS iView)
You need to install the foloowing Web Dynpro Components in ur J2EE server.
PCI_GP
MSS
2) If the projects decides NOT to upgrade to ERP 2005 BUT to stay with ERP 2004, do I need to install the EP 7.0 ALL over AGAIN ?
If so, how do I install both the BP ERP 2004 and XSS on it in ONE installation (as I performed in for the BP ERP 2005) ?
If NOT, how do I uninstall the BP ERP and XSS of the ERP 2005 and install those for ERP 2004 ? OR does the BP ERP 2005 support ERP 2004 as well ?
The pre-requiste for BP ERP2005 is a backend ERP2005. So it will not function with backend ERP 2004.
You don't need to uninstall anything. Just download the Mysap ERP 2004 BP and do the necessary configuration to connect it to the BACKEND ERP 2004.This will solve the problem.
You can find the configuration guides and other information abt the BP here.
https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000687949& --> Click on Documents -> Manager Self service.
Hope this solves ur problem.
Regards
Deb
[Reward points for helpful answers]

CRM and ECC 6.0

Hi Gurus,
Can any one tell me the difference in functionalities between crm and ecc 6.0?
Or ecc6.0 is integrated with crm?
What all functionalities of crm can be configured through ecc 6.0?
Whether we require a seperate crm system like the R/3 4.7 and connect it through the middleware
Please suggest at the earliest
Thanks in advance
Ajay

Hi Ajay,
This question could have saved us all this efforts
Btw, opportunity management is used to capture the potential customers info. It helps to capture the buying pattern, the source from which this opportunity is captured, the probability of winning the order. Also we can maintain the various stages of Oppoprtunity and the activities that need to be performed in each phase. You can also maintain the competitor info in opportunity.
Also if you are using PCUI, the opportunity created in CRM5.0 using PCUI can be created as Sales Quotation in ECC.
The opportunity is not replicated in ECC otherwise.
The opportunity can be then followed up by sales order which can then be replicated into ECC.
More info is available on http://help.sap.com/saphelp_crm50/helpdata/en/5b/60c565c63d5a4d8200472b6008eb92/frameset.htm
Hope this will help
Regards,
Rekha Dadwal

You gain a point for every point that you reward. So reward helpful answers generously

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

How to Connect to Remote ECC 5.0 System from EP ?

Hi,
We are using EP6.0 - located in India, and our client ECC5.0 System is in US. Can anyone please let me know the steps how to connect to Remote ECC 5.0 System?.
Thanks in advance.
Krishna Kumar J

Hi,
Finally we have successfully got connected the ECC 5.0 system which is located in the remote network thru VPN Connection using the same connecting procedure for the local R/3 System.
Thanks & Regards
Krishna Kumar

How to use JCO and RFC

Hi guys, please help me out
I'm new to JCO and do not have any idea about it.
Here is my situation, for testing, I want to call an ABP RFC FM in SAP just to return a single text message to Java application through parameter.
(Of course, I have access to SAP from my company and I do not have any Java compiler in my computer).
From my understanding, there 2 main things to concern (Please correct me if i'm wrong and please tell me the steps I should do)
1) Software installation and configuration
   What software do I need to install on my computer, is
   it JCO, SAPGUI, Java Compiler? What kind of
   configurations do I need for JCO?
2) Programming
   a) SAP side
      Write an ABAP RFC FM just to return a text message
      to Java application through parameters (No problem
      with this step)
   b) My computer side
      Write a Java application to call ABP RFC FM
      Do you guys have any simple source code example for
      this?? Please remember that this Java application
      simply call an ABAP RFC FM to get just a single
      text message.
I really appreciate your help
Thank you

Hi Dean,
USe Eclipse for Java programming.
If you are downloading the latest version of JCO, make sure you have latest version of SAP Gui as there are version issues as the librfc.dll needs to be of compatible version.
As far as your sample code is concerned, here it is ...
import com.sap.mw.jco.*;
public class CallFunction extends Object {
     public static void main(String args[]) {
          CallFunction app = new CallFunction();
     int count;
     JCO.Client mConnection;
     JCO.Repository mRepository;
     public CallFunction() {
          try {
               // Logon info
                    mConnection = JCO.createClient("500", // SAP client
                                               "username", // userid
                                               "password", // password
                                                  null, // language
                                         "server name", // application server host name
                                                "00"); // system number
               mConnection.connect();
               mRepository = new JCO.Repository("MY_connection", mConnection);
          } catch (Exception ex) {
               ex.printStackTrace();
               System.exit(1);
          JCO.Function function = null;
          try {
               function = this.createFunction("ABAP_FM");
               mConnection.execute(function);
               System.out.println(
                    function.getTableParameterList().getValue("Exporting_Message"));
          } catch (Exception ex) {
               ex.printStackTrace();
               System.exit(1);
     public JCO.Function createFunction(String name) throws Exception {
          try {
               IFunctionTemplate ft =
                    mRepository.getFunctionTemplate(name.toUpperCase());
               if (ft == null)
                    return null;
               return ft.getFunction();
          } catch (Exception ex) {
               throw new Exception("Problem retrieving JCO.Function object.");
Here in this mention ur function module in place of ABAP_FM and exporting parameter in place of Exporting_Message.
Regards,
Tanveer.
Please please reward some points if found helpful.

'SPROXY' - Multiple PI Systems connected to one ECC System for ABAP Proxies

Dear Experts
I am currently facing an issue when I want to connected multiple PI instances to one ECC client for
ABAP Proxy purposes.
In transaction 'SPROXY', in the Enterprise Service Brower, only one PI instance is shown and accessable.
Can this setting be changed to allow multiple PI systems in this Enterprise Service Browser?
Thanks for your ideas.
Mathias

Hi,
Check these replies.
R/3 connected to multiple XI instances
'SPROXY' - Multiple PI Systems connected to one ECC System for ABAP Proxies
Multiple XI Instances
Multiple XI instances or multiple app server
Thanks,
Vijaya.
Edited by: Vijaya Lakshmi Palla on Jun 4, 2008 11:43 AM

Connecting Jco and ECC

Similar Messages

Maybe you are looking for