For header condition type can we maintain condition records?Ĭan access sequence be assigned to a header condition type? Yes So to populate a condition type automatically we need a condition record. This discount should be applicable for the entire order and it should not be duplicated in every item. The best way i found was to create a condition record for customer master against a discount condition type." This requirement is from Īs in the above requirement, some business scenarios require that a header discount or surcharge populate automatically in the sales order when some criteria are met. A one time $100 bonus to customer irrespective of material or order type. There is some confusion - In a sales order, can header condition type value be entered manually only? Can an access sequence be assigned to a header c ondition type? Can condition record be maintained for a header condition type? īusiness requirement: " requirement of referral bonus. See also the following document for more frequent issues on MD04: If there is no requirements for the sales order on those tables, nothing will be displayed and this is very often related to the sales order requirement class/type settings. Transaction MD04 reads the sales order requirements from tables VBBE or VBBS. ĥ - The sales order is not displayed on MD04. This is usually related to the sales order requirement class/type settings. It happens when “daily requirement” or “weekly requirement” is selected for the availability check in the material master.Ĥ - The sales order is displayed on MD04, but it does not affect the "available quantity". Note 1723507 provides a solution to this issue.ģ - The sales order/delivery number is not displayed.
Usually, this kind of issue happens because there is a quantity of material still linked to the sales order special stock. If the planning file entry is not marked after running this report, not 2144821 should be implemented.Ģ - A MTO sales order is completed/delivered, but the sales order special stock is still displayed on MD04. Notes 20636466 corrects a program error that generates this kind of inconsistency. This is usually an inconsistency and the report SDRQCR21 should be already available on your system to clear inconsistent records. This document provides a brief explanation and the solution for the most commonġ - A sales order/delivery is already completed or deleted but it still appears on MD04. Issues related to sales orders are very frequently observed on transaction MD04.
#CORRECTION PROGRAM FOR MD04 SAP UPDATE#
*** Update from : Note 1992885was created based on the information from this document ***
0 kommentar(er)
