SAP ALE IDocs Interview Questions And Answers

Dialog work processor

yes, we can attach more than one message types to one idoc.
For example sendor wants the records on both material and
purchase at same time then we need to add two message types
to one idoc.

in SALE we maintain the Sendor as well as three Receivers
(how many receivers to send the same idoc),
and assign the sendor in sendor system as well as assign
receivers in receivers system(sale-->assignment) three
receivers.

maintain the RFC destination on sendor side and all
receiver side also (sm59).

maintain the port for sendor and three receivers.

maintain the sendor and all receivers for a same message
type in distribution model.(bd64)

maintain the partner profiles for sendor and all receiver
side also (we20).

execute the outbound program(idoc generation)like BD12 for
DEBMAS message type .

check out the status using we02 or we05.

By executing Conversion Program RBDMOIND...
1) Execute RBDMOIND in outbound program
2) If the status code is convert into 3 to 12 then we can
confirm the IDOC received successfully..

Data from 3rd party can come from middleware tools like MERCATOR. Also data can from 3rd Party from email or fax also. This can be done by intergration mail system with SAP inbox.


The usual connection for middle ware tool can be type 4 TCP/IP - depending upon the setting of your gateway server properties one can integrate SAP with other party Middleware systems.

The very first setting you need to check is in distribution
model if the message type is configured for given sending
recieving system combination.if this is correct and partner
profile is wrong, you will get an IDoc stuc in 56 status on
inbound.
You can also check in we09 with giving more details like
segment name (related to MARA table ) and the corresponding
material no. in the field for selection with MATNR.

for outbound we can send through program or
functionmodule.but inbound idoc only through function
module.so its depends wheather it is outbound or
inbound.then we will debug

EDIDD to store data records.
EDIDC to store control information.
EDIDS to store status of IDOC

According to my knowledge in SAP XI we have so many kind of
control levels to process the message. For instance i will
discuss on few points, like
1) Here using XI we can communicate with the SAP or Non-SAP
at sender side or reciever side.
2) XI supports both Syncronus and asyncronus communications
3) in XI we can find the status of the message where it is
during the process of Message processing.
4) We have so many kinds of monitoring techniques.
5) Here we can have N number of senders and N number of
recievers based on your requirement.
6) It supports to process multiple messages at a time from
different senders to multiple recievers.
So I feel we cant perform all these things in
Interfaces.That is the reason XI come into picture.

If you are sending one idoc is to more systems you are
create one sender logical system and more recive logical
systems in T.CODE is SALE. then yoou are send In T.CODE
BD64.

no we con't send.because When ever we try to send an IDOC
it checks with distribution model and is there any
filtering is defind or not, if it is defined then checks
with filter data and then it checks with reciver and
messagetype.

ALE/IDocs are used for asynchronous information
interchange.while BAPIs are used for synchronous
information interchange

'TidDatabaseConnectionString' this is the type of port for
processing idoc's.

DIFFERENT TYPES OF PORTS

1.TRFC --> IDOCS/ALE
2.XML --> JAVA
3.FILE PORT --> IDOCS
4.INTERNET --> WEB APPLICATIONS
................

pi(process integration) itself acts as middleware for
creating connection between A2A OR B2B SCENARIOS.pi provides
sinle point of integration.

For errors we need to check for the status codes and cming to
debug we can debug our the assingned function module i.e
idoc_input_matmas05 or z(fun module) in case of custom and
while processing in bd87 the complete idoc can be processed
by selecting the option available.

No it is not possible.because vendor number or po numbers
are the uniqe.so it can holds the same vendor or po number
uniquely.

If you have any error in IDOC u can edit it by using we02 tcode,
after that you can reprocess the corrected IDOC by using bd87
tcode.

Table node:tables are dynamic because the table size depend
on the amount of tha data selected at runtime.

Templete node:templetes are static because the no of column
and lines are determind before the actual output.

- communicating between two physically separated systems.
Either SAP to SAP or SAP to Non-SAP ,we use IDOC.

- SAMPLE Scenario is a new custom ALE where the receiver of an
internal service must be able to reverse the invoice receipt,
which will then cancel the applicable billing document
automatically on the service providers system. To avoid the conflicts between two systems.

SAP memory (Global Memory): - is available to a user during
the entire duration of a terminal session. Its contents are
retained across transaction boundaries as well as external
and internal sessions.

ABAP/4 memory
The contents of the ABAP/4 memory are retained only during
the lifetime of an external session (see also Organization
of Modularization Units). You can retain or pass data
across internal sessions. The EXPORT TO MEMORY and IMPORT
FROM MEMORY statements allow you to write data to, or read
data from, the ABAP memory.

u r trying to generate the idocs with 10
records, and u find only 8 (records) idocs created rest
(records) are missing.

Check with the filter set up for the records for its
receiving partner system(logical system).

Correct the filters then try regenarating the idocs(missing
records).

You can use BD87 if you want to reprocess same idoc
number,here it will not generate new idoc number.
suppose there was RFC Issue ,connection got failed then
after rectifying RFC Connection then you can reprocess
same idoc number.

in case data is missing,then you need to WE19 Transaction -
> enter idoc number -> fill the missing data.
just drag the segments ,here you can fill data where ever
required.

If you use WE19 then it creates new idoc ,it gives work
flow message.

EDIDC stores control/header record.
EDIDD/EDID4 stores data records.
EDIDS stores status records.

SAP system present in customer environment is copy of
original system which is at SAP itself. That means all the
objects present in customer environment are copy of the
object originally created in SAP environment.

So, If we modify copy of object then it is called as repair
and assigned to development task repair. Repair of object is
also called as modification.

Whereas if we modify object in it's original system where it
is actually created may it be SAP system or the objects
created by customer in customer environment. Then such
changes is called as corrections and assigned to task
Development/Correction

OAK code is a code which is used to convert OPK to IDOC..