SAP Learnings

Greenfield vs. Brownfield vs. Bluefield in SAP Implementation 1. Greenfield 🌱 Fresh start. Clean slate. - Build a completely new SAP system from the ground up. - Ideal for major transformations or companies with outdated processes. - Think of it as constructing a new building—tailored exactly to your needs. 2. Brownfield 🏗️ Renovate what you already have. - Upgrade and modernize your existing SAP system. - Best for companies that want to preserve data and processes while improving performance. - It’s like renovating your current home—same structure, but with modern upgrades. 3. Bluefield 🔵 Blend the best of both worlds. - Selectively migrate key processes and data to a new SAP system. - Ideal for minimizing downtime and ensuring flexibility. - It is like moving your favourite furniture to a new, modern space. Which one is right for businesses? - Greenfield = Transformation. - Brownfield = Optimization. - Bluefield = Hybrid flexibility. The Bottom Line? SAP implementation strategy de...

Integrations are developed to exchange data between sap to sap system (ECC to SAP BI/BW) or sap to non sap system (Example: SAP-MES) as well. Integrations work on either of the below data sharing mechanisms: Push data (event trigger happens in sap ecc or hana) to non sap system [suppose if we are to share material master records to non-sap system, then the message can be triggered upon save event of material code] or  Pull data (request for data is sent by non-SAP system to send data).[Such requests are scheduled in nature and triggered by scheduler].  Types of messages based on direction of data flow: Inbound: Message is called as inbound, if the segment is incoming for SAP, standard SAP tables are updated with the data in the segment. Outbound: Message is called as outbound, if the segment is outgoing for SAP, Standard tables are not updated using this data. Integrations are triggered based on predefined events. Events are finalized by discussing with business.  Ex.: Ev...

How many years of experience do you have & relevant.  Whichever processes you have worked? Previous experiences? Support project which ever process you have worked? can you tell me about SAP PM org structure in hierarchal way? Can you tell me about SAP PM Master Data? What are all the transactional data's you prepared? - Notification/Work order While creating maintenance plan - Scheduling indicators are there what are the types - Fact. Calendar / Time / Key Date in the same page as 8th point there is a tick mark what was that & what it refers to (what was the use of it)??   - Completion requirements In equipment master we mention catalogue profile from where you create?? - SPRO In equipment master we assign the catalogue profile. when we create the Notification, we will select the Code groups /  Codes. is there any specific report (Standard report) there from which we can get the detail whatever notification by codes/code groups. Have you ...

 Steps involved in IDoc set-up  Setting up Inbound/outbound IDocs for system interfaces between systems can reduce the processing time of documents considerably. IDoc interfaces allows to transfer data in faster and safer way. During order to cash cycle we come across multiple IDocs for data transfer. Few logical messages that can be used are mentioned below. #ORDERS: We receive this as inbound IDoc which will have all the header and line item details required for order creation. Processing this IDoc is capable of order creation in SAP system. This way we get the order created without any manual intervention which reduces risk of human error at order creation level. Same Logical message type IDoc when generated for purchase order, it can be used to send the purchase order to vendor. Using EDI IDoc for purchase orders over traditionally used email/ telephone medium can reduce the overall purchasing time for the business and helps to maintain accuracy of data. #ORDRSP: This can ...

 

 Unit Testing  Integration Testing  Regressing Testing  Performance Testing  Functional Testing  User Acceptance Testing Security Testing Test Cycle: Discover Prepare Explore Realize Deploy Run   Discover: Discovery of access Prepare & explore: Fit to Standard analysis Realize:   Scope & Configure ( Implementation Test - Quick check of configuration changes) -  Migrate, Integrate, Extend & test (End user acceptance test - test on customer-owned test cases) Deploy: Onboard & deployed Run: Operate, Test monitor & Support (Regression Test - Test of customer own  & SAP delivered process after Updates/Changes

HCL INTERVIEW We are hiring for the profile of SAP -PM (Pan India) Detail about domain experience 1. Domain experience The person should have maintenance exposure in the manufacturing or Service Industry (Preferably Integrated Steel Plant, Oil refinery, Aerospace, Defense, or Railways) Experience in Enterprise Asset maintenance like Turbine /Complex Utilities Asset repair shop, Locomotive repair shop, Steep Plant, Shipyard Maintenance Shop, Complex Asset Maintenance Exposure, Aircraft Maintenance Process Exposure Maintenance Planning Long term or short term, maintenance execution, Component repair or Complex asset Maintenance process for third party, Document Management. Repair and Overall process, Maintenance repair process, demand, gap, souring of parts 2. SAP Experience a. Good understanding of the following Business processes: i. Plant Maintenance 1. Breakdown Maintenance (Mandatory) 2. Preventive Maintenance (Mandatory) 3. Predictive Maintenance (Preferred) 4. Refurbishment Proces...