cancel
Showing results for 
Search instead for 
Did you mean: 

ALE / IDOCS

Former Member
0 Kudos

Hi Gurus

Can anybody pls send me the configuration steps for ALE& IDOCS.

Reg

Sneha Reddy

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Configuring the service for an outbound ALE IDoc and IDoc packet

The configuration process described in the following steps configures the adapter, creates business objects for outbound ALE IDocs, and if desired, creates an IDoc wrapper business object for an IDoc packet of multiple individual IDocs.

Why and when to perform this task

For information about configuring other business objects, refer to the appropriate service configuration topics.

Steps for this task

Switch to the Business Integration perspective in WebSphere® Integration Developer.

Right-click the frame of the Business Integration perspective window and select New > Enterprise Service Discovery from the pop-up menu. If Enterprise Service Discovery is not visible, select Other from the bottom of the pop-up menu. Then, in the window that appears, expand the Business Integration folder and select Enterprise Service Discovery and click Next.

When prompted to select an adapter to use for discovering the service, select IBM WebSphere Adapter for SAP Software and click Next. If you have previously run the enterprise service discovery wizard, your connection properties have been saved and appear when you expand the adapter name node (click the plus symbol + next to the adapter name). You can select the saved connection properties if you plan to connect to the same SAP application as when you last ran the enterprise service discovery wizard.

When prompted to specify properties in the Configure Settings for Discovery Agent window, specify the adapter configuration properties for connecting to SAP. Properties marked with an asterisk (*) are mandatory. Be sure to set the Select Module property (under Metadata Properties) to the value of ALE.

At the bottom of the window, click the Show Advanced button.

When prompted to specify logging options, specify a log file location and set the Logging Level. In a test environment, choose FINEST, which provides the highest level of logging. In a production environment, choose a level lower than FINEST, so as to optimize the logging process.

Click Next.

In the Find and Discover Enterprise Services window, click Run Query.

Under Objects Discovered by query, drill down to the Discover By Name node, and then click the Filter button. You can also drill down to Discover By

In the Filter Properties for Discover by Name window, enter the name of the IDoc you want to discover. You can include an asterisk (*) as a wild card character at the end of the name to indicate that you want to discover all SAP application components that start with the specified name.

Click OK.

Navigate to the desired Basic or Extension IDoc and click the Add button. The Configuration Parameters window appears.

In the Configuration Parameters window, do the following to add the IDoc to the list of business objects to be imported.

If you want to create an ALE wrapper object (for an IDoc packet of multiple individual IDocs), select the Create ALE wrapper check box.

Select the Use SAP Field Name to generate attribute(s) check box.

In the Enter the Release field, specify the SAP release number to identify the IDoc type you want the enterprise service discovery wizard to use for creating business objects. Note that you can specify an earlier release than the one you are currently using, if for some reason you wish to create business objects based on earlier versions of the IDoc type. If the earlier version of the IDoc type has fewer segments than the current version, the enterprise service discovery wizard may create a definition with missing segments or it may display an error indicating that the generation of the business object definition was unsuccessful. This inconsistency is due to different versions of SAP requiring different API calls.

Click OK.

Repeat step 12 and step 13 for each IDoc you want to discover and then click

Repeat step 12 and step 13 for each IDoc you want to discover and then click Next. The selected objects appear in the bottom window frame.

If you want to remove an object from the list, select the object name and click Remove.

Click Next to proceed.

In the Configure Objects window, enter BODEFS in the Object Location field, specify the name space, and select Outbound in the ServiceType field.

Click Add. The Add window appears with a list of operations you can select to associate with this business object. For outbound, the only operation you can select is Execute.

Select the operation and click OK. The Configure Objects window appears with the selected opeClick Next.

In the Generate Artifacts window, click New and then specify the module name where the SCA artifacts (business objects, their properties, import file, export file, and WSDL) should be saved.

ration listed under Operations

In the Generate Artifacts window, specify the folder within the module where the service description should be saved.

In the J2C Authentication Data Entry field, enter SAP_Auth_Alias and select the Deploy connector with module check box.

In the Generate Artifacts window, click the Use discovered connection properties radio button to set properties at this time. (The Use connection properties specified on server button lets you configure properties later, using the WebSphere Process Server administrative console).

Specify the connection properties and then click Finish. Properties marked with an asterisk (*) are required.

Former Member
0 Kudos

Hi Sneha,

ALE:--

The following steps need to be noted when configuring your ALE solution:

Confirm business requirements - Before commencing configuration ensure that you have the detail of the business requirements for the whole scope of the implementation.

Configure the ALE basis portion to enable ALE in the development environment. This involves the following steps:

Create Logical System (LS) for each applicable ALE-enabled client;

Link client to Logical System on the respective servers;

Create background user, to be used by ALE, on each client;

Create RFC destination for each destination client; and

Generate partner profiles for sending system. (Can only do this if at least 1 message type exists against the sending system's LS). This automatically generates the port if the LS and RFC name are the same.

Following the basis configuration is the functional configuration:

Create a Customer Distribution Model (CDM);

Add appropriate message types and filters to the CDM;

Generate outbound partner profiles;

Distribute the CDM to the receiving systems; and

Generate inbound partner profiles on each of the clients.

Keep your ALE configuration diagram up to date and follow change management procedures rigorously, as you begin to configure. Areas you need to document well include the finer details involved with an ALE implementation:

Listings / classes;

Object types \ Workflow tasks;

Conversion rules;

Filters & Segment filters;

Change pointers \ Fields activating change pointers;

Serialization;

Partner profiles: Immediate Vs Background;

Background job definition and scheduling;

Control data required to be in synch; and

...

Functional specifications need to be drawn up, by the business, describing exactly what is required by them, that is not available in the standard ALE scenarios.

A technical specification can then be drawn up by the ALE team. In this technical specifications the following needs to be addressed:

New IDocs required;

New fields added to existing IDocs;

Program \ user exits \ message control for populating the fields;

Inbound functional module details;

ALE configuration set up requirements; and

Error handling.

Once the specification is completed and confirmed by the business, programming can begin.

Developing an ALE scenario will include the following steps:

OUTBOUND:

Create Segments and IDoc type;

Create Message Type and link to IDoc type;

Populate IDoc using message control \ user exit or program (ABAP);

Distribute IDoc using MASTER_IDOC_DISTRIBUTE;

Create object type if required;

Define CDM with message type and filter object. Distribute model. Generate outbound partner profiles;

INBOUND:

Write inbound function module (FM) to process inbound IDoc (ABAP);

Create process code and link to FM;

Generate inbound partner profiles; and

Link object type to FM for error handling.

IDOC:-

An IDoc is made up of the following parts:

Control Record: This section contains control information regarding the Idoc. Its constituents are Sender’s name, Receiver name, Message type and Idoc type (illustrated in figure 3). The format of the control record is similar for all IDoc types.

Data Segment: It consists of a header that contains the identity of the Idoc. Its constituents include, a sequential segment number, a segment type description and field containing the actual data of the segment.

Status records: The status record shows the information regarding the already processed stages and remaining processing stages of the Idoc. It has an identical format for each IDoc type.

T code for Idoc

WE30 -- develope Idoc types

WE02 -- Idoc list

WE09 -- Idoc testing tool

Reward points if u helpful

Cheers

Govind

Former Member
0 Kudos

SENT MAIL REWARD IF HELPS

Former Member
0 Kudos

ayub send to my email id as well

murali.maliki@gmail.com

Former Member
0 Kudos

Please give ur e-mail ID, I will forward it to u

REgards

AK

Former Member
0 Kudos

Hi,

Can anybody pls send me the configuration steps for ALE& IDOCS.

Plz send on my mail id

panmahajan@gmail.com

thx

pankaj