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.

Similar Messages

IDoc - XI (BPM) - File, Successful status but no message generated

Hi,
I am trying to do Sravya's blog for BPM correlation.
I am sending IDocs from R/3 system to XI, even though message shows successful status there is no message is created on the receiver.
One strange thing is when I go into the SXI_MONITOR -> process (radio button) -> messages -> PE is taking me to the <b>Inbound Queue</b> not to the workflow log.
The next button is outbound status has green flag (message scheduled on outbound side).
Could you please help me resolving this problem.
Thanks
Kiran
Message was edited by: Kiran Reddy

Thanks and that solved the problem.
Now my multi source mapping is not working any ideas ?

Error handling problem with outbound idoc status 02 and XML HTTP Port

I set up an ALE scenario to send master data out of SAP via an XML HTTP port. All goes well until the idoc receives error 02.
It looks like idocs in this error status with the use of an XML HTTP port can not be reprocessed via the standard SAP techniques. Program RBDAGAIN takes them out of the list for reprocessing (even though the connection is back up and running).
Is there any solution to still use the standard ALE error handling ?

Hi Karin,
Looks like based on note 701597, you can only reprocess these idocs manually via a workitem. I qouted the relevant text below:
3. Error handling with status '02':
An HTTP IDoc in status '02' should not automatically be sent once again.
Up to now, the RBDAGAIN report was used to resend incorrect IDocs.
However, this report was adjusted and now deletes all IDocs in status 02
to be routed to a HTTP port from the list of selected IDocs. IDocs to a
HTTP port in status '02' should only be sent manually via a work item.
Regards:
Rex

How to change Idoc Status

Hello Friends,
How can i change status of Idocs from 02, 51, 64 to below status
31 for Outbound idocs
68 for Inbound Idocs
I have searched the forum, and many people are advising to use BD87 to perform it.
I have checked BD87 and i am unable to find option to change status to 31 or 68
There is some thing similar
BD87 -> Give input and Execute -> Goto -> Transactional RFC -> Convert Idoc Status -> but here there is no option to give final status 31 or 68. Even though i have executed, but status is not changed.
Can any one please let me know what is correct path (or) any thing wrong ?
Thank
Tony

for inbound run RBDAPP01 / RBDMANI2 depending on status 64 or 51, outbound RBDAGAIN for 02, uncheck background processign at the bottom of the screen, and on the next screen press Delete.

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

IDOC status on 03 but not recieved on target system

Hi,
We are recieving inbound idoc from external system and processing Inbound IDOC on SAP system, after processing inbound idoc on SAP we are sending status outbound idoc to external system.
The above functionality was working fine before upgradation.
after upgradation we have recreated RFC (TCP/IP) connection, updated at port level and also configured the new SAP system details ( sid, Hostname, service programsname...) on external system correctly.
Now we are recieving inbound idoc from external system on upgraded system,after processing inbound idoc details on SAP system, generating outbound idoc from SAP and it reaching the outbound prot sucessfully on 03 status with green light.
But external system is not recieving the IDOC. How to find why idoc is not reaching external system even though it is sucessfully passed at outbound port level with green light status 03.
We have also checked the SM58 for TRFC entries but we didn't identified any entries on SM58. Please help us on this issue
Thanks,
Raju

Hi Raju,
As mentioned by The specified item was not found., the one common problem for the IDocs not being sent might be a missing COMMIT WORK. I.e. when using the standard SAP API's for sending outbound IDocs, SAP actually creates the IDoc and registers an update function for sending the IDoc out. So without the COMMIT WORK, the IDoc usually exists on the database (implicit or database commmits), is in status 03, but hasn't been sent out and cannot be found in the outbound RFC queue (because SAP never tried to send it).
If you're convinced that a COMMIT WORK is happening (and after trying to send the outbound IDoc) then I'd try the following: Replace the used RFC destination (or re-define it temporarily) with one that points to the same system from where you're sending. If you don't see the IDocs as inbound IDocs or in the outbound RFC queue, the sending never happens. (Ok, might be a moot point if you completely trust your external system, but usually it's good to even rule out the most unlikely causes - if it's simple.)
So if this didn't help, maybe you can provide some further insight into how you're creating/sending the outbound IDocs. This could help us in trying to get some answer, but for a starter the COMMIT WORK mentioned by The specified item was not found. is in my opinion the best candidate.
Cheers, harald
p.s.: Even if you're using ALE, I don't think it could be due to anything in your distribution model as mentioned by The specified item was not found.. If you wouldn't have setup the distribution model, the SAP API's should create a master IDoc in memory and then no communication IDocs (since there's no recipients or due to filtering) and thus there should be no outbound IDocs on the database.

CRMXIF_ORDER_SAVE_M02 Idoc status 53, but no transaction created in CRM

Hi,
Via transaction WE19, I have filled idoc CRMXIF_ORDER_SAVE_M02.
When I click on "standard inbound", the idoc is generated and get the status 53 which seems to be OK, but no Transaction is created in CRM.
Any idea ?
I've tried to fill more fields of the idoc structure but nothing changed.
Is there a step I am missing ?
What's the use of these fields in the idoc structure ?
APPL_SNAME
DATAX
Thanks for any help !
Aussie

Hi Aussie,
In transaction WE19 for the Idoc CRMXIF_ORDER_SAVE_M02.
It has no problem with data instead check the receiver Port, sender port, Partner No,
Partner type, role . If these didnot match then the data will not be reflected in CRM.
regarding APPL_SNAME: it is not relevant with the problem, its a structure of teh description.
Please see the ports.
have a nice day!!
receiver Port , sender port, Partner No, type, role Partner profile not maintained
Name of structure for the technical description
With regards,
Lakshmi Narayana

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 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

Idoc in 53 status but not processed completely. Missing authorisation error

Hi ,
Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
They got below warning message when I checked in WPER transaction code.
" Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
These IDOCu2019s are processed via user background. Not sure why we have authorisation issues as this user has SAPALL. Any ideas?
Thanks
Deepthi.

done.

Idoc in 53 status but not processed completely.

Hi ,
Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
They got below warning message when I checked in WPER transaction code.
" Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
Any idea what might be the reason?
Thanks
Deepthi.

Hello,
This seems to be an Authorisation issue, Kindly check for Purchasing Group 110, who are all assigned Buyers...
Then for those Buyers.. you can check what authorization is missing from Su53..
Compare with those who has authorisation to create PO Vs who does not have ..
you will have to provide the same authorisation to those users
Thanks and regards
PJ

IDOC status 30 but partner profile is set to send immediately (04)

Hi guys,
I have a problem with idocs not being sent immediately... The outputs, the EDI partner profiles are all set up correctly...
it is configured to send immediately however, it's not doing so... prior to upgrade to ECC 6.0 it's working fine... now its not...
However, in BD87 thru manual release of IDocs, it is working fine...
Is there any changes to ECC 6.0 for this matter? or is there anything that needs to be set up other than those mentioned above in order for it to work in ECC 6.0?
Thanks a lot!

Mark, have you looked at the OSS notes? By 'IDOC status 30' it finds 300+ notes, this is really a wide-spread issue.
The most recent one is 150202, which actually recommends collecting the IDocs instead of having "send immediately" because it saves the RFC resources. This is not really an ABAP issue, so you might want to discuss this with your Basis admin.
Also, from my experience, even with "mission critical" processes the users, in fact, never feel any real difference between "immediate" and 5-10 min. Sometimes (due to a technical problem, for example) nothing goes on for 30+ min. and no one even notices.

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 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

IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

Hi All,
I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
Error Detail :
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
This error can have several reasons:
The segment ZPROSEG is assigned to a group whose header segment does not occur.
The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type PROACT01 (extension PROACTEX).
Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
Below is the Details of the Steps which I have followed:
1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
Here when I run syntax check warning appears "No predecessors exist". I am not sure if its okay!!
3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
DATA segnam(27).
READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
IF sy-subrc NE 0.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
APPEND dedidd.
ENDLOOP.
ENDIF.
Finally ran transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
Looking forward for your reply.
Many thanks in advance.

Hello,
Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
lv_index = sy-tabix. " <<--
ADD 1 TO lv_index. " <<--
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
*APPEND dedidd.
INSERT dedidd INDEX lv_index. " <<---
ENDLOOP.
Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

IDOC status 03 but no XML generated

Similar Messages

Maybe you are looking for