SAP Logistics

At times, businesses will come up stating that physical inventory is performed for wrong quantities and require reversal for the difference posting happened. In this situation, the business has to perform physical inventory again, the system will never allow you to reverse the material document posted through physical inventory.

Enterprise Structure Assignment  Relationship between individual org. elements are maintained here ********************************************************** Plant to company code assignment : Can we assign one plant to multiple company codes? One plant can be assigned only to one company code one company code can have multiple plants  ************************************************************ one plant can have 'N' number of storage locations ************************************************************ Purchase organization to company code assignment Can we assign one purchase org. to multiple company codes? One Purchase org. Cross company code purchases if I assign company code to purchase org. then I am restricting purchase org. to specific company code If I do not maintain any company code in the assignment then the purchase org. can be used for purchase goods for multiple company codes ************************************************************* Purchase organization to

 At times, business users do purchase orders for the purchase requisitions created through sales orders. Again, after few days business users will try to use the same purchase requisitions to create new purchase orders.  In this situation, SAP throws the error message Error '06249' even though it is maintained as a warning message in system messages. This is standard SAP functionality and below is the workaround need be implemented as proposed by SAP in the note mentioned in the subject line.   The following workarounds are possible - from both MM and SD perspectives: Solution for MM side: Use the already existing PO + item. In this existing PO item, please create a new delivery schedule (tab "delivery schedule") for the new delivery date and the open units, then the system will allow you to continue. - or - Solution for SD side: Create a new schedule line in the old sales order item, or create a new item in the sales order for the remainin

Characteristics values for an object cannot be extracted from the database table directly. Hence we are required to follow the below steps to fetch the data : First, pass the material into table KSSK and fetch object number Pass the object number into the KLAH table to fetch the class Pass the class into a functional module: 'CLAF_CLASSIFICATION_OF_OBJECTS' to fetch the characteristics and characteristics values.

 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.  

Core component of SAP Retail is Retailing functionality which mainly covers SD,MM & WM. When Log on to SAP Retail, system will in general display SAP Easy Access menu meant for generic to Manufacturing domain but however if we require default screen to be displayed as Retail Easy Access  Goto User Own data ----> Goto Defaults  and enter W10T in Start Menu. Below are the Retail Terminologies commonly seen :    SAP Retail                                                                        R/3                                                                        Article                                                                                 Material Site                                                                                         Plant Logistics Calendar                                                Factory Calendar Merchandise Category                                         Material Group Requirements Planning                                    Materials

MM Configuration for the plant : Creation of the plant - V_T001W Assignment of storage location to the plant - V_T001L Assignment of the valuation area to Company code - V_T001K Assignment of the purchase organisation to the plant - V_T024W Maintain stock and value update for the respective material types linked to the plant - T134M Maintain Plant parameters - V_159L Maintain negative stocks to the storage location ( if required ) - MM ---> IM ---> Goods issues SD Configuration for the plant : Shipping point determination - TVSTZ Assign sales organization - distribution channel - plant - V_TVKWZ_ASSIGN Assign shipping point to plant - V_OVXC Define, copy, delete, check shipping point - V_TVST Storage location determination - V_TVKOL PS configuration for the plant : Specify Parameters for Network Type - V_T399X_NN Specify Parameters for Network Scheduling -  V_TCX00_FAUF Define Checking Control -  V_TCO11 Define Confirmation Parameters - V_TCORU_P In case

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th

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

Logic to display final approver name  Fetch FRGGR FRGSX FRGKE by passing EBELN and FRGRL Eq ‘X’ Into table EKKO Pass FRGGR FRGSX into table T16FS and Fetch FRGC1 , FRGC2 , FRGC3 , FRGC4 , FRGC5 , FRGC6 , FRGC7 , FRGC8. If NOT FGRC1 IS INTIAL AND FRGC2 IS INITIAL PASS FGRC1 INTO TABLE T16FW  AND FETCH OBJID PASS  OBJID INTO TABLE USR21 AND FETCH PERSNUMBER PASS PERSUMBER INTO TABLE ADRP AND FETCH NAME_TEXT Display NAME_TEXT in the report output to display processor name ELSEIf NOT FGRC2 IS INTIAL AND FRGC3 IS INITIAL PASS FGRC2  INTO TABLE T16FW  AND FETCH OBJID PASS  OBJID INTO TABLE USR21 AND FETCH PERSNUMBER PASS PERSUMBER INTO TABLE ADRP AND FETCH NAME_TEXT Display NAME_TEXT in the report output to display processor name ELSEIf NOT FGRC3 IS INTIAL AND FRGC4 IS INITIAL PASS FGRC3 INTO TABLE T16FW  AND FETCH OBJID PASS  OBJID INTO TABLE USR21 AND FETCH PERSNUMBER PASS PERSUMBER INTO TABLE ADRP AND FETCH NAME_TEXT Display NAME_TEXT in the repor

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

At times, business requires to mass block PO's and release whenever required. For this to accomplish, We cannnot be done through Mass Transaction as system will consider as 'L' even though we pass Value 'S' in LOEKZ field. For this to accomplish we are required to perform LSMW - Batch input method where recording need to be performed to ME22. Below is the sample LSMW export file for reference. [Recording        ] : ME22 [Recording Text   ] : po change /SAPDMC/LSGBDC                ZTEST_IMP      ME22           0001                                        0000TME22