Leading zero check got activated in production .

Hi,
We had a DIMP ( Discrete Industries Mill Products) addtional installation to our existing landscape on last weekedn. we have a strange issue after that.
Most of the select queries based on material number,vendor,customer are failing. with further analysis it was observed that select queries are failing because of leading zero's missing .
we are surprised since the same queries worked perfectly fine before ( and it still runs perfectly fine in qulaity client) but now it is failing.
we know workaround to change all custome programs with conversion exit addtion to material,lifnr,kunnar ect.. but does anybody know if there is any business function which got activated to check leading zero's in select queries and this got activated along with DIMP.
let me know if you have any helpful inputs.
PS: i wnat to restore my original settings for leading zero so we dont need to change nay programs.

Hi Santosh,
some more analysis is required: For the failed selects, where do the missing-leading-zero kunnr/matnr/lifnr come from?
If from screen input, check the screens are active, check the input fields data type, active, conversion exit correct?
It may be a good idea to check the whole system for inactive objects.
If from other sources, check the complete way the data goes before use in SELECT WHERE clause.
If you have found one errors source, this will lead to more.
There are a couple of SAP notes on DIMP, at least the activation process of DIMP should be checked.
Regards,
Clemens

Similar Messages

Remove leading zeros coming from Active Directory

Greetings all. Our sapusername is stored in Active Directory with leading zeros. Is there a way to remove these zeros in the portal so SSO will work? I have had my AD team manually remove the zeros in front of my sapusername, so I'm sure that's the issue.
Alternately, is there a setting in R3 that would allow leading zeros?

Hi,
I've seen the problem before and I think you only have two choices (haven't looked into if R3 can accept leading zeros)
1. Since you are allready retrieving sapusernames from an R3 change that mapping to remove leading zeros and possibly put it in a new attribute.
2. Create a JAAS login module which retrieves found username from the HeaderVariableLoginModule and trims leading zeros before putting the username back to shared state. This new LoginModule must be placed before the CreateTicketLoginModule.
Note it is not very trivial to create a JAAS login module but an excellent guide can be found here http://help.sap.com/saphelp_nw2004s/helpdata/en/46/3ce9402f3f8031e10000000a1550b0/frameset.htm

Product ID doesn't have leading zeros

Hi,
In the table CRMD_SRV_REFOBJ, some of the product ID has leading zeros and some of the product doesn't have leading zeros. Any idea why it is happening like that?

Hi,
Please check it the products base table COMM_PRODUCT. If you find similar set of values, then issue could be with programs creating Product IDs.
Usually Products flows from ECC, also possiblility to be created in CRM too. So, the check the Badi impli CRM_EQUI_LOAD for flow from ECC.
Hope this helps.
Satish

Removing Leading Zeroes in Location value

HI Gurus,
I am having some trouble in releasing demand plan to SNP. On the demand planning side, we are using standard characteristic 9ALOCATION for storing location values. When I release demand plan (using Location characteristic - 9ALOCATION) to SNP, I get a message saying 'Location 00000000000000003000 does not exist'. But, I have location '3000' assigned to the active model in APO system.
I believe this issue is arising because, the system is storing leading zeroes in Location value '3000' on Demand Planning side. I know that there is customization setting (SPRO-> APO -> Master data -> Product -> specify output format) to prevent leading zeroes from being added to product number. But I don't see a similar setting for Location and moreover I am using 9ALOCATION and not 9ALOCNO.
So, how can I remove leading zeroes in the values of 9ALOCATION.
Any help/comments are appreciated.
Thanks,
Shiv.

I found a solution to this problem. Unlike 9ALOCNO, Characteristic '9ALOCATION' has Alpha conversion routine. So this conversion routine fills up the leading zeros. I removed Alpha conversion routine from the 9ALOCATION in RSA1 and it works fine now.

How to remove pound symbol # and preserve leading zeros in BEx Query

Hi,
I have two questions regarding the display in BEx Query.
1. How can I remove the pound symbol # for blanks in BEx Query?
2. How can I preserve leading zeros? At the moment, value "001" will be displayed as "1". But I need the leading zeros.
Thanks.
Joon

Hi ,
You can apply these settings in Bex query designer.
If you need to remove pound symbol jsut make a new formula and use NODIM function you will find this function under data functions.
So NODIM(Your price keyfigure) this will remove the Pound symbol.
For # just find out against which characterstic you are getting # then go to default values panel there you will find all your characterstic which you are using in report---Rt click -Restrict-single valuesdirect input-#-Move to selection(That forward arrow)--select that # and choose exclude from selection (That red square icon).
And yes for leading zeros check out this thread
Leading zeros not displaying
Hope it helps you.
Regards,
AL
Edited by: AL1112 on Jun 9, 2011 1:43 PM
Edited by: AL1112 on Jun 9, 2011 1:47 PM

MMBE & Leading Zeros

We have just upgraded to Ecc5 from 4.6c and t-code OMSL did not have the leading zeros checked. Leading Zeros appear in MMBE when the transaction is executed. They do not appear anywhere else in the system. Does anyone have any suggestions on how I can fix this with MMBE ?
Regards,
Nick

Application server file showing zeros infront of the material number.
1200# 0012401387# XXXXXXXX
Once file created in app server, I am using one custom FM to send that output in excel format / txt format via email.
when I send txt file via email, I am getting leading zeros. But when I send xls file via email, I am not getting zeros.
I checked custom FUNCTION MODULE . No mistakes in that.
===
Sudhir,
As you said, I passed ( ' ) single quote infront of the material number. When I check the excel file, single quote also displaying like this '0000100.
Application server file showing like below
1200# '0012401387# XXXXXXXX
===
Could you please advise anyone how can we acheive this.
Thanks

Leading zeros in the Product allocation characteristic combinations.

Hi All,
I am copying Characteristic combination from planning area to product allocation group, after i complete the transaction system is automatically preceding the zeroes to the product number.
I have one the following activities before copying CVC of planning area to product allocation group.
against all the Product allocation settings.
2.Created the MPOS with product (characteristic length of Product is 18), Customer and Allocation object.
3.Created planning area and planning book.
4.Copied cvc combination from planning are to product allocation group and also copied planning area values in to Product allocation group.
5.Tried to check in the ATP simulation mode, while I was doing system has given no characteristic combination found, when I checked Product is preceding zeros as per the filed MATNR length 40 and this MATNR is selected from the Product allocation field catalog, But when I add zeros to product system is performing Product allocations in simulation mode.
6.Tried triggering gATP Product allocations by creating Order in ECC, here also it has given same error No characteristic combination exists.
When I did initial R&D on this. I found that material number in the product allocation characteristic combination is leading by zeros for ex:- 000000000000000002200325.
Could any one please suggest me what to do on this.
Thanks and Regards,
T.Muthyalappa

Hi Muthyalappa ,
If i have understood your question properly , then my guess is you should be facing this problem only for numeric material codes. Try out the following things
1. Execute the same test condition for a non numeric material. I believe it will work perfectly .
2. For numeric material codes it is not working because of the difference in MATNR length between ECC and APO. In ECC the maximum possible MATNR length is 18 char whereas it is 40 chars in APO. So as per std SAP functionality the numeric materials get concatenated with leading zeros when you try to transfer it (or carry out any kind of processing ) from ECC to APO.
ex consider material 12345. In ECC it will be stored internally as 13 leading zero's followed by12345 . But in APO it will be stored as 35 leading zero's followed by 12345. Your issue is the system does not recognize the CVC that has this material as characteristic. At the time of cvc creation / change make sure your material characteristic ( especially for numeric material codes) totally has 40 chars . Pack it with leading zeros and make the material length 40.
Try this out and update me .
Thanks
Saradha

Leading zero for Product ID deleted when posting confirmation

Dear All,
I'm facing a problem when posting confirmation document from SRM to backend for PO item WITHOUT account assignment. When I want to post confirmation document, there is an error message 'Material document data and PO data do not match (Material )'. When I check the Idoc for confirmation, the leading zero in product ID was deleted in Idoc. For Example:
The product ID is 000000001600000000 (18 character, as defined in Tcode COMCPRFORMAT) when confirmation document created, but the document can't be posted, I can only save the document. And when I check the Idoc, the product ID became 1600000000.
I've already create a PO and confirmation for the same product using account assignment (Cost Center). And confirmation posted succesfully in backend. FYI, I've already implement note 1568941 in my SRM system.
Does anyone here ever have the same problem?
Rgds,
Aleluya.

problem solved after implement note 1592750
Rgds,
Aleluya sap.

Leading zeros in product ID for catalog items

Hi,
Does anyone know why some product IDs in the catalog have leading zeros while some don't? It's a hassle to the users to add a wildcard character in the product ID when searching for items in the catalog just because the product ID format is inconsistent. How do we correct the existing catalog items with leading zeros in the product ID and how do we prevent this from happening again.
Many thanks,
Joy

Hi Joy,
Are the catalog items created in SAP CCM 2.0 SRM_EXTRACTED_CATALOG by extraction from SRM_SERVER or created manually by upload file or similar?
Regards,
Jason

EBS check number with leading zeros

When we upload EBS, we are getting the check number in the record 16 (reference field). But unlike the check number posted in SAP, the check number in the BAI file has 2 leading zeros. Now since check number is coming in record 16, instead of record 88 we are not able to solve this problem through String configuration.
So, we thought of following solutions(Options):
1. Modify the check lot numbers to have two leading zeros plus associated changes like the form and so on.
2. Modify the check number in the incoming file u2013 strip the check number with two leading zeros with the use of customer enhancement. (After upload and before posting)
Can we solve the problem of leading zeros (before the check number) through any configuration steps instead of changing the SAP script form for check(Check lot) or going for customer enhancement.
Thanks
Ron

You are correct, since the check numbers are coming through only in the 16 records and not in the 88 records, you cannot use a search string to resolve the issue with leading zeros. Also, I do not know of any other configuration that can be used to reformat the reference values in the 16 records.
The 2 solutions you have listed are both valid options. Although with the first option (changing the check lots), you would need to make sure the business users approved of changing the check lots before going forward with that option. And you would still have to manually clear checks that had been issued prior to the check lot change.
At my company, we went with the second option - using ABAP code to update the check numbers from the file to match those in SAP (we actually had to add leading zeros to the check numbers). In our case, we had already created a pre-processor program for other re-formatting of the file that was needed prior to loading it into SAP - so we added the check number logic to that.
However, if you do not have a pre-processor program, I know there is a user exit available for EBS - exit EXIT_RFEBBU10_001, include ZXF01U01. I have heard of others using this exit to update the check numbers from 16 records. The exit is called during the FF.5 processing.
Regards,
Shannon

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

Visual Studio Projects Not Showing FileVesion Leading Zeroes in File Properties

I created a simple Visual Studio 2013 windows form application setting the AssemblyInfo.cs file as show below.
// You can specify all the values or you can default the Build and Revision Numbers
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0227")]
[assembly: AssemblyFileVersion("1.0.0.0227")]
[assembly: AssemblyInformationalVersion("0.0.0.0227")]
I built the application and went to the Windows File Explorer and brought up the file properties. What I see is that the product version showing the leading zeros, but the file version field does not show the leading zeros.
It appears to be a bug either with Visual Studio or with Windows. Which one is it and is there a fix?

Hi Sarah,
We can't see the screenshot. Do you mean you use Windows Explorer to browse to the AssemblyInfo.cs file and check the property?
If you change the product version or the file version from the AssemblyInfo.cs file, you need to firstly rebuild the assembly, then if you go to the debug/release folder, check the property of the assembly file, the Details tab will show you the corresponding
changes of these properties. It's the assembly property but not the cs file property.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

CRM 7.0 Leading zeros on material in sales documents delta replication

Hi
During initial load of sales documents from ECC to CRM the item is replicated with leading zeros.
The consequences is that CRM do not find the product and the crm order gets an error message that the product is not maintianed in product master.
So my question is; how to replicate the order without leading zeros for items?
BR
Johan

Hello Johan,
You need to check txn:OMSL in ERP and you need to make sure that settings are in sync with CRM customizing path settings.
SPRO>IMG>Cross-Applicaiton Component>SAP Product>Basic Settings-->Define O/P Format..
Especially you need to check for the lexicographical flag.
If this flag is set, then 0123 is different from 123.
Hope this helps!
Best Regards,
Shanthala Kudva.

Truncation of leading Zeros when Down Loading into Excel - OLE Objects

Hi,
Can any one help me on this.
I am using <b>OLE Objects</b> to download Data into Excel Sheet. Data with leading Zeros is getting truncated in Excel.
Ex: Report Output is showing Plant Number as 0002. But when i am downloading to Excel Plant value will become 2 .
   I would like to have it as 0002 in Excel.
I have declared Werks as CHAR of 4.I am using OLE Obects for Downloading into Excel Sheet.
I am using "OLE2_OBJECT" I can not use any other FMs to down load to Excel.As i am modifying this program not creating.
Thanks In Advance.
K.Nirmala
Message was edited by: Nirmala Reddy

Hi Nirmala,
While downloading to excel sheet, u need to change the number format of cell from General to Text, then leading zero's won't get deleted. For that u need to set the property of the cell. Please check this sample code,
INCLUDE OLE2INCL.
tables : zobrent.
data : it_kna1 type table of zobrent with header line.
handles for OLE objects
DATA: H_EXCEL TYPE OLE2_OBJECT,        " Excel object
      H_MAPL TYPE OLE2_OBJECT,         " list of workbooks
      H_MAP TYPE OLE2_OBJECT,          " workbook
      H_ZL TYPE OLE2_OBJECT,           " cell
      H_F TYPE OLE2_OBJECT.            " font
DATA H TYPE I.
DATA: cell1 TYPE ole2_object.
*&   Event START-OF-SELECTION
START-OF-SELECTION.
select * from zobrent into table it_kna1
           where zopanid = '10001'
            and zo_brent = '050'.
start Excel
CREATE OBJECT H_EXCEL 'EXCEL.APPLICATION'.
PERFORM ERR_HDL.
SET PROPERTY OF H_EXCEL 'Visible' = 1.
get list of workbooks, initially empty
CALL METHOD OF H_EXCEL 'Workbooks' = H_MAPL.
PERFORM ERR_HDL.
add a new workbook
CALL METHOD OF H_MAPL 'Add' = H_MAP.
PERFORM ERR_HDL.
output column headings to active Excel sheet
PERFORM FILL_CELL USING 1 1 1 'EDate'.
PERFORM FILL_CELL USING 1 2 1 'Brent'.
PERFORM FILL_CELL USING 1 3 1 'Zopanid'.
PERFORM FILL_CELL USING 1 4 1 'Contract Type'.
PERFORM FILL_CELL USING 1 5 1 'Price Type'.
PERFORM FILL_CELL USING 1 6 1 'Installation Type'.
PERFORM FILL_CELL USING 1 7 1 'Volume'.
PERFORM FILL_CELL USING 1 8 1 'AQ'.
PERFORM FILL_CELL USING 1 9 1 '00000123'.
LOOP AT IT_KNA1.
copy values to active EXCEL sheet
    H = SY-TABIX + 1.
    PERFORM FILL_CELL USING H 1 0 IT_KNA1-zo_effdat.
    PERFORM FILL_CELL USING H 2 0 IT_KNA1-zo_brent.
    PERFORM FILL_CELL USING H 3 0 IT_KNA1-zopanid.
ENDLOOP.
CALL METHOD OF h_excel 'Cells' = cell1
    EXPORTING
      #1 = 1
      #2 = 1.
FREE OBJECT H_EXCEL.
PERFORM ERR_HDL.
if sy-subrc eq 0.
   write : / 'year'(001).
endif.
     FORM FILL_CELL
sets cell at coordinates i,j to value val boldtype bold
FORM FILL_CELL USING I J BOLD VAL.
CALL METHOD OF H_EXCEL 'Cells' = H_ZL EXPORTING #1 = I #2 = J.
PERFORM ERR_HDL.
GET PROPERTY OF H_ZL 'Font' = H_F.
PERFORM ERR_HDL.
SET PROPERTY OF H_F 'Bold' = BOLD .
PERFORM ERR_HDL.
***Changing the format of the cell from General to Text
<b>SET PROPERTY OF H_ZL 'NumberFormat' = '@'.</b>
PERFORM ERR_HDL.
SET PROPERTY OF H_ZL 'Value' = VAL .
PERFORM ERR_HDL.
ENDFORM.
*&      Form ERR_HDL
FORM ERR_HDL.
IF SY-SUBRC <> 0.
WRITE: / 'Fehler bei OLE-Automation:'(010), SY-SUBRC.
STOP.
ENDIF.
ENDFORM.                    " ERR_HDL
U just paste this code in a sample program & see.
Please reward, if found helpful.

Adding leading zeros before data loaded into DSO

Hi
In below PROD_ID... In some ID leading zeros are missing before data loaded into BI from SRM into PROD_ID. Data type is character. If leading zeros are missing then data activation of DSO is failed due to missing zeros and have to manually add them in PSA table. I want to add leading zeros if they're missing before data loaded into DSO.... total character length is 40.. so e.g. if character is 1502 then there should be 36 zeros before it and if character is 265721 then there should be 34 zeros. Only two type of character is coming either length is 4 or 6 so there will be always need to 34 or 36 zeros in front of them if zeros are missing.
Can we use CONVERSION_EXIT_ALPHPA_INPUT functional module ? As this is char so I'm not sure how to use in that case.. Do need to convert it first integer?
Can someone please give me sample code? We're using BW 3.5 data flow to load data into DSO.... please give sample code and where need to write code either in rule type or in start routine...

Hi,
Can you check at info object level, what kind of conversion routine it used by.
Use T code - RSD1, enter your info object and display it.
Even at data source level also you can see external/internal format what it maintained.
if your info object was using ALPHA conversion then it will have leading 0s automatically.
Can you check from source how its coming, check at RSA3.
if your receiving this issue for records only then you need to check those records.
Thanks

Leading zero check got activated in production .

Similar Messages

Maybe you are looking for