Communication IDOC?

Hi
While using the transaction BD10 to send materials I am getting an message "0 Communication IDOCs created" and "1 master IDOC created".
I have also maintained the Distribution Modal view in the transaction BD64 .
I couldnt understand why Communication IDOC is not created?
Thank You

Do you have a filter set up in the distribution model for that message type?

Similar Messages

Creation of communication IDOC's from BD12

Hi All,
I am triggering BD12 transaction for few customers.
For some set of customers i am able to create both Master IDOC & Communication IDOC.
Ex: For the customers whose Account Group is : 0001
For other set of customers i am able to create Master IDOC but Communication IDOC i am not able to create.
Ex: For the customers whose Account Group is: ZCRD
Customer in account group ZCRD do not have sales area data maintained, where in there is no information maintained for sales, billing, shipping & Partner functions.
Where as customers in account group 0001 have the sales area data maintained.
This is the functional analysis of both the Account Groups.
Can anybody tell the reason why Communication IDOC's are not created for Account Group-ZCRD customers & For Account Group-0001 communication IDOC's are created!
Can anybody solve this issue!
I have debugged this issue step-by-step for both Account Group's [ZCRD, 0001] related customers, There is no check in code for Account Group-ZCRD so that communication IDOC's does not get created.
Also both Account Group's customers went through same piece of code, Only at in F.M call to MASTERIDOC_CREATE_REQ_DEBMAS
the returned parameter CREATED_COMM_IDOCS is 0 for Account group-ZCRD related customer where as it is 1 for ACcount Group-0001 related customer.
Can anybody resolve this issue so that Communication IDOC's will also be created for Account Group-ZCRD related customers!
Thanks in advance.
Thanks,
Deep.

Hi Naveen,
Thank you for the reply.
In BD64 i have checked the details.
There is no checks/filteration against Account Groups-ZCRD/0001.
One more thing is the customers for Account Group-ZCRD are
Credit Master accounts.
Is there any way i can find the resolution for the same!
Thanks for the reply.
Thanks,
Deep.

Problem in the formation of communication idoc

Transfering master data from our system to the client system.
After doin all the outbound configurations from BD10 im sending the materials.
ALL the master idoc are created but only 0 communication idoc is created. how can i solve the problem.

Hi,
Since you are transferring the data through ALE, you need to make settings in BD64 (distribution model) and also WE20 paretner profile.
How to maintain:
BD64:
Go to Edit mode and click on button 'Create model view' and fill the popup inputs 'Short text, Technical name, start date and enddate'.
Now click on button 'Add message type' and give 'Model view, Sendor, Receiver and message type'.
These should be same as that of WE20.
Save it and then try once again. now issue will be resolved.
Please reward if useful.
Regards,
Ramesh

Regarding generating Master/Communication IDOCS's from BD12 forfewcustomers

Hi All,
I have one issue when i am using BD12.
I am inputting some customers and output type/message type and executing the transaction for some customers it is generating both Master & Communication IDOCs, But for some customers it is generating only Master IDOC's but not Communication IDOC's.
These kind of cases are coming for particular Account Group [Ex: ZCRD etc..],
Can anybody tell me what is the relation between Account Grooup & Customer & why it is stopping generation of Communication IDOC's for particular Account group related customers.
How can i solve this issue!
Can anybody solve this issue!
Thanks in advance.
Thanks,
Deep.

Hi All,
Any inputs/Solution for the above posted issue!
Resolution in this regard will be appreciated.
Thanks,
Deep.

O Communication Idocs

Hi
I have an error. In QAS, I have an Idoc to File scenario. I triggered an idoc from WE19 by adding data manually and it reached XI. I went to BD10 and then tried to trigger from there. I got an error like this
1 Master Idoc set up for message type
0 communication IDoc(s) generated for message type
Any clue why I get this error ?
Midhun

Sandeep
I created a Model View. Now, I don't see nodes under that as I see under other scenarios. I only see the Model View that I created ECC_XI_File. How do I get nodes? I just have one line there. I saved it. Should I add more details ?
I have only entered the four fields
Where do I enter the Logical System Names of both Source and Target ?
Midhun

Communication IDoc is not generating after master IDoc for "DEBMAS"

Hi gurus,
i have done all steps from the beginning to the end for an Idoc transfer of type "DEBMAS".I have created the settings in BD61,BD50 and BD52.And also i can work with other master message types like ARTMAS.I didn't give any filter groups in BD64 for the message type "DEBMAS".When ever i execute BD21(RBDMIDOC) only master idoc is generating,there is no communication idocs for the message type "DEBMAS".Please help someone in this issue.
My special question / doubt is, when ever a master idoc creating ,is it must to create a communication idoc ,if there is no filter in "DEBMAS"?
Please clear someone and explain my doubt.
your help will be highly appreciative...
rgds
tom
Moderator message: Please don't use all upper case in subject line
Edited by: Thomas Zloch on Feb 28, 2010 5:25 PM

hi,
communication IDoc is missing when ...
- Distribution Modell is missing
- Filter in Distribution Model is existing an no IDoc is generated (Filter at KNA1M segment only)
try the following.
Goto BD12. Choose your partner and the receiving System and send an IDoc.
Is the Comm. IDoc generated ?
if yes ... there is something with your ChangePointer Logik (BD52, .... look at Table BDCP/V)
if no ... you should take a deeper look at BD64 distribution model.
Maybe the receiver partner or filter is not correct.
good luck,
Gordon
Edited by: Gordon Breuer on Feb 25, 2010 1:12 PM

Difference b/w Master & Communication IDocs

Hi All,
What is the difference b/w Master & Communication IDocs.
Akshitha.

The master Idoc is the Temporary Idoc & kept in memory buffers until communication IDocs are generated. These recipient-specific IDocs are called Communication IDocs and are Stored in the Database.
But the master Idoc is not.
The Communication IDocs are transferable IDocs not the Master Idoc. For every Receiver, each separate communication Idocs will be created from master Idoc.
more info on idocs....
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Regards
vasu

Problem in communication IDOCS

Hi all,
I am facing a problm in setting up of communication IDOC while sending a material from 1 system to the other . I checked all the configuration settings in setting the RFC, creating ports , and distribution model and so on....
After creating a partner profile and distribute the model i am checking in bd10
it is giving me the status as 1 master idoc has been created and 0 communication idocs has been generated .
Can any one of please suggest me where I am going wrong ?
points rewarded

Hi,
check the below settings for distributing material master data..check if u have done all these steps..
For distributing master data like material master, vendor master, customer master we have standard transaction codes that are provided by sap.
Bd10(send material master)
Bd12(send customer master)
Bd14(send vendor master)
Bd30(boms)
The order of Tcodes are:
           Bd54 (creating logical systems)
           Scc4 (assigning logical systems )
           Sm59 (rfc destination)
           We81 ( message type)
           We30 ( idoc type)
           We31 ( segment type)
           We82 (linking message type and idoc type)
           We21 (creating port)
           We20 (partner profiles)
           Bd64 (Distribution model)
           Bd10 (material master)
Ex: material master.
     Message type: matmas.
     Idoc type: matmas05.
Regards,
Nagaraj

No Communication Idocs are creating with the tcode BD21 for ARTMAS

Hi,
I am executing BD21 for the message type ARTMAS to trigger the Article master change pointer idocs. Before executing it I have changed the Article message using the t.code MM42. After executing the BD21 it is only creating Master Idoc but not Communication Idocs. If any one have idea on this please help me.
Regards,
Vasu.

Hi Jack,
change pointer configuration is ok for the message type ARTMAS. Also the MAKT-MAKTX is also there in the tcode BD52 for the message type ARTMAS. Once I change the material through MM42, I am able to see the entry in table BDCP2 but not in table BDCPS. I am able to trigger the idocs through BD10 successfully.
Regards,
Vasu.

0 Communication IDOCS

Dear XI experts,
I have setup a distribution model with the message type MATMAS and setup the partner profile to send IDOC from SAP to XI. I get this message below
Model view SCBIT40 has not been updated
Reason: the following ALE connection already exists in model view SCBIT01
..... message type MATMAS
..... sender M2ECLNT800
..... receiver M2ECLNT001
When I try to send the material through transaction BD10 it gives me a message
0 communication IDoc(s) generated for message
MATMAS
Thanks for your analysis.
Br,

Hi,
I had one distribution model and I deleted it. I´ve created a new one using the same logical client and the same message type but when i go to ditribute I obtain this error :
Model view TEST_01 has not been updated
Reason: the following ALE connection already exists in model view PA/OM
..... message type HRMD_A
..... sender HRMCLNT400
..... receiver HRECLNT500
I´ve read your post,, could you explain mehow I can the client assigment?
thnaks a lot and best regards, Sapera

Master& communication idocs

if i send an idoc to 5 recipents how many master & comunication idocs will be generated

1 master and 5 communication idocs.

No Communication IDOC generating for MATMAS --- Urgent

Hi,
I have two systems in the Landscape; one is DA1 and other is DA3. Both systems are exactly identical.
When I am triggering idoc of message type MATMAS from bd10 in DA1 systems, it successfully generating MATMAS idoc and I am able to see that idoc in we02 but when I am triggering MATMAS idoc in DA3 system; it is generating Master IDOC but it is not generating Communication idoc for Message type MATMAS and in we02 as well I am not able to see any such idoc.
Both the Systems are exactly same and I have checked ALE configurations in both the systems, they are same.
Can anyone suggest, what could be the problem.
Regards,
Varun

hi,
As Bineah mentioned check the distribution model, distribute it and generate partner profile. verify all the configurations once again i hope it will do.
if any queries let me know .
~linganna

What is memory idoc , communication idoc

plz tell me about
         memory idoc , communication idoc.

hi kalyan,
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..comm idoc is the physical idoc which is reciever specific
IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
   Depending upon the triggering mechanism i.e change pointer,message control
   etc the programming technique changes and the type of process.
2)Existing IDOC was extended
   User Exits are used to populate data in new segments added and to read them
   back.
3)To enhance an exsiting process.
   User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP      IDOC type
MESTYP    Message Type
RCVPRN    Recieving Partner (Destination)
RCVPRT    Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
                is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
       INT_EDIDD-SEGNAM = 'ZSEGMENT'
       W_SEGDATA-field1 = value    "taken from some table
       W_SEGDATA-field2 = value    "taken from some table
       INT_EDIDD-SEGDATA = W_SEGDATA
       APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
      There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
      In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in
the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
thanks
abdul
reward me if usefull

ALE distribution error - 0 communication IDOC

Hello,
We are getting 0 communication IDOC generated for message type DOCMAS error for ALE document distribution error. Please advice where to look for the error.
Anirudh

hi,
ani,
u check this,
If you want work items to be created when errors occur for the purpose of error handling, you need to assign the standard task TS40007915 PCROLL to a position or a workflow organizational unit.
Or
You can also distribute dependent objects manually for classes. You can use report program RCCLDIHI to distribute a complete class hierarchy including all classes characteristics, and characteristic values.
Only the message code (004 - change) is allowed for sending a document (message type DOCMAS). This function also creates the document in the target system.
You can control the sending of documents with the indicator Distribution lock. An object with this indicator in its status will not be distributed into other ALE systems.
You can set the indicator in Customizing Document Management System  Define document type  Define status. The distribution lock is read when a distribution automatically starts after a change pointer is set or for an Integrated Distributed PDM Solution (ID PDM).
You can ignore this setting by starting the distribution manually. When you set the indicator Ignore distribution lock in the initial screen, then all documents will be distributed overriding the previously set status.
You control the distribution of object links with the indicator You cannot maintain the object links via ALE and Object link unchanged in target system.
Information about object links are distributed through IDoc type DOLMAS01.
The data is transferred to the workstation application and to storage data in IDoc type DOCMAS04 if an original file exists to a document. The Remote Function Call interface protocol transfers the contents of the original file, for example text or design drawing.
You can determine whether you want originals of a certain document type to be distributed by ALE into another system under the setting Document Management System  Define document type  Define transport of originals for ALE. You can control distribution with various criteria.
You want to distribute all original files of the application WRD (Microsoft Word) for the document type R-1 (report) that are stored in vault VAULT1 (Vault for Office Applications). You do not want to distribute documents of the same document type for the application WWI (Winword 6.0).
You can process the status for the desired objects.
1. Select in Customizing Cross Applications Components  Distribution (ALE)  Standard ALE Business Processes  Logistics  Master Data Distribution  Integrated Distributed PDM Solution (ID PDM)  Object status (for example, Define BOM status).
2. Process the indicator Distribution lock
ben

Master IDOC but not the communication IDOC

Hi
what is master IDOC and the communication IDOC
what is the diff?
i have installed sap gui in my system and how to connect the sapserver through internet?

HI SAPABAP,
1>Master idoc is only created but it won't be stored in database,where as communication idoc is stored in database.
2>Data is transferred via communication idoc not by master idoc.
Regards,
Nagaraj

Communication IDOC?

Similar Messages

Maybe you are looking for