Skip to main content

Schedule Line Category

A schedule line consists of confirmed delivery quantities and corresponding confirmed
delivery dates. This provides us info regarding when the delivery can take place.

Delivery Block:

A delivery block can be maintained at Sales Document level and Schedule line Category level.
Delivery block maintained at schedule line category level will be proposed at schedule line level of the sales order.

Movement Type 

Any movement of goods both physical or logical will be captured in the form of movement type in This controls the inventory update and generation of accounting document. The SD module uses goods movement from 601 to 699.

All goods issues to customer from unrestricted stock will be performed through Movement type '601'
All customer returns will be captured through 651

601 GD goods issue:delvy
651 GD ret.del.  returns
653 GD returns unrestr.
655 GD returns QI
657 GD returns blocked
641 TF to stck in trans.
643 TF to cross company
645 TF cross company
647 TF to stck in trans.

Item Relevant For Delivery Indicator 


When selected, the checkbox item, Rel.F.Dlv. allows the items attached to a schedule line to be relevant for delivery and leave this field deselected for those schedule line categories where you do not want the items to be delivered such as inquiry- and quotation-related schedule line
categories.

Movement Type 1-Step 

This field allows you to enter the movement type for one-step movement of goods.

This is Ideally used during Stock Transfer Process.

Order Type/Item Category/Account Assignment Category

During the auto-creation of purchasing document through sales order in the third party or individual PO scenarios system fetches the Purchasing document type, Item category and account assignment category from here.

Purchase Requisition Delivery Schedule

This field indicates whether the sales item is relevant for delivery rescheduling. This is not relevant during third-party orders processing eas vendor delivers goods directly to the customer and rescheduling of delivery schedule is not required in this case.

 This field is ideally used during individual purchase order process where the goods come to
your warehouse first and then issued to the customer location.

Availability check (ATP) & Transfer of Requirements (TOR)

We can control with the schedule line category whether an availability check and transfer of requirements should be carried out in the sales documents. The possible settings for this at schedule line level are dependent on the settings in the requirements class which is determined by the requirements type of the material.

If requirement class is not enabled with availability check functionality and if it's associated schedule line category is enabled with it even then availability check will not be performed So it's imperative that availability check needs to enabled at requirement class level before turning on at schedule line category level.

If a specific schedule line category needs to be skipped from ATP and TOR then this can be done at schedule line category level.





Comments

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...