Distribution Model BD64

Hi all,
I am new to Idoc and all other related stuff. I have a small doubt. Af far as I know, to send Idoc's from sending system to recieving system we need to configure ports(WE21) and partner profiles(WE20) on both sides. But my team lead says it's fine even if we create on one side and include SYNCH in the partner profiles and distribute the model view which seems wierd to me. The basic type for this is SYNCHRON. Can anyone explain me what is right as per SAP standards. Is synch an SAP supplied one or user defined ?
Thanks and Regards,
Ben.
Message was edited by: Daniel Ben

Hi Daniel,
Go through the following links below :
<a href="http://www.sapgenie.com/ale/configuration.htm">http://www.sapgenie.com/ale/configuration.htm</a>
<a href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc">http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc</a>
Please reward points if it helps.
Regards,
Amit Mishra
Message was edited by: Amit Mishra

Similar Messages

Tables with distribution model(BD64)

Hello
I want to transport RFC(sm59), partner profiles(we20), ports(we21), distribution model from one system to another(it is the same system but after PRD->QAS copy).
I found following tables containing relevant data:
EDIPO
EDIPOA
EDIPOD
EDIPORT
EDP12
EDP13
EDP21
EDPAR
EDPI1
EDPO1
EDPO3
EDPP1
RFCATTRIB
RFCCHECK
RFCDES
RFCDOC
RFCSYSACL
RFCTRUST
TBDLS
TBDLST
I miss only passswords for RFC's and (especially) distribution model(BD64). Does anyone knows in which tables they reside?

Hello Jan,
From NW 7.0 onwards, the paswords were encrypted based and will create a secure storage key which is based on the SId and installation number.When ever if you are copying these tables where the functional entires that requires passwods,which will be invalidated after copying.For this you need to migragte the secure store entires after copying.More over every time when these secure store entires got invalidated,will have a communication to SMP for the creation of Migration key.You need to look further to install migration key for this problem.
1. Check which are the entries are invalidated after copying, Goto SECSTORE transaction ,select "all applications " option and execute,
2. Get the migration key from http://service.sap.com/migrationkeys
3.Install the migration key in SECSTORE transaciton by giving inputs like old SID,new SId,old installation number and New installation number.
see details from this note:816861
Hope you can solve your problem.
Best Regards,
Shyam Dontamsetty

Need to rename the Distrinution model ( BD64)

Hello,
Please tell us how to rename the Distribution Model (BD64) along with the technical name.
This we need to perform as post-refresh activity.
Thanks
Hari

Hi Hari,
To rename Distribution Model View: Select the model view and press function key 'F2'. Enter a new name in 'Short text'.
To rename Description/Technical Name: Select the model and click on 'Add Message Type'. Enter a new name in Model view.

Activate my distribution model

Hi,
When I tried to activate my distribution model (BD64) thro edit>model->distribute, It says Model view has not been updated, Distribution model is currently being processed.
I tried many times, but every time I am getting the same message.
How to solve this ?
Thanks,
Ram

Hi,
why do you want to distrubite your model ?
(do you need to distribute it to another R3 right?)
if not than you don't need to do it
just save the model and you can use it
if you have to distribute try checking
who else is in edit mode
if this is try logging againg to r3 and delete
your previous sessions
Regards,
michal

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,

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

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

R/3 to XI (Idoc to File): Do we need to maintain distribution model in R/3?

Hi All,
I have a very basic question regarding Distribution model.
My scenario is IDOC-->File ( SAP R/3 --> XI). So all I am trying to do is send the IDOC frrom R/3 to XI. ( Within XI I am going to do an FTP to the 3rd party file server)
I have created a distribution model, but was wondering if I really need to create one as message is going from R/3 to XI and not from R/3 to another R/3.
Please help let me know If I need to distribute this model to XI or to SAP production sytem or I do not need to duistribute at all for this scenario.
Thanks
Shirin

Hi,
if you create partner profiles and port via t.code.
i hope, it's not required to maintain Distribution model.
please check the below points.
Configuration Steps for Idoc to File Scenario.
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
To Configure the IDOC TO FILE SCENARIO, SETTINGS IN SAP-XI
STEP 1:ALE SETTINGS IN SAP-XI
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code 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 Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) ALE SETTINGS TO POST IDOC OUT OF SAP-R/3 ***********************************************************************
a) Create RFC Destination using T.code in SM59.
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.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(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)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (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
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item u2018Generate Partner Profilesu2019
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> u2018Distributeu2019 to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
warm regards
mahesh.

"Customer" BAPI in Distribution Model for Training and Events

We have an HR box with Training and Events - When booking an attendee on a course, you can select the "contact person" tab. Our SD box is separate from HR, so all the contact persons are maintained there. Is it possible to use the "Customer" BAPI in a distribution model so that when we search in the HR box for a contact person, it actually fetches the data from the SD box?
I remember reading up on this a while back but I can't find the documentation I had back then...
I know that in BD64 I can create a distribution model, and if I remember correctly, i should be able to "Add BAPI" and use object type "Customer" - Then add all the methods that I need... (like Find, List, Search etc) In essence, once this model has been distributed to the other system, if I go to transaction XD03 in the HR box, I should be able to display customer master details that only exist on the SD box - Is that correct?
Please help as I am not able to get this to work...

Ok I figured it out...
I have created a distribution model with the HR system as the source, and the SD system as the target.
In change mode, click the "Add BAPI" button and choose object BusPartnerEmployee, method CheckExistence
Do the same for the following:
BusPartnerEmployee.Display
BusPartnerEmployee.GetList
Customer.CheckExistence
Customer.Display
Customer.ExistenceCheck
Customer.Find
Customer.GetContactList
Customer.GetDetail2
Customer.GetInternalNumber
Customer.GetList
Customer.GetSalesAreas
Customer.Search1
Ok so I know that this might be a little over-kill, especially all the Customer methods that I added, but it works

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.

Specific IDoc + Distribution Model = pb of filter

Hi,
I created a Message Type "ZHRMD_A" and an extension "ZEXT", and I use the standard IDoc type HRMD_A06. Thus my Idoc is: ZRMD_A.HRMD_A06.ZEXT
All work fine: my ECC send correctly this idoc with the good values...
But my problem is inside the Distribution Model (BD64): I haven't the line "Data filter active" under my Message Type ZHRMD_A, so I cannot add filter !
Can I add filter on a specific Message Type?
if yes, how?
any idea is welcome.
Regards
Mickael

Hi,
u can use the tcode- BD56 for segment filtering.Also check for BD95.
Regards,
Nagaraj
Message was edited by:
nagaraj kumar nishtala

ADD BAPI in distribution model

Hello everybody,
Can you please expalin use of ADD BAPI button given in BD64/distribution model.
Please explain with an example.
I tried to to serach on inetrnet about ADD BUTTON.But not much information available niether ADD BAPI was explained in me training.
Thanks.

Hi Jitu,
gr8 to se ur reply.
I think ur suggesting custom idoc for accounting.
Though we need not use MASTER_IDOC_DISTRIBUTE.
We can still create custom idoc using BDBG.
Just need to instanciate BO-
CALL FUNCTION 'SWO_CREATE'
EXPORTING
 objtype = 'ZBUS6035_A' "My z- BO ,Here we can use standard BO
 objname = 'ZBUS6035_A' "Custom method
IMPORTING
 object = l_objhnd
EXCEPTIONS
 no_remote_objects = 1
 OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
break-point.
pass data to container for bapi
SWC_GET_ELEMENT lt_cont 'Date1' DATE1.
fire BAPI
CALL FUNCTION 'SWO_INVOKE'
EXPORTING
ACCESS = 'C'
object = l_objhnd
verb = 'ZBUS60351_A'
PERSISTENT = ' '
IMPORTING
return = l_return
VERB =
MODE_ID =
TABLES
container = lt_cont.
My problem is resolved now.Icould use ADD BAPI for IDOC triggere.
Thanks everybody for kind help.
Edited by: Sanjay_lnt on Feb 1, 2011 11:35 AM
Edited by: Sanjay_lnt on Feb 1, 2011 11:37 AM

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

File2idoc:Error in ALE distribution model for SendResponse

Hi,
I'm using XI to configure a file to idoc scenario.
Now in WE19 I could see relevant data,but in WE05 it showed the error status 51,and the detail message was "Error in ALE distribution model for SendResponse".
Do I have to create a distribution model in BD64?I did this ,but failed to create.

hi,
i dont think distribution model is required for inbound case.
just check the below configuration.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
chirag

Distribution Model BD64

Similar Messages

Maybe you are looking for