Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

ALE/IDOC within system/client

Clemenss
Active Contributor
0 Kudos
356

Hi experts,

I know IDOCs are use for communication with other systems. Is it possible to have an ALE scenario for use inside one system, i.e. a specific document like an order is saved and automatically an IDOC output is created and processed as input for another process (like customer-specific financial document?).

Until now, I know only inbound and outbound processes but I don't know if it is possible the same system as input and output at the same time.

Any ideas about possible solutions welcome!

Thanks in advance

Clemens Li

1 ACCEPTED SOLUTION

Former Member
0 Kudos
136

hi

you can use same system for inbound and outbound with different client.

9 REPLIES 9

Former Member
0 Kudos
137

hi

you can use same system for inbound and outbound with different client.

0 Kudos
136

same system, same client: no way?

Former Member
0 Kudos
136

hi

first go to scc4,assign logical system name for 2 clients .And go to bd64, proceed steps that follow for configuring between two systems. note u should create a rfc dest in sm59 for same system in logical system

name .

Former Member
0 Kudos
136

hi ,

i didn't try this, any way in bd64 while creating model view assign same logical system as sender and receiver .all the best.

Former Member
0 Kudos
136

Hi, through model view, you can't create a model with same source and target LS. That's the restriction of SAP.

I have an idea, but haven't tried it.

List as following:

As we know, the IDOC throw out from source system using the FM 'MASTER_IDOC_DISTRIBUTE' at last.

And target system receive the IDOC by the FM 'IDOC_INPUT_XXXX'. XXXX according to the IDOC type we received.

Now, you need the target system and source system to be same.

So why not abandom the 'MASTER_IDOC_DISTRIBUTE'?

We can fill a IDOC structure, and directly call associated 'IDOC_INPUT_XXXX'.

I'm not certain it will be effect. But looks worth trying.

And by the way, why you need a IDOC sent to local system. If you need a technology to do the Inbound work, there is several choose for you, e.g. LSMW BAPI and some standard program offered by SAP.

Hope it will be helpful

Thanks a lot

Message was edited by: zhenglin gu

Former Member
0 Kudos
136

Hi,

If you are hell bent on finding a way to do it, you can try configuring outbound as EDI ( in message control ) and setup the partner profile so that it uses a tRFC port pointing to same system and client (RFC destination in the tRFC port). Obviously as mentioned in previous posts you can not use distribution model, you need to set things up manually.

Output determination or message control has two cummunication mediums for sending out IDOC's, one is EDI and second is ALE. Difference is that ALE looks at distribution model to find the recipient and EDI looks at partner profiles to find recipient directly.

Cheers,

Sanjeev

Former Member
0 Kudos
136

Hi,

You can create a mannual process to populate the IDOC and then use to to create it if you want to use the same client.

However as per the SAP practise goes the ALE is suitable while communication with different client. For the same client you can use the workflow option in you case scenarion like you want once the action A is completed there should be automatic execution and completion for action B also you can check if there is any user-exit availabe for the action A where you can put the check once the process is complete then the nect process should trigger.

/Manik

Former Member
0 Kudos
136

Very much possible.

The inbound FM has to have the logic for the other process (like customer-specific financial document).

Remember to reward points to the replies that answered your question.

0 Kudos
136

hi

You can Go to this Link and download the whitepaper.

http://www.sapgenie.com/ale/whitepaper.htm

In The 7.3 Topic it has been explained to configure this scenerio.

Thanks