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..

Buddula15

You can Use the Tcode BDM2..


Through this tcode you can view the Sending system Idoc 
Number and Corresponding recieving System Idoc number... 
status also you can get from this Tcode..

or elso note down the Corresponding Idoc number and check 
in WE02..

Renjith Remanan
Collabera/IBM/WDC

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.

By using webmethods tool like Contiva(using in TCS) we can
get data from 3rd party system

check inbound partner profile(WE20) in the receiver
side.give the correct partner number,message type and
process code.i

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.

Hi,

If above answers didn't solve your Problem, Check the Port 
Numbere in Tcode IDX1. and Message types configuration in 
IDX2.

Renjith Remanan
Collabera/IBM

using function module idoc_outbound_<message type>. we  can 
set the break point for this function module.

you can debugg the idoc through we19

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

i think we can debug using dynamic debugging mode for the
tcodes that are used for sending data like BD14,BD12,BD10

IN REAL TIME MAINLY WE WORK ON EXTENDED IDOC. WE WILL GO FOR
THE CAHNGE POINTER IF THERE IS ANY CHANGE IN THE EXITING
DATA NOT THE NEW DATA.IF WE CHAGE THE DATA (EX-CUSTOMER
ADDRESS)AND EXECUTE BD21 THEN CAHNGW POINTER WILL WORK.IF WE
CREATE A NEW CUSTOEMR THEN CAHNGE POINTER WILL NOT WORK

change pointers technique is used when u want to send only
changes that are occured to the data in the database.to do
this 3 tcodes are needed.
BD61
BD50
BD21 (or) execute RBDMIDOC

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

EDID4 is the table to store data segments (EDIDD is the 
structue, not a table)

Transport the data r/3 system to another r/3 system
or The data will be transport one client to another client

EDIDC, EDID4, EDIDS will have the values of control record, 
data record, status records. But field the values in the 
segments like E1EDP01-MATNR are not stored in any tables. 
Reason behind this is the values in idocs are not fixed for 
all IDOCS and will differ based on the transaction data.

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.

Still if u get any thing other than this please mail me at 
cravisap@gmail.com

Hi , 

Master IDOC : This idoc collects all the required data into 
single IDOC and this is temporarily stored in memory. 

Communication IDOC: there can be n number of communication 
IDOCs generated. This comes into picture after the Master 
IDOC is validated from the distribution model . And this 
IDOC is stored in database table . you can see this IDOC 
from we02 tcode. 

Best Regards, 
Suresh .

Inbound process strats when application data is creatred
inthe  database.

Based on the given input outbound program trigers ,reads the
application data from the database& generates the master idoc.

Master idoc is the data inthe internal table. master idoc
data will not save any where in sap.

comm idoc is the physical idoc which is reciever specific.

1 master &communication idoc

5 master idocs and the number of communication idocs is 
based on the number of recipient systems which is mention 
in the customer distribution model of that message..

master idoc: in the outbond process all the data in sap r/3 
is retreived via outbond program.after retrieving, the data 
is arranged in segments in heirarichal order in an internal 
table.this internal table which has segments and data is 
known as master idoc.

communication idocs : this completely depends upon the 
distribution model which has list of senders and 
receivers.so if receivers are not attached to senders in 
distribution model than we have zero communication idocs.so 
communication idoc is simply the data which gives the link 
between the senders and receivers.

if u send 5 records it means u r sending 5 master idocs and 
the number of communication idocs depend upon the number of 
receivers u have in the distribution model.

Master IDoc(s) : The internal table(s) having Segments and
Master Data is known as Master IDoc. The number of Master
IDocs generated are depend upon the number of records you send.

Communication IDoc(s) : The number of Communication IDocs
generated are depend upon the number of Receivers you have
in the Distribution Model.

Hi, 

As per my knowledge, you cannot send the single IDOC to 
multiple system . At a time an IDOC can be directed to only 
single system . 

Thanks & Regards, 
Suresh

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.

Hi,

Create Two output type for the same So/PO and assign the 
output type in partner profile.

REgards,
Nandha

You Have to Maintina distribution model ( BD64 ) for this 
scenario.

Then you need to maintain the partner numbers(ie logical
systems) in both SALE(tcode) and BD64. At the same time
maintain partner profiles for each receiver participating in
the communication.

Above Realated Functionalities (operations) is Related to 
Fuctional Guys only, or Sume times According to requirement 
Clients are take care some output determination.

endusers and keyusers define condition records
output type and output determinition are configured by 
functional consultants.

All these configuration settings are done by functional
consultants.


Regards
Rami Reddy

CHANGE POINTERS:ACTIVATION OF CHANGEPOINTERS FOR MESSAGE 
TYPES.


CREATION OF IDOCS FR CHANGE POINTERS.

CHANGE POINTERS CONCEPT IS BASED ON CHANGE DOCUMENT 
TECHNIQUE,WHICH KEEPS A TRACK ON ALL THE CHANGES MADE TO 
KEEP DOCUMENTS SUCH AS 
MATERIALMASTERS,CUSTOMERMASTER,VENDORMASTER.
ALL THE CHANGES CREATIONS DONE TO THOSE DOCUMENTS ARE 
STORED IN CHANGE DOCUMENT HEADER TABLE.
TABLE NAME:CDHDR

Message control : Every Idoc that is trasnferred is 
associated with the message type.

Message type defines the type of data the idoc is 
containing.

See for example : If i am transffering material data then 
my message type would be MATMAS it is predefined.

in the same way if i am tranfering Customer data then my 
message type would be DEBMAS.

And So on.

to create a message control:

if you want to send a po go to  <me21n> select/create the 
po.no click /messages/ enter details of output type, medium 
and partner , also configure the same in <nace>.

go to <we20>
select the vendor and double click the message type will 
take to another screen.
click message control and enter the details with respect 
to /messages/ and give the process code & save.

message control will be created.

msgcontrol is mainly used for transactional data to enerate 
the idoc.frist u identify wt type of data u want transfer.
for using msg control we20 tcode inbound 
parameters,outbound parametes,mudium in which vrous 
componetsu fill it

it should be handled by technical consultants

IT IS FUNCTIONAL

Functional consultant responsibility.