I stuck at Idoc status 26

Hi all,
I need a help in Idoc. I got Idoc status 26. How can i fix this problem. plz help me. its urgent..

Hi Narendran Muthukumaran,
I am new to Idocs. can you give clear steps how i can procede. I found that my idoc is having status code 26 twice. First one showing 'Get details from previous status records with status 26' and second status 26 showing 'EDI: Syntax error in IDoc (mandatory segment missing)'. The segment E1EDP16 has the attribute 'Mandatory' in the syntax description of the basic type DELFOR01 (customer enhancement ). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
This error may have been triggered by an unidentifiable segment before the expected mandatory segment.
when i see the status 26 it given procedure has....
Please check the IDoc or the syntax description of the basic type DELFOR01 (customer enhancement ).
so plz guide me how to do it..

Similar Messages

Receiver JDBC channel is stuck in "delivering" status.

Hi experts,
I have a IDoc -> JDBC scenario, and when the JDBC channel tries to process a message, it get stuck in "delivering" status. Here's the log of the message process:
2011-04-25 17:38:10 Success Message successfully received by messaging system. Profile: XI URL: http://xq0ds001:50100/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2011-04-25 17:38:10 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2011-04-25 17:38:10 Success Message successfully put into the queue.
2011-04-25 17:38:10 Success The message was successfully retrieved from the receive queue.
2011-04-25 17:38:10 Success The message status set to DLNG.
2011-04-25 17:39:08 Success Delivering to channel: CC_JDBC_NA_Familiares_BUXIS_Receiver
2011-04-25 17:39:08 Success MP: Entering module processor
2011-04-25 17:39:08 Success MP: Processing local module localejbs/CallSapAdapter
2011-04-25 17:39:08 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2011-04-25 17:39:09 Success JDBC adapter receiver channel CC_JDBC_NA_Familiares_BUXIS_Receiver: processing started; party , service BS_NA_BUXIS_QA
Any ideas of what could be causing this?
Many thanks!
Vanesa.-

Hi Vanesa,
Make sure you have set the MaxThreadCount parameter to 350 or higher depending of the case and of the resources available.
To increase the parameter, please follow the instructions below:
1. In the left frame choose Server -> Kernel -> ApplicationThreadManager
2. In the tab Display Configuration (right frame) choose Switch between view and edit mode to activate the edit mode.
3. The parameter MaxThreadCount must be set to 350.
4. You will then need to restart the J2ee
For reference see note #937159 - XI Adapter Engine is stuck
For specific setting to an adapter can be done by going to Services -> SAP XI AF Messaging
Look at the property 'Messaging connections' here you will see the following queues:
Send.maxConsumers (asynchronous sending - outbound)
Recv.maxConsumers (asynchronous receipt - inbound)
Call.maxConsumers (synchronous sending - outbound)
Rqst.maxConsumers (synchronous receipt - inbound)
Depending on where the bottleneck is occurring (i.e. too many entries in the Send.maxConsumers) you can increase these parameters.
Example of parameter value syntax (sample for JDBC adapter):
(name=JDBC_http://sap.com/xi/XI/System, Send.maxConsumers=15, Recv.maxConsumers=15, Call.maxConsumers=15, Rqst.maxConsumers=15)
For reference see note:
#791655 - Documentation of the XI Messaging System Service Properties
And see the link:
/people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
Regards,
Caio Cagnani

User Profile Service - User Profile Incremental Synchronization Timer job stuck at 33% Status: Pausing

User Profile Service - User Profile Incremental Synchronization Progress: 33% Status: Pausing
It has been almost 15 days.
Both User Profile Service and User Profile Synchronization Service are in Started state and FIM service also starting
I tried clearing sharePoint config cache.
I also restarted the sharepoint timer service.
I tried almost everything that is on Internet but nothing helped me.
Is there any other way to solve the issue as I was struck on production server (ASAP)
In synchronization serivce manager status of MOSS_DeltaImport is Inprogress from past 2 days
Best Regards.

Hi,
Please follow the steps in the link below to clear the configuration cache.
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
Here is a similar thread for your reference:
https://social.technet.microsoft.com/Forums/en-US/beaa852c-6f40-428a-b97c-20722864e045/user-profile-service-user-profile-incremental-synchronization-timer-job-stuck-at-88-status?forum=sharepointadminprevious
Or try to clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. Microsoft has provided a step by step procedure on clearing file system cache from the SharePoint front-end servers
in this kb article.
You can also see the ULS logs and check error messages.
http://sharepointlogviewer.codeplex.com/
Best Regards
Dennis Guo
TechNet Community Support

IDOC status at 30, but in we05 it is 03

Hello Gurus!!
My program generates an IDOC and as soon as the idoc is generated it the status is 03 then i have todo something else.
Within the program when i am cheking the status is 30 but actually in transaction we05 the status is 03.
I have cheked the partner profiles and transfer_idocs_immeadiately has already been selected.
I have already gone thru the forum but no valid solution was given,
There is no need to change any ALE configurations / port configurations because everything just work fine. It is only that within the program i am not able to catch the status 03. the proram is not waiting untill the idoc status is 03. it is capturing only the status 30.
Is there any thing that i can do within the program? should i capture the idoc number and then check the idoc status from EDID4?
Please answer o this questions ASAP.
Regards.

Initially when you create the outbound idocs then status is 30. then you have to run the program RSEOUT00 to process the idoc then after the processing the status changes to 03.
But the Program RSEOUT00 is optional. In the partner profile (WE20) If you select the option 'Collect Idocs', then you have to schedule the program RSEOUT00 to process the Idocs otherwise if you have choose the option 'Transfer idoc immediately', you don't need to do anything.
Thanks,
Srinivas

Is it possible to create a custom IDOC status?

Is it possible to create a custom idoc status on table TEDS1?
I have looked through customising and cannot seem to find a way to create a new idoc status.
Has anybody done this?

Hello Chester..
hope this link will be helpful,
Re: IDOC status
*********Please reward points ,if found useful

IDoc status 53 in employee replication from SAP HR

Hi experts,
We are having some problems in CRM BP creation with role employee.
We are using CRM 5.0 and SAP ECC 6.0 and we are trying to replicate employees information to CRM from HR.
After read the notes 934372, 615896, 550055, 363187, 312090 we made the next configuration steps in our systems:
R/3:
- Creation of connection port (trans. WE21)
- Creation of logical system (trans. WE20) and assignment of outbound message HRMD_ABA
- Creation of distribution model (trans. BD64) with all filters indicated in note 312090
CRM
- Creation of logical system (trans. WE20) and assignment of inbound message HRMD_ABA
- Creation of conversion between basic types HRMD_A05 and HRMD_ABA01 (trans. WE70) as described in note 312090
- Creation of conversion between message types HRMD_A and HRMD_ABA (trans. WE73) as described in note 312090
- Creation of external number range ZE from HR01200001 to HR01299999 (using PA04 in R3 we found the number range between 01200001 and 01299999)
- Creation of BP Grouping with the same name of number range (ZE) checked to be external too
- Update of table T77S0 (using SM30):
HRALX HRAC X
HRALX PBPON OFF
HRALX PBPHR ON
HRALX PBPON ON
HRALX PNUMB 3
HRALX PPROL BUP003
HRALX PSUBG ZE
PLOGI PLOGI MV
We know we should have the same value in R3 and CRM for PLOGI/PLOGI, so we created in CRM MV because that is the plan version used in R3. To create it, we just manually add a new row in table T778P and then selected it in table T77S0. Is this the correct way to create a plan version?
After these steps, in R3 we execute program RHALEINI with parameters:
- Plan version = MV
- Object type = P
- Object ID = an active employee
- Reporting period = all
- Transfer mode = Insert
- Receiving system:
Receiving partner No = DCRCLNT300 (logical system created in WE20)
Message type = HRMD_ABA
And everything looks fine in R3.
In CRM, using trans. WE05, we can see that the iDoc is created, apparently without problems with status 53 - "Applicaton document posted" but the business partner is never created.
Did we miss some configuration steps?
Should we do something more after see the iDoc in CRM to create BP?
Thanks in advance.
Alda

hi pratk bhai,
ya i have done the same setting what Ada has mentioned eariler,
and as of your suggestion to maintatin the mandatory infotype, i have even done tht,
after running RHALEINI in R3, the status is all green here.
when i run the tcode BD87 to check the Idoc status its showing fine (Error free).
now, through tcode se38 the report CRMHRALE_CENTRAL_PERSON shows all the employees as status green,,
but the partner number is not getting generated. ( i have used HRALX-PNUMB= 3 (Prefeexing the number range coming from R3)).
kindly advice me what should be done in order to generate a BP number for the replicated HR Employee.
best regards,
Madhup

IDoc Status 02 ( Could not find code page for receiving system )

Hi All,
I am getting Idoc status 02 when I am trying to send IDocs from ECC to PI system ( Production ).
Error description.
Could not find code page for receiving system
Message no. E0266
Diagnosis
For the logical destination PIP001, you want to determine the code page in which the data is sent with RFC. However, this is not currently possible, and the IDoc cannot yet be dispatched.
Procedure for System Administration
Possible causes are:
1. The entry no longer exists in the table of logical destinations.
2. The target system could not be accessed at runtime.
3. The logon language is not installed in the target system.
4. In the destination system, no logon language is maintained
Please help.
Thanks - Vinay.

Hi Vinay,
Status 02 occurs when data is not passed to port suceessfully. Check the RFC desination is working fine and your able to connect to target system and also check correct port is assigned.
Regards,
Vinod.

IDOC STATUS 29 to 68

Hi all,
Customer request is change idoc status from 29 to 68.
68 = no further processing inbound side
31 = no further processing outbound side
if i change status of idoc from 29 to 68 using Fn module IDOC_STATUS_WRITE_TO_DATABASE
Data of idoc is vanishing.
I observed that if i change status of idoc from 29 to 31 then there is no data loss in idoc with same Fn module.
Is there any way to change idoc status from 29 to 68 without losing the Idoc data.
anyway for both 68 & 31 meanings are same , but customer requires 29 to 68.
if u have any idea please suggest me.

Hi Suneel,
If the program does't exits then try this ...
DATA: L_EDIDC_TAB       LIKE EDIDC      OCCURS 1 WITH HEADER LINE,
      L_IDOC_STATUS_TAB LIKE BDIDOCSTAT OCCURS 1 WITH HEADERLINE,
      L_IDOC_CONTROL    LIKE EDIDC.
    L_IDOC_STATUS_TAB-DOCNUM = <your IDoc number>.
    L_IDOC_STATUS_TAB-STATUS = '68'.
    APPEND L_IDOC_STATUS_TAB.
    CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
         EXPORTING
              IDOC_NUMBER               = L_EDIDC_TAB-DOCNUM
         IMPORTING
              IDOC_CONTROL              = L_IDOC_CONTROL
         TABLES
              IDOC_STATUS               = L_IDOC_STATUS_TAB
         EXCEPTIONS
              IDOC_FOREIGN_LOCK         = 1
              IDOC_NOT_FOUND            = 2
              IDOC_STATUS_RECORDS_EMPTY = 3
              IDOC_STATUS_INVALID       = 4
              DB_ERROR                  = 5
              OTHERS                    = 6.
Regards,
Ferry Lianto

Idoc Status 53 but Applicaton document not posted message type PORDCR

Hi,
Need your help. I am using message type PORDCR and Basic type PORDCR04 to create Purchase order through inbound Idocs. I am getting correct status '53' Application document posted along with the new Purchase order number. When I am trying to see it in EKKO / or ME23N I could not see this purchase order.
Can anyone please let me know what could be the possible reason for document is not getting posted in in database but Idoc status is correct.?
Thanks in advance.
Regards,
Deepak

check SM13 and ST22 to see if there are any errors there

IDoc status is not coming to '03'

Hi,
When I run my program, it is giving IDoc status as 30. When I go and see in WE05, it is showing same status. It's not getting 03 status.
I know that we can bring the status to 03 by executing the program RSEOUT00. But I want this to come from my program where I have used MASTER_IDOC_DISTRIBUTE function module.
Generally, even though I get status 30 in the program, when I go and see in WE05, 03 status is displayed. But I don't know what happend this time, it is showing 30 status even in WE05 also.
Please tell me what could be the reason.
Regards,
Suman.

Hello,
Check if there are any dumps in the system
Or
if there are any authorization issues.
IF there are dumps, then the system usually stops autoprocessing the idocs and you might need to schedule the program at periodic intervals to get the idoc in status 03.
Thanks,
Sushil Joshi

IDOC status 03 but no XML generated

Hi Experts,
I am facing a problem related to idoc i.e. I am getting idoc status 03, still no XML created at the server directory.
Scenario is: A custom idoc is created with a z report which selects data & send idoc as an XML file in the server directory
IDOC (the first \ represents root as it is a unix server, 2nd \ is a saparator nd then IDOC is a folder to save XML files). Folder IDOC is having all permission(777). When i send idoc using the report is fives status 30 & after that when process it through BD87 it gives a status message 03.
I checked the partner profile, port etc. Even in port access test is OK.
I even tried putting directory as //IDOC , /IDOC but then no access possible error came. only work with
IDOC & gives status message 03.
But no idoc is reaching at the other end i.e.
IDOC.
Can anyone tell me how to fix this problem. Is the problem at SAP end of Unix end.
Regards,
Nik

Hi,
Check the Port configuration.In this case mostly problem form port configrations only.
Check Directory,Outbound file paramters in the port configuration.
Thanks,
radha.

IDOC Status, Tracking in SAP PI/PO Single Stack

Hi All,
My PO version: 7.4, SP4. I am not sure my questions below are still a limitation in current PI/PO single stack systems, and hence requesting your help for the same.
1) Is there a way we can track outbound idocs in SAP PI/PO single stack similar to PI abap stack IDX5? ( Note:- I couldn't find any option in IDOC monitoring in single stack SAP PO 7.4, SP4)
2) IDOC status is always 0 in SAP PO 7.4 single stack IDOC monitoring. I am not sure if this status is just specific to my PO system. Any setting needs to be applied?
ps: Please post only relevant answers/solutions
Thanks,
Praveen Gujjeti
Message was edited by: Praveen Gujjeti

Hi All,
As per SAP help: Comparison of IDoc Adapter (IE) and IDoc Adapter (AAE) - SAP NetWeaver PI Reference Documentation - SAP Library idoc status and tracking not supported in current PO versions. May be SAP will add this feature in upcoming PO versions
Auditing, Monitoring ,and Tracing Functions
Attribute/Feature
IDoc Adapter (IE)
IDoc Adapter (AAE)
ALE Audit
Supported
Supported
IDoc tracing
Supported (transaction IDX5)
Not supported
IDoc monitoring
Transaction IDX5
Integration with channel monitor and message monitor (as part of Advanced Adapter Engine monitor)
Status tracking -SYSTAT
(analysis and further processing of messages that have not been processed)
Not supported
Not supported
RFC monitoring
Supported
Not supported
Message persistence in the IDoc adapter
Supported
Message correlation information can be stored in IDoc adapter.
Not supported.
Message is persisted in messaging system with correlation data persisted in adapter.
Regards,
Praveen Gujjeti

Idoc status is in 12, but it does not reached to Target.

Hello Experts,
We are facing a problem with outbound Idoc.
The problem details are as below.
We have generated an Idoc(Without message Control) and dispatched it to external vendor. Idoc status is 12, when we check it in midleware(seebeyond) it does not reached.
There is no error with RFC and Port definition.
Could you please suggest us whats wrong with it or where its gone.
Thanks in advance.
BR//
Raghu

Hi Siva Prakash,
Thanks for your response.
There is no error with RFC, its working perfectly.
BR//
Raghu

PI RWB-Messages stuck in Delivering Status

Hi Experts,
PI 7.1
Scenario: Proxy to Mail (Outbound)
QOs: Exactly Once in Order
We are facing problem while sending messages to receiver.
Messages are stuck in Delivering status and the messages followed by them are going into holding status.
Messages in Delivering status has no audit logs.
Issue has started couple of months back. We took restart initially to rectify the barrier but it is happening again. This is repetitive issue and we are looking for permanent fix. Restart is not preferred resolution as it is a production system. Please suggest how can we overcome it? It would be a great help.

Hi Hardik
I've blogged about this issue recently. Please check out the blog:-
http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/03/27/handling-and-preventing-messages-stuck-in-to-be-delivered-status
Rgds
Eng Swee

Idoc status 53.Yet application data is not posted.

IDOC status is 53. But application data is not partially posted.iam generating 2 idocs, one for type INFREC01 and other for COND_A01. iam Generating IDOC using a fm IDOC_INBOUND_ASYNCHRONOUS. purchase info record is posted succesfully. but condition info record is not posted.
for both the idoc its shows green status-53. moreover data in EINA EINE KONH KONP is updating, but its not displayed in transaction ME13.
Kindly help me.

Hi,
Check the config stuff if you are usng the right IDoc...See partner profiles and the message types.
thanks

I stuck at Idoc status 26

Similar Messages

Maybe you are looking for