IGE1 table in SAP Business One (Goods Issue (rows))
IGE1 is the SAP Business One table that stores the rows of a goods issue: one row per item taken out of stock, with warehouse, quantity, account and the base document. It joins to the header OIGE on DocEntry; rows issued to a production order have BaseType 202.
IGE1 key fields
| Field | What it holds |
|---|---|
DocEntry | Header key. Joins to OIGE.DocEntry. |
LineNum | Row number. |
ItemCode | Item. Joins to OITM.ItemCode. |
Dscription | Item description. |
Quantity | Quantity issued. |
WhsCode | Warehouse. Joins to OWHS.WhsCode. |
Price | Price of the row. |
StockPrice | Stock price of the row. |
AcctCode | Account code of the row. Joins to OACT.AcctCode. |
BaseType | Base document type: 202 = production order. |
BaseEntry / BaseLine | Base document key and row. |
OcrCode / Project | Distribution rule and project code. |
How IGE1 relates to other tables
IGE1 rows belong to one OIGE header (DocEntry). BaseType 202 with BaseEntry points to the production order (OWOR) the components were issued to. TargetType 59 means the row was copied on to a goods receipt.
Common joins
IGE1 T0 INNER JOIN OIGE T1 ON T1.DocEntry = T0.DocEntry (header)IGE1 T0 LEFT JOIN OWOR T2 ON T2.DocEntry = T0.BaseEntry AND T0.BaseType = 202 (production order)IGE1 T0 INNER JOIN OACT T3 ON T3.AcctCode = T0.AcctCode (account name)
When you use the IGE1 table
Use IGE1 to total component consumption per production order, to report issued quantity per account and to compare actual issues with the components planned on the order.
Example query: components issued per production order
SQL Server
SELECT T0.BaseEntry AS ProductionOrderEntry, T0.ItemCode, T0.WhsCode, SUM(T0.Quantity) AS QtyIssued FROM IGE1 T0 INNER JOIN OIGE T1 ON T1.DocEntry = T0.DocEntry WHERE T0.BaseType = 202 AND T1.CANCELED = 'N' GROUP BY T0.BaseEntry, T0.ItemCode, T0.WhsCode ORDER BY T0.BaseEntry, T0.ItemCode
SAP HANA (column names in double quotes)
SELECT T0."BaseEntry" AS "ProductionOrderEntry", T0."ItemCode", T0."WhsCode", SUM(T0."Quantity") AS "QtyIssued" FROM IGE1 T0 INNER JOIN OIGE T1 ON T1."DocEntry" = T0."DocEntry" WHERE T0."BaseType" = 202 AND T1."CANCELED" = 'N' GROUP BY T0."BaseEntry", T0."ItemCode", T0."WhsCode" ORDER BY T0."BaseEntry", T0."ItemCode"
Paste either version in Tools → Queries → Query Generator. Need the other dialect for your own query? Use the SQL to HANA converter.
Common pitfall: BaseEntry is a DocEntry, not the order number
IGE1.BaseEntry holds the production order DocEntry, not its DocNum. Join OWOR on DocEntry (with BaseType = 202) to show the order number users know. See WOR1 table (production order components).
Ready-made queries that use IGE1
- Slow-moving items (no sales in 90 days): Items with stock on hand that have not been invoiced in the last 90 days.
Questions about the IGE1 table
How do I link IGE1 to a production order?
IGE1.BaseType = 202 and IGE1.BaseEntry = OWOR.DocEntry.
Which account does a goods issue row post to?
IGE1.AcctCode, which points to OACT.AcctCode.
What is the difference between IGE1 and WOR1?
WOR1 holds the components planned on a production order; IGE1 holds what was actually issued from stock.
Related tables
OIGE (Goods Issue (header)) · OWOR (Production Order (header)) · WOR1 (Production Order (component rows)) · search all SAP Business One tables
Sources: SAP Business One documentation and SDK (DI API database tables reference), SAP Help Portal.
Ready to get started?
Tell us what you need. You get a clear technical answer, a fixed scope and a price, usually within 24 hours.