OFTP channel failed to convert into EDI

[Former Member]

Hi Experts,

I  am just a starter to PI and do not have knowledge in seeburger mechanism . Currently I am facing a problem within seeburger workbench  in which mainly call counter functions.

Coming to the point, Scenario is INVOIC02 IDOCS to  EDI (EANCOM format) in which file processed successfully via PI server  but not reached out to destination as a plain EDI file.I can see channel is in active but adapter (OFTP-TCP) failed to convert into EDI. In seeburger workbench shows the file count is incremented for each execution.

Please help me  on how to push the file to destination through seeburger  and explain how OFTP works (OFTP sender EERP channel and OFTP receiver channel)

Greatly appreciated your help.

Thanks,

Gopi

[Former Member]

Nitin and Harish-- Thanks for your inputs.

Could you please tell me where and how to check bic mapping. As per RWB audit log  i am seeing  below error details :

Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 6 errors occured. First error: FieldData testValueTooLong(): destination offset 4: The value assigned to the Field 0020 (value 643740001 exception_in_UNBCounterjava.lang.RuntimeException: CounterBeanServlet: Could not call nextCounter() method

----------------------------------------------

>>the previous source file(edi xml) having the field 0020 with value 64374000100460 was sent with success ad corrsponding destination file(flat edi file) also created and field value is incremented for every execution as 470,480..

>> the next file should be 470(Interchange control reference)  which is not created.

If this is data issue, please explain how to reprocess as other files are in queue (hold status).

Thanks,

Gopi

[Harish]

Hi Gopi,

>>the previous source file(edi xml) having the field 0020 with value 64374000100460 was sent with success ad corrsponding destination file(flat edi file) also created and field value is incremented for every execution as 470,480..

------>>> According to your logs the value of field 0020 is 643740001 and it seems it is long as per the schema. i would suggest you to check the external definition where you must have the type definition for the field.

>> the next file should be 470(Interchange control reference)  which is not created.

You can check BIC mapping in BIC mapper tool.

regards,

Harish

[Harish]

Hi Gopi,

the problem would be in EDI XML to EDI flat conversion. there might be a data or structure issue due to that BIC is unable to convert the XML into flat format.

you can check the logs which will provide the exact error (which segment or field is in error). or you can run the XML in BIC mapper to find out the exact issue.

regards,

Harish

[Former Member]

Hi Harish,

Thanks for your reply. I can see the error in the field D_0020 (EANCOM format). value assigned to this field is too large. In RWB showing as system error and due to this, all other messages are in hold.

exception_in_UNBCounterjava.lang.RuntimeException: CounterBeanServlet: Could not call nextCounter() method of the Servlet. Cause=java.lang.Exception: Servlet returned 500 Internal Server Error - Response Message: Internal Server Error - Error Stream: SAP NetWeaver Application Server Help   500 Connection timed out Error: -5 Version: 7210 Component: ICM Date/Time: Tue Nov 17 02:40:45 2015 Module: icxxthr_mt.c Line: 4477 Server: {-} Detail: Connection to partner timed out.

Thanks,

Gopi

[Harish]

Hi Gopi,

To resolve the issue there are two options

1) If the value is wrong then data needs to be corrected and then retrigger the message

2) If value is correct and BIC is unable to handle that,, then BIC mapping needs to change to accept this values.

regards,

Harish

[nitindeshpande]

Hello Gopi,

This is a data issue. Can you please check the data passing in the D_0020 field in mapping? Seems like invalid value is getting passed.

Regards,

Nitin