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.

Similar Messages

File2idoc:Error in ALE distribution model for SendResponse

Hi,
I'm using XI to configure a file to idoc scenario.
Now in WE19 I could see relevant data,but in WE05 it showed the error status 51,and the detail message was "Error in ALE distribution model for SendResponse".
Do I have to create a distribution model in BD64?I did this ,but failed to create.

hi,
i dont think distribution model is required for inbound case.
just check the below configuration.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
chirag

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

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

Error while generating Distribution Model in ERP to EWM

I am trying to generate new distribution Model from ERP to EWM for my warehouse.
In system one distribution Model already exists for another warehouse. Below error encountered.

Hi Suraj,
Thanks for the answer
Yes i was using the Wrong Distribution Model , I should have selected EWM , but i was giving some new name as i thought that was required. Hence message came.
I did with EWM distribution Model and all worked well.
Thanks
Inder

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

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

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

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

Re : Distribution model is currently being processed

Hi
While doing Maintain distribution model and distribute views the following error is coming
"Distribution model is currently being processed"
How to solve this
Thanks
Mani

That means some body else is Running BD64. That mean the transaction is locked. So Try after some time.
Check in SM12 any locks on BD64 transaction.

Error while distributing a distribution model in BD64

Hi,
I am trying to send an IDOC from one client to another client of the same SAP system. To achieve that, i have created the necessary logical systems and made the necessary partner, port configuration as well as RFC Destination. In BD64, I have created a new model and added a BAPI 'SAVEREPLICA' and Object 'BUS1093' using Add BAPI button. But when I am trying to distribute the model it's giving the following error - 'Model view ABCDX has not been updated. Rreason: Distribution model is currently being processed'.
Kindly help,
Thanks in advance,
Deep.

Using of BAPI is not accepted between two clients of the same system, you'll have to use different SAP systems

How to restrict the idoc creation based on the distribution model

Hi all,
I want to create the idocs for certain material types only, for this i configured Distribution model and set the filter for material types.
If the delivery is created with the material type which is not in the filter means,
Idoc is creating for that Delivery with header segments only and restricting Item level segments.
it is coming to XI and failing in mapping every time.
I do not want to generate the whole idoc itself. Am i missing any thing??
Regards
Edited by: Suman gupta on Jun 10, 2010 11:13 PM

Hi Mike,
>>config in PI in the routing condition - if no lines exits don't send the message to the mapping/receiver
If no lines exists we can restrict don't send to receiver, but how can we restrict dont send to mapping??
It comes to mapping and failing in PI MONI.
Is there any way that i can restrict the Idoc generation itself in ECC ??
Regards

R/3 to XI (Idoc to File): Do we need to maintain distribution model in R/3?

Hi All,
I have a very basic question regarding Distribution model.
My scenario is IDOC-->File ( SAP R/3 --> XI). So all I am trying to do is send the IDOC frrom R/3 to XI. ( Within XI I am going to do an FTP to the 3rd party file server)
I have created a distribution model, but was wondering if I really need to create one as message is going from R/3 to XI and not from R/3 to another R/3.
Please help let me know If I need to distribute this model to XI or to SAP production sytem or I do not need to duistribute at all for this scenario.
Thanks
Shirin

Hi,
if you create partner profiles and port via t.code.
i hope, it's not required to maintain Distribution model.
please check the below points.
Configuration Steps for Idoc to File Scenario.
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
To Configure the IDOC TO FILE SCENARIO, SETTINGS IN SAP-XI
STEP 1:ALE SETTINGS IN SAP-XI
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) ALE SETTINGS TO POST IDOC OUT OF SAP-R/3 ***********************************************************************
a) Create RFC Destination using T.code in SM59.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item u2018Generate Partner Profilesu2019
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> u2018Distributeu2019 to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
warm regards
mahesh.

Use of Distribution model in Idoc to file

Hey guys
just outta curiosity,why do we need to create distribution model for IDOC to file scenario,we can ofcourse do the scenario without creating Distribution model (by using WE19 to send IDOC's).
is it because for day to day transactions we wont go for WE19(its just for test purposes),we rely on Distribution model?
also is it job of XI developer to create DM ?
thanx
ahmad

Ahmad,
BD 64 Distribution model allowed you to automatically create the Logical Systems ( BD54 ) and the partner profiles.
The steps you create to send an Idoc from your R3 system to XI ,( Bd54, we20 ) etc are all nothing but steps in the Distribution Model Bd 64 to send an Idoc to XI,
Regards
Bhavesh

Problem with IDoc filtering in the distribution model

Hello Experts,
We are using a distribution model in which we have set filters as like the following
Filter Group 1
Plant : XYZ
Sales Org: SAP1
As far as the documentation says this Condition should work with AND logic between Plant and Sales Org
(i.e ~ Plant XYZ and SO SAP1 ) but the IDoc gets created even if any one of the condition is met(looks like working in OR logic).
How to achieve the AND filtering between the different objects.
Would appreciate your kind help.
Thanks in advance.
RGds,
Vasanth.

> Jakub ~ Yes I checked the generated IDocs(classified pertaining to my Model)for my model alone and that's where we are facing this problem
So that's the filtering problem.
I would check in which segments are the "filtering objects" located (BD59) and whether it is a mandatory segment. If it is a mandatory segment - IDoc should not be created. If it is an optional segment - this segment and its subsegmets will be filtered out - but IDoc will be created.
> ~ Do we need to apply some SAP Notes to avoid this problem ?
> But why the filter should behave in OR fashion ? I do not understand.
I believe that Sachin meant that the logic is:
Filter Group1 OR Filter Group 2 OR ... Filter Group N
Filter Group 1 Object 1 AND Filter Group 1 Object 1 ... AND Filter Group 1 Object M
Filter Group 1 Object 1 Value 1 OR Filter Group 1 Object 1 Value 2 OR ... Filter Group 1 Object 1 Value L
regards,
Jakub

Error in IDOC Distribution Model

Similar Messages

Maybe you are looking for