Maintaining distribution model for ALE audit.

hi,
I have to create a bcakground job in the receiver system to periodically send back the audit data to the sender system. To do the same i need to maintain a distribution model for ALe audit. For doing so i don't have the modal view XIDEMO in BD64. How to implement. Also in SM59 while maintaing RFC destination it says U6D_700 no longer exists. Please suggest how to get it resolved.
Regards
Akash SInha
Edited by: Akash Sinha on Dec 16, 2009 9:59 AM

Hello,
You can create your own model view in BD64. In the model view add message type ALEAUD with sender as your system name and logical system of your reciever.
Also configure the Partner profile in WE20, with outbound parameter ALEAUD and IDoc Type ALEAUD01.
Schedule the program RBDSTATE with the required parameters.
BR/Yogesh

Similar Messages

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

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.

Distribution Model for the Message

want to create a filter for my Distribution Model for the Message Type HRMD_A .
The filtering should be based on Company Code .
I'm getting only infotypes but now should I filter based on Field BUKRS ?

1. Go to Tcode BD59.
2. Create a Custom ALE Object Type
3. Specify the corresponding Segment name where BUKRS exists and the Field Name as BUKRS.

How to maintain Customer distribution model in ALE

hi FRIENDS..
i wish to know what will be the transaction code of maintaining the customer distribution model, and how we maintain it. and also distribute custome model in IMG sreen... please reply me...i will surely award you nice points....
bye...
naim

U can create/maitain distribution model using BD64.
Or else u can create it using SALE transaction code.
U need to give sender/reciver/msg type.
==============================================
procedure:
click on Create Distribution model button-->give the technical name
select the DModel Technical name>add msgtype>
it will ask sender/reciver/msgtype.
pass those parameters and generate partner profiles through environment menu
=================================
to distribute a model view to partner syste,:
Select mview
edit>modelview>distribute
Message was edited by: Eswar Kanakanti

Executing RBDSTATE for ALE-Audit Processing

Hi Experts,
when I execute RBDSTATE into my Z_Function for BOMMAT Inbound Processing, it doesn't find any IDoc for the ALE-Audit Processing :
"No data relevant to audit were selected."
Any idea ?
Regards,
David

Hi Gordon,
I've decided to create another Distribution Model, only for ALEAUD (why ? I don't know...).
Now the IDoc ALEAUD is created into the Target System, but with Status is 02 "Could not find code page for receiving system".
Regards,
David

"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

Distribution Model for PP-PDC

Hi Guys,
I'm new to this and I'm trying to find out, how I can create a filter for a "Subsystem Grouping" based on Work Centers.
I've already assigned a subsystem group to all work center belong to a single plant.
I'm trying to setup the distribution model to send IDOCs to an external system
I've added a BAPI with details as follows:
Model Name:                  XXXXX_LS
Sender:                          XXXXX
Receiver:                        XXXXXX
Obj. Name / Interface:     RCVPRORDCF
Method:                          ReceiveProdOrder
I've also assigned all Work center from 1 plant into the same Subsystem Group in CR02 ->Subsystem Link -> Subsystem Group = 301
How can I create a filter to filter by the subsystem group for the work center, to download only those production orders based on this?
Or, is there another way that I can filter by plant?
Thanks a lot for the help guys

1. Go to Tcode BD59.
2. Create a Custom ALE Object Type
3. Specify the corresponding Segment name where BUKRS exists and the Field Name as BUKRS.

Disable ssn field in distribution model for e-recruiting

We are running e-Recruiting 3.0 as a stand alone, and moving HR master data using ALE. The only problem is that the client does not want to have SSN in the e-Recruiting system. Is it possible to filter out SSN within the distribution model, if not where is it stored in e-Recruit so we can mask it after it is moved over.
Thanks,
Alex

Hi Alex:
Follow this path in IMG path
SAP Netweaver --> Application Server -->IDoc Interface/ALE --> Modelling and implementing Business processes --> Converting data between sender and receiver
Follow the steps there and you can do it.
Please award points if Helpful.
Thanks
Venkat

HR Indirect Role Assignment through HR ORG Distribution Model with ALE

1) When i assigned indirect (position level security) roles in CUA(SolMan) using pfcg click on organization managment to position after that i did user comparsion but i can not see user id in user tab.
2) If personel no is not the same as infotype 0105 assigned user, How do you check your Indirect role assignment If you are using soultion manger. We dont have PA20, PA30, PA48 t-codes in soulution mangers.our CUA a in Soultion manger .
Help is greately appericiated. Thanks

I created HR_ORG structure(HRMD_ABA) in dev (HR system-Sending system) and add filters according to help.sap document, generate partner profile using we20. After that I transfered org structure in CAU (SolMan-Non HR systems- Receving system) using ALE run (Run SA38 -RHALEINI) i think its working.
Composite roles are reside in Dev (HR-system), For indirect roles assignment (position level security) i created composit role just only roles name and description with out tcodes and auth object in CUA (SolMan -Non HR system).
For test position assigment, I run pfcg in CUA(SolMan) click on organization management select position and click indirect roles assignment after that i did user comparsion but i cant not see users id in user assignment. Please let me know any helpful Suggession. Thanks for ur quick response..

Maintain Distribution Model

I need a list of all fields that will crate an IDOC when they get changed.
IDOC Type is DEBMAS
And then I need a list of all Field from the Trx XD03 that will not crate an IDOC.
For example Comments
Can someone please help me?

hi,
we can fing all the fields which create an IDOC if they changed... but it is based on MESSAGE TYPE but not with Iodc type..
in <b>Tcode BD52</b>-->if you give the Message type name -->it will display the field names and table names....based on this configuration..all the chage pointers which create an IDOC will stores in VIEW -- BDCPV..

Inbound idoc- distribution model

Hi,
    Is it mandatory to create distribution model for inbound idoc processing?

Hi all,
        Mine is inbound scenario.
        Sender is XI system
        Receiver is R/3 system.
        Do i need to maintain distribution model for this?
1.As per my knowledge, distribution model is only created in outbound scenario? In inbound scenario why distribution model is not created?
2.On the outbound side, after generating partner profiles we get SYNCH SYNCHRON in outbound partner profile. My question is there any setting to generate partner profiles on inbound side also?
or else SYNCH SYNCHRON will be for only outboud?
Please clarify........

Distribution system for logical system not correctly maintained

Im logged in into SAP R/3 system. When starting transaction POIT I chose "production orders for".
I fill in the fields for
Plant -> 001
Material -> T-HV200 (Ice Mix)
At the top I have to enter a "optimization system".
I chose the logical system I created (CE6CLNT850) from a list.
After I hit the execute button it says:
"Distribution system for logical system CE6CLNT850 not correctly maintained."
The distribution model for CE6CLNT850 (transaction: BD64) looks like this:
Componentsystem CE6 SAP R/3 4.6c----
CE6CLNT850
NX7CLNT800----
NX7CLNT800,No Short text exists
LOIPRO----
Production order
What is the problem here?
And by the way, WHY DO I HAVE 479 entries in my list of logical systems when I'm trying to chose the "optimization system"???
best regards,
Lunatikk

Thanks for your answer,
the RFC destination is configured correctly. It says that the connection works when I run the test.
I'll post it in an other forum as you suggested but I have another question:
You said that it is possible to have 474 logical systems configured on the system.
1. Who defined those systems and why?
I am the first one in my company using this system.
We ordered to a SAP system through RAC Service.
I thought we would get a "fresh installation" of the SAP system -
2. please correct me if I'm wrong.
For example there are logical systems with names like "boon software" and "camstar", which are real companies.
There aren't just logical systems configured, there are also additional RFC destinations, distribution models and ports that were there from the beginning.
3. Is it possible that those logical systems interfere with the sending of the IDOC. Could it be possible?

Are these steps correct for ALE configuaration ?

1.An ALE Configuration we have to do five steps
a)Define logical System (SALEsending and receiving system logical systemdefine logical system)
b)Assign client to the logical system( SALEsending and receiving systemlogical system Assign client to the logical system)
c)We have to define port at (WE21)
d)GENERATING PARTNER PROFILES(WE20)
e)Define target system for RFC calls (sm59)
f)Creating Distribution model (BD64)
g)WE42 for creating process code.
h)Send Data ( bd10)
i)Get Data(bd11)
j)BD51
k)WE57
We have to repeat the FIRST 6 steps for each of the sender and receiver and those are compulsory. I am not yet clear about the last 5 steps.
E.g. our sender is 200 and receiver is 400
So for each of them we have to do the 5 steps twice.

folow the link
http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html
/people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
which will givw u the steps for ale configuration
steps are
. ALE->Sending and Receiving Systems->Logical Systems->Define Logical System. a. Here you add the name of the logical system for the distributed system. To make them easy to find I like to name them based on instance/client so in the case of the system listed above I would call it DM7200. This naming convention makes it easy to follow in various systems.
2. ALE->Sending and Receiving Systems->Logical Systems->Assign Client to Logical System.
a. In this step you assign your logical system to a particular client. WARNING: DO NOT CHANGE THIS IF IT IS ALREADY CONFIGURED!!! That holds especially true on an FI system as it cannot be changed once it is set. Make sure to discuss this with the Basis team before entering the data.
3. ALE->Sending and Receiving Systems->Systems in Network->Synchronous Processing->Determine Target System for RFC Calls
a. This area allows you to tell SAP where to make RFC calls based on the logical system. That means that when I want to look up Vendor information in cases like infotype 194 and 195 where a function module is called that I can tell the system where to go to find that information. To configure this you should make sure that the system where the financial information will be kept is listed.
4. ALE->Modelling and Implementing Business Processes->Maintain Distribution Model and Distribute Views
a. In this step we will define where the FI data comes from and what data we expect to receive. We will also define the system that will be receiving the payroll posting and what data we will be sending that system.
b. SAP Recommends the following list of messages to be received from the financial system:
i. COACTV-IDoc for cost center/activity type
ii. COAMAS-Master activity type
iii. COELEM-Cost Element Master Data
iv. COGRP1-Cost Center Groups
v. COGRP2-Cost Element Groups
vi. COGRP5-Activity Type Groups
vii. COSMAS-Master Cost Centers
viii. CRECOR-Core Vendor master data distribution
ix. CREMAS-Vendor master data distribution
x. GLCORE-Master data G/L accounts (CORE IDoc)
xi. GLMAST-Master data G/L accounts (master IDoc)
xii. PRCMAS-Profit center master record
xiii. RCLROL-Reconciliation ledger rollup
c. To add these messages you can follow the steps listed here:
i. Go into change mode by clicking on the pencil/glasses button or Distribution model->Switch Processing Modes via the menu
ii. Click on the Create Model View Button
Fill in the data for your model. Below is my example.
iii. Now it is as simple as adding message types. Click on the Add message type button and enter the required data. The sender is the FI system and the receiver is the Payroll system. Tip: Once you add the first message type if you select it before adding the next message you will only need to fill out the message portion and not the sender and receiver
iv. Now we need to build the partner profiles so that the systems know where the distribution model needs to get or put things. To do this go to Environment->Generate Partner Profiles.
Enter the partner system you want to use and press execute or F8.
This screen shows the successful creation of the partner profiles. If you want to see them can go to transaction WE20.
v. Now we must send the model to the other system. To do this use menu path Edit->Model View->Distribute
Now I should be able to see this model in my FI system, in this case, DM3. I can take a look at this via transaction BD64 in the other system
You'll notice that the coloring on the messages and models is in gray. This indicates that the model is maintained in another system.
d. We also have to configure the model for posting to the other system. In this case we will be using BAPI's and not message types. SAP recommends the following BAPI's:
i. AcctngServices.DocumentDisplay, Accounting: Display Method for Follow-On Document Display
ii. AcctngEmplyeeExpnses.Post, Accounting: Post G/L Acct Assignment for HR Posting
iii. AcctngEmplyeeRcvbles.Post, Accounting: Post Cust. Acct Assignment for HR Posting
iv. AcctngEmplyeePaybles.Post, Accounting: Post Vendor Acct Assignement for HR Posting
e. For the most part the steps are the same as above but it is slightly different because you use the Add BAPI button instead of the Add Message Type. BAPI's are case sensitive so you'll need to be exact.
<REMOVED BY MODERATOR>
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 22, 2008 2:27 PM

Need of distribution model in IDOC triggering

Hi,
I have one question dat is it necessary to maintain distibution model in BD64 for outbound IDOCs or only maintaining partner profile in WE20 is mandatory.
I have seen some cases in which distribution model is not maintained.
Please let me know the cases in which we maintain distribution model
Thanks in advance.

hi,
The distribution model describes the ALE message flow between logical systems u2013 that is, it determines which messages are distributed to which logical systems.
For example, you can make distribution dependent on conditions that you define as filters in the ALE distribution model.
please refer this blogs for more info:
Data Ditribution Model BD64 config
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a610f507d11d18ee90000e8366fc2/frameset.htm
thanks ,

Maintaining distribution model for ALE audit.

Similar Messages

Maybe you are looking for