WINIT Operations
Monitor Configuration Jobs
no token

Summary the whole estate over the selected window

Activity per day across the window — a flat stretch is a feed that stopped

Interfaces what arrived, what was written, and which SFA tables it lands in

A job run reports success for writing zero rows, and a payload nothing has consumed produces no run at all — so an interface that fetches every night and projects nothing looks identical to one that works. That is what the left rule on each card answers.
declared in int_entity_mapping — configuration written by the projector — read from the code, not configured · click any table or Mappings to open the column detail

Fetched data the payloads already stored — inspect, or take a copy

These are the bytes the source actually sent, as stored in int_raw_landing. Downloads are built on the server and served as a file, so what you get is the whole filtered set, not the page on screen.
Download index (CSV) JSON

Delete stored payloads the one action here that cannot be undone

This is the one action here that cannot be undone. int_raw_landing is the replay anchor — everything else on the console can be put right by replaying, and this cannot. A payload that has already been projected can go, and the rows it wrote stay in the destination. A payload that has not been projected is the only copy of data that has never been written anywhere, and for a delta interface whose watermark has moved past it, the source will not serve it again.

Call the source hit a configured SAP interface and see exactly what comes back

Read from int_source_config, so this is what the platform will actually call tonight — not a separate list that can drift.

Map the payload draw which field belongs in which column

The fields on the left are read from a stored payload, so they are what the source actually sends; the columns on the right are read from the destination database's own catalogue, so a column added by a migration is mappable the moment it exists. Lines already implied by int_field_mapping are drawn for you as a starting point, dashed until you save. Every one of them is editable: a seeded mapping can be wrong, and one you can see but not correct is worse than one you cannot see. The board is saved to int_mapping_link as a record of intent, and does not change what tonight's run writes until someone promotes it.