Interaction between Distribution model, partner profile, etc.

Hello,
I am a newbie in the SAP world, and I am a little bit lost in the behavior of the Outbound Processing (the send of an IDoc to an external non-SAP system).
Actually my question is how the following components interact during an outbound process :
- RFC Destination
- Logical Port
- Logical System
- Partner Profile
- Distribution Model
- SAP Gateway
- IDOC Repository
- ALE Service
Currently, the only thing I think I have really understood is that the RFC Destination allows to hide to SAP the Program ID of the registered external server...
Thanks a lot
Sebastien

For each logical system and each basic message type (for example, LOIBOM), a unique message type has to be defined by reducing the original one (for example, MYBOM).
If you reduce a message type, only the obligatory fields are automatically selected. You must select those segments and fields you want to have transferred. Fields that have not been selected for transfer always contain the value "/".
Maintain partner profile
Each of the message types of the customer distribution model (see above) must be assigned to the partner profile. Enter the receiver port (see above), package size, output mode and IDoc type in the detail screen of the receiver port. You must also define whether the IDocs should be sent immediately, or if they should be collected first.
Maintain customer distribution model directly
First define a customer model for a logical R/3 system. The displayed list shows which logical system is the sender and all the possible receiving systems that have been defined. "Create message type" defines which logical system receives information from the logical R/3 system.
When maintaining the customer distribution model, you usually add all (reduced) message types that should be sent from the R/3 system to the external system.

Similar Messages

Taking Dump of Ports, Partner Profiles etc before Client Deletion

Hi,
Let me firstly tell you about the requirement.
I need to delete a 9TB client using TDMS. And then re-create it again for users. Now the problem is , that the Partner Profiles, Ports will be deleted when I delete the client, which I cannot afford to loose are there are a lot of them.
So, what is the best way to take a dump of the ports and partner profiles and other relevant things. I tried taking the table entries into transports and thought of re-importing them. But I'm not sure what all tables will be there as there are many like :
EDPP1 (general partner profile),
EDP12 (Message Control),
EDP13 (outbound parameters)
EDP21 (inbound parameters)
Partner function exists in table TPAR
Outbound process code exists in table TEDE1
Logical message type exists in table EDMSG
Process code exists in table TEDE2
What is the table for Basic Idoc type
Port is defined in table EDIPORT but where is their assignment to the Logical Name its not in this table.
There would be so many tables that are interdependent and I don't wanna loose even a single one of them.
Please advice the best option, as I am nearing the deadline to delete this client.
Your help is really appreaciated.
Thanks.

Hi
Iam adding some pots to the above which may help you Take screenshots for some important Settings / Configurationsso that you can easily restore them afterclient refresh. For example
u2022     TMS Configuration (STMS)
u2022     Printer Settings (SPAD)
u2022     Logon Group (SMLG)
u2022     OP Mode (RZ04)
u2022     RFC Destinations (SM59)
u2022     WE20 u2013 Partner Profiles
u2022     WE21 u2013 Ports in IDOC Processing
u2022     Client Definitions (SCC4)
u2022     Logical System Names (SCC4 and SM30: V_TBDLS)
u2022     E-Mail Configuration (SCOT)
u2022     SAP House-Keeping Jobs and Customeru2019s Jobs (SM37)
u2022     SSL Configuration (STRUST) if using
u2022     Others
Se09 other request u2022object list Enter R3TR  TABU  RFCDES
Regards

Does it mean that, 1 CDM/Partner Profile/Port = 1 specific partner?

Hi experts,
As I am beginner to IDoc concept, hv few doubts, like,
1) Does it mean that the development of, 1 CDM(Distribution Model) / 1Partner Profile / 1Port = exclusively 1 specific partner? I mean, for instance the organisation possess 100 partners, so it means that it shuld hv 100 CDMs(Distribution Model) / 100 Partner Profiles / 100 Ports?
2) For out bound direction, for a newly created IDoc sending Does it not necessory to create/use the Process code?
3) If partner profiles r created, so the Ports r automatically cretaed in the system? Or we must create the ports explicitly?
4) Does it means that The distribution of CDM from sender to receiver = Creation of new CDM in the receiving system for that particular partner?
ThanQ in advance,
Rgds,
Sri.

Hi,
1) Does it mean that the development of, 1 CDM(Distribution Model) / 1Partner Profile / 1Port = exclusively 1 specific partner? I mean, for instance the organisation possess 100 partners, so it means that it shuld hv 100 CDMs(Distribution Model) / 100 Partner Profiles / 100 Ports?
It is not necessary exclusively but it can be (depend on your business process).
You could also have a single logical system and a single IDoc port for multi partner purposes. In this case, you can use message code and message function to segregate the partner data in receiver system/sender system.
2) For outbound direction, for a newly created IDoc sending Does it not necessory to create/use the Process code?
For transactional data i.e sales order, billing, delivery and etc., you still need to use process code via message control setup (in partner profile). However, for master data distribution i.e material master, vendor master, customer master and so on, you do not need to setup process code in the partner profile. The extraction program will call corresponding FM to generate and distribute the IDoc.
3) If partner profiles are created, so the Ports r automatically cretaed in the system? Or we must create the ports explicitly?
You can use existing IDoc port for new created partner profile or you can create new port via transaction WE21. System will not create automatically the port. You need to link to correponding message type in partner profile (WE20).
4) Does it means that The distribution of CDM from sender to receiver = Creation of new CDM in the receiving system for that particular partner?
If both sender and receiver systems are SAP then you need to setup distribution model (BD64) for both system. Otherwise, if only one SAP system involved and other is external system then you need only to setup one distribution model.
Hoep this will help.
Regards,
Ferry Lianto

While creating partner profile, if the partner type is u0093LIu0094 what r the sett

While creating partner profile, if the partner type is LI what r the settings we need to configure?

Hi Chiru,
For a IDOC to File scenario, just follow these steps:-
SLD-
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
In addition do the following in XI:
1. SM 59 - Create RFC destination pointing to R3.
2. IDX1 - Create a port for R3
3. IDX2 - Import IDOC metadata.
I hope this provides you a solution.
Regards.
Praveen

Generation Partner Profiles from ALE Distribution Model

Hi ABAP/EDI experts,
I am a trainee. I am getting training from Pvt consultancy. I am working on SAP Demo systems.
I am trying t generate an IDoc using ALE method.
IN SALE window, I created two logical systems,ZVK_SS_800 and ZVK_SS_820. I assigned them to two clients 800 and 820 respectively.
In SM59 i created an RFC connection ZVK_RFC004 of type 3. Here I gave the client Number as 820. ( I'm not sure what to give)
In BD64, I created an ALE Model and added the message type MATMAS with Sending and Receiving Logical systems.
From the Environment drop down menu , selected generate partner profiles and executed with defaults checked. ( Transfer IDocs Immediatley and Trigger Immediately).
I got the following log.
Log For Partner Profile Generation:
Partner:
In Green Color
Partner ZVK_SS_800 as partner has been Created ( Sending System)
Partner ZVK_SS_820 as partner has been Created (Receiving System)
Port:
In Red Color
Port Cloud not be Created
RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
Enter the RFC destination and Restart the generation.
Please help me to fix this probelm.
Any kind of Help will be surely rewarded.
Thanks,

From SM59, you can Test your RFC Connections between Clients. I would do this from Client 800 and test the Connection to Client 820. If that checks okay, I would then try SM59 on Client 820. Check the RFC Connection from Client 820 to Client 800. Be sure you have your Logical Systems defined on Both Clients. You can also double click on your Error Message to see if there is a Long Text Available that might give you further information as what needs to be corrected. I am not an Expert in this area, but have setup several ALE Models for my Variant Configuration without any problems. If you could include your EMail Address on your Business Card I could EMail you my instructions. Your Basis person may also be able to help you based upon your Error Message.

Change log for Distribution model and partner profile

Hello All,
Could any one please suggest how to get teh change log of the distribution model and partner profiles in SAP.
Thank you!
Arvind

Hello,
The documentation says what distribution model is used for. My question is can we have change log for any change in the distribution model like user, time and date.
In production system if distribution model and partner profiles are changed by someone to a destination which should not be used, then how can we trace who has changed it.
I hope I am able to explain.
Arvind

What is the difference between generate partner profile and creat partner

What is the difference between generate partner profile and creat partner profile ?

Create Partner ProfilesAlthough partner profiles are usually created automatically, because of the unusual inbound and outbound profiles needed on the same system, the manual generation of certain profiles is required.
The following subsections describe the partner profile settings for the standard client (assumed here to be ALExxxCyyy), as well as for the corresponding dummy client (assumed to be DUMxxxCyyy). The dummy client partner profiles should have been generated by the automatic generation process completed previously. Nevertheless, these should be checked to ensure that all profiles exist.
Generation of Partner Profiles
The following messages should be added to the 4xx-ORDR model for ALExxxCyyy to DUMxxxCyyy on the reference client:
ORDERS
ORDCHG
ZINVRV
ORDRSP
INVOIC
FIDCMT
The partner profiles should first be generated using the standard auto-generation procedure on the reference client (for SYNCH messages to be created).
This model should now be distributed to the both ALExxxCyyy and DUMxxxCyyy.
The partner profiles should now be generated on the client being configured (i.e. yyy) using the auto-generation procedure defined in the standard ALE configuration procedures.
Generate partner profiles for sending system. (Can only do this if at least 1 message type exists against the sending system's LS). This automatically generates the port if the LS and RFC name are the same.
generate partner profiles tcode BD82
creating partner profiles tcode WE20
 There are two methods for maintaining the partner profile:
 Maintain partner profile manually:
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Target system. Under Outbound parameters, choose the Create outbound parameters icon, and enter the values for the outbound parameters according to the slide Sender: Partner Profile (outbound).
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Sending system. Under Inbound parameters, choose the Create inbound parameters icon and enter the values for the inbound parameters according to the slide Sender: Partner Profile (inbound).
 Generate partner profile:
Prerequisite: The current distribution model is distributed to all participating systems.
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (outbound)
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (inbound)
Regards
Vasu

TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and

Hi All
Can anyone pls give me all the TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and BAPI
Thanks
ss

Hi SS..
 SM59-For creating the RFC destination
 we21- For ports
 we20-Partner profiles.
For more inforamtion Please look at the below information:
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 XI 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.
 Thanks and Regards,
 Chandu.
Message was edited by:
 Chandu
null

Partner profile setting between BI and R3

Dear all,
we have client refersh of R3 quality now they have change the name of the client to 330 to 720.
now if i chekc the source systm , it show the RFC checked failed.
now i need to connect with new configuration so please let me know what are the step and what should i do in partner profile with details.i have only one day to do this.

Hi Viral,
Check this link :
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/908836c3-7f97-2b10-4cb8-e6790361c152
Cheers,
Tanish

Inbound delivery partner profile question

Hello,
Based on the help documentation, i have setup a distribution model between ECC and EWM system.
After executing this transaction /n/SPE/OL19, my distribution model is properly generated and I am able to send Idoc from ECC system. However on on EWM system, I am getting an error related to message type DELINF is not found in inbound partner profile.
I searched in WE80 and I do not see this message type in SCM system, can someone kindly suggest if the below mentioned message types used in ECC are right and on the SCM side I have only one message type which is SYNCH.
Following message type in ECC
DELINF
DELORD
/SPE/LIKP.DELIVERYCHANGE
/SPE/LIKP.REQUESTCHANGES
/SPE/LIKP.SAVEREPLICA
BUS2015.DELIVERYCHANGE
BUS2015.SAVEREPLICA
BUS6050.EXECUTE
Following message type in SCM
SYNCH.
Am i missing some setting which is preventing from idoc to be posted in EWM to generate inbound delivery request.
If someone could suggest what are the message types should exist for inbound in EWM side or DELINF needs to be added in EWM system.
Appreciate your suggestions/comments.
Thanks
Bhaskar

No..you can not know it.There is no log.

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.

IDocs, INVOIC partner profile configuration

Hi,
I need to receive the INVOIC IDocs from sender system.
Sender(S) system is new system
receiver(R) system is already exisitng system.
I tried to configure the inbound settings in receiver syste. But message type INVOIC, process code INVL, FM all are already available and configured for some ohter systems.
Now if i configure only partner profiles and distribution model, then is it work.
Thanks
Kiran

Kiran,
INOVOIC, INVL, Process codes etc come with the standard system. They can be configured for any partner profile and any sender system.
First, you need to determine the inbound connection. Will the new sender system (S) going to follow the same RFC connection already setup for other sender systems? E.g. Are all the inbound IDOC's flowing through PI or a single EAI system?
If yes, then you just need to setup a new partner profile and use the same port already setup for your existing connections.
If no, then you have to determine how the sender system will connect with SAP. Will they drop files in the SAP's application server? After dropping can they execute the startrfc.exe with required parameters. If they can then you can just proceed with creation of a port to listen that folder (assuming the RFC connection is already setup for that connection) and move ahead with partner profile creation and other mandatory setups. If they cannot trigger the startrfc.exe, then you have to define a new RFC destination (SM59) and a new port (WE21) to read data for this RFC destination. You have to determine when to read the data (e.g. explicit host type etc).

Wrong logical system for partner profile

Dear gurus,
we have been sending ORDERS Idocs for some time now, using to a logical system called MSC_MM_PRD, a RFC connection called MSC_MM_PRD and a port for Idoc processing called A000000003.
Now, we would like to send ORDERS Idocs to another logical system. We created that new logical system called MES001, a RFC connection (MES) and a Port for IDoc processing using that RFC destination (A00000004).
After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.
But then, I had to create a new message type for purchase orders to use that new connection (called ZEDI) and I guess that is where I made a mistake: I copied the existing message type for the old ALE connection and changed some parameters (like name etc.).
Now, when I create a new purchase order and add a message of the new type and save the order, I get an error message:
EDI: Partner profile outbound process code not available
Message no. E0335
Diagnosis
An outbound partner profile could not be found with the following key:
/MSC_MM_PRD/LS//EF/ZEDI//
[u2026]
Procedure
Please check the outbound partner profiles for the assignment of the process code:
As you can see, SAP tries to find an outbound partner profile using the old logical system (MSC_MM_PRD) and the new message type (ZEDI) as a key and obviously fails.
Can anyone please tell me why SAP uses the old logical system and how I can change that?
Cheers
Alicia

Hi,
problem was, that we had not created a proper distribution model for the message type (BD64). After we did that, it worked fine.
Cheers
Alicia

ALE Distribution Model

Hi,
I've created an ALE distribution model to process the interface concerning Set Up HR and Accounting. Initialy we make it all and distribute it to the receiving system (FI) and it seems to be ok. After that the funcional team generate some movements and the IDOC's were generated but they were not sent to the FI system. We've a look at tRFC and an error concerning user or password invalid appears, so i define again the user comunication and after a few adjustments to the model view we distribute it again to the FI system. When i execute it the following message appears : Model view HRFI-CFP has not been updated / Rreason: Distribution model is currently being processed.

Next step we delete the model view and created it again but the same error still remains.
Can anyone help me ???
Thanks is advance.
JMMatos

Hi
Distribution Model A model that describes the ALE message flow between logical systems.
Applications and the ALE distribution service layer use the model to determine receivers and to control the data distribution. The relationships between logical systems, message types, BAPIs and filters are defined in the distribution model.
Ex: The screen shot depicts customer distribution mode ALE_TRNG_Mar07.
Sender Logical System EC1CLNT800
Receiver Logical System SALES
Message Type CREMAS
No filter conditions defined.
This configuration step allows the installation of core ALE features on which data transfer activity will be based.
In the distribution model you can specify the messages to be sent to a given logical system. You can also define the conditions for the content and dispatch of messages in the filters.
The distribution model consists of one or more views that you can define
After creating the distribution model the model needs to be distributed to the receiver system.
Partner profiles need to be generated in both sender and receiver systems using transaction BD82 (automatically) or WE20 (manually).

Use of Distribution model in Idoc to file

Hey guys
just outta curiosity,why do we need to create distribution model for IDOC to file scenario,we can ofcourse do the scenario without creating Distribution model (by using WE19 to send IDOC's).
is it because for day to day transactions we wont go for WE19(its just for test purposes),we rely on Distribution model?
also is it job of XI developer to create DM ?
thanx
ahmad

Ahmad,
BD 64 Distribution model allowed you to automatically create the Logical Systems ( BD54 ) and the partner profiles.
The steps you create to send an Idoc from your R3 system to XI ,( Bd54, we20 ) etc are all nothing but steps in the Distribution Model Bd 64 to send an Idoc to XI,
Regards
Bhavesh

Interaction between Distribution model, partner profile, etc.

Similar Messages

Maybe you are looking for