<taSopMultiBin>

  • Article

You use the <taSopMultiBin> XML node to manually add bins, use a bin other than the default, or when you enter non-serial/non-lot items.

Element name

Data type

Length

Required

Default

Description

SOPNUMBE

string

21

Y

Not applicable

SOP document number

SOPTYPE

i4

2

Y

Not applicable

SOP type:

2=Order;

3=Invoice;

4=Return

(5=Back order--not valid);

6=Fulfillment order

ITEMNMBR

string

30

Y

Not applicable

Item number

LNITMSEQ

i4

4

N

0

Line item sequence; must match the sequence number in the SOP line if the item is on more than one line

CMPNTSEQ

i4

4

N

0

Component sequence; must match the sequence number in the SOP line if the item is a kit item

BIN

string

15

N

<blank>

Bin number; the default bin will be used if this element is not passed in

QTYTYPE

i4

2

N

1

Quantity type:

1=On hand;

2=Returned;

3=In use;

4=In service;

5=Damaged

UOFM

string

8

N

<blank>

Unit of measure; the default unit of measure will be used if this element is not passed in

QUANTITY

number

21

Y

Not applicable

Quantity; must be greater than zero

CreateBin

i4

4

N

0

Create bin on the fly:

0=False;

1=True

OverrideBin

i4

1

N

0

Override bin shortage flag:

0=Do not override;

1=Override

RequesterTrx

i4

2

N

0

Requester transaction:

0=False;

1=True (if True, it populates requester shadow table)

USRDEFND1

string

50

N

<blank>

User-defined field; developer use only

USRDEFND2

string

50

N

<blank>

User-defined field; developer use only

USRDEFND3

string

50

N

<blank>

User-defined field; developer use only

USRDEFND4

string

8000

N

<blank>

User-defined field; developer use only

USRDEFND5

string

8000

N

<blank>

User-defined field; developer use only

This node uses document exchange for updates. All existing values are overwritten with the value specified by the update document. If a field in the update is blank, the existing value is changed to be blank.