on 04-02-2013 12:41 PM
Dear Experts,
I have a situation here. . .
The Outbound Delivery is sent from the AII instance to the ECC.
The event capture notification sent simultaneously to the OER system through the PI system has the below ERROR in its payload.
The format of 'urn:epc:id:sgtin:0037000.065736.37000657429' is not valid
I assume its a customizing error.
Though I am not able to find whats wrong or where !!
Please help me out with this...
Below is the actual error recorded in SXMB_MONI
Thanks in advance
Sam Anish
Hi,
I gues you are working with EM 7.0? Or are you already on EM 7.01? In the latter case you could consider activating business function AIE_OER_PTACOLDCHAIN. Activating this business function deactivates the ID-mapping (and the validating of the format) for the EPCs. In other cases you have to adjust the customizing in your AII system, that is part of your OER. In the customizing you can find the related customizing activities here: SPRO -> Auto-ID Infrastructure -> Settings for SAP Object Event Repository -> ID Settings.
Nevertheless, recommendation is here to use at least EM 7.01 with activated business functions - especially if you have high volume use cases (->performance).
Cheers, Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Anish,
I think I am too late to respond to this query.
I had encountered this error in the past. This error is due to:
1) not maintaining the ID type settings in OER configuration step
2) Misalignment of ID type settings in AII and OER.
Check these setting (for eg. ID format and ID format header) in both systems and ensure that they are aligned. Even a missing dot or extra space can result in the above error.
Let me know if that helps.
Regds
Ishwar
Sam- Is this issue resolved now? If yes, what was the solution.
Thanks,
Abhishek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello experts,
here is my trace file. Hope somebody has an idea:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Call Inbound Proxy
-->
</Trace>
************************************
--> </Trace>
</Trace>
************************************
--> ************************************
--> ************************************
--> ************************************
--> </Trace>
</Trace>
************************************
--> ************************************
--> ************************************
--> ************************************
--> ************************************
--> ************************************
--> ************************************
--> </Trace>
</Trace>
************************************
--> ************************************
--> ************************************
--> ************************************
--> </Trace>
************************************
--> ************************************
--> ************************************
--> </Trace>
</Trace>
************************************
--> </SAP:Trace>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello folks,
currently I have several issues. One of them is the same Sam mentioned in the initial post.
@Sam: Could you solve it with Satishs recommendation?
@Satish: could you give us detailed information how to configure the ID Mapping (transaction etc.) It would be gread because I am new in this area.
Thank you.
Regards,
Fatih
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sam ,
I am sure you might have got some solution to this issue . I am also facing the same issue . Could you please share solution of the issue . Thanks for your support .
Regards.
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Rajesh Dwivedi
My apologies for the delay in reply.
I had to concentrate on other standalone issues for a while,so there's been no progress on the above error from my side yet. I shall post the solution once I get back to the integrated scenarios. In the mean time, if you have a solution to the error, please do post it. That'd be really helpful.
Regards
Sam Anish
Hi Sam Anish,
Would you be able to tell us what interface are you using to do this activity?
Also on what system (SAP AII, SAP PI or SAP ECC) are you seeing this error?
Where you able to reprocess the failed message from SXMB_MONI? If so we should be able to find a place where we can put a break-point(if ABAP) or do some trace and see where exactly the error is triggering.
Regards,
BRV
The Pack --> Load scenario triggers Event capture notifications from SAP AII Instances to the OER.OER on receiving the message, displays this error in its SXMB_MONI.
Interfaces used :
EventCaptureNotificationOut ---> EventCaptureNotificationIn
AII ---> OER
This particular error comes with a fancy status Icon which says application error when hovered over.
The trace message in OER :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">http content length 4811</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=receiver</Trace>
<Trace level="1" type="T">Remote address = 172.18.246.211</Trace>
<Trace level="1" type="T">Process ID: 2511</Trace>
<Trace level="1" type="T">Work Process ID: 3</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = AID</Trace>
<Trace level="1" type="T">client = 500</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER_P7R</Trace>
<Trace level="1" type="Timestamp">2013-06-25T11:53:08Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = 001EC9D184F703E1A6994EC7DC06DEEC</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="T">--start of determination of sender interface action</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface action for sender found</Trace>
<Trace level="1" type="T">hence keep interface action INIT</Trace>
<Trace level="1" type="T">--end of determination of sender interface action</Trace>
<Trace level="1" type="T">--start of determination of receiver interface action</Trace>
<Trace level="1" type="T">number of services: 0000000001</Trace>
<Trace level="1" type="T">loop 0000000001</Trace>
<Trace level="1" type="T">select interface EventCaptureNotification_In</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/PTA</Trace>
<Trace level="1" type="T">end of loop 0000000001</Trace>
<Trace level="1" type="T">no interface action for sender or receiver found</Trace>
<Trace level="1" type="T">hence set interface action to DEL</Trace>
<Trace level="1" type="T">--end of determination of receiver interface action</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = AID</Trace>
<Trace level="1" type="T">client = 500</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER_P7R</Trace>
<Trace level="1" type="Timestamp">2013-06-25T11:53:26Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 000</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="3" type="T">Manual Restart: increase Tracelevel to 3</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 016</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline RECEIVER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="3" type="T">message version successfully read from persist version= 002</Trace>
<Trace level="2" type="T">Increment log sequence to 003</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="3" type="T">system-ID = AID</Trace>
<Trace level="3" type="T">client = 500</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SAMANISH</Trace>
<Trace level="1" type="Timestamp">2013-07-18T05:11:53Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = RECEIVER</Trace>
<Trace level="3" type="T">Internal PLID = SAP_RECEIVER</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_RECEIVER</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INBOUND_PROXY</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2013-07-18T05:11:53Z CET Begin of pipeline processing PLSRVID = RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2013-07-18T05:11:53Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_INBOUND_PROXY</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_INBOUND_PROXY</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INBOUND_PROXY</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_PROXY_FRAMEWORK_WS_XI</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="3" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>
</Trace>
<Trace level="3" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 017</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline RECEIVER</Trace>
</SAP:Trace>
Pl do share your thoughts.
Thanks & Regards
Sam Anish
User | Count |
---|---|
9 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.