on 01-28-2011 7:29 AM
Hi
All the sudden dx_request does not work for some SFCs. Mostly if they have been repaired. Any idea why this can happen?
The message is:
<DX_REQUEST>
<EXPORT>
<NC_DATA_OBJECT>
<NC_CONTEXT_GBO>SFCBO:EEEL1,EE110125000669</NC_CONTEXT_GBO>
</NC_DATA_OBJECT>
</EXPORT>
</DX_REQUEST>
and answer:
<?xml version="1.0" encoding="UTF-8"?>
<DX_RESPONSE>
<CONCLUSION success='no'/>
<EXPORT_RESPONSE>
<TOTALS failed='1' total='1' invalid='0' succeeded='0'/>
<LOG>
NC_DATA_BO failed (NC_CONTEXT_GBO:SFCBO:EEEL1,EE110125000669, USER_BO:, SEQUENCE:, INCIDENT_DATE_TIME:)
Exception occurred: Invalid handle value "*"; valid value "ItemBO" instead of "" (Message 10040)
Database rollback occurred
Database commit occurred
</LOG>
<RESULT>
</RESULT>
</EXPORT_RESPONSE>
</DX_RESPONSE>
Br,
Jennsen
FYI: as to why you see different results when logging an NC........
If you specify Ref Des and Component, Export Works
If you specify Ref Des but no Component, Export does not work
The issue is ITEM_BO in the NC_DATA_REF_DES table is *
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jennsen,
This is the same "problem" as for Inventory Receipt: DataXchnage was not meant to maintain production business objects like SFC, logged NC data, disposition, Inventory etc. It is Production Interface who should care about automating production activities by means of XML requests.
So, for production BO, DataXchange is not guaranteed to process all of them correctly once it was not designed, coded and tested appropriately.
As concerns NC_DATA, it may work in some case and may not in other cases because of specific internal conventions about linking child table's records to parent table's record, that was designed for GUI rather than for XML.
Regards,
Sergiy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
110 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.