>>1. Port
Ports are channel through which idocs are exchanged.
>>2. Partner Profile
Partner Profile specifies the kind of message that we are going to exchange with our business partner
>>3. IDOC type and IDOC
IDoc type defines the structure of the idoc. IDoc is a container which carries the data from one system to the another.
>>4. Process Code
Process Code refers to inbound function module which will read the data from the idoc and post it in the system.
>>5. Message Type
Message Type defines the kind of data that you are exchanging with your business partner.
Cheers,
Hakim

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

Need a Clarification in defining a Partner Profile

Hi Experts,
I have a requirment wherein i need to send delivery idoc delvry01 for all the deliveries created for a shipping point.
I have created a output type ZLD0 and has Shipping point as the access seq. I have maintained condition records for the shipping point to create idocs for.
I have created partner profile with the logical system. But its not working.
Is there anyway to trigger idoc on the delivery document by not defining each and every customer on the partner profile.
i mean to say in this case how to create the partner profile, is it with logical system or Customer number. if it is with customer number, if i have 1000 customers, creating 1000 Partner profiles is doesn't make sensce...
Please clarify this...
Thanks in Advance
Narendra.

I haven't done this for deliveries but we did something similar for the Purchase Orders, so maybe this will give you some food for thought.
We defined one Logical System per Purchasing Organization. Unfortunately, the PO output could not have been assigned to the 'logical system' partner type. So what we ended up doing - we created a new outout type ZNEU (copy of standard NEU) and set up access sequence Doc.Type / Purch. Org. / Vendor. Then in MN04 for this option we added a record for each Purchasing Org (EKORG) and all the applicable Vendor Numbers. It is pain in the back but it's much faster than creating individual profiles.
Now when I look at the PO output there is a line with ZNEU and vendor # as a partner but when I run RSEOUT00 I get an IDoc for the whole Purchasing Org.
So replace Purch. Org with Shippint point and Vendor with Customer and it's pretty much your scenario. I'm not sure what's the SD transaction similar to MN04, try VV31.
Good luck!

Cdm and partner profiles

can help me out in,,,,,What are CDM and Partner Profiles in ALE??

Hi Praveen,
Chk these links
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
ALE
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.

***Reward Points if Useful
Regards
Gokul

Process code & Partner Profile Issue

Hi Experts ,
Hi ,
I need to configure partner profile with a external system . I will be receiving customer data from the ext System .
I though of using msg type DEBMAS and msg type
and process code DEBM. I see its uses function module IDOC_INPUT_DEBITOR.
So what exactly this function module does ?
I was wandering if I need to create new Process code / Function Module .
My requirement is receiving the customer data along with address , shipping informations , customer no . So that when I drop orders its becomes available.
Thanks
MM_sD

Hi ,
Check all the settings needed for an R/3 - XI- R/3 scenario..... In ur case R/3 to XI is working fine and u have to check the XI-R/3 side.
Check the RFC destination ( Both in XI and in R/3)
Check the logical system name
PORT, Partner profile .....
Regards,
Jude

Process Code - Idocs

Hi all!
    In Outbound parameters of partner profile we r mentioning the process code.
   Can u pls tell me why? i feel bcoz..... suppose we r purchasing from vendor in outbound parameters i am mentioning the process code.
Now in the inbound processing of the vendor the vendor will access our process code via RFC to generate Idoc and Vice Versa.
   Pls Tell me i am right or wrong.
Looking for your reply very eagarly.
Thanks
Rahul.

Rahul,
Process codes are used in both Outbound & Inbound processing.
Outbound: The main purpose of the process code is, there is an FM which is attached behind the process code and that FM will populate all the segments with the necessary data.
For example: I have an Sales order and I need to send an order confirmation. So you define your partner profiles in WE20, provide the necessary message type and double click on that you can see the message control and your output type, process code ..etc
Similarly is the case with Inbound, say you receive an Idoc from another system and the same data needs to be posted into your system, then you do the similar setting for Partner profiles, but in case of Inbound, you will not have any Message control, but an process code is directly defined here. There is an FM which is tied to this process code and the data is posted based on the FM.
Hope it is clear.
Thanks,
Suresh Ganti

Send emails to specified users,but SAP is picking from partner profile WE20

Hello
By using FM 'SAP_WAPI_START_WORKFLOW', passing with task = 'TS00007989' amd triggering workflow, if at all my IDOC get fails! This work flow/task will send en emaill to the Permitted Agent defined in partner profile, WE20 for that partner type/message type, fine. In our case, the Permitted Agent is 'Workflow Administrator', so he is getting emails for IDOC errors.
But, we do not want to let SAP pick this Adminstartor from partner profile, we want to maintain a custom table for users IDs and we want to SAP pick this receivers/recepients from this custom table for User IDs
Note: already am passing user IDs in ' agents' table parameter explicitly, but still SAP is picking workflow admin from partner profile!
How can i achive this? any user-exit or any BADI or ENH? Pls. let me know
Thank you

HI
Can you please give inputs on following
1. Where you are triggering WF using 'SAP_WAPI_START_WORKFLOW'
2. is that workflow custom workflow ?
There in one way triggering custom workflow when IDoc is in error mode.
1. When you assign function module to process code there is ALE table button in front of FM.
2. Once you click that you can assign Object type, start event, end event.
3. To this particular event custom worklfow will be triggered.
4. In your custom workflow you can select agents as per your requirement.
Regards
Sachin

Process Code for Outbound Production Order??

Does anybody know the Process Code for Outbound Production Order??
BASIC Type : LOIPRO01
Message Type : LOIPRO
Regards,
Ravi

Hi Everybody.
There's no standard process code for LOIPRO Outbound Idocs.
This Idocs are threated as master data info, and could only be automatically generated by Data Distribution Model.
BD64.
Anyway, you can define your own Outbound Process Code in WE41 using CLOI_MASTERIDOC_CREATE_LOIPRO FM.
You can choose.
Regards.
Albert.

Process code for 869(EDI ) Order Status Inquiry Message type.

Hi Gurus,
Please can any one help in providing Process Code for 869 Order Status Inquiry Message type.
Thanks,
Sudhakar

Hi Everybody.
There's no standard process code for LOIPRO Outbound Idocs.
This Idocs are threated as master data info, and could only be automatically generated by Data Distribution Model.
BD64.
Anyway, you can define your own Outbound Process Code in WE41 using CLOI_MASTERIDOC_CREATE_LOIPRO FM.
You can choose.
Regards.
Albert.

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

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

WE20 - partner profiles: inbound parameters - how to determine process code

Running standalone scenario on SRM 5.0.
First of all, it is not possible to "generate partner profiles" automatically in BD64 (distrubution model) in the backend system for message types:
BBPIV, BBPCP, ACC_GOODS_MOVEMENT, ACLPAY and MBGMCR.
The following error is displayed:
BBPCO
Inbound parameters for message type BBPCO could not be created
Enter a valid process code
etc.
When trying to create partner profiles manually in WE20, how do I determine the process codes for the different message types?

Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
Solution
Check and if necessary, correct the following entries:
1. Assign function module to message type
Transaction WE57
The following entries are required:
Module IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
Type F F
Basic type BBPIV01 BBPCO01
Msg type BBPIV BBPCO
Direction 2 2
Object type BBPBUS2081 (not for Release 3.1)
Note that object type BBPBUS2081 is not defined in Release 3.1*. In
this case, the 'Object type' entry remains empty.
2. Characteristics of inbound function modules
Transaction BD51
The following entries are required:
Inbound FM IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
Input type 1 1
03.09.2008 Page 2 of 3
Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
Dialog allowed No No
3. Create the missing process code with Transaction WE42 (change inbound
process code). You can name the process code whatever you want. 'IV01'
or 'CO01' are examples.
The entry should look like this:
Process code IV01 (CO01)
Description BBPIV (BBPCO) inbound invoice
Option ALE Processing with ALE service
Processing Type Processing by function module
Save the entry. You are then on the detail screen. Enter:
Module (inbound)
Function module
IDOC_INPUT_BBP_IV (IDOC_INPUT_BBP_ACC_PO)
Application object
Object type
BBPBUS2081 (- no entry -)
4. Maintain the process code that has just been created in the partner
profile for the logical system.
Transaction WE20
Partner type 'LS'
regards
Muthu

Steps to Configure Port and Partner Profile for Outbound process

Hi,
I want to Configure the partner profile and Port definition for outbound Message type REMADV ( for Vendor).
Could anyone please tell me the steps to configure.
Thank you,
Renu

Hi Renu,
In partner profile we define the system which are going to communicate between themself and send data, here we give some logical name for the system which are going to be partners in data communication.we set it using WE20
Port is a medium through which we send the data it connect one system with the system in other end its unique, depend on the scenario we use diff ports like file port(EDI) transactoional port(ALE) internet port(for internet apl), like this i dont remember all the name, so according to our application type we select the ports we set port using WE21 usally tport name start with A*** something like this. withour defining a port we cant communicate with other system its the linker b/w the 2 system.
For more information please refer the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4943f2b7-0a01-0010-37af-faff35b2f08c
Regards,
Moqeeth

EDI Partner Profile creation at Transaction Code FI12

How is the partner profile created when you select the Icon Partner Profiles, which is transaction code WE20 that is accessing from transaction code FI12.
The type is B for bank. Can the partner number be a end user defined number? Can this be the vendor number for the bank? That does not appear to be an option!
Here are my questions of the Post processing permit agent design.
How are the values for the "Types" created?
Thanks
Chris Courter

Rohan Patil wrote:>
> BEGIN = 1.
> edi_dc40 segment values
> SEGMENT = 1.
> TABNAM = EDI_DC40.
> MANDT = 120.
> DIRECT = 2.
> IDOCTYP = CREMAS05.
> MESTYP = CREMAS.
> SNDPORT = SAPNBD.(XI port)
> SNDPRT = LS.
> SNDPRFC = LS
> SNDPRN = NXICLNT120.
> RCVPOR = SAPNED.(ECCport)
> RCVPRT = LS
> RCVPFC = LS
> RCVPRN = ECCCLNT120(ECC partner number).
Hello Rohan,
IDocs SNDPRN/SNDPRT/MESTYP will be taken in SAP for processing the received IDOC,so in your case either you need to create the partner profile NXICLNT120 with all inbound details or need to change the same in mapping and pass the values of your partner in SNDPRN SNDPRT fileds of control record
HTH
Rajesh

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving 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 XI towards R/3
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) Create an RFC Destination to XI 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 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 Inbound 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 Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
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
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Define Port, Partner Profiles, Process Code

Similar Messages

Maybe you are looking for