"Error during application input" while processing IDOC with status 51

Hi ,
I tried to post an error IDOC with status "51" of message type FIDCC2 using program RBDINPUT, it just creates a message "Error during application input" . It is not calling the application dialog . Does anyone have answer for this?
Thanks,
Hemant.

HI,
Kindly check the RFC entries in t-code SM58.
If any entries are their please release them manually selecting each one and press "F6".
Regards,
Anil.

Similar Messages

Processing idocs with status 8

hi friends,
how to process idocs with status 8

Hi,
Chek this thread which contains step by step procedure to process Idocs
mannualy process idoc
Also try these steps
1. Goto Infopackage
2. Click on the "Details" Tab of the Infopackage
3. Goto Datapackage which is currently process
4. Under the detail tab you can see
Date, Time, Record... in that you can also see IDOC#
5. Take the IDOC# and goto BD87 of the Sourcesystem
6. Paste the IDOC# against IDOC
7. Give IDOC Status = 64
8. Give Partner system = "Your Source System"
9. Execute BD87.
10. You will navigate to next screen
11. Maximize all by using "Expand Subtree" button on Menu
12. You can see "IDOC stauts " column with 64
13. Click on the row against to 64
14. Click button "Execute" on Menu.
15. Your IDoc will start processing
16. If it success IDoc status will be turned to 53 else to 51.

5 IDOC with status 29 Error in ALE service

hi there,
im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
IDOC Status Outbox:
IDOC failure between 13/07/2008 to 14/07/2009
1 IDOC with status 02 Error passing data to port
5 IDOC with status 29 Error in ALE service
IDOC Status InBox:
88 IDOC with status 51 Application document not posted
regards
raju

Hi,
Check this thread.
DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Regards.

While processing Idoc -error

Hi ,
While processing Idocs we are facing with 2 error can any one help me out.
1.Order 123 does not exist
2.Error in document: BKPFF $ DR0CLNT400
Message no. RW609
Diagnosis
Errors occurred when checking or posting the document
Reference type = BKPFF
Reference key = $
Logical system = DR0CLNT400
You can find the errors in the log
Thanks and Regards
Sri

HI,
Please go to transaction WE02 and look at the IDOC.
The IDOC will have a STATUS section. when you expand it, it will give you a log with error status. Double click to look at the detailed error.
Looking at the error it looks like you are bringing in an IDOC from another SAP system to this SAP system. The order # 123 against which IDOC is for, doesn't seem to exist in the receiving SAP system.
Regards

Inbound Processing of Idocs with status other than success

Hi,
I am new to ALE/Idocs. Can anyone please let me know how can I process the Idocs which have the status other than 53.
Thanks & Regards,
Indira

Hi,
In addition to the previous posts few more programs to process failed inbound IDocs are as mentioned below.
- Use program RBDAGAIE to process edited IDocs (IDocs with status 69)
- Use program RBDAPP01 to process IDocs failing with serialization issue (IDocs with status 66)
- Use program RBDAGAI2 to process IDocs after ALE inbound error (IDocs with status 56, 61, 63, 65)
~ Bineah

XOQ-01703: error during parse of build process script: (clear, compile)", "

Hi All ,
I was just clearing the dimensions using the below in SQL commandline throwing below error . However this works fine with my another 5 dimensions .Any advice ?
SQL> exec dbms_cube.build('POSITION using (clear, compile)');
BEGIN dbms_cube.build('POSITION using (clear, compile)'); END;
ERROR at line 1:
ORA-37162: OLAP error
XOQ-01703: error during parse of build process script: "BUILD POSITION using
(clear, compile)", ""
ORA-06512: at "SYS.DBMS_CUBE", line 236
ORA-06512: at "SYS.DBMS_CUBE", line 280
ORA-06512: at line 1
Thanks,
DxP

I believe in this case the parser that is parsing the build process script is treating the dimension name "POSITION" as a keyword and not as an OLAP Cube Dimension name. You may wish to rename the dimension to a name other than "POSITION" or double quotes as specified previously.
Edited by: user713408 on Aug 1, 2011 12:12 PM

Portal Runtime Error : An exception occurred while processing a request

Hello friends,
After upgradation of my portal to the following patch level, SAP J2EE 6.20:
Portal Version : EP 6 SP 2 patch 29 hotfix 0
Content Mgmt and Collaboration version : 6 SP2 patch 5
i faced many performance related issues. Portal seems to be very slow. After logging in, most of the time I get 2 errors:
Either
1> Iview remains blank.
Or
2> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
But when I refresh that particular iview, it works fine.
I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."Aug 18, 2005 6:07:42 PM # PRT-Async 2 Fatal Exception ID:06:07_18/08/05_0669
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
Component class : com.sapportals.portal.prt.pom.RootComponentNode
User : tempuser
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
 at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Help needed.(as i am helpless now.)
Regards,
Nilz

Anthony,
I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
I created like this
 project-> rightclick-> export-> par ->selecting project-> givint protal password-> and finish.
The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
but the par file is created in the NW studio Navigation bar.
Let me know any help regarding this
thanks
venkat

Splitter program for processing the IDOCS with status 64.

Hello folks,
I have a requirement explained below. I am looking for a sample code which could help me to jump start with initial development.
Requirement:
Develop a splitter program which retrieves all the IDCOS with status 64, create and schedule batch jobs with 200 IDOCS each. The splitter program with be scheduled every 15 min.
Restrictions
Only 150 batch jobs can be created at a time.
Estimation
There may be around 36000 IDOCS with status 64 every hour.

Srinivas,
Here is the explaination why we require a splitter program.
Using RBDAPP01 parellel processing
Let us assume there are 4 servers A, B, C and D in a server group. If we select RBDAPP01 parellel processing there will be too many RFC calls to the servergroup.
(there are some more RFC calls later on for Order creation for example). As there is a restriction with number of RFC calls, we need to clear other RFC's before making new one. This is making complex and messy.
Using RDBAPP01 serial processing
For the volume of orders getting created each day, it takes a week to process those Idoca created in one day. Hence it is not a good solution.
Splitter program
We spawn 150 batch jobs with 200 records each. This way if we think it takes 20 min for each job to complete...by the end of 20th min we must had processed 30000 idocs.
Hence it is the solution offered.
Srinivas...still this confuses me..but if I am wrong anywhere please correct me.
But your initial response has helped me a lot. Everything was blank to me, ur reply made it clear over the requirement.
Thanks a lot,
Naren

Idoc with status 68

Hi,
Can any one tell me the reason for idoc status as 68.......in which case the system will show me the idoc status as 68
Thanks,
Shilpa

IDoc status Description
Outbound values :-->
00 Not used, only R/2
01 IDoc generated
02 Error passing data to port
03 Data passed to port OK
04 Error within control information of EDI subsystem
05 Error during translation
06 Translation OK
07 Error during syntax check
08 Syntax check OK
09 Error during interchange handling
10 Interchange handling OK
11 Error during dispatch
12 Dispatch OK
13 Retransmission OK
14 Interchange Acknowledgement positive
15 Interchange Acknowledgement negative
16 Functional Acknowledgement positive
17 Functional Acknowledgement negative
18 Triggering EDI subsystem OK
19 Data transfer for test OK
20 Error triggering EDI subsystem
21 Error passing data for test
22 Dispatch OK, acknowledgement still due
23 Error during retransmission
24 Control information of EDI subsystem OK
25 Processing despite syntax error (outbound)
26 Error during syntax check of IDoc (outbound)
27 Error in dispatch level (ALE service)
28 Not used
29 Error in ALE service
30 IDoc ready for dispatch (ALE service)
31 Error - no further processing
32 IDoc was edited
33 Original of an IDoc which was edited
34 Error in control record of IDoc
35 IDoc reloaded from archive
36 Electronic signature not performed (timeout)
37 IDoc added incorrectly
38 IDoc archived
39 IDoc is in the target system (ALE service)
40 Application document not created in target system
41 Application document created in target system
42 IDoc was created by test transaction
Inbound Values::-->
50 IDoc added
51 Application document not posted
52 Application document not fully posted
53 Application document posted
54 Error during formal application check
55 Formal application check OK
56 IDoc with errors added
57 Test IDoc: Error during application check
58 IDoc copy from R/2 connection
59 Not used
60 Error during syntax check of IDoc (inbound)
61 Processing despite syntax error (inbound)
62 IDoc passed to application
63 Error passing IDoc to application
64 IDoc ready to be transferred to application
65 Error in ALE service
66 IDoc is waiting for predecessor IDoc (serialization)
67 Not used
68 Error - no further processing
69 IDoc was edited
70 Original of an IDoc which was edited
71 IDoc reloaded from archive
72 Not used, only R/2
73 IDoc archived
74 IDoc was created by test transaction

Reprocessing IDOCS with status 52

Hi all,
I facing a problem with IDOC status 52.
After correcting the error it had given, I want to reprocess it again.
Kindly tell me any report or transaction name for reprocessing IDOC with status 52.
Regards,
Rahul

Hi Rahul,
You can use the below Programs for IDocs Reprocessing:
RBDMANI2 : Reprocess Idocs manually
RBDMANIN : Posting of IDocs with Status 51
RBDMOIND : Outbound Idocs status 03->12
RSEOUT00 : For Processing 30 Status IDocs
RBDAPP01 : For Processing 64 Status IDocs
RBDAGAIN : Reprocess Incorrect Outbound IDocs
RBDAGAI2 : Reprocessing of IDocs after ALE Input Error
Regards
Aneesh.

Reprocess Idocs with status 3

Hi ,
I want to reprocess successful IDOCs with status 3 again,how can I do that?
I think logically we can change the status other than 3 and use BD 87 to reprocess them?is this correct way?Idoc numbers would change or they would create new IDOCs?
thank you,
Babu

Hi,
You can use transaction BD87 to monitor the IDoc statuses.
and use the following programs to reprocess outbound and inbound error IDoc(s).
RBDAGAI2 - Re-processing of IDocs after ALE Input Error
RBDAGAIE - Reprocessing of Edited IDocs
RBDAGAIN - Process Outbound IDocs with Errors Again
RBDAGAIP - New Posting of Partially Posted IDocs
RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
RBDINPUT
Reward points
Regards

Idoc with status 32

Hi
In we05 transaction i see one idoc with status 32.
Status text was: idoc was edited
T100 text was: change data record was saved..
how to overcome this staus to post the idoc in target system??

Hi,
    RBDAGAIE - Reprocessing of Edited IDocs .
    The above Standard program is for Reprocessing Idoc's.Go through this program.So that u will rectify that error.
Note: -
      Description: This report reprocesses an edited IDoc in inbound or outbound processing. The edited IDoc has one of the following statuses:
32: IDoc edited (outbound)
69: IDoc edited (inbound).

Report RBDAPP01 not processing IDocs in status 51

Hello guys,
I have a problem with the execution of some Inbound Idocs using program RBDAPP01.
Now the Idoc is executed in background with a job. Sometimes we have some locks because we receive idocs going to the same order, and then remain in status 51.
In the variant of the job we filled to execute Idocs with status 64 and 51, but the idocs that remain in status 51 are not processed, at the end we have to do it manually.
There is no parallel processo to avoid the locks.
Do you know how we can solve it?
Many thans in advance.
Regards,
Xavi.

i do have the same problem. is there an solution to this?

Performance issues in using RBDAPP01 for reprocessing iDocs with Status 64

Hi All,
I am using the Standard ABAP Program 'RBDAPP01' for reprocessing Inbound iDocs with Status 64 (Ready to be posted).
When this is scheduled as a job in background, I find that it opens multiple sessions and occupies all available dialog sessions.
This in turn slows down the entire system.
Also, I find the addition 'Packet Size' on the selection screen for the program.
Is it related in any way to the number of sessions the program creates?
Any pointers in resolving this issue will be extremely helpful.
Thanks in advance.
Regards,
Keerthi

Hi,
When you mention Parallel Processing, it becomes active only if I choose that particular option on the selection screen right?
In my case, I haven't chosen parallel processing, but still the overall system performance seems to have fallen very badly.
Now please correct me if my understanding is wrong.
If I increase my Packet Size, it should improve the system performance, but will increase my runtime for the selected iDocs.
But as I have not selected parallel processing in this current situatuon, it should not have any impact here.
Have I summarized it rightly?
Thanks in advance.
Regards,
Keerthi

Process Flow with Status Busy

Hello
In Warehouse Builder Browser I have one Process Flow with Status Busy. I have restarded the whole server and status is still Busy.
Through Oracle Workflow I try to Find Active Processes and there just is no one.
Why is my Process Flow still Busy and how do I stop it? (Maybe the there is an error in Warehouse Builder Browser, it is not busy?)
Best regards,
Tina

Just logout and login into Warehouse Builder Browser again. It is not busy any more ;-).
/Tina

"Error during application input" while processing IDOC with status 51

Similar Messages

Maybe you are looking for