/SAPSLL/CUHD_MASS_REFRESH_EXP does not send Status update to S/4

[dean_hinson2]

Hello,

During testing we think we find that when a document recheck is done in GTS, the status change is not being sent to S/4. I tried to review/debug /SAPSLL/CUHD_MASS_REFRESH_EXP. I did find a routines rfc_destination_get, reference_docs_dequeue and reference_docs_enqueue, but these were never executed, nor do they seem to be executed from other routines.

So, I am wondering if the document recheck send the document status change to S/4 systems? Can you please confirm either way? If the status is supposed to be sent to S/4, how can you check/debug?

Thank you in advance.

Regards, Dean.

[arunakumar_biswal]

Hi Dean,

As per my understanding, the "Recheck Document" programme never sends any update or status to the feeder system, it just checks for any update or new information applicable to customs documents as per the availability within the GTS system. For example, during the creation of sales order, a licence was not available, and after the creation of licence master data for this sales order, we can execute this programme so that a new license master can be applied to the customs document.

Feeder systems get the status of GTS customs documents by using FM /SAPSLL/CD_STATUS_GET within feeder system programme. this FM use RFC connection to pass feeder system documents and immediately get status from GTS .

Regards

Arun

[dean_hinson2]

Hello Arun,

Did a test without my customers... I think my customer was in the document in change mode.

The recheck did send a status update to the S/4 system. Just can't find the code that does it.

Regards, Dean.