►
Description
Agenda:
1. Features proposal for Milestone 2 https://github.com/magento-engcom/msi/wiki/MSI-Roadmap
2. Source level Reservations support by Paul Hachmang (https://tinyurl.com/MSI-23m44s)
3. Add support for Negative Min Qty Threshold when Backorder is enabled by Paul Hachmang
(https://tinyurl.com/MSI-1h4m53s)
A
I'd
propose
to
start
the
first
grooming
meeting
devoted
for
the
half
as
a
milestone
to
homicide
project.
I
know
that
there
are
some
issues
with
internet
connection
in
Austin
offices.
Probably
why
our
product
owner
mark
Renton
can't
manage
to
join
I'll
already
pink
him,
but
I
suppose
that
he
can
jump
in
in
the
middle
of
the
medium
and
I
prepared
the
the
list
of
stories.
The
list
of
possible
features
which
we
can
discuss
today
and
I'm
pretty
interesting
to
hear
your
opinion
regarding
what
this
story's
and
would
watch
it
features
you
that
you
consider.
A
A
A
Following
the
link
on
the
side
road
map,
we
see
that
mark
mark
is
going
to
join
us
pretty
soon.
As
soon
as
his
laptop
gonna
be
reloaded
and,
as
you
know,
we
implemented
the
basic
functionality
of
multi-source
inventory,
which
is
which
are
applicable
for
simple
configurable,
virtual
and
downloadable
product
types.
And
now
we
have
a
reservation
stock
reservation
mechanism
which
can
be
used
for
preventing
over
selling
and.
A
A
A
We're
gonna
release
the
next
better
version
of
homicide
and
that's
why
we
need
to
take
into
a
call.
So
we
need
to
take
into
account
that,
probably
during
the
summer
months,
we
will
we'll
get
some
drop
of
productivity,
because
many
many
guests
from
from
community,
we
will
go
on
vacation
this
five,
probably
our
our
velocity,
not
gonna,
be
so
big
as
it
was
as
it
was
during
the
spring
and.
A
A
A
Implementation
of
this
interface
proxies
all
the
code
to
legacy
Cadillac
Cadillac
inventory
stock
item
and
our
Desirables
vision
is
to
our
desirable
vision,
is
to
provide
own
persistent
mechanism
and
to
provide
own
own
database
tables
to
store
the
data
for
both
stock
item
configuration
in
the
source
item
configuration
also.
We
need
to
differentiate.
A
Configuration
for
source
item
out
of
configuration
for
stock
item.
Currently,
all
the
configuration
which
we
have
now
is
applicable
just
for
stock
and
zone.
The
exception
from
this
rule
is
the
lows:
low
stock
configuration
which
is
actually
which
is
actually
in
a
notification
based
on
warehouse
level
so
based
on
the
source
level,
and
we
don't
have
some
generic
source
item
configuration
now.
A
But
these
items
eventually
will
will
give
us
an
ability
to
totally
separate
existing
catholic'
inventory
mechanism
out
of
newly
created
inventory
provided
by
MSI,
because
currently
we
are
still
coupled
to
the
legacy
system.
Another
another
point
of
copying
to
the
legacy
systems
that
we
don't
support,
bundle
and
group
products.
A
This
next
two
items
you
know
in
our
product
backlog,
because
currently
we
don't
provide
support
of
multi-sourcing
for
both
bundle
and
group
products,
and
the
bundle
and
group
products
are
supported
just
on
default
default
stock
and
default
source,
and
actually
that's
why
we
have
this
special
cases
for
the
food
source
in
default
stock.
And
this
is
actually
the
reason
why
we
we
are
not
allowed,
for
example,
to
disable
default
force
and
why
we
are
not
allowed
to
add
more
sources
to
the
fold
stock.
A
We
actually
preserve
the
ability
of
indexation
of
bundle
and
group
products,
so
these
are
two
items,
the
main
goal
of
which
is
to
provide
the
ability
to
first
of
all,
to
make
an
indication
of
bundle
and
group
products
for
multi
sourcing
and
support
the
bundle
and
group
products
at
the
time
of
the
source.
Selection
algorithm
in
other
items
in
our
in
our
backlog
is.
A
Also,
we
have
a.
We
have
an
epic
devoted
for
the
mass
inventory
action,
especially
reassignment
of
source
items
from
and
to
different
sources,
and
we
are
going
to
support
this
functionality
as
an
easy
onboarding
process.
When
single
stock
merchant,
he
is
going
to
to
become
a
multi
stock
and
he
is
reassigning
source
item
from
the
full
source
to
other
already
pre-created
sources.
Currently
we
already
have
an
epoch
which
describes
is
discover,
and
now
we
already
have
Ricardo,
who
is
currently
working
on
this
epic
functionality.
A
A
A
The
list
of
sources
which
sub,
which
support
the
solar
store,
pickup
and
the
customer
will
choose
manually
what
sources
would
sources
or
source
should
fulfill
his
order
and
also
at
least
at
least
we
had
an
intention
to
improve
our
our
source
selection,
algorithm
and,
along
with
priority
based
algorithm,
which
we
currently
have
implemented
in
MSI.
We
wanted
to
introduce
the
minimum
delivery
cost
and
the
you
know
a
case.
A
So
that's
why
we
wanted
to
introduce
the
garrisoning
based
on
the
source
based
on
the
source
address
and
the
shipping
address
another
stuff,
which
is
also
pretty
important,
and
this
one
is
supposed
to
be
mandatory
for
us
that
we
need
to
provide
that
performance
comparison
for
for
magenta
to
the
three
without
a
Massiah
magenta
to
the
three
with
MSI
and
we
need
to
provide.
We
already
have
pot
scenarios
in
our
p80
scenarios.
A
A
So
these
are
the
main,
the
main
stories
which
we
already
have
an
our
product
backlog
and,
let's,
let's
discuss-
and
maybe
you
have
some
other
proposal
regarding
the
story
which
we
need
to
include
a
milestone.
I
just
want
to
say
that
this
is
not
the
full
list
of
stories
and
we
are
not,
and
we
don't
give
a
guarantee
that
all
of
these
stories
would
be
implemented
at
the
end
of
milestone.
Do
so
now
we
are
trying
to
to
compose
the
backlog
and
after
that,
we'll
prioritize
it.
A
B
A
C
Was
just
listening
see
now
to
see
how
this
all
goes?
So
it's
pretty
new
for
me
to
do
a
conversation
like
this
hope.
You
could
hear
me
I
had
the
idea
to
to
give
some
gifts
on
give
short
backstory
and
why
I
would
like
to
have
the
source
reservations
is
because
we
have
a
requirement
from
a
customer
to
implement
the
to
implement,
transfer,
orders
or
or
purchase
orders
in
Magento.
They
have
a
product
that
is
sold
one
month
before
it's
shipped.
C
C
Then
we
can
just
figure
out
the
the
saleable
quantity
of
the
product
and
and
then
we
can
just
figure
out
where
it's
coming
from,
but
then
a
customer
mentioned
that
they
also
are
required
to
have
an
Evan
as
a
single
purchase
order
for
all
the
items
that
that
need
to
be
order
and
and
combining
those
two
requirements.
Let
me
do
the
source
reservations
and
by
creating
the
source
reservation
we
we
can
actually
solve
that
issue,
and
we
can.
C
C
C
The
the
two
parts
I
wanted
to
use
the
the
reservations
for
is
to
actually
ever
have
the
ability
between
the
source,
selection,
algorithm
and
the
actual
physical
shipment
of
the
product.
Currently
in
the
current
MSI
implementation,
the
actual
physical
shipment,
the
Magento
shipment,
is
used
as
a
fiscal
ship
is,
but
in
our
system
we
first
need
to
select
a
source
and
then
do
this,
make
the
I
communication
with
where
else
and
then
actual
market
shipments
a
shipped,
and
my
idea
was
to
actually
implement
that
with
a
with
a
temporary
shipment.
C
A
shipment
document
and
the
way
it
works
is
in
order
process
it.
It
currently
does
a
stock
selection
when
the
water
is
placed,
of
course,
and
then
we
need
to
create
some
cron
job
to
actually
automatically
create
the
shipment
documents
and
I'm,
not
sure
about
that.
I
haven't
worked
that
out
yet
how
to
actually
do
it,
but
when
a
shipment
is
made,
the
order
stock
is
now.
His
reservation
is
nullified
and
a
source
reservation
is
made
by
the
shipment.
C
C
After
that,
where
else
does
some
stuff
and
it
communicates
back
to
D
to
the
to
Magento,
and
we
invert
then
mark
the
source,
reservationist
nanofied
an
actual
deduct,
the
the
actual
source
that
way
the
the
quantity
that
is
available
in
where
else
will
actually
be,
which
the
quantity
that
is
actually
that's
actually
set
on
a
product
in
Magento
I
believe
that
that
was
the
case
with
the
earlier
situations.
Well,
but
but
now
we
have
to
depart
in
between
I
am
I
thought
about.
It
cancel
step,
I'm,
not
sure
what
to
do
about
that.
C
But
I'm
can
imagine
that
it
would
be
interesting
to
have
a
cancel
State
on
shipment,
that
you
can
bring
ship
and
that
you
can
recreate
a
shipment
when
the
warehouse
doesn't
actually
happen
in
stock,
which
happens
sometimes
because
I
do
not
always
track
there
one
of
these
properly,
and
so
there
was
one
part.
The
other
part
is
what
I
wanted
to
work.
What
I
wanted
to
create,
or
what
I'm
required
to
create
for
the
customer
are
transfer
orders.
C
Transfer
orders
are
actually
like
shipments
from
from
a
source
and
to
would
do
a
different
source,
so
you
have,
we
have
two
types
will
be
care
about
stock
of
the
source
or
we
do
not
care
about
stock
the
source.
When
you
have
the
when
you
care
about
stock,
the
stores
its
of
the
source
is
probably
your
own
warehouse
or
something
that
you
manage
and
start
for,
or
it's
an
external
supplier
that
you
do
not
manage
a
stock
for.
C
So
when
we
created
a
transfer
order,
there
will
be
the
interface
in
the
backend
of
of
Magento,
that
you
can
create
a
transfer
order
and
the
seller
or
the
merchant
can
add
products,
define
its
quantities
and
then,
when
the
transfer
order
is
confirmed,
the
the
quantities
are
handled
in
the
end
in
the
system.
When
you
have
a
from
source,
the
quantities
are
deducted
from
the
source
reservation
table
so
from
the
warehouse.
Where
is
shipping
from
its
it's
read?
The
quantities
are
reserved,
so
it
so
it
can
be
sold
on
webshop
and
on
the
two
source.
C
C
But
I
wasn't
he
had
some
other
interfaces
that
that
implemented
the
same
functionality
in
there.
They
had
the
extra
fields
like
received,
rejected
thinking,
so
not
sure
what
to
do
about
that
yet,
but
they
have
to
safely
transfer
those.
The
two
source
items
are
also
attitude,
actual
quantities
on
on
the
products,
and
that
allows
us
to
create
the
flow
and.
C
So
so
that
that's
that
the
target
we
are
working
towards,
we
have
a
release
of
this
November.
So
we
expect
to
have
everything
built
for
them
and
with
their
there
are
some
discussion.
What
oh
yeah
I
had
some
discussion
with
one
of
you
guys
for
to
actually
do
with
all
the
other
code
you've
written,
because
there
we
sell,
have
some
discussion,
what
we
should
actually
publish
out
the
source,
and
but
one
of
the
most
basic
parts
is
the
source
for
socialization
API.
C
It's
currently
implemented,
and
it
currently-
and
it
currently
is
in
almost
an
exact
exact
copy
of
the
of
the
inventory
reservation
API,
because
it's
it
follows
a
lot
of
the
same
patterns
and
I
do
have
some
questions.
How
I
should
implement
some
stuff
because
I
have
to
have
to
plug
in
that
it
actually
made
me
ta
upend,
the
indexer,
with
some
additional
information,
but
I've
got
I,
have
to
figure
some
query
stuff
out
how
to
actually
solve
it,
and
so
that's
what
it?
What
I?
What
I
had
so
far.
B
A
Maybe
like
because,
for
example,
the
main
intention
could
be
just
introduced
kind
of
cash
level
or
selection
algorithm
and
that
save
it
introducing
kind
of
reservation
for
sources
when
and
which
will
provide
you
an
ability,
for
example,
to
print
the
shipment
documents
and
make,
and
when
you
make
the
real
deduction
you
can
apply
this
a
try,
this
algorithm
and
the
ete
to
results
to
deduct
to
do
that.
The
particular
amounts
from
from
sources.
So
actually
this
is
equation.
So,
whether
you
need
some
cash
layer
or
you
really
need
to
use
this
source
and.
C
Did
the
the
ideas
that
new,
so
the
question
is
like
there
should
recreate
the
new
shipment
state
or
should
we
just
create
a
new
entity?
That's
request,
or
should
we
just
have
the
result
of
a
source
selection
algorithm?
Should
we
have
F
that
there
were
there?
Was
we
had
an
earlier
discussion
and
the
point
is
the
source
selection
result
of
one
water
can
influence
the
source
selection
result
of
the
of
another
order,
so
we
actually
need
to
only
actually
need
to
know
for
sure
that
that
I'm
able
to
fulfill
both
orders
correctly?
C
If
you
know
what
I
mean
so
he
did
the
dependency
between
the
orders
actually
important
as
well.
So
therefore,
I
need
to
actually
have
commitment
from
the
warehouse
I'm,
not
sure
about
what
the
word
commitment
mean
so
for
problems
from
the
warehouse
that
they
could
say.
Okay,
I'll
probably
be
able
to
handle
this,
and
so
it
so
it's
not
something
that
actually
can
be
properly
once
it's
created.
It
should
be
able
to
be
changed
without
an
official
flow.
C
It
is
it's
more
than
cashing
mm-hmm
I'm,
not
sure
what
it
means
sub,
because
III
to
write
down
the
two
advantages:
the
advantages
of
the
performance
shipment
or
the
dependent
shipment
or
shipment
states,
so
that
we
only
need
to
introduce
a
state
for
shipment
in
the
system
and
else
or
the
UI's,
and
almost
everything
stays
the
same.
So
it
from
my
perspective.
It's
a
relatively
minimal
effort
to
do,
and
then
we
we
already
have
it
every
different
system
that
actually
creates
the
shipment
request
and
it's
something
like
a
new
API.
C
A
C
If
I
actually
implemented
the
state
before
the
before
the
current
shipment,
if
we
do
not
have
two
reservations,
I
will
now
have
to
actually
deduct
the
source
and
I
will
actually
break
things
more
than
they
currently
are.
I
think
it
currently
works
fine,
because
you
actually
create
a
shipment
when
the
actual
inventory
is
deducted
in
the
warehouse
itself,
but
whatever.
If
I
use
the
shipment
request
functionality,
then
I'm
I,
think
I
I
I
I
deduct
the
inventory
too
early
so.
A
C
I
think
the
when
the
when
the
shipment
request
is
made,
but
when
the
when
the
first
date
of
a
shipment
is
made
I
think
that's
a
trigger
to
actually
push
all
the
the
the
shipment
request
to
be
a
warehouse
to
and
they
they
will
confirm
it
and
I.
Think
that
will
happen
in
one
go
and
if
that
makes
sense,
yep.
C
A
A
Source
reservation,
yeah,
I,
think
so,
and
actually
we
can
even
rename
it
to
source
reservation,
mm-hmm
and
and
I
believe
we
can.
We
can
put
it
into
into
dedicated
module
because
currently
it's
the
part
of
the
inventory's
chicken
yeah,
taking
into
account
that
this
service
could
be
called
as
a
part
of
the
RMA
process
or
create
memo
or
it
turns
it
or
so
forth.
Mm-Hmm.
D
A
B
C
A
C
C
So
so
what
is
happening
is
it's
currently
I'm
appending,
so
I
have
two
fixtures.
It
actually
creates
all
the
inventory
and
then
I
have
the
yeah
I.
Think
I've
made
a
single
mark
well,
but
most
of
them
are
succeeding
right
now
and
the
thing
that's
happening
so
it's
great.
It
creates
all
the
defaults
for
kite
source
items
and
then
it
then
binds
them
to
do
a
single
stock
and
now
I
can
append
the
reservation.
C
I'll
show
you
method
the
reservation
builder.
It
works
the
same
way
as
a
reservation
already
does
for
the
stocks,
and
it
just
in
a
lot
of
the
code
is
almost
an
exact
replica
of
that.
So
this
part
is
working
and
an
algae,
append,
reservations,
class
that
actually
happens
to
the
reservations.
I
do
have
some
to
do's
here
and
there
to
actually
solve
some
issues.
What
currently
does
this
item
did
this
q1
on
stock
item
10
I
append
five
items.
It
should
have
eight
point
five
and
but
I
append
five.
So
there's
thirteen
point,
five.
C
What
it
actually
should
have
and
then
then
I
do
actually
comparison
and
I
do
don't
I
do
not
do
to
some
I,
also
reset
it
in
the
test,
but
it's
like
it's
more
like
a
cleanup,
so
this
part
works.
I.
Think
that
that's
good
I
do
have
some
other
to
do.
Sigh
I
still
need
me
to
do
actually
I've
been
fully
working
because
we
have
the
index
report.
I
think
that
I
have
to
get
working
and
I
had
the.
C
C
You
have
for
payments
if
it's
online
and
offline
a
payment
determines
if,
if
the
invoice
has
different
statuses
and
something
like
that
should
also
be
implemented
for
the
shipments
but
I'm
not
sure
how
to
actually
do
that
yet
and
then
for
the
free
interface
itself.
I
think
it's
just
a
create
shipment
and
then
confirm
shipment
for
market
shipped
button
in
yet
my
panel,
and
that
maybe
allows
you
to
actually
like
the
way
it
I
do
not
have
a
very
advanced
UI
plane
right
now.
Mm-Hmm
I
thought
brought
the
API
first
and
then
do
the
UI.
E
C
It's
a
little
bit
fresh
I
haven't
actually
published
anything
yet.
Okay
I
had
some
discussion
with
one
of
the
other
guys
about
about
how
we
should
contribute
ever
everything
and
anything,
five.
What
if
I-
and
we
had
some
discussion
with
our
internal
marketing,
what
what
he,
how
we
should
handle
this?
How
we
should
actually
handle
this
because
it's
work,
it's
a
lot
of
work,
we're
we're
doing
for
for
all
the
for,
for
the
complete
functionality
and
I
should
be
actually
yeah
well,
yeah.
C
E
C
D
D
With
using
source
related
reservation,
we
could
decouple
the
application
of
source
selection
algorithm
at
shipment
time
I
mean,
in
the
end,
the
source
selection
algorithm
as
the
task
of
splitting
stock
related
reservations
into
one
or
more
source
related
reservations
without
affecting
the
stock,
and
it's
only
when
we
concretely
ship
for
source
that
we
can
have
stock
deduction.
So
it's
it's
another
way
of
deferring
this
stock
deduction
and
in
some
way,
saving
the
result
of
the
source
selection
algorithm
by
splitting
these
stock
reservations
into
multiple
sources
evasions.
D
These
probably
we
should
consider
this
change
as
useful,
regardless
of
a
specific
needs
that
pull
as
now.
This
can
be
useful
too.
Yes
to
not
be
bounded
to
the
shipment.
We
already
seen
that,
for
example,
for
some
products
we
don't
have
shipment
for
mere
tools
or
downloadable
products.
We
don't
have
shipment,
so
the
idea
that
we
deduct
stock
at
shipment
time
has
been
proving
not
being
correct,
so
maybe
we
can.
We
can
discuss
about
Emmaus.
This
change.
C
Think
it's
a
favorite,
it's
my
turn
to
speak
and
I.
Think
that's
exactly
the
exactly
the
point.
I
am
what
I
think
I
am
I'm,
not
sure.
I'm
now
I
think
you
you
described
exactly
the
the
issues
I
run
into
that
the
shipment
isn't
exactly
the
moment.
You
actually
need
to
deduct
something
always
and
I
need
to
have
yeah
all
right,
I'm,
not
sure
how
to
further
respond
onto
that.
B
D
That
causes
the
stock
reservations
to
be
placed,
and
we
don't
have
these
these
two
blocks
and
when
we
have
the
shipment
we
apply
the
selection
algorithm.
Let's
create
compensation
on
reservations
with
the
idea
described
by
by
Paul.
We
can
have
the
order
that
places
reservations,
the
selection
algorithm,
which
converts
source
reservations
into
stock
reservations,
and
only
when
we
have
stock
deductions.
D
D
Decoupling,
the
the
stock
deduction
from
the
shipment,
but
taking
notes
of
splitting
that
the
stock,
the
stock
reservations
in
two
source
reservations.
We
can
apply
the
source
selection,
sorry
and
what
I'm
proposing
is
decoupling.
The
search
selection
algorithm
from
the
shipment
yeah.
We
can
apply
this
or
selection
algorithm,
and
this
sort
of
selection
algorithm
transforms
the
stock
reservations
in
two
source
reservations.
So
so
we
have
the
information
of
which
source
must
be
addressed
by.
A
Want
to
say
that,
currently,
our
source
selection
algorithm
is
not
really
coupled
to
shipment,
because
if
it
would
be
probably
it
would
with
order
object.
But
currently,
our
selection
of
there
is
manipulated
with
abstraction
layer
and
that's
why
this
is
potentially
possible
to
use
the
source
selection
algorithm
at
the
time
of
the
order
placement
working
with.
So
currently,
we
have
kind
of
factory
and
factory
with
the
name,
something
like
build.
The
source
version
request
based
on
water,
so,
for
example,
interview
injecting
selection
algorithm
at
the
time
of
the
order,
placement.
A
A
But
what
I
think
about
the
whole
proposal
that
you
know
that
in
MSI
we
have
potential
synchronization,
I'll,
usually,
and
this
issue's
supposed
to
be
supposed
to
be
handled
by
system
integrator,
because
sometimes
we
as
a
framework,
don't
know
the
correct
behavior,
for
example.
What
to
do?
If
we
have
the
reservation
for
I,
don't
know
100
items
and
I
was
talk
of
a
lability
is
200,
but
after
after
the
reservation
is
placed,
we
have
that
synchronization.
A
A
A
So
here
for
us,
probably
it
would
be
even
more
even
more
different
situation
when
the
data,
when
we
have
the
reservation
so
ever
was
a
source
item,
but
somewhere
in
somewhere
in
the
middle,
we
get
synchronization
with
external
system
and
we
will
get
an
update
of
our
source
item
quantity
and
after
we
get
the
update
for
the
source
item
on
this,
is
we
can
realize
that
we
are
not
able
to
fulfill
there?
We
get
some
inconsistency,
yeah.
C
C
A
A
So
that
how
to
how
to
like,
if
you
get
getting
started
in
in
this
problem,
let's
just
definitely
data
inconsistency,
but
what
system
should
be
debugged
in
any
way
to
find
an
issue,
whether
it's
going
to
be
Magento,
whether
it's
not
clear,
because
some
of
the
request
which
comes
by
which
come
from
magenta
could
not
be
delivered
to
your
B
or
maybe
your
P
get
an
update
from
another
system.
If
it's
omni-channel
environment.
B
C
B
C
And
I
think
in
a
way
your
your
the
the
problem.
You're
describing
is
a
is
a
problem
but
I
think
it's
an
extension
of
the
bigger
problem
that
actually
was
there.
The
big
problem
that
actually
is
there
without
the
source
reservation,
because
right
now,
I
can
I
can't
do
anything.
I
need
to
store
the
source
reservation
some
way
in,
because
I
can't
just
run
the
reservation,
the
the
algorithm
and
then
just
to
the
API
calls
and
then
hope
for
the
best
that
everything
pans
out
in
the
end,
of
course,
so
ok.
A
E
C
All
right,
I
I
can
I
can
only
describe
the
issue
if
you'd
like
yeah
all
right.
So
sorry,
the
whole
point
we
were
just
talking
about
the
body
transfer
order,
stuff
transporters
are
like
pre-orders
so
that
our
orders
that
are
already
placed
that
will
be
eventual
stock
on
a
source
and
back
orders
are
like
yeah,
just
place.
C
Your
design,
we'll
figure
out
where
the
icons
will
come
from
when
they
are
actually
placed,
and
so
that's
like
the
back
on
the
function
of
the
instance
yeah
and
I
thought
the
the
feature
came
from
a
miscommunication
because
we
implemented
the
negative
means
sale.
Quantity
image
enter
one
for
one
of
her
customers
there,
which
would
ask
the
much
warehouse
thing
and
as
the
transfer
orders,
Lia
and
etc,
and
that
so
we
implement
there
so
I
had
was
more
fresh
air.
Why
doesn't
this
functionality
work?
Because
that
would
solve
the
back
water
issue?
C
D
A
Really
the
main
maze,
the
main
question,
probably
I,
have
from
the
Luton
food
perspective.
So
currently
we
decided
that
we
will
allow
to
specify
the
negative
stress
hold
so
negative
means
means,
sell
quantity,
stress,
hold
and
I'm
not
wrong
about
the
correct
name.
Analysis
parameter
just
in
case
when
JEB,
but
order
is
enable
for
particular
product,
but
what
to
do
if
we,
if
we
switch
on
the
border
and
apply
the
negative
quantity
for
this
result?
And
after
that,
we
which
is
able
but
Porter.
A
D
A
D
D
B
D
A
A
C
Do
have
a
question
yeah,
yeah
yeah,
of
course,
one
kind
of
thing
they
did
the
potential
pitfall
of
using
the
when
you.
Let
me
share
my
screen
yep
second,
so
when
you,
when
you
fill
in
a
negative
quantity
like
this
yep
now
I,
don't
understand
what
it
should
do,
it
should
chill
out.
It
should
allow
backwards,
yellow
zero,
and
but
when
you
do
this,
what
what?
C
What
should
he
do
because
it's
it
becomes
when
I
entered
minus
85,
it
becomes
clear
that
I
should
only
allow
85,
but
if,
when
I
enter
zero,
what
should
he
do?
Do
I
actually
do
not
allow
back
orders
or
should
I
allow
back
orders
what's
happening
and
when
you
allow
back
orders
when
you
enter
a
positive
number,
what
what
do
you
actually?
C
C
Million
dollar
question
and
then,
when
you
use
count
fake,
it
still
has
the
value
it
still
reports
of
value.
And
it's
like
it's
like
the
the
feature
I
wanted,
and
it's
not
this
field,
because
the
thing
I'm
one
of
this
a
lot
of
quantity
below
zero
and
then
a
field
like
here
yeah,
but
only
until
my
80-85
or
something
yeah
I
already
did
a.
D
Change
in
the
code
base
that,
if
the
coders
are
allowed,
this
threshold
at
the
moment
is
meaningless.
If
you
allow
back
orders,
destruction
is
ignored,
yeah.
So
it's
the
opposite
of
the
of
the
discussion
we
had
before
in
else,
but
orders
are
allowed
any
any
value
that
which
is
positive
is
is
not,
is
not
meaningful.
Yeah
all.
D
A
C
C
C
So
turdy
the
infinite
thing
came
and
it's
a
second
time
it
popped
up
for
me,
because
it
was
also
for
a
saleable
quantity.
If
you
allow
back
orders
the
saleable
quantity,
saleable
quantity
becomes
infinite
at
some
points.
If
you
do
not
limit
the
back
orders,
its
infinite
by
by
definition
so
I
think
that
that
was
confusing.
We
also
add
about
that,
and
things
I'm
not
sure
how
to
proceed.
A
A
Definitely
makes
sense,
it's
a
little
bit
pity
that
mark
already
disconnected
because
it
sounds
like
a
good
question
to
him.
So
I
will,
after
the
end
of
this
meeting,
I,
will
share
the
recording
and
pink
mark
to
provide
the
answer
and
I
asked
provides
his
aunt
Arina
in
a
massage
section,
also
I
expected
to
kill
described
from
the
user
perspective,
how
to
how
to
better
analysis,
yeah.