Entity Relation: ItemWareHouse -> ItemCode

Entity Relation: ItemVersion -> ItemCode

Integration hub: Importable

Mandatory field

Primary key

Database: "OITM"."ItemCode"

Integration hub: Importable

Database: "OITM"."ItemName"

Version number of the item

editable. If it's defined in Item Version Control, it's not editable and the system is working with Item Version control

Linked table: BEAS_OITM_VERSION

Integration hub: Importable

Database: coalesce("OITM"."U_beas_ver",'')

Integration hub: Importable

Database: "OITM"."FrgnName"

Linked table: OCRD

Linked column: CardCode

Integration hub: Importable

Database: "OITM"."CardCode"

Integration hub: Importable

Database: "OITM"."CodeBars"

Linked table: OCRD

Linked column: CardCode

Integration hub: Importable

Database: "OITM"."CardCode"

Integration hub: Importable

Database: "OITM"."ItemType"

Database: case when "OITM"."InvntItem" = 'Y' then 1 else 0 end

Database: case when "OITM"."ManBtchNum" = 'Y' then 1 else 0 end

Database: case when "OITM"."ManSerNum" = 'Y' then 1 else 0 end

Define automatic batch number / serial number generation

can generate the batch automatically for a receipt transaction.

Here you can set up whether the batch is entered manually or generated automatically when posing in material.

Batch according to material

===========================

If an assembly is posted in, as batch number is determined that one of the first material in the BOM of the assembly which was last posted in.

Example:

Assembly: "Paste y in container x"

|- Bill of Materials: Paste y

|---|- 1. issue batch aaa

|---|- 2. issue batch bbb

If "Paste y in container x" is now produced and posted in, the batch number of "Paste y" of the last posting, i.e. batch "bbb" is assigned.

Automatic batch determination

=============================

Batches are generated automatically, at stock correction the next number can be requested.

see Batch generation

Special case at SAP-posting processes:

If the entry field for quantity is left with Ctrl-Tab, the batch assignment screen opens. There is a button "next batch"

Clicking there, the next batch number according to SAP - batch determination program is determined and entered to the current field.

Batches are always determined automatically.

Manual batch input

==================

If activated, manual batch input is always performed for this item.

Default Value: M

Constraints:

batchnum is same as last cunsumed material=J

automatic batch number generation=N

manual batch number=M

Integration hub: Importable

Database: "OITM"."U_batchroh"

stcklistenposition_bearbeiten.htm

Integration hub: Importable

Database: coalesce("OITM"."U_dispo",'K')

stcklistenposition_bearbeiten.htm

Integration hub: Importable

Database: "OITM"."PrcrmntMtd"

Database: case when "OITM"."PlaningSys"= 'Y' then 1 else 0 end

Return the Issue Method for this item

(Defined in Item Master Data)

B = Backflush

M = Manual

Batch- and Serial number related items always "M"

But you can overwrite this in configuration wizzard - Production - Material Posting - Backflush -

also post batch numbers

also post serial numbers

if this is activated, the system return "B" for Batch or/and Serial numbers too

Database: case when "OITM"."ManBtchNum"='Y' and 'J' = 'J' then 'B' when "OITM"."ManSerNum"='Y' and 'J' = 'J' then 'B' else "OITM"."IssueMthd" end

Default Value: 0

Constraints:

No=0

extented view=1

separate bom=2

Integration hub: Importable

Database: coalesce("OITM"."U_beas_VerControl",0)

Database: (select count(*) from "BEAS_ITEM_VERSION" where "BEAS_ITEM_VERSION"."ItemCode"="OITM"."ItemCode")

Integration hub: Importable

Database: "OITM"."U_kalk_pr"

Database: "OITM"."U_losgr_ka"

Database: coalesce("OITM"."U_beas_CalcLotsizeWoUnit","OITM"."U_losgr_ka")

Default Value: 0

Integration hub: Importable

Database: "OITM"."U_losgr"

Database: case when coalesce("OITM"."U_beas_prlotsizeU",0)=0 then "OITM"."InvntryUom" else "OITM"."U_me_verbr" end

Default Value: 0

Integration hub: Importable

Database: "OITM"."MinOrdrQty"

Default Value: 0

Integration hub: Importable

Database: "OITM"."OrdrMulti"

Integration hub: Importable

Database: "OITM"."InvntryUom"

Linked table: BEAS_ME

Linked column: ME_ID

Integration hub: Importable

Database: "OITM"."U_me_verbr"

Integration hub: Importable

Database: "OITM"."BuyUnitMsr"

Entity Relation: UnitGroup -> UnitGroupId

Unit of measure groups (UoM groups) are groups of one or more units of measure that you either

allow as units of measure for a product or exclude from the set of possible UoMs for the product.

You can assign UoM groups for the products of both the deliverying and receiving locations.

Linked BSL objects:

UnitGroup, UnitGroupLines

Linked table: OUGP

Linked column: UgpEntry

Integration hub: Importable

Database: "OITM"."UgpEntry"

Database: "OITM"."OnHand"

Linked table: OWHS

Linked column: WhsCode

Integration hub: Importable

Database: coalesce("OITM"."DfltWH",'')

Integration hub: Importable

Database: "OITM"."U_znr"

Integration hub: Importable

Database: "OITM"."U_match"

Integration hub: Importable

Database: "OITM"."U_din"

Entity Relation: ItemGroup -> ItemGroupCode

Integration hub: Importable

Database: "OITM"."ItmsGrpCod"

Entity Relation: MaterialGroupId ->

Integration hub: Importable

Database: "OITM"."U_gruppe"

Integration hub: Importable

Database: "OITM"."U_haltbark"

Entity Relation: RawMaterial -> RawMaterialId

Linked table: BEAS_WST

Linked column: WST_ID

Integration hub: Importable

Database: "OITM"."U_wst_id"

Related to the settings of "artikel_spezgew":

If "J" (by Item) then OITM.U_BEAS_DICHTE

If "N" then BEAS_WST.DICHTE

If NULL value, then 1

Integration hub: Importable

Database: coalesce("OITM"."U_spezgew",1)

Default Value: 0

Integration hub: Importable

Database: coalesce("OITM"."BHeight1",0)

Database: (select "OLGT"."UnitDisply" from "OLGT" where "UnitCode"="OITM"."BWdth1Unit")

Default Value: 0

Integration hub: Importable

Database: coalesce("OITM"."BWidth1",0)

Database: (select "OLGT"."UnitDisply" from "OLGT" where "UnitCode"="OITM"."BWdth1Unit")

Default Value: 0

Integration hub: Importable

Database: coalesce("OITM"."BLength1",0)

Database: (select "OLGT"."UnitDisply" from "OLGT" where "UnitCode"="OITM"."BLen1Unit")

Integration hub: Importable

Database: "OITM"."PicturName"

Integration hub: Importable

Database: "OITM"."U_picture2"

Integration hub: Importable

Database: "OITM"."U_picture3"

Return Price from current item

if cardcode is defined and valuation is a price list, the system use the DI-API from SAP, otherwise own system

Valuation:

xx (number) = Price List

D Average Price

L Last purchase price

K beas calculation price oitm.u_kalk_price

B last valuation price

W last incoming good price

N with out all for second valuation (24.4.14 M.Heigl)

I Item Price from last Issue document

R Item Price from last Receipt document

// beas Script Example: Return calculation price

instance bsl b
b.get=Item(<itemcode>,<whscode>,<cardcode>,<quantity>,"K")
messagebox=<b.price>

Return all attachment, documents and pictures related to an Item

- Beas Attachments

- SAP Attachments

- Pictures

In JSON format with follow properties

Type:

-- "beas"=Beas Attachments (BEAS_DOKUMENT)

-- "SAP"=SAP Attachments (ATC1)

-- "Picture"=Picture 1-3 from OITM. It return always all 3 pictures. If not define, filename = NULL

Nr:

-- internal reference

Info

-- Only Beas: Additional info / notes

FileName

-- The file name with attachment

Example:

{

"value": [

{

"Type": "beas",

"Nr": 1,

"Info": "Second File",

"FileNAme": "C:\\beas\\beas\\bmp\\classic\\button.png"

},

]

}