Set up Partner Profile

I am in the phase of implementing Best practice for data services for data migration using IDOC
When I reach to the phase of Set up Partner Profile
1. In the SAP Easy Access screen, enter transaction code SE38.
2. In Program, enter /SMB99/AIO_IDOC_SETUP and choose the Execute button.
I received the following error
Program /SMB99/AIO_IDOC_SETUP does not exist
Please if anybody face the same problem please respond

Hi,
Check note 1465531. You will have to create a new Z program in the system.
Regards,
Jeroen

Similar Messages

Just one partner profile for SAP XI?!

Hi,
well i have some thoughts concerning configuring the partner profile on sender side.
I have different systems to which e.g. IDocs will be send to. Therefore i was thinking to set one partner profile for each connected system.
But on the other hand it is also possible to just configure one partner profile, e.g. called SAP XI, and seperate the different IDocs inside this partner profile because of different Message-Types of the Outb-parameters, and inside this because of the IDoc-Type.
So what is the most propriate way to solve this, is there a suggestion by SAP?!
thx in advance, Jens

Hey guys,
Just thought I'd add my experiences here.
In one of our implementations we created partner profiles with respect to XI. We had multiple source systems , but the Target ECC team was like, we do not care who sends the data to XI, as far as we are concerned we get data from XI. So we create only one partner profile. We agreed to this and so all Idoc's posting from XI had the XI as the sender partner name. The project went into production and things were fine.
Then comes the next release. And what do we realise, that the same Idoc will not be posted from XI but for different source systems with different formats. The Inbound processing for the idoc was also being changed stating that Idoc from Source system A needs to be processed with this T code and Idoc's from System B with this code. reason was different bsuiness rules across different geographies.
Now, at this juncture we realised in vain that it would have been better had we maintained the partner profiles with respect to the End Systems . having it with respect to XI caused issues in the fact that we are unableto trace out which Idoc belonged to which system.
Since, then we always recommend all partner profiles with respect to End Systems and not with respect to XI. Helps the business also understand how many idoc's were posted for which source system and so on.
Just my 2 cents and experience here. Would love to heard more on this topic as well.
Regards
Bhavesh

Partner profile details for WBI

Hi all
    this is my requirement.we need to send a file from WBI to SAP as IDOC.i want to know about sender details(i.e) sender port ,sender address,partner number.just suggest me about these things
    Thanks in advance

Hi ,
          Please refer the folowing links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
Configurations in R/3 side
1. SM 59 (RFC destinations)
Create a RFC destination on the XI server. The connection type should be R/3 connection. The target host needs to be the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Provide the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
Configurations in XI server.
1. SM59 (RFC destination)
Configure the RFC destination specific to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
TESTING:
WE19 For pushing the idoc in xi through trfc port.
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Assign points if you found helpful
Regards.,
V.Rangarajan

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

IDOC status 30 but partner profile is set to send immediately (04)

Hi guys,
I have a problem with idocs not being sent immediately... The outputs, the EDI partner profiles are all set up correctly...
it is configured to send immediately however, it's not doing so... prior to upgrade to ECC 6.0 it's working fine... now its not...
However, in BD87 thru manual release of IDocs, it is working fine...
Is there any changes to ECC 6.0 for this matter? or is there anything that needs to be set up other than those mentioned above in order for it to work in ECC 6.0?
Thanks a lot!

Mark, have you looked at the OSS notes? By 'IDOC status 30' it finds 300+ notes, this is really a wide-spread issue.
The most recent one is 150202, which actually recommends collecting the IDocs instead of having "send immediately" because it saves the RFC resources. This is not really an ABAP issue, so you might want to discuss this with your Basis admin.
Also, from my experience, even with "mission critical" processes the users, in fact, never feel any real difference between "immediate" and 5-10 min. Sometimes (due to a technical problem, for example) nothing goes on for 30+ min. and no one even notices.

Posting IDocs, partner profile setting

Hello,
I want to ask for advice.
It happens IDoc hangs on R/3 side while requesting data to load them to BW. This IDoc has no error and after manual processing (BD87) data are transfered correctly and IDoc posted. It is message type : RSRQST and it has set up " Trigger by background program" option in Partner profile / inbound parameters.
What could be the reason that IDocs hang without any error?
Addtionally:
what is recommended as IDoc processing option?
is it : Trigger by background program or trigger immediatelly?
Thank you in advance, Peter

Thank you for fast feedback.
I checked notes 561880 , 555229 and 535172 but they point to issues with resources during IDoc processing to application. I am not quite sure if this is my case. I Think my problem occured before the IDoc processing to appliccation.
I suppose if there is a problem with resources the IDoc gets " status 64, "NO RESOURCES, IMMED. PROCESSING NOT POSSIBLE:
However the problem I am referring to is that IDoc gets "Status 64, No filters , No conversion , No version change . If I understand it right this means that IDoc was processed by ALE and waits for further processing to Application. Unfortunately it doesn't start.
any idea what could be the problem? or does it really have something to do with resources?
Thank you,
Peter

How do I set up EDI PArtner Profiles

Hello All,
Can anyone tell me how to set up the EDI partner profiles in ECC 5.0.New to EDI.
Can anyone pass the good documentation on EDI please..
Thanks
Viky

<a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/64/d1b318a28111d3962d00a0c943a141/frameset.htm">Partner Profile</a>

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

Using SYPART01 IDOC for setting partner profiles from external system

We wish to maintain our partner profiles from an external system.
Is there any existing interface for doing this.
It seems that the sypart message is only for output, not input.
Any ideas or suggestions?
Thanks!
Dan

Hello Dan,
Thanks for your post.
I hope the following code helps in future.
http://wiki.sdn.sap.com/wiki/display/Snippets/Copy+partner+profiles+with+SYPART+message+quickly.

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

Partner profile set-up

Hi All,
How we can assign a different vendor as a Good Supplier for a particular vendor. I have checked in main vendor master partner profile not able to find the same.
Thanks
Chandru

Hi CHANDRAMOHAN ,
Please go through the above link :
Partner Function in Vendor master

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.

Generating SRM Partner Profile in SAP R/3 system

Hi,
Please can someone shed some help as to why I get the message below when attempting to Generate SRM Partner Profile in SAP R/3:
"No messages have been defined for the selection conditions in the model"
I have in fact sucessfully generated this in SRM, but get this message when trying to do the same in R/3 backend.In B64, i have also set it to Transfer Idocs Immeditate.
Thank. You.
Pooja.

Hello Pooja
please check you have supplied correct logical system or not
in the modelview
cross check via scc4.
Re: No messages have been defined for the selection conditions in the model
muthu
Edited by: Muthuraman Govindasamy on Oct 3, 2008 2:48 PM

Partner Profile not fnd (file-to-idoc)

Hi,
Idoc in r/3 failed with 56 error. Partner profile not found.
partner profile was set up (between XI logical system and R/3 system) in R/3 server.
Control record of idoc is showing sending system as MDMSBX01 with port SAPXI0. Actually, MDMSBX01 is the source sytem(file server). I can't even find this port SAPXI0 in IDX1. Not sure, how this got picked up.
I was testing the scenario by using "test message" in Integration Engine(RWB) since I do not have access to FTP server. I am sure this is causing to pick up wrong source system(instead of XI server system as source). Please clarify.
Below is XML message from MONI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000011006</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS05</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPXI0</SAP:SNDPOR>
<SAP:SNDPRN>MDMSBX01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPEC0</SAP:RCVPOR>
<SAP:RCVPRN>EC0CLNT100</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2007-04-20</SAP:CREDAT>
<SAP:CRETIM>14:36:52</SAP:CRETIM>
<SAP:ARCKEY>40697C80EF8711DBB286000F203CD31A</SAP:ARCKEY>
</SAP:IDocOutbound>

Hi,
as explained by Ahmad, see the Partner profile os created or not in , R3 system,
At the same time in receiver Idoc adapter select the apply control record from payload checkox .As per moni , the parner profile is in xml, so try to see the partner profile is created in R3 by TcWE21,check for inbound messgae type the said Idoc is existed or not and the corresponding process code is selected or not..
Regards
Chilla

Partner Profile - LS

I have two decentralized system which needs to receive ASN and POs from SAP. Each of these systems consist of 3 plants. How would I set up the Partner profile to group the 3 plants under on each decentralized system?
Would I set up the partner profile with a partner type of Vendor(plant) or is there a way to set up the partner profile as Logical System and somehow group the 3 plants under each logical system?
I have seen a screen in SAP which allows you to put a small bit of ABAP during a partner function call, but I dont remember the transaction.
Any help would be greatly appreciated

you can make it by having two seperate output types defined for each receiving systems.
For example ZNE1 for system 1,ZNE2 for system 2.
Maitain cond. records for the plants.
So based on the plant system proposes the output.
Now you have got the output proposed.
next thing define the two logical system reprsents the receiving systems.
Then use BD64 to define the distribution model whereas you specfiy sendinf system 'YOUR SYSTEM' Receiving system 'LS_RECVSYS1' message type 'ORDERS' and save it.
Then again add another entry Receiving system 'LS_RECVSYS2' and message type 'ORDERS'.
maintain partner profiles for the two logical systems.
specify the output type ZNE1 and application as EF for LS_RECVSYS1.
specify the output type ZNE2 and application as EF for LS_RECVSYS1.
This is done to send out the purchase order.
different output types specified under message control tab makes the system to decide which system should get the outbound IDOC.
So the flow is like,you have the output proposed for 3 Plants,system checks the partner profiles.Then it check for ALE dist. model to get the actual rec. system to send out the IDOC.
Same procedure can be followed for sending out ASN too.
This works .

Set up Partner Profile

Similar Messages

Maybe you are looking for