BPS - No alpha conversion exit or similar provision?

Dear BPS Experts,
In the Flat File that we are loading to BPS Cube (using the HOW-TO Paper in SDN), if User is having a value 100000006 for Customer and value 10200058 for Material then the flat file upload exit fails. It works only when user changes the value for Customer to 000000000100000006 and value for Material to 0010200058.
I believe, you must have understood my point.
PROBLEM 1
In BW, we have Conversion Exits like ALPHA that take care of internal to external format conversion and vice-versa. Unfortunately, in BPS, it seems system expects users to enter values as they exist in the master data tables like P Tables for Characteristics.
QUE 1: Is my above understanding correct?
We have many characteristics (25-30) in our file and I do not want to write a separate Exit to do any conversion like ALPHA, that would really slow down the performance.
PROBLEM 2
We have a field in the file called 'Manager Name'. Now this field can really have any value. It is not possible for us to load master data in BW for this field. If BPS is suffering from this basic limitation then I am afraid, we can not use it for loading flat file. We have to use only BW
QUE 2: Is there any way, by which I can make BPS accept and load transaction data in BPS Cube even if some master data in that file does not exist. If so, then what is the way to go about it?
I am aware of BW means to load Flat File data to BW/BPS Cubes. But we have many compelling reasons to use Planning Folder to load Flat File. Hence, if some expert can advice about overcoming these limitations with BPS then it would be highly appreciated.
PS: I understand, functionally it does not make sense to plan for something which does not exist in master data. Having said so, there can be some exceptional situations and BPS being the sibling of BW, I expected it to have that capacity.
Regards,
Adi
Edited by: Adi Kulkarni on Aug 13, 2009 3:13 PM

Hi Deepti,
I appreciate your link. That document is very good although it does not solve my problem.
Please note that I am talking about loading a flat file to BPS Cube here and there may be hundreds of values which still do not exist in master data. Your suggested HOW-TO document will be helpful when someone tries to enter data in a planning layout as we do not expect users to enter so many records in planning layout.
I am also aware that we can simply create a Z-Transaction Code (similar to RSD1) to update master data values for a particular InfoObject and Users can be given access to this code. But that is not what I intend to do.
I am looking for a broader and generic solution.
When we load a flat file to BW, we have an option in InfoPackage "Load Transaction Data even if no Master Data exists".. that kind of option or setting really along with something similar to ALPHA Conversion Exits.
Hope my requirement is clearer.
Regards,
Adi
Edited by: Adi Kulkarni on Aug 13, 2009 3:32 PM

Similar Messages

ALPHA Conversion Exit Problem

Hi,
I have an InfoObject ZPRODUCT1 with ALPHA Conversion Exit in RSD1 definition.In the Infosource and in the DataSource/Trans. Structure TAB when i check for the corresponding field it has some other Conversion exit called 'PRID1' and i couldn't change it.
When i load the data i get the error at the PSA level itself and the message is,
InfoObject /BIC/ZPRODUCT1 does not contain alpa-conforming value 80001909.
How to fix this problem?
Thank you
arun

Thanks,
I already did that and it worked properly.
Can you explain how come the conversion exit in Data source transfer structure and the InfoObject can be different?How did this worked?
Will i be able to modify the Conversion exit assignment in the infoobject or Data Source/Trans. Structure TAB? How do i do this, it looks display only in RSD1?
Thank you
arun

Conversion exit ALPHA, external- internal

What does the below Alpha Conversion do :
<b>Conversion exit ALPHA, external->internal</b>
An example wud help me understand better!!

Hi,
A conversion routine is identified by its five-place name and is stored as a group of two function modules. The function modules have a fixed naming convention. The following function modules are assigned to conversion routine xxxxx:
CONVERSION_EXIT_xxxxx_INPUT
CONVERSION_EXIT_xxxxx_OUTPUT
The INPUT module performs the conversion from display format to internal format. The OUTPUT module performs the conversion from internal format to display format.
E.g. If you specify ALPHA conversion for Material number then when user enters the value for MATNR as 123; internally it is converted to 0000123 and is stored in that format in the database. In this case, conversion is done from external format to internal format and the other way if you are reading value from database; it is converted from internal to external format and value is shown as 123, instead of 0000123.
Hope this helps.
PB

Conversion exits before value mapping in AIF

Hi All
I'm trying to use conversion exits before mapping in define value mapping, where I want to truncate leading zeroes in the source field before the value mapping is executed.
I'm using the conversion exit 'ALPHA' (internal->external) to achieve this, but the leading zeroes do not get truncated. Below is an example-
Conversion Exit: ALPHA
Data Element for conversion:
Direction: Internal->External
Source Value: 0000012345
Expected Value after conversion: 12345
Actual Value after conversion: 0000012345
A similar issue Error in reading a value from database table is noted here, however note 1892571 that is suggested does not seem to resolve the issue I'm facing.
Am I missing something here?
Regards
Chandra

Hi Glenn Bumanlag,
I think the values that you have given for source values (Agency and scheme)
and Target values (Agency and scheme) may be mismatching so kindly chek that...even i got the same error in the past..........
If you the this problem kindly change it accordingly and also refresh the cache once you that with this.........
Kindly follow the below mentioned link and check if you have followed these steps.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00ee347e-aabb-2a10-b298-d15a1ebf43c5
Thanks
Sai
PS: kindly reward points if helpful

Web Dynpro ABAP: Assigning of Conversion Exits in ALV

Hi,
We are currently developing a generic data display application using ALV technology in Web Dynpro ABAP. "Generic" means that the structure of the data is created dynamically during runtime (using RTTS) and that even the contained data elements are created dynamically without any relation to DDIC. The generation is based on metadata like field name, data type, length, decimals, conversion exit.
Our problem is that we were not able to find a way to assign the conversion exit of a data element ("column") in Web Dynpro ALV. Without this feature, no output conversions will take place since the data elements have no relation to DDIC. In the "classical" ALV, this could be easily done using method SET_EDIT_MASK of class CL_SALV_COLUMN.
Is there a similar method in WebDynpro ALV or at least an alternative approach to assign a conversion exit to a column or cell?
Thanks for your help in advance.
Best Regards,
Sven

Hello Sven Hader,
As you said you are generatiing the metadata like field name, data type, length, decimals, conversion exit dynamically.
Can you please let me know how you are diong this?
Meanwhile, you can try this approach to assign a Conversion exit to ALV Table column attribute dynamically.
DATA:     lv_data                         TYPE dd04v,
              lv_mode_ext2int          type   ESEBOOLE. "Conversion mode that you are in
read the data from the database
    CALL FUNCTION 'DDIF_DTEL_GET'
      EXPORTING
        name                = lv_ddobjname
        state               =   iv_object_state
        langu               =   iv_langu
      IMPORTING
        dd04v_wa         =   lv_data
      EXCEPTIONS
        illegal_input       = 1
        OTHERS           = 2.
    CHECK NOT lv_data-convexit IS INITIAL.
    CONCATENATE 'CONVERSION_EXIT_' lv_data-convexit '_INPUT'
      INTO cl_im_imp_ehs_material_erp=>mv_conversion_exit_input.
    CONCATENATE 'CONVERSION_EXIT_' lv_data-convexit '_OUTPUT'
      INTO cl_im_imp_ehs_material_erp=>mv_conversion_exit_output.
IF lv_mode_ext2int = 'X'.
    ASSIGN cl_im_imp_ehs_material_erp=>mv_conversion_exit_input
        TO <lv_funcname>.
ELSE.
    ASSIGN cl_im_imp_ehs_material_erp=>mv_conversion_exit_output
        TO <lv_funcname>.
ENDIF.
(3) call the conversion exit
CHECK <lv_funcname> IS ASSIGNED.
TRY.
      CALL FUNCTION <lv_funcname>
        EXPORTING
          input = iv_value
        IMPORTING
          output = ev_value.
      IF sy-subrc <> 0.
      ENDIF.
    CATCH cx_sy_dyn_call_illegal_func
          cx_sy_dyn_call_illegal_type
          cx_sy_dyn_call_param_missing
          cx_sy_dyn_call_param_not_found.               "#EC NO_HANDLER
ENDTRY.
Endif.
I hope it should work.
Thanks,
Bharath.K
Edited by: Bharath Komarapalem on Dec 16, 2008 2:47 PM

Dont want ALPHA conversion

Hi All,
According to our requiremetn we dont want Alpha conversion. So i have removed check box in the info object definition. And also i did not use any conversion logic(usning Exit_conversion_alpha_input) in the transfer rules.
But while loading i am getting an error <<info object>> does not contain alpha confirming value 028.
and if i use alpha conversion there is no error but the value would 0000028, in which our customer is not interested. How to avoid this error??
Is there any other way to solve this problem with out using conversion exit.
Regards,
Ravi

Hi....
The ALPHA routine converts purely numeric user input like '4711' into '004711' (assuming that the characteristic value is 6 characters long). If a value is not purely numeric like '4711A' it is left unchanged............
I think values are found that do not have the correct internal format........
Due to this you are facing this issue.....Check the field length of the value for which you are facing this issue.......
Regards,
Debjani.......

0material alpha conversion in BEx query

Folks,
I want to ALPHA convert the material number during BEx query execution. Once the query is executed, I should see the ALPHA converted number. Please advise.
Thanks.

Hi,
can you please give an example of what you want to achieve? 0MATERIAL has already MATN1 as conversion exit....
Achieving this in BEx during query runtime could be quite tricky...
Alternatives would be
- adding a nav attribute to 0MATERIAL like ZMAT_ALPHA and load it with the ALPHA conv exit
- virtual charateristic
- changing the displayed values in VisualBasic or in the WebTemplate
hope this helps....
Olivier.

Assigning Conversion Exit to a Select-Option on Selection Screen.

Hi,
Is it possible to assign Conversion Exit (Like ALPHA) to a Select-Option on a Selection Screen. If so can anyone please tell me how is this achieved.
Thanks & Regards,
Goutham.
P.S.: Points will be definitely awarded.

Hi Anjaneyulu,
Thanks for the Reply.
But the problem comes here, when he enters both the ranges as well as single values, using the extension button provided for the select-option.
One option i found was in the layout of selection screen, to the select-option i assigned the ALPHA as conversion exit. But it says that this will be over-written once program/screen is generated.
Kindly let me know if any one has a solution for this.
Thanks & Regards,
Goutham.

Error in ALPHA conversion while loading hierarchies

Hi,
I got the following error while loading hierarchies:
<i>Error in ALPHA conversion in NodeId00000088 for InfoObject 0PROFIT_CTR
Message no. RH224
Diagnosis
The technical node name for node id 00000088 is not consistent for conversion exit ALPHA, which is stored with InfoObject 0PROFIT_CTR.
Possible reasons for the error:
The original consistent value returned by the DataSource was changed by a conversion routine to a non-consistent conversion exit value.
The DataSource returns a value that is not consistent in the conversion exit.
System response
Loading the hierarchy was terminated.
Procedure
Check whether the correct conversion exit was entered for the InfoObject. If necessary, change the conversion exit, conversion routine or the data to be extracted.
A further option is to activate automatic conversion in the transfer rules. Here, the system executes the conversion exit, making sure that the data is in the correct format.</i>
If it is not hierarchies, we fix this error by prefixing the zeros (as we are working on Qbox we wont change the transfer rules to select the conversion routine) but here there is no PSA, the data is coming from ALE. Based on this please suggest me to how to fix this error?
Points will be given for any helpful suggestion

Ganesh,
Can you please check out the Alpha Conversion Routine and also nodeid for that infoobject..
There might be some inconsistencies in the code..
Hope it helps
Gattu

Alpha conversions in BW7

Hello all,
I found out that transaction for alpha conversion became obsolete in BW 7.0. You can observe this while you try to run TA RSMDCNVEXIT or RSMDEXITON in BW 7.0 SP10+ system is raising following error:
Data conversion functions are no longer supported Message no. RSMD001
Since I briefly searched on OSS and I'm not successful to find any relevant note I would like to ask here how Data conversion are handled in BW7. Somebody has any clue?
PS. Note that I'm running on Unicode system.
Thanks
m./

Hi Martin,
Since some objects of the new data flow in BI 7.0, for example BIA, are not covered by RSMDCNVEXIT it has been set to obsolete. You should not use it anymore.
As an alternative to solve your problem, if you would like to switch on a certain customer exit, you have to delete the data, switch on the customer data, and reload the data.
For further information regarding to Customer exit please check the below links:
Customer Exits
   http://help.sap.com/erp2005_ehp_04/helpdata/EN/f1/0a56f5e09411d2acb90000e829fbfe/frameset.htm
Creating Free Characteristics and Characteristic Values
   http://help.sap.com/erp2005_ehp_04/helpdata/EN/cd/6a5378051a11d2a5700000e8407c05/frameset.htm
Selecting Characteristics and Storing Characteristic Values
   http://help.sap.com/erp2005_ehp_04/helpdata/EN/c1/376a58449a11d188fe0000e8322f96/frameset.htm
Rgds,
Colum
Edited by: Colum Cronin on Jul 7, 2009 4:01 PM

When is a conversion exit triggered?

Hi,
are conversion exits only triggered via GUI:s ?

Hi
Conversion Exits will triggered when u r input/output to a perticular data element which is associated with domain which is attached with conv routine.
take an example
suppose
kunnr a domain whih is attached with ALPHA
if i am giving 80 to store it in database it will store 0000000080 as its length is 10 char
and while ouput it will show me 0000000080.
i think now u got
if helpful
Reward me points
Regs
Manas Ranjan Panda

Leading zeros without ALPHA conversion

Hi all,
we had an infoobject CHAR16 with ALPHA exit, after further analysis we realized that we had to save the field without without trailing zeros so what i've done was to modify the char deleting the ALPHA exit.
I test in DEV this change and the field was populating correctly in the datastore object, for example:
Before
3455 -> 0000000000003455
After
3455 -> 3455
Now i've transported this change in production but it doesn't seem to work, after reloading a chunk of data it's still applying the ALPHA conversion to the field: i've also checked the PSA and i've got the right value.
Any thoughts?
Thanks
Stefano

Stefano,when you remove the alpha conversion from the infoobject then it might create some inconsistencies while loading data and also in reading the value.
Lets say firstly you loaded the data to object with Alpha conversion so value got stored like this :
3455 -> 0000000000003455
Now when you remove the Alpah conversion then value get stored as
3455 -> 3455
System will treat the above entries as two separate records and not single record.Check in system as well.
To display the data correctly you need to enter the value as they are like one with leading zeros and one without then you may be able to see both the records.
Hope this gives an idea.
Regards,
AL

Enable alpha conversion on infoobject, deletion of data no option

Hi SDN forum users
I have this issue where I need to enable / activate alpha conversion on an existing infoobject. The problem is that this infoobject is used in several DSO's and cubes, so many, that deletion of data and reload is not an option (It does not contain Master Data only used as transaction data). Therefore I need to find a solution, that makes activation of alpha conversion possible even though data exits. I have heard about the transaction RMSDEXITON for this, but since we are using version 7.0 this option has been removed.
So how do you guys see the possiblities for me to enable alpha conversion?

Hi.....
U can add the conversion routine for this Infoobject in three ways...
In the BW side...in the Datasource Level
In the datasource >> Go to fields tab >> there search the R/3 field which is mapped to that Infoobject in the Transformation >> Then in the Conv.Routine column select the Alpha Conversion Routine and In the Format column select External....
In the Transformation
Write a field level routine for that particular field abd call the Alpha conversion routine there...
In the R/3 side
In the Customer exit ....Go to SE37 >> EXIT_SAPLRSAP_001 >> Double click on ZXRSAU01 >> search the datasource......write the code there....
Regards,
Debjani....

I would like to know about conversion exits.

i would like to know about conversion exits.

Hi,
Under Domain of a data element of a field, Output Characterestics field 'Convers. routine' is used to create conversion routines, system will do the data changes with in these routines while storing the data into table and retriving the data from table.
Ex: if coversion routine is defined as 'ALPHA' for a standard domain , with this value system will create two function modules.
CONVERSION_EXIT_ALPHA_INPUT
CONVERSION_EXIT_ALPHA_OUTPUT
you can also create your own conversion routines by defining the value in this field. i have defined conversion routine to convert NUMC type data to DEC type data with 'ZCNV'.system will generate two FM's. you need to write the code in those FM's according to your logic.
see the code for this :
CONVERSION_EXIT_ZCNV_INPUT
FUNCTION CONVERSION_EXIT_ZCNV_INPUT.
""Local interface:
*" IMPORTING
*" VALUE(INPUT)
*" EXPORTING
*" VALUE(OUTPUT)
DATA : ws_output type numc10.
ws_output = input.
output = ws_output.
ENDFUNCTION.
CONVERSION_EXIT_ZCNV_OUTPUT
FUNCTION CONVERSION_EXIT_ZCNV_OUTPUT.
""Local interface:
*" IMPORTING
*" REFERENCE(INPUT)
*" EXPORTING
*" REFERENCE(OUTPUT)
data : ws_value type dec12.
ws_value = input.
WRITE: ws_value TO output DECIMALS 0.
ENDFUNCTION.
Thanks & Regards,
Sunil

Error in conversion exit CONVERSION_EXIT_PERI7_INPUT

Hi Gurus, I am trying to load 3 external flatfiles. They are all similar files with only year difference 2006,2007 and 2008. I was able to load 2 of these files for year 2006 and 2007. Now I am getting this error message "Error in conversion exit CONVERSION_EXIT_PERI7_INPUT" and in details I get "An error occurred in record 1 during execution ofconversion exit CONVERSION_EXIT_PERI7_INPUT for field FISCPER".
This indcates the field 0FISCPER. When I check the data type it is the same for all the files. The conversion routinr PER17 is also same for all. I still do not get why I am getting this error. Does anybody have a hint on this?

Hi Bigtoja,
There has to be something different in the 3rd file. If not the format then, data. The reason is that, the first 2 files are loaded. Try the following to confirm. If the data is similar, you should be able to load it. Take a backup of the File 2. Copy the contents of File3 into File2. Make sure that the format of all the columns are same. Now, upload File2. If data is correct, it gets loaded. Otherwise, something wrong with wither format or data. You have the backup of File2 in case something is screwed. Hope it makes some sense.
Thanks and Regards
Subray Hegde

BPS - No alpha conversion exit or similar provision?

Similar Messages

Maybe you are looking for