Known Issue: Redwood_S4AJ_ImportJobTemplate errors with "Please create your communication arrangement again" – Redwood

Symptoms

Redwood_S4AJ_ImportJobTemplate errors with message "Please create your communication arrangement again"

Cause

Configuration issue in S/4 HANA

Affected version

S/4 HANA On-Prem/Private Cloud Edition 2022+ and S/4 HANA Application Job Connector v1.0.0.1

Resolution

Configure BC_EXT_APPJOB_MANAGEMENT for On-Premise per https://me.sap.com/notes/3527503 (contact SAP Support when assistance is needed)

Reference

SAP note 3527503

Error

stderr.log

ERROR 2025-02-21 08:08:06,858 GMT [Redwood Job Thread Pool: REDWOOD.S4_APP_ProcessServer.ServiceForRedwood_S4ApplicationJob worker 0-Executor 9800820] job.Redwood_S4AJ_ImportJobTemplate.45534587 - Failed to generate Process Definition for template '...'
com.redwood.extensions.sdk.sapappjob.exception.SAPApplicationJobApiException: Please create your communication arrangement again. See note 3119486.
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.extensions.sdk.sapappjob.SAPApplicationJobApi.handleResponse(SAPApplicationJobApi.java:252)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.extensions.sdk.sapappjob.SAPApplicationJobApi.send(SAPApplicationJobApi.java:238)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.extensions.sdk.sapappjob.SAPApplicationJobApi.getTemplateData(SAPApplicationJobApi.java:159)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.scheduler.app.sapappjob.job.RunApplicationJobTemplate.generateProcessDefinition(RunApplicationJobTemplate.java:105)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.scheduler.app.sapappjob.job.ImportApplicationJobs.lambda$importJobTemplate$5(ImportApplicationJobs.java:224)
at com.redwood.scheduler.api.uow.SchedulerSessionUnitOfWorkManager.perform(SchedulerSessionUnitOfWorkManager.java:112)
at com.redwood.scheduler.api.uow.SchedulerSessionUnitOfWorkManager.perform(SchedulerSessionUnitOfWorkManager.java:71)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.scheduler.app.sapappjob.job.ImportApplicationJobs.importJobTemplate(ImportApplicationJobs.java:215)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.scheduler.app.sapappjob.job.ImportApplicationJobs.lambda$performImports$1(ImportApplicationJobs.java:155)
at java.base/java.util.Iterator.forEachRemaining(Iterator.java:133)
at java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1845)
at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.scheduler.app.sapappjob.job.ImportApplicationJobs.performImports(ImportApplicationJobs.java:149)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.scheduler.app.sapappjob.job.ImportApplicationJobs.execute(ImportApplicationJobs.java:123)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.scheduler.app.sapappjob.job.S4ApplicationJobExecutor.onExecute(S4ApplicationJobExecutor.java:39)
at Library REDWOOD.Redwood_S4ApplicationJob//com.redwood.scheduler.custom.app.extensions_shared.model.CustomJobExecutorBase.execute(CustomJobExecutorBase.java:42)
at com.redwood.scheduler.customjob.service.CustomJobInstance.lambda$execute$0(CustomJobInstance.java:88)
at com.redwood.scheduler.script.java.impl.classloader.ThreadContextRunnable.call(ThreadContextRunnable.java:48)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)

issues.txt

Template ... (...) Import Errors:

Severity Code Message 
ERROR APJ_FW/029 Please create your communication arrangement again. See note 3119486.

SAP_Transaction For backend administrators: use ADT feed reader "SAP Gateway Error Log" or run transaction /IWFND/ERROR_LOG on SAP Gateway hub system and search for entries with the timestamp above for more details
SAP_Note See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)