4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

SAP PI / PO BLOG
Stories Of The Daily Struggle With SAP Process Integration And SAP Process Orchestration
(https://pipoblog.com/)

Ta g : E r r o r s A n d S o l u t i o n s
Error messages in SAP systems are o en not very user friendly. Hopefully, I already figured the soultion for one of your erros out.

(https://pipoblog.com/2017/08/message-in-status-message-recorded-commit-missing/)

Message in status Message recorded (commit

missing)
(https://pipoblog.com/2017/08/message-in-
status-message-recorded-commit-missing/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 8 - 1 1
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 8 / M e s s a g e - I n - S t a t u s - M e s s a g e - R e c o r d e d - C o m m i t -
Missing/) |

Scenario
You created a test message with the testing tool in transaction SPROXY to test an asynchronous interface out of your
ERP system. A erwards you checked transaction “SXMB_MONI” or “SXI_MONITOR” for the test message.

Error
The message has a white flag and shows the following error:

Message in status Message recorded (commit missing)

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 1/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/08/2017-08-02-17_58_32-.png)

sxi_monitor: Messages in status commit

Solution
Asynchronous message are recorded until the work is committed. Go back to the “Test Service Consumer” view of
transaction “SPROXY” and click on Extras – > Trigger COMMIT WORK.

(https://pipoblog.com/wp-content/uploads/2017/08/2017-08-02-17_59_18-Test-Service-Consumer_-Change-
Request.png)

Trigger Commit Work in Proxy Test Tool

The message should be sent to the receiving system now. If you call your proxy out of some ABAP code, make sure you
do not forget to add a commit statement.

(https://pipoblog.com/2017/08/eer-certificate-rejected-by-chainverifier/)

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 2/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

Peer certificate rejected by ChainVerifier

(https://pipoblog.com/2017/08/eer-
certificate-rejected-by-chainverifier/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 8 - 0 7
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 8 / E e r - C e r t i f i c a t e - R e j e c t e d - B y - C h a i n v e r i f i e r / ) |

Scenario
In a scenario with a SSL encrypted (HTTPS) SOAP target URL in the SOAP receiver channel, the message goes into an
error state.

Error
The following error is shown in Message Log in PIMON:

SOAP: Call failed: java.io.IOException: Failed to get the input stream from socket:
iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier

Solution
The SSL certificate needs to be imported into PIs keystore.

Download the certi cate from the target server

1. Open the Target URL in Chrome (or any other Browser)
2. Open the developer tools by clicking on the three dots -> More Tools -> Developer Tools (Shortcut STRG + SHIFT
+ I)

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 3/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/08/chrome_developer_tools.png)

Chrome: Open developer tools

3. Go to the “Security” Tab and click on “View certificate”

4. Go to the Details Tab and click on “Copy to file” button
5. Click on the “Next” button and select “DER-codet-binary X.509 (.CER)”

(https://pipoblog.com/wp-content/uploads/2017/08/2017-08-07-16_36_12-Service-Web-Service.png)

Download Certificate

6. Click on “Next” button and select a destination on you local PC

Import certi cate into keystore

1. Open the Netweaver Administrator (http://your.pi:port/nwa)
2. Go to Configuration -> Security -> Certificates and Keys
3. Select the “Trusted CAs” View and click on “Import Entry”
4. Select entry type “X.509 Certificate”, enter the path to the certificate you downloaded before and click on
“Import”
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 4/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/08/2017-08-07-16_54_00-Certificates-and-Keys-SAP-
NetWeaver-Administrator.png)

Certificates and Keys: Import entry

5. Resend your message

If your error is not resolved, open the certificate again and click on certification path. A erwards, double click the first
and second certificate (one a er each other), save them and also import them into the TrustedCAx view.

(https://pipoblog.com/2017/07/complete-bpmn-error-traces/)

Find complete BPMN error traces

(https://pipoblog.com/2017/07/complete-
bpmn-error-traces/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 7 - 3 1
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 7 / C o m p l e t e - B p m n - E r r o r -Tr a c e s / ) |

Scenario
During the development of a BPMN on SAP Process Orchestration you will probably arrive at a point where your
Process does not work as expected. One way to find the issue is to check the traces in the Log Viewer, to find out more
about the error.

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
Find the traces in the Log Viewer
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 5/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

1. Triggered the BPMN to run again

2. To check the BPM Status open PIMON (http://your.po:port/pimon)
3. Go to Monitoring -> Processes and Tasks -> Manage Process
4. Open the “History” Tab and select “Show: Advanced”. You can find the Log ID in the log entries below.

(https://pipoblog.com/wp-content/uploads/2017/07/2017-07-26-11_13_06-Manage-Processes-SAP-
NetWeaver-Administrator.png)

Manage Processes: Find Log Id

If the following message is shown:

For more details, decrease severity of log controller as described in SAP Note
1753560.

Please check the section Increase BPMN Trace level and a erwards start again with step 1.

5. Open  the NetWeaver Administrator (http://your.po:port/nwa)

6. Got to Troubleshooting -> Logs and Traces -> Log Viewer
7. Open View -> Open View -> System Logs and Traces

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 6/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/07/2017-07-26-
11_14_03-Log-Viewer-SAP-NetWeaver-Administrator.png)

Open “System Logs and Traces” view in Log Viewer

8. Add a filter for Log ID and enter the Log ID out of the “Manage Processes” View

(https://pipoblog.com/wp-content/uploads/2017/07/2017-07-26-11_14_54-Log-Viewer-SAP-NetWeaver-
Administrator.png)

NWA Log Viewer: Filter for Log ID

9. You can find the whole error trace in the filtered results.

Increase BPMN trace level

To increase the BPMN trace level follow the steps below:

1. Open  the NetWeaver Administrator (http://your.po:port/nwa)

2. Go to Configuration -> Infrastructure -> Log Configuration
3. Select
We use cookies “Show:that
to ensure Tracing Locations”
we give you the best experience on our website. If you continue to use this site we will assume that you
4. Click on “Open Filter” and filter for Location “BPMNException”
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 7/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

5. Change Severity for location “ExceptionAdapter$BPMNException” to “ALL”

(https://pipoblog.com/wp-content/uploads/2017/07/2017-07-26-11_15_17-Log-Configuration-SAP-
NetWeaver-Administrator.png)

NWA Log Configuration: Increase Severity for ExceptionAdapter$BPMNException

6. Click on “Save Configuration” and trigger your BPMN again

Also, check out SAP Note 1753560 (https://launchpad.support.sap.com/#/notes/1753560).

(https://pipoblog.com/2017/07/start-process-disabled/)

“Start Process” in Process Repository is

disabled
(https://pipoblog.com/2017/07/start-
process-disabled/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 7 - 2 6
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 7 / S t a r t - P r o c e s s - D i s a b l e d / ) |

Scenario
If you develop a BPMN, you probably have to manually trigger the process multiple times to check that everything
works as expected. One way to trigger a BPMN is the usage of the “Start Process” function in the Process Repository.

You can find the Process Repository in the NetWeaver Administrator -> Processes and Tasks -> Process Repository.

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
Error
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 8/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

The “Start Process…” button in the Process Repository is disabled.

(https://pipoblog.com/wp-content/uploads/2017/07/2017-07-26-11_44_46-Process-Repository-SAP-NetWeaver-
Administrator.png)

“Start Process…” button in Process Repository is disabled

Solution
The role “SAP_BPM_SuperAdmin” is necessary to use the “Start process…” function. To add the role to your user,
follow the steps below:

1. Open the NetWeaver Administrator (http://your.pi/nwa)

2. Go to Configuration -> Security -> Identity Management
3. Select you User and open the “Assigned Roles” Tab
4. Click on “Modify” and search for the role “SAP_BPM_SuperAdmin”
5. Select the role, click on “Add” and a erwards on “Save”

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 9/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/07/2017-07-26-11_43_41-Identity-Management-SAP-
NetWeaver-Administrator.png)

Add role SAP_BPM_SuperAdmin to user

A er refreshing the repository browser, the “Start Process…” button should be available.

(https://pipoblog.com/2017/07/error-during-bpmn-deployment/)

Error during BPMN deployment

(https://pipoblog.com/2017/07/error-during-
bpmn-deployment/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 7 - 2 0
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 7 / E r r o r - D u r i n g - B p m n - D e p l o y m e n t / ) |

Scenario
Developing and debugging a BPMN can be a nightmare. The build and redeployment of a BPMN can take up to five
minutes and lead to multiple errors.

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
A er multiple successful deployments, it was no longer possible to deploy or undeploy a process.
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 10/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

Error
The following error message was shown in the deployment log of SAP NetWeaver Developer Studio:

Description: Description: 1. Adapter com.sap.glx.adapter.internal.Transformer has

refused deploy unit e5853c8198e860817e261ae672f4bfc4 using configuration
mode DEPLOYMENT

-> Transformer could not get lock within 60 seconds

Solution
Restart the Galaxy Core Service to fix the issue. This can be done like this:

1. Open the NetWeaver Administrator (http://your.pi:port/nwa)

2. Go to Operations -> Systems -> Start & Stop -> Java Services
3. Search for Name “Galaxy Core Service”
4. Select your Instance and click on Restart
5. Wait some seconds and  try to deploy your service again

(https://pipoblog.com/wp-content/uploads/2017/07/2017-07-26-10_13_28-Start-Stop-SAP-NetWeaver-
Administrator.png)

NWA: Restart Galaxy Core Service

(https://pipoblog.com/2017/07/forbidden-error-xi-receiver-channel/)

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 11/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

Forbidden Error in XI Receiver Channel

(https://pipoblog.com/2017/07/forbidden-
error-xi-receiver-channel/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 7 - 1 6
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 7 / F o r b i d d e n - E r r o r - X i - R e c e i v e r - C h a n n e l / ) |

Scenario
In a configuration with an SAP R3 system as receiver, which is connected via a XI Receiver Channel, the message cannot
be delivered to the target system.

Error
The following message is shown in the Message Log of PIMON:

SOAP: Error occurred:

com.sap.engine.interfaces.messaging.api.exception.MessagingException:
java.io.IOException: HTTP Error response for SOAP request or invalid content-type.;
HTTP 403 Forbidden

Exception caught by adapter framework: java.io.IOException: HTTP Error response

for SOAP request or invalid content-type.; HTTP 403 Forbidden

Transmitting the message to endpoint <local> using connection JPR failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
java.io.IOException: HTTP Error response for SOAP request or invalid content-type.;
HTTP 403 Forbidden

Solution
Activate the Integration Engine Service on your target system:

1. Open SAP GUI and connect to your target system

2. Open transaction “SICF”
3. Enter “/sap/xi/engine” as “Service Path” and click execute
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 12/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/07/2017-07-31-16_09_37-.png)

Transaction SCIF: Service Path /sap/xi/engine

4. Right click on “Integration Engine (SAP XI Message Format)” and select “Activate Service”

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 13/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/07/2017-07-31-16_09_07-Define-Services.png)

Transaction SCIF: Activate Integration Engine Service

5. Restart your message

6. If it still does not work, check that the used user has the role “SAP_XI_APPL_SERV_USER”

(https://pipoblog.com/2017/07/idoc_error_parse_failure/)

IDOC_ERROR_PARSE_FAILURE: Namespace
in IDOCs
(https://pipoblog.com/2017/07/idoc_error_pa
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 14/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

rse_failure/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 7 - 1 2
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 7 / I d o c _ e r r o r _ p a r s e _ f a i l u r e / ) |

Scenario:
In a SOAP to IDOC scenario with a XSLT mapping, the receiving IDOC Communication Channel produced an error
message.

Error:
The following error message is shown in the Message Log:

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE:

Invalid XML 1.0 character encountered within IDoc-XML for type <ORDERS05>:
state=EXPECTING_IMMEDIATE_TAG_END, charPosition=64, lineNumber=1,
columnNumber=65, invalidChar=U+0078,
sourceSnippet=…UTF-8″ standalone=”no”?><ORDERS05
xmlns:a=”http://example.namespace.com/order”><IDOC BEGIN=”1″><EDI_DC40
SEGMENT=”1…
—————————————————^

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-14-11_30_40-
Message-Monitor-SAP-NetWeaver-Administrator.png)
Error Message in PIMON Message Monitor

Solution:
Namespaces are not allowed in IDOCs. You can add the  exclude-result-prefixes  parameter to your stylesheet
definition to make sure that the given namespaces are not added to the target document.

<ns0:stylesheet version="1.0" xmlns:a="http://example.namespace.com/order" xmlns:ns0="ht

We usetp://www.w3.org/1999/XSL/Transform"
cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
exclude-result-prefixes="a">
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 15/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

Multiple namespaces can be added by using a white space as separator:

<ns0:stylesheet version="1.0" xmlns:a="http://example.namespace.com/order" xmlns:ns0="ht

tp://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="a b c">

(https://pipoblog.com/2017/06/commit-fault-asj-ejb-005043-failed-in-component-sap-comcom-sap-aii-ad/)

Commit fault: ASJ.ejb.005043 (Failed in

component: sap.com/com.sap.aii.ad)
(https://pipoblog.com/2017/06/commit-
fault-asj-ejb-005043-failed-in-component-
sap-comcom-sap-aii-ad/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 6 - 1 6
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 6 / C o m m i t - F a u l t - A s j - E j b - 0 0 5 0 4 3 - F a i l e d - I n - C o m p o n e n t -
Sap-Comcom-Sap-Aii-Ad/) |

Scenario
Simple ERP to PI communication via IDOC.

Error
The IDOC is not send out to PI and the following error message is shown in transaction SM58 on ERP system:

Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad)

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 16/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-16-10_27_49-Transactional-RFC.png)

Error in SM58

Solution
To find out why the IDOC cannot be send to our PO system we will check the channel monitoring of the IDOC sender
communication channel first. If there is no error in the channel monitor, we have to do dive deeper into the system, by
using the XPI Inspector:

1. Open the XPI Inspector on your SAP PO system.

http://po.host.name/xpi_inspector

2. Select Example “50 (XI Channel)” and add your IDOC sender communication channel by searching for the
channel name, checking the checkbox and clicking the “Add selected” button.

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 17/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-16-10_42_54-XPI-Inspector.png)

XPI Inspector configuration page

3. It is best to stop the XPI inspector as soon as possible. Otherwise, you have to look through thousands of log
entries. Therefore, open SM58 and search for you message to be prepared to resend the IDOC (Edit -> Execute
LUW (F6)).
4. Hit the “Start” button in XPI inspector and wait till the start page is loaded.
5. Resend the IDOC (Edit -> Execute LUW (F6)) in SM58.
6. Click the “Stop” button in XPI inspector and wait for the result page to show up.
7. Click on the number in the “Records Count” column of the Server Nodes table. If you have multiple Server
Nodes, you have to go through all of them.

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 18/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-16-10_40_26-XPI-Inspector_-Result.png)

XPI Inspector result page

8. Search for a log entry with your IDOC (you can use the browser search CTRL+F and search for your IDocNumber,
MessageType or anything else)

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 19/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

Client = 001
CreationDate = 20170615
CreationTime = 171650
Direction = 1
EDIMessage =
EDIMessageGroup =
EDIMessageType =
EDIStandardFlag =
EDIStandardVersion =
EDITransmissionFile =
ExpressFlag =
IDocNumber = 0000000052812406
IDocSAPRelease = 750
IDocCompoundType = null
IDocType = DELVRY07
IDocTypeExtension =
MessageCode =
MessageFunction =
MessageType = Z_DELV_IT
OutputMode = 2
SenderAddress =
SenderLogicalAddress =
SenderPartnerFunction =
SenderPartnerNumber = A22001
SenderPartnerType = LS
SenderPort = SAPA22
Serialization = 20170615171650
RecipientAddress =
RecipientLogicalAddress =
RecipientPartnerFunction =
RecipientPartnerNumber = RECPPRN
RecipientPartnerType = LS
RecipientPort = A000000003
Status = 30
TestFlag =
ROOT (Type: ROOT)
!
+-- E2EDL20004 (Type: E1EDL20)
!
+-- E2EDL22001 (Type: E1EDL22)
!
+-- E2EDL21 (Type: E1EDL21)
! !
! +-- E2EDL23 (Type: E1EDL23)

9. Some lines below you should find a line with a red or yellow background with your error

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 20/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-16-10_37_50-
xpi_inspector_display_itemtraceoption1467050.png)

Warning in XPI Inspector

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 21/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

[EXCEPTION]
com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound bind
at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup
at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup
at com.sap.aii.af.service.cpa.InboundRuntimeLookup.(InboundRuntimeLookup.java:88)
at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBinding(AbstractLo
at com.sap.aii.af.idoc.inbound.IDocInboundProcessor.findBindingAndChannel(IDocInbound
at com.sap.aii.af.idoc.inbound.IDocInboundProcessor.initForIDocListProcessing(IDocInb
at com.sap.aii.af.idoc.inbound.IDocInboundProcessor.process(IDocInboundProcessor.java
at com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(IDocReceiverBean.java:127)
at sun.reflect.GeneratedMethodAccessor1393.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(Re
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Abstra
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Int
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Abstra
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptor
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Abstra
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Abstra
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Abstra
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.inv
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Abstra
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interc
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Abstra
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Inte
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Abstra
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lo
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Abstra
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChai
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(
at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProx
at com.sun.proxy.$Proxy3278.onCommit(Unknown Source)
at com.sap.mw.jco.jra.JRA$ReaderThread.commit(JRA.java:8639)
at com.sap.conn.jco.rt.DefaultServerWorker.onCommit(DefaultServerWorker.java:209)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJa
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:275)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:356)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:232)
at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:8947)
at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:245)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecu

The error message

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 22/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

Couldn’t retrieve inbound binding for the given P/S/A values:

probably means that your ICO is not configured correctly. Check that you selected the right IDOC and sending system.
Maybe you forgot to transport the configuration? Also, it could be a cache refresh problem. You can edit the
description, save the configuration and activate it again to refresh the cache.

(https://pipoblog.com/2017/06/reset-cae-status-for-argentina-invoices-afip/)

Reset CAE Status for Argentina Invoices

(AFIP) (https://pipoblog.com/2017/06/reset-
cae-status-for-argentina-invoices-afip/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 6 - 1 4
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 6 / R e s e t - C a e - S t a t u s - F o r - A r g e n t i n a - I n v o i c e s - A f i p / ) |

Scenario
During the integration of the synchronous AFIP webservice for Argentina invoices via  SAP PI / PO, I did some End-to-
End tests and struggled with multiple errors on PI side. Unfortunately, sometimes it was impossible to do a new test
because one invoice was no longer in a send able state.

These are the possible states:

CAE Status Description

I Sent to AFIP
A Approved
P Approved with Reservations
R Rejected
N New Document
C Contingency
E Validation Error
O Observations

Error
The following error message is shown when clicking on “Send to AFIP” button in SAP ERP transaction
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
“J1AEXPMONITOR”:
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 23/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

Another document is already in process

Solution
1. Goto transaction SE16
2. Insert table name “J_1ACAE” and click on the “Table contents” button
3. Insert some filters into the mask (optional) and click on the “Execute” button

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-08-10_44_54-Sametime-Appshare-
Highlighter.png)

Enter filter values and execute

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok
4. Select line where you would like to change the CAE status and click on the “Change” button
https://pipoblog.com/tag/errors-and-solutions/ 24/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-08-10_45_29-Sametime-Appshare-
Highlighter.png)

Select one table entry of table “J_1ACAE” to edit

5. Remove the “X” in field “RFC SENT LOCK” and click on “Save” button

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-14-10_55_33-Table-J_1ACAE-Change.png)

Change CAE STATUS for table entry

We use cookies to the

6. Leave ensure
datathat we give
browser toyou the the
unlock besttable
experience on our website. If you continue to use this site we will assume that you
7. Try to resend the message in transactionare happy with it.
“J1AEXPMONITOR” Ok

https://pipoblog.com/tag/errors-and-solutions/ 25/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/2017/06/reset-rfc-sent-lock-for-argentina-invoices-afip/)

Reset RFC Sent Lock for Argentina Invoices

(AFIP) (https://pipoblog.com/2017/06/reset-
rfc-sent-lock-for-argentina-invoices-afip/)
B y M a x i m i l i a n ( H t t p s : // P i p o b l o g . C o m /A u t h o r /A d m i n / ) | 2 0 1 7 - 0 6 - 1 1
( H t t p s : // P i p o b l o g . C o m / 2 0 1 7 / 0 6 / R e s e t - R f c - S e n t - L o c k - F o r - A r g e n t i n a - I n v o i c e s - A f i p / ) |

Scenario
During the integration of the synchronous AFIP webservice for Argentina invoices via  SAP PI / PO, I did some End-to-
End tests and struggled with multiple errors on PI side. Unfortunately, a er every test I had to create a new invoice in
ERP system, because the invoice was marked as already sent.

As creating a new invoice for every test takes time, I looked for a way to reset the send status of existing invoices.

Error
The following error message was shown when clicking on “Send to AFIP” button in SAP ERP transaction
“J1AEXPMONITOR”:

Document is in process

Solution
1. Goto transaction SE16
2. Insert table name “J_1ACAE” and click on the “Table contents” button
3. Insert some filters into the mask (optional) and click on the “Execute” button

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 26/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-08-10_44_54-Sametime-Appshare-
Highlighter.png)

Enter filter values and execute

4. Select one line and click on the “Change” button

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 27/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-08-10_45_29-Sametime-Appshare-
Highlighter.png)

Select one table entry of table “J_1ACAE” to edit

5. Remove the “X” in field “RFC SENT LOCK” and click on “Save” button

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 28/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

(https://pipoblog.com/wp-content/uploads/2017/06/2017-06-08-10_46_01-Sametime-Appshare-
Highlighter.png)

Remove RFC SENT LOCK for table entry

6. Leave the data browser to unlock the table

7. Try to resend the message in transaction “J1AEXPMONITOR”
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 29/30
4/16/2019 Errors and Solutions Archives - SAP PI / PO Blog

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you
are happy with it. Ok

https://pipoblog.com/tag/errors-and-solutions/ 30/30