TMW_GET_LOCAL_TP_BUFFER omits imported transports: Is that correct or an error?

[raphael_ostermann-goletz]

Hello community,

I have a question to the function TMW_GET_LOCAL_TP_BUFFER. We want to use this function outside of a CHARM process and found two situations, where the function result in table ET_TPBUFFER is not identically to our expectations:

1. If the TP buffer (internal table lt_buffer, filled by local function TMS_TP_SHOW_BUFFER) contains a stop mark (STOPMARK), then the next transport is missing in the output table ET_TPBUFFER

2. If the last transport of the import queue (lt_buffer) was correctly imported, then the transport is still missing in the output table ET_TPBUFFER.

(If another transport is appended to the TMS import queue and is imported, then the before missing transport appears in ET_TPBUFFER and the newly imported transport is missing.)

An example is attached to this discussion.

The function is part of package STMWFLOW, wich is included in component SAP_BASIS. The code of the function is in SAP_BASIS release 702 level 12 the same as in SAP_BASIS 731 level 4. Note 996631 doesn't affect the behaviour in above situtations.

Questions: Works the function correctly (as designed for the CHARM-process) or is there still an error in CHARM?

Which sense make the omitted transports, even if the omitted transports have the same status than the other transports in the output table?

Thank you for answering

Best regards

Raphael Ostermann-Goletz

[raphael_ostermann-goletz · Accepted solution]

Hello,

SAP has an answer to the question: A new version of note 996613 (version 4), in which the problem of the last missing transport is solved. Also the STOPMARK is cleaned up from the result table, because it isn't a regular transport.

There was one point which I didn't recognize at first: Even if the function is called TMW_GET_LOCAL_TP_BUFFER, the function only returns the transports, which are not imported,  imported with option 'u0' (tp remains for further import in the queue) or where the import ended with RC > 4 (errors). So the function returns all open transports.

In our example picture above we can determine, that the missing transport after the STOPMARK was imported without option 'u0' (status is 'imported', green hook) and successfull (RC = 4).

So it is correct, that this transport is missing.

But this analysis was helpfull for deciding to delete the STOPMARK in the buffer table of the function, because STOPMARK can't be imported like a transport, so it has not the status of an open transport. - Sometimes you will find a SYNCMARK remaining in the queue (even if package installation is completed, it's a result of installation problems), and the function should ignore SYNCMARK in the same way as STOPMARK (we hope that this will be realized too in the new version of the note 996613).

Thank you for reading this discussion, which will now be closed as answered.

Best regards

Raphael Ostermann-Goletz