This action might not be possible to undo. Are you sure you want to continue?
0 It is used for data conversion from legacy system to SAP, Master data creation and for simple transaction. LSMW is developed by functional consultant using below 4 object type and input methods: > Standard Batch / Direct input (For Material creation / extension - Program name - RMDATIND, BOM creation Program name - RCSBI010, etc..) > Batch input recording (Work center creation, production version creation, Routing header data change, Serial number creation, MIC creation, QM info record creation, Material master data change etc..) > Business object method - BAPI (Inspection plan, etc...) > Idoc (Intermideate document) It contains generally 26 steps, in which 20 steps are under main steps. Important design steps are: > Maintain Object Attributes > Maintain Source Structures (Incase of multiple source structure, logical path needs to be created using transaction code - FILE) > Maintain Source Fields > Maintain Structure Relations > Maintain Field Mapping and Conversion Rules (Auto field mapping functionality is available) Important Transaction steps are: > Specify Files > Assign Files > Read Data > Display Read Data BDC (Batch Data Conversion) It is used for data conversion from legacy system to SAP, Master data creation and for simple transaction. Transaction record is done by functional consultant (T-code SHDB) and development is done by ABAPer using this transaction record and FS logic. It is generally used for huge data conversion, using some validation logic, which is difficult to be done through BAPI (Business Application Programming Interface ) BAPI (Business Application Programming Interface) is a set of interfaces to object-oriented programming methods that enable a programmer to integrate third-party software into the proprietary R/3 product from SAP. For specific business tasks such as uploading transactional data, BAPIs are implemented and stored in the R/3 system as remote function call (RFC) modules. Each BAPI is processed with a function module. BAdi (Business add ins) BAdis (Business Add-Ins) are the new way in which SAP allows you to enter additional logic for validation and updation into an application. BADIs are avialble in standard SAP with multiple method. One BADI can be implmented for multiple times using transaction code SE18 / SE19. BAdi can be used for Validation for BOM components ( like storage location, usage probability for alternate component (BOM_UPDATE)), Mail communication to concern person at the time of BOM change User Exit / Customer Exit User exit are the way in which SAP allows you to enter additional logic for validation and updation into an application. User exits are avialble in standard SAP with includes within a function module exit. One user exit can be implemented only once using t-code SMOD and same needs to be assigned to a single project using t-code CMOD. User exits can be used for Usage probability validation in production order (PPCO0001), MRP with MRP key (M61X0001), Usage dicission validation (like all stock should be posted before UD), result recording should be Customized Process:
Screen varaients / Transaction varaients are required to activated in respective clients. This Screen Varient / Transaction Varaient (T-Code is SHD0) Through screen varaient. Function modules also play an important role during updating and in interaction between Reports: BOM matrix report development using function module "CS_BOM_EXPL_MAT_V2" Plan Vs. This is done by functional consultant. populated with difult value & fields can be made mandatory for particular transaction code. There is no standard process available in sap to capture and analysis the productivity. productivity analysis is one of the important factors for manpower planning execution in production line.Recording production loss reason for information purpose: There is no standard process to capture. Function Module: Function modules allow you to encapsulate and reuse global functions in the SAP System. Single screen varaient or multiple screen varaient can be clubed to create transaction varaient and separate t-code can be assigned to that transaction varaient to perform the standard transaction with screen validation as mentioned in screen varaients. Vendor wise LAR & LRN in PPM: Vendor LAR & LRN report is required for MIS and vendor rating purpose. production activity is continued in several shifts. They are managed in a central function library. Z-reports need to be developed as per business requirement with desired format. we can analysis the MRP results and stock requirement status in standard layout. production and the achievement MIS report. User specific transaction varaients can be created (Transaction Varaient = Group name + Transaction code). Through screen varaient / transaction varaient . MRP Analysis: Through t-code MD04/MD05. But for effective analysis of MRP. why there is a difference between target production quantity and actual production quantity. Production report as required by managment in desire format. Screen varaient can be created for: Quick Viewer (SQVI) Quick viewer is a easy tool. Same can be made availble for all user id by assigning transaction code to the program of quick viewer. through which simple report can be created by using single table and table joining. Shift wise production confirmation recording and reporting through user exist: In manufacturing industries. business can analysis the root cause and eliminate the same to improve productivity as well as timely achievement of customer requirements. Quick viewers are user id specific. functionalities of menu bar can be diactivated. Capturing these reasons. Quick viewer can be created for: > Material master data details > List of production order with reference to plan order . It is required to analysis the production performance in shift wise also. Productivity calculation: In manufacturing industries. The SAP System contains several predefined functions modules that can be called from any ABAP program. screen fileds can be made hidden.