Issue in distribution model

Dear PI experts,
I am currently facing and issue with sending an IDOC to the SAP PI. I receive two messages one is for master IDOC which is successfully processed and the other is for communication IDOC which is showing 0 Idocs processed. I believe this is an issue with the distribution model, where also I have performed the necessary settings and stil I am unable to identify where the issue is.
But I also believe it is in the distribution model and dont know how to fix it there.
Thanks for your help.
Andy

Dear Andy,
As Bhavesh suggested please look in to SM58 Tcode in R/3 for TRFC errors and please look in to
following SAP note to rectify the errors occur in SM58 related to IDoc:
SAP Note 940313 - IDoc adapter: Error messages in SM58
This note better explains about configuration issues related to IDoc.
Best Regrads
Praveen

Similar Messages

Issue with distribution model

Hi
We are trying to set up payroll posting document via ALE interface. We have done the following settings
1. Distribution model setup with filters on for standard bapi's
2. Partner profile setup
3. RFC destination setup
When we try to post payroll data,it was returned with the following errors
       RFC destination is not maintained for object BUS6001 and method PRECHECKPAYROLLACCOUNTASSIGN
       RFC destination is not maintained for object BUS6001 and method PRECHECKPAYROLLACCOUNTASSIGN
       The account assignment objects could not be checked
       The account assignment objects could not be checked
       RFC destination is not maintained for object BUS6004 and method CHECK
       The G/L account could not be checked
We verified RFC destination and it was working fine. Type of user used in RFC dest is Communciation. Hope this is not a issue.
Although above issues are very general, couldn't find relevant solution for this.
Please, can some one help me how to fix them.
Thanks

Hi Chinna,
Have u checked whether the distribution model is properly received in the target system ?
Thanks

Issue with HR Distribution Model from ECC to CRM

Hello Gurus,
I am replicating employees from the ECC to CRM. I followed the C05 u201CCRM Organizational Model with ERP HR Integrationu201D Best Practice. Initially employees replicated without any trouble from ECC QAS to CRM DEV. The issue came since we also created a replication model from ECC QAS to CRM QAS.
Even dough each replication model has defined each corresponding receiver system (CRD and CRQ), since we created the new distribution model, employees are now only replicating to CRM QAS which was the last created distribution model.
Since we only have data en ECC QAS we have use this same system for the CRD and CRQ. The question here is: Can we only have one distribution model? Is there any way to achieve employee replication also to CRD?
Extra Information: When using PFAL for replicating, I´m using object P and after executing the systems confirms in green the replication for both systems. But when I a search the HRXX in CRD I didn`t find it I just found it in CRQ.
Thanks for your comments on this.
Points will be reawarded

Dear Kumar,
you should not schedule RBDMIDOC before you have done the initial distribution because the most of the idocs will run into error (if new objects are created in ECC the distribution will create correct data in CRM; changes on existing objects will run into error because the object has not been created by distribution of essential data).
Before scheduling the idoc creation from change pointers you should have done the intitial distribution of organizational data and employees using the procedure described in note 363187.
Regards,
Michael

Material Master Change Pointers/Distribution Model - any suggestions?

Dear All,
Hope everyone is doing good.. I have been trying to come up with a solution for the below issue, but didn't get any further. Your help is highly appreciated.
Initial Design:
Couple of years before we had a plant 123 and plant 456 where we need to send the materials. So we had specified these plants in Distribution Model and things worked fine.
First Problem
During testing what we have found out was, if some one changes MARA level, IDOC is being created but it's not being sent out of SAP system because the IDOC doesn't have 123 and 456 plants which the distribution model filtered it out and no data got sent to SAP PI.
Solution implemented:
After doing lot of analysis and research we have implemented solution as per the blog The specified item was not found.
Today's problem
There are couple of more plants we were supposed to send the data 789 and 678. The problem is if some one did a mass change on plant 456, the above solution implemented takes all the data(not the deltas) and pushing it out. Even though the change is only on 456 plant, we were unnecessarily sending the data to 789, 678 which is causing lot of problems.
Now we realize we shouldn't have gone with the solution mentioned above, because it's not applicable in my scenario.
Does anyone handled this kind of scenarios in the past, if so can you please shed some lights?
Thanks,
Raj

Hi Raj,
As per my experience what you had already implemented, that is absolutely correct. I don't think there is any alternative to send the data as a whole (I understood if you are not sending the Plant data, how the middle ware filter them).
Now your requirement is if you make some mass changes in the materials which are extended different plants other than 456 plant, we have to restrict them. To restrict the outbound Idocs for MATMAS. you can use the Filter option in BD64 (Distribution Model). Here after creating the Filter Group, you can edit LOV for Plants.
Once your mass changes transmission is over, you can remove this.
Hope this will work, at least you can give a try...............

Problem with distribution model receiver ports

Hi,
I am facing a problem with distribution model.
I am using Distribution model for material classification data. I am sending my classification data using CLFMAS message type to one of the receiver. Again another person also sending classification data to another receiver.
But both objects will run at different times.
Problem is for every run and every change it is creating 2 idocs instead of 1 idoc.
I am able to create an IDOC with my changes for classifications. But it is creating 2 idocu2019s instead of creating 1 idoc. Because of there is another distribution model with same message type with different receiver port has been configured. I.e. reason it is creating 2 idocu2019s and sending to both the revivers.
When I run my changes It needs to create 1 idoc and send to my receiver port. If another person run his job it needs to create another idoc.
So how will I filter distribution model based on receiver port? it needs to create only 1 IDOC ..

Hi kotesh,
A similar issue.
check if this will help.
Do the following:
Go to TOOLS>ALE Development>IDoc Type Development> WE81 and create a new message type and give it a different name - say ORDERS2. Use WE82 to link it to an IDoc Type - say ORDERS05. So now you will have two message types linked to the same IDoc type. Each message type can now be referred in different logical systems without any clashes.
Now you can use BD64 to build your model using message types ORDERS and ORDERS2 without getting the multiple recepient error message.
Then use WE20 to set up each partner profile using your defined output conditions in message control to trigger the creation of the IDoc. Now you will beable to send the same Idoc type to different recepients.
source:http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/sap-distribution-model-3008763
Regards,
SuryaD.

Trying to understand Distribution Model

When I view the metadata of a Distribution Model, I see DM overview which contains 2 tabs. One for Data Objects and Second for Rules. I am trying to understand the tables in each of these tabs.
Association Table - RR00200100G_AT
DRDS Table - DM00200100G1
DR Table (Runtime) - RR00200100G1
What are they used for and when to the entries get updated?
Thanks
JB

Thanks for the quick reply Siva....
I am trying to investigate a behaviour where we have a normal rule based on a Date Pattern. The business requirement is to distribute only today's data back to the user's device. The issue we are seeing is that there are data in the device that were created in the past.
The rule's criteria is based on CREATED_BY(UserID) and CREATED_ON(date) node attribute from the data object.
In the rule, the CREATED_BY is mapped to the USER device attribute and the CREATED_ON is a date pattern, where the Operator is 'EQ', Custom Type is 'C' - Constant Offset, and Date Pattern is 'Current Date'.
With this set-up, there are four events that were created in the Execution Plan - Device Addition, Device Modification, Device Removal and Sliding Window-Date. There's also a job, Sliding Window-Date,
that is scheduled to run once a day at midnight.
My observation is that every day, after the Sliding Window-Date runs. The DRDS & DR tables, in the second are updated. But the entries in the Association table, from the first tab, are not updated.
I am expecting that the Status Flag, in the Association table, of all records that are not relevant for that date, get's updated to 'D' so that when the user syncrhronize they will get deleted from the device.
What am I missing? What triggers the update to the Association table?

How to add BAPI in ALE-distribution model?

HI all,
I have to send The post goods issue through ALE-IDOC, this have to create the Goods Receipt in the receiving side.
I came to know that the message type for this is MBGMCR , when i am trying to add this in the distribution model , it is prompting an error message that this message type belongs to BAPI.
So , to send the required data , i have to add the BAPI.
Please help me clearly on how to add this and what are the steps involved in distributing data through BAPI ?
Thanks,
Vamshi

In we20
process code will be BAPI and setting will be same as in other process codes
in bd64 i have example..
TCode BD64
Add ADRMAS in Distribution Model u2018TestERDToEXDu2019 as follow:
Click on u2018Add BAPIu2019 Buton.
Give Object Name as AddressOrg
Give Method Name as SaveReplica
You will get a entry as follows
Edited by: Madan Gopal Sharma on Jul 1, 2008 9:02 AM
Edited by: Madan Gopal Sharma on Jul 1, 2008 9:04 AM

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,

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.

How to transport distribution model

hi i am having doubt in distributing model.
is it possible to transport distribution model?
if yes.
1. in real time where distribution model is created i.e in production or development system.
2. is it correct way to create distribution model directly in production system.
3.if it created in development system how to transport it.

Hi,
You never transport the distribution model.
Usually it is done by distributing the model (BD64) through RFC connection (let's say from DEV -> QA). It depends on your company procedures. Some company maintains in each client (DEV, SANDBOX, QA, PROD).
For PROD distribution model, I would recommend to setup manually instead of distibuting from DEV for security of data integration and interface purposes. If you allow to distribute from DEV to PROD, you could easily make a mistake either over write/change the existing production model interface and can caue production error/issue.
Hope this will help.
Regards,
Ferry Lianto

Distribution of Distribution modell error

Hello,
I've created my distribution model in a 4.6C system but everytime I try to distribute the modell I get an error saying:
Kommunikationsfehler ist aufgetreten
Server repository could not create function template for 'MODEL_VIEW_REPLICATE'
Any ideas?
Kind Regards,
Christoph Mertins

Hello Christoph,
During the ALE Model Distribuion, the Function Module MODEL_DISTRIBUTE is called and from within this FM a
Remote Call is made in the RFC Destination (Target System) for the Function MODEL_VIEW_REPLICATE.
It seems you are getting the below stated issue during the Remote Call.
The possible reasons for this are
a) Model View name is not specified
b) No Authorization to Create or Change the Model View in target system for the user id mentioned in SM59
c) The BAPI or Message Type involved in the Distribution Model already exists in another Distribution Model in Target system
d) Model is being edited by another user in the target system
Based on these reasons, you can trouble-shoot the problem.
Hope this resolves your problem. Pls reward.
With Regards
Vijay Gajavalli

Cannot find the Recv Logical system in Distribution Model

HI experts,
Im triying a Idoc to file scenario, the logical system for PI and R3 has been already created and assinged for the appropriate clients.
and i ve created the port from r3 using tcode we21 and in PI using idx1 and Idx2. The RFC destination also created for PI and R3 system.. when i created the distribution model using BD64 in R2. when i assigning message type i can give the source logical system and i cant find the Receiver logical system... Also in WE19 i cant find the receiver port (which i created in IDX1 and IDX2)..
Could u tell me how to solve this prob???
Regards
Balaji

Hii Ravi,
Thanks for your reply,
Yes i have created the port (RFC800) idx1 and give RFC destination which points the R3 system.
I have assigned the meta data to that port using tcode idx2.
And I have created port with port name "PORT800" in R3 using we21 and give the RFC destination which points the PI system
when im using the WE19... i gave source logical system as R3 Logical system and receiver logical system as PI Logical system.
now im getting error like "PORT RFC800 DOESNT EXIT IN THE THE TABLE OF PORT DISCRIPTIONS".
Regards,
Balaji
Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM
Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM

Hiding fields of a table in distribution model

Hello Folks,
I have a standard table with the append structure included with two fields.
I have created two distributed systems to two different servers- but want to transfer standard table data without custom fields data to one system, where as standard + custom fields structure to other system.
Could some help me out in fixing this.

Hi,
Go for field level filtering in Distribution model.
Thanks,
Asit Purbey

Not able to create Distribution Model nor Import using IDX2

Hello,
I have created an RFC destination, and i'm able to connect successfully also remote logon is working with error, i have also created Port associated in RFC destination.
But when i try to added a message type in distribution model, i get an error rfc destination not maintained.
Same goes with Import of metadata, i not able to maintain an Port in IDX1, hence not able to import metadata.
If i import an Idoc or create an external defination will it help.
any help would be appreciated.
Regards,
Abhishek

>>i not able to maintain an Port in IDX1
I hope you have created RFC destination in PI system. What error do you see when you try to maintain port?
Regards,
Prateek Raj Srivastava

How to create a data filter for BAPI used in a Distribution Model ?

I am trying to create IDOC's for a QM inspection plan via message type QPMK in ECC 6.0. When creating the new message type in the Distribution Model, it forced me to use a BAPI (MasterInspectionChar) rather that just the message as I have done in the past. In order to ensure that only IDOC's related to a specific plant and material type get sent out, I was trying to create a filter.
I am able to get into a 'Change Filter' dialog by double clicking 'No data filter set' under the node 'MasterInspectionChar.SaveReplica'. However, an attempt to highlight anything on this dialog and clicking button 'Create filter group' results in msg. 'Select node: Content-dependent parameter filtering'.
Online help led me in a different direction, one thread led me to believe I needed to create a table entry for the filter in table TBD16 via BD81 for later attachment to the BAPI in the Distribution Model. Before this, I created two Z* ALE Object Type records for plant and material type in table TBD11 via BD95 for what I thought would provide a lookup back in BD81 for creation of a new filter record, but these objects are not found. Per the help, I am also unclear as to whether I would need to set up Receiver determination or Parameter filtering, nor where to make this step in the configuration happen?
Can anyone point me back in the correct direction to get a data filter set up for this BAPI within the Distribution Model ?
Thanks - Mike

Just to clarify, what I am having trouble with is finding where exactly to plug in the name of the plant to be filtered? If using a message type such as MATMAS in a distribution model, it is very straight forward to navigate down from the 'Data filter active', and assign a value to whatever field you wish to filter via the 'List of Values'. But in this example, message type QPMK required use of the BAPI MasterInspectionChar, and therefore the different method in creating the filter.
I cannot find similar functionality when navigating the BAPI related row, for MasterInspectionChar. The 'Change Filter' dialog popup displays a row for 'Container' and then 3 more rows containing 'BAPI structure...'. Clicking the 'Attribute' checkbox on any of these rows sets 'Data filter active' as a node under the BAPI. Double clicking the 'Data filter active' brings me back into the same dialog, and selecting any row with an attempt at this point to create a filter results in the 'Select node: content-dependent parameter filtering' warning. Is this warning occuring because of missing configuration?
Thanks - Mike

Issue in distribution model

Similar Messages

Maybe you are looking for