Partner Profiles related

How to obtain the corresponding process code for a particular message type.
My requirement is to add a new Message type ORDCHG for a particular partner.
Plz provide your valuable suggestions.

Hi!
U need to check whether its a outbound or inbound message type.
Based on that info check for transaction we42 for inbound and we41 for outbound procces codes.
Search for the approprite proceed code.This can be done by selecting the process code and click on the logical message folder in the same we42 transaction.
u could see the message type assigned to that proces code.
for adding the message type to the partner profile access we20 and then go for the appropriate logical system and add the message type accordingly to the outbound or inbound message types.
thanks
kedar

Similar Messages

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

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.

Partner Profile configuration for EDI 810

Hi,
I am configuring partner profile for EDI 810 (Invoice). In the message control tab, what values should be entered for
1. Application
2. Message Type and
3. Process Code
Thank you.

Hi,
- Check Transaction NACE to see what applicatios you can use for different objects.
- Check transaction WE42 for all outbound process codes
- Check transaction WE41 for all inbound process codes.
- Check transaction WE64 for inboud / outbound message types and related process codes.
EDI 850:
Application - EF
Process code - ME10
Message type - NEU ( or your custom message type setup for EDI )
IDOC - ORDERS01 to ORDER05
EDI 810:
Application - V3
Process code - SD09
Message type - RD00 ( or your custom message type setup for EDI )
IDOC - INVOIC01 , INVOIC02.
EDI 820:
i think this is for inbound idoc of Payment Order/Remittance Advice. When yuo setup inbound partner profile, you do not need to know application
Process code - LOBX
Message type - LOCKBX
IDOC - PEXR2002
Let me know if you need any other information.
Regards,
RS

Partner profile,Message type

First time if I am configuring SAP R3 and SAP BW system
I need to create Partner profile and Port definition ,message type RSINFO,RSSEND,RSRQST.
Creating SAP R/3 source system in BW-I need to use RFC user or my user id is fine.
Any one help me out which message type goes to where or related any documents.
Please advise on this

Hi,
For info about source system connections see the following notes:
793717 Client copy into the BW client in Netweaver/mySAP ERP
606757 Naming conventions for logical systems
524554 Storing destinations in the BW environment 
423184 ALE: Problems with logical system names
325470 Activities after client copy in BW source systems
184971 Notes on BW source system connections 
184754 Procedure after BW database copy
184447 Building a BW-system landscape
184322 Procedure after DB copy of BW source systems
121163 BDLS: Converting logical system names
Kind regards, Patrick Rieken.

Delivery split through VLSP along with JIT Calls with AW Partner profiles

Hi SAP SD/LE Guru's,
I have one critical issue to resolve immediately in my implementation of SAP 4.6C system in multinational automotive industry. It's in the area of Delivery split along with AW - Duns number partner profile and JIT calls.
Here is the scenario:
1. JIT(Just In time) calls will be created through EDI based on the ship-to, PO Nos, Duns number.
2. The requirements will be updated in Scheduling Agreements JIT Delivery schedule.
3. Picking is done based on the requirements.
4. Packing, Deliveries and Handling units are created: Note: Each handling unit is linked to one JIT Call.
5. Based on the Shipments, Deliveries needs to be split into further sub-deliveries.
Ex. One Delivery has two HU's. This needs to be split into another delivery so that one HU need to be detached from original and attach to new delivery. At the same time corresponding JIT call also need to be detached from original delivery and attach to new delivery. This can be done through VLSP : Subsequent split(Outbound delivery). Split profile: 003 - split based on Quantities.
The issue: When executing delivery split using VLSP and split profile: 003, the system is terminating and giving short dump.
The error analysis says that AW - Duns number is creating the problem. The short dump occurs in SAPLV05I in Function module: SD_PARTNER_UPDATE.
There is an SAP note: 154766 related to this problem says that Partner header should be used only once in copy control.
But in customization of copy control from Sales order to Delivery, there is no VBPA Partner header.
I appreciate if you can provide solution for delivery split and resolve this short dump issue.
Thanks,
Murali Chintakunta

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

Error: "EDI: Partner profile inbound not available"

Hi All,
iam getting the following error while loading the FI related data.
"EDI: Partner profile inbound not available"
Suggestions are appreciated.
thanks
Kiran

Hi,
Refer the link:
Re: EDI: Partner profile not active
With rgdS,
Anil Kumar Sharma .P

Creation of Partner Profiles in EDI

Hello!!
Good Afternnon to all.
how to create partner profiles in EDI.
Is it the same like we create in ALE/IDOCS.
Please reply the steps and tcodes to create.
regards,
Ram Mohan

The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
3. After that, assign the IDoc Type to Message Type in WE82.
4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
i. In Message Control Configuration, we'll maintain
a. Condition Tables
b. Access Sequences
c. Output Types
ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.

Partner profiles usage

Hi,
Please can any one send me details about partner profiles usage and the tcode where exactly we have to maintain this.
If anyone have documentation on AlE is added advantage for me.
Regards,
Koti

Hi,
Logical System name is used to indicate the application system to which you are sending the data. Partner profiles use the above Logical System name to determine the system to which the data is to be sent ie you have to tell wether inbound or outbound.
Below are the links for ALE IDOC related materials.
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)
Reward points if useful.
Regards,
Soumya.

What is PDC in partner profile? and PDC time req. ID card

Hi all,
These are actually tabs when you click F4 on agent in WE20 (partner profile). What is PDC? Please point me to related files or threads.
Thanks,
Charles.

Hi,
Please check this online document.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ed60b490-0201-0010-dc82-8bea16db1dfd
Regards,
Ferry Lianto

Importing Trading Partner Profiles

Greetings,
Is there an XSD that captures our notion of Trading Partner Profile? If so, is there a back door way of importing XMLs of that type into an Oracle Integration B2B (I suspect there's no way of doing that from the console)?
To elaborate, IHAC who is trying to migrate from an existing B2B deployment to Oracle Integration. In the process, we will need to recreate the tons of TP profiles they've already configured in Oracle B2B. The good news is that those existing TP profiles TPs can be exported into an XML format. If we support that format ourselves, that I was thinking of running their XMLs' through an XSLT to align it with our format, and then importing those XMLs automatically.
On a related note, I'd be interested to know if we understand ebXML CPPs and CPPAs, because in general, that would be a good way of importing TP profiles and agreements, regardless of their origin.
Regards,
Karthick

Hello Karthik,
We have the notion of Self Service API which can be used to create Trading partner and Agreement in Bulk. Please refer
http://rameshnittursblog.blogspot.com/2007/09/creating-b2b-metadata-using-self.html
Please send a test mail to [email protected] for self service API samples.
Rgds,Ramesh

Client Copy and Partner Profiles

Hi,
I have a doubt related to client copy and how it will affect the partner profiles.
We have a client which has quite a lot of partner profiles defined in it. Now the problem is that the Basis team is planning to perform periodic client copies on this System which will copy the data from another client say 010 to the client in discussion. My doubt is, when this happens what will happen to the partner profiles that are already there in the target? Will it be lost resulting in we creating it all over again? if so is there anyway to get around this issue?
I would appreciate any kind of input on this issue.
Thanks
Praveen

as far as i know a client copy is based on some parameter say it can be client copy based on master data, client copy based on application data etc. I guess partner profile is an application data so in tht case if client copy is done in its context no data will be lost.
just my thought, but please confirm on this with a BASIS team or try a post in the forum for Adminstration and BASIS.

Problem BD64- Generate Partner Profile

Hello everybody,
After creation the model view in the transaction SCUA i go in the transaction BD64 and i try to generate the partner profile to the child systems but i got an error as below:
Object type US, ID BASIS unknown (please observe upper/lower case)
    Message no. E0624
Diagnosis
Object BASIS of type US is not known in the system.
Procedure
Enter a valid object and check the type.
    Make sure upper case and lower case are used correctly.
Somebody can help me?
Best Regards,
Fábio Karnik Tchobnian

Hi,
your question is not really related to SQL Server but to the CUA. Please post your question in a different forum (Netweaver Administrator maybe) and I am sure you will get answer there.
Sven

Logical system and partner profile configuration

Hi,
I have a SQL server which is defined as a Business system in my landscape. It is sending records to ECC 6.0 which makes it a JDBC to IDOC scenario (inbound IDocs)
First question is do I have to mention a logical system name for the SQL server Business system too ?
Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
Thanks in advance.
Cheers,
S

Hi Sam,
> First question is do I have to mention a logical system name for the SQL server Business system too ?
Yes, In SLD You have to specify logical system name of the SQL server business system while creating SQL system.After importing business system into Integration directory,in Adepter-Specific Identifiers you can see logical system name of SQL server business sytem which you defined in SLD.
> Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
Yes,You have to create Logical system in ECC system for SQL system(Logical system name must be with the same name as logical system name you have given in XI SLD in previous question)
> Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
In WE20 You have to maintain partner profiles for SQL server Logical system
For example: If SQL server Business system name is SQLDEVBS and logical system name is SQLDEVLS
In ECC you have to create logical system as SQLDEVLS and
Partner profiles for SQLDEVLS in WE20.
Please let me know if you have any issues.
Cheers,
JAG

Multiple Logical Systems in Partner Profile for one instance

Can we create multiple Logical Systems in Partner Profile (WE20) for one instance or one System? If it is possible, can we create Logical System with respect to Plant/Country?

I am not quite sure if I understood your problem completley. But let's see...
Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
You can find more information about it in this guide here on SDN:
Link: [High Availability;
More information about High Availability Setups for SAP System can be found here on SDN:
Link: [High Availability]
If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
Hope this helps.
Best regards,
Mathias

Partner Profiles related

Similar Messages

Maybe you are looking for