SAP Logistics

Delivery scheduling calculates date in the delivery header roughly as described below: Delivery date minus Transit time   = Goods issue date Goods issue date - Loading time    = Loading date Loading date - Pick/pack time      = Picking date Loading date - Transportation lead time                                   = Transportation planning date

Product allocation must be switched on in the requirement class (transaction OVZG) and in the schedule line (transaction VOV6). Transfer of requirement must be switched on in the requirement class and in the schedule line. Availability check must be switched on in the requirement class and in the schedule line. Product allocation determination procedure has been maintained in the Basic data 1 tab in Material Master. Check your update settings: Check the update setting of the info structure in transaction MC25. For standard info structure S140, you can use the standard formulas 141 – 144. Formula 140 is the standard formula, independent from the info structure, and must always be entered for characteristic Product allocation object. If you use your self-defined info structure, you can use formulas 141 - 144 as a copy reference and you must adjust them to your info structure. The key figure incoming orders quantity (AEMENGE) must be updated. Update must occu

The aim of the scheduling is to determine the goods issue date, loading date, material availability date, the transportation planning date and when necessary a new delivery date. Customizing:  Sales documents: The delivery and transportation scheduling can be activated in transaction OVLY. Customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation Scheduling -> Define Scheduling By Sales Document Type It is controlled by the document type. Deliveries: For deliveries you have to consider the setting in transaction 0VLK. Field 'Rescheduling' controls whether a new scheduling is carried out. Stock transport documents: In stock transport documents you also have the possibility to use the SD scheduling functionality. If you do not activate it then an MM scheduling is carried out. Customizing path: Materials Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -&g

Is the delivery type marked as relevant for transportation in Customizing? (Customizing: Sales and Distribution -> Transportation -> Specify transportation relevance, here: Maintain transportation relevance for delivery types) Is a route entered in the delivery and is the route characterized as transportation relevant in Customizing? (Customizing: Sales and Distribution -> Transportation -> Specify transportation relevance, here: Maintain transportation relevance for routes) A transportation blocking reason must not be set in Customizing for the delivery type! (Customizing: Sales and Distribution -> Transportation -> Specify transportation relevance, here: Maintain transportation relevance for delivery types) A transportation locking reason must not be set in the delivery itself! (VL01, Change delivery: Header -> Transport.relev.info, where the field 'Transportation blocking reason').

BAPI_INQUIRY_CREATEFROMDATA      Create customer inquiry   BUS2030 BAPI_QUOTATION_CREATEFROMDATA    Create customer quotation BUS2031 BAPI_SALESORDER_CREATEFROMDAT1   Create sales order        BUS2032 You can use BAPI_SALESDOCU_CREATEFROMDATA to create the following sales document categories: BUS2034      Contracts BUS2094      Credit memo request BUS2096      Debit memo request BUS2102      Returns BUS2103      Subsequent delivery free of charge

You can use transaction CMOD with SAP enhancement MM06E001 to find the user exits (you can also find them in the object navigator in the function group XM06), for example, the following exits are relevant: EXIT_SAPLEINM_012 -> Customer enhancement for configuration (table APPL) EXIT_SAPLEINM_013 -> Customer enhancement for changing material configuration data EXIT_SAPLEINM_001 -> Customer enhancements for enhancing the control record EXIT_SAPLEINM_002 -> Customer enhancements for data segments EXIT_SAPLEINM_011 -> Final customer enhancement