Error with RFC provided in PACK for R/3 v5.1 and 5.2.1

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
underwoodn
Participant
Posts: 1
Joined: Fri Jun 01, 2007 6:09 am

Error with RFC provided in PACK for R/3 v5.1 and 5.2.1

Post by underwoodn »

I have been writing interfaces for a number of years using the
DataStage PACK for R/3 against various versions of SAP. My
current customer is running ECC6.0 Unicode. I am running
DataStage 7.5.1A and PACK for r/3 version 5.1. I have loaded
the RFC provided with the install (ZDSRFCU.txt, or the transport
files), and attempted to conduct the test per the installation
guide on the RFC where you test it and provide "5" and "T000" as
your parameters. This should a successful response, but rather
I get the error "ASSIGN CAST WRONG LENGTH". It goes on to read:


"In the current program "SAPLZETL", the ASSIGN...TYPE...statement
was used to assign the type "D" to the field symbol
"<%_1_SYSINI>". The length defined for this type is 16 but the
reference field is 32 characters long. The type to be assigned
is in the field "FIELDS_INT-TYPE"."

I debugged the program and it throws the error while processing a
date field stored in T000. I have found out that the 5.1
version of PACK for R/3 does not support Unicode and have tried
the files provided with version 5.2.1, but have received the
same results.

I am curious if there is anybody out there that has successfully
implemented this RFC in a Unicode environment. IBM customer
support has not yet been able to tell me if this has even been
tested on their end. Please help if you have any experience.

Thanks,
Nate
koojo
Premium Member
Premium Member
Posts: 43
Joined: Sun Jul 11, 2004 1:30 pm
Location: USA

Post by koojo »

Yes ... You can use the ABAP Extract pack sucessfully on a unicode system. You need to import the meta data from the unicode system and make syre you generate the ABAP on the unicode system. There are differences in the generated ABAP on a unicode and non unicode system. On the colums Tab the display width needs to be double that of the length. I have noticed this to be a requirement only with SAP unicode systems for the ABAP extract pack :) .
Post Reply