XML IDOC post to R/3 Via WAS - want to see error content with JavaScript

Hi,
I am posting XML IDOCs to our R/3 system via a webpage that I have built with JavaScript. I am posting to the WAS, which is configured to read the XML IDOC with SAP's standard class handler CL_HTTP_IDOC_XML_REQUEST. We are on basis 620 support pack SAPKB62041.
In my webpage, I have the JavaScript code set to read the status and statusText so I can see the response from WAS when I post my XML IDOC. However, I am getting back very generic information when I encounter a 409 error. THe statusText is always "input_not_found". So I debugged the class handler code and found that SAP is returning back the more descriptive error info in HTML format.
I ran a packet sniffer to see what WAS returns and the info looks like this:
<html><head><title>IDoc-XML-inbound not ok</title><h1>IDoc-XML-inbound not ok</h1></head><body>
E:Table Lookup Error:300 Cannot map value for field MESCOD in table ZFI_IF_IDOCORG using values
SNDSAD = |TE| and RCVLAD = |GL| and MESTYP = |ACC_DOCUMENT|</body></html>
I want to know how I can get my webpage to read this HTML info and store that into an alert so I can read this text that I'm returning back to the HTTP post.
This is how my script looks. I'm using IE6.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
     <title>Test XML</title>
<SCRIPT ID=clientEventHandlersJS LANGUAGE=javascript>

</SCRIPT>
</head>
<body>
<BR>
This page posts to
<BR>
http://some_server:1089/sap/bc/zxml_idoc?sap-client=200&sap-language=EN
<FORM name=xmlform method=post >
<P><TEXTAREA style="WIDTH: 623px; HEIGHT: 369px" name=xmlData rows=23 cols=77>
</TEXTAREA>
<P>
<INPUT type="button" value="Submit XMLHTTP" id=XMLHTTPButton name=XMLHTTPButton
LANGUAGE=javascript onclick="return XMLHTTPButton_onclick(document.xmlform.xmlData.value)">
</form>
Previously with this class handler, SAP returned the detailed info back to the "alert(xmlhttp.statusText)" and I had no problem seeing the return info. But now they have decided to format it in HTML and I don't know how to view this text since it has no ID on it to pull this into an alert box.
If anyone has any ideas, please let me know.
Thanks,
Andrea

Ok!
I have solve the problem. So, I was trying to connect via SSO within an user that was not registered in R/3 and I forgot it.
Sorry for the inconvenience.

Similar Messages

I was getting email notification (at my yahoo account) when my phone was located, that has stopped. I was wanting to see why. I would like the notifications to continue.

I was getting email notifications (at my yahoo account) when my phone was located. This has stopped. Is there a way to restart the email notifications?

If you truly change your existing Apple ID's email address to a new email address, follow these instructions: iOS 7: If you're asked for the password to your previous Apple ID when signing out of iCloud
If you created a whole new Apple Account because you couldn't access the old one after being hacked, you will need to contact the Apple Account Security Team. Apple ID: Contacting Apple for help with Apple ID account security

Loading Invoice XML IDoc with digital signature via XI into R/3

Hi,
I received an Invoice XML IDoc with digital signature via Mail (for test purposes) and want to load it via XI into an R/3 systeme.
My idea is to load the Invoice XML IDoc file via the File Sender Adapter into XI and send it to the R/3 system via the IDoc Inbound adapter.
Due to the digital signature the file looks like this:
0 S      *H÷
   D0 @   1 0       +      0 '      *H÷
      0 0 û      etc.
When I load the file like this with the File Sender Adapter, an error message occurs in the XI Monitoring as the XML Parser cannot read the file due to the digital signatur (as expected).
Has anybody an idea how I can configure the File Sender Adapter Communication Channel to be able to load only the XML IDoc and ignore the digital Signature strings?
Thanks in advance for your support.
Alex

BTW
do use the second way you need:
Security Settings for the Sender Mail Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/27/c0524257a1b56be10000000a155106/content.htm
and
Key Storage Service
http://help.sap.com/saphelp_webas630/helpdata/DE/e9/a1dd44d2c83c43afb5ec8a4292f3e0/content.htm
apart from adapter module config
Regards,
michal

Receiving binary IDOC via Queue and convert it to XML-IDOC

Hello,
we are focusing the following scenario:
We receive an plain, binary IDOC in a MQSeries Queue. We want to pick it, transform it and place it into R/3 (of course using XI 3.0). Afterwards the other way around.
I know the Howto for the ABAP mapping from XML-Idoc to plain IDOC. This may also work for our scenario. Do you agree?
The other way around is more difficult. I assume that - since the IDOC adapter resides in the ABAP stack - we cannot re-use an existant adapter module in the JMS adapter. Right?
I heared about JCO capabilities of "xmlizing" Idocs - but did not find hints within the javadoc. Anyway, would this really be the preferred way - writing an user exit for the adapter using JCO - to handle this? There must be a way to do it better, must it not?
How did you guys face this problem - I think its a common one...
Any starting points for a discussion are appreciated....
Greets,
helge

Hi Helge,
For the conversion of the incoming flat message, one could imagine a similar ABAP mapping as the one described for the XML->flat message conversion. The function module IDX_IDOC_TO_XML could be a good starting point for your search.
To perform conversions in the Java stack (e.g. in an adapter module) might be a quite complex task since you first have to get the IDoc metadata. And there you cannot reuse existing function modules.
Best regards
Joachim

XML Publisher post-processing error 'java.io.FileNotFoundException'

Hi,
We are getting following XML Publisher post-processing error while running XML Publisher report.
It was working earlier but suddenly its erroring out.
[9/07/10 9:00:17 PM] [OPPServiceThread1] Post-processing request 559655.
[9/07/10 9:00:18 PM] [39177:RT559655] Executing post-processing actions for request 559655.
[9/07/10 9:00:18 PM] [39177:RT559655] Starting XML Publisher post-processing action.
[9/07/10 9:00:18 PM] [39177:RT559655]
Template code: XXHPOXPRRFLR
Template app: XXH
Language: en
Territory: 00
Output type: PDF
[9/07/10 9:00:18 PM] [UNEXPECTED] [39177:RT559655] java.io.FileNotFoundException: /apps/oracle/DEV/inst/apps/DEV_hlt439erplap001/logs/appl/conc/out/o559655.out (No such file or directory)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:106)
     at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:274)
     at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:173)
[9/07/10 9:00:18 PM] [39177:RT559655] Completed post-processing actions for request 559655.
Please help me out to resolve this issue.
Thanks & Regards,
Sagarika

Hi,
java.io.FileNotFoundException: /apps/oracle/DEV/inst/apps/DEV_hlt439erplap001/logs/appl/conc/out/o559655.out (No such file or directory)Most probably this file is not created (since no changes have been done recently, so definitely it is not a permission issue), and if there are any log files generate at the client side it should help in investigating the issue.
Thanks,
Hussein

Starting new database LUW inside ABAP during IDoc posting

Hi all,
During posting of an inbound IDoc, I am trying to update my Z-table in user-exit. I want to do it regardless of the result of IDoc posting. The problem is: if IDoc posted successfully - table is updated because COMMIT WORK is called at the end of the posting, however, if IDoc not posted - ROLLBACK WORK is called and table is not updated. So, my aim now is to commit the update of Z-table in any case, but it is the only thing that should be committed - no other prior update FMu2019s should be committed.
I'm aware about the following thread
http://forums.sdn.sap.com/thread.jspa?threadID=1884700
Author of this thread says that he solved a problem by means of RFC and STARTING NEW TASK. But ABAP help says
that starting asynchronous RFC triggers immediately a database commit in the calling program (which is unacceptable because all prior update FMu2019s will be committed ). I've checked and it is really the case.
From my point of view SET UPDATE TASK LOCAL with COMMIT WORK should work in such kind of tasks, but in case of IDoc processing the whole process runs in a local update (see SET UPDATE TASK LOCAL in FM 'IDOC_INPUT'), so writing once again SET UPDATE TASK LOCAL has no effect.
I tested SUBMIT statement as well. It had no effect and then I found out from ABAP help that SUBMIT ... AND RETURN starts new SAP LUW, but NOT a DB LUW. That is if I update my Z-table in the program called by SUBMIT - all ROLLBACK statements still affect my Z-table update.
Is there any simple solution? Please suggest.
Thanks in advance!

Hello,
Try SUBMIT VIA JOB.....
Sample Code
call function 'JOB_OPEN'
exporting
jobname = name
importing
jobcount = number
exceptions
cant_create_job = 1
invalid_job_data = 2
jobname_missing = 3
others = 4.
if sy-subrc = 0.
submit z_idoc_create_process_order and return
via job name number number
with p_aufnr = it_header1-aufnr
with p_werks = it_header1-werks
with p_autyp = c_autyp
with p_auart = it_header1-auart
with p_dispo = it_header1-dispo
with p_opt = c_opt
with p_mestyp = c_mestyp.
if sy-subrc = 0.
call function 'JOB_CLOSE'
exporting
jobcount = number
jobname = name
strtimmed = 'X'
exceptions
cant_start_immediate = 1
invalid_startdate = 2
jobname_missing = 3
job_close_failed = 4
job_nosteps = 5
job_notex = 6
lock_failed = 7
others = 8.
if sy-subrc 0.
endif.

XML IDOC to Native IDOC Conversion

Hi,
We have a scenario, where we need to convert XML idoc into native idoc and write to a file. I am doing this based on
How To Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0.
When I first executed the scenario, I was getting the following error
Z_ABAP_MAPPING_IDOC_TO_FLAT (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.
After including the try-catch block, now i am just getting a blank file without any conversion.
Can anyone help me on this?
Regards,
Ravi

Hi,
It looks to be error in ABAP mapping
To test ABAP mapping in XI use the transaction SXI_MAPPING_TEST after creating a little scenario in the directory.
Or even you could do this with below sample code
Lets create one ABAP mapping class with the method IF_MAPPING~EXECUTE
data: obj type ref to zcl_abap_mapping_test.
data: source type xstring,
result type xstring.
data: param type ref to IF_MAPPING_PARAM,
trace type ref to IF_MAPPING_trace.
create object obj.
try.
CALL METHOD obj->IF_MAPPING~EXECUTE
EXPORTING
SOURCE = source
PARAM = param
TRACE = trace
IMPORTING
RESULT = result.
CATCH CX_MAPPING_FAULT .
ENDTRY.
This is a link very useful for ABAP Mapping :
http://help.sap.com/saphelp_nw04/helpdata/en/86/8280ba12d511d5991b00508b6b8b11/frameset.htm
Or may be think this exception you need to catch it in the ABAP..
This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
just cross verify with this guide-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
Thanks
swarup

Inbound IDOC Posting

I am developing a function module in ECC that will be used to post inbound IDOC for customer creation DEBMAS07
The logic is as follows -
The function receives an IDOC structure
It then invokes function module 'IDOC_INPUT_DEBITOR'
IDOC_INPUT_DEBITOR takes care of creating a new customer in table KNA1. But I was expecting IDOC_INPUT_DEBITOR to also handle the IDOC posting. This way I can go to WE02 and see a new IDOC record. What am I missing? Is there some more code I need to write after the function module call?
Thank you.
* IDOC structures for using ALE
     data       lc_no_display         type bdwfap_par-inputmethd value ' '.
     data       lt_idoc_control       type standard table of edidc.
     data       ls_idoc_control       type edidc.
     data       lt_idoc_data          type standard table of edidd.
     data       lt_idoc_data_knvi     type standard table of edidd.
     data       lt_idoc_status        type standard table of bdidocstat.
     data       ls_idoc_status        type bdidocstat.
     data       lt_return_variables   type standard table of bdwfretvar.
     data       lt_serialization_info type standard table of bdi_ser.
     data       lv_workflow_result    type bdwf_param-result.
     data       pi_idoctyp            type edi_iapi00-idoctyp.
     data       pt_segments           type standard table of edi_iapi11.
     data       lw_segments           type edi_iapi11.
     data       ls_idoc_data          type edidd.
     data       ls_e1kna1m            type zdebmas07_e1kna1m.
     data       e1kna1m               type e1kna1m.
*** CONTROL DATA
     ls_idoc_control-mandt = input-idoc-edi_dc40-mandt.
     ls_idoc_control-status = input-idoc-edi_dc40-status.
     ls_idoc_control-doctyp = input-idoc-edi_dc40-idoctyp.
     ls_idoc_control-direct = input-idoc-edi_dc40-outmod.
     ls_idoc_control-rcvprt = input-idoc-edi_dc40-rcvprt.
     ls_idoc_control-rcvprn = input-idoc-edi_dc40-rcvprn.
     ls_idoc_control-stdmes = input-idoc-edi_dc40-stdmes.
     ls_idoc_control-outmod = input-idoc-edi_dc40-outmod.
     ls_idoc_control-sndpor = input-idoc-edi_dc40-sndpor.
     ls_idoc_control-sndprt = input-idoc-edi_dc40-sndprt.
     ls_idoc_control-sndprn = input-idoc-edi_dc40-sndprn.
     ls_idoc_control-mestyp = input-idoc-edi_dc40-mestyp.
     ls_idoc_control-idoctp = input-idoc-edi_dc40-idoctyp.
     append ls_idoc_control to lt_idoc_control.
*** READ SEGMENTS
     pi_idoctyp = ls_idoc_control-idoctp.
     call function 'IDOCTYPE_READ_COMPLETE'
       exporting
         pi_idoctyp         = pi_idoctyp
       tables
         pt_segments        = pt_segments
       exceptions
         object_unknown     = 1
         segment_unknown    = 2
         relation_not_found = 3
         others             = 4.
     loop at pt_segments into lw_segments.
       case lw_segments-segmenttyp.
         when 'E1KNA1M'.
           ls_idoc_data-segnam = 'E1KNA1M'.
           ls_idoc_data-mandt = sy-mandt.
           ls_idoc_data-segnum = lw_segments-nr.
           ls_idoc_data-psgnum = lw_segments-parpno.
           ls_e1kna1m          = input-idoc-e1kna1m.
           move-corresponding ls_e1kna1m to e1kna1m.
           move e1kna1m to ls_idoc_data-sdata.
           append ls_idoc_data to lt_idoc_data.
           exit.
       endcase.
     endloop.
*** IDOC INPUT CALL FUNCTION
     data: response type zsi_create_customer_is_res_tab.
     data: response_lwa type zsi_create_customer_is_respons.
     data: lwa_error_message type string.
     call function 'IDOC_INPUT_DEBITOR'
       exporting
         input_method          = lc_no_display
         mass_processing       = space
       importing
         workflow_result       = lv_workflow_result
       tables
         idoc_contrl           = lt_idoc_control
         idoc_data             = lt_idoc_data
         idoc_status           = lt_idoc_status
         return_variables      = lt_return_variables
         serialization_info    = lt_serialization_info
       exceptions
         wrong_function_called = 1
others                = 2.

Hello Megan,
Check with the function modules
EDI_DATA_INCOMING
IDOC_WRITE_AND_START_INBOUND
Program:
RBDAPP01
I guess this would answer your query.
Regards,
TP

IDOC not to be converted to XML-IDOC

Hi
there is a setting you can make in XI so that IDOCS sent to XI from R/3 are not converted to XML-IDOC.
That parameter is XML_CONVERSION.
I found out from SAP today that this will only work if you are sending from R/3 to R/3 via XI.
But I want this to work for R/3 to ThirdParty via XI.
So SAP are saying this will not work.
OK - so does anybody have a simple XSLT I can use that will strip out the XML tags so I have a plain old IDOC ?

Hi,
1.if, so then ask him to provide SAP at target (in this case its possible)...there is no other option.(as of now SAP does't provide these kind of functionality)
2.otherwise if he required the same structure at target then go with IDoc...PI...File scenario
Please explain to your end user clearly about IDoc functionality..hope he will understand..
Rgds,
MFH

Com.sap.aii.utilxi.misc.api.BaseRuntimeException:An invalid XML character (Unicode: 0x1f) was found in the element content of the document

Hi,
I'm getting the below runtime exception during IDOC- SOAP message mapping in Integration engine.
"Runtime exception occurred during application mapping com/sap/xi/tf/<<<\\Message mapping object name\\>>>; com.sap.aii.utilxi.misc.api.BaseRuntimeException:An invalid XML character (Unicode: 0x1f) was found in the element content of the document"
I have no clue why this exception occurs. Could anyone say the reason of the exception?
Thanks!
Regards,
Gopi

Hi Gopinath
Check this thread
An invalid XML character (Unicode: 0x1d) was found in the element
Kind regards
Javi

IDOC posting error with dollar values

Hello,
We have recently started posting general ledger transactions via IDOC. We just noticed that a few of the idocs reflect a status 53 however did not create postings. When drilling into the message, it says that there were not valid line items. (meaning lines with 0 dollar value). However all of the records had valid dollar values. I have found a few notes that adress this as an issue in 46B, however we are on 4.7 and all of the suggested code fixes have been implemented already. Has anyone seen this happen?
-Jeff

1. Please check that the process code in the inbound partner profile is correct.
2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.
BR,
Alok

IDOC posted with error

Hi
working on File2 IDOC scenario..my idoc posted .. but that is red and green in SXMB_MONI... where should I check for correct the problem?

I am getting error like this :(SXMB_MONI)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please help me

IDOCType PORDCR101 : XML IDoc conversion: No known segments identified

Hello all,
I'm strugling with the mapping to the IDOC create puchase order PORDCR1.PORDCR101.
The source structure for the moment is exactly the same as the target strcuture i.e. our IDOC.
So I would not expect to much problems with this one.
However, when sending the message we get the following error in SXI_MONITOR:
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I also augmented the trace lvl to 3 and got the following in the Trace-part of TC SXI_MONITOR and
suspect it starts to get wrong already in the beginning
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Outbound IDoc-Adapter -
</Trace>
<Trace level="1" type="T">----
</Trace>
Trace level="1" type="T">Convert one IDoc</Trace> .
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore segment field: COMP_CODE</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADERX</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADERX</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOADDRVENDOR</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOADDRVENDOR
I already found the four or so other threads on the SDN website about this error and in the mean-time tried them (delete and reload the structure with IDX2, set the begin and segment-attribute to 1, make sure that the segments-names self are also mappend) but to no avail.
We just implemented two other IDOC's (DELVRY03 and WMMBID02) and they arrive at SAP without problmens.
Hope you have form ideas to get me out of this one.
Tnx and best regards.
Bart.

Hi Bart,
We had a similar problem.... It took us 2 days to find out what the problem was... Nothing on SDN was helpfull so far... First we incremented the trace level of XI to see the debug messages... Then we saw that certain segments could not be identified and are ignored, others not...
So further investigation in IDX2 to the specific IDoc with problems showed us a list with all used segments and their versions. Some segments had only 1, others had more versions....
So we could identify the problem as a segment version problem. It seemed that our IDoc Communication Channel took not the most recent version. So we changed the "Segment Version" to the most recent one and the problem was solved!
Please reward points if this was usefull to you...
cheers!
Pedro

XML-IDOC inbound for ECC 6.0

Hi,
in a ECC 6.0 only landscape we would like to process XML-IDOC in inbound. For outbound we have already create a XML-IDOC port... but I don't be able to find it for inbound.
How can I do it ?
Regards.
Ganimede Dignan.

Hi,
it's quite simple, if you have a system base on NW 2004s or newer you have all that you need but take in mind XML-IDOC it's not a Free XML .... it's an XML structure as an IDOC.
In WE21 TCODE you can set-up and "XML File" port or and "XML Http" port.
In anyway you can parser each XML by ABAP custom code.
read olso some of my old notes....
IDOC_INBOUND_FROM_FILE => called within report RSEINB00
IDOC_XML_FROM_FILE         => not called by any report (on release 4.6c)
I have used fm IDOC_XML_FROM_FILE already many times to manually transfer XML-IDocs from one SAP system to another.
Given the fact that report RSEINB00 is quite simple (see below) you could create your ZRSEINB00 for processing XML IDocs.
The reports can be scheduled in background to process the inbound IDocs continuously.
REPORT RSEINB00 MESSAGE-ID E0.
* EDI inbound processing (main program to be scheduled)
* This program processes one file with one ore more intermediate
* documents. When an error occurs, a message will be send via workflow
* processing.
* The index of the last successfully processed record of the file is
* always written to the table EDFI2.
* If the program is startet again for this file, the table EDFI2 will
* be interpreted and the processing will start at the next record.
* PARAMETERS
PARAMETERS:
* directory + name of file that has to be processed
P_FILE LIKE EDI_PATH-PTHNAM DEFAULT '/usr/sap/.../SYS/global/...'.
* DATA
DATA:
G_MESSAGE_FIELDS LIKE EDIMESSAGE.
* MAIN PROGRAM
START-OF-SELECTION.
* do inbound processing from file
CALL FUNCTION 'IDOC_INBOUND_FROM_FILE'
       EXPORTING
            FILE_NAME            = P_FILE
       EXCEPTIONS
            FILE_OPEN_FAILED     = 1
            MARKER_TO_BE_DELETED = 2
            READ_FILE_FAILED     = 3
            IDOC_NOT_STORED      = 4
            FILE_DELETE_FAILED   = 5
            MARKER_MODIFY_FAILED = 6
            EVENT_CREATE_FAILED = 7
            FIRST_RECORD_INVALID = 8
            INVALID_RECORD       = 9
            OTHERS               = 10.
IF SY-SUBRC 0.
* fill message fields for exception handling from system fields
    MOVE-CORRESPONDING SY TO G_MESSAGE_FIELDS.
* error handling using the 3.0 business workflow
    CALL FUNCTION 'IDOC_ERROR_WORKFLOW_START'
         EXPORTING
              DOCNUM                  = 0
              EVENTCODE               = 'EDIM'
              MESS                    = G_MESSAGE_FIELDS
         EXCEPTIONS
              NO_ENTRY_IN_TEDE5       = 0
              ERROR_IN_START_WORKFLOW = 0
              OTHERS                  = 0.
* do not care for exceptions here
    COMMIT WORK.
* abend message for RFC
    MESSAGE ID     G_MESSAGE_FIELDS-MSGID
            TYPE   'A'
            NUMBER G_MESSAGE_FIELDS-MSGNO
            WITH   G_MESSAGE_FIELDS-MSGV1 G_MESSAGE_FIELDS-MSGV2
                   G_MESSAGE_FIELDS-MSGV3 G_MESSAGE_FIELDS-MSGV4.
ENDIF.
* end of report
there are some function modules to accomplish this.
IDOCS_OUTPUT_IN_XML_FORMAT
IDOCS_OUTPUT_VIA_XML_HTTP
for inbound processing,
IDOC_INBOUND_XML_SOAP_HTTP
IDOC_INBOUND_XML_VIA_HTTP
IDOC_XML_FROM_FILE
IDOC Adaptor,
IDX_IDOC_TO_XML
Extended table maintenance, to display IDOC in XML format with XSL,
IDOC_XML_DISPLAY
IDOC_XML_TRANSFORM

IDOC POsting Error: Transition no. OBJ_SYS is blocked by another user

Hi Experts,
I m sending the XML from a third party system into SAP using XI as middleware for IDOC posting (FB01).
I m getting an error <b>Transition no. <xx> is blocked by another user</b> while sending intercompany and cash applications. SAP is unable to process such XML directly.
But if i login to SAP and mannually post the IDOC, it is getting posted successfully.
Any idea what may be the cause?
Useful answers will be rewarded for sure.
Regards
DhanyaR Nair

Hi Dhanya,
        In your inbound idoc processing program, pls do use the lock mechanism for the FI document which you are processing and if it cannot be locked then keep it on wait for sometime and check for the same.
        If its a standard program check whether it can be done in XI.
      When SAP is locking the transaction it will be unlocked after the commit work and hence its happening.
The reason why you may not be getting this in individual processing is that you are doing the same thru a single session. And the lock if am not wrong is happening in table level and not in record level.
Cheers
JK

XML IDOC post to R/3 Via WAS - want to see error content with JavaScript

Similar Messages

Maybe you are looking for