2898881 - Process Communication Error "Technical error APLC_LER 030" Between Outbound Delivery Request and Logistics Execution Request

In terms of Project Stock Order Scenario for Project XXX,  find a process communication error exists between Outbound Delivery Request and Logistics Execution Request.

SAP Business ByDesign

1. Go to Application and User Management Work Center.
2. Navigate to Process Communication Errors View.
3. Select Open Errors with Incidents.
4. You observe a process communication error as below.

• Sending Document:Outbound Delivery Request
• Receiving Document: Logistics Execution Request
• Main Error: Technical error APLC_LER 030

The business user ignores the project or its project task is closed and continues to cancel the line items of the project stock order. The message gets blocked from updating the business document.

Our development team will add logic to prevent users from doing so in a future release.

Before the logic is promoted, please ask the business user to check the project task status of the project stock order before doing the cancel action.

To fix the affected document, you need to change the project status by following steps:

1. Go to Project Management Work Center.
2. Navigate to Projects View.
3. Select Project XXX and edit it.
4. Go to Product- Project stock order subtab.
5. Find the Project Stock Order, you will understand the corresponding Project Task YYY.
6. Go to Project Plan- Gantt Chart subtab.
7. Select Project XXX, make sure that the status is not completed or closed.
8. Find the Project Task YYY in Search Text filed, make sure that the status is not completed or closed.
9. Save.

Once the project and its task get restarted, please submit a case so that SAP support can restart the stuck message in the backend.

CM_SPAF_AGENT_TASK_ROOT, Technical error APLC_LER 030, Project Stock Order,  Project Task, Status. , KBA , technical error aplc_ler 030 , cm_aplc_ler , cm_spaf_agent_task_root , AP-LEC , Logistics Execution Control , AP-PRO , Project Processing , Known Error