IDOC Model View Generation Issue

Hi all,
I am working on IDOCS and I am facing the follwing error when I try to distribute the Model View in IDOC--
"the following ALE connection already exists in model view HR_TO_PI"
I had deleted the above "HR_TO_PI" model view and I created a new one with new name.
But I still get the same message.
I don't think this is an issue with configuration.
I am assuming it's an issue with table entries. Does this-"HR_TO_PI" value get stored in any table in the back end ?
Kindly help. I had a look at SDN and other places but they all ask to check for partner profiles and logical systems which I believe I have configured right.
Warm regards,
Hari Kiran
Edited by: HARI KIRAN REDDY on Feb 23, 2012 11:24 AM

Hi Sravan,
I had a look at TBD00. It shows all my current distribution models but not the one mentioned in the error.
I had a look at some other tables in the TBD series but of no help.
I don't know in which table that entry has ended up.
It's frustrating.
Thanks for the input once again.
Warmr egards,
Hari Kiran

Similar Messages

IDoc to IDoc scenario: distribute the 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 XIB:100 (XI system)
I successfuly created a message type and generated the model view in tcode BD64.
Question:
When I try to distribute the model view which system should I choose?
a) XI System or
b) Receiver system ERP:200
When I choose the receiver system ERP:200 and get the following error
Target system: ERP:200
Model view ECCCLNT100 has not been updated
Reason: Distribution model is currently being processed
When I try to choose my XI system I get the following error:
Target system: XIB:100
RFC destination for synchronous communication (message type SYNCH)
Partner profile LS PIBCLNT100 SYNCH does not exist
Generate partner profile
or specify outbound partner profiles for message type SYNCH
Is that an error? If yes, how can I fix them?
Thank you very much
Thom

Hi
Look my reply on this thread regarding SYNC Message Type.
Re: problem while distribute model view
When I try to distribute the model view which system should I choose?
a) XI System or
b) Receiver system ERP:200
You are sending IDoc to XI then R/3 so select XI system. because receiver of IDoc is XI then IDoc would be send from XI.

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

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.

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

Help: one request using ALE&IDOC to Posting Goods Issue about MaterialScrap

Hi Exports,
i got a situation. My client is using ALE&IDOC to deal with the Material Scrapping. The business scenario is:
1. One third system (Non-SAP) Send IDOC to SAP Production Server through the Intermedia SEEBEYOND.
    Message Type: MBGMCR
    IDOC Type: MBGMCR02
    BUSINESS OBJECT: BUS2017
2. SAP Production Server use "Message Type: MBGMCR" to find out the BAPI in Distribution Model and trigger the BAPI.
the Distribution Model:
Model View
SEEBEYONG
PRODUCTION
GoodsMovement.CreateFromData
Reciever determination: no filter
Now my client's request is:
When the Movement Type is 551 in the IDOC Segment "E1BP2017_GM_ITEM_CREATE", This IDOC will be ignore and not trigger the BAPI to post goods issue.
i try to add the destination filter in the Distribution Model. but when i add the filter group, there are only two filter parameter ("Plant" and "Storage Location") and don't allow to add others.
i have no idea now. can anyone give me a favor. thank you very much in advance.
Edited by: Dave Wang on Feb 29, 2008 7:09 AM

We got hold of the Idoc type 'DELVRY03 PGI SHPCON' we are able to post the Idoc but we are able to do the packing only or we are able to change the deliveries but the PGI is not happening..
please help us on this.. is there some condig that updates the delivery with the PGi or is there something else do be done in the Idoc....
will provide additional details if required.
Thanks
Arun

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.

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

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

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

Oracle 11g R2 Model view DML formulae/programs

Hi All,
We are in the process of migrating our cubes from 10.2 to 11.2. We have lot of DML formulae and programs in object view in our current environment(10g). As 11g R2 does not support Object view we are trying to move all our formuale and programs to model view. We are looking for some guidance/suggestions on this topic.
Our current problems are we have lot of formulae of different dimensionality in our object view for ex if we have 6 dim then we have DML formulae from different combinations of these 6 dimensions which is forcing us to create cubes(logical) of all these different dimension combinations.
I saw somewhere online I can edit awm.properties file and still can use Object view in 11g also. I am not sure that is a best practice. Eventually object view completely gets locked from users in next releases?

The object view is not supported in 11g. While it is true that you can enable it as Brijesh describes, it will not display 11g generated objects correctly. One technical issue is that the java code in the object view attempts to parse the object definition in the client. (e.g. DEFINE xyz VARIABLE INTEGER). It has not been updated with new 11g keywords (such as LOCKDFN), and frequently produces errors or (which is worse) misleading information. You could try OX if you can track down a copy.

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.

Generate DELVRY Idoc when Post goods issue is done in SAP

I need to generate an Idoc when post goods issue is done in SAP (outbound to SAP) .I understood that I can do this using the message control .The message type DESADV with the process code DELV will support this.
But I didnt understand how to trigger the Idoc.In the current scenario our Company is doing the post goods issue in SAP for the in three different ways.
1.Manually doing the post goods issue through the transaction VL02N
2. an Inbound Interface (using Idoc) which will do Post goods Issue in SAP
3.Another Interface using BAPI, which will, do post goods issue in SAP
I have to run my outbound interface when the post goods issue is done by all the above three ways. Can any one help me out in this?

You have to configure the output first .
You can use output type LAVA ( avaialble in Std SAP ) .
( Tcode is NACE , Select Application V2 -> Outputtypes ).
( Create condition records suitable to generate an output)
Next is ALE.
Setup a distribution Model ( for DESADV ) and all other setup for ALE i.e. Distribute Dist. Model / Generate Partner Profile .
In the Partner profile in WE20 select your partner system. Double CLick on Outbound Message DESADV ( this wd be there after you generate partner profile , if not add it here in outbound ) . On this screen goto tab MESSAGE CONTROL .
Application - V2
Message Type - LAVA
Process Code - DELV.
Now you are ready to go. The moment a PGI is done in any form an output LAVA would be proposed and processed using process code DELV.
Cheers.

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

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

IDOC Model View Generation Issue

Similar Messages

Maybe you are looking for