SCENARIO 1:

Consider that you have got a Business Requirement that says, “It requires a control at the Production Order level”, which implies that when a sales order has been created, the creation of a production order will also take place based on the sales order values. This needs to be stopped for various business reasons. There is no standard functionality available where the functional user will be able to configure this in SAP.

The current open sales order at the production level should not be hot by the process. ABAPer has to MAKE a checkpoint creation for the business where the quantity will be approved by the Manager, which needs to be produced based on the sales order.

You need to code at numerous user exits and a custom table should be created that populates all the details of sales orders and restricts the user authority only for the approval authority like Manager. It has to perform the quality checks multiple TIMES before we finally decide for moving the code into production.

SCENARIO 2:

Generally, when the creation of a sales order takes place, the sales order gets BLOCKED based on the credit check or credit limit(if activation was done by the functional consultants) of the customer. So, you need to ‘unblock’ the sales order even if the customer has been EXCEEDED the credit limit depending on CERTAIN conditions.

For this scenario, you need to write code at numerous places, during the time of the creation of sales orders and also during the delivery time. This process is known as enhancements.

So, for ABAPers the constant evolution of SAP coding standards for core ABAP must be the same, but the methodologies and techniques of implementation or workarounds will be evolving.