SAP Logistics

  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

Shipping Point 1 As soon as the material availability date or the transportation scheduling date for a schedule line is reached, the schedule line becomes due for shipping. I.e., Order will be displayed in the delivery due list VL04. Point 2 Delivery block can be controlled in Sales document type (Header Level) and Schedule line Category (Schedule line level) Point 3 Delivery status of an order is updated upon creation of the delivery document. Delivery status is updated at header and Item level of sales document Point 4 Shipping Point Determination Shipping point is an independent organisation unit within which processing and Monitoring of the deliveries as well as goods issue is carried out. A delivery is processed by one shipping point only. Shipping point can be determined for each item based on the below criteria. Shipping conditions from customer master data + Loading group from Material master record + Delivering Plant. Delivery can be process

Message type ' CRESTA ' (FM -  IDOC_INPUT_CRESTA )  is used to distribute the credit management information between SAP systems and Non-SAP to SAP systems in case of business uses central finance. Standard SAP has provided transaction Code 'FCV1' is create A/R summary report which will subsequently generate CRESTA IDoc with customer credit information. This program creates A/R summary data within a control area per credit account. This data can then be used either within distributed credit management, or in a non-distributed system. CRESTA IDoc will not update the credit master data (FD32) in the the target system instead it will update  A/R summary data in the credit master data. In technical terms, System will not update table KNKK ( Credit Master data) instead it updates KNKKF* tables (Credit Management: FI Status Data). While creating the sales order, system will perform credit check based on the data from

 At times, You might find it difficult to find the open transport request for a smart form, program, table or any when developer take over the project in between. In this situation, We have taken an example to find transport request for a smart form to shown case the process to be followed. Step 1 : Go to transaction code - SE03 and then select find objects in request/tasks. Step 2 : By default system doesn't provide you object type for smart form. Hence Enter object type as 'SSFO' and then enter form name in the object name field . Step 3 : Select the object and select request status as both' Released' and 'Modifiable' Step 4 : Click on execute button to get the TR details Step 5 : Double click on the TR to get objects included in the transport request. Thank you.

At times, business is raise request to add custom fields in the billing documents report (VF05N). This document will provide you an easy to accomplish this request. In this document, We have considered an example where business requires Customer name to be displayed as standard SAP provides only Customer Code. Below are the process steps to be followed to accomplish this request. Step 1 :  Report layout is displayed with the number of fields containing in the structure -  ERPSLS_BILLDOC . So in this case, We have added Customer name in the mentioned structure. Step 2 : To populate values in the newly added field in the structure, We have used implicit enhancement as per the below. Goto Report of VF05N - ERPSLS_BILLDOC_VIEW and then go to include - ERPSLS_BILLDOC_VIEW_DATA_SEF01 Post processing of call function - ERPSLS_BILLDOC_VIEW   Write the below code which is used to populate customer name IF LRT_DOC[] IS NOT INITIAL. select KUNNR,name1 from kna1 into table @DATA(LRT_DOC_TEMP) FOR

The physical inventory process plays a vital role in the warehouse as it is part of statuary requirements that all materials should be counted at least once a year. Physical inventory process can be carried out at Inventory Management level, Warehouse Management Level and Handling Unit level. This article will talk about the physical inventory process at Handling Unit level . Below are the HU physical inventory process steps : Create Physical inventory document - HUINV01 Change or delete physical inventory - HUINV02 Perform Stock Count - HUINV03 Perform Stock Recount - HUINV04 Post HU stock differences - HUINV05 Inventorize HU - HUINV06 Different status of HU's during Inventory: Before creation of physical inventory document - HU status will be PHEX and WHSE Ideally ( Available to use) Upon creation of physical inventory document - HU status will be INIV,PHEX and WHSE If Physical inventory document is deleted then system will remove INIV status again Perform Stock Cou

 At times, We find difficult to identify exits for a program.  This post will explain you an easy way to find list of  Customer Exits and BADI's available for a program. Below are the process steps to be followed : Step 1 : Goto T.Code : SE16N, Enter transaction code  Step 2 : Fetch program name Step 3 : Collect Program Name and pass it to TADIR table to fetch development class Step 4 : Pass Development class again into TADIR table by passing OBJECT as SMOD to fetch all customer exit's and OBJECT as SXSD to fetch BADI's related to the program. In this case, I have passed SMOD to fetch customer exits. Step 5 : All Customer exits related to the program are displayed Step 6 : Once EXIT is identified. To get description related to it, Pass Exits into table MODSAPT and SXS_ATTRT to get descriptions corresponding to them. Thank you.