Search This Blog...

Loading...

Monday, September 8, 2014

Background Job setup in SAP

It’s often required to run certain programs in background to avoid performance issues in SAP or to automate routine tasks. Most of the time we schedule customer invoice creation, delivery creation are background jobs in SAP. Sometimes if you have to do large number of data uploads to SAP, it’s advisable to run those programs in background as well. There are various methods to run / schedule programs in background. The advantage of background processing is that you can schedule the job to be run any time you want.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!



Sunday, August 31, 2014

How to determine different number ranges for delivery documents based on the shipping point

Sometime back we discussed about having different number range for sales documents based on the sales organization. Click here to view that.
Today we will discuss how we can have different number range for delivery documents based on the shipping point. Document numbers for delivery documents in SAP are triggered via the number range assigned to delivery document type in the IMG path: SPRO -> Logistic Execution / Shipping / Deliveries / Define Delivery Types
This number range is defined under the IMG path: SPRO -> Logistic Execution / Shipping / Deliveries / Define Number Ranges for Deliveries
As the number range is assigned to the delivery document type, you cannot determine different number ranges for the same delivery document type in different shipping points. For example, if you have two shipping points in the system and you want to have two different number ranges for delivery document type "LF" for those two shipping points, then SAP standard number range setting cannot be used directly.
But this is possible via use exits in the delivery creation.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Thursday, August 21, 2014

Using events in the delivery document

Let's say you have configured credit management functionality in SAP to block all delivery notes where customer is exceeding the credit limit. In such a case; business request customer to pay the full amount or lesser amount in advance! Here business normally informs the customer, the date that he/she should make the payment. As soon as the payment is made, the goods have to be shipped from the warehouse to the customer.
In such a scenario, business should not hold the delivery note in the SAP system, until customer pays the required amount. If delivery information can be sent down to warehouse system with the date that customer is suppose to made the payment, then warehouse can pick / pack and keep it ready in the warehouse. As soon as the payment is received in SAP and the information is passed to warehouse, the goods can be issued to the customer. This will avoid the delay of warehouse processing after customer places his payment.
Such a business requirement can be handled via events in the delivery note header.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Friday, July 25, 2014

Customer Classification


SAP has provided standard set of fields in the customer master to be used for various purposes. Some fields are per-defined for certain purposes with an attached functionality behind. In order to provide maximum flexibility for SAP users, there are some fields which are not pre-defined, but can be used for custom purposes such as; Customer Group 1 to 5. But those fields are depending on the sales area of the customer. If you want to define a value which is independent of the sales area, you can define your own classification for customers. This classification can be attached to customer master with different characteristic values. Since this is not sales area depended, you can define it as a global value for the customer master.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!


Tuesday, July 15, 2014

How to determine different number ranges for sales orders based on the sales organizaton

The sales document number that you see in SAP is created out of the number range attached to the sales document type in configuration. 
As the number range is assigned to the sales document type, you cannot determine different number ranges for the same sales document type in different sales organization. For example, if you have two sales organizations in the system and you want to have two different number ranges for sales document type "OR" for those two sales organizations, then SAP standard number range setting cannot be used directly. But this is a very common business requirement when you have multiple company code or sales organization using same sales document type. Therefore SAP has give the provision via user exits in the sales order creation.
Please click here to view how you can determine different number range for delivery documents based on the shipping point.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!



   How to Determine Different Number Ranges for Sales Orders Based on the Sales Organizaton

Thursday, June 26, 2014

Invoice Split Logic in SAP

 For certain business requirements, you need to define customer specific invoice split criteria. This can be achieved using below method.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Monday, May 5, 2014

How to disable Delete option for Sales Documents

Sometimes certain businesses request to disable the delete functionality in the sales order. This is to prevent users deleting sales documents after they were created in SAP. It can be the complete sales document, a single line item or a single schedule line in the sales order. Instead of deleting the sales order/ line item / schedule line, business wants users to set an appropriate "Rejection reason" in the sales order. By doing so the planning figures for sales orders and actual system data will be always in sync. It also impacts on reporting.
You cannot achieve this using standard SAP customizing. But SAP has provided a user exit to achieve the same. Let's see how you can do it using these user exists.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!


Sunday, January 5, 2014

Delivery Split Logic in SAP

For certain business requirements it is required to define customer specific delivery split criteria's. This can be achieved using below method. 


Happy Reading!!

Please feel free to post your suggestions, feedback and comments!


Wednesday, November 27, 2013

How to block materials for sales order creation

Due to various reasons it is often requested by business to discontinue certain materials for sales order creation. In such a scenario, we need to block those materials to prevent sales order creation.
This can be achieved using below fields in the material master under "Sales: Sales org 1" tab.

  • "X-distr.chain status" (Cross-distribution-chain material status) field together with the "Valid from" field -
  • "DChain-spec. status" (Distribution-chain-specific material status) field together with the "Valid from" field -

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!





Wednesday, September 18, 2013

One time customer master in SAP

A customer who only comes into a business transaction with you once is called one-time customers in SAP terminology.
Since they come only once, it is not necessary to create a master record (Customer Master) in SAP for such a customer. To reduce the database space, you can create a customer master record within the business transaction to store that data.
In order to create such a customer, you can have a template customer in SAP to determine all default values required in the customer master. This will ensure less data entry and accuracy at the real customer creation.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!