# Help Needed: Correcting \<PERS\_NO\> in BAPI message bodies for known IntegrationEntryIds and requesting an demo

**URL:** <https://community.criticalmanufacturing.com/t/help-needed-correcting-pers-no-in-bapi-message-bodies-for-known-integrationentryids-and-requesting-an-demo/612>\
**Category:** Integrations\
**Tags:** v11.3, erp\
**Created:** [February 13, 2026, 6:11am UTC](https://community.criticalmanufacturing.com/t/help-needed-correcting-pers-no-in-bapi-message-bodies-for-known-integrationentryids-and-requesting-an-demo/612 "2026-02-13T06:11:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![joy\_jiang](https://avatars.discourse-cdn.com/v4/letter/j/977dab/32.png) [@joy\_jiang](https://community.criticalmanufacturing.com/u/joy_jiang)\
**Post date:** [February 13, 2026, 6:11am UTC](https://community.criticalmanufacturing.com/t/help-needed-correcting-pers-no-in-bapi-message-bodies-for-known-integrationentryids-and-requesting-an-demo/612/1 "2026-02-13T06:11:50Z")

</div>

Background  
Some BAPI requests contain an incorrect \<PERS\_NO\> in the XML body, which causes SAP posting failures. We already have the list of IntegrationEntryIds that must be corrected.  
Error (RESULT):  
BAPI process failed due to: Error during posting confirmation (err:x08) Personnel master record 02965274 not found (check entry) The error was reported by action ERPOutputMessageHandlerAction.

**Request snippet:** \*\*\*\*

\*\* \*\*\<PERS\_NO\>02965274\</PERS\_NO\>

What we need

An minimal demo/sample (script/action/pipeline config) showing how to do this.

The PERS\_NO above should be replaced with a valid personnel number 02967667

 ![](https://canada1.discourse-cdn.com/flex050/uploads/community_criticalmanufacturing/original/1X/3276226ec736fb3b9527faf75c5185ac4f7d9de4.png)

---

<div class="post-metadata">

**Author:** ![Ricardo\_Cunha](https://yyz2.discourse-cdn.com/flex050/user_avatar/community.criticalmanufacturing.com/ricardo_cunha/32/1133_2.png) [@Ricardo\_Cunha](https://community.criticalmanufacturing.com/u/Ricardo_Cunha)\
**Post date:** [September 8, 2026, 1:46pm UTC](https://community.criticalmanufacturing.com/t/help-needed-correcting-pers-no-in-bapi-message-bodies-for-known-integrationentryids-and-requesting-an-demo/612/2 "2026-09-08T13:46:58Z")

</div>

Hi Joy,

Updates of Integration Messages payloads are not supported. Example:

 ![image](https://canada1.discourse-cdn.com/flex050/uploads/community_criticalmanufacturing/original/2X/2/23511ce5037893edae98120c132a692bf22b2aff.png)

You’d need to create a new Integration Entry with the updated payload. In simple steps:

1. Load the original Integration Entry and its message:

```auto
var serviceProvider = (IServiceProvider)Input["ServiceProvider"];
var entityFactory = serviceProvider.GetService<IEntityFactory>();

var ie = entityFactory.Create<IIntegrationEntry>();
ie.Load("<IE_NAME>");
ie.LoadIntegrationMessage();

var message2 = Encoding.UTF8.GetString(ie.IntegrationMessage.Message);

```

1. Change the payload data according to your requirement.
2. Create a new Integration Entry with the same metadata (source, target, message type,etc. )

For tips on how to programatically create a new Integration Entry see my response to this post: [How to create a MES to MES Integration Entries using DEE, please give an example code, thanks a lot! - #2 by Ricardo\_Cunha](https://community.criticalmanufacturing.com/t/how-to-create-a-mes-to-mes-integration-entries-using-dee-please-give-an-example-code-thanks-a-lot/606/2)

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex050/user_avatar/community.criticalmanufacturing.com/system/32/23_2.png) [@system](https://community.criticalmanufacturing.com/u/system)\
**Post date:** [September 10, 2026, 1:47pm UTC](https://community.criticalmanufacturing.com/t/help-needed-correcting-pers-no-in-bapi-message-bodies-for-known-integrationentryids-and-requesting-an-demo/612/3 "2026-09-10T13:47:01Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.