cancel
Showing results for 
Search instead for 
Did you mean: 

Mapping program not available in runtime cache

Former Member
0 Kudos
1,771

Hi

In Production, the mapping in ESR doesn't work. It says this message in SXMB_MONI. Mapping program not available in runtime cache.  I don't see the object id of mapping in SXI_CACHE. I used my id to create them in DEV and QAS. In Prodn, I used the client id. Is that why I get this error message? I mean I transported the objects from QAS using client id.

Also I see that one of the Idocs is missing in Production. Should I import it the same way I import in DEV? Also is it advisable to delete and recreate mapping in Production ? The import doesn't seem to work.

Regards

Accepted Solutions (1)

Accepted Solutions (1)

iaki_vila
Active Contributor

Hi Radhika,

You could try to refresh de runtime cache in the transaction sxi_cache.

1, Try with Delta cache refresh, if the error persits try with complete cache refresh.

2. If the error persists try to refresh CPA cache:

Partial refresh:

It's possible to refresh a single object in the cache. Follow this steps:

    PI's Main Page -> Administration -> Integration Builder -> Cache Overview -> Single Repository

    Object Cache Refresh.

    Object Type:  your object type like operation mapping or message mapping

Full refresh:

http://<hostname>:<port>/CPACache/refresh?mode=full

with PIDIRUSER/XIDIRUSER

If you want to know a bit more about the this caches:

Delta a complete cache refresh from sxi_cache: http://scn.sap.com/thread/891755

CPA cache. In this forum http://scn.sap.com/thread/1028733 SAP Mentor’s Prateek explains in an easy words what is the CPA cache purpose.

Regards.


Answers (1)

Answers (1)

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Radhika,

If the steps outlined by Iñaki, do not help to resolve this see the note #1580750 PI Integration Builder: objects are missing after successful import. This recommends that you create a new version of the objects you are transporting (in the source system) and then execute the transport again. If the other steps don't solve this, then following note #1580750, should do.

Regards

Mark