RFC call from jco to new Unicode Client "RuntimeException bapi not found in SAP"

[Former Member]

Hi

We upgraded to a Unicode system and we have only English language and codepage 4103 installed. Previously the codepage was 1100.

If we call existing BAPIs, the calls are 100% okay, but as soon as an ABAPer makes a change to the BAPI, that BAPI is no longer found by jco?

One of the anomalies is that the Connection attributes from SAP sends back non-unicode attributes.. for instance the PARTNER_BYTES_PER_CHAR returned is still 1 instead of the Unicode 2. And the PARTNER_CODEPAGE received back is still the previous non-unicode value of 1100 instead of the new codepage of 4103? Even if we force the connectProperties to 4103

connectProperties.setProperty(DestinationDataProvider.JCO_CODEPAGE,"4103");

Please let me know if you have a solution or suggestion or require more input for analyses.

Thank you and best regards,

Adrian

[Former Member · Accepted solution]

JCo saves a property file to the file system and reads it again. That file was outdated with the old IP and logon credentials. Now with the new IP for the Unicode System, the Java code had to be enhanced by adding the following line (for every run):

  createDestinationDataFile(ABAP_AS, connectProperties);

This updates the properties file with the latest jco.client.codepage,  jco.client.ashost=IPAddress and other logon parameters.

[Former Member]

Hi Adrian,

Have you tried to clear the JCO cache after the parameter was added to the RFC?

https://help.sap.com/saphelp_nw73/helpdata/en/7a/018a7bd67b43b7a7a5f07d0fdd0073/content.htm

[Former Member]

That's a great idea. I'll chat to the java developer and see if he can do that and will let you know if it works.

[Former Member]

Hi Daniel

The Basis consultant says that we don't have a java instance on our SAP system. We only have an ABAP instance. So the instructions can't be followed from our side. However I agree it could be related to CACHE or BUFFERS that need to be refreshed. But our java developer says that he stopped the VM java instance and started it again. That should've refreshed the CACHE. But we're stuck with the same issue.

Adrian

[former_member185239]

Hi Adrian,

Kindly check whether the program exist ZVP_FOB_PREIOD in your SAP system.

Also let us know , when are you getting the error and from where are you calling the program.

Are you getting any dump in ST22 in SAP system.

With Regards

Ashutosh Chaturvedi

[Former Member]

"the RFC/BAPI does exist and is executable with those input parameters within SAP."

No there is no ST22 dump.

After the jco call as per pasted dump, the error is within that output.

[former_member185239]

Dear Adrian,

Kindly check the table EDIPOACODPAG and check the codepage of the RFC.

Also paste the error screen  which you are receiving on BAPI.

784381 - IDoc: Status 02, code page cannot be determined

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi Ashutosh

Our table EDIPOACODPAG has no entries.

This is the full call and error:

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: Start

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: D:/Lotus/Domino/devdat/domino/html/VDP/

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: strURLValue - OpenAgent&shortname=johnsnow&staffNo=123456&prefix=E&date=Tue Jan 26 08:50:47 UTC 0200 2016&supplier=&export=csv&dealer=&action=ZFOBPrice&sapc=&lifnr=L99887&period=2015 0009&_end

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: Action ZFOBPrice

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: IV_LOTUS_ID ----- johnsnow

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: IV_LIFNR ----- L99887

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: IV_PERIOD ----- 2015 0009

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: B4 Sap connect

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: sapConnect Start

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: docConn NOT null

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: SAPConnect : Set parms

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: SAPConnect : JCO_ASHOST : 11.3.22.999

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: SAPConnect : JCO_SYSNR : 00

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: SAPConnect : JCO_CLIENT : 001

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: SAPConnect : JCO_USER : rfc_johnsnow

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: SAPConnect : JCO_PASSWD : THRONES

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: SAPConnect : JCO_LANG : E

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: Connection attributes:

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: --------Connection attributes------

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: DEST:                  ABAP_AS_WITHOUT_POOL

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: OWN_HOST:              DEVCLI001

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: PARTNER_HOST:          jndev01

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: SYSTNR:                00

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: SYSID:                 DEV

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: CLIENT:                001

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: USER:                  rfc_johnsnow

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: LANGUAGE:              E

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: ISO_LANGUAGE:          EN

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: OWN_CODEPAGE:          1100

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: OWN_CHARSET:           ISO8859_1

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: OWN_ENCODING:          iso-8859-1

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: OWN_BYTES_PER_CHAR:    1

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: PARTNER_CODEPAGE:      1100

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: PARTNER_CHARSET:       ISO8859_1

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: PARTNER_ENCODING:      iso-8859-1

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: PARNER_BYTES_PER_CHAR: 1

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: OWN_REL:               720

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: PARTNER_REL:           731

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: PARTNER_TYPE:          3

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: KERNEL_REL:            721

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: TRACE:                 

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: RFC_ROLE:              C

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: OWN_TYPE:              E

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: CPIC_CONVID:           00000000

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: trace:

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: --------Connection attributes-----

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: false

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: sapConnect End

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: sapData Start

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: sapData tName : ZVP_FOB_PERIOD

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: java.lang.RuntimeException: ZVP_FOB_PERIOD not found in SAP.

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at SAPConnect.sapData(Unknown Source)

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at JavaAgent.ZFOBPrice(JavaAgent.java:343)

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at JavaAgent.NotesMain(JavaAgent.java:80)

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at lotus.domino.AgentBase.runNotes(Unknown Source)

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at lotus.domino.NotesThread.run(Unknown Source)

[Sriram2009]

Hi Adrian.

[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: sapData tName : ZVP_FOB_PERIOD
[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM: java.lang.RuntimeException: ZVP_FOB_PERIOD not found in SAP.
[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at SAPConnect.sapData(Unknown Source)
[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at JavaAgent.ZFOBPrice(JavaAgent.java:343)
[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at JavaAgent.NotesMain(JavaAgent.java:80)
[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at lotus.domino.AgentBase.runNotes(Unknown Source)
[1460:0040-15C0] 2016-01-26 08:50:52 AM  HTTP JVM:  at lotus.domino.NotesThread.run(Unknown Source)

You may require to check the Z program /function module (ZVP_FOB_PREIOD)  with integration of Lotus Domino.

Regards

SS

[Former Member]

Thanks S Sriram, but the RFC/BAPI does exist and is executable with those input parameters within SAP. I don't know what you mean by "check with integration of Lotus Domino"? This is a java connector call to SAP and execution of RFC/BAPI that does exist. It was created within a non unicode environment and now after the conversion to unicode it did work initially, but after input parameter was added, it now no longer is found from java connector?