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

Similar Messages

How to find the number of idocs generated for a customer on the basis of his purchase order in a day ?

How to find the number of idocs generated for a customer on the basis of his purchase order in a day ?

Dear Friends,
I am absolutely agree with your answer .
But my question is,
Lets say.....
One customer sending X number of purchase orders in a day , so how many IDocs generated on that specific day for that specific customer .
So, Question is , How can we find the no of sales orders(IDocs) generated for the customers on the specific day ?
Hope you all understood my requirement .
Thanks & Regards,
Aditya

Usage of ALE - idocs generated for BAPIs

Hi
I need to use - the std idocs generated for BUS2032 object - CREATEFROMDAT2 method to store the BAPI call ( BAPI_SALESORDER_CREATEFROMDAT2 )data for those sales orders that could not be created.
If I want to use the SAP delivered BAPI ( BAPI_SALESORDER_CREATEFROMDAT2 ) to call as it within an ABAP program - and then if the call did not go through - then log the data for BAPI into the corresponding idoc with the message type SALESORDER_CREATEFROMDAT2 ( idoc type SALESORDER_CREATEFROMDAT202 ) do I need to move the values from the BAPI structures to the idoc segments programatically ? Or since the idoc is linked to the BAPI - by definition, is there an implicit way to move data to the corresponding idoc segments and save the idoc .
Can anyone out there give me a code sample to do - what I have asked above ?

Hi,
I guess you can use function module ALE_SALESORDER_CREATEFROMDAT2 to create idoc from bapi data. You can pass the entire data in internal tables that you are passing to BAPI into above mentioned function module and then it will create an Idoc for the same. Also populate the receivers in the internal table receiver.
KR Jaideep,

0 idocs generated for msg type cosmas

Hi everyone..
please help out with this idoc issue
I'm trying to send data with msg type COSMAS from 800 to 810 using BD16 as follows:
it just says 0 idocs generated.
I have again gone back and checked my customizations but can't figure it out.
the steps i have done are:
create and assign logical systems
open rfc connections from both c800 and c810
create model view and assign msg type in bd64 in c800.
create partner profiles in both c800 and c810.
open port from c800 .. .DO i have to open a port from c810 as well??
Some doubts I have :
do i have to do :
"Generate the partner profiles by selecting the navigation path from the main menu, Environment --> Generate Partner profiles"
from BD64 after i create the model view and add msg type COSMAS.
regards,
allwyn

HI
no, i have not done anything relating to bd64 in c810 ..that wasn't mentioned in the notes I am following .. Do I have to repeat the same steps like I did in c800?

Idoc generated for creation of sales order

Hi all,
In my project we have two different boxes-I and B.When a purchase order is created in I Box an idoc is triggered which goes to the B Box and creates a sales order.I want to do some changes in E1EDKA1 and E1EDPA1 segment in the idoc in I Box so that when it goes to B Box it will show the changed one.For example if there is EN in E1EDKA1 and E1EDPA1 segment then in B Box it will be appeared as ZA.I need to know that for this change I have to do the coding changes in which USER EXIT?The function module which is triggered during the sales order creation in B Box is IDOC_INPUT_ORDERS.
Thanks in advance
Raj

Hi Raj,
go to se37..
enter the function module and after each segement append there is a customer exit and badi is available to add you custom code..
in the user exit read the segement and modify the segemnt data..
these are the below exits available for the Orders
ORDCHG I VEDB0001 Sales Ord. Change
ORDERS I VEDA0001 Sales Orders "this is the user exit for you to code..
ORDRSP I MM06E001 Order Response for
Purchase Order
search-- CALL CUSTOMER-FUNCTION '011'--Fm--EXIT_SAPLVEDA_011--include--INCLUDE ZXVEDU13.
Regards,
Prabhudas

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

1 matser idoc generated but 0 communication idoc .

hai all.
am practising ale-idoc.and sending material with message type MATMAS.
i done rfc connections . b/w 800 n 810. i got it .
but my prob is
1 master idoc generated for message type MATMAS.
but 0 communication records generated for msg.type MATMAS.
idoc is not generated
how can i rectify this erorr.
pls do helpful.
tanx in advacne .
Satya.

Hi Satya,
The ALE distribution model defines which applications in your distributed systems communicate with each other and which types of data are distributed. You require a separate ALE distribution model for a Central User Administration (CUA).
In the central system, you define the structure of your Central User Administration in the model view, which you then distribute to the child systems.
Two types of data are distributed in the ALE distribution model of the CUA to be defined:
· User master data (including assigned roles and profiles)
·Company addresses
You require two methods in the distribution model to distribute user data and company addresses. These methods are realized using BAPIs of the business objects USER and UserCompany with the method clone.
You can check the following links for details.
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a610f507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a610f507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/44/1a243754192009e10000009b38f839/frameset.htm
Give points if the answers are helpful.
Regards,
Biswa.

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.

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

Double IDocs Generated from SAP

We create delivery in R/3 using VL01N & subsequently pick & pack changes done with VL02N. Then normally ONE IDOC is generated.
Problem.
Here 2 IDOC's generated for a single delivery document.
How can this happen? pl help.
We processed the same data in WE19 for testing but in this case only One IDoc gnerated.

All settings are OK.
On that day almost 300 IDocs Generated for different deliveries.
But only 2 IDocs get generated from sinle Delivery.

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

CRMXIF_ORDER_SAVE IDOC not getting generated for BUS_TRANS_MSG BDOC

Hello Experts,
In our project, we have a requirement to send custom fields in the BUS_TRANS_MSG to external system through XIF. The model of BDOC BUS_TRANS_MSG triggering IDOC CRMXIF_ORDER_SAVE_M02 perfectly worked in the development system. We wanted to try the custom field extension in the Sandbox. So as per OSS note 916093, we have extended E101_CRMXIF_CUSTOMER_H segments with custom fields and tried generating the interfaces in BDFG transaction. While generation with IDOC CRMXIF_ORDER_SAVE_M we got an error message "Incompatible change to complex data type
type E101CRMXIF_ISU_PRA1_X". So went about creating a custom IDOC ZZ_CRMXIF_ORDER_SAVE_M02 for message CRMXIF_ORDER_SAVE. Even for this config, the IDOC is not getting generated for the BDOCs. Lastly, configured the IDOC ZZ_CRMXIF_ORDER_SAVE_M02 to a custom function module ZZ_BDFG_IDOC_TEST_FM. The FM got generated and activated, even then the IDOC is not generated for the BDOC.
SMOEAC config in Sandbox looks the same as the Development system. We do not the reason why IDOC is not getting generated and also the reason for error in BDFG while generating the interfaces after adding custom fields to CUSTOMER_H segment.
Any help would be appreciated.
Thanks,
Partha

Hi Partha,
Kindly check the following thread.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f?QuickLink=index&overridelayout=true
XIF adapter
Hope it answers your Query
Regards,
Srikanth.Naga

Several idocs got generated for the PO transmission

Hi,
We have got a problem regarding the transmission of PO via email or idocs. While PO generates only one output type with NEU. there are several idocs and email (depending on the condition record for the vendor and purchasing organization) getting generated and are dispatched to the vendor. There should be only one idoc or email generated for the PO dispatching to vendor.
Did anyone of us get this problem in the past? Please share your experience with me and if you have any solution for the same.
Best regards,
Subhash

Hi BK,
Thanks for your answer but there is just one condition record for this vendor. The problem is that, there is only one successfully processed message type 'NEU" in the purchase order but multiple idocs or emails are generated within a timespan of few seconds/minutes. These multiple records can be seen is SOST list (in case of email) and WE02 (in case of idocs).
Thanks n BR,
Subhash

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.

In DOM (or EOM) scenario, no IDOC is generated for XIF_IDOC site type

Hi friends,
I have a problem with an XIF_IDOC site in the Distributed Order Management (DOM).
We are using DOM scenario to separate and distribute CRM sales order
items to different sites. Under the tcode SMOEAC, I defined a new site
called "EKSIRLANDA" whose type is external interface for IDOC
(XIF_IDOC). I made a subscription of "DOM items" (DOM Order Split
(MESG) ) for the EKSIRLANDA site. After that, (under the tcode WE20) i
defined EKSIRLANDA logical system partner profile with the outbound
message type "CRMXIF_ORDER_SAVE_M". I saved a new order under the tcode
CRMD_BUS2000115, but no IDOC generated. After checking all the related
customizing and the CRM_DOM_ITEM_DISPATCH method implementation of
CRM_DATAEXCHG_BADI everything seemed all right. By the way, we are
using CRM_DATAEXCHG_BADI badi to separate the related items to the
related sites. Anyway, i added another subscription called "All
Business Transactions (MESG)" to the EKSIRLANDA site and saw that 2
IDOCs are generated. I investigated those 2 IDOCs. One of them is what
i want. In other words, it contains only the related order items that
are separated from the others in the CRM_DATAEXCHG_BADI
(CRM_DOM_ITEM_DISPATCH method). The other IDOC contains all the order
items. I do not want this second IDOC. If i remove "All Business
Transactions (MESG)" subscription and leave the "(DOM Order Split
(MESG)" subscription alone, no IDOC is generated. This is the problem.
Why does not "DOM Items" subscription alone generate any IDOCs? IDOC
settings are not wrong because when i add "All Business Transactions
(MESG)" subscription to the EKSIRLANDA (XIF_IDOC) site, the IDOC is
generated, but this time an extra IDOC containing all the items is also
generated. What is the problem?
Thanks in advance for your help.
Mehmet Karasu

nobody has no idea for this question ???

No Communication IDOC generating for MATMAS --- Urgent

Similar Messages

Maybe you are looking for