Roles/profiles for IDoc exchange between ECC & PI

Hi guys,
I'm using a IDoc->PI->File scenario and otherwise and I need to set up a communication user between ECC and PI for this IDoc exchange, but I don't want to use sap_all. Can you please tell which roles/profile to assign so the IDoc exchange would work?
Thank you,
Olian

http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
From Note: 837595
Authorization object S_RFC
Field name RFC_TYPE value FUGR
Field name RFC_NAME value EDIMEXT, SDTX
Field name ACTVT    value 16
Authorization object S_IDOCDEFT
Field name ACTVT   value 03
Field name EDI_CIM value ' '
Field name EDI_DOC value TXTRAW01
Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
Field name ACTVT      value 03
Field name DICBERCLS value

Similar Messages

Wireless application for files exchange between two computers,pls Help

Hi everyone,
I need your help,pls.I have to make a wireless application for files exchange between two computers,but I don't know where to start from.I guess that this should be a client/server and after establishing a connection I have to be able to exchange files between each others.Please help me

the wireless connection does not matter.
This is a socket (client server as you said) same way.
look out:
http://java.sun.com/docs/books/tutorial/networking/index.html
cya

Roles/Profiles for ALEREMOTE

hi all,
can anyone let me know all the Roles/Profiles required for the User ALEREMOTE in a production system.
I understad that the roles sap_all, sap_new , s_bi-wx_rfc and s_bi-whm_rfc can be used in the development and the Quality systems but am told that the roles SAP_ALL & SAP_NEW are not supposed to be used for ALEREMOTE in the Production systems as it would give all authorizations to all the users.
so, could anyone kindly let me know the various roles/profiles that need to be assigned to the user ALEREMOTE keeping in mind that SAP_ALL & SAP_NEW are not allowed and at the same time all the transactions w.r.t BW3.5 should go through successfully.
kindly revert back at the earliest as we are in the process of going to the BW Production.
Thanks & Regards
Manicks

hi Manicks,
check oss note 150315-BW-Authorizations for Remote-User in BW and OLTP. hope this helps.
Symptom
1) The ALE user fails security in the BW side
2) Missing authorizations when executing Customizing of extractors
3) No IDocs could be sent to the SAP-BW using RFC.
4) Automatic source system connection failes with error R3220: No RFC-Parameters in source system defined
5) When collecting content in BW, warning message RSAOLTP035 comes up
Other terms
Authorizations, SAP_ALL, S_BI-WX_RFC, S_BI-WHM_RFC, S_RS_ALL, ALEREMOTE, BWREMOTE, RSAOLTP 553, RSAOLTP553
Reason and Prerequisites
a) In the BW there exist two user:
 i) a human administrator, using S_RS_ALL
 ii) a user called BWREMOTE (or similar), used to receive the data from the OLTP, using S_BI-WHM_RFC
b) In the OLTP there exist also two user:
 i) a human administrator, needing authorizations to create users and RFC-destinations.
 ii) a user called ALEREMOTE (or similar), used to ...
 1) ... connect the OLTP to the BW
 2) ... extract the data
 3) ... send the data to the BW
 4) ... show monitoring dialogs for tasks 1 to 4, the profile S_BI-WX_RFC is used (however does
not suffice on some points since some authorizations are
missing in the delivered profile)
 5) ... make customizing of OLTP extractors
 for this, additionally the authorizations to execute IMG-functionality, to execute Transaction SBIW and to maintain the applications, which shall be customized, must be given during the customizing functionality is used.
Solution
1) The profile S_RS_ALL resp. S_BI-WHM_RFC must contain (at least) the following authorizations:
Profile
2) The referred functionality is b) i) 5), thus
 the authorizations to execute IMG-functionality,
 to execute Transaction SBIW and to
 maintain the applications, which shall be customized,
 must be temporarily given to ALEREMOTE, if you want to execute the
 functionality from BW-side. The permissions for executing the
 customizing is not included in the profile S_BI-WX_RFC, since
 this is a critcal functionality.
 However there is the possibility to execute the customizing
 in the OLTP by a human administrator by hand, using Transaction
 SBIW.
3), 4) For sending the Idocs and reading RFC-destinations
 the profile S_BI-WX_RFC is incomplete.
 Please check, if the following authorizations are included:
Profile
--- S_BI-WX_RFC <PRO> Business Information Warehouse, RFC User
-- B_ALE_ALL <PRO> All authorizations for ALE/EDI
-- S_APPL_LOG_A <PRO> Application log: All
-- S_BTCH_ADM <PRO> BC: Batch - Processing authorization
-- S_BW_RFC <PRO> BW: Authorization Profile: Other
-- See above, same sub-profile as in S_BI-WHM_RFC
 --- S_IDOC_ALL <PRO> All authorizations for IDoc functions
- BW AddOn BW-BCT 1.2B:
These authorizations have been delivered with BW AddOn Patch 2 (see 158489 for the AddOn Patch information), except release 45B. For 45B, the authorizations are delivered with BW AddOn Patch 1.
- PI2000.1:
For 4.6B and 4.6C due to delivery errors, this profile also is incorrect. Please transport it from the BW into the Oltp (it is the same in any system and release).
- PI2000.2:
For 4.6C due to delivery errors, this profile also is incorrect.
Please transport it from the BW into the OLTP (it is the same
in any system and release).
- PI2001.2:
For 4.6C due to delivery errors, this profile also is incorrect.
Please transport it from the BW into the OLTP (it is the same in any system and release).
Alternatively, import the sapserv* transport BRSK002208 under the directory
general\R3server\abap\note.0150315 into your OLTP-System.
For help on the sapserv* transport refer to Note 13719.
5) If you have PI-Basis 2005.1 in your source system, you need to attach role SAP_RO_BCTRA to your user in the source system. Otherwise, the functionality mentioned in the message is not available. The system continues to function as before, you may ignore the warning.

Solution Manager 4.0 Solution Monitoring User -Roles-Profiles for Satellite

Hi All,
I have installed Solution Manager 4.0 (OS -Linux ,Database - DB2) .
Now i need to connect solution manager to the R/3 4.6C
Satellite Systems (DEV, QAS ,PRD) for Solution Monitoring
and Service level Reporting .
I have read the configuration guide , but unable to get clear idea .
1) what users (alos type of user -Dialog , Service, Communication etc) do i need create in DEV , and Test in QAS for solution Monitoring .
2) what exact roles /profiles need to be assigned to these users in satellite systems .
3) what users/roles /profiles needs to be done in SOLMAN system
i have applied all the required plug ins and support packs
in satellite systems and solman 40 ..
Please advice . Your response will be a great help for me .
Satish

Hello Satish,
Just clarify, if u have meant connecting the satellite systems for EWA reports to be precise. Early watch Reports. If its is the case, then repond so that i can putin my inputs which may be helpful for you in this config.
Rgds,
Sri

Partner Profile for IDOC - configuration

Hi..
I have an inbound IDOC TPSSHT01, which has been extended by adding a Z segment.. But I keep getting an error message.. The IDOC is created with status 56 and the message says "No inbound profile found".. I have configured the Inbound profile to include the message type 'SHIP' in WE20 and also added the message type in WE57 and WE82... Do i need to do any further settings?
Thanks
Rishi

hI,
Please use transaction code WE20 to generate inbound partner profile
Goto WE20 transaction of the client 200 where you are posting the idoc and maintain the partner profile for the inbound type for the idoc type and the corresponding message type of SHIP. This is because you would have maintained it as the outbound parameter from client 100. But at the receiver end also you need to configure the same.
Status 56 comes up when the partner profile for the idoc type is not maintained. Once its maintained, the idocs which you post will go into 53 if its successfully processed and to 51 if its failing due to any inbound processing program validation
*Reward points
Regards

Idoc exchange between SAP R/3 4.6C and AS/400

Hi
We need to develop an interface between SAP 4.6C and AS/400 Warehouse System. The users are totally new to idoc concept. I need some information where I can get information on how idoc can be created from by AS/400 warehouse persons ? What kind of middleware is needed, etc. ?
Hopefully in simple terms since the users are in South Korea.
Thanks!

Hi Dhanesh,
You can use SAP XI (Exchange Infrastructure) as a middleware to establish
the interface between SAP R/3 & AS/400.
The output of an AS/400 can be of any format, but that will be converted by
SAP XI into IDoc & will post the same in SAP R/3.
For information on XI, check the following PDF:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1ebea490-0201-0010-faad-a32dd753d009
http://help.sap.com/saphelp_nw2004s/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm
best regards,
Thangesh

Need role/profile for ALE system user

I have created a system user and assigned it to the necessary RFCs in our DEV system. The RFCs are used to ALE data between our DEV, QAS, and PRD systems. If I assign profile B_ALE_ALL to the user in the receiving system I do not get IDOCS created in our QAS system. If I assign SAP_ALL to the user I do get IDOC's created in QAS. Can anybody recommend another role to assign. Or a method to troubleshoot this authorization error. I want to limit this system user in the receiving system to creation of IDOCs only.
Thanks in Advance, Jay

Hi,
Then I recommend to give sap_all and trace the user in QAS system. Once the data transfers are complete, please anaylyze the trace and see what authorizations it requires. Now build a role with this authorizaiton and remove sap_all.
Since you are transferring applicaiton data, the programs might also check that access as well.
Regards,
Gowrinadh

IDOC exchange between different businesses

Hello.
I have the following 2 scenarios to design:
1.I need to exchange an IDOC from an SAP system in my landscape (I'll refer to it as MySap from now on), to an external SAP system (I'll refer to as EXT from now on).
2. I need to exchange an IDOC from EXT to MySap.
In both scenarios - the IDOC invloved has a user defined extension.
I also have a PI system in my landscape. while for now the external system have no PI of her own.
for each of the scenarios I would like to know the benefits of the external party using a PI of thier own.
for the 1st scenario:
1. MySap -> PI -> EXT
2. MySap -> PI -> EXT PI -> EXT
for the 2st scenario:
1. EXT -> PI -> MySap
2. EXT -> EXT PI -> PI -> MySap
What is the best way to desing each of this options?
Should I be using the IDOC adapter when sending the IDOC to the external system? (EXT PI or EXT)
How should I identify the structure of the external IDOC? should I develop it the same way in MySap? should I somehow have the XSD of the structure (how can someone export an XSD of his IDOC without a PI?)
Any suggestion will be welocme.
Thanks.

ii you wanted to transfer data between two SAP systems then you can directly send it through ALE IDOC/RFC in that case you have to check the firewall setup in your landscape...in such case but will not have good monitoring and message tracing capability....
with PI you can have monitoring and message tracing as well as all the capability and features of PI if you go through PI in between MySap -> PI -> EXT.
You have three options to integrate with SAP system through PI - IDOC/RFC/Proxy - if for your business case you have a std IDOC/RFC go with that otherwise go for proxy.
thanks
chirag

Pick Up file and remove roles/profiles for the specified ID's

I am wondering if the following would be possible.
I want to dump a csv file containing user ID's that are no longer required on a daily basis on a server. Would it be possible to write a program to go out and retrieve that file and where ever there is a match on ID's, remove all roles and profiles associated with that user and change the user group?
Sounds very simple from a theoretical standpoint but I'm not sure of it's truely feasibility. I'm not looking for any coding, just to know whether it could be done. Any help would be great.

Hi Martin,
Very true, but infrastructure folks might not want to manage certificates and OS users (good tip for Chris to check on...)
Open file shares are out there "in the wild" - which is what I wanted to warn against (in addition to the application authorizations within SAP to run this "interface"...
If it is running as a job, then a check on system field sy-batch = 'X' is usefull, but blunt only for the online execution.
Personally I have used an (inaccessible) timestamp execution scheme for such things in DB tables not accessibly to the application transactions before. Have not been able to hack it myself, but tried hard..
But if the file shares are open or the password is in clear text (in a script, .properties type file, ABAP text, network traffic, etc) then I would not class it as secure.
Such "identity management" stuff, particularly when you want to intergrate it with HR events, is best taken care of centrally in an "identity store" which you can secure and encryot etc centrally.
Local batch jobs accessing servers and registering / starting external programs and vise-versa to transfer files etc is decentral spagetti coding and security nightmare... ;-(
Cheers,
Julius

Which role, profile for monitoring adapter & messages in Runtime Workbench?

Hi guys,
let mi pls know, which one is needed.
Thanx!
Olian

Hi Olian,
Check this help file on Monitoring:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/08438c77-0501-0010-50a0-e39fe8fa0446
Regards,
Subhasha Ranjan

Settings for IDoc Processing Maintain Partner Profile Manually

Hi Everybody,
I just wanted to maintain a partner profile for IDoc Outbound Processing in CRM7.0. The Partner Type is LS (Logical System).
Now, when I'm creating an Outbound Parameter and want to save, I get an Error Message that the field package size must be > 0.
The problem is, that there is no field Package Size. In older systems there is such a field under the field receiver port.
Anyone any idea where is the missing field or another solution.
Thanks and regards,
Sebastian
PROBLEM SOLVED !!
When you get the error message, press enter several times and the field appears. Incredible.... but true.
Edited by: Sebastian Wilhelm on Sep 3, 2009 4:06 PM

Hi,
Steps to do ALE Configuration with respect to IDOC:
Configuration in R/3:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using we21 and refer the port to the created RFC dest in above Step.
3. Create a Logical System using Transaction BD54.
4. Create a partner profile using transaction WE20.
Also need to configure in XI:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using Transaction IDX1 and refer the port to the created RFC dest in above Step.
3. The port has to be displayed in the IDX2 transaction and we should be able to view the idocs which we imported through integration repository otherwise we have to manually import the idocs from IDX2 using the port created above
Also refer to the link below for further details:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Regards,
Nithiyanandam

Best communication between ECC and PI

Hi All
SAP is planning to adapt Enterprise Service Architecture (ESA) in the journey towards Service Oriented Architecture (SOA).
We are working on new implementation project. We have many asynchrounous scenarios. We would like to configure acknowledgements and also like to handle errors effectively.
Could you please suggest which communication between ECC and PI is preferrable?
(Webservices, IDoc, BAPI or RFC)
Thanks
Sai

IDoc, BAPI , rfc - all can be used for seamless communication between ECC and PI. It is totallu dependant on the application and way information is exchanged. For master and transactional data idoc are prefered as for the acknowledgements supported by it. Not sure how effeciently we can handle system and appl ack incase of bapi/rfc. but at the same time idoc will be a drawback for sync comunication where rfc/bapi is preferd. It is SOA or ESA the concepts build in SAP are targeted to serve the enterprise needs where idoc,bapi/rfc are used for servicing the business unit objectives

ALE Settings for IDOC

Hi,
For configuration of IDOC adapter
1) we need to create RFC Desination both XI System and R3 System.For port creation if v given same port name in both XI system and R3 system it will work or not ?
2) On Receiver SAP system, we need to configure the logical system normally for XI system, were v can find logical system of XI System.
3) Can RFC Destination b same on both systems( R3 system, XI System)
Regards,
Praveen

Hi
The following configurations are needed for Idoc scenarios
1) ECC Configuration : a) Create RFC connections from ECC to XI in SM59. rfc connection name should be target XI logical system name . BD54 or SALE are the tcodes for checking the logical system for respective client.
                                   b) Create port in we21 & provide the above RFC destination.
                                   c) Now Create Partner Profile in we20 ...partner profile name should be target logical system name.
                                        assign the outbound parameters with receiver port created in we21.
2) XI Configuration : a) Create a RFC connection for XI to ECC ...rfc name should be target logical system name(ecc).
                                  b) Create port in IDX1...it should be SAPXXX..where XXX is the ecc system id.
                                  c) Import the idoc metadata in IDX2.
For Outbound idocs generate the model view in BD64.
Regards
Abhijit

Why thet gave option for idoc in bw

hi friends,
why they gave option idoc (data transfer method ) in bw. what is the use. we have psa, again why we need idoc.
Thanking u
suneel.

IDOC (Intermediate Document)
IDOC is SAPs standard format for electronic data interchange between systems. IDOCs can be used in the following business scenarios:
- Application link enabling (ALE). Communication between logical systems; logical systems can be SAP R/3, R/2, or non-SAP systems.
- Electronic data interchange (EDI). Communication between an SAP R/3 or R/2 system and a non-SAP system
In SAP BW, an IDOC is a data container for data exchange between SAP systems or between SAP systems and external systems based on the EDI interface.
SAP RESTRICTIONS
IDOCs support limited file size (1,000 bytes).
Data cannot be loaded to PSA using IDOCs (ALE).
OPTIMIZATION
Queries and Data Staging
You should leverage PSA (and ODS) to store detailed data rather than in the InfoCube as it may contribute considerably to the increase in the query (keep detailed data out of the InfoCube) and system performance (due to higher throughput during data load since PSA uses TRFC rather than IDOC).
Regards
Naga

What are the roles/profiles required in solman and satilite system.....

Hi All,
What are the list of roles/profiles (for SOLMAN and Satellite system) required to create logical instance etc... for monitoring and tasks.
Regards.
kumar

Hello Kumar,
please have a look at the Configuration Guide for SolMan on the SAP Marketplace. ALso for information on required documentation, see SAP Note 1088980.
Best regards,
Annett

Roles/profiles for IDoc exchange between ECC & PI

Similar Messages

Maybe you are looking for