Ale Config! Help Needed!

Former Member — Wed, 29 Aug 2007 08:50:23 GMT

Hi Guys!

Pls look at the diagram below,

Service Receiver Service Provider

P.order -

>Sales Order------|

Order Confirmation<----

P.order Change -

> Sales Order Change

Invoice Receipt< -

Invoice

Reverse Invoice Receipt----

> Cancel Invoice.

Here, Two logical Systems Service Provider & Service Receiver

Two Clients

Here 4 transactions taking place, according to my knowledge ( p.order, order confir, invoice receipt, cancel invoce) between two systems.

( pls correct me if i am wrong)

Questions?

1) I want to know for these 4 transactions how many port definitions & Distribution model has to set up in both the systems.

2) What about Partner profiles is it same for the 4 transactions .

Pls Explain me briefly.

Pls correct me if i am wrong.

Thanking You all for your Answers in Advance

Rahul.

Re: Ale Config! Help Needed!

Former Member — Wed, 29 Aug 2007 08:54:02 GMT

Hi,

SM59 RFC Destination

Here we specify the login settings for the destination including

the I.P address or Application Server name and the User name and

password.The information entered here is used to run Remote Function

Calls(RFC ) on the destination server .We can create number of types

of RFC Destinations but 3 types are important .

R/3 (R/3 to R/3), LS(logical system) and TCP/IP.

The name of the RFC destination should be same as that of Logical

System as it helps in creation of automatic partner profiles.

WE21 Port Definition.

There are 6 types of ports but only 2 types File and Transactional RFC

types of ports are important.

We have to specify the RFC Destination before a port can be created.

WE57 This is used to assign the Inbound function module to the Message Type

and to the IDOC Type.

WE42 This is used to define the process Code for Inbound Processing.

BD95 Define Filter object type .We can specify the field and the table it belongs

to as a filter object .

BD59 Assignment of Filter object type to the Message Type .Here we create the

link between Filter object and the segment and the message type and the

segment Field.

BD50 Set message Type to reducible.

BD65 Define Mandatory Fields.

BD64 Distribution Model . Also known as Customer Distribution Model Used to

define all the messages that will be exchanged between remote systems

and the name of thes logical systems. Any filters can also be specified.

The model once created has to be distributed on every system which will

be communicating ,It can be maintained on only One system.

BD21 Creating IDOcs from change pointers.

This can be used to create IDOCs from change pointers for a particular

message LIKE MATMAS.

BD22 This can be used to delete change pointers.

BD87 Status Monitor. Idocs can be selected base on number of criteria and there

processing status can be seen in detail.

BD10 Material Master Data Distribution .

Based on Message MATMAS.

BD12 Customer Master Data Distribution .

Based on Message CREMAS.

BD14 Vendor Master Data Distribution

Based on Message DEBMAS .

BDFG Generate ALE Interface for BAPI.

Here we specify the Business Object and the BAPI Function module for

which the interface has to be created.

WE31 Segment Editor.

This is used to create segments. We create the segment type and

segment definition is automatically created by editor e.g. Z1DUMMY is

segment type and Z2DUMMY is the segment definition .We specify the

fields and the data elements these cp\orresponds to create segments.

WE30 IDOC Editor

It is used to create a new IDOC Type or IDOC Extension .We specify the

segments that will be addd to the IDOC type.

WE02/05 IDOC List.

Various selct options and parameters are provided to select IDOCs

depending on the date, direction , mesage type etc.

WE20 Partner Profile

Here we create partner profile for each and every partner from / to which

the messages will be exchanged.There are 6 types of PF generally only

profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.

We specify the partner number and partner type and the agent and

the agent type responsible for handling of errors .

For every message send to the partner we have a outbound record and for

evry message coming from the partner we have the inbound record .

We specify the message in the otbound/inbound records ,double

clicking will take us to the detailed screen where the IDOC Type ,Port

and whether the IDCO will be immediatelt processed or collected are

mentioned.

Thanks

Naveen khan

Re: Ale Config! Help Needed!

Former Member — Wed, 29 Aug 2007 09:23:04 GMT

Hi!

Pls anybody give specific answers

Re: Ale Config! Help Needed!

Former Member — Wed, 29 Aug 2007 10:40:31 GMT

Hi Rahul,

As u said here 4 transactions are taking place.

Here partner profiles will be the same for the 4 transactions.

coming to port creation.......actually this port is a channel through which IDOC travels.So it's totally depends upon the requirement.To my knowledge we have to create one port.

coming to distribution model,where partner profile is generated and communication IDOC is created, we can create one distribution model for each transaction....

Plz reward points if it helps u...............

Regards,

Jaya

Re: Ale Config! Help Needed!

Former Member — Wed, 29 Aug 2007 11:08:16 GMT

Thanks Jaya for your wonderfull xplanation

topic Re: Ale Config! Help Needed! in Application Development and Automation Discussions

Ale Config! Help Needed!

Re: Ale Config! Help Needed!

Re: Ale Config! Help Needed!

Re: Ale Config! Help Needed!

Re: Ale Config! Help Needed!