Distribution Model View - Error

Hi,
When we try to distribute the model view, we get an error 'Model View has not been distributed. Reason : Maintenance systems for model view D-HR-MD are not identical...Maintenance system in sending system D-OFS-HR.....Maintenance system in receiving system DH3-500' .
What is being referred to as the maintenance system here? Are we missing out on something?
Thanks in advance!
Regards,
Nejuma Iqbal

Hi buddy,
we are also facing the same type of Error in BD64 while distributing the model view
Could you please help me to resolve this error
Regards

Similar Messages

ALE Distribution model view

Hello
I am setting up an ALE scenario to send idocs from system A to system B. I have a problem with the distribution model view. The model has been distributed to the receiving system with the wrong basic idoc type entered in the partner profile. I would like to know how I can change the model view and re-distribute it.
Thanks,
A.P.

Hai
Go through the following Procedure
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
        save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
   select all what ever you want and delete remaining fields.
   save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
   it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
   give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards
Sreeni

Filter in Distribution Model View

Hi,
I am sending HR master data to E-rec system using Distribution Model view.
Here i need apply filter for HRMD_A message type for field Pernr, here the condition is
only one employee data needs to be send, all other employees needs to be filtered.
The problems is as you know there might be thousands of employees (pernr ) which i cannot list out while setting filter.
Please suggest me solution for this.

Hi,
you can use BADI "IDOC_CREATION_CHECK" to Filter those Values and decide to create or not.

BD64-Log of Model View Error

Hi,
In BD64 I have defined the model and also successfully created the partner profile.But after that when I am trying to do Edit/ModelView/Distribute I am getting following error.Can you please help me why am I getting this error?
Target system TESTECF800                  Model view MATERIAL has not been updated
                                                         Reason: No authorization to create model view MATERIAL
                                                      ..... authorization object B_ALE_MODL
                                                ..... Parameter: activity 01 , model view MATERIAL
Regards,
Bedayan.

Hi Bedayan,
As per the error your current profile is not having proper authorization to maintain model view. I think your basis people have revised the authorization objects.
I donot have the authorization to distribute the model view to the target client
Reddy

BD64 - Distribute Model View error?

Hi, Expert:
when I distribute model view using BD64. the following
error message comes:
"Target system is an external System. It does not support this function."
what's the problem? thanks

hi
good
go through this link, which ll give you brief idea about the model view -BD64, i hope this ll help you to solve your problem.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
thanks
mrutyun^

Failed to open model viewer error, for Decision Tree Model

Oracle 11.0.2
SQL Developer 3.0.04
I am trying to follow ODM tutorial here :
http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r2/prod/bidw/datamining/ODM11gR2.htm
After completing initial analysis, I want to investigate the Decision Tree model more closely. As I choose View Models > CLAS_DT_1_1, I get an error message:
Failed to open model viewer
Details are:
java.lang.RuntimeException: not instanceof RoundedTreeNode
     at oracle.dmt.dataminer.mviewer.dtree.model.TreeNode.assignPropertyChangeListener(Unknown Source)
     at oracle.dmt.dataminer.mviewer.dtree.DecisionTreeEditor.setPropertyChangeListener(Unknown Source)
     at oracle.dmt.dataminer.mviewer.dtree.DecisionTreeEditor.open(Unknown Source)
     at oracle.ideimpl.editor.EditorState.openEditor(EditorState.java:283)
     at oracle.ideimpl.editor.EditorState.createEditor(EditorState.java:184)
     at oracle.ideimpl.editor.EditorState.getOrCreateEditor(EditorState.java:95)
     at oracle.ideimpl.editor.SplitPaneState.canSetEditorStatePos(SplitPaneState.java:232)
     at oracle.ideimpl.editor.SplitPaneState.setCurrentEditorStatePos(SplitPaneState.java:195)
     at oracle.ideimpl.editor.TabGroupState.createSplitPaneState(TabGroupState.java:102)
     at oracle.ideimpl.editor.TabGroup.addTabGroupState(TabGroup.java:379)
     at oracle.ideimpl.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:1403)
     at oracle.ideimpl.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:1337)
     at oracle.ideimpl.editor.EditorManagerImpl.openEditor(EditorManagerImpl.java:1263)
     at oracle.ide.editor.EditorUtil.openDefaultEditorInFrame(EditorUtil.java:164)
     at oracle.dmt.dataminer.workflow.WorkflowContextMenu$2.actionPerformed(Unknown Source)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2018)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2341)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
     at javax.swing.AbstractButton.doClick(AbstractButton.java:376)
     at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:833)
     at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:877)
     at java.awt.Component.processMouseEvent(Component.java:6504)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3321)
     at java.awt.Component.processEvent(Component.java:6269)
     at java.awt.Container.processEvent(Container.java:2229)
     at java.awt.Component.dispatchEventImpl(Component.java:4860)
     at java.awt.Container.dispatchEventImpl(Container.java:2287)
     at java.awt.Component.dispatchEvent(Component.java:4686)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4832)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4492)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4422)
     at java.awt.Container.dispatchEventImpl(Container.java:2273)
     at java.awt.Window.dispatchEventImpl(Window.java:2713)
     at java.awt.Component.dispatchEvent(Component.java:4686)
     at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:707)
     at java.awt.EventQueue.access$000(EventQueue.java:101)
     at java.awt.EventQueue$3.run(EventQueue.java:666)
     at java.awt.EventQueue$3.run(EventQueue.java:664)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
     at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87)
     at java.awt.EventQueue$4.run(EventQueue.java:680)
     at java.awt.EventQueue$4.run(EventQueue.java:678)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:677)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:211)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
I get this error for Decision Tree Model only. For other models, there is no problem. How can I fix it?
Thank you.

After setting system language to English, be sure to restart SQL Dev to retry the test.
Make sure you have the latest patches installed.
Go to menu: Help-> About. In the About dialog, select the Extensions tab and check if you have Data Miner version 11.2.0.2.04.40. If not, go to menu Help->Check for Updates, and install the SQL Developer and Data Miner patches.
SQL Dev 3.0 is not certified with Java 7.
Thanks,
Marat
Edited by: mspivak on Jan 10, 2012 12:33 PM
Edited by: mspivak on Jan 10, 2012 12:33 PM
Edited by: mspivak on Jan 10, 2012 12:34 PM

Generate Distribution Model ERP = EWM

HI
I am performing Generate Distribution Model ERP => EWM for new WH. Getting below error message.
Method BUS2015.SAVEREPLICA exists in model view WMS
Message no. BDDISTMODEL051
Please Help to resolve as early
Rgds
Dinesh.P

Hi Dinesh,
When you are trying to Generate Distribution Model for your warehouse that time there are three fields one of those is your ERP warehouse number and Second is Logical System of EWM and third one is Distribution Model view. You might have entered a wrong model view name and then you tried to execute, system is giving you error that ".... method exists in model view WMS" that means you need to enter WMS model view in third field and then execute with radio button selected CREATE ENTRIES along with BOTH radio button selected.
Thanks and regards
Anoop Singh

Error in distribution of model view

I created a modelview for distribution of CLFMAS types IDOCS from DEV to PRD.
Created ports,RFC destination etc.
I was able to generate partner profile in the sending system.When I try to distribute the model view in BD64,
I get this error . Initially, I thought it was because I did not have authorization for BD64 in PRD. Now that I have, I still get this error.. Any advice ?
Distribution of model view CHARS2PRD
Target system PRD100                      Communication error occurred
Process request without transaction. TID is empty.

I see the message did not post properly..THis is the message..
Distribution of model view CHARS2PRD
Target system PRD100                      Communication error occurred
Process request without transaction. TID is empty.

Model view distribution error

Distribution of model view MATMODEL
Target system MATLOGR3
RFC destination for synchronous communication (message type SYNCH)
Partner profile LS MATLOGR3 SYNCH does not exist
Generate partner profile
or specify outbound partner profiles for message type SYNCH
Target system MATLOGXI
RFC destination for synchronous communication (message type SYNCH)
Partner profile LS MATLOGXI SYNCH does not exist
Generate partner profile
or specify outbound partner profiles for message type SYNCH
I am getting this error when i will distribute the moddel view,,...
in Ecc5.0
what i have do now

Hi,
Just chk if hv implemented all the following steps;-
Once the mapping is done then re-check the ALE settings.
SAP XI
1) RFC Destination (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.
2) Create Port (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 (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Ashwin M
Reward if useful

Error in Model View Distribution

Hello all,
Re: Error in distribution of model view
I am referring this thread, as i am facing the same error. The thread does not have answers to solve the issue.
The issue is, when i try to distribute my view i am facing the below error.
Communication Error Occurred
Process request without transaction. TID is empty.
I do have all authorizations, and the Target system is running.
Regards,
Raja

Do any body come across this issue or solved this type of issue, please throw some light on it. Thank you
Edited by: Raja on Aug 25, 2009 10:46 PM

Tcode PFAL there is no model view for the distribution of HR Data.

Hi friends ,
i am facing new problem,i want to send iDOC to other system.
previeous its working fine.
but to day when i open tcode PFAL.
it give me Error:"There is no model view for the distribution of HR master data"
what is the solution for that.
i want to send HR Data.
its urgent please give me any solution ithat will help me alot.
thanks in advance

There is already Distributed Model Created.
can u give me annother tcode so i can send Metarial data, by IDOC.
please help me.
Thanks

IDOC to IDCO scenario: Distribution of model view

Hi!
I try currently to configure a IDoc to IDoc scenario for SAP ECC 6.0 system with following business 2 systems:
ERP:100 (Sender)
ERP:200 (Receiver)
and PIB:100 (XI system)
I successfully created a message type u201CZCREMRu201D and generated the model view PIMODEL in tcode BD64.
Sender: ERP:100
Receiver: PIB:100
I assigned 3 partner profiles ERPCLNT100, ERPCLNT200, PIBCLNT100 and assigned a message type SYNCH with IDOC type SYNCHRON as outbound parameter.
Unfortunately when I try to distribute the model u201CZCREMRu201D and choose my XI system I get the following error:
Distribution of model view PIMODEL
Target system PIBCLNT100
Model view PIMODEL has not been updated
Reason: Distribution model is currently being processed
Question:
Do I miss some other inbound and outbound parameters?
IF yes, which and on which systems?
Thank you very much!
regards
Thom

Hi Rob
Y're right i made mistake when i was creating in SRM RFC destination puting host name of SRM system not ERP.
Thanx
Marcin

Distribution of Model View in ALE

Hi Experts,
I am setting up an ALE distribution of application data during which i am facing a problem durin ste step
of "Distribution of Model View" .
I am getting an error RFC destination does not exist , though i have created my RFC destinarion and i checked it using "Test Connection" & "Remote Logon".
Please Suggest me.
Regards.
Shrikant.

Hi,
Follow these below steps for ALE configuration
Step1: Creation of Logical system u2013 Transaction BD54
Step 2: Assigning client to Logical System u2013 Transaction SCC4
Step 3: Creation of RFC destination u2013 Transaction SM59
Two RFC destination needs to be created u2013 one at the sender with the destination as the receiver, and another at the receiver with the destination as the sender.
Step 4: Port generation u2013 Transaction WE21 - Port is required for the outbound message type and hence port generation is required only at the sender.
Step 5: Creation of partner profile u2013 Transaction WE20
Both outbound and inbound partner profiles need to be created.
Step 5.1: Creation of outbound partner profile.
Step 5.2: Creation of inbound partner profile.
Step 6: Creation of Distribution Model u2013 Transaction BD64 - This needs to be done at the sender
Regards,
Jyothi CH.

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

Error while distributing the ALE distribution model through BD64

Hi,
I am getting the error while distributing the distribution model through BD64. The error is as follows:
"Model view DVGDVH has not been updated
Reason: the following ALE connection already exists in model view TESTMOD".
What does this means?
Regards,
Soumya.

Dear Sapera,
I faced the same problem last night.
We just manually deleted the distribution model from receiving system.
Log on to receiving system => BD64 => change/dispay => edit => delete => Save.
Once deleted log in to sender system and then select model and distribute again.
by performing this we were able to resolve this issue.
Warm regards,

Distribution Model View - Error

Similar Messages

Maybe you are looking for