Idoc Processing Error - Communication error calling XI interface
Hi All, We in the middle of our upgrade from IS-PS-CA 472 to ECC6 and are facing issues processing old Idoc's with status 64 via BD87 the error message says that "Communication error calling XI interface". We have not implemented XI at this point in time.
Can anyone please advice why this is happen is this something to do the SAP version.
Please help.
Rgds
Saj
Can you provide the message number.
Reddy
Similar Messages
-
Inbound IDOC processing, error duplicate key
We want to retrieve certain order-idocs in our system, before they are processed, to change AND insert segment data.
Flow we use in our current program
- DOC_STATUS_WRITE_TO_DATABASE
to change the status of the idoc (ok) (status 69)
- EDI_DOCUMENT_OPEN_FOR_EDIT (ok)
- EDI_CHANGE_DATA_SEGMENTS (ok)
- EDI_DOCUMENT_CLOSE_EDIT => not ok
This program gives SAPSQL error
Via debugging, we see that a new idoc number is
called (save as backup idoc ?), but we want the
current IDOC to be processed.
The system wants to insert in EDID4 => dump :
"Use an ABAP/4 Open SQL array insert only if you
are sure that none of the records passed already
exists in the database."
( I prefer to use these standard functions, in stead of just deleting and inserting into "EDID4" )
regards,
answers will be rewarded.
code extract
INCLUDE ZBE01458_TOP.
INITIALIZATION.
V_EDIT_STATUS = '69'.
V_PROCESSED_STATUS = '32'.
start-of-selection.
clear t_edidc. refresh t_edidc.
SELECT * FROM EDIDC into table t_edidc
WHERE DOCNUM in S_docnum
and mestyp in S_mestyp
and idoctp in S_idoctp
and credat in S_credat
and rcvpor in S_rcvpor
and rcvprt in S_rcvprt
and rcvprn in S_rcvprn
and sndpor in S_sndpor
and sndprt in S_sndprt
and sndprn in S_sndprn
and status in S_status.
loop at t_edidc.
move t_edidc-docnum to v_docnum.
refresh v_status.
V_STATUS-docnum = V_DOCNUM.
V_STATUS-status = V_EDIT_STATUS.
clear EDIDS.
select single * from EDIDS where docnum = v_docnum.
if sy-subrc = 0.
MOVE EDIDS-STACOD to V_STATUS-STACOD.
endif .
APPEND V_STATUS.
PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING V_DOCNUM.
changing part for DEDIDD "idoc data
PERFORM OPEN_IDOC_FOR_CHANGE.
PERFORM CHANGE_IDOC.
PERFORM CLOSE_IDOC_FOR_CHANGE.
refresh v_status.
V_STATUS-docnum = V_DOCNUM.
V_STATUS-status = V_PROCESSED_STATUS.
APPEND V_STATUS.
PERFORM CHANGE_IDOC_STATUS tables V_STATUS
USING V_DOCNUM.
endloop.
*& Form OPEN_IDOC_FOR_CHANGE
text
--> p1 text
<-- p2 text
FORM OPEN_IDOC_FOR_CHANGE.
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
EXPORTING
DOCUMENT_NUMBER = V_DOCNUM
ALREADY_OPEN = 'N'
IMPORTING
IDOC_CONTROL =
TABLES
IDOC_DATA = DEDIDD
EXCEPTIONS
DOCUMENT_FOREIGN_LOCK = 1
DOCUMENT_NOT_EXIST = 2
DOCUMENT_NOT_OPEN = 3
STATUS_IS_UNABLE_FOR_CHANGING = 4
OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " OPEN_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC
text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC.
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
TABLES
IDOC_CHANGED_DATA_RANGE = DEDIDD
EXCEPTIONS
IDOC_NOT_OPEN = 1
DATA_RECORD_NOT_EXIST = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CHANGE_IDOC
*& Form CLOSE_IDOC_FOR_CHANGE
text
--> p1 text
<-- p2 text
FORM CLOSE_IDOC_FOR_CHANGE.
CLEAR t_EDI_DS40.
t_edi_ds40-docnum = v_docnum.
t_edi_ds40-status = '51'.
t_edi_ds40-repid = sy-repid.
t_edi_ds40-tabnam = 'EDI_DS'.
t_edi_ds40-mandt = sy-mandt.
t_edi_ds40-stamqu = 'SAP'.
t_edi_ds40-stamid = 'B1'.
t_edi_ds40-stamno = '999'.
t_edi_ds40-stapa1 = 'Changes made to idoc ...'.
t_edi_ds40-stapa2 = t_new_kunnr.
t_edi_ds40-logdat = sy-datum.
t_edi_ds40-logtim = sy-uzeit.
APPEND t_edi_ds40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
EXPORTING
DOCUMENT_NUMBER = V_DOCNUM
DO_COMMIT = 'X'
DO_UPDATE = 'X'
WRITE_ALL_STATUS = 'X'
TABLES
STATUS_RECORDS = t_EDI_DS40
EXCEPTIONS
IDOC_NOT_OPEN = 1
DB_ERROR = 2
OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CLOSE_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC_STATUS
text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
USING P_DOCNUM.
CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
EXPORTING
IDOC_NUMBER = p_docnum
IDOC_OPENED_FLAG = ' '
NO_DEQUEUE_FLAG = 'X'
IMPORTING
IDOC_CONTROL =
TABLES
IDOC_STATUS = P_IDOC_STATUS
EXCEPTIONS
IDOC_FOREIGN_LOCK = 1
IDOC_NOT_FOUND = 2
IDOC_STATUS_RECORDS_EMPTY = 3
IDOC_STATUS_INVALID = 4
DB_ERROR = 5
OTHERS = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
else.
commit work.
ENDIF.
ENDFORM. " CHANGE_IDOC_STATUSUrmila,
I tried this sequence : code extract follows...
I got the duplicate key errors again.
what about delete first and then insert again in EDID4 table ?
source code extract:
INCLUDE ZBE01458_TOP.
INITIALIZATION.
V_EDIT_STATUS = '69'.
V_PROCESSED_STATUS = '32'.
V_SAPCODE = 'SAPE0184'.
start-of-selection.
clear t_edidc. refresh t_edidc.
SELECT * FROM EDIDC into table t_edidc
WHERE DOCNUM in S_docnum
and mestyp in S_mestyp
and idoctp in S_idoctp
and credat in S_credat
and rcvpor in S_rcvpor
and rcvprt in S_rcvprt
and rcvprn in S_rcvprn
and sndpor in S_sndpor
and sndprt in S_sndprt
and sndprn in S_sndprn
and status in S_status.
loop at t_edidc.
move t_edidc-docnum to v_docnum.
move-corresponding T_EDIDC to WA_EDIDC.
V_STA-docnum = v_docnum.
V_STA-status = '51'.
V_STA-repid = sy-repid.
V_STA-tabnam = 'EDI_DS'.
V_STA-mandt = sy-mandt.
V_STA-stamqu = 'SAP'.
V_STA-stamid = 'B1'.
V_STA-stamno = '999'.
V_STA-stapa1 = 'Changes made to idoc ...'.
t_edi_ds40-stapa2 = t_new_kunnr.
V_STA-logdat = sy-datum.
V_STA-logtim = sy-uzeit.
V_STA-STACOD = V_SAPCODE.
PERFORM OPEN_FOR_PROCESS.
PERFORM SET_IDOC_STATUS USING V_DOCNUM V_STA.
PERFORM CLOSE_IDOC_FOR_PROCESS.
PERFORM OPEN_IDOC_FOR_CHANGE.
PERFORM PROCESS_IDOC_STRUCTURE.
PERFORM CHANGE_IDOC.
PERFORM CLOSE_IDOC_FOR_CHANGE.
refresh v_status.
V_STATUS-docnum = V_DOCNUM.
V_STATUS-status = V_EDIT_STATUS.
V_STATUS-STACOD = V_SAPCODE.
clear EDIDS.
select single * from EDIDS where docnum = v_docnum.
if sy-subrc = 0.
MOVE EDIDS-STACOD to V_STATUS-STACOD.
endif .
APPEND V_STATUS.
PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING V_DOCNUM.
endloop.
*& Form OPEN_IDOC_FOR_CHANGE
text
--> p1 text
<-- p2 text
FORM OPEN_IDOC_FOR_CHANGE.
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
EXPORTING
DOCUMENT_NUMBER = V_DOCNUM
ALREADY_OPEN = 'N'
IMPORTING
IDOC_CONTROL = WA_EDIDC
TABLES
IDOC_DATA = DEDIDD
EXCEPTIONS
DOCUMENT_FOREIGN_LOCK = 1
DOCUMENT_NOT_EXIST = 2
DOCUMENT_NOT_OPEN = 3
STATUS_IS_UNABLE_FOR_CHANGING = 4
OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " OPEN_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC
text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC.
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
TABLES
IDOC_CHANGED_DATA_RANGE = DEDIDD
EXCEPTIONS
IDOC_NOT_OPEN = 1
DATA_RECORD_NOT_EXIST = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CHANGE_IDOC
*& Form CLOSE_IDOC_FOR_CHANGE
text
--> p1 text
<-- p2 text
FORM CLOSE_IDOC_FOR_CHANGE.
CLEAR t_EDI_DS40.
t_edi_ds40-docnum = v_docnum.
t_edi_ds40-status = '69'.
t_edi_ds40-repid = sy-repid.
t_edi_ds40-tabnam = 'EDI_DS'.
t_edi_ds40-mandt = sy-mandt.
t_edi_ds40-stamqu = 'SAP'.
t_edi_ds40-stamid = 'B1'.
t_edi_ds40-stamno = '999'.
t_edi_ds40-stapa1 = 'Changes made to idoc ...'.
t_edi_ds40-stapa2 = t_new_kunnr.
t_edi_ds40-logdat = sy-datum.
t_edi_ds40-logtim = sy-uzeit.
APPEND t_edi_ds40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
EXPORTING
DOCUMENT_NUMBER = V_DOCNUM
DO_COMMIT = 'X'
DO_UPDATE = 'X'
WRITE_ALL_STATUS = 'X'
TABLES
STATUS_RECORDS = t_EDI_DS40
EXCEPTIONS
IDOC_NOT_OPEN = 1
DB_ERROR = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CLOSE_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC_STATUS
text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
USING P_DOCNUM.
CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
EXPORTING
IDOC_NUMBER = p_docnum
IDOC_OPENED_FLAG = ' '
NO_DEQUEUE_FLAG = 'X'
IMPORTING
IDOC_CONTROL =
TABLES
IDOC_STATUS = P_IDOC_STATUS
EXCEPTIONS
IDOC_FOREIGN_LOCK = 1
IDOC_NOT_FOUND = 2
IDOC_STATUS_RECORDS_EMPTY = 3
IDOC_STATUS_INVALID = 4
DB_ERROR = 5
OTHERS = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
else.
commit work.
ENDIF.
ENDFORM. " CHANGE_IDOC_STATUS
*& Form OPEN_FOR_PROCESS
text
--> p1 text
<-- p2 text
FORM OPEN_FOR_PROCESS.
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_PROCESS'
EXPORTING
DB_READ_OPTION = DB_READ
DOCUMENT_NUMBER = V_DOCNUM
ENQUEUE_OPTION = SYNCHRONOUS
IMPORTING
IDOC_CONTROL = WA_EDIDC
EXCEPTIONS
DOCUMENT_FOREIGN_LOCK = 1
DOCUMENT_NOT_EXIST = 2
DOCUMENT_NUMBER_INVALID = 3
DOCUMENT_IS_ALREADY_OPEN = 4
OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " OPEN_FOR_PROCESS
*& Form SET_IDOC_STATUS
text
--> p1 text
<-- p2 text
FORM SET_IDOC_STATUS USING P_DOCNUM P_STA.
CALL FUNCTION 'EDI_DOCUMENT_STATUS_SET'
EXPORTING
DOCUMENT_NUMBER = P_DOCNUM
IDOC_STATUS = P_STA
IMPORTING
IDOC_CONTROL = WA_EDIDC
EXCEPTIONS
DOCUMENT_NUMBER_INVALID = 1
OTHER_FIELDS_INVALID = 2
STATUS_INVALID = 3
OTHERS = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " SET_IDOC_STATUS
*& Form CLOSE_IDOC_FOR_PROCESS
text
--> p1 text
<-- p2 text
FORM CLOSE_IDOC_FOR_PROCESS.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_PROCESS'
EXPORTING
DOCUMENT_NUMBER = V_DOCNUM
BACKGROUND = NO_BACKGROUND
NO_DEQUEUE = ' '
IMPORTING
IDOC_CONTROL = WA_EDIDC
EXCEPTIONS
DOCUMENT_NOT_OPEN = 1
FAILURE_IN_DB_WRITE = 2
PARAMETER_ERROR = 3
STATUS_SET_MISSING = 4
OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CLOSE_IDOC_FOR_PROCESS -
Hi all,
I have an issue while trying to simply ALE a material from one SAP4.6C system to another. The MATMAS04 IDoc is being received properly by the receiving system, but goes to status 51 when we attempt to post it.
The error message is:
<b>"Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT"</b>
The inbound partner profile for MATMAS message type is specifying a process code <b>'MAT2'</b> which should call FM <b>IDOC_INPUT_MATMAS_MDM</b>. Why would the system try to call the FM mentioned in the error?
I have checked the partner profile, the process code, and the assignment of FM to message type as directed by the error message and they all seem to be correct.
Thanks!Hi Stefan,
Both sending and receiving system are on 4.6C.
The cotrol record on the receiving side shows everything to be correct. Message type is MATMAS and IDoc type is MATMAS04 as expected.
Incidentally, the IDocs post correctly when pushed through the test tool in the receiving system and specifying the material function module. It is only posting automatically or manually through BD87 that doesn't work.
--Jack -
Hi gurus,
i am trying to process IDoc using BD87, but i get the error:
'No resources, immed. processing not possible: Too few free dialog work'
i am new to basis and haven't had any training. please advice on what to do.Hello Arafat,
Two options:
1. Increase the number of dialog processes in your system. This is a long term solution.
2. Process the idocs in background provided you have sufficient processes there as well. This is a short term solution.
I guess you have a fresh installation and may be your are processing USERCLONE idocs.
Regards.
Ruchit. -
Hello,
First I would like to apologize for the title, maybe it is not as descriptive as it should, but I have no idea how to explain my issue in such a short place.
I have created a new relationship for OM, called Z53, as a copy of standard relationship 003, through transaction OOVK, selection 003 and clicking on copy, to make sure I do not miss anything.
As a background, we have plenty of relationships 003 in the system, that were always sent to us via ALE and converted to 003, because in the customer system was X03, and never had a problem with that.
Now as per a business requirement we need to convert the relationships to Z53 instead of 003, so basically we are receiving the same X03 relationships between the same objects, but now we convert them to Z53 instead of 003.
However, the behaviour is not the expected, as example:
As you see in the picture above, we currently have 12 registers with 003 relationships. Now the same 12 registers (X03) will be sent again, but now we will convert to Z53, so what I expect is another 12 registers created, with exactly the same info but Z53 instead of 003. This is the result:
If you compare the pictures, from the 12 003 relationships I had before, 6 of them have been deleted and changed to Z53, and the others have remained the same. This is really a strange behaviour and I would appreciate any light you can throw to this problem.
Thanks for your help in advance!
Kr,One genaral solution to these kind of problem is to use your mouse to click on every possible drill down field/line
You can use We05/We02 ..a lot many other Xns to see the status and actual error message associated.
But as I said use drill down & find the real error.
Cheers,
Ram -
Hi, I'm following the SOADEMO quickstart tutorial, but it's really frustrating because in each step I always found missing things on the tutorial..
Please I'm very interested on this software but I cannot continue..
The error is the following:
[2007/04/25 10:41:13] Fallo al llamar a la operación "OrderSequence" en el proveedor "OrderSequence".menos
-<messages>
-<input>
-<orderSequenceInput>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="OrderSequenceInput_msg">
<OrderSequenceInput xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/OrderSequence"/>
</part>
</orderSequenceInput>
</input>
-<fault>
-<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>null
</code>
</part>
-<part name="summary">
<summary>
file:/C:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_SOAOrderBooking_1.0_937b09d1bd8dae1b33b028b2871aef63.tmp/OrderSequence.wsdl [ OrderSequence_ptt::OrderSequence(OrderSequenceInput_msg,OrderSequenceOutputCollection) ] - WSIF JCA Execute of operation 'OrderSequence' failed due to: El marco del adaptador no ha podido crear la conexión de JCA saliente.
file:/C:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_SOAOrderBooking_1.0_937b09d1bd8dae1b33b028b2871aef63.tmp/OrderSequence.wsdl [ OrderSequence_ptt::OrderSequence(OrderSequenceInput_msg,OrderSequenceOutputCollection) ] - : El marco del adaptador no ha podido establecer una conexión de JCA saliente debido al siguiente motivo: ORABPEL-12529
Problema de ManagedConnectionFactory.
No se ha podido instanciar ManagedConnectionFactory oracle.tip.adapter.db.DBManagedConnectionFactory debido a:
Falta la clase: oracle.tip.adapter.db.DBManagedConnectionFactory
Clase Dependiente: oracle.tip.adapter.fw.wsdl.WSDLUtils
Cargador: oracle.bpel.common:10.1.3
Origen del Código: /C:/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
Configuración: <code-source> in /C:/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
Esta carga se ha iniciado en orabpel.root:0.0.0 mediante el método Class.forName().
La clase que falta no está disponible desde ningún origen de código o cargador del sistema.
Asegúrese de que el adaptador de recursos JCA correspondiente se ha desplegado.
; nested exception is:
ORABPEL-12511
El marco del adaptador no ha podido crear la conexión de JCA saliente.
file:/C:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_SOAOrderBooking_1.0_937b09d1bd8dae1b33b028b2871aef63.tmp/OrderSequence.wsdl [ OrderSequence_ptt::OrderSequence(OrderSequenceInput_msg,OrderSequenceOutputCollection) ] - : El marco del adaptador no ha podido establecer una conexión de JCA saliente debido al siguiente motivo: ORABPEL-12529
Problema de ManagedConnectionFactory.
No se ha podido instanciar ManagedConnectionFactory oracle.tip.adapter.db.DBManagedConnectionFactory debido a:
Falta la clase: oracle.tip.adapter.db.DBManagedConnectionFactory
Clase Dependiente: oracle.tip.adapter.fw.wsdl.WSDLUtils
Cargador: oracle.bpel.common:10.1.3
Origen del Código: /C:/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
Configuración: <code-source> in /C:/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
Esta carga se ha iniciado en orabpel.root:0.0.0 mediante el método Class.forName().
La clase que falta no está disponible desde ningún origen de código o cargador del sistema.
Asegúrese de que el adaptador de recursos JCA correspondiente se ha desplegado.
Examine el archivo log en busca de motivos. Active el registro de depuración en la consola BPEL.
</summary>
</part>
-<part name="detail">
<detail>null
</detail>
</part>
</bindingFault>
</fault>
</messages>There are two ways to check this:
- from the container, login to Oracle Enterprise Manager (<server>:<port>/em), find your OC4J instance where SOA Suite is running, then click the 'Administration' link. Then click the task icon at 'services', 'JDBC Resources'. Check the datasources there to see if they all point to the correct location.
- from JDeveloper, open the demo project. Double click the Database adapter(s) to see which connection is used. If you get an error, the connection probably isn't defined in JDeveloper. Click on the 'new..' button, and create a new database connection. The redeploy the project and try again.
HTH,
Bas -
Hi
While an Inbound is being processed it is not behaving as per the design and if the same type of idoc is reprocessed through BD87 is it behaving as per the design.
In detail, the idoc will create a purchase order based on reservation number in R/3 and the quantity needs to be checked against the availability. If the quantity is more in the idoc counting all line items of idoc segments it should not be posted giving that the quantity is not available. If it is automated it is not checking, but while testing on creation of an inbound idoc and reprocessed the validation is happenning.
So, please help me in understanding as why the idoc is not getting validated when it is automated ans whne it is reprocessed through BD87 it is getting validated.
Thanks
ShankarHi Shankar,
how do you notice that your code is not executed.
Usually I would say it should.
Therefore I recommended to implement an infinite loop to make sure that it is really not executed.
By the way...where did you implement your coding?
Best regards,
Oliver
Edited by: Oliver Hütköper on Aug 12, 2011 8:45 AM -
R/3- XI Idoc processing error.
We are trying to send an IDoc from R/3 to XI (PI). The IDoc has status 03 (IDoc sent to R/3 System or external program, Data passed to port OK). But we do have the following message which is probably returned by XI:
No service for system SAP<sys-id>, client <client> in Integr
Does anyone have an idea what to do and where?
Is it something in R/3 (guess not since status seems to be OK), or any configuration to be done in XI?Hi,
Your sender system (R/3) needs to be translated into Service by IDoc adapter in XI.
It takes client <MANDT> and sender port <SNDPOR> from control record and based on that finds service.
Before, you need to maintain Logical System Name for your R/3 Business System in SLD and then update Adapter Specific Identifiers in your service in XI (ID).
Pleas, ref this doc: [SAP NetWeaver Exchange Infrastructure - Using the IDoc Adapter|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd]
Regards,
Jakub -
BOM mapping with change number error during IDoc process
Hi all,
i am creating BOM using IDoc BOMMAT04.i have checked this IDoc will use FM IDOC_INPUT_BOMMAT inside.
in this function module, it is using FM CSAP_MAT_BOM_CREATE and CSAP_MAT_BOM_MAINTAIN to create and change.
currently, creation and deletion is success. but when change, if the change number passed as an input parameter, the IDoc process error saying that the BOM header not allowed to update for read-only field.
if i not pass the change number, the change will be success, but no change number displayed in the item. that is not the user expected.
and if i delete the bom with change number, create a new BOM for the same material is not aloowed, saying that BOM already existing.
it seems that CSAP_MAT_BOM_CREATE and CSAP_MAT_BOM_MAINTAIN cannot support much. it is limited.
can anyone have any good solutions? thanks!yeah, for the change, i have solved it.
but currently, if i delete the existing BOM with a change number, the re-creation is not allowed by the IDoc saying that the BOM already existing.
if i delete in CS02 without change number, it deleted from DB and can be re-create.
but if delete in IDoc without change number, it failed saying that local BOM can not be deleted by ALE.
do you have any solution? i want to implment in IDoc: delete existing BOM and create a new one for the same material with change number. (currently the standard IDoc FM not support BOM group) -
Inbound Idoc processing issues - Partner Profiles - error status 56
Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-DHi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM -
SOAP:1.023 SRT: Processing error in Internet Communication Framework
Hi,
We are developing consumer proxies on ECC enhancement Package 4.
Could you please advice us on the mandatory Technical Configuration that is required in order to consume Web Services from external (non-SAP systems) Providers?
We are trying to test a consumer proxy which consumes a Web Service hosted on a third party system but we are getting the following error:
SOAP:1.023 SRT: Processing error in Internet Communication Framework: (""ICF Error when receiving the response: ICM_HTTP_
Thank you in advance.
Kind RegardsHi,
If I were SAP support I'd point you at [SAP Note 5|https://service.sap.com/sap/support/notes/5]-
If I were a grumpy forum user I'd answer with [Let me google this for you|http://lmgtfy.com/?q=SOAP%3A1.023+SRT]
Since I have my good 5 minutes I'd say this:
The most important part of your description is missing, that is ...ICM_HTTP_XXXXX????? with XXXXX???? probably being CONNECTION FAILED. Most probably you have a routing or proxy problem, which means, your app server can't reach the destination (given your destination URL does exist at all).
You might find details in ST11 and some help in [this thread|Calling external webservice fails on 4 of the 5 server instances;.
Have fun,
anton -
Processing error in Internet Communication Framework
Hi ,
I'm in to the configuration phase of solman_setup in solution manager where I am facing the Processing error in Internet Communication Framework.
Tcode: saomanager->service administration -> web service configuration:
"SRT Framework exception: Service Ping ERROR: Error when calling SOAP Runtime functions: SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED""
Also i have checked in smicm-> goto->trace file. I'm getting the following warnings
Thr 10372] HttpSAPR3SetParam: Switched j2ee status to: 1
[Thr 65180] Wed May 14 20:35:57 2014 [Thr 65180] *** WARNING => Connection request from (22/33/0) to host: http, service: 80 failed (NIEHOST_UNKNOWN) [Thr 65180] EX-T22, U33, 001 SATHEESH, 192.168.8.17, 20:35:41, M0, W9, , 1/0 {0003001f} [icxxconn.c 2271] [Thr 36776] Wed May 14 20:36:43 2014 [Thr 36776]
*** WARNING => Connection request from (19/20/0) to host: harwich01, service: 55000 failed (NIEHOST_UNKNOWN) [Thr 36776] RM-T19, U20, 001 SATHEESH, egdp103, 20:36:27, M0, W9, SM59, 2/2 {000300c1} [icxxconn.c 2271] [Thr 15168] Wed May 14 20:42:14 2014 [Thr 15168]
*** WARNING => Connection request from (22/33/0) to host: http, service: 80 failed (NIEHOST_UNKNOWN) [Thr 15168] EX-T22, U33, 001 SATHEESH, 192.168.8.17, 20:42:09, M0, W9, , 1/0 {000200d8} [icxxconn.c 2271] [Thr 53732] Wed May 14 20:44:42 2014 [Thr 53732]
*** WARNING => Connection request from (19/20/0) to host: harwich01, service: 55000 failed (NIEHOST_UNKNOWN) [Thr 53732] RM-T19, U20, 001 SATHEESH, egdp103, 20:44:40, M0, W9, SM59, 2/2 {000300de} [icxxconn.c 2271] [Thr 12772] Wed May 14 20:44:44 2014 [Thr 12772]
*** WARNING => Connection request from (19/20/0) to host: harwich01, service: 55000 failed (NIEHOST_UNKNOWN) [Thr 12772] RM-T19, U20, 001 SATHEESH, egdp103, 20:44:42, M0, W9, SM59, 2/2 {000300df} [icxxconn.c 2271] [Thr 65180] Wed May 14 20:46:52 2014 [Thr 65180]
*** WARNING => Connection request from (22/33/0) to host: http, service: 80 failed (NIEHOST_UNKNOWN) [Thr 65180] EX-T22, U33, 001 SATHEESH, 192.168.8.17, 20:46:38, M0, W9, , 1/0 {000200e6} [icxxconn.c 2271] [Thr 15168] Wed May 14 20:55:09 2014 [Thr 15168]
*** WARNING => Connection request from (22/46/0) to host: http, service: 80 failed (NIEHOST_UNKNOWN) [Thr 15168] EX-T22, U46, 001 SATHEESH, 192.168.8.17, 20:55:09, M0, W6, , 1/0 {000200fa} [icxxconn.c 2271] [Thr 65180] Wed May 14 20:55:38 2014 [Thr 65180]
*** ERROR => IcmReadFromPartner(id=2/252): No data from server received (rc=MPI_EBROKEN: pipe broken/canceled/7) [icxxth
Can anyone help me in fixing this issue.
Thanks,
Satheesh E****** SECURITY WARNING ******
Wed May 14 19:59:58 2014
Error: Timeout occured (-5), Traffic Control: Nettimeout (30) exceeded by peer: 127.0.0.1:53675 [icxxthr.c 4285]
trc file: "dev_icm_sec", trc level: 1, release: "720"
Wed May 14 20:32:20 2014
hostname SAPSOLMAN.Mas.eGinnovations.com
logfile name dev_icm_sec
max file size 512000
switch type 0
max file size 512000
file wrap 0
logging level 2 -
Error on outbound processing (- to IDoc), nodetailed error message
Hi guys!
I'm facing a problem with sending IDocs to R/3. My messages have red flag in outbound status, but there is no detailed error message. Everything seems to be ok, but my IDoc doesn't arrive to R/3 and there is that red flag in XI.
What could cause this? It seems like there is some communication problem. Any ideas?
Thank you,
OlianHi,
IT will give the status number,what is the status number in IDOC check it and update the thread.
if u find its a data problem u can debugg the FM,go to WE19 and give ur IDOC number and there u will find the option start out bound processing form this opion u can debugg the code and know wat is the error.
Check ur ALE settings.
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Regards,
Phani
Reward points if Helpful -
Hi everybody,
I've got an application that logs data to an Excel spreadsheet using the Report Generation Toolkit. My VI's have worked fine in the past using Excel XP, but since I've upgraded to Excel 2007, I am getting COM errors like this one:
"Error -2147417842 occurred at The application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi" That is the exact wording, even with the weird punctuation and capitalization.
The first occurrence of the error is not determinate. Sometimes, up to 10 logging sessions, involving a new .xls file, can occur before this error pops up. Once this error occurs, I must quit LabVIEW to resolve it. If I try to do anything with Excel, I always get this error, although sometimes it comes out of different source VIs. Excel_Open.vi is another.
These logging VIs have worked just fine until upgrading to Excel 2007. I checked, and I was using a really old version of the Report Generation Toolkit, v1.0.1. I read the documentation and had a big sigh of relief when I realized I needed to upgraded to v1.1.2 to get Excel 2007 support. However, even after upgrading, I'm still getting the same errors. I'm using LabVIEW 8.0.1, and I'm also building these VIs into an application. The error occurs both in the LabVIEW IDE and in the built application. Does anybody out there have any idea what I can do to fix this? I googled a little, and discovered this is a COM error, but I can't find any references to the Report Generation Toolkit specifically.
Thanks,
Phil
Solved!
Go to Solution.Hi Christian,
I do not see that exact option listed, do you mean "user interface"? I recognize the "Run in UI Thread" option, it's on the Call Library Function Node.
I checked, and my top-level VI has "same as caller" set, and I believe all my VIs are set to "same as caller". Are you suggesting I change my top-level VI preferred execution environment to "user interface", or just the logging sub-VIs that use the Report Generation Toolkit?
Thanks,
Phil
Attachments:
VI_properties.png 15 KB -
Dear Gurus,
Hope you all are fine. I am consuming 2 external WSDL's in ABAP (SE80 - Service Consumer). These are working fine in SAP DEV server. But when i execute tham in SAP QAS server, i am getting this error.
(SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION))
can anybody tell whet could be the problem?
ThanksDear Inaki,
These proxies are working fine in DEV server. I transported them in QAS and tried to execute but getting that error. Networking team say that SAP and other servers can free communicate to each other.
Regards
Maybe you are looking for
-
Bad translation of labels in ADF Query Panel
Hi, When I use an ADF Query Panel, all labels and buttons are translated automatically to Danish (probably because I have Danish region settings or some such). The problem is that it is not a very good translation: In the "Match" radio group at the t
-
Lenovo Thinkpad T60 - 1952 Screen problems
Hello! I have Thinkpad T60 and i have a little problem: Sometimes my screen blinks and turns blue or pink or black. And when i press the "FN+F7" the T60 screen get output to both LCD and External display even tho there is no display plug in! and the
-
Hi All, Is there a Standard report/infoproviders which can be used to display me2n transaction - PO information. Thanks in advance. Monica.
-
Hi Experts Can you explain me that, in table some of the fields has predefined values, whether its a value table or what. Pls explain, how to set predefined values for particular fields to our own tables. Thank in advance. Regards Raj
-
As3IsoLib: Loading Image and Adding to Sprite.
I'm using a library called 'As3IsoLib' in my isometric game to create sprites and other elements. Currently I add a sprite and load an image to be displayed for the sprite. Up until now I have not checked to see when the image has actually loaded as