Bapi sales order change schedule lines


  • Change availabilty check / schedule lines in sales orders
  • Sales Order transactions VA01/VA02/VA03
  • Function Module To Change or Cancel Confirmed Quantity
  • No Schedule Lines Due for Delivery upto Selected Date
  • SAP SD Availability Check
  • Change availabilty check / schedule lines in sales orders

    That should not be surprising considering that users will be confronted by no less than 10 date fields during normal order maintenance. That number can rise to more than 15 depending on how you slice the numbers. In this article, I will explore these date fields and how they impact other activities. Read on for more on Sales Document Date Fields. Since sales document date fields appear on all three layers of the Sales Order — Header, Item, and Schedule Line — and since there is a lot of overlap between many of these fields, it makes sense to organize this discussion by function.

    The Created On date is the date that the sales order was saved to the database. Not much else to say on that one. The primary function of this date is to control when a sales document appears in management reports.

    Typically this date is set to the Creation date. PO Date fields exist at both the header and item levels. In most cases, SAP will still expect you to have a PO number and date on the header, but you can change the item-level dates on the Item Overview, Sales, or Procurement tabs. Traditionally, the PO date will correspond to the date that the customer created the PO in their system.

    You input the date and SAP saves it. It may appear on some standard output such as Order Acknowledgements, but I am unaware of any other use for it. In any event, the user can manually overwrite the default pricing date on the order. This, however, should probably be discouraged unless a valid reason exists for making this sort of manual change. The Pricing Date is automatically adopted by the invoice in the billing process. Keep in mind that this could impact pricing; changing the pricing date from the original document will trigger repricing for that billing document.

    One of the more complicated date-related functions on the sales order involves determining when your customer receives their deliveries. In most cases, this should default to the current date, but controls exist to change that proposal. First, you can opt NOT to have a default date at all.

    This is located on the order type configuration screen in the IMG. On the same screen, you can also specify a lead time in days that will act as a buffer. A schedule line is created for each line item with the CRDD maintained.

    As each item is entered, the ATP process will run to see whether or not the date can be met. If so, the single schedule line is confirmed. If not, then secondary schedule lines are created with dates on which the product CAN be confirmed.

    These proposed dates are dependent upon several factors. Material Lead Times — Expected lead times when purchasing or manufacturing a product. Also includes goods receipt lead times and QA lead times. Shipping Lead Times — Time required for picking, packing, loading, etc. SAP considers all of the above and then determines one or more product availability dates.

    It is possible for SAP to determine several additional schedule line dates. In this example, you would see three separate schedule lines with three different dates.

    This value simply corresponds to the first schedule line date for the item. As you may have guessed, changing the First Date value on the main sales screen will just change that schedule line date.

    Nothing too magical. You can double-click a schedule line to pull up the schedule line details. The Shipping tab reveals some additional dates used for logistics planning. These dates and times all deal with lead times for the performing of specific shipping tasks. This date can be based upon a lead time in the route which is useful when, for instance, a carrier requires notification ahead of time.

    A basic example would be a trucking company that requires at least 5 days notice before committing to a pick-up. This is the date on which picking should begin in order to meet the subsequent deadlines. Similar to the Loading Date, the amount of time estimated for picking is controllable through the Shipping Point configuration and can consider several criteria: Shipping Point configuration and Route settings are two examples.

    The amount of loading time can be determined from a combination of the Shipping Point configuration, the Loading Group of the material, and the Route. Since the route is a major input to this date, SAP will assume zero lead time if a route is not specified. The Goods Issue Date is the date on which the goods must physically leave the shipping point. This primarily takes into consideration the customer requested delivery date and the transit time required for the delivery.

    The latter of which is dependent upon the route. If no route is determined on the sales order, SAP assumes zero transit time. Lastly, you arrive at the Delivery Date. This is the date and time that the customer expects the item s to arrive at their desired location. This date, of course, must take into account the transit time between the point of origin and the destination.

    The most common way to take this time into account is by using settings on the Route. This billing date is then copied to the item level where it can be freely maintainable if you wish to maintain the date manually.

    This would make the most sense in an Order-related billing process in which the billing document is generated directly from the Sales Document. If you are billing for a Service without a delivery, there is a separate date field called the Service Rendered Date which is located just below the Billing Date.

    In standard SAP processing, the system will propose the service rendered date instead of the sales order billing date for this scenario. Just to complete the loop, if a service is delivered alongside physical products on a delivery then the PGI date will be proposed for the Services Rendered date. Billing plans are commonly found on certain types of contracts, or sales orders intended to structure larger projects which are invoiced in a particular way. They determine the duration of the billing plan.

    In the case of contracts, this will normally correspond to the validity period on the contract header. The Dates from and Dates Until fields can be used to adjust the billing schedule for a single line item. This would most often be used in conjunction with a Header-level Billing Plan. The Settlement and Settlement To dates represent the billing period for the item. The Billing Date will correspond to one of these dates depending on whether the billing is to be performed In Advance or not.

    Most users just stick to the ones they need for their own purposes. Share this:.

    Sales Order transactions VA01/VA02/VA03

    Reservations, stock blocked or reserved for some special purposes Purchase requirements which are derived from sales orders Deliveries created which are scheduled for delivery and Post Goods Issue PGI Transfer of Requirements Whenever you create a Sales Order, a transfer of requirements is generated.

    Based on the product ordered by the customer, the concerned department identifies whether the ordered goods are produced in-house, whether we have sufficient raw material to convert the required product into the finished goods, whether we need to procure the raw materials from the vendor and inquire about the time required by the vendor to deliver the product in the production facility where the required product will be produced and then finally dispatched to customer.

    If the required product is not produced in-house, then it has to be procured externally from the vendor and then delivered to the customer. First, a Checking Group for Availability needs to be defined in material masters of the materials that will be ordered by a customer. To edit a material master, start MM02 transaction from the command bar. Here you need to enter the material number that you would like to edit.

    Material Master — Initial Screen Once you press Enter button on the keyboard, a dialog box will appear to select views that you wish to maintain.

    Here, we are interested in the field called Availability Check. We will set the availability check 01 which means that the system will generate aggregated requirements for this material after grouping all sales orders with this material placed during a particular day. We can do this check using the stock report transaction MMBE. As you remember, we create new sales orders in the transaction VA Next, select the relevant line item with the unavailable material and press button to view Schedule Lines for this item.

    Otherwise, the system would have created another line with a confirmed quantity and date. We can go to the transaction MMBE to check if the stock is indeed available.

    The system will create a new schedule line with confirmed quantity on the new delivery date. Have any questions or comments? We would love to hear your feedback in the comments section below. Navigation Links.

    Function Module To Change or Cancel Confirmed Quantity

    As far as SAP expects or any date beyond it. In this case change it from You should now be able to create the delivery as usual. Reason 2 : This is a more serious problem and cannot be solved without either config changes or master data changes.

    Let me take this example that one of the students has provided. Everything looks pretty innocent until this point. Now check out the Schedule lines associated with this line item. As you can see, the confirmed qty is Zero. That means, the system is not able to confirm the quantity either via procurement or via production.

    In this case, the availability check will fail and the item will be considered back-ordered. You have 5 EA that will sit on the shelf for two weeks while MRP will direct you to purchase or make 1 EA for the more urgent customer order. Regardless of the customer or the urgency of their need, the pre-existing confirmation will trump the subsequent order.

    No Schedule Lines Due for Delivery upto Selected Date

    Backorder Rescheduling evaluates existing material confirmations and backorders and shifts confirmations based on criteria you specify in the report parameters. In most normal cases, you would probably specify Sales Orders, but requirements can vary.

    The delivery priority is a two-digit numeric field with configurable values that determine the priority of Sales Order items during delivery processing. The Delivery Priority can be set on the customer master as a defaulted value on the Sales Order, but is typically manually adjustable on the Sales Document. Document Number You can use the Sales Order document number to control confirmation allocation — the lower number takes priority.

    You must obviously consider document number ranges if you decide to seriously consider using this criteria. Document Item This goes hand-in-hand with the Document Number.

    SAP SD Availability Check

    You can double-click a schedule line to pull up the schedule line details. The Shipping tab reveals some additional dates used for logistics planning. These dates and times all deal with lead times for the performing of specific shipping tasks.

    This date can be based upon a lead time in the route which is useful when, for instance, a carrier requires notification ahead of time. A basic example would be a trucking company that requires at least 5 days notice before committing to a pick-up.

    This is the date on which picking should begin in order to meet the subsequent deadlines. Similar to the Loading Date, the amount of time estimated for picking is controllable through the Shipping Point configuration and can consider several criteria: Shipping Point configuration and Route settings are two examples. The amount of loading time can be determined from a combination of the Shipping Point configuration, the Loading Group of the material, and the Route.

    Since the route is a major input to this date, SAP will assume zero lead time if a route is not specified. The Goods Issue Date is the date on which the goods must physically leave the shipping point. This primarily takes into consideration the customer requested delivery date and the transit time required for the delivery. The latter of which is dependent upon the route. If no route is determined on the sales order, SAP assumes zero transit time.

    Lastly, you arrive at the Delivery Date. This is the date and time that the customer expects the item s to arrive at their desired location. This date, of course, must take into account the transit time between the point of origin and the destination.

    The most common way to take this time into account is by using settings on the Route. This billing date is then copied to the item level where it can be freely maintainable if you wish to maintain the date manually. This would make the most sense in an Order-related billing process in which the billing document is generated directly from the Sales Document.

    If you are billing for a Service without a delivery, there is a separate date field called the Service Rendered Date which is located just below the Billing Date. In standard SAP processing, the system will propose the service rendered date instead of the sales order billing date for this scenario.

    Just to complete the loop, if a service is delivered alongside physical products on a delivery then the PGI date will be proposed for the Services Rendered date.


    thoughts on “Bapi sales order change schedule lines

    1. I apologise, but, in my opinion, you commit an error. Let's discuss it. Write to me in PM, we will communicate.

    Leave a Reply

    Your email address will not be published. Required fields are marked *