Partner profiles issue

Hi All,
We are trying to sett the partner profiles for source systems.Able to do RFC connection.But not able to see data.
Thanks
Sidd

hi
are you able to jump from BW to R/3?? through sm59??
are you able to see data in rsa3 of your R/3 system...
If it is ok,you should see the data in bw..
Teja

Similar Messages

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

Partner profile not available.

Dear Folks,
i am doing the scenario JDBC to IDOC. For that i did all the necessary ALE settings and configured the systems. While executing that scenario. In we02, i am getting the error partner profile not available eventhough i configured it. From the error i found that, in technical info, partner number and port are different. And i am getting some Default parnter number and port.
From my observations, i checked the Sender business system and i found that, logical system which was mentioned for this business system is replicating as a default parnter number in the technical info.
please guys i need your valuable suggestions to eradicate this error.
Regards,
Dileep

Hi Mark,
I checked the payload and i am not using header mapping.
I tested the same by doing some modification like, In sender business system, i replaced the default logical system name with which i am using.Then idoc status is changed to status 50. But i am getting the Default port as previously said.
one more thing is , whenever i am getting this partner profile error, it is hitting one of my Company portals. i.e., displaying this partner profile issue in MSS(managerial self service) of HR Portal.
I was little bit confused of why it is hitting the portal?
what would be the key point for their connection?
Please help.
Regards,
Dileep

Issue in Partner Profile config for Outbound IDOC

Hi Experts,
I have requirement like, When ever there will be any change in a Sales Order an Outbound IDOC will get triggered though a output type. This IDOC will save a file in the Application Server.
The Message Type i am using is ORDERS and the Basic Type is ORDERS05.
I have created a Partner Profile also a Receiver Port of type FILE.
I have Assigned Message type in Outbound Parameters.
I have assigned Receiver Port and Basic type under "Outbound Option".
I have Assigned Applications as 'V', Message type as 'Output Type' and Process Code under "Message Control".
When i am changing any Sales Order no IDOC is getting Triggered. I checked the Sales Order>Extras> Output> Header> Edit, the Output type is in Status RED with Message " No Partner Profiles (Message Control) Maintained".
Please guide me if i have missed any configs.
Help me solving this issue.
Thanks in Advance!
Priyabrata

Hi Priyabrata,
please try changing in your partner profile the application from V to V1. Another problem that's often causing the partner profile not to be found are the partner functions that are added automatically by SAP, but sometimes forgotten in the partner profile.
I don't have a SAP system at the moment, but as far as I remember the long text of the message indicates the partner profile parameters that SAP uses for the lookup.
If all of this doesn't help, I'd quickly debug this and see why SAP's not picking up the correct partner profile.
Cheers, harald

ALE issue:No partner profiles (message control) maintained

Hi,gurus:
My ALE scenario is tranferring PO from client 800 to 900 client.
Now the logical system,partner profile，port，rfc，distribution model are created both the sender and receiver side.
In ME21N->MESSAGE, the output type is NEU,and medium is A,partner function is LS,partner is ECCCLNT900.
When I saved the PO,the status is red,and no idoc was generated.
I viewed the processing log,the information is: No partner profiles (message control) maintained.
But my distribution model is sender:ECCCLNT800;receiver:ECCCLNT900;MESSAGE：ORDERS;
The partner profile is ECCCLNT900(LS),and the outbound parameters are ORDERS,SYNCH. For ORDERS,the message control is EF,NEU,ME10.
Have you ever met this issue?
Thanks in advance.

Hi Li,
Please refer this threads...
Re: Message is not proposing automatically
Re: IDoc was saved but cannot or should not be sent
Hope you have to post this thread in ABAP General category..
Regards,
kumar.

File to IDOC - issue with partner profile

I have done File to IDOC scenario and tested it end to end successfully. For same have done all require configuration setting in R/3 like defining logical System and partner profile. And it sends new IDOC successfully in R/3 with status code 50 (IDoc added).
But when I create new logical system and partner profile in R/3 and when I use same logical system in my above mention scenario then my new generate IDOC in R/3 return status code 56 (EDI: Partner profile inbound not available). But same scenario work fine with my earlier partner profile. Here I have done all require changes at adapter level like adapter specific identification and same new logical system I have update in SLD with my business system Logical System Name.

Hi Bhavesh,
Thanks for your reply.
In control record, I checked with sender and receiver partner. In this sender partner is new partner profile which I have created with port details. Receiver partner has logical system name which I have mentioned in my SLD for my receiver business system. But in receiver partner dont have any port details.
But still it has same problem.
-Sunil

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

Issue !!! Partner Profile Creation Using EDI !!!

Hi!
 Can anyone tell me whats the use of Message Code & Message Function for Creating Partner Profiles using EDI
 Transacion WE20 for EDI.
 Thanks.

Hi,
These fields can be used to differentiate between processing of the same message type. You can create several partner profiles using the same message type. By populating these fields, you are able to assign different process codes. Otherwise you are only allowed one entry for the message type.
For example, you need to setup two inbound partner profile for delivery advice. One is dealing with incoming shipment (process code DELS) and the other one dealing with purchasing (process code DESA). Both are using same message type DESADV. If you did not specify message code or message function. They system will allow to setup only one inbound message type for DESADV and not for two entries in inbound partner profile. For this case, you need to populate both the message function fields, for example SHP (Shipment) and PUR (Purchasing).
By doing these, system will allow you to assign different process codes for same message type.
Also these will allow you to split/group the IDocs processing (running parallel).
For example, if you want to post the incoming above message types, you can use standard program RBDAPP01 to process and running parallel by specify message function in selection screen or you can setup different variants to run in the background.
Regards,
Ferry Lianto

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

Partner profile is not getting updated in FSCM.

Hi All,
We are using FSCM for credit management. We have a issue wherein partner profile are not created for a customer.
We created a customer and hwne checked we found that the partner profile is not there for the customer. We are checking the master data but not able to find the exact reason.
Can somebody help me solving this issue.
Regards,
Satish.

Which version of ECC are you using?
In ECC 6.0, you have to activate CVI (Customer Vendor Integration)

Why T-RFC Port canu2019t handle Partner Profile Segment Release Version.

Can TRFC Port handle the segment release of each of the segment if configured in Partner Profile.
As per sap, in Partner Profile, if we maintain the two field "Seg. Release in IDoc Type" and "Segment Application release" to a SAP Release lower than the current release version then all the segment populated by the IDoc adapter should be populated as per the lower release structure.
For test Purpose I have created two IDoc using File Port and TRFC port and for both of then I have maintained the Partner Profile Fields "Seg Release in IDoc Type" and "Segment Application Release" as 46C although the latest release is 701.
In the IDoc there is a custom segment ZE1PMX with two Version Release 46C & 701. 46C is having 7 Fields and 701 is having 9 fields.
Test using TRFC Port: Using TRFC port the IDoc that is getting generated are not having the segment structure of release 46C instead of that it is taking the segment structure of latest release 701 which is having 9 fields.
Test using File Port: Using File port the IDoc that is getting generated are having the segment structure of release 46C instead of latest release 701 which is having 7 fields which is desirable.
I have also done these testing in other SAP release like 700 and found that while saving the partner profile with a lower segment release number it throws an warning message as "Segment definitions missing for release 620/620" and IDocs are not getting generated with a error status Code 2 "Segment E1BPMEPOITEM1 is unknown in Release 620 /". But from release 701 sap allows us to save the Partner Profile without warning and also creates the IDoc without error but the segments takes the latest release structure instead of the release maintained in the Partner Profile.
If any one has already done some investigation on this issue please let me know why there is a difference in TRFC Port and File Port. Is there any other configuration that is missing for T-RFC Port.

Hi Dennis
This forum is focused on [SAP NetWeaver Gateway|http://www.sdn.sap.com/irj/sdn/gateway], i.e. the (relatively) new OData/REST-orientated mechanism to expose ERP data and functions.
You're talking about the ('classic') Gateway i.e. the service that runs on port 33<SYSNR>. As a result, you are better off posting in the forum that covers that Gateway, i.e. [Application Server Infrastructure|SAP NetWeaver Application Server;
The names do make it confusing, for sure.
Good luck!
dj

Getting EDI:Partner profile not available.

Hi,
I am a newbie to SAP XI. As I am doing File to IDOC scenario, I am getting error - EDI:Partner profile not available.
My Scenario details:
1. Created RFC Destination, RFC port, logical System and Partner profile in both Sender (XI) as well as Receiver(SAP R/3) systems.
2. Created SWCV, Technical sys, Business Systems in SLD. I used the Logical system created (for SAP R/3) on XI system in my business system.
3. Created Data type, Message type, Message interface, Message Mapping and Interface mapping in Integration Repository and activated them.
4. Imported IDOC from SAP r/3 system during Namespace creation and used it for mapping.
5. used Integration Directory wizard to create Communication channels, Sender & Receiver agreements, Receiver Determination, Interface Determination.
6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.
7. Activated all Standard Change list items.
The file for the above Scenario has been picked up amd i am getting "Chequered Flag" on both ends in "SXMB_MONI" monitor. When i change over to SAP R/3 to check idocs created (i.e., T.code - we05) my scenario idoc status is 56 and it says.. Status; Idoc with errors added.
I have gone through many of the forum suggestions and blogs regarding this issue, but still not able to resolve my problem.
can somebody suggest me solution please.
Thanks,
Vijay.

Hi,
6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.
>>>Check this for Reciever Business System.. not for Sender system..
BTW, if you get chequered flag in XI, then idoc data is sent from XI. Can you check all the data from XI is populated in the idoc structure in SAP R/3 in we05...by clicking each segment.. if so, then there is no problem from XI..
check WE20 ..partner profile configuration in R/3 also check inbound parameters are given
Regards,
Moorthy

Partner profile value for XI system

I got a outbound message with partner profile value as
<SAP:SNDPOR>XIDEV</SAP:SNDPOR>
<SAP:SNDPRN>XiALE01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
Where do I go and change the SNDPRN value in SLD? or is it SLD I change it. SAP R3 is looking for sender partner profile in caps. How to change this value in XI
thanks

Hi,
Please update few things.
1. Since it is an outbound from XI into another R/3 machine, I would first suggest you to check IDOC posted in R/3 which has an error message tagged to it. This is applicable only when Message went from XI into R/3 and we see an error in the SXMB_MONI as RFC destination not found etc.,.
In such a case, IDOC error message with 53/51 etc, will post an error message like "SENDER NOT IDENTIFIED". This SENDER and RECEIVERs can be seen in the CONTROL RECORD of the IDOC.
From R/3, use transaction WE02/WE05 and locate your IDOC (normally in the OUTBOUND folder on left, look at last few messages which have RED TRAFFIC SIGNAL and match the partners).
To resolve this, create the RFC PORT first. XIDEV using WE21 referring to your XI client. The prerequisite for this is to have a RFC destination already created to port XI and a logical system (BD54 transaction).
Create a Logical System (Business Partner) of type LS using WE20 and (Logical system you have created or identified in BD54) should be configured as you want.
This should resolve your issue.
2. If the issue is with XI and message is not seen in R/3, make sure you have assigned proper logical system in the SLD for your technical landscape. If this is pointing to a different logical system, then probaboy you may want to change to suitable logical system.
Suggest you to look for the definitions using SM59 and IDX1 in R/3.
Hope this answers, please let us know your findings.
Thanks,
Srini.

Partner Profile vanishes in BW system

Hi All,
We are facing a recurring issue which happens in BW QA system after we refresh is from the BW production system.
After about a week or so after the refresh, the data loads halt in the BW QA system and the BW team gets an error "EDI partner profile not available".
After i checked, i found that the logical system name entry for the EDW QA system (i.e. self system entry) is missing from the table EDPP1 and also from transaction WE20.
I re-created it in WE20 and the entry automatically got created in EDPP1 table.
My question is : I suspect that some job or application program is deleting this entry. We checked the background jobs but no luck.
How do i resolve this error. The client has come up with this question and he wants an answer as to why this
entry is being automatically.
Can you please help?
Regards,
Hari Kishan

Hi,
See the following SAP Notes:
SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
SAP Note 325470 - Activities after client copy in BW source systems
SAP Note 325525 - Copying and renaming systems in a BW environment
SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
SAP Note 1333302 - Special procedure for BW system copy
SAP Note 996238 - Dump 'RFC connection error' after BW system copy
Search for PDF in SDN
How Tou2026System Copy in SAP Business Intelligence System Landscapes
Thanks
Reddy

Partner profile and partner number in output of order/invoice.

Hello Experts,
I want to know how system pick partner profile from output type triggered in sales order/invoice??
I could see partner profile is different from partner number exist in output triggered in sales order/invoice.
I want to know the triggering point of idoc from SO/invoice.
Thanks

The phrase "ouptut goes to partner" indicates that the partner will be recipient of the output type. E.g., ship-to partner will be the recipient of the delivery and the delivery note.
The use of an output partner in the output condition record is used to control the output device used in the output determination - a completely separate issue.
Unless you are (e.g.) using different printers for outputs which will be sent to different partners, you would likely be better off using a more generic access for your output condition records.
HTH
James

Partner profiles issue

Similar Messages

Maybe you are looking for