cancel
Showing results for 
Search instead for 
Did you mean: 

Error: Could not read Header Mapping in Receiver Agreement

Former Member
0 Kudos

Dear SAP experts,

Newly installed SAP G7A PI 7.1(Acceptance box) was already released to customer.

We are doing an initial test (BAT phase), wherein, our end-to-end scenario is, from a EP Portal application ---> G7A PI 7.1 --> Trading Partner via AS2 protocol.

G7A PI is connected to Trading Partner via AS2 protocol.

Currently, our EP Portal application is in-active at the moment, that's why we used 'manual XI submitter', to send a message from G7A PI itself going to Trading Partner.

The message was success in the Integration engine of G7A PI, and the output message was produced.

As the message reached the Adapter Engine layer of G7A PI, we encountered a specific error,

Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: Could not create CPAObjectMapper: InvocationTargetException caused by Could not read Header Mapping in Receiver Agreement: while trying to invoke the method com.sap.aii.af.service.cpa.Party.getParty() of an object returned from com.sap.aii.af.service.cpa.NormalizationManager.getXIParty(java.lang.String, java.lang.String, java.lang.String), Could not create CPAObjectMapper: InvocationTargetException caused by Could not read Header Mapping in Receiver Agreement: while trying to invoke the method com.sap.aii.af.service.cpa.Party.getParty() of an object returned from com.sap.aii.af.service.cpa.NormalizationManager.getXIParty(java.lang.String, java.lang.String, java.lang.String)

Basically, "Could not create CPAObjectMapper - InvocationTargetException caused by Could not read Header Mapping in Receiver Agreement"

I am thinking, one of the possible cause is that we used manual XI submitter, in G7A PI, instead of the utilizing the actual Sending system (EP Portal application).

Or possible cause is that the AS2 adapter in G7A is not yet stable, thus causing the issue.

We've already done successful connection when we're in GDD PI (Development box) during our SIT phase.

Objects in G7A were mirror of GDD PI.

Kindly advise for your inputs.

Thanks!

Gerberto

Accepted Solutions (0)

Answers (1)

Answers (1)

prateek
Active Contributor
0 Kudos

This shouldn't be a problem with manual sending of data. You may try complete CPA Cache refresh. Also make sure that the entries used in Header Mapping are active.

Kind regards,

Prateek

Former Member
0 Kudos

Hi,

It seems that the cause of the error is the unstable performance of the PI box, since, this was newly installed and there were patches that were not yet added.

Thanks for the support!

Gerberto