Why a PCS 7 Alarm Acknowledgment May Not Show the SIMATIC BATCH Name

@1%s@ is not a universal BatchName placeholder: it formats the first associated value attached to that specific message as a string. If an alarm displays the source chart name, check the generating block's event mapping and Batch-parameter transfer. The acknowledgment/report entry may be a separate record from the original block alarm, so its data fields must be identified and verified independently; the available details do not establish how to add BatchName to this specific acknowledgment.

Separate the alarm message from its acknowledgment

The source distinguishes an alarm that already displays the batch name from an acknowledgement entry that does not. In PCS 7, message lists distinguish incoming and acknowledged alarms; the acknowledgment concerns the message state. A text placeholder configured for the originating block event does not automatically prove that a separate acknowledgement/report record carries the same associated values.

What the placeholder actually formats

@1%s@ formats associated value 1 as a string. It does not request a value named BatchName from SIMATIC BATCH. If the displayed result is a source chart name, the exact event likely supplies that value at slot 1; confirm using the message-generating block's documentation and the event's configured associated values. The forum reply itself cautions that the mapping is block-specific.

Check batch-value transfer for the exact message source

Identify the APL block, event/message ID and source alarm entry. Inspect that block's V9.1 documentation for its associated-value mapping and whether BATCH parameters are transferred for that message. Do not substitute another block's placeholder mapping. The Siemens APL V9.1 manual contains version-specific “Reporting with BATCH parameters” guidance, but its large PDF could not be opened during research, so its exact feature-bit applicability is not asserted here.

Investigate the acknowledgment record separately

Determine whether the report row is the original process alarm with acknowledgement state, an OS acknowledgment/operator action record, or a SIMATIC BATCH message. Compare the original and acknowledged entries in the actual message list/archive and identify which one the batch report queries. SIMATIC BATCH V9.1 Readme documents enabling the “Batch” category in Alarm Control for batch messages; that display filter does not establish that the acknowledgment event itself inherits an APL block's BatchName value.

Verification

In a test project or approved reporting test, compare one known batch alarm and its acknowledgement. Record event source, message ID, message text, associated values, archive fields and report query. Verify that the batch name remains tied to the correct batch when alarms are acknowledged later; do not infer a fix from changing @1%s@ in the original alarm text.

Limitations and Operational Precautions

PCS 7 V9.1 is stated, but the APL block, batch version, message ID, report source and screenshots are missing. No accessible manufacturer documentation established how to add the batch name to the specific acknowledgment entry. Treat the proposed associated-value mapping as a diagnostic path, not a confirmed solution.

Engineer FAQ

Will @1%s@ always show the batch name? No. It formats associated value 1, whose meaning depends on the block and event.

Does enabling Batch messages in Alarm Control change acknowledgement values? The BATCH V9.1 Readme documents a display filter for Batch messages, not a change to acknowledgement-record fields.

Technical References

SIMATIC BATCH Blocks V9.1 SP2 Function Manual, 07/2022, A5E42579230-AC, pp. 17–18 (associated values for listed BATCH interface-block messages); official PDF opened and read.
SIMATIC BATCH Readme V9.1, 02/2021, A5E42579339-AA, section on showing Batch messages in WinCC Alarm Control; opened and read. This is a list-display option, not proof of acknowledgement-value mapping.
PCS 7 Advanced Process Library V9.1 SP1 Function Manual, section 2.1.9.38 “Reporting with BATCH parameters”; identified but PDF too large to open, so no claim here relies on it as verified.