IRA Business Process

Order Fulfillment (OF) > Order Fulfillment Reference Information

IRA Business Process

The IRA Business process is a business process object that does the majority of all invoice creation under Stream V. IRA can be invoked using the modes in the following table, which indicates the mode and processing functions.

Ira: Mode	Invoice	Credit	RACredit	Vendors	POS	Pending
Order Types	S,L,Rtv	S	S? Tagged RA Lines	S,L	S,L	S? Tagged Pending lines
Use Pick lines	Yes	No	No	No	No	No
Create Warehouse Records (BIN/WARETRAN update?)	Yes	Yes	Yes	No	No	No
Process Kits	Yes	No – costing	No –costing	No ? Invalid?	No? see note	No – see note – no lines for components
Create Pending Record (OS,DS,SH, and RTV = N)	On “L” If RTV=N	No	No	On “L”	On “L”	Closes existing records
Pending Doc Type Created	R or T (invoice ticket bill)	NA	NA	V – for stk or nonstk	R?	NA – outbound
Pending Cost Source	70 Unit	NA	NA	Transact – from PO less rebate	70 Unit	NA – outbound
Close existing Pending records	No	No	No	No	No	Yes
Close or update RA records	No	(Y or N)	Yes	No	No	No
Create AP Credit Memo	RTV =Y	No	No	No	No	No
Expect Serial Numbers in Array	Yes	No	Yes	Yes	Yes	Yes
Process pre-assigned serial records	No - possibly if pre-assign in soe	Yes – from invoice or RA.	Yes – from RA.	No – or yes if we create order in PO, tie qty to ship to ser#	No	Yes - From original loaner – depends on interface
Create new serial records on-the-fly	Yes – if ser_rec set N	No – update existing	No – update existing	Yes – if not specified in PO or calling	Yes –if ser_rec set N	No – update exist – tied to original loaner.
Update QtyOh in Inventory	Yes (stk)	Yes (stk)	Yes (stk)	No	Yes (stk)	No
Update Allocated in Inventory	Yes	No	No	No	No	No
Update Res Qty in Inventory	Yes	No	No	No	No	No
Update Total RSV in Inventory	Yes	No	No	No	No	No
Cost for Invoice line – Transact	70 Unit - rebate	70 Unit	70 Unit	PO price in local - reb	70 Unit	Pending Cost
Load Transact PO Info	No	No	No	Yes	No	No
INVTRAN Qty Logic - Stocking Items	Transact * -1 To QTY	Transact * -1 To Qty	Transact *-1 To Qty	Transact to Ref_Qty	Transact *-1 to Qty	Transact *-1 To Ref_Qty
INVTRAN Qty Logic – Nonstk	Transact *-1 To Ref_qty	Transact *-1 To Ref_qty	Transact *-1 To Ref_qty	Transact * –1 to Ref_Qty	Transact * –1 to Ref_Qty	Transact *-1 To Ref_Qty (pending qty clrd)
Invtran Types	OI,DI,OS,DS,SH,IN,CM,RV	DI,OI,CM	OI	VS, VP (stk), OI, OS (non stk).	?	PI
Cost in INVTRAN	70 Unit	70 Unit	70 Unit	PO price in local curr.	70 Unit	Pending Cost
Prev Cost in INVTRAN	70 Unit	70 Unit	70 Unit	70 Unit	70 Unit	70 Unit
New Cost in INVTRAN	70 Unit	70 Unit	70 Unit	70 Unit	70 Unit	70 Unit
Company in INVTRAN	Transact Co RTV depends on co name	Transact Co	Transact Co	Vendor from Poline	Transact Co
Load FC PO Price/xrate, curr in Invtran	No	No	No	Yes from PO, date	No	No
Load PO NO in Invtran	No	No	No	Yes - Vendor	No	No
Load Source Line in INVTRAN with	Transact Line	Transact Line	Transact Line	Po Line from transact PO line field	Transact Line	Transact Line
Post Invtran to GL	No	No	No	Yes	No	No
Update Weekly/Monthly Sales History (OI,DI,IN *cm, pos)	Yes	Yes	Yes	Yes	Yes	Yes?
Update Sales History (OI,DI,IN, *cm, pos) MTD, QTD, YTD Accumulators in Inventory	Yes Sls,Qty,Cost	Yes Sls,Qty,Cost	Yes	Yes VS Rev, Qty Cost	Yes Sls,Qty,Cost	Yes?

Argue no to kitting on pos as item does not exist except as components (top item is a placeholder).

If you want to sell kits, they should be prepackaged in the store vs. in separate bins with component ids on them?

If kit is invoiced into pending, the pending record is for the completed kit and it can later be invoiced as single line item from there – no build processing required.

A vendor ship pending nonstock record is included on pending valuation but valued at 0 – to allow later billing without throwing inventory out of balance (no value in 70 so transfer to pending should still be 0 value).

Generic Manifesting