problem with data with Z info object

[Former Member]

Hi Team,

we have a problem with data in Z info object

the Z info object is extracted from generic extractor (View).. it has Alpha Conversion activated in Info-object properties(Data type -Character String ,      Conv Routine -ALPHA)  in Info object properties

the same properties are maintained in Tansfer rules as well

the  generic extractor view fetches data from 3-4 standard tables.. and this Z info object is added in generic extractor

the problem is that this Z info object accepts all the data which has Alpha-numeric values, Spaces etc.., but it throws an error in BW when this Z info object has only "Numeric Values"..

for example

Zinfobject has values such as "/aaa/2013/abc" --> accepted in BW

Zinfobject has values such as "       " (Space) --> accepted in BW

Zinfobject has values such as " 213 " or "4044567 " etc --> not accepted in BW throws error "Info object contains non-alpha compliant value"

How should i resolve this issue?

your quick answers will be rewarded

thank you very much

Prince

[Former Member]

Using an info object with type NUMC is a better option else need to do a zero padding using the FM suggested FCI CONVERSION_EXIT_ALPHA_INPUT...

Thanks,

Nithesh.

[former_member182226]

Hi,

Use NUMC data type for infoObject.

Regards,

Aviansh

[former_member182343]

Hi,

Try one simple thing - Remove Conversion Exit(ALFA ) at infoobject level and enable lower case check box and try to load data from PSA /source .

-Vijay

[FCI]

"213" is not alpha-compliant, "00...00213" is. Try to make these values alpha-compliant by using the function module CONVERSION_EXIT_ALPHA_INPUT in the field routine.

This problem is descibed in the note 386982 (alpha routine in BW side, no routine on R3).

Regards,

FCI

[former_member209895]

Hi Prince,

    Alpha conversion routine works or comes into picture when the string / value being loaded is set of numbers.. If you load values such as /0123 or M1000 then these values will get loaded. However if you try to load a value as 123 into an infoobject of length 5 then the error will come up as the value needs to be left padded with 2 zeros, ie., 00123.

Two exits related to alpha conversion are

CONVERSION_EXIT_ALPHA_INPUT : This takes care of adding zeros to the left of the numerical value being loaded, there by avoiding the error. This could be used in the field routine as suggested by FCI above, to fix the data if the data cannot be fixed in the source system.

CONVERSION_EXIT_ALPHA_OUTPUT: This outputs the stored data without the left zeros.

Both these could be tested in SE37 for further understanding.

Hope this helps,

Regards,

  Manohar. D

[former_member530944]

Hello

if your data flow is related 3.x then it is easy to avoid this problem.

please enable "Check Box" for the column "Conversion" in Transfer rules.

[former_member182470]

Maintain in RSKC : ALL_CAPITAL or  ALL_CAPITAL_PLUS_HEX

If the problem still persists, please follow the below doc:--

http://scn.sap.com/docs/DOC-12084