SAP Logistics

Business some times requires to populate data like profit center in the accounting document based on certain criteria rather than through the regular way of  fetching from material master. In this situation, we have to leverage the below mentioned customer exit to populate the values in the accounting document. EXIT_SAPLV60B_004 Thank you

Standard SAP provides routine to maintain at output procedure level to trigger output type when post goods issue is completed.  But however, SAP hasn't given any routine to trigger output when packing status is incomplete. To enable this functionality, we have to create a new custom routine in the 9* series with the below logic and assign it to the respective output type in the output determination procedure. IF  KOMKBV2-PKSTK = 'C' AND ( KOMKBV2-KOSTK EQ 'C' ).     SY-SUBRC = 0.   ELSE.     SY-SUBRC = 4.   ENDIF.

Automatic POD Concept For customer proof-of-delivery (POD) confirmations for an outbound delivery, you can define a time window in which the confirmation from the customer must occur. This time window is specified in units of days and stored in the field 'POD timeframe' of the customer master data for the sales area (KNVV-PODTG). If the current date and time in the local time zone (!) of the user running the transaction lies before the end of the time window, the transaction / program does NOT process the delivery, because the confirmation of the customer could still happen.   Logic for POD date calculation The end of the time window in which the POD is expected from the customer is calculated as the delivery date (LIKP-LFDAT) plus the POD timeframe as a net duration. Net duration means that only the working hours according to the factory calendar of the delivery (LIKP-KNFAK) are used for this scheduling. The factory calendar of the delivery is usually determined from the calen

  Proforma invoice Goods issue is not required to create delivery related proforma invoice. Order related billing document If business requires to raise invoice before goods are delivered to customer or Service items then order related billing document is used Delivery related billing document If business requires to deliver goods to customer before raising commercial invoice then delivery related billing document is used

There is a common requirement from functional consultants on how to do debugging. Below is the raw info on the debugging and different ways of doing it. Debugging is a common tool used by the technical team to analyze dumps during transactional processing and program behavior. Through debugging we will come to know the run values of the program as well. Debugging can be performed in two different ways : 1. Debugging by watchpoint 2. Debugging by Breakpoint Debugging based on watchpoint At times, we are unsure about how the value is getting determined for a variable then we can put the watchpoint on the variable deriving the value so that the system will stop at all points where the value is being fetched for the variable. Debugging based on Breakpoint Debugging based on break point will be done only when the consultant is aware of the exact piece of code where a breakpoint can be enabled. The breakpoint can be done in two ways. Internal breakpoint External b

IDocs is an abbreviated form of Intermediate Documents. Data from SAP will send in the form of IDoc between SAP ----> SAP or SAP ----> Non SAP. Type of data exchanged between systems Master Data  Transactional data Master Data Master Data can be manually / Automatically pushed. The manual push of master data can be done by respective transaction codes and we can schedule the batch job for an auto push of master data. Sample T.Codes Send Material Master Data ---> BD10 Send Customers Master Data ---> BD12 Send Vendor Master Data ----> BD14 Send Cost Center Data  ---> BD16 Transactional Data Transaction data such as Sales Order, Delivery, Purchase Orders etc will be sent through Output Setup where IDocs will be triggered based on the Output with Medium '6'. The output type is linked with Message type in the partner profile. To enable an exchange of change data between system then we are required to create a new output ty

Commonly, Business contains conditions which should be applied to entire document i.e., header conditions.In general, maintaining the header condition in the sales or purchasing document leads to duplicating the condition value or amount to all line items instead of splitting the condition value amount the line items. Below is the case without Group Condition Business Process : In order to fix this issue, SAP has provided Group Condition Functionality which splits the header value among the line items instead of duplicating the header condition value. Below screenshots depict the Group Condition Functionality : Process Flow Thank you

Order Required field : The Order Required field is used to specify the document type to be referenced in the creation of this delivery. Default Ord. Type : Specify the default order type here. If a delivery is to be created without reference, you need to specify a “pseudo” order type, which is a reference order type that is required from an internal control point of view. For example, in the case of delivery type LO, the default order type is DL. This order type is configured like any other sales document. Item Requirement: This is a provision to attach a requirement routine for delivery items without reference to a sales document. 201 No ord.w.indep.item Maintaining this routine will restrict user from adding new items at delivery level 202 Order w IndpdntItem Maintaining this routine will allow user to add new items at delivery level independent of sales order or preceding document Delivery Rescheduling You can control whether a redetermination

During sales order processing, the system automatically determines individual purchase order items. However, you can also change standard items to individual purchase order items during sales processing manually. Material exclusive for Individual purchase order, If you procure a material exclusively by individual purchase order, you can define in the material master record that the material is always treated as an individual purchase order item during sales processing. The system will then automatically determine the appropriate item category TAB. To identify a material as an individual purchase order item in the material master record, enter BANC in the field Item category group on the Sales: sales org. 2 screen. Changing Manually in Sales Order If you want to use an individual purchase order to purchase a material that you normally produce yourself, you can overwrite the item category in the sales order, provided that the configuration of yo

Business at times as a part of product sales dumps stock at the customer location and will bill the customer based on the customer sales. The business scenario of employees taking samples to showcase at Expo can be mapped through consignment process as well. In this case, the employee needs to be created as a customer. The consignment process in SAP standard consist of four Steps: 1. Consignment fill up (send materials to customer consignment). 2. Consignment issue (issue materials from customer consignment to the customer) 3. Consignment return (return materials from customer ownership to customer consignment) 4. Consignment pickup (pickup consignment stock and move it to plant stock) Sales Process Sales Document Type Item Category Schedule Line Category Movement Type Relevant for Billing Consignment Fill Up KB or CF KBN E1 631 No Consignment Issue KE or CI KEN C0 or C1

Stock transfer process Inter-Company process If the transaction between two different plants of different company codes then this is considered as an intercompany transaction in SAP.Hence settlement needs to be done for the supplying company code so commercial invoice will be raised for receiving company. Pre-requisites 1.        Supplying plant need to be created for supplying company code 2.        Receiving plant need to be created for receiving company code 3.        Receiving sales line should be extended to supplying and receiving plant 4.        Supplying plant need to be maintained in supplying sales line 5.        Create customer in supplying sales area 6.        Supplying plant need to be created as Vendor in receiving company code 7.        Shipping data need to be maintained for both supplying and receiving plant 8.        During shipping data maintenance customer need to be assigned to receiving sales area 9.        Supplying plant need to

Stock transfer process Stock transfer will be of two kinds: 1. Intra company 2. Inter company  Intra Company process If business requires transaction to be performed between two different plants of same company code. Then this considered as intra company transaction in SAP .Hence no billing document will be generated and if required proforma invoice will be raised. Pre-requisites 1.        Supplying plant and receiving plant need to be created for the same company code 2.        Receiving sales line should be extended to supplying and receiving plant 3.        Supplying plant need to be maintained in supplying sales line 4.        Create customer in supplying sales area 5.        Shipping data need to be maintained for both supplying and receiving plant 6.        During shipping data maintenance customer need to be assigned to receiving sales area 7.        Supplying plant need to be assigned to Delivery type ‘NL’ and purchase document type ‘UB’

A schedule line consists of confirmed delivery quantities and corresponding confirmed delivery dates. This provides us info regarding when the delivery can take place. Delivery Block : A delivery block can be maintained at Sales Document level and Schedule line Category level. Delivery block maintained at schedule line category level will be proposed at schedule line level of the sales order. Movement Type  Any movement of goods both physical or logical will be captured in the form of movement type in This controls the inventory update and generation of accounting document. The SD module uses goods movement from 601 to 699. All goods issues to customer from unrestricted stock will be performed through Movement type '601' All customer returns will be captured through 651 601 GD goods issue:delvy 651 GD ret.del.  returns 653 GD returns unrestr. 655 GD returns QI 657 GD returns blocked 641 TF to stck in trans. 643 TF to cross company 645 TF cross co

Pricing Indicates whether the system automatically carries out pricing at the item level. Blank No pricing This is used for Text items and Items not relevant for pricing scenarios X         Pricing standard The system carries out pricing for standard items in a sales order. A         Pricing for empties B         Pricing for free goods (100% discount) This is used for free Goods Items Schedule Lines Allowed Schedule lines determines the delivery date and quantity. Enabling this check box, Will display schedule lines at sales order item level else schedule lines tab will not be displayed  For standard item, schedules lines exists but where as for text or service items this is not required to be enabled as schedule lines are not required. Item Relevant for Delivery This checkbox is enabled for the items which don't have schedule lines and require delivery processing. Ideally, this is used for text items and Value Items. It serves only fo

An item category controls the behavior of an item and below are the controls which defines the item category. Item Type : A way of classifying items that require different kinds of processing by the system. The system processes items that refer to a specific material differently than items that do not refer to a material. For example, text items do not require processing for pricing, taxes, and weight calculations Below are the common item types used in SAP. Blank Standard Item Business generally uses standard items in SAP. The pricing for a standard item takes into consideration the change in quantity, weight, volume, and time units associated with the material. A         Value Item SAP provides value items for scenarios where you bill your customer for the goods or services rendered. B         Text item Text items are generally used for sending print materials such as flyers, catalogs, and so on, to the customer. These items are generally not billable to th

Reference Mandatory If the business requires to create a sales document only by copying it from an existing document then leverage this field. For instance, if the business requires creating sales order only with reference to a quotation document or Inquiry document then we can select either choose 'B' or 'A'  here for quotation or inquiry restrict sales document from getting created standalone. You can set up the SAP system to create a new sales document with reference to the following: A: inquiry B: quotation C: sales order E:  scheduling agreement G:  contract M:  billing document Remember that a selection in this field will only make it compulsory for the document to refer to an existing document.  Copy Control Settings : This will have a dependency on the copy controls as the actual flow of data between the two documents will happen once it is maintained. Item Division :  When selected, it allows the item division t