PLMSI Version 3.0 & All FP– Guideline For Logging ...

This guide is intended to provide an overview of the PLM system integration (PLMSI) monitoring capabilities. It also covers approaches to error handling and troubleshooting. For more in-depth details, please refer to the official SAP documentation.
PLMSI for S/4HANA Administration Guide

Why Logging and Monitoring for PLM system Integration is so important?
Logging and monitoring are critical for PLM system integration (PLMSI), because integrations are distributed, can be asynchronous, and business critical.
Efficient and reliable process monitoring through simplicity, traceability, clear responsibilities for key business users brings the advantage for a working system and a clear understanding where the possible problem between an external PLM system connected to PLMSI lies.
When something goes wrong, logs and monitoring are often the only reliable way to understand what happened.

Content:

Prerequisites
Logging and Monitoring
- SAP Application Log
- SAP Application Interface Framework
- PLMSI Workbench
Error Handling and Troubleshooting and recommended actions
- Possible status codes and errors from PLMSI for SAP S/4HANA
- Troubleshooting with analyzing request payload

Note: PLM system integration 3.0 is delivered as add-on to SAP S/4HANA on-premises and SAP S/4HANA Cloud and Private Cloud Edition.

1. Prerequisites

PLMSI add-on or S/4HANA private or on-prem 3.0 onwards Support Packages is installed.
Please find more information about this on the SAP documentation.

PLMSI Configuration and external configuration is done, connection is set up between an external PLM system and PLMSI.

Users need authorization through authorization object /PLMF/ADM and general administration rights. SAP documentation: PLMSI for S/4HANA Authorization concept overview

2. Logging and Monitoring
Tip: Always start troubleshooting with logs and monitoring tools before changing configuration or code.

2.1 SAP Application Log

The application log allows an application or object oriented recording of events. Both are classified by object and any subobject which belong to it.
The application log helps to identify business and technical errors that occur during data transfer. In case of an error it gives first indications what the error cause and source might be.
The default expiration date for PLMSI log objects is 90 days after the creation date.

Using the SAP Application Log
1. Open the SAP Application Log via the transaction /SLG1.

2. Choose from the available log objects or search for all with /PLMF*.

You can use the F4 help to review and select from the available sub objects.

System view:
The system shows all log messages that are relevant for this aspect of the integration with the external PLM system.

For more information about SAP Application Log refer to the SAP Help documentation:
PLMSI for S/4HANA Administration SAP Application Log

2.2 SAP Application Interface Framework

The SAP Application Interface Framework (AIF) enables monitoring the endpoints of the integration in a single framework residing in the SAP backend system. The AIF is a more advanced monitoring tool to also assess what data was passed and generated by the integration. It is possible to see the in- and outbound payload within AIF.
Interface Names allow a more specific analysis based on the entity and call type.

Prerequisites:

AIF is implemented and error log level is set to FULL.
PLMSI Business Configuration Sets (BC Sets) for AIF are implemented.
AIF Logging in transaction /SPRO IMG customizing for PLMSI in Define Scenario and Version is set to active in the tested Scenario.

Using the SAP Application Interface Framework

Open transaction /AIF/ERR and select the namespace /PLMSI, an interface name if necessary, and the date range.
Select either only the “error logs” or “all logs”.

System view:

The system shows all log messages configured for this aspect of the integration that are relevant to the external PLM system, broken down by individual entities that can be sent and each separated into Maintain and Read requests.

For more information about AIF refer to the SAP Help documentation:
SAP Application Interface Framework
PLMSI for S/4HANA Administration AIF

2.3 PLMSI Workbench

The PLM System Integration Workbench is designed for technical development support use cases. As a power user or administrator, you can use the PLMSI Workbench report to work on PLMSI messages.
Search for inbound and outbound messages that are processed by PLMSI and take certain actions for a message or object, for example, copy a message, download request, response, and system data, or activate break point IDs used in PLMSI.

Prerequisites for extensive search :

PLMSI add-on Version 3.0 FP 02 or onwards Support Packages for S/4HANA private cloud or on-prem is installed.
SLG1 is logging works.
Users need authorization through authorization object /PLMF/ADM.

Using the PLMF Workbench

Eather go to transaction /PLMF/WORKBENCH.
Or call up PLMSI Workbench from the SAP Easy Access- SAP Menu Cross-Application Components – PLM System Integration – PLMSI Workbench.
Fill in the parameters you want to search for.

System view:
The system shows all log messages configured for this aspect of the integration that are relevant to the external PLM system, depending on the search terms.
Additionally the Object Details, send JSON Request and Response if available are also visible. For more information about SAP PLMSI Workbench visit the SAP Help documentation:
PLMSI for S/4HANA Administration PLMSI Workbench

3. Error Handling and Troubleshooting
General error handling troubleshooting overview for external PLM to SAP S/4 Hana System. Find more information about this topic in the following SAP documentation:
PLMSI for S/4HANA Administration Operating PLMSI

Prerequisite:
Check SLG1 Logs, PLMSI Workbench or Activate AIF Logging and define API Msg Type in Define Scenario and Version.

General approach:

Check status code. In case of application errors (201) proceed with below mentioned steps.
Check if object was created with transferred data.
Check SLG1.
Check AIF Monitoring / external PLM logs.
Check PLMSI Workbench.
Check if configuration matches your expectation.
- SAP PLMSI IMG Customizing.
- Ext. PLM configuration.

3.1 Possible status codes and errors from SAP:
Here are some examples of possible status codes and errors from PLMSI for SAP S/4HANA and recommended actions.

Status code

Information

Payload persisted

Recommended actions

201 – error / success

Application error:
The request was processed, but an application-level error occurred.

Yes

· Review monitoring and logging tools to identify the root cause:

SLG1 – Check application logs for detailed error messages
AIF (Application Interface Framework) – Verify message status and payload processing
External PLM Logs – Cross-check the originating system for inconsistencies
PLMSI Workbench – Validate message flow and processing status

· Confirm whether the payload was persisted correctly and can be reprocessed if needed

400 – bad request

Technical error:
The request could not be processed due to invalid or incomplete input.

· Verify that all mandatory fields are provided

· Check field constraints:

Maximum field length is not exceeded
Correct data types are used (e.g. EDM.String)

· Validate the request structure and format (JSON/XML)

· Ensure the business scenario can be correctly determined from the payload

401 – not authorized

Technical error:
Authentication failed when accessing the SAP Web Application Server.

· Verify technical user credentials:

Correct username
Valid password

· Ensure the SAP user:

Exists in the target system
Is of type System (or required technical user type)

· Confirm host and port configuration maintained in external PLM

· Check that the required authorization roles are assigned to the user

403 – forbidden

Technical error:
The request was authenticated but blocked due to missing permissions or security restrictions.

· Check network and infrastructure settings:

Firewall rules allow the connection

· Validate user authorizations:

Required roles and permissions are assigned

· Verify authentication requirements:

SSL certificate is valid, trusted, and correctly configured

· Review SAP security logs for authorization check failures

404 – not found

Technical error:
The requested resource or service endpoint could not be located.

· Verify that the SAP service is:

· Check whether extPLM is calling the correct endpoint:

URL path
Service name
HTTP method

· Confirm system aliases and routing configuration

500 – internal server error

Technical error:
A technical error occurred on the server while processing the request. The payload was not persisted.

· Investigate server-side runtime issues:

Check for ABAP dumps or unhandled exceptions (e.g. via ST22)

· Validate the request payload handling:

Ensure the referenced JSON file is reachable and syntactically correct

· Verify service availability:

Confirm the HTTP service is registered and active in the SAP system

· Check security token handling:

Validate CSRF token handling and ensure the token is fetched and passed correctly

· Review application and system logs:

Analyze error details in SAP logs to identify the exact failure point

3.2 Troubleshooting with analyzing request payload:

Most errors occurred due to wrong values sent within the request payload. These values are either incorrectly extracted within external PLM system or not configured in SAP PLMSI. This leads either to an unexpected behavior in the target system or to an application error.
It is recommended to validate the request payload at first if the error messages from the target system are unclear. SAP saves both, the request and response payload.

General approach:
1. Go to Transaction SLG1 and copy the External Message ID from the Error that you want to investigate.

2. Or go to AIF and copy Message ID for Internal Message ID.

3. Go to PLMSI WORKBENCH and enter the message ID or fill in the parameters you want to search for.

Note: It is possible to search in PLMF Workbench without an Internal Message ID and External Message ID. Therefore, you can search for example by scenario with date and time range and additional if preferred with a Domain Model Object Type.

For more information about Error Handling and Troubleshooting PLMSI for SAP S/4HANA, see the official SAP Help documentation:
PLMSI for S/4HANA Administration Error Handling
PLMSI for S/4HANA Administration Troubleshooting

For Troubleshooting and recreation of an error case in SAP without external PLM system, please visit the following documentation:
PLMSI for S/4HANA How to test the integration without a external PLM system

Source link