R3 to SCM Integration

[Former Member]

Hi All,

I am trying to connect from R3 ( 4.7 ) system to SCM 5.0 but my RFC destination is throwing error " Name or Password is incorrect" though I give correct login details of my SCM system. Actually error is while testing the authorization in RFC destination transaction.

What kind of authorizations or roles an user required to connect to SCM 5.0 from R3 ( 4.7 ) ?

If any one has got idea about this please share that.

Thanks in advance.

Sreedhar

[Former Member · Accepted solution]

Are you using alpha nunberic passwords? if so try setting and using a all numeric password instead

[Former Member · Accepted solution]

Thanks Harish ,

Thats solved my RFC problem but data is not posting. Now I will need to check all settings properly.

[Former Member · Accepted solution]

R/3 4.7 should have the release value of SCM 5.0 as "50" defined in NDV2 transaction in ecc spro. If its not there, you need a developer access key to maintain the same. This is mandatory for data transfer bet the two servers.

Regards,

Loknath

[Former Member]

Hi ,

Following are the steps. Read it once and check if you have maintained everything before CIFing.

Reward if useful.

R/3 Customizing activities

u2022Check and/or activate ALE settings (Transaction code: SALE)

A "Logical system" is defined to capture the R/3 environment and the APO environments. In the R/3 environment, these logical systems can be associated with physical clients through the client maintenance transaction (Transaction code S004). All data transfer mechanisms related to the Core Interface[CIF] work with this Logical System mapping.

It is important to note that two logical system should not share the same name.

u2022Set up RFC destination (Transaction code: SM59)

In this step, a mapping is made between the client within the R/3 or the APO environments and the TCP/IP addresses of these systems. With this setup, a port is established for the communication between the logical systems and the network management applications.

u2022Define Target Systems (Transaction code: CFC1)

This setup is made to ensure the data transfer mode through the Core Interface. This setting is made from the menu path Settings Target Systems in the CIF menu.

On this screen, Change View u201ATarget Systems and Operation Modes: Overview appears.

Select New entries.

In the connection, enter the same name that was previously used for the RFC destination.

The system automatically sets the operation mode.

u2022Define APO Release (Transaction code:NDV2)

This setup is done to provide information to the system landscape on which APO system is being interfaced with on the other end. This setting is made from the menu path Settings  APO Releases in the CIF menu.

The following information must be provided for this configuration

The corresponding R/3 Plug-In system type

The release name of the APO target system

u2022Specific customizing required for correct transfer of vendor and customer locations to APO (Transaction code: STZGC)

The time zones need to be specified for each of the countries and regions that are being transferred into the APO system.

The menu path for reaching this transaction code is

Tools  AcceleratedSAP  Customizing  Edit Project  SAP Reference IMG  General Settings  Time Zones  Display Time zone Customizing geogr. data

Ensure that all the time zones are properly maintained in this screen for all the countries and the country + region combinations. Incorrect or absent time zones will result in no transfer of data to the APO system.

APO Customizing activities

u2022Check and/or activate ALE settings (Transaction code: SALE)

A "Logical system" is defined to capture the R/3 environment and the APO environments. In the R/3 environment, these logical systems can be associated with physical clients through the client maintenance transaction (Transaction code S004). All data transfer mechanisms related to the Core Interface[CIF] work with this Logical System mapping.

It is important to note that two logical system should not share the same name.

u2022Set up RFC destination (Transaction code: SM59)

In this step, a mapping is made between the client within the R/3 or the APO environments and the TCP/IP addresses of these systems. With this setup, a port is established for the communication between the logical systems and the network management applications.

u2022Define Business System Groups (Transaction code: /SAPAPO/C1)

The Business System Group integrates different physical systems into a super-ordinate logical unit. This logical unit will control the transfer of all master and transaction data between any APO - R/3 system combination

The settings for the BSG is done through the following menu path:

APO Implementation Guide  Advanced Planner and Optimizer (APO)  Basis Settings  Integration  Business System Group  Maintain Business System Group

It is recommended that the APO System be assigned to the same BSG to which the logical system or R/3 instance(s) that contain the master data server belong. Only then can preliminary maintenance of the master data be carried out in APO.

u2022Add Logical systems to BSG (Transaction code:/SAPAPO/C2)

In this step, the logical systems configured in the R/3 and the APO environments are mapped to the Business System Group

This configuration ensures the integrity of master data in the APO environment by attaching the BSG name as a part of the master data key fields.

Regards - Chandan

[pavansingineedi]

Thanks for info. its working