This is a follow up on my
older blog "BW
request types: RSSM vs RSPM".
Sometimes it becomes handy
to filter a data by a request. Situation can be like there are multiple
requests in a new table of aDSO object. The data is not activated yet so there
is a request ID that can be used to recognize what data were generated by which
request.
But the catch is that request
that is visible in DTP run monitor or in aDSO manage screen (t-code RSMNG)
and the one that can be used in aDSO’s active table is not the same.
Format Data
Type
DTP monitor DTPR__YYYYMMDDHHMMSSXXXXXXXXX RSREQUID CHAR30
Its DTPR and 23-digit timestamp. Use in DTP monitor.
RSMNG {YYYY-MM-DD HH:MM:SS XXXXXX TZN} RSREQUNR / RSMNGTIMESTMP CHAR30 (not counting curly brackets) Used
in Manage Data Targets / UI Monitors.
Request no YYYYMMDDHHMMSSXXXXXXXXX REQTSN NUMC23
Used for active aDSO table filtering. Sometimes called as
Raw Request Timestamp / ID.
The DTP monitor or RSMNG
actual shows it in a format DTPR__YYYYMMDDHHMMSSXXXXXXXXX or respectively in
more human readable format - {YYYY-MM-DD HH:MM:SS XXXXXX TZN} . If any those would be given to a selection
screen of the active aDSO table it would be rejected complaining that the field
is only numeric. The values that the selection screen accepts is just part of
the request string without out the “DTPR__”. That part is just numeric one. Entering
it to the selection screen a specific data set that belongs to that request
will be shown.
More information:
BW
request types: RSSM vs RSPM

No comments:
Post a Comment