on 03-19-2009 1:49 PM
I try to send capture events from AII to OER but in SLG1 of OER i get following errors
Invalid par. type in table TRACKPARAMETERS, tr.CS/ID ID EPC_1.30SGTIN-96 DE1464BE205427F1A9FC0050568D1, event code OBJECTEVENT
what would be the reason?
thanks
Hi Yogesh ;
unfortunately , i cannot found internal table TRACKPARAMETERS in the functions and classes of OER while i was debuging..i searched only OER side because i use sproxy of OER directly , there is no connection to AII in this testing scenario..
Do you have another solution hint?
I think there must be a place in SPRO to define trackparameters or etc..
I can observe the errors only from SLG1 , is there any place to see the details about this error.
as you guess , because it isnt a shortdump, there is no any log in ST22
Thanks..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tuncer,
Oh ok.
Since you are on OER side, and using the PTA scenario (visible from the XML message in the post)
i guess this deals with the EM side of OER
Tracking always refers to Event Management. So the spro config of Event Mgmt related side might be of help to you.
I have had no hands on on OER, unfortunately and dont have a system to access. So what i can only do for you is take a guess.
Its like hitting an arrow with your eyes closed to an aim.
But i hope it could be of atleast some help to you
Thnks
Hello Yogesh;
I send following message
<?xml version="1.0" encoding="UTF-8" ?>
<sap:EPCISDocument xmlns:sap="http://sap.com/xi/PTA" creationDate="2009-03-19T10:02:59+01:00" schemaVersion="1.0">
<EPCISBody>
<EventList>
<ObjectEvent>
<eventTime>2009-03-19T10:02:59+01:00</eventTime>
<eventTimeZoneOffset>+01:00</eventTimeZoneOffset>
<epcList>
<epc>urn:epc:id:sgtin:8699502.100281.42</epc>
</epcList>
<action>ADD</action>
<bizStep>urn:epcglobal:hls:bizstep:commission</bizStep>
<disposition>urn:epcglobal:hls:disp:active</disposition>
<readPoint>
<id>urn:epcglobal:fmcg:loc:0000000003404.ZL_H01_DG_PROD</id>
</readPoint>
<bizLocation>
<id>urn:epcglobal:fmcg:loc:0000000003404.</id>
</bizLocation>
<bizTransactionList>
<bizTransaction type="urn:sap:oer:btt:eprod">urn:sap:oer:bti:eprod:8699502.0000610999</bizTransaction>
</bizTransactionList>
<extension>
<SAPBizTransactionExtension>
<bizTransaction type="urn:sap:oer:btt:eprod">urn:sap:oer:bti:eprod:8699502.0000610999</bizTransaction>
<NameValuePair>
<ParameterName>PRODUCT</ParameterName>
<ParameterValue>221</ParameterValue>
</NameValuePair>
</SAPBizTransactionExtension>
</extension>
</ObjectEvent>
</EventList>
</EPCISBody>
</sap:EPCISDocument>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tuncer,
I worked on Event Management stuff for Track & Trace a few months back.
I have a vague idea that this TRACKPARAMETERS mentioned here is some internal table structure that was used in the ABAP code for messages sent to event management system. Here OER is fulfilling your same capability.
So, Tuncer, i may be wrong but atleast it has atleast some food for thought for you.
Please look into the ABAP code of the activity/rule which is responsible for sending event message to OER in SAP AII.
Note: There might be a RFC BAPI which calls up the SAP OER system in that code. Here you might find the internal table structure called TRACKPARAMETERS.
This might give you an idea of what the table contains. (ie missing parameter)
Effectively you can find out from the message list where this error has come up from and find the code.
This might give you a good idea.
This information is purely based on my past experience and apologies if its incorrect. But worth a try.
Thnks
Hi Tuncer,
Can you please figure out what this filed parameter type in the above mentioned table mean?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.