cancel
Showing results for 
Search instead for 
Did you mean: 

Automatic Customer Master Data IDOC creation

Former Member
0 Kudos

I have a few questions on Customer Master Data IDOCs

1. First Scenario

Customer is created, the IDOC is created AUTOMATICALLY and sent to the external system. The changes of customer master are not sent out automatically.

2. Second Scenario

Customer is created, the IDOC is created Automatically and sent to the external system. The changes of customer master are sent out automatically. How should I organize it? It this scenario we can use change pointers as I assume.

3. Third scenario

Customer is created, the IDOC is created Automatically and sent to the external system. The changes of customer master are sent out automatically but the message type is different than the creation idoc..

The questions:

Could you please give me the steps how those scenarions can be fulfilled? Which SAP mechanisms can be used? Do we have to write any new coding?

Please advise!

Thank you for your help,

Points will be granted!!!

Michal

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Apart from the suggestions given above, you can also use.

BD54- Creation of Logical system

SCC4- Assignment of the client to the logical system.

Thanks

Krithika

Former Member
0 Kudos

Hello Friend,

ALE process is used to send information from SAP to External systems. BD12 is the T-code used to send Customer IDOCs from SAP to other systems. program RBDSEDEB represents the same T-code so a batch job can be set for this program with certain frequecy to automate the process.

For any change in the customer master change pointers can be used.

Configuration Settings

Setting up the ALE Infrastructure is like building a bridge. There are 2 steps:

Basic Settings for IDOCS:

The basic settings for the IDOC interface need to be maintained once of each system involved in distributed processing that is not subjected to frequent changes. The parameters in the table specify the administrator for the IDOC interface at runtime.

WE46  EDIADMIN table.

Communication Settings:

The communication settings for the ALE process establish links between 2 SAP systems so that they can execute any function on each other. These settings are done once for each system and are independent of the distribution scenario. There are 5 steps involved in setting up ALE and is part of SALE transaction.

The steps are:

1. Define clients

2. Maintain logical system

3. Assign logical systems to clients

4. Setting up an RFC destination.

5. Define PORT.

Define Clients

Client is a self contained unit. Example: Corporation. Client set up is normally done by the Basis team. The 2 clients can be on the same system or different systems. Example for Clients is 100 & 110. Transaction Code is SCC4.

Maintain Logical System

The system involved in distributed processing are assigned logical names, which uniquely identify systems in a distributed environment as shown in the Figure

Menu Path:

SALE Sending and Receiving Systems Logical Systems Define Logical System

Assigning Logical Systems to Clients

The logical name of the system is linked to the client of the SAP system. A one-to-one relationship exists between a logical system & client.

Menu Path:

SALE Sending and Receiving Systems Logical Systems Assign Client to Logical System

Setting up an RFC Destination

In RFC destination the information required to log on to the remote system is specified. Transaction Code is SM59

Menu Path:

SALE Sending and Receiving Systems in Network Define Target Systems for RFC Calls

ALE uses R/3 connections for communicating with remote SAP systems. On double clicking the line item under respective Client Login details is displayed as shown in the following figure

Port Definition

A port defines the medium in which data is exchanged between 2 systems. tRFC port is used for ALE Communication. Transaction Code is WE21

The 3 parameters present in port configuration are:

u2022 Port name: to uniquely identify the port.

u2022 Description: of the Port

u2022 Logical destination: RFC destination.