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

Similar Messages

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.

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.

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

Hi Experts,
   I need help from you all as i struck in idoc to idoc scenario.
i need to send the idoc from source system(R/3) to target system SAP(APO).
Please guide me what all the steps to be followed.
i need to send the same idoc to target.

hi,
[Re: IDOC to IDOC Scenario;
also a sample scenario wid steps as follows :
Description:
In this scenario we are sending an IDOC from an R/3 system to the IDOC in other R/3 system through XI.
XI Details:
Integration Builder: Design
Component Name : SAPNW of sapnw
Namespace             : urn: idoc2idoc
Integration Builder: Configuration
Scenario Name     :   IDoc2IDoc
Business System   : SAP01 (Cgnsap 01 System)
                                   SSI (Cgnsap 13 System)
Communication Channels:
1) No Sender Channel is required as we are using IDOC.
2) CC_OUT_IDOC_MATMAS05 [Send the data from Xi to CGNSAP01].
Transaction Codes Used:
SM59- To Create RFC Destinations
WE21- To Create IDoc Ports
SALE- To Create Logical System
WE20- To Create Partner Profiles
BD64- Display Distribution Model
WE19- To Trigger an IDoc
IDX1- Port Maintenance in IDoc Adapter
IDX2- Metadata Overview for IDoc Adapter
Processing Steps:
Source Side Configuration: CGNSAP13 (SAP R/3)
IDOC used: MATMAS.MATMAS05
Using Transaction Code WE19 we can see the structure of IDOC (MATMAS05), which we are using
Go to Transaction Code WE19 and enter the name of IDOC in Basic Type and execute
Click on the Segment data and then a screen will come in which the data of IDOC is entered
Creation of RFC Destination:
1. Create RFC Destination: To create a RFC destination use transaction SM59.
The RFC destination is created to provide IDOC a route from SAP system to XI server. Thus once the IDOC is initiated will reach to this destination for further transformations.
2. Create a RFC Destination XI_IDOC2IDOC with Target Host: Cgnsap 32(XI System) and select the connection type as 3(Connection to R/3 System).
The following screen will come once you will click on Create for new RFC destination.
Give a name to your RFC destination.
The Target Host field will be your XI server like cgnsap32.
All the other fields are dependent on the target host.
Save this and your RFC will be created.
Go to Logon/Security tab and fill the details for the Cgnsap32 system as shown below
Creation of IDOC PORT:
3. Create Port: To create a port uses the transaction WE21. We need a port to send the IDOC to the intended RFC destination.
Create a new Transactional RFC.
Give the port name.
Select the RFC destination for this port.
Save the data.
Creation of Logical System:
4.       Now Go to Transaction Code SALE and create Logical System.
Sending and Receiving Systems->Logical Systems->Define Logical System
Click on New Entries and fill the relevant details as show below
b) As we will save it a new window will pop up, in this click on Create and then it will ask you to create a New Request. Just give description of the request and save it, else everything is self-generated.
c) Hence the Logical System is created.
Create another RFC Destination with Target host as cgnsap13. Also create a port and logical system as above using the RFC Destination. This is used as a sender to trigger the IDOC from cgnsap13.
Creation of Partner Profile:
Partner Profiles: Now we will create Partner Profiles by using transaction WE20. These partner profiles are created to identify our logical system uniquely, as we know that there can be n number of logical system in a Business System.
In the Partner No field enter the name of the logical system created.
Enter the Partner Type as LS (logical system).
The type and Lang field will be same.
In the Agent field select the business system from which you are sending the IDOC.
In the Message Type Field include the IDOC.
Save all the data.
Creation of Distribution Model:
Go to Transaction Code BD64 and create Distribution Model.
Click on create model view, window will popup as shown below.
Enter the short text and the technical name as required.
Once the model view is created, click on Add message type. A window pops up as shown below. Enter the details of the model view, sender logical system name (for cgnsap13 in this case) and the receiver logical system name. (Logical system created in cgnsap13 for sending to XI server)
XI SIDE CONFIGURATION: CGNSAP32 (XI SYSTEM)
Creation of RFC Destination:
1. Go to Transaction Code SM59 and select R/3 Connections and click on CREATE.
2. Create a RFC Destination RFC_IODCTOIODC with Target Host: Cgnsap 01(R/3 System) and select the connection type as 3(Connection to R/3 System).
Creation of IDOC PORT:
3. Go to Transaction Code IDX1 and create an IDoc Port PORT_01 (Transactional RFC) and map it with the RFC destination (RFC_IDOCTOIDOC).
4. Go to Transaction Code IDX2, Click on Create and enter the details of IDoc Type and Source Port.
Target Side Configuration: CGNSAP01 (SAP R/3)
Creation of Logical System:
4.       Now Go to Transaction Code SALE and create Logical System.
Sending and Receiving Systems->Logical Systems->Define Logical System.
Click on New Entries and fill the relevant details as show below
b) As we will save it a new window will pop up, in this click on Create and then it will ask you to create a New Request. Just give description of the request and save it , else everything is self generated.
c) Hence the Logical System is created.
Creation of Partner Profile:
Partner Profiles: Now we will create Partner Profiles by using transaction WE20. These partner profiles are created to identify our logical system uniquely, as we know that there can be n number of logical system in a Business System.
In the Partner No field enter the name of the logical system created.
Enter the Partner Type as LS (logical system).
The type and Lang field will be same.
Now add Inbound parameters.
In this screen, enter the Message type and the Process Code for u2018MATMASu2019 and save it.
Now go to   XI (http://cgnsap32:50000/rep), click on Integration Repository for Design.
Go to SLD by clicking on the u2018System Landscape Directoryu2019 in the above screen
Click on Business Landscape and check for the Business Systems, which have the required Technical systems (cgnsap01, cgnsap13 in this case) and the required clients (800 of cgnsap01 and 800 of cgnsap13).
We create a business system if the required business systems do not exist
Creation of Business System:
Click on New Business System and the following screen will appear.
Enter the name of the Business System and click next.
Select the type of the business system in this case its Web AS ABAP.
Select the Technical System for the Business System.
Select the required client.
Select the Business system role and related integration server and click Finish to complete the creation of the business system.
Design: Integration Repository
1. Create a Namespace under component SATYAM_SAPXI_IDOC.
2. Import the IDOC by using Import Wizard in the Imported Object in the Design time.
3. Create a Message Mapping and drag IDOC Structure into Source Message and Target Message panes. Map the mandatory fields of the input and output IDoc structure. Save and activate the message mapping.
4. Create an Interface Mapping for the IDoc.
CONFIGURATION TIME:
SCENARIO: Create a scenario in which all the objects will be created.
Scenario Name: SAP_XI_IDOCTOIDOC
Business System Name: SAP01 (for cgnsap01), SSI (for cgnsap13)
As we are going to send IDOC from the system so no Sender Channel is required.
SENDER AGREEMENT: No Sender Agreement is required.
Communication Channel:
Select IDOC Adapter and provide the details as shown below.
RECEIVER DETERMINATION: In receiver determination, we have to specify the Service and Receiver details.
INTERFACE DETERMINATION: Specify the service, interface and Inbound and outbound interfaces.
RECEIVER AGREEMENT:
Provide the sender service, receiver service and Receiver Communication Channel here.
In the Header Mapping, select the Sender Service as the receiving R/3 Business system
       (SAP 01 in this case).
Testing :
To test all the configuration of IDOC which you have done follow this test procedure:
Use transaction we19 for IDOC Processing.
Give your IDOC and execute it.
c)       Then enter values in IDOC and save it.
d)       Check the values in the XI System using SXMB_MONI Transaction Code.
Regards.
Siddhesh
Edited by: Siddhesh Naik on Nov 3, 2008 10:06 AM

Related to distribution the model view

hi
When we try to distribute the model view, we get an error 'Model View has not been updated. 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?

Are you created distribution model for the correct Logical systems. Check it once.

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.

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

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

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

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

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.

Model view distribution

Hi ,
I have to synchronise SAP system A and SAP System B through ALE .If any change in the material in System A has be reflected in system B and vice versa.in this case do I need to create two model views. can I create one model view and distribute it.If i distribute will the partner profiles will be created automatically .why we distubute model view.Please reply.
Thanks,
Ravi

Hi,
You have to create only one model view..
create it,then goto environment menu in SALE and create partner profile
port is created by itseld.
then distribute it to you other system.
we distribute model view to transfer the information to ither system that which is the sending system receiving system and what data you are sending.
Regards,
pankaj singh
reward points if helpful.

IDOC to IDCO scenario: Distribution of model view

Similar Messages

Maybe you are looking for