Bom lotsize

my bom has the lot size 1 to 1000
i like to change it to 1 to 2500
is it possible to change the existing bom.
which controles the lot size entry in bom any default setting can be made
kindly explain .

Hi,
In Header Screen go to Edit ---> Define Tech. Type --> Select M (Multiple).
This will activate the Lot size fields in Header Data screen.
Regards,
Dhaval

Similar Messages

Select BOM as per lot size against planned quantity

Dear all
i hav prob. releated select BOM as per lot size against planned quantity , suppose i hav monthly plnned order for
1000 nos. quantity and having two alternative BOMs like lot size 0 to 500 and 0 to 200 , so after MRP run system should create planned order(inhouse prod.) as per lot size i.e. 500 x1 and 200x 2 ., how is it possible please guide me .
thankx in advanced

create a two production version , if the plan quantity is more than 200 system will take the Alternative BOM and take the BOM ( 0-500 ) otherwise system will take the BOm ( lotsize 0-200).
Or
Create a Production version, Manually change the PV as per your requirement , And rerun MRP with delete a recreate option
regards,
Sundaresan

Production order for alternate BOM and Routing

Hi All,
In my business(Discrete) scenario I have alternate bom and routing has group counters. some times i should use first BOM and First group counter. Then next Bom and next group counter. But lotsize is same( prodcution version how to assign).
When creating production order i should select which ever i need.
Regards,
S.Suresh.

> In my business(Discrete) scenario I have alternate bom and routing has group counters. some times i should use first BOM and First group counter. Then next Bom and next group counter. But lotsize is same( prodcution version how to assign).
>
> When creating production order i should select which ever i need.
>
Hi,
For your requirement you can define your Order Type Dependent parameters OPL8 as:
Production Version : 1 Manual Selection of production Version.
In this case every time when you creat your Production order System will ask for the Production version to be selected. You need to select the PV manually then only you can proceed further.
This setting is applicable only when the Production Order is Created.
It will not effect the Planned Oredr creation via. MRP Run..
Hope this helps..
Regards,
Siva

Differ Bom(sales,subcontracting ,stock transfer)

Dear All
As per the allover opinion i would like to introduced my query again with new thread.
Actully i want to create Bom For
1. Sales
2. Subcontracting
3. Stock transfer
4. Production
Like differ Production Version.
So how can we create the Bom and there differ version.

Pankaj,
The way i understand your requirement,
1. Sales BOM is required for you which is common accross all sales order, if this was the requirment then you need to create a BOM using transaction "CS01" with Usage = "5".
If you wanted to create a BOM specific for every sales order, then as the forum suggested you need to create it through transaction "CS61".
2. Subcontracting I assume that you would need a subcontracting BOM which would be delta from Production BOM.
In this case you need to create a BOM using transaction "CS01" with usage as "Production"=1, you could create this using copy option. System creates this BOM with an alternate number.
Since there are 2BOMs you need to differentiate through production versions, this can be directly created using transaction "C223" or in "MM02" - MRP4 View. Here you define which combination of routing and BOM is going to be used for production and subcontracting.
The trick here is that when a production order is created if the lotsize and validity parameters are same with both the production versions then system selects the lowest value production version, so always make the production related BOM production version as least value ex. "0001".
To handle the subcontract scenario, you need to assign the relevant production version in the Subcontracting category purchase inforecord (ME11) of the materail. If you are using Quto Arrangments you can assign this in Quto Master (MEQ1).
3. I assume that you are looking for BOM at the production plant for the material , it should be a normal production BOM with usage 1.
Hope this helps....Reward your points and close the thread if so,
Regards,
Prasobh

BOM is not getting displayed in case of centralized planning plant.

Dear All,
there are 2 plants for which we have centralized planning. the users have created Equipment BOM for the two plants. but in case of the second plant for which the planning plant is different from the maintenance plant, the BOM is not getting displayed in the Maintenance Order (i.e. in the components tab).
kindly through some light on it. whether i have to do some settings for it.
Regards,
Ritesh Kapoor

Hi,
Yes while using IH01, i have ticked the BOM explosion option, but when i am giving the plant there then only it is displaying the BOM of that equipment.
Also when i am creating an order for the same equipment, then it does not displays the BOm & shows the message which i have written in my previous mail.
Ritesh

Report for bom wise target and actual cost as well as qty at line item

Dear Experts,
Is there any standard tcode for bom wise target and actual cost as well as qty at line item level for the month.
there is one tcode s_alr_87013127 but user has to double click in order to get line item details.
I want to see line item wise breakup/bom wise target and cost cost as well as qty.
Thanks in advance.
regards
RK

Dear experts,
I am still looking for a revert.
regards
RK

Error while creating BOM

Hi
iam facing error while creating, changing and display BOM.
Error: Status MHCO of the user interface SAPLCSDI missing.
rgads

Dear,
MHCO - BOM item screen GUI status..Are you using any Alternative item?
Have you applied any new patch in the system?
Contact ABAPer, can give more details
In SAP service place serach for this interface program,,,you will get many notes on this.

Giving BOM material as free good in Sales Order

Hi,
I have a business requirement.
I want to give a free good in Sales Oreder which is a BOM material.This should be possible by manually changing Item category for the line item in the Sales Order just like how we can change TAN to TANN in normal circumsatnces when we add free good material for any NON BOM material.
In standard functionality,the item category determined for this BOM material is TAQ but this item category field in Sales Order is non editable because of which I can not include the BOM material as free good in my sales order.
I have already defined one z Item category for free goods for this BOM material & want to use it in Sales Order.
Can you please suggest how this can be handled ?
Or is there any other work around by which will allow me to include BOM material as free good in my Sales Order ?
Thanks in advance
Regards,
BM

Hi,
Thanks everyone for the feedback.I agree with Samir Danish.It is a standard functionality of SAP which does not allow free goods for BOM material.
However, can someone suggest work around to deal with this issue.I mean if any one has been doing any work around for this issue then please let me know.It s becoming critical for me.
Regards,
BM

BOM in Scheduling agreement (Type LZ)

HI
I am using scheduling agreement (Type LZ) for maintaining my sales plan for a period of 4 months. (1st one month - daily & subsequent months as weekly requirements). Ii would create delivery and invoices for each supply.
Pricing previously was based on the finished product (basic price for product was available). SO there was no problem.
<u>New requirement:</u>
finished Product above - is made up of components. Now, price should be derived from components. For this I have enabled SD Bom for my finish product.
But the problem is when i use the Finish product code in scheduling agreement type LZ, the BOM doesn't explode (it explodes in other scheduling agreement types, say LP)
Clarification:
1. Is it possible to calculate price of the higher level material by summing up the components' price?, with out BOM explosion
2. Is BOM explosion possible in scheduling agreement with delivery schedule (LZ).
Note:
1. Necessary settings for item category & BOM master already in place.
2. BOM is exploding in sales order and other sheduling types, except doc type LZ.

If it is maintained as error message, it does not allow me to maintain delivery schedule more than target quantity of 100 EA. Also the overdelivery tolerance is maintained as 20 %, so it should allow me to maintain delivery schedule of 120 EA, but it does not allow me to maintain greater than target quantity of 100 EA. Please let me know your comments.

Variable size item problem in BOM

hi all,
We have semi-finished material with componets as variable size items (item cat. R)
Now in the variable size tem data, Size 1 = 1,406 MM, Size 2 = 1,220 MM. Numner is 1 ST, formaula place is blank.
Qty Var-Sz Item is calculated by system is 3.957 M2. On what basis this value is calculated?
In the component material we have maintained a componenet scrap quantity as 15%.
BOM ratio of header : component = 1NOS : 1 ST
Again when we create a production order for the header, for 1 NOS header quantity component qty becomes 2.
For 2 NOS of header qty, component becomes 3 like this.
Why this happens..
Regards,
Srijit.

Thread closed

Error in BOM Dependency update

Hi Experts,
I have developed a BDC for BOM dependency it is working fine in foreground and it is throwing error in background, I am attaching the error screen and the code, please let me know where I am going wrong:

The error log in your screen shoot says that a certain field is not an input field. If it is working fine in foreground and giving this error in background, it could be because some programs have different screens or different versions of screens for background processing so if you made a recording in foreground the screens won't be quite right when run in background. To correct this issue you could try going to SHDB and making a new recording selecting check box "Simulate Background Mode".

PP - Explosão de BOM Phantom em Ordem Planejada

Olá pessoal!
Tenho um cenário onde dentro do meu Produto Acabado, tenho vários componentes organizados em Grupo de Alternates, e para cada grupo, defino um componente como Principal ( 100% de utilização ) e os outros como Opcionais ( 0% de utilização ). Entre esses componentes existem alguns que são configurados como Phantom ( Special Procurement 50 ), e esses itens Phantom, quando são Opcionais na BOM, ou seja, 0% de Probabilidade de Uso em Alternate Item Group, ele não é carregado na lista de componentes da Ordem Planejada. Apenas o Phantom que está como Principal aparece na Ordem Planejada, juntamente com seus subcomponentes.
Os demais componentes que não são Phantom, aparecem normalmente dentro da Ordem Planejada, tanto os que tem 100% de utilização, quanto os que tem 0% definido na BOM. Obviamente, toda a necessidade é apontada no item Principal, mas eu posso modificar de acordo com a disponibilidade do material.
Quando a Ordem de Produção é criada diretamente pela CO01, sem conversão de Ordem Planejada, a lista de componentes traz todos os Phantoms normalmente, independente do percentual de utilização.
Alguém sabe me dizer se existe algum tipo de configuração para permitir que os Phantoms Opcionais, também sejam carregados para lista de componentes das Ordens Planejadas sem precisar alterar o percentual de utilização na BOM?
Agradeço antecipadamente.

Olá Márcio,
você descobriu se há parametrização para sua questão?
Abraço.

Message type BOMMAT (change BOM)

Hello Guru,
I have some question and need help, when i try a standard transaction CS02, try to change a BOM material existing for example, the base quantity of the BOM was 650, i enter new data as 655, but suddenly retain the original Qty as 650 and save the changes as SAP will accept the changes i've done (BOM for material 2456 changed) but eventual i have not change any value to the original BOM. SO it mean this is standard SAP funtionality for CS02.
But when we use an interface using message type BOMMAT a standard SAP message tpye, we have created an IDOC using this message type and same data as the original was maintain to it, to be more exact we plan to change a BOM thru this IDOC but all the data we have is the same value of the original BOM, so we expect no error could be encounter of this IDOC since in standard CS02, changing of BOM even same value was inidicated did not had error message encountered when saving.
But thru our process, when we try to process the IDOC with message type BOMMAT in program RBDAPP01 (BD20) the idoc did not pass it when into status 51(Error when saving BOM. Please see the application log.) and when we check the BOM it has duplicate value upon executing the program we able to fix it when we delete the duplicate line segment in the IDOC and reprocess it once again.
my question is why in standard message type BOMMAT had encountered error when processing when we try to make change of BOM even the same value is carried out by the IDOC, and why in standard CS02 saving a change of BOm with same value as it is SAP accept the process? Please help and clear the process.
Any inputs R.Brahamankar and Vivek
Thanks
Edited by: Ryan on Feb 9, 2009 9:23 AM

BOMMAT and process code BOMM

Unused BOM components not getting filtered

I have written a Query for BOM, which is having ECM active. Earlier there were 14 components.
3 components have been removed. But If I execute my Query--it is getting all the 14 components
instead of 11.
In CS03--If I execute,
with both Valid from and Valid to date as today--Defaulted--Then 11 components are displayed.-OK
If I keep Valid from Only--Then 11 are displayed.--Ok
If I remove both Valid from and Valid to date--Then 14 are displayed.-Ok
If I keep valid to date --Then it is displaying all the 14 components.
That means Valid from is acting a s filter.
If I use the same Valid from--(Tried all the Valid From fields in STPO) in my Query--It is not taking.
The strange thing this, If we give that Particular date (On which the component is changed)--Then it is
taking and showing the output in the query.
The thing I need here is --The same functionality (Filtering criteria) has to be put into my Query.
P.S: Even Standard reports like CS11/CS12/CS13 are not filtering, in the way--CS02/CS03 are doing.
Any suggestions would be highly appreciable. Thanks in advance.
Wherever we see in the standard reports--The Valid to is coming from structures.

Hello,
You can try with CS11/CS12 where select Change No. and valid from date.
If you change a Material BOM with a change number then a new entry is created in the database (tables STPO, STAS).
Best Regards,
R.Brahmankar

Error-BOM is not valid

Hi all,
i am creating a BOM with item & sub item .
i am getting the error like BOM is not valid.
i am giving my coding below.plz suggest where i am doing mistake.
it's urgent.
can u plz give some sample coding where sub-item will be there in that BOM.
any idea will be highly appreaciated.
correct answers will be rewarded.
regards
pabitra
report z_bom_create
       line-size 132
       line-count 65.
      no standard page heading.
*-- DATA DECLARATION--
include <icon> .
*---Tables
tables : s076, t100, marc .
*---Types
types : begin of t_upload,      " Upload file data
         col1(18),
         col2(10),
         col3(30),
         col4(12),
         col5(50),
       end of t_upload,
       begin of t_split,
       location like stpu-ebort,
       end of t_split.
*data:begin of i_return occurs 10.
*include structure bapiret2.
*data:end of i_return.
data:i_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
types:begin of t_item."occurs 10.
include structure BAPI1080_ITM_C.
types:end of t_item.
types:begin of t_subitem." occurs 10.
include structure BAPI1080_SUI_C.
types:end of t_subitem.
types:begin of t_header." occurs 10.
include structure BAPI1080_MBM_C.
types:end of t_header.
types:begin of t_bomgroup." occurs 10.
include structure BAPI1080_BGR_C.
types:end of t_bomgroup.
types:begin of t_variant." occurs 10.
include structure BAPI1080_BOM_C.
types:end of t_variant.
data:it_itemas LIKE bapi1080_rel_itm_bom_c OCCURS 0 WITH HEADER LINE,
     it_subitemas LIKE BAPI1080_REL_SUI_ITM_C OCCURS 0 WITH HEADER LINE.
*--- Tables
data: i_upload type standard table of t_upload, " to hold data
      i_upload1 type standard table of t_upload,
      i_upload2 type standard table of t_upload,
      i_split type standard table of t_split,
      i_item type standard table of t_item,
      i_subitem type standard table of t_subitem,
      i_header type standard table of t_header,
      i_bomgroup type standard table of t_bomgroup,
      i_variant type standard table of t_variant.
data: wa_upload type t_upload, " to hold file data,
      wa_upload1 type t_upload, " to hold plan data,
      wa_upload2 type t_upload,
      wa_split type t_split,
      wa_item type t_item,
      wa_subitem type t_subitem,
      wa_header type t_header,
      wa_bomgroup type t_bomgroup,
      wa_variant type t_variant.
data:v_matnr like mara-matnr,
     v_start like sy-index,
     v_count(3) type c,
     v_num(4) type c value '0000'.
*--Constants
data: c_dot type c value '.',
      c_x type c value 'X',
      c_comma type c value ','.
-------Selection Screen Design -
*Selection screen for input of upload file address
selection-screen skip 2.
selection-screen begin of block blk1 with frame.
parameters     : p_file like rlgrap-filename obligatory .
parameters     : p_matnr like mara-matnr obligatory,
                 p_werks like marc-werks obligatory memory id wrk,
                 p_stlan like afko-stlan obligatory default '1' .
selection-screen end of block blk1.
---AT SELECTION SCREEN -
*at selection-screen on value-request for p_file.
**--For popup to select file.
perform f_give_help.
*at selection-screen on p_matnr.
perform f_check_matnr.
-----START OF SELECTION -
*--Data upload using WS_Upload.
perform f_get_data.
perform f_get_bom_data.
perform f_get_bom_data1.
perform f_call_bapi.
perform f_error_display.
*&      Form f_give_help
      text
--> p1        text
<-- p2        text
*FORM f_give_help.
*call function 'WS_FILENAME_GET'
      exporting
           mask             = ',.,..'
           mode             = 'O'
      importing
           filename         = p_file
      exceptions
           inv_winsys       = 1
           no_batch         = 2
           selection_cancel = 3
           selection_error = 4
           others           = 5.
if sy-subrc <> 0 and not sy-msgty is initial.
   message id sy-msgid type sy-msgty number sy-msgno
   with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*ENDFORM.                    " f_give_help
*&      Form f_check_matnr
      text
--> p1        text
<-- p2        text
*FORM f_check_matnr.
*CALL FUNCTION 'BAPI_MAT_BOM_EXISTENCE_CHECK'
EXPORTING
   MATERIAL              = p_matnr
   PLANT                 = p_werks
   BOMUSAGE              = '1'
VALID_FROM_DATE       =
VALID_TO_DATE         =
TABLES
   RETURN                = i_return.
*ENDFORM.                    " f_check_matnr
*&      Form f_get_data
      text
--> p1        text
<-- p2        text
FORM f_get_data.
call function 'WS_UPLOAD'
   exporting
CODEPAGE                      = ' '
      filename                      = p_file
      filetype                      = 'DAT'
    tables
      data_tab                      = i_upload
   exceptions
     conversion_error              = 1
     file_open_error               = 2
     file_read_error               = 3
     invalid_type                  = 4
     no_batch                      = 5
     unknown_error                 = 6
     invalid_table_width           = 7
     gui_refuse_filetransfer       = 8
     customer_error                = 9
     others                        = 10
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
ENDFORM.                    " f_get_data
*&      Form f_get_bom_data
      text
--> p1        text
<-- p2        text
FORM f_get_bom_data.
delete i_upload where col1 is initial.
delete i_upload where col1 cs 'ITEM'.
i_upload2[] = i_upload[].
delete i_upload2 where col1 cs 'FINISHED GOOD'.
read table i_upload into wa_upload with key col1 = 'FINISHED GOOD:'.
if sy-subrc = 0.
v_matnr = wa_upload-col2.
if v_matnr <> p_matnr.
message e001(zl) with p_matnr.
endif.
else.
message e000(zl).
endif.
ENDFORM.                    " f_get_bom_data
*&      Form f_get_bom_data1
      text
--> p1        text
<-- p2        text
FORM f_get_bom_data1.
loop at i_upload into wa_upload where col1 CS 'FINISHED GOOD'.
v_start = sy-tabix + 1.
loop at i_upload into wa_upload1 from v_start .
        if wa_upload1-col1 cs 'FINISHED GOOD'.
          exit.
        else.
perform f_split_upload_data.
     endif.
endloop.
      endloop.
ENDFORM.                    " f_get_bom_data1
*&      Form f_split_upload_data
      text
--> p1        text
<-- p2        text
FORM f_split_upload_data.
if not wa_upload1-col5 is initial.
if wa_upload1-col5 cs c_comma.
split wa_upload1-col5 at c_comma into table i_split.
loop at i_split into wa_split.
v_count = v_count + 1.
endloop.
if wa_upload1-col4 <> v_count.
   wa_upload1-col4 = v_count.
endif.
clear wa_upload1-col5.
clear wa_split.
clear v_count.
loop at i_split into wa_split.
wa_upload1-col5 = wa_split-location.
append wa_upload1 to i_upload1.
endloop.
else.
append wa_upload1 to i_upload1.
endif.
else.
append wa_upload1 to i_upload1.
endif.
clear wa_upload1.
ENDFORM.                    " f_split_upload_data
*&      Form f_call_bapi
      text
--> p1        text
<-- p2        text
FORM f_call_bapi.
clear wa_upload1.
wa_header-material = p_matnr.
*wa_header-plant = p_werks.
wa_header-bom_group_identification = 'BAPI_SMP_COL1'.
wa_header-bom_usage = p_stlan.
wa_header-alternative_bom = '1'.
append wa_header to i_header.
wa_bomgroup-bom_usage = p_stlan.
*wa_bomgroup-created_in_plant = p_werks.
*wa_bomgroup-bom_group = ''.
wa_bomgroup-object_id = 'SIMPLE1'.
wa_bomgroup-bom_group_identification = 'BAPI_SMP_COL1'.
wa_bomgroup-object_type = 'BGR'.
append wa_bomgroup to i_bomgroup.
wa_variant-alternative_bom = '1'.
wa_variant-base_qty = '1.000'.
wa_variant-valid_from_date = sy-datum.
wa_variant-bom_group_identification = 'BAPI_SMP_COL1'.
wa_variant-object_type = 'BOM'.
wa_variant-object_id = 'VAR'.
wa_variant-bom_status = '1'.
wa_variant-valid_from_date = sy-datum.
wa_variant-function = 'NEW'.
append wa_variant to i_variant.
it_itemas-bom_group_identification = 'BAPI_SMP_COL1'.
it_itemas-sub_object_type = 'ITM'.
it_itemas-sub_object_id = 'SIM'.
it_itemas-super_object_type = 'BOM'.
it_itemas-super_object_id = 'VAR'.
it_itemas-valid_from_date = sy-datum.
it_itemas-function = 'NEW'.
append it_itemas.
it_subitemas-bom_group_identification = 'BAPI_SMP_COL1'.
it_subitemas-sub_object_type = 'SUI'.
it_subitemas-sub_object_id = 'SIMP'.
it_subitemas-super_object_type = 'ITM'.
it_subitemas-super_object_id = 'SIM'.
append it_subitemas.
loop at i_upload2 into wa_upload2.
*wa_item-item_id = v_num.
*v_num = v_num + 1.
wa_item-bom_group_identification = 'BAPI_SMP_COL1'.
wa_item-object_type = 'ITM'.
wa_item-object_id = 'SIM'.
wa_item-item_no = wa_upload2-col1.
wa_item-item_cat = wa_upload2-col2.
wa_item-component = wa_upload2-col3.
wa_item-comp_qty = wa_upload2-col4.
wa_item-valid_from_date = sy-datum.
append wa_item to i_item.
endloop.
loop at i_item into wa_item.
loop at i_upload1 into wa_upload1 where col1 = wa_item-item_no.
wa_subitem-bom_group_identification = 'BAPI_SMP_COL1'.
wa_subitem-object_type = 'SUI'.
wa_subitem-object_id = 'SIMP'.
IF not wa_upload1-col5 is initial.
on change of wa_upload1-col5.
v_num = v_num + 1.
wa_subitem-subitem_no = v_num.
wa_subitem-subitem_qty = '1'.
wa_subitem-installation_point = wa_upload1-col5.
append wa_subitem to i_subitem.
clear wa_subitem.
endon.
endif.
clear wa_upload1.
endloop.
clear v_num.
clear wa_upload.
endloop.
CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'
EXPORTING
TESTRUN                  = ' '
ALL_ERROR                = ' '
TABLES
    BOMGROUP                 = i_bomgroup
    VARIANTS                 = i_variant
   ITEMS                     = i_item
   SUBITEMS                  = i_subitem
    MATERIALRELATIONS        = i_header
   ITEMASSIGNMENTS           = it_itemas
   SUBITEMASSIGNMENTS        = it_subitemas
TEXTS                    =
    RETURN                   = i_return.
*if i_return[] is initial.
*CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
*write: /'BOM created:', stpo-stlnr.
*else.
*if not i_return[] is initial.
*loop at i_return.
WRITE:/ i_return-type, i_return-id, i_return-number,
         i_return-message.
*ENDLOOP.
   IF i_return-TYPE = 'E'.
   errmsg-type = i_return-type.
   errmsg-line = i_return-message.
   append errmsg.
     ULINE /1(108).
     write:/ icon_led_RED as icon, i_return-MESSAGE.
     ULINE /1(108).
   ENDIF.
   IF i_return-TYPE = 'W'.
   errmsg-type = i_return-type.
   errmsg-line = i_return-message.
   append errmsg.
     ULINE /1(108).
     write:/ icon_led_YELLOW as icon, i_return-MESSAGE.
     ULINE /1(108).
   ENDIF.
ENDLOOP.
**write: / i_return-id, i_return-number, i_return-message(80).
**endloop.
**write: /'Error'.
**endif.
ENDFORM.                    " f_call_bapi
*&      Form f_error_display
      text
--> p1        text
<-- p2        text
FORM f_error_display.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
loop at i_return.
WRITE:/ i_return-type, i_return-id, i_return-number,
          i_return-message.
ENDLOOP.
ENDFORM.                    " f_error_display

Are u sure That BAPI is the right one to use to create BOM , I think this Error is coming from BAPI itself So try to Debug the BAPI from where its throwing the error.
Regards
prabhu

Bom lotsize

Similar Messages

Maybe you are looking for