cancel
Showing results for 
Search instead for 
Did you mean: 

Table ADLZSN (serialnumber used in QF01)

0 Kudos

Hello,

1: When we record a QM defect (QF01) a serialnumber had to be filled in here. We have a serialnumber without leading zero's but the systems asks for a serialnumber with leading zeros because table ADLZSN field SETON is marked'X'. Using table ADLZSN we found out that leading zero's are placed automatically by SAP. Switching this off still there is a problem that the serialnumber cannot be entered here, due to the fact that its the serial number we have for this material. What do we have to do to make this work. It seems that OSS note 608872 cannot be used because this note is not relevant for the SAP system we are using. Please help. We are also aware of the conversion that had to be done with existing serialnumbers but what about new QM defects??

2: Table ADLZSN is used for telling the system that serial numbers are filled with leading zero's. OSS note: 211653 tells us the following:

Solution

The solution is available as a special development available within IS-A&D release 4.6B.

Call customizing transaction OLZSN and create one new entry and switch the field "Leading Zeros" (SETON) on. The client is then set to allow leading zeros. Remark: If an entry already exists in this table, use this entry, do not create another entry. Only the first entry is used.

When working with this functionality, the user now has to enter the exact number of leading zeroes every time a serial number is accessed! Evaluate whether this is acceptable in your business. It will work fine in environments that use shorter or externally assigned serial numbers.

A workaround in the standard is to use a special alphanumeric character in front of the serial number with leading zeroes. The number will then not be treated as numerical and saved "as is" on the database.

This functionality should not be switched on lightheartedly. It will not be possible to switch back to the old way of handling serial numbers without a mass maintenance program which doesn't exist as of this note."

using the programm: SAPLIPW1   /   DIMPG_LIPW1F16================E   line 7:

5             ENDENHANCEMENT.

6             ENHANCEMENT 2  .

7             SELECT single * FROM adLZSN.

8                 if sy-subrc = 0.

9                   if adlzsn-SETON = 'X'.

10                    IF CH_SERNR CO '0123456789 '.

11                       TRANSLATE CH_SERNR TO UPPER CASE.  "#EC TRANSLANG

You see that a here a select single without key is used, therefore always the first entrie in the table is read even if the serial profile isn't used anymore.

This is not the only programm where this is found, All the programms that are using this table works the same way. Is this a bug in SAP or ??? Would this also mean that the other entries doesn't make any sence??

Please tell us.

Thanks an advance.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

The code is getting the first entry found in the table. If you want do disable this functionality simple remove all entries from the table. This will cause in SAP filling leading zeros automatically in conversion routines:

CONVERSION_EXIT_ALZSN_OUTPUT

CONVERSION_EXIT_ALZSN_INPUT

Please check oss note 198285 and adjust your system to the correction instructions.

Greetings,

0 Kudos

Hello Ivaylo, This can be done or even better this should be the most proper way to do. But even then Why is htere a table entrie possible and when reading the code itś always a read single.

On the other hand the reason for this is that the problem is that when transacion QF01 is done a serial number is select, via F4 and when the enter is pressed the system says that the serial number cannot be used. I have also mentioned this at SAP and they told me that an OSS message was made but not released yet.