IDoc distribution

Hi,
I have one query while dealing with ALE configuration. Suppose I have to distribute IDoc in multiple system i.e. one sending say client 100 & receiver say client 200, 500, 700.
How to deal if we have to distribute Idoc's to multiple systems.
Plese tell me step by step starting from configuration.

hi neha
yes i think its possible.
u go to transaction BD87.
there u can select range of partner system to which the idoc is to be send
and then select the idoc to be send in that
but i suppose u will have to create the distribution model for them.
please try using this option
regards
ravish
plz reward if useful
Message was edited by:
ravish goyal

Similar Messages

IDOCs Distribution Model: filter whitout Filter group

Hi guys!
In my IDOCs distribution model of IDOCs with Message Type "Z", when i try to add a Filter, in the popup dialog to enter the Filter group i canot see nothing...only a line with a "Dependent on class membership: Requires classes to be defined in the sending system"
but not show the expected fields like Sales organization, or the Account group
¿this is a custonizing problem?
Best Regards,
Antonio

Hi,
First, create ALE Filter objects via BD95 (if they do not exist yet)
Secondly, assign ALE Filter objects to your message type for the appropriate segment: BD59
Then, run bd64 ...
Regards,
Jakub

Specific IDoc + Distribution Model = pb of filter

Hi,
I created a Message Type "ZHRMD_A" and an extension "ZEXT", and I use the standard IDoc type HRMD_A06. Thus my Idoc is: ZRMD_A.HRMD_A06.ZEXT
All work fine: my ECC send correctly this idoc with the good values...
But my problem is inside the Distribution Model (BD64): I haven't the line "Data filter active" under my Message Type ZHRMD_A, so I cannot add filter !
Can I add filter on a specific Message Type?
if yes, how?
any idea is welcome.
Regards
Mickael

Hi,
u can use the tcode- BD56 for segment filtering.Also check for BD95.
Regards,
Nagaraj
Message was edited by:
nagaraj kumar nishtala

Error in IDOC Distribution Model

HI all ;
Please Help me in this Issue!!
am working with standard IDOC Using MATMAS (Material Master Transfer)
LS_800 - Outbound.
LR_810 - Inbound.
--> BD54.
--> SCC4.
-->SM59.
-->WE21.
-->WE20.
--> WE20 ( in inbound side) Clear Up to this level.
After that the Problem in Distributing the Model,,,,
In Bd64 t-code Distribution Model.
while Generating the Partner Profiles in BD64 ;
its giving the blank message like below.
No message has been defined for the selection conditions in the model.
when we distribute(in BD64) 2 Errors (red) Like Below;
RFC destination for Syncronous Communication (Message type SYNCH)
Partner Profile LS LR_810 SYNCH does Not Exits.
Generate Partner Profile.
or Specify outbound partner Profile for message type SYNCH
RFC destination for Syncronous Communication (Message type SYNCH)
Partner Profile LS LS_810 SYNCH does Not Exits
Generate Partner Profile.
or Specify outbound partner Profile for message type SYNCH
Thannks;
Upender.

In Bd64 t-code Distribution Model.
create the model view ,
add message type Matmas to it.
-> select the model view
->environment-> generate partner profiles
In Partner Profiles u hv to maintain the Outbound parameters in Both LS_800 &
LR_810 .
in receiver port, double click & make sure that the rfc destination assigned connects successfully..
Regards.

ALE/Idocs Distribution Model

Hi
I am facing one problem in distribution model. Im trying to send idocs from one system to another. The distribution model has been created and been distributed to the other system. so no error comes in the source system. Even the idocs are generated without error.
Now in the receiving system,
1) after the distribution model is created in this system by distribution option from the source system and when i try to generate the partner profile in this system. It gives the error that " No messages have been defined for the selection conditions in the model". Though everything is created here.
2) the idocs reaches in this system but in error state. Again the error says partner not found.
Now am not able to understand how to rectify this problem. when the model is distributed why this partner is not being created automatically.
can anybody help???
regds
sanjeev

This is the error that comes when I run the FM (FM is active) contrary to the error:
Runtime Errors         CALL_FUNCTION_NOT_ACTIVE
Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          20.11.2007 12:13:39
Short text
     The function module is not active or contains no code.
What happened?
     The function module "ZIDOC_INPUT_ZADR_MESSAGETYPE" is called, but
     cannot be found in its function group.
     Error in the ABAP Application Program
     The current ABAP program "ZIDOC_INPUT_ZADR_MESSAGETYPE==FT" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
      not caught in
     procedure "FUNCTION_CALL" "(FORM)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The program "ZIDOC_INPUT_ZADR_MESSAGETYPE==FT" contains the CALL FUNCTION
      statement.
     The name of the function module to be called is "ZIDOC_INPUT_ZADR_MESSAGETYPE".
   but "ZIDOC_INPUT_ZADR_MESSAGETYPE" cannot be found in its function group.
   Possible reasons:
   a) The function module "ZIDOC_INPUT_ZADR_MESSAGETYPE" has not been activated.
    Therefore,
      it cannot be found at runtime.
   b) The Function Library contains an incorrect entry for
    "ZIDOC_INPUT_ZADR_MESSAGETYPE".
   c) The function module contains no code, even FUNCTION ... ENDFUNCTION
      is missing.
Missing RAISING Clause in Interface
    Program                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Include                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Row                                     69
    Module type                             (FORM)
    Module Name                             FUNCTION_CALL
Trigger Location of Exception
    Program                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Include                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Row                                     93
    Module type                             (FORM)
    Module Name                             FUNCTION_CALL
Source Code Extract
Line SourceCde
   63 *
   64 DATA: OTHERS(1).
   65 *
   66 FORM EXISTENCE_CHECK CHANGING VARIA.
   67   VARIA = 1.
   68 ENDFORM.
   69 FORM FUNCTION_CALL.
   70   CLEAR %_OWORKFLOW_RESULT.
   71   CLEAR %_OAPPLICATION_VARIABLE.
   72   CLEAR %_OIN_UPDATE_TASK.
   73   CLEAR %_OCALL_TRANSACTION_DONE.
   74   CLEAR %_OIDOC_CONTRL.
   75 %_OIDOC_CONTRL = %_IIDOC_CONTRL.
   76   CLEAR %_OIDOC_DATA.
   77 %_OIDOC_DATA = %_IIDOC_DATA.
   78   CLEAR %_OIDOC_STATUS.
   79 %_OIDOC_STATUS = %_IIDOC_STATUS.
   80   CLEAR %_ORETURN_VARIABLES.
   81 %_ORETURN_VARIABLES = %_IRETURN_VARIABLES.
   82   CLEAR %_OSERIALIZATION_INFO.
   83 %_OSERIALIZATION_INFO = %_ISERIALIZATION_INFO.
   84 * TRANSAKTION = 'Repo', PROGRAM = REPORT
   85   IF ATRA = '1'.
   86     SET RUN TIME ANALYZER ON %_INTERNAL.
   87   ENDIF.
   88 IF DESTI IS INITIAL.
   89 IF DEBUG = '1'. BREAK-POINT AT NEXT APPLICATION STATEMENT.
   90 ENDIF.
   91 DEBUG = SPACE.
   92 GET RUN TIME FIELD TIME1.
>>>>> CALL FUNCTION 'ZIDOC_INPUT_ZADR_MESSAGETYPE'
   94 EXPORTING
   95 INPUT_METHOD = %_IINPUT_METHOD
   96 MASS_PROCESSING = %_IMASS_PROCESSING
   97 IMPORTING
   98 WORKFLOW_RESULT = %_OWORKFLOW_RESULT
   99 APPLICATION_VARIABLE = %_OAPPLICATION_VARIABLE
100 IN_UPDATE_TASK = %_OIN_UPDATE_TASK
101 CALL_TRANSACTION_DONE = %_OCALL_TRANSACTION_DONE
102 CHANGING
103 IDOC_CONTRL = %_OIDOC_CONTRL
104 IDOC_DATA = %_OIDOC_DATA
105 IDOC_STATUS = %_OIDOC_STATUS
106 RETURN_VARIABLES = %_ORETURN_VARIABLES
107 SERIALIZATION_INFO = %_OSERIALIZATION_INFO
108 EXCEPTIONS
109 WRONG_FUNCTION_CALLED = 001
110 ERROR_MESSAGE = 002
111 OTHERS = 003.
112   IF ATRA = '1'.

CUA - IDOCS - DISTRIBUTION UNCONFIRMED STATUS

Hi,
I have seen the strange issue in CUA IDOCs with respective of a child system...
That is, If i do the user maintenance with respective of the child system in the central system and save it.
1) then the system is generating the IDOC's for central and the respective child systems.
2) The changes are getting reflected to the respective child system.
But when i check SCUL in CUA, still it is showing as DISTRIBUTION UNCONFIRMED STATUS
I have verified the below things
A) OUTBOUND and INBOUND jobs in central and Child are working fine.
B) IDOCS are getting posted in child system with status 53
C) RFC connection is fine
D) Partner profiles are fine
E) SCUA - showing green
NOTE:
The issue is happening only for one system -client and all other systems and clients were working fine without any issue
Kindly let me know your opinion
Sv

>
> NOTE:
>
> The issue is happening only for one system -client and all other systems and clients were working fine without any issue
Hi,
Please follow the [SAP Note 169538 - CUA: Too many unconfirmed users in the log|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=169538].
Is the RFC from that Child system to Central system is working properly?
Basically this kind of Unconfirmed status happens when the IDoc processing get stuck due to too many IDoc generation. You can schedule a job in that child system for the report RDBPROCESS to process the unprocessed IDocs in a certain interval of times.
You may also want to check the changes happened in SCUL by [SAP Note 632486 - Improvements to transaction SCUL|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=632486].
Regards,
Dipanjan

Inbound idoc- distribution model

Hi,
    Is it mandatory to create distribution model for inbound idoc processing?

Hi all,
        Mine is inbound scenario.
        Sender is XI system
        Receiver is R/3 system.
        Do i need to maintain distribution model for this?
1.As per my knowledge, distribution model is only created in outbound scenario? In inbound scenario why distribution model is not created?
2.On the outbound side, after generating partner profiles we get SYNCH SYNCHRON in outbound partner profile. My question is there any setting to generate partner profiles on inbound side also?
or else SYNCH SYNCHRON will be for only outboud?
Please clarify........

Idoc distribution with status of error records.

Hi Gurus,
my business requirement is i want to creat the Outbound Interface to distribute the data from sapserver to ESB server using the one userdefined function module, in this custom function module i written the logic to validate the input data if validation is file those error records are updated to one return table parameter and using the FM Master_Idoc_distribute for create and distribute the sucessfull records. till its working fine (with status 30-ready to dispach, 01- idoc creatd is in we05 and i have done the all configaration of message type creation, idoc type creation, port, partnerfrofil) ,
but my requirement is , for example if in 10 records even one record is also error records then no need to distribute the idoc data to sending system, just i want to send the idoc number with status error with error message.
plese suggest me the appropriate procedure.
Thanks & Regards,
Sai Ram.

Hi,
in ur code ur filling the idoc data rcord, control record ryt ..before u append data to idoc data , u r also validating and u might be doing in loop for appening the idoc data.
if there is any error in idoc then it won't distribute the data, it will be in error status only..u can only see the data in WE02. Then u can also change the data in WE02 and redistirbute it via BD87.
if u have any conerns let me know
Regards,
Nagaraj

PLNSHP IDOC distribution through R3 system

Hi Experts!
I have a requirement to distribute data from APO through the standard PLNSHP IDOC to an external system. The problem is that I cannot distribute IDOCS directly from the APO system as the message broker (IBM MQ) is only set up in the R3 system and we are not allowed to set it up in the APO system.
Now I'n trying to use the R3 system as a gateway, but the problem here is that the standard IDOC PLNSHP does not exist in the R3 system. I created this IDOC in the R3 system and renamed the segments to start with a Z so it would fall in the customer namespace (I of course get error messages otherwise) and now the communication between the 2 systems to send the IDOC from APO to R3 works fine. However, R3 cannot process the incoming IDOC as the segment names and basic type differs...
So my question: Is there another way to do this? If not, is there a way to change the incoming IDOC data in the R3 system so the correct segment names and basic type (the ones in the customer namespace in R3) are used?
Thank you in advance!
Iwan Ferreira

Hi Raynald LaGuerre ,
Moslty IDoc Filtering will be done in Outbound Side & not in Inbound Side.
Though the System received IDoc from Different R/3 systems, it has to be filtered in Sending Systems itself and not by Receving Systems.
There wont be any use in filetering the IDoc at Receving side, since it utilises the Network traffic and reached the destination system.
Regards,
Anbalagan

Idoc : distribution model

Dear all,
I m getting following error during distribute model view....
Model view MODEL1 has not been updated
Rreason: Distribution model is currently being processed.
Please help me

HI,
The distrobution model is being used by some other application, so please create a new distribution model and try.
Regards
Sathish

Filters in Idoc distribution Model

Hi All,
We are using message type: HRMD_A to distribute HR master data changes to middleware system. Now my requirement is that i should send changes pertaining to US employees alone.
Do i need to create filter group for IT0001 in BD64 where i need to maintain set of personnel areas assigned to country grouping: 10 - US. or any other approach. Please let me know. Thanks in advance.

Hi,
try to define filters in BD95 tcode and then assign filter to message type in BD59 tcode , then configure the filter in BD64 and then distribute.. see if it works.
Regards,
Nagaraj

Why to use chnage pointers for master data idoc why not the change idoc

Hi Gurus,
I have one doubt about Idoc.
When changes to master data has to be sent Change pointers are configured and used. (CDPOS & CDHDR). In case of the transaction data change change idoc is used as is the case with orders (we use ORDCHG for ORDERS message type to send the chnage details to a order which was already sent to other system.
Why we can't use change idoc or message type whatever, instead of Chnage pointers in case of master data or vice versa in case of transaction data.
Your valuable input will be rewarded with suitable points!!
-B S B.

Hi,
It was a good question ... SAP seems never designed the change pointer to handle transactional data IDocs. Only for master data IDocs distribution purposes.
It may due to volume data ... the transactional data can change many times within a day compare with master data which hardly change or once a while.
Regards,
Ferry Lianto

IDOC for listing/exclusion conditions (transaction VB01)

Hello,
we need to export the conditions for listing or exclusion entered in transaction VB01 (tables KOTG900 ff) to an external sales order system. Does the system provide an idoc for this purpose?
best regards
Rainer Fischer

Check OSS Note 863767 - FAQ: Listing/Exclusion. Per point 6,
6. Question: Can the table contents of material listing and exclusion be distributed to other systems by means of IDocs?
No. In the SAP standard system, there is no IDoc distribution of conditions for the usage 'G' (listing/exclusion).
Regards,

Stop IDOC receiver channel

Hi folks,
I have what seems like a simple question about IDOC receiver channels, but I have yet to find an elegant answer.
My scenario is a Non-SAP system with an http sender through XI to an R/3 IDOC receiver. My R/3 system will go down for upgrade for a 2 day period but the external system will continue to send messages.
I suspect the IDOCs will queue in XI while R/3 is down because the RFC destination is unreachable, but I would like to stop attempts to send while the R/3 system is down.
I know about availability times for other channels but this technique is not available for IDOC. Is there some way of scheduling the IDOC distribution from XI so that no attempt to send to R/3 is made during the outage ???
Thanks in advance,
Guy

Thanks Karthik,
That's exactly what I did to demonstrate what might happen (used the wrong password). The message went into error, I reset the password and re-processed and all was fine.
It just seems to me that there should be a cleaner way - maybe something in QOut scheduling ??
Thanks,
Guy

How to get an idoc?

Hi gurus:
When i change a record in R/3,how can i get the record's idoc?
alex zhang

hi
U can use Change pointers:
 ALE Change Pointers
Applications which write change documents will also try to write change pointers for ALE
operations. These are log entries to remember all modified data records relevant for ALE.
Most applications write change documents. These are primarily log entries in the
tables CDHDR and CDPOS.
Change documents remember the modified fields made to the database by an
application. They also remember the user name and the time when the modification
took place.
The decision whether a field modification is relevant for a change document is
triggered by a flag of the modified fields data element. You can set the flag with
SE11 by modifying the data element.
For the purpose of distributing data via ALE to other systems, you may want to
choose other fields, which shall be regarded relevant for triggering a distribution.
Therefore R/3 introduced the concept of change pointers, which are nothing else
than a second log file specially designed for writing the change pointers which are
meant to trigger IDoc distribution via ALE.
So the change pointers will remember the key of the document every time when a
relevant field has changed.
Change pointers are then evaluated by an ABAP which calls the IDoc creation, for
every modified document found in the change pointers.
The Change pointers are written from the routine CHANGEDOCUMENT_CLOSE
when saving the generated change document. So change pointers are automatically
written when a relevant document changes.
The following function is called from within CHANGEDOCUMENT_CLOSE in
order to write the change pointers.
CALL FUNCTION 'CHANGE_POINTERS_CREATE'
EXPORTING
change_document_header = cdhdr
TABLES
change_document_position = ins_cdpos.
Change pointers are log entries to table BDCP which are written every time a transaction
modifies certain fields. The change pointers are designed for ALE distribution and written by
the function CHANGE_DOCUMENT_CLOSE.
Change pointers are written for use with ALE. There are ABAPs like RBDMIDOC
which can read the change pointers and trigger an IDoc for ALE distribution.
The change pointers are mainly the same as change documents. They however can
be set up differently, so fields which trigger change documents are not necessarily
the same that cause change pointers to be written.
In order to work with change pointers there are two steps to be performed
Turn on change pointer update generally
Decide which message types shall be included for change pointer update
R3 allows to activate or deactivate the change pointer update. For this purpose it
maintains a table TBDA1. The decision whether the change pointer update is active
is done with a
Function Ale_Component_Check
Currently (release 40B) this check does nothing else than to check, if this table has
an entry or not. If there is an entry in TBDA1, the ALE change pointers are generally
active. If this table is empty, change pointers are turned off for everybody and
everything, regardless of the other settings.
The two points read like you had the choice between turning it on generally or
selectively. This is not the case: you always turn them on selectively. The switch to
turn on generally is meant to activate or deactivate the whole mechanism.
The change pointers which have not been processed yet, can be read with a function
module.
Call Function 'CHANGE_POINTERS_READ'
The ABAP RBDMIDOC will process all open change pointers and distribute the
matching IDocs.
Dispatching ALE IDocs for Change Pointers
Change pointers must be processed by an ABAP, e.g. RBDMIDOC.
The actual distribution of documents from change pointers must be done by an
ABAP, which reads the change pointers and processes them. The standard ABAP
for that is RBDMIDOC. For recurring execution it can be submitted in a scheduled
job using SM35 .
Reward points for helpful ans.
Regards
Aarti

IDoc distribution

Similar Messages

Maybe you are looking for