you can use this object, if you create a workorder and work with Scripts.
don't declare this object.
(this object is in ue_produktconfig_script)
More Information for use this object: see Training-Unit "99_variantenscript"
User-Function
addbom |
you can use this command in the variant-script in the assembly to create new bom-Positions |
addrouting |
you can use this command in the variant-script in the assembly to create new routing-Position |
addparallelresource |
you can use this command in the variant-script in the assembly to create a parallel-Resource-Position Properties: ressource, activ, alternativ, description, costelement, timereservation Example: variant.addparallelresource=resource_id=1000,description=you can use this, ... |
propertie=field |
you can set the properties in the bom- and routing-position in the position-variantscript (the yellow c left of the position-number in the bom- and routing-Position) Example: variant.menge_verbrauch=5 |
Properties for bom
itemcode |
(or art_id) |
quantity |
(or menge_lager, menge_verbrauch) |
quantity by |
(or menge_je) |
roundingtype |
(or round_type) 0=rounding at .5, 1=rounding up, 2=rounding off, 3=multiple of, -1=no rounding |
roundingdec |
(or round_dec): count of decimal place for round type 1 or 2 |
routingpoisition |
(or aplanpos_id) link to the routing (beas_ftapl.pos_id) |
length |
(or abm1) |
width |
(or abm2) |
height |
(or abm3) |
activ |
(or aktiv, actice). set 1, true, j or y for success |
warehouse |
(or whscode): the warehouse for issue |
additionaltext |
(or usertext) |
udf1..15 |
udf1 to 15 |
price |
the price (higher prior as the standard-price-finding - only by create the calculation. Only by calculation. use format variant.price=<newprice,#0.000000> |
itemname |
set the itemname |
Properties for Routing
resource_id |
(or aplatz_id): link to resource beas_aplatz.aplatz_id |
operation |
(or ag_id): link to cataloge beas_ag. if you change this propertie, beas don't load the other properties from the catalog! It is a define only for this field without functionality! |
clockmandantory |
(linked with field bde) set true/1/Y/J for success |
desciption |
(or bez) |
setup |
set the field traplatz and tr2aplatz and define the setup-time |
setup_calculation |
(or traplatz) set only the setup-time for calculation |
setup_scheduling |
(or tr2aplatz) set only the setup-time for schedulung |
time |
(or teaplatz) set the time per piece |
costelement |
(or timetype_id) |
timefor |
(or menge_je) linked to field "menge_je" |
timein |
(or menge_zeitje) set only 1 = per minutes, 60=per hour |
usefaktor |
(or nutzen) |
worksteps |
(or anzahl) |
idletime |
(or tl) |
overlapptime |
(or ueblgrz) |
scrapfactor |
(or ausschussfaktor) |
qcinspectionplan |
(or qs_id) |
payslips |
(or anzls) |
udf1...15 |
udf 1 .... udf15 |
external_price |
(or fag_price) |
external_priceper |
(or fag_priceje) |
external_minprice |
(or fag_minprice) |
external_transportprice |
(or fag_transportprice) |
external_transportpriceper |
(or fag_transportpricea) |
external_currency |
(or currency) |
supplier |
(or cardcode) |
feedback_unit |
(or rm_me_id) |
feedback_factor |
(or rm_faktor) |
activ |
(or aktiv, actice). set 1, true, j or y for success |
aktivformel |
you can set this to "N" |
resource_fc |
Resource-Fullcost. If this value not 0, then beas use this resource-cost for full cost. Only in Precalculation. Not compatible for the Postcalculation. Insert Costs in Field "beas_pk_pos.ag_vollkosten" Attention: Use decimal-Variables. Only in this way you've no problem with the decimal-Sign
dec lc_fc // use "." as decimal-Sign lc_fc=5.1234 // now convert to string variant.resource_mc=<lc_fc,#0.000000>
|
resource_mc |
Same as resource_fc, but for he Marginal Cost-Price. Insert Costs in Field "beas_pk_pos.ag_grenzkosten" |
System-Function
workplan_nextpos (resteworkplan) |
set the tool-counter to 0. beas use this, if the next labor-Pos is insert |
resetcounter |
set the workorderplan and bom-counter to 0 |
resetcreate |
destroy all create-commands |