cancel
Showing results for 
Search instead for 
Did you mean: 

Next Number Maintenance fails to show right replaceable parameters

Former Member
0 Kudos

System: SAP ME 6.0.4.0

I am trying to define the numbering pattern for SFC in Next Number Maintenance (Number Type = Floor Stock Receipt). The online documentation describes the replaceable parameters that can be used as prefixes or suffixes.

If I use one of the following replaceable parameters:

%ITEM_GROUP_BO.(1)%

%ITEM_GROUP_BO.(2)%

%PARENT_SHOP_ORDER_BO.(1)%

%PARENT_SHOP_ORDER_BO.(2)%

%PRIORITY%

%SHOP_ORDER_BO.(2)%

%USER_BO.(1)%

%USER_BO.(2)%

ME fails to show me the right sample next number:

ITEM_GROUP_BO.(2)100014*

i configured the following:

Prefix:                     %ITEM_GROUP_BO.(2)%%ITEM_BO.(1)%

Suffix:                     %ITEM_BO.(2)%

Number Base:         10

Current Sequence:   14

Thanks for your help,

Markus

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I originally missed the fact that you were using  %ITEM_GROUP_BO.(2)%.   That is not a valid string since Item Groups only have two parts to the handle: Site and Item Group.   Element 2 is not available in the item group.  Try  %ITEM_GROUP_BO.(1)% instead.  I am not sure why it works sometimes.

Also, try using various combinations of %% to see if you can combine 2 entries without any characters between them.  Maybe %%% might work.

The ability to use two %...% strings next to each other without a character in between is a design gap.  I am not sure how to fix that without causing problems for the customer.  It might not be simple.

Answers (2)

Answers (2)

Former Member
0 Kudos

It is probably not a bug.  The string '%%' means use a single % in the generated next number.

Try putting a character between the the %% in your example:

        %ITEM_GROUP_BO.(2)%_%ITEM_BO.(1)%

Using two % characters to mean display a single % might be a problem for this type of scenario, but I suspect we won't be able to change it without affecting existing customers.

Former Member
0 Kudos

Hey Mike,

thanks for answer my question.
We need this constellation for our customer without any characters beetween %%. e.g. %ITEM_GROUP_BO.(2)%%ITEM_BO.(1)%

If i use your example %ITEM_GROUP_BO.(2)%_%ITEM_BO.(1)% SAP ME shows the same mistake. e.g. ITEM_GROUP_BO.(2)_1000

the same if i configurate the single
parameter %ITEM_GROUP_BO.(2)% e.g. ITEM_GROUP_BO.(2)

Thanks,
Markus

0 Kudos

Hi Markus,

Looks as if you have found a bug. Please submit a support ticket to MFG-ME-MNT component.

Regards,

Sergiy

Former Member
0 Kudos

Hi,

I want SFC number to be same as shop order number and this is what i have done in "next no.maint'.

Prefix:%SHOP_ORDER_BO.(2)%

number base:10

Current sequenc : DONT know what to enter here.

Rest all the fields are empty.

If i enter any number in 'current seq'..that no. will get suffixed to my shop order no. which i don't want.I want only the shop order no.as my SFC no.

Please suggest.

Thanks.

Regards

Mansi

0 Kudos

Mansi,

Current Sequence is a required field - you cannot leave it empty.

It is a counter that is used during creation of ID.

Maybe you should generate SFC by DM520 at Start to be able to manually enter the ID you need.

Regards,

Sergiy

Former Member
0 Kudos

Hi Sergiy,

I am not able to get the expected result.

Can you please elaborate on "number base' and 'current sequence' entries when i want to assign 'replacebale parameters' @ 'next number seq' .

I want SFC number to be same as my shop order no.Hence in prefix field i enter '%SHOP_ORDER_BO.(2)%' and keet suffix field blank.

Please guide me on this.

My final requirement is to get SFC release no. same as shop order no.

Regards

Mansi

0 Kudos

Mansi,

By means of NN Maintenance you cannot get the SFC with the ID equal to Shop Order because the value of Current Sequence is always added to the Prefix which is your SO number.

But you can generate SFC ID whatever you want if you use DM520 to create the SFC on fly. The details on DM520 can be found on this forum or in the online help.

Regards,

Sergiy