cancel
Showing results for 
Search instead for 
Did you mean: 

Lookup of function BAPI_ENTRYSHEET_CREATE metadata failed for destination

Former Member
0 Kudos

I am using two BAPI's BAPI_PO_GETDETAIL & BAPI_ENTRYSHEET_CREATE

I am getting following error intermittently when trying to call BAPI, what could be the reason????

SAP.Middleware.Connector.RfcInvalidStateException: Lookup of function BAPI_PO_GETDETAIL metadata failed for destination WO ---> SAP.Middleware.Connector.RfcInvalidStateException: Lookup of StructureOrTable BAPIEKBE metadata failed for destination WO ---> SAP.Middleware.Connector.RfcCommunicationException: destination WO failed when calling DDIF_FIELDINFO_GET -- see log for details

   at SAP.Middleware.Connector.RfcRepository.Execute(RfcFunction function)

   at SAP.Middleware.Connector.RfcRepository.LookupRecordMetadataClassic(String name, RecordType recordType)

   --- End of inner exception stack trace ---

   at SAP.Middleware.Connector.RfcRepository.LookupRecordMetadataClassic(String name, RecordType recordType)

   at SAP.Middleware.Connector.RfcRepository.LookupRecordMetadata(String name, RecordType recordType)

   at SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadataClassic(String name)

   --- End of inner exception stack trace ---

   at SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadataClassic(String name)

   at SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadata(String name)

   at SAP.Middleware.Connector.RfcRepository.GetFunctionMetadata(String name)

   at SAP.Middleware.Connector.RfcRepository.CreateFunction(String name)

Accepted Solutions (0)

Answers (1)

Answers (1)

MarkusTolksdorf
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Amit,

if it's happening only intermittently, it is very likely that it was caused by some connection problem. However, once the function modules and the used data types are cached by the NCo runtime, it's actually no longer necessary to look them up unless your code regularly clears the repository. Or the program itself is only a short-runner ...

In order to find the real cause, the log would be helpful and if it's possible to run with trace turned on for a longer time a trace at level 4 of this situation.

Best regards,

Markus