IDCO's Struck in TRFC Monitor

Hi All,
I am extracting data from R/3 to BW,
While Extracting time some IDOC's are not processed in to BW system,these are struck in TRFC Monitor(SM58).
These Idoc's we can execute manually one by one,
But is it possible to execute the All IDOC's at a single time is there any program to execute all IDOC's single time
Note : All Idoc's related to only One data source

Hi,
Please check the below programs
tRFC Tools
· RSARFCRD: tRFC Monitor (transaction SM58)
· RSARFCSE: Restart an LUW (background job)
· RSARFCEX: Restart tRFC LUWs (background job)
· RSQOWKEX: Restart QOUT qRFC LUWs
· RSQIWKEX: Restart QIN qRFC LUWs
· RSARFCSE: Delete an LUW (background job)
· RSARFCER: Delete various LUWs
Also check the link below:
http://help.sap.com/saphelp_nw04s/helpdata/en/25/bcfa40badbf46fe10000000a1550b0/content.htm
-Vikram

Similar Messages

TRFC Monitor in R/3 Means?

Hello All
What do u mean by TRFC monitor in r/3 side?how to do it and what is the Tcode for that?
Pl let me know
regards
balaji

hello BI Project "GUY"
thanks for your immediate info given.
why v need to check this "TRFC" and "QRFC"? in SMQA and CFS2?how to analyze here?
can u elaborate me the reason behind this?
Many Thanks
balaji

SM58 TRFC Monitoring

Hi,
I have few messages in SM58. I need to look into those. When i select the message and click Execute LUW or Debug LUW, I get following message
Funtion Module Does not exist or exception reaised.
I looked into function module it is RFC enabled and commit work is also present at the end of the code in FM. Please suggest me the way to check the message.
Thanks & Regards,
Sadhna Achhra.

Thanks for your prompt reply.
I checked it in SE91 but i just see the message, no more information is available. It is a system message.
Regards,
Sadhna

Message got struck in hold status in message monitoring.

Hi SDNers,
             I am doing Idoc to File scenario. I triggered an Idoc and it is successfully processed in XI and got struck in message monitoring with hold status.
             After repetetive attempts of restarting the message, still it is in hold status.
             Even if I tried to cancel the message, it is not cancelling as it is in hold status.
            Can anybody please help how to process the message or can anybody explain how to cancel the message from message monitoring, which is in hold status.
Regards,
Jayaram.G

Hi,
If the message that has not yet been delivered is not in error state, the problem cause is probably that the message is blocked in the QRFC queues of the Integration Engine.
Check queue status
Call the Integration Server and call transaction SMQR in the sender and receiver Integration Engine in the corresponding system client.
Check the status of the scheduler and the status of the XBQ* and XBT* queues:
u25CF     Inbound qQueues
XBTI* (ExactlyOnce)
XBQI* (ExactlyOnceInOrder)
u25CF     Outbound queues
XBTO* (ExactlyOnce)
XBQO* (ExactlyOnceInOrder)
u25CF     Acknowledgment queues
XBTB* (ExactlyOnce)
XBQB* (ExactlyOnceInOrder)
u25CF     Large message queue
XBTL* (ExactlyOnce)
If the scheduler has the status Waiting, it is waiting for free work processes. This is why delays occur when XML messages are processed.
If not all necessary queues are registered, you can search for queues with the name prefix above using transaction SMQ2. Use transaction SXMB_ADM to register the queues in this case.

TRFC problem in R3

Hi experts,
All my my jobs are struck in tRFC status text says Transaction Recorded. if i execute LUW for IDOC_INBOUND_ASYNCHRONOUS
function module manually, then all jobs are extracting the data to BW. This has been happening for the last 3 days. I am excecuting manually one by one (in tRFC-R/3) for the function module.
Can please anybody suggest solution clearly to fix this problem . It would be great help from you guys.
Thanks in advance
RJ

Hi Roshan,
I dont know, much about this but, after any TRFC call is made through an RFC function module, COMMIT WORK should be done after the function module.
I think this is a very old question.
Thanks & Regards,
Poorna.

Idoc trfc processing very slow

Hello,
I am troubleshooting slow processing of idocs in an Xi test system.
idocs are being processed at a rate of betwen 40 / 60 per hour so at the current rate there will stil be another 3 days (approx) until the queue is cleared.
In SMQS on the Xi (source) system the specific idoc destination is set-up as follows: -
Clt - 10
Destination - R2RREG100
Type - R
W/o tRFC -
Max.Conn. - 10
Max. Runtime - 60
Status - WAITING
Act.Conn - 5
Host ID - ax2t003a_X2T_43
The RFC connection between the two systems has been tested successfully.
Selecting TRFC Monitor and there are still over 3000 rows similar to the following (was over 7000 when first checked)
Caller - PIAFUSER
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - R2RREG100
Date - 15.12.2011
Time - 12:38:22
Status Text - Transaction recorded
Transaction ID - 8218046C00014EC9DE911C9B
Host - ax2t003a
Tctn
Program - SAPMSSY1
Cln - 10
Rpts - 30
I am told by the application team that processing 7000+ idocs is not a large amount for this system
The Xi (source) system and the R3 destination system have both been restarted to clear memory etc but this has not improved speed of processing.
I presume the problem was caused by trying to process too many idocs at once through the Xi system as mentioned in SAP Note 1548446.
I have read SAP Note 1483757 and checked ST03n last minute load on RFC table in the R3 destination system -
Task Type Name - RFC
#Sequential Read - 4,782,264
T Seq Read - 1,157
Avg Seq Read - 0.2
#Accesses -      13,515,579
T Time - 204
Avg T - 0.0
#Changes - 54,206
T Changes - 63
Avg Changes - 1.2
Calls - 18,352,049
Avg Time - 0.1
#Reads - 1,828,651
#DB Recs- 109,376
#Records - 7,687,467
#Calls - 0
T Time - 0.0
Avg Time - 0.0
Last minute load Table Statistics for the destination system ARFCRSTATE table shows the following :
Table Name - ARFCRSTATE
Records -      1,822
Modifiable - 226
records - 0
Sequential Reads - 1,596
T Access - 1
In accordance with the note I tried setting the following on the detaination system but did not see any improvement in processing speed so have now removed the parameter and scheduling of the report.
    1. Set the profile parameter abap/arfcrstate_col_delete to 'X' on the default profile of the destination system.
    2. Periodically schedule the RSTRFCEU batch job in intervals of 5 minutes, in the destination system.
Q1 -after setting 'abap/arfcrstate_col_delete' I did not restart the R3 system. Is a restart required for this to take effect?
Q2 - What else should I check to identify why idocs are being processed so slowly ?
Q3 - Is there anything else I could change to speed up processing ?
Many thanks,

Many thanks jbagga for your reply.
My issue was resolved by SAP who suggested changing the processing mode for message type in WE20 on the receiver system from "Trigger Immediately" to "Trigger by background program".
With the processing mode set to "Trigger Immedaitely" the sender system calls the receiver, the idoc is stored on the dateabase and the application processing was carried out in the same LUW. As a result of this the send must wait until the application finishes processing the messages before it can anything else.
The processing mode was changed to "Trigger by background program" which decoupled the IDoc transfer from the IDoc application processing, performance immediately improved in the XI (sender) system and cleared the queue.
Regards,

Error in tRFC

Hi All,
I am loading delta (daily) from three datasources 2LIS_12_VCITM, 2LIS_11_VASCL and 2LIS_11_V_ITM.
Data in RSA7 is not giving any issue but in tRFC monitor (SM58)we are getting red entries specifying that
"Function module "/BI0/QI2LIS_11_V_ITM0003" not found"
"Function module "/BI0/QI2LIS_11_VASCL0001" not found"
"Function module "/BI0/QI2LIS_12_VCITM0002" not found"
These entries are repeating frequently.
The jobs at BW side are success but as an impact we are missing some data in BW side(InfoCube)
can any body help me how to fix this issue?
thanx
Rama

Hi Ram ,
if u could load first the master data & then load transactional data one after other and not in parallel your problem will be solved .
Cheers!

Erraneous tRFC entries in R3 source when loading to APO production

Hi All,
I am loading delta (daily) from three datasources 2LIS_12_VCITM, 2LIS_11_VASCL and 2LIS_11_V_ITM.
Data in RSA7 is not giving any issue but in tRFC monitor (SM58)we are getting red entries specifying that
"Function module "/BI0/QI2LIS_11_V_ITM0003" not found"
"Function module "/BI0/QI2LIS_11_VASCL0001" not found"
"Function module "/BI0/QI2LIS_12_VCITM0002" not found"
These entries are repeating frequently.
The jobs at BW side are success but as an impact we are missing some data in BW side(InfoCube)
can any body help me how to fix this issue?
thanx
Rama

Rama,
RFC Monitor does not give much details on the error. Look in ST22 and SM21 to see what is happening.
Viren

Request Status Differs in RSMO and Data target

Hi,
I have a master data full load . it strucked in trfc and i cleared it manually in sm58.
The request in RSMO turns to Green automatically,but the datatarget in status tab it shows in red.
Why is this behavior and how to rectify it
Thanks
Bala

Hi,
As the dataload did not get complete because of data getting stuck in SM58, the datatarget monitor would get changed to red automatically once the expiry time for dataload completion is reached.
After this, you would have cleared the SM58 by executing LUWs in it. Because of it, RSMO would be showing green whereas datatarget is still red.
Just check in the datatarget monitor whether any data has got loaded. If yes, then turn the status manually to green and activate the dataload. It would not give any issues.

Common issues with BW environment

Hello Experts,
could you please mention all teh common issues faced in BW environment with the solution available.
I have many issues and I wante dto know whether all teh teams face the same.
This would a good oppurtunity to have everything in one thread.
Thanks and regards
meps

Hi,
We will have somany issues plz check some of them
1. DTP Failure
Select the step-> right click and select “Display Message”-> there we will get the message which gives the reason for ABEND.
A DTP can failure due to following reasons, in such case we can go for restarting the job.
System Exception Error
Request Locked
ABAP Run time error.
Duplicate records
Erroneous Records from PSA.
Duplicate records:            In case of duplication in the records, we can find it in the error message along with the Info Provider’s name. Before restarting the job after deleting the bad DTP request, we have to handle the duplicate records. Go to the info provider -> DTP step -> Update tab -> check handle duplicate records -> activate -> Execute DTP. After successful competition of the job uncheck the Handle Duplicate records option and activate. DTP Log Run:
If a DTP is taking log time than the regular run time without having the back ground job, then we have to turn the status of the DTP into Red and then delete the DTP bad request (If any), repeat the step or restart the job.
Before restarting the Job/ repeating the DTP step, make sure about the reason for failure.
If the failure is due to “Space Issue” in the F fact table, engage the DBA team and also BASIS team and explain them the issue. Table size needs to be increased before performing any action in BW. It’ll be done by DBA Team. After increasing the space in the F fact table we can restart the job.
Erroneous Records from PSA:      When ever a DTP fails because of erroneous records while fetching the data from PSA to Data Target, in such cases data needs to be changed in the ECC. If it is not possible, then after getting the approval from the business, we can edit the Erroneous records in PSA and then we have to run the DTP. Go to PSA -> select request -> select error records -> edit the records and save.Then run the DTP. 2.      INFO PACKAGE FAILURE: The following are the reasons for Info Pack failure.
Source System Connection failure
tRFC/IDOC failure
Communication Issues
Processing the IDOC Manually in BI
Check the source system connection with the help of SAP BASIS, if it is not fine ask them to rebuild the connection. After that restart the job (Info Pack).
Go to RSA1 -> select source system -> System -> Connection check.
In case of any failed tRFC’s/IDOC’s, the error message will be like “Error in writing the partition number DP2” or “Caller 01, 02 errors”. In such case reprocess the tRFC/IDOC with the help of SAP BASIS, and then job will finish successfully.
If the data is loading from the source system to DSO directly, then delete the bad request in the PSA table, then restart the job
Info Pack Long Run: If an info pack is running long, then check whether the job is finished at source system or not. If it is finished, then check whether any tRFC/IDOC struck/Failed with the help of SAP BASIS. Even after reprocessing the tRFC, if the job is in yellow status then turn the status into “Red”. Now restart / repeat the step. After completion of the job force complete.
Before turning the status to Red/Green, make sure whether the load is of Full/Delta and also the time stamp is properly verified.
Time Stamp Verification:
Select Info Package-> Process Monitor -> Header -> Select Request -> Go to source System (Header->Source System) -> Sm37-> give the request and check the status of the request in the source system -> If it is in active, then we have to check whether there any struck/failed tRFC’s/IDOC’s If the request is in Cancelled status in Source system -> Check the Info Pack status in BW system -> If IP status is also in failed state/cancelled state -> Check the data load type (FULL or DELTA) -> if the status is full then we can turn the Info Package status red and then we can repeat/restart the Info package/job. -> If the load is of Delta type then we have to go RSA7 in source system-> (Compare the last updated time in Source System SM37 back ground job)) Check the time stamp -> If the time stamp in RSA7 is matching then turn the Info Package status to Red -> Restart the job. It’ll fetch the data in the next iterationIf the time stamp is not updated in RSA7 -> Turn the status into Green -> Restart the job. It’ll fetch the data in the next iteration.
Source System
BW System
Source System RSA7
Source System SM37
Action
I/P Status RED(Cancelled)
I/P Status (Active)
Time stamp matching with SM37 last updated time
Time stamp matching with RSA7 time stamp
Turn the I/P Status into Red and Restart the Job
I/P Status RED(Cancelled)
I/P Status (Cancelled)
Time stamp matching with SM37 last updated time
Time stamp matching with RSA7 time stamp
Turn the I/P Status into Red and Restart the Job
I/P Status RED(Cancelled)
I/P Status (Active)
Time stamp is not matching with SM37 last updated time
Time stamp is not matching with RSA7 time stamp
Turn the I/P status into Green and Restart the job
I/P Status RED(Cancelled)
I/P Status (Cancelled)
Time stamp is not matching with SM37 last updated time
Time stamp is not matching with RSA7 time stamp
Turn the I/P status into Green and Restart the job
Processing the IDOC Manually in BI:
When there is an IDOC which is stuck in the BW and successfully completed the background job in the source system, in such cases we can process the IDOC manually in the BW. Go to Info Package -> Process Monitor -> Details -> select the IDOC which is in yellow status(stuck) -> Right click -> Process the IDOC manually -> it’ll take some time to get processed.******Make sure that we can process the IDOC in BW only when the back ground job is completed in the source system and stuck in the BW only.   3.      DSO Activation Failure: When there is a failure in DSO activation step, check whether the data is loading to DSO from PSA or from the source system directly. If the data is loading to DSO from PSA, then activate the DSO manually as follows
Right click DSO Activation Step -> Target Administration -> Select the latest request in DSO -> select Activate -> after request turned to green status, Restart the job.
If the data is loading directly from the source system to DSO, then delete the bad request in the PSA table, then restart the job
4.      Failure in Drop Index/ Compression step: When there is a failure in Drop Index/ compression step, check the Error Message. If it is failed due to “Lock Issue”, it means job failed because of the parallel process or action which we have performed on that particular cube or object. Before restarting the job, make sure whether the object is unlocked or not. There is a chance of failure in Index step in case of TREX server issues. In such cases engage BASIS team and get the info reg TREX server and repeat/ Restart the job once the server is fixed. Compression Job may fail when there is any other job which is trying to load the data or accessing from the Cube. In such case job fails with the error message as “Locked by ......” Before restarting the job, make sure whether the object is unlocked or not. 5. Roll Up failure: “Roll Up” fails due to Contention Issue. When there is Master Data load is in progress, there is a chance of Roll up failure due to resource contention. In such case before restarting the job/ step, make sure whether the master data load is completed or not. Once the master data load finishes restart the job. 6. Change Run – Job finishes with error RSM 756       When there is a failure in the attribute change run due to Contention, we have to wait for the other job (Attribute change run) completion. Only one ACR can run in BW at a time. Once the other ACR job is completed, then we can restart/repeat the job. We can also run the ACR manually in case of nay failures. Go to RSA1-> Tool -> Apply Hierarchy/Change Run -> select the appropriate Request in the list for which we have to run ACR -> Execute. 7. Transformation In-active: In case of any changes in the production/moved to the production without saving properly or any modification done in the transformation without changing, in such cases there is a possibility of Load failure with the error message as “ Failure due to Transformation In active”. In such cases, we will have to activate the Transformation which is inactive. Go to RSA1 -> select the transformation -> Activate In case of no authorization for activating the transformation in production system, we can do it by using the Function Module - RSDG_TRFN_ACTIVATE Try the following steps to use the program "RSDG_TRFN_ACTIVATE” here you will need to enter certain details:Transformation ID: Transformation’s Tech Name (ID)Object Status: ACTType of Source: “Source Name”Source name: “Source Tech Name”Type of Target: Target NameTarget name: “Target Tech Name”
Execute. The Transformation status will be turned into Active.
Then we can restart the job. Job will be completed successfully.
     8. Process Chain Started from the yesterday’s failed step:
In few instances, process chain starts from the step which was failed in the previous iteration instead of starting from the “Start” step.
In such cases we will have to delete the previous day’s process chain log, to start the chain form the beginning (from Start variant).
Go To ST13-> Select the Process Chain -> Log -> Delete.
Or we can use Function Module for Process Chain Log Deletion: RSPROCESS_LOG_DELETE.
Give the log id of the process chain, which we can get from the ST13 screen.
Then we can restart the chain.
Turning the Process Chain Status using Function Module:
At times, when there is no progress in any of the process chains which is running for a long time without any progress, we will have to turn the status of the entire chain/Particular step by using the Function Module.
Function Module: RSPC_PROCESS_FINISH
The program "RSPC_PROCESS_FINISH" for making the status of a particular process as finished.
To turn any DTP load which was running long, so please try the following steps to use the program "RSPC_PROCESS_FINISH" here you need to enter the following details:
LOG ID: this id will be the id of the parent chain.
CHAIN: here you will need to enter the chain name which has failed process.
TYPE: Type of failed step can be found out by checking the table "RSPCPROCESSLOG" via "SE16" or "ZSE16" by entering the Variant & Instance of the failed step. The table "RSPCPROCESSLOG" can be used to find out various details regarding a particular process.
INSTANCE & VARIANT: Instance & Variant name can be found out by right clicking on the failed step and then by checking the "Displaying Messages Options" of the failed step & then checking the chain tab.
STATE: State is used to identify the overall state of the process. Below given are the various states for a step.
R Ended with errors
G Successfully completed
F Completed
A Active
X Canceled
P Planned
S Skipped at restart
Q Released
Y Ready
Undefined
J Framework Error upon Completion (e.g. follow-on job missing)
9. Hierarchy save Failure:
When there a failure in Hierarchy Save, then we have to follow the below process...
If there is an issue with Hierarchy save, we will have to schedule the Info packages associated with the Hierarchies manually. Then we have to run Attribute Change Run to update the changes to the associated Targets. Please find the below mentioned the step by step process...
ST13-> Select Failed Process Chain -> Select Hierarchy Save Step -> Rt click Display Variant -> Select the info package in the hierarchy -> Go to RSA! -> Run the Info Package Manually -> Tools -> Run Hierarchy/Attribute Change Run -> Select Hierarchy List (Here you can find the List of Hierarchies) -> Execute.

Sales orders locked

Hi to all,
I am facing an strange issue as we use Scenario-A for sales order creation which are created in CRM then replicated to ECC for subsequent processing & now we get some strange issue of sales orders not able to open in ECC as we get the error as sales order is locked by some user in CRM system.
I had checked in all queques & Bdoc we find no orders locked but the sales order gets released after sometime in few hours also all these locked sales orders are distributed successfully without any issue.
Thanks in advance,
Shiva

Hi Shiva,
If an update is terminated, the status is switched from WAITUPDA to VBERROR.
You can also go directly from the tRFC Monitor and qRFC Monitor to the terminated update task in transaction SM13.
And when an order is already been sent to ECC System you cannot make changes in CRM. In order to do so you have to activate the interactive changes in customizing.
Regards
Sidd

Error while loading data from ECC to BI

Hi BW Experts,
while loading data from ECC 6.0 to BI i got error in details tab of the infopackage as datapackage 1 arrived in bw processing not yet finished.
Could any one help me out?
Thanks

Amar,
please check the source system job status. If its successfully completed then we can expect data load sucess in BW side.
to check source system status: RSMO> select related load>in Menu Environment-->Job overview in source system.
once this over check the TRFC or IDocs struck
if TRFC, chk in TCode-SM58 or from environment select TRFC from source/data warhouse.
if you are finding TRFcs are in stuck just select and run manually to complete.
M

IDOC sticks in XI - forever?

Hi,
an Idoc sticks in the XI system for over 7 days. Is there a chance to restart that message?
The queue entry shows that:
Caller
XIAPPLUSER
Function Module
IDOC_INBOUND_ASYNCHRONOUS
Target System
CRP_100
Date Time
18.01.2006 11:00:23
Status text
Transaction executing
Transaction ID
C0A83D0E0D9C43CE11B70077
The column outbound status in SXMB_MONI shows a green flag with tooltip "message scheduled on outbound side".
That message definitly did not receive the target system - I have checked that.
I couldnt restart from SXMB_MONI: You cannot restart XML message
49A3CD43AA2DF502E1000000C0A83D0E with this
status/type -> can I change the status, so that a restart is possible?????
What can I do?
Is there a way to monitor such errors/problems within XI (CCMS...)?
Many thanks for every help!
Regards,
Christian

Hi Michal,
SMQ1 and SMQ2 are empty - nothing at all.
But if I start the TRFC monitor (SMQS) I can see the entry described above. Should I execute "execute LUW" from the "Edit" menu or "Reset status" from the "Edit" menu??
Thanks and regards,
Christian

No service for system SAPNID, client 800 in Integration Directory

Hi All,
I am getting No service for system SAPNID, client 800 in Integration Directory in tRFC monitor (SM58).
My scenario is IDOC to File.
I did following step in R3.
1. Created RFC destination pointing to XI systems (name:XID)
2. Created IDOC port (name: SAPNID) and use above (XID) RFC in RFC destination.
3. Create Partner Type LI (Partner No. 3000) and add message type ORDERS, set the receiver port (SAPNID) created above.
XI Side.
1. Create Technical System (Name : XID)
2. Business Systems (Name: R3XID)
3. In Integration Repository.
 Created Data Type
 Import IDOC ORDERS.ORDERS04
 Created Message Interface
 Created Message Type
 In Mapping Object created Message Mapping and Interface Mapping.
4. In Integration Directory
 Created the Scenario (name : FILE_FROM_IDOC)
 Assign Business Systems as R3XID
 Create communication channel(name: FILE_ORDERS_COM_CHNL)
 Create Receiver Determination
 Interface Determination
 Receiver Agreement.
IDOC is triggered correctly but in tRFC monitor I am getting following error
No service for system SAPNID, client 800 in Integration Directory
With regards
Sunil

Hi Udo/Renjith and Rakesh,
Thanks for quick reply and appreciate you help.
Now I can say that there is some problem with my Technical Systems or Business Systems, let me give you details regarding my Technical/Business systems.
During post-Installation i created Technical/Business System, following are the details regarding these systems.
Technical Systems.Detail
System Name: XID
System Home: crmides
Installation Number: INITIAL Change...
Release: 640
Description:
Administrative Contact:
TMS Domain:
TMS Transport Group Name:
Clients: 100 800 Add...
Message Server: XID crmides
Central Application Server: crmides_XID_00
Secondary Application Servers: Add...
Internet Transaction Servers: Add...
Installed Products: SAP EXCHANGE INFRASTRUCTURE, SAP EXCHANGEINFRASTRUCTURE 3.0 XID
SAP R/3, 4.5B XID on crmides
SAP R/3, 4.6C XID on crmides
Add...
Installed Software Components
Business Systems:
1. R3XID
2. SAPNID
Earlier I have only one Client (100) and One Busines Systems (R3XID)
My XI Systems is XID Host : crmides Client : 100 System Number : 00
My R3 Systems is NID Host : netbw Client : 800 Systems Number : 02
Business Systems Detail
Name: R3XID
Description:
Administrative Contact:
Business System Role: Integration ServerApplication System
Pipeline URL:http://crmides:8000/sap/xi/engine?type=entry
Integrated Business Systems: SAPNID
Group: (No Group Assigned)Edit Groups...
Transport Targets:
Technical System: XID on crmides Change...
Client: 100 of XID
Logical System Name: SAPNID
Installed Products: SAP R/3, 4.5B XID on crmides
SAP R/3, 4.6C XID on crmides
SAP EXCHANGE INFRASTRUCTURE, SAP EXCHANGEINFRASTRUCTURE 3.0 XID
Software Components: ABC, 1.0 of knack
R/3 CORE 4.5B
SAP ABA 4.6C
SAP ABA 640
SAP APPL 4.6C
SAP BASIC JAVA LIBS 6.30
SAP BASIS 4.6C
SAP BASIS 6.40
SAP GUI FOR WINDOWS 4.5B
SAP GUI FOR WINDOWS 4.6C
SAP GUI FOR WINDOWS 6.20
SAP HR 4.5B
SAP HR 4.6C
SAP ITS 4.6B
SAP ITS 4.6C
SAP J2EE ENGINE 6.30
SAP J2EE ENGINE CORE 6.30
SAP JAVA TECH SERVICES 6.30
SAP JCO 6.30
SAP SOFTW. DELIV. MANAGER 6.30
XI ADAPTER FRAMEWORK 3.0
XI CONNECTIVITY SE 3.0
XI TOOLS 3.0
During Post Installation I had one Technical Systems (XID) and one Business Systems (R3XID), after that I created one more Business Systems (SAPNID).
SAPNID Business Systems Detail
Name: SAPNID
Description:
Administrative Contact:
Business System Role: Application System
Related Integration Server: R3XID
Group: (No Group Assigned)
Transport Targets:
Technical System: XID on crmides Change...
Client: 800 of XID
Logical System Name: SAPNID
Installed Products: SAP R/3, 4.5B XID on crmides
SAP R/3, 4.6C XID on crmides
SAP EXCHANGE INFRASTRUCTURE, SAP EXCHANGEINFRASTRUCTURE 3.0 XID
Software Components: ABC, 1.0 of knack
R/3 CORE 4.5B
SAP ABA 4.6C
SAP ABA 640
SAP APPL 4.6C
SAP BASIC JAVA LIBS 6.30
SAP BASIS 4.6C
SAP BASIS 6.40
SAP GUI FOR WINDOWS 4.5B
SAP GUI FOR WINDOWS 4.6C
SAP GUI FOR WINDOWS 6.20
SAP HR 4.5B
SAP HR 4.6C
SAP ITS 4.6B
SAP ITS 4.6C
SAP J2EE ENGINE 6.30
SAP J2EE ENGINE CORE 6.30
SAP JAVA TECH SERVICES 6.30
SAP JCO 6.30
SAP SOFTW. DELIV. MANAGER 6.30
XI ADAPTER FRAMEWORK 3.0
XI CONNECTIVITY SE 3.0
XI TOOLS 3.0
I do not know whether SAPNID is required or not, earlier I used R3XID as Business Systems at the time of configuration now I changed it to SAPNID. I am getting the same error in both the case.

IDOC Scenario - User has no RFC authorization for function group EDIN

Hi all,
I'm trying to configure an IDOC scenario from ECC to XI.
RFC's, ports and destinations already configured. On WE19 I'm creating an IDOC for testing the scenario. The IDOC is sent successfully, and it stops on TRFC Monitor with error "User PIRFCUSER has no RFC authorization for function group EDIN." .
Some of you knows what authorization is needed? Basis team said the roles are the same at DEV environment, and there this scenario works fine.
Thanks for your help.
regards.
Roberti

Hi,
Check with PIRFCUSER user , that is having the right authorization or not ..
And make sure that this user is present in the system & it should not locked.
to check that user is present or not-----goto su01 of the system & check
Regards
Seshagiri

IDCO's Struck in TRFC Monitor

Similar Messages

Maybe you are looking for