Availability+check28

Embed Size (px)

Citation preview

  • 8/12/2019 Availability+check28

    1/9

    CONCEPT OF AVAILABILITY CHECK

    As soon as you enter the button to save the sales order, the lne te!s n the sales order "oes nt#o dre$tons% one s &or the 'r$n" and one s &or the s$heduln"% be$ause s$hedule lne sde$ded de'ends u'on the $usto!er re(uested delvery date, and (uantty%

    No# besdes sales order also sear$hes &or the !ateral n the 'lant, #arehouse or stora"elo$atons, to deter!ne #hether the as)ed (uantty $an be a''roved or not% and Ths s #hat #e$all here *+P *ateral re(ure!ent 'lannn"-*+P .#heather ths orders lne te!s are avalable or not /

    s$hedule lne s deter!ned by Ite! $ate"ory 0*+P ty'e% No# &or your n&o, avalablty $he$)you also $an do by Co12, or *314%-

    No# lets understand #hat s ATP

    ATP5 Avalablty To Pro!se, !eans the or"an6aton $an 'ro!se the $usto!er, by #hen the"oods $an be delvered to there door ste' de'endn" on $ertan $ondtons% On$e *+P $he$)edenou"h (uantty s there, and Trans&er o& re(ure!ents assured that the sto$) $an be !adeavalable by date as)ed by the $usto!er #th &or#ard and ba$)#ard s$heduln", ATP $an be

    !ade%

    Avalablty $he$)s 5 $an be !ade at Plant level, and to !a)e sure #hen the !ateral #ll beavalable, not only ths but Avalablty $he$)s also ta)es nto $onsderaton the '$) 'a$) t!e,loadn" t!e, trans'ortaton s$hedule t!e, and all these t!n"s 'ut to"ether "ves rse to

    Planned "oods ssue date 7 ths s the date #hen the "oods are trans&erred &ro! the o#nersh'o& busness to the o#nersh' o& sh''n" a"ent%

    8h''n" dates are then added to the 9oods ssue date and results .3elvery dateand all ths 'ro$ess #h$h s done auto!at$ally n a s'lt o& se$ond, $o!!un$ated to theordern" 'arty%

    The &ollo#n" 'la$es de$des & Avalablty should be !ade5

    :% 8$hedule lne $ate"ory o& the te! te! $ate"ory0*+P ty'e-;% te! $ate"ory o& sh''n" do$% Lne te!s-

  • 8/12/2019 Availability+check28

    2/9

    Configuration Steps

    Availability Check and Transfer of Requirements

    ID

    Title 3eter!naton O& +e(ure!ent Ty'es =sn" Transa$ton

    Release Id Enterprise Version ECC 6.0

    Menu path IMG.>>sales & Distb>>Basic functions>>Availability Cec! an" #ransfer of$e%uireents>>#ransfer of re%uireents>>Deterination 'f $e%uireent #ypes (sin)#ransaction

    Transaction Code *+$'

    The folloing Requirement types ere assigned to item category and MR! Type "#

    Requirement Types Description

    0,, Delivery re%uireent

    0-, 'r"erDelivery $e%uireent

    ConfigurationDescription

    ,. $e%uireent types /ere assi)ne" to ite cate)ory an" M$+ #ype. *ave te "ocuent.

    Required $ields Ite cate)ory1 M$+ #ype & $e%uireent Class

    Configuration

    !rerequisites

    2 Ite cate)ories to be create"

  • 8/12/2019 Availability+check28

    3/9

    Configuration Rationale #e syste cec!s te availability of te )oo"s base" on te re%ueste" "elivery

    "ate of te custoer an" creates M$+ recor"s /ic contain all necessary

    inforation for passin) on to aterial plannin). #e transfer of re%uireents

    ensures tat te )oo"s are available in tie for te "elivery.

    Configuration Steps

    Availability Check and Transfer of Requirements

    Title Carry 'ut Control 3or Availability Cec!

    Release Id Enterprise Version ECC 6.0

    Menu path IMG.>>*ales & Distribution>>Basic functions>>Availability Cec! an" #ransfer of$e%uireents>>Availability cec!>>Availability cec! /it A#+ 4o)ic or a)ainst

    plannin)>>carry out control for availability cec!

    Transaction Code *+$'

    Checking Rules for Availability Check"

    Checking Rules Description

    A *D 'r"er

  • 8/12/2019 Availability+check28

    4/9

  • 8/12/2019 Availability+check28

    5/9

    Configuration

    Description

    5. Go to 0 In"ivi"ual $e%uireents an" cec!in) rule A *D 'r"er7 an"

    confi)ure te "etails. In In'ut/ar" fiel" purcase or"ers1 reservations1

    sales re%uireents an" "eliveries are cec!e".

    -. *ave te "ocuent.

    Required $ields Cec!in) Groups & Cec!in) $ule

    Configuration

    !rerequisites

    Cec!in) )roups & Cec!in) $ule

    Configuration Rationale In tis IMG step1 you "efine cec!in) rules for te availability cec! an" allocate te to acec!in) )roup. #e cec!in) rule specifies te scope of te availability cec! for terespective transactions in sales an" "istribution by specifyin) precisely /ic stoc!s1 receipt

    an" issue eleents soul" be ta!en into account "urin) te availability cec!.

  • 8/12/2019 Availability+check28

    6/9

    Configuration Steps

    Availability Check and Transfer of Requirements

    Title Define proce"ure for eac "elivery ite cate)ory

    Release Id Enterprise Version ECC 6.0

    Menu path IMG.>>sales & Distribution>>Basic functions>>Availability Cec! an" #ransfer of$e%uireents>>Availability cec!>>Availability cec! /it A#+ 4o)ic or a)ainst

    plannin)>>Define proce"ure for eac "elivery ite cate)ory

    Transaction Code *+$'

    Item Categories Description

    284C Interco *toc! #r. Ite

    2848 *tan" *toc! #rans Ite

    2$E8 $E#

    2#A8 *tan"ar" Ite

    Configuration

    Description

    9. Availability cec! soul" be active for "elivery ite cate)ory 28481

    284C1 2#A8.6. *ave te "ocuent.

    Required $ields Ite Cate)ory

    Configuration

    !rerequisites

    2 Ite Cate)ories to be create"

    Configuration Rationale Confi)ure te availability cec! for or"er"eliveries.

  • 8/12/2019 Availability+check28

    7/9

    Configuration Steps

    Availability Cec! an" #ransfer of $e%uireents

    ID

    Title Define proce"ure by re%uireent class

    Release Id Enterprise Version ECC 6.0

    Menu path IMG.>>sales & Distribution>>Basic functions>>Availability Cec! an" #ransfer of$e%uireents>>Availability cec!>>Availability cec! /it A#+ 4o)ic or a)ainst

    plannin)>>Define proce"ure by re%uireent class

    Transaction Code *+$'

    Requirement Class Description

    0,, Delivery re%uireent

    0-, 'r"er"elivery re%uireent

    ConfigurationDescription

    :. Availability cec! an" #'$ bot cec! bo; soul" be active.

  • 8/12/2019 Availability+check28

    8/9

    Configuration Rationale In ths I*9 a$tvty you de&ne &or ea$h re(ure!ents $lass #hether anavalablty $he$) and>or trans&er or re(ure!ents should be $arred out%

    Configuration Steps

    Availability Cec! an" #ransfer of $e%uireents

    Title Define +roce"ure 3or Eac *ce"ule 4ine Cate)ory

    Release Id Enterprise Version ECC 6.0

    Menu path IMG.>>sales & Distribution>>Basic functions>>Availability Cec! an" #ransfer of$e%uireents>>#ransfer of re%uireents>>Define +roce"ure 3or Eac *ce"ule 4ineCate)ory

    Transaction Code *+$'

    Availability check % Transfer &f Requirements !rocedure ere defined for Schedule line category"#

    Schedule line Categories Description

    2C Intercopany $eplen

    2M 8o Mat. +lannin)

    28 $eturns

    2+ M$+

    2$ $eplenisent /o M$+

    2* 4e)

    2V Consuption M$+

  • 8/12/2019 Availability+check28

    9/9

    Configuration

    Description

    =. Avb cec! bo; to be active for availability /ereas $e%uireents soul"

    not be active.

    ,0. *ave te "ocuent.

    Required $ields *ce"ule line cate)ory

    Configuration

    !rerequisites

    2 *ce"ule line cate)ories to be create"

    Configuration Rationale In tis IMG step1 you specify for te respective *ce"ule line cate)oriesof te sales"ocuent /eter an" availability cec! an"or transfer of re%uireents soul" be carrie"

    out. #ese confi)urations are only relevant for te sales "ocuents.