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.
Showing results for 
Search instead for 
Did you mean: 

what triggers idoc posting in outbound message from sap ?

Former Member
0 Kudos

Do change or create events can be used to trigger Posting to IDOC? Have any body used idoc for outbound message sending from SAP?


Active Contributor
0 Kudos

Yes, you can trigger IDoc on create or Change event.

- Alpesh

Active Contributor
0 Kudos


Yes you can trigger,

Even I had worked on PO created/change and send IDOC from SAp to other service through EDI..

What exactly do you want?



Former Member
0 Kudos

Hi Reddy,

Posting IDoc Packets

Two groups of function modules are used to post IDocs:

· Function modules which process IDocs in mass. These transfer packets of IDocs for which individual IDocs are updated in the same Logical Unit of Work (LUW).

· Function modules which process one IDoc per call.

· INPUTTYP contains the code for posting function modules.

To display the function module's INPUTTYP on the ALE Development screen, choose IDoc ® Inbound Processing ® Function Module® Maintain Attributes (BD51).

INPUTTYP can contain the following values:

· "0", for function modules which process IDocs in packets.

"1" and "2" for function modules which process one IDoc per call:

If you post the IDocs immediately, the SAP sending system determines the packet size. ALE inbound processing can recognize if the posting function module allows packet processing and if so, passes the IDoc packet to it. If not, the IDoc packet is split into individual IDocs.

If IDocs are posted in the background, you can specify the size of the IDocs to be generated in the program RBDAPP01.

If you use function modules that can process IDocs in mass, the database load is reduced.

If you group IDocs into packets, this may also be practical for function modules that post inbound IDocs one at a time, because the ALE layer calls the function module several times in the same dialog process, thereby reducing the administrative load on the SAP system.

If program RBDAPP01 carries out the background processing, as a guide, you should use a packet size of between 20 and 100 IDocs.

Packet processing and parallelism complement one another. Packet processing and parallelism complement each other, although in some situations they may compete with each other. If the size of the packet is too big, this may mean that not all the available dialog processes are being used.

Scheduling IDoc Posting

There are two ways of posting IDocs in ALE inbound processing:

· Immediate processing:

Upon receipt inbound IDocs are immediately released for posting. ALE inbound processing splits the IDoc packets into individual IDocs.

· Background processing

Inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand.

The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs can be put into packets and then processed.

Perform the following steps:

1. Set-up background processing (IDoc/ALE area menu):

IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Profiles (WE20)

Then the required setting is: In the detail screen Inbound Parameters select the option Trigger by background program.

2. Schedule posting (ALE customizing):

Transaction SALE ® Set-Up System Monitoring ®

Posting IDocs in Recipient System ®Schedule

You can also process the IDocs manually by passing them to the posting function module. In ALE Administration choose Monitoring ®Status Monitor (BD87), select the IDocs and then select Process.