The SSCC external number range with non-numeric char assignment for HU

[Former Member]

Hi the requirement is to have the vendor code embedded in the 13 digit SSCC code generated while doing the Hundling Unit Management.

The config has been done and we get the 18 digit code with also contains but only numeric characters .

my customer need to Hundling Unit Management. with non-numeric characters the vendor code.

I defined configured number by plant storage location level and assigned to pkg material type

If any can help me to configure the external number range for HU with non-numeric characters

Regards

[Former Member]

Hi all,

Extract from SAP NOTE "1930424 - How to get External Handling Unit number as alphanumerical type" indicates the following:

---------------------------

CAUSE

• In SAP standard, it's not possible to get HU identifications with letters.
• Alphanumerical numbers are not allowed. You have to use numerical numbers because the field HU is a numeric field which is hard coded.
• All programs in R/3 are designed to read HU with this data format.
• Number Length Domain is NUMC20

RESOLUTION

• External Alpha Numeric ID is not possible in the HU.
• However, you can implement your own coding to get EXIDV with letters in user-exit EXIT_SAPLV51S_001 (called in V51S_CREATE_HU_HEADER).
• Ensure that changing the number range should not lead to further problems.

--------------------------------

OUR RESEARCH:

Approach - 1: SAP’s mentioned advice as per SAP NOTE 1930424

• Implemented the change in the user exit, by passing the value into the field. But when we tested the result the following happened:
• When the user enters the alphanumeric value on the screen then SAP checks for the validity of the external HU before executing the code in the user exit. Since the SAP standard number range does not accept alphanumeric values it fails and errors out.

Approach - 2: Creating a custom number range and using it instead of the SAP standard

• We created a custom number range ZHU_VEKP and defined it exactly same as the SAP standard number range (HU_VEKP) with the difference of the "Number Length Domain". We defined it as CHAR20 (HU_VEKP had it as NUMC20).
• We then change the "NR Transaction" (found in the "Customizing" section) for ZHU_VEKP to HUEX. This is what is also maintained for HU_VEKP. At any given time there can be only 1-1 mapping between the number range object and the NR transaction. Thus to be able to do this you will have to remove it from HU_VEKP and then add it to ZHU_VEKP.
• After this, whenever you go to (in transaction SPRO) Logistics General --> Handling Unit Management --> External Identification --> Number Range Maintenance for HU identification, you will notice that it will refer to ZHU_VEKP object instead of HU_VEKP.
• The above ensures that a user can maintain ranges in ZHU_VEKP directly from SPRO. But when it comes to assigning it to a Packaging Material Type, it’s a puzzle. To be able to use a number range one needs to assign it to the Packaging Material Type which is available at Logistics General --> Handling Unit Management --> External Identification --> Define Number Assignment for Each Packaging Material Type. Over here, once should be able to assign it under the column "Number Assignment" against the particular Packaging Material Type. But on F4 one notices that there are only the following options (thus clearly indicating that ZHU_VEKP is not available to assign):

A	SSCC18 already at creation of handling unit
B	Number range interval 'HU_VEKP'
Any external number can be entered (no HU functionality)

CONCLUSION:

The only way which we believe we can achieve the requirement is by directly changing the Number Length Domain from NUMC20 to CHAR20. But this would mean changing the SAP Standard.

Hope this helps.

Regards,

Ujjval

[Former Member]

Hello Lior,

We are implementing same scenario currently at my client place. Can you please help, how to replace HU number with SSCC number. Is there any BADI or Enhancement to do this.

Thanks,

Kamal.

[Former Member]

Dear Eleonora,

You wrote: "In standard it is not possible to get HU identifications with letters. Handling Unit numbers can only contain numeric values in standard." Isn't that too general a statement? It is definitely true for Handling Units to be numbered according to SSCC, i.e. based on number range object LE_SSCC (although the number length domain is CHAR9), and the restriction does make sense because SSCC is an international standard consisting of numerals only. However, if Handling Units are numbered externally based on object HU_VEKP with a domain of the CHAR type, alphanumeric IDs can be used (as I saw for myself by re-testing it today). In fact, I had quite a few customers who had the requirement to number Handling Units alphanumerically from external sources and who - to the best of my knowledge - implented this. WM is another issue, but as you already wrote, there is a user exit for the purpose.

Best regards,

Christiane

Edited by: Christiane Schnellenbach on Mar 2, 2010 2:19 PM

[Former Member]

Hi Christiane,

Per our analysis:

Extract from SAP NOTE "1930424 - How to get External Handling Unit number as alphanumerical type" indicates the following:

---------------------------

CAUSE

• In SAP standard, it's not possible to get HU identifications with letters.
• Alphanumerical numbers are not allowed. You have to use numerical numbers because the field HU is a numeric field which is hard coded.
• All programs in R/3 are designed to read HU with this data format.
• Number Length Domain is NUMC20

RESOLUTION

• External Alpha Numeric ID is not possible in the HU.
• However, you can implement your own coding to get EXIDV with letters in user-exit EXIT_SAPLV51S_001 (called in V51S_CREATE_HU_HEADER).
• Ensure that changing the number range should not lead to further problems.

--------------------------------

OUR RESEARCH:

Approach - 1: SAP’s mentioned advice as per SAP NOTE 1930424

• Implemented the change in the user exit, by passing the value into the field. But when we tested the result the following happened:
• When the user enters the alphanumeric value on the screen then SAP checks for the validity of the external HU before executing the code in the user exit. Since the SAP standard number range does not accept alphanumeric values it fails and errors out.

Approach - 2: Creating a custom number range and using it instead of the SAP standard

• We created a custom number range ZHU_VEKP and defined it exactly same as the SAP standard number range (HU_VEKP) with the difference of the "Number Length Domain". We defined it as CHAR20 (HU_VEKP had it as NUMC20).
• We then change the "NR Transaction" (found in the "Customizing" section) for ZHU_VEKP to HUEX. This is what is also maintained for HU_VEKP. At any given time there can be only 1-1 mapping between the number range object and the NR transaction. Thus to be able to do this you will have to remove it from HU_VEKP and then add it to ZHU_VEKP.
• After this, whenever you go to (in transaction SPRO) Logistics General --> Handling Unit Management --> External Identification --> Number Range Maintenance for HU identification, you will notice that it will refer to ZHU_VEKP object instead of HU_VEKP.
• The above ensures that a user can maintain ranges in ZHU_VEKP directly from SPRO. But when it comes to assigning it to a Packaging Material Type, it’s a puzzle. To be able to use a number range one needs to assign it to the Packaging Material Type which is available at Logistics General --> Handling Unit Management --> External Identification --> Define Number Assignment for Each Packaging Material Type. Over here, once should be able to assign it under the column "Number Assignment" against the particular Packaging Material Type. But on F4 one notices that there are only the following options (thus clearly indicating that ZHU_VEKP is not available to assign):

A	SSCC18 already at creation of handling unit
B	Number range interval 'HU_VEKP'
Any external number can be entered (no HU functionality)

CONCLUSION:

The only way which we believe we can achieve the requirement is by directly changing the Number Length Domain from NUMC20 to CHAR20. But this would mean changing the SAP Standard.

Regards,

Ujjval

[Former Member]

Hi,

(I sent the information to you today, just to inform people with same requirement:)

In standard it is not possible to get HU identifications with letters.

Handling Unit numbers can only contain numeric values in standard.

However, you can implement your own coding to get EXIDV with

letters in user-exit EXIT_SAPLV51S_001 (called in V51S_CREATE_HU_HEADER)

You will also have to change the number range object from NUMC to CHAR,

but that will be a modification of the standard.

Please also take into consideration that in case of HUM and WM managed

storage locations the HU numbers are taken over as SU numbers, and the

SU numbers also do not support alphanumeric numbers, this would also

only possible during a modification. Please check the attached note

63720 for this.

Regards,

Ely

[Former Member]

Lior,

In standard, number range object HU_VEKP provides for 20 digit numbers. You could replace the domain NUMC20 by domain CHAR20, for example, to be able to maintain number range intervals that suit your purpose.

Best regards,

Christiane

[Former Member]

Lior,

Why couldn't a container be a Handling Unit? Or do your containers circulate between your company and your vendor(s)?

Best regards,

Christiane

[Former Member]

Thanks for your answer.

One problem of using the standard object of HU

: object HU_VEKP includes 9 position only and I need HU = 13.

Second problem: object HU_VEKP accepts alpha-numeric characters only i need not numeric character:

Example of container numbers

ZCSU2675322

GVCU5256646

CBHU8681690

Regards

Lior

[Former Member]

Dear Lior,

As Baseer already wrote, SSCC is an international standard that uses numerals only. However, the usage of external numbers for Handling Units is not prevented by setting the "HU ID unique" indicator. The system checks the uniqueness of an external number and refuses it if it already exists in the client.

If you want to work with alpha-numeric Handling Unit IDs, you could think of changing the number length domain of the number range object HU_VEKP so that it accepts alpha-numeric characters.

Best regards,

Christiane

[Former Member]

Hi,

Thanks mate ...

But my issue is Handling Unit = Container and i need standart solution

Maybe is not good idea to use number range functonality for this problem

Regards

[Former Member]

You cannot have alpha numeric numbers in SSCC. This will not meet the GS1 standards for SSCC numbers.

If you wish to have an external number for your HU then SAP cannot gurantee the uniqueness for handling units. Therefore you have to switch off the unique HU flag. This will then allow you to enter any external number as a HU number.