on 01-13-2006 6:16 AM
Hi,
We are in BW 3.5 with support package SAP_BASIS SAPKB64014 and R/3 4.7 with support package SAP_BASIS SAPKB62056.
We have implemented the note 869628 already when we had a problem stated in note 901878. Data load was fine till last week.
Now when we try to load data to BW from R/3, the info package status is Yellow and gets time out.
The message in BW says "<b>Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n</b>". There is no inbound
IDOC found in BW.
In R/3 the IDOC status is 64 with messages
1. "<b>No resources, immed. processing not possible: Function deactivated</b>"
and 2. "<b>No filters , No conversion , No version change</b> ."
We found our problem listed in Note 555229 but the note is not valid to our version and we were not able to implement it in SNOTE.
Is there any other solution for this? Coz without the data load happening we are not able to proceed any further in our developement work.
Regards,
Pradhiba
PS : We have recently applied Windows 2003 SP1 and SQL Server SP4 to our R/3 server. Does this have any impact on our problem?
hi Pradhiba,
1. "No resources, immed. processing not possible: Function deactivated"
sounds no resource in r/3 ? memory, tablespace ? can ask basis check ?
any short dump (st22), system log (sm21) ?
is it happened to all extraction ? all just this datasource ? can we know the datasource name ? try with rsa3 what happen ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Pradhiba,
take a look oss note 555229-IDocs hang in status 64 for tRFC with immediate processing and 561880-Requests hang because IDocs are not processed
hope this helps.
555229
Symptom
IDocs hang in status 64 in the inbox. The message text in the IDoc status record is: (B1999) "NO RESOURCES, IMMED. PROCESSING NOT POSSIBLE: <reason>".
Solution
The proposed solution includes source code corrections and a configuration enabled by the source code corrections.
The source code corrections can be imported for this version within a version between the Support Package given in note 535172 and the lowest Support Package given in this note. It is available with the highest Support Package given in this note for the corresponding version. There are 2 configuration variants:
1. Return to the processing in the same dialog process as the IDoc receipt
Maintain the following entry in the TEDEF table using transaction SE16 in every client for which you want to postpone the behavior:
Field EVENTT with value TRFC-IDOC and field ROUTID with value SYNCHRON
Caution: You have thereby restored the original behavior prior to note 535172. It may therefore happen again that IDocs are received and processed repeatedly.
1. Change from dialog to background process
Maintain the following entry in the TEDEF table using transaction SE16 in every client for which you want to postpone the behavior:
Field EVENTT with value TRFC-IDOC and field ROUTID with value BATCHJOB
The IDoc is then processed by the application in a second, parallel process, provided there are enough dialog processes. If no dialog process is currently free, report RBDAPP01 is scheduled for this IDoc and executed as a background process. The job number is logged in the IDoc status record with the status 64. The user under whose identification the IDocs are received must have authorization to release jobs in the S_BTCH_JOB authorization object.
Hi A.H.P,
Thanks for your reply. Unfortunately i have already tried note 555229, though the note was not valid to our R/3 version, i tried implementing it, in SNOTE transaction i got a message that the note is invalid and so it was of no use. I tried making the entry in TEDEF table, the request turns Green in R/3 but in BW it is still in the same state with the same message and if i check the IDOC movement in BW using transaction WE05, i dont find any Inbound IDOCS to BW. So what do i do?? i have raised a note in Service.SAP.... if u know any other way out pl let me know
Pradhiba
Hi Pradhiba and A.H.P,
I got this problem yesterday and I tried all steps mentionned in this message of yours. Just for your information I checked the following points also (maybe it helps you to analyse better the problem):
-
System Analysis:
1. SE16 T000
2. SE16 RSBASIDOC in both systems
3. SU01 PROFILES
BWREMOTE > To be checked
ALEREMOTE and profile S_BI-WX_RFC see note 150315 > To be checked
4. WE20 Partner Profile LS settings in both are OK
BW outbound RSRQST
inbound RSINFO RSSEND
R/3 outbound RSINFO RSSEND
inbound RSRQST
also check 'RSSEND' in R/3
BIDOCTYP = ZSUB161 > To be checked
5. SM59 .. appears to be ok
6. check inconsistency in tables RSISOSMAP and RSOSFIELDMAP
SE16 BW for table RSISOSMAP
7. SE16 BW for table RSOSFIELDMAP
no 'T' entries
8. in BW > source system
The remote users for calling and sending data must have the type
Dialog or CPIC (see Note 161570).
9. Run the report RS_TRANSTRU_ACTIVATE_ALL (activate all BW structures)
10. check entries on the table bdls
-
Maybe I will re-check all this again today.
In the mean time I will appreciate any other suggestions that you may have about this issue.
Thanks,
PL.
Message was edited by: Paulo Lie
Message was edited by: Paulo Lie
Hi..
there is a note - 561880. It says,
1. Make sure there is always sufficient DIA, that is, at least 1 DIA more than all other work processes altogether, for example, 8 DIA for a total of 15 work processes (see also note 74141).
TIP: 2 UPD process are sufficient in BW, BW does not need any UP2.
When i checked in my system, i have 6 DIA and 8 others. So we have asked our Basis team to make DIA more compared to others, ie., to increase our DIA to 9. Let us see what happens then. Once it is increased, i will try the data load and let you know the result.
Regards,
Pradhiba
Hi All...
I finally solved the problem....
In R/3, i was just analysing the transaction SM58. There i found many IDOCs ready for processing. Then i tried something like this.
In Menu - Goto - QOUT Scheduler
Again in Menu - Goto - QRFC Resources. In that i found that DIA-WPs for tRFC/qRFC was 0(zero) while Max. DIA-WPs was 9.
I was searching for help to find how to allocate resources to tRFC/qRFCs.
somewhere in this link http://help.sap.com/saphelp_nw04/helpdata/en/62/73241e03337442b1bc1932c2ff8196/frameset.htm
there was a reference to transaction SARFC, there i found a red message saying that said 'system configuration is not correct'. So i double clicked on the system name, there i found the status as inactive(0), i explicity made it active(1) and clicked on copy.
Thats it, it automatically allocated 7 resources out of 9 to tRFC/qRFC and all the data loads which were hanged for all these days got a green immediately!!!!
Anyways Thanks for all the help!!
Regards,
Pradhiba
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.