cancel
Showing results for 
Search instead for 
Did you mean: 

DX_Request on NC_DATA_OBJECT

Former Member
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

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 *

Former Member
0 Kudos

Hi

I also noticed that our previous attempts to log NCs with REF_DES worked when we logged also Component value. We will use both at the same time.

Thanks for pointing it out.

Br,

Jennsen

Answers (1)

Answers (1)

0 Kudos

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

Former Member
0 Kudos

Hi

Are these functions present with Web Services or is a supported way of information exportation removed completely?

Br,

Jennsen

0 Kudos

I doubt that WS support information exportation for NC_DATA at least.

Regards,

Sergiy