BD64 Model View - Wrong Maintenance System

Hello.
We refreshed our QA system from Production. Production is in a different CUA than our test systems. The QA system still thinks that it is in the production model view n BD64 and I cannot get it to accept the new distribution model from the CUA for our test systems. Furthermore, the entries in BD64 in the QA system are grayed out and cannot be deleted locally. The production CUA doesn't recognize the new system at all either.
How can I get the QA system to point to the right maintenance system in BD64?
Thank you.

Nevermind. I deleted the DM and redistributed.

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

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.

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 Model (ALE) - Message type has to be deleted from model view

Hello,
I want to delete a message type from an existing model view in the distribution model (of the maintenance system).
But when I mark the concerning message type and press Edit->Delete the message 'Action cannot be carried out on the nodes selected' occures. Deleting the complete model view would work...
Does anyone know how I can get this without setting up a new model view?
Many thanks in advance,
Juergen

hi,
>>'Action cannot be carried out on the nodes selected'
you get this message if you try to delete a message type
from a model view that was not created on your system
(it has been replicated and it's maintained on another system)
so you can only delete this message type on the system that has
"master" distribution model
if it's not master then it's usually grey and you can only delete if it's black in change mode
>Deleting the complete model view would work...
if you try that you will see info that it's not the "master" system for this model
check it and let me know
Regards,
Michal Krawczyk

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

CUA: Model view not created automatically in Child System

Hi, I try to create a CUA with just a child system thru txn SCUA. The result of generation is good and all green. The part that is not right is I do not see the model view created in txn BD64 of child system, I can see it created in master system. Both RFC of master and child system are working fine. I do not see errors at WE20 & WE21 as well. Under this situation, I can see CUA active in master system but not child system. Hence, CUA is not working as it says in master system.
I have setup CUA couple of times before but this is the first time that I encounter such a weird situation. Does anyone has any clue where could have gone wrong?
Edited by: Annie Chan on Jul 25, 2008 5:23 PM

Hi Everyone,
It is indeed a RFC issue but it was a silly mistake with the incorrect hostname that I am suppose to connect to. Hence, the Distribution Model doesn't exist in the child system. Nervertheless, your advise does point to the right direction.
Thanks so much for your input. Points are granted as accordingly.
Regards,
Annie

Unable to Distribute Model View in BD64

Hi Gurus,
Model View - SR2CLNT251
Receiver of Model View - EA1CLNT251
i went to txcode bd64 > i clicked on model view SR2CLNT251 then went to edit > model view > distribute and clicking the logical system of EA1CLNT251. then error will be encountered.
Model view SR2CLNT251 has not been updated
Reason: No authorization to change model view SR2CLNT251
.....authorization object B_ALE_MODL
.....Parameter: activity 02, model view SR2CLNT251
i already given correct authorization to my ID, but still the error persists.
Please help. Thanks!
Regards,
Tony

Hi Tony,
You need authorization for authorization object 'B_ALE_MODL' in system I guess either in system SR2CLNT251 or in EA1CLNT251.
Best Regards,
Tushar

Is model view(BD64) necessary for EDI

is model view created using BD64 necessary for a EDI transactions? I have created a logical system, a RFC destination and a EDI File Port.
After all this i am trying to push a material master data using BD10 to the file port. When i do that the system gives me a message saying that master idoc created but it does not create a communication idoc. Only if i have a Model view set up in BD64 it creates a communication idoc. So my question is do we need a model view for EDI configuration?
~Suresh

Hi,
BD64 is required for master data distribution..
If you are having a interface that sends IDOCs to the customer or receive IDOCs from the vendor..You don't require BD64 setup..
Thanks,
Naren

Reg. Model View BD64

Hi,
I have created a model view and generated the partner profiles. when i am distibuting the model view, I am getting an error " Model View XXXX has not been updated" "Reason: Maintenance systems for model view XXXX are not identical".
could anybody tell me , how to resolve this issue.
Thanks & Regards,

Any luck with the resolution to this error?
Thanks,
John

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^

Distribution Model - Change Maintenance System

I need to change the maintenance system for a distribution model - anyone know where to do this?
<b>History</b>
We have a sandbox( HRX ) that is a copy of an older production system. We have since upgrade to ECC6.0 and changed the names of our development servers from HRD to HUD.
When I modify the distribution model in HUD and transport to HRX, HRX still thinks HRD is the maintenance system, not the new ECC 6.0 server.
Where can the maintenance system be changed?
points for answers.
thanks,
rp

Hi,
You may want to define the logical system and assign client to logical system (transaction SALE) for HUD. Then you need to delete the old distribution model of HRD and create new one for HUD (transaction BD64) and generate the partner profile (WE20).
Also ensure the RFC connection was setup properly.
Regards,
Ferry Lianto

Error in distributing the Model View in BD64

Hi Experts,
I have some problem in distributing model view in BD64. please see here the error details:
Model view <logical client> has not been updated
Reason: No authorization to create model view <logical client>
.....authorization object B_ALE_MODL
.....Parameter: activity 01, model view <logical client>
i have created full auth and B_ALE_MODL role for the specific account but still i cant proceed.
Please help.
Thank you,
Tony

Hi Experts,
In addition, this is in line with our integration between SRM 7.0 EHp1 SPS05 and ECC 6.0 EhP4 SPS03. both systems are running in windows 2003 64bit.
Edited by: Tony on Aug 3, 2011 4:30 AM

Model view (t-code- bd64) configuration issue

1) Is it possible with out distributing customer distribution model in outbound side ,can we receive idoc data in inbound side?
2) after distribution of model view in outbound side is it possibel to create filter techniqe in inbound side?
Thanks
Bhaskar Reddy

Hi,
1) Is it possible with out distributing customer distribution model in outbound side ,can we receive idoc data in inbound side?
- Yes, if is not MASTER data, probably you do not need to configure BD64 for outbound IDoc.
2) after distribution of model view in outbound side is it possibel to create filter techniqe in inbound side?
- You can filter in the Distribution Model easily. So you should use it for filtering data. Otherwise you need to filter it programmatically in some customer-exit.

BD64 Model View - Wrong Maintenance System

Similar Messages

Maybe you are looking for