SAP MDG: TAX classification based on country and tax type
Process: Method – DERIVE_DATA Code: Thank You 🙂
SAP MDG: TAX classification based on country and tax type Read More »
SAP Process Explorer
SAP MDG: How to make Roles default for Customer & Supplier Change Request Type
Scenario: Process: Create a Class Method – DERIVE_DATA Code:
SAP MDG: How to make Roles default for Customer & Supplier Change Request Type Read More »
SAP MDG: Problem in Toolbar Following Code Addition for New Button
Note: Please check previous blogs, to understand this blog Requirement Sometimes after addition of code, toolbar will be filled with new buttons that can be done to hide Go to Component Configuration – BS_CU_OVP, main page – Customizing Choose the component configuration – Custom UIBB which created As Per above some button will be visible, in previous screen (As which Highlighted with the Name – Here), Just Select that toolbar & check in right & choose Option NONE after that screen look like this, without any button Then need to get configure customizing entity & new button in tool bar, it automatically starts works in UI If above process not working out, follow another process which defined below Done, Custom LIST UIBB got set & It will start working creating Rows
SAP MDG: Problem in Toolbar Following Code Addition for New Button Read More »
SAP MDG: How to get the Custom List UIBB NEW button to work
Note: This blog continuation after previous blog Requirement Process Create a class in SE24 & Assign Super Class Redefine The Method & Choose Filter Option IF_FPM_GUIBB_LIST~GET_DATA Add the code for following method IF_FPM_GUIBB_LIST~GET_DATA Remove entire code & paste below code
SAP MDG: How to get the Custom List UIBB NEW button to work Read More »
SAP MDG: How to Remove Toolbar for Custom Entity (LIST UIBB)
Requirement As Per My Creation of Custom Entity LIST UIBB faced this Issue. The highlighted things need to be removed, by leaving first new button. Process to perform for above operation Once done with above process After done with process new button will not work, to click & rows to get created will cover this in upcoming blog Stay Tuned 🙂
SAP MDG: How to Remove Toolbar for Custom Entity (LIST UIBB) Read More »
Order-to-Cash (OTC) Cycle (End User)
The Order-to-Cash (OTC) process in SAP is a critical business process that encompasses the entire lifecycle of a customer order, from order creation to cash receipt. It integrates various SAP modules, primarily SAP Sales and Distribution (SD), with some touchpoints in SAP Financial Accounting (FI) and SAP Materials Management (MM). Below, I’ll elaborate on the OTC process in SAP with detailed steps, covering the end-to-end flow. Overview of the OTC Process The OTC process typically includes the following key stages: Let’s break it down step-by-step with detailed explanations for each phase. Step 1: Pre-Sales Activities Pre-sales activities lay the foundation for the OTC process. These are optional steps but are commonly used to manage customer interactions before an order is placed. Step 2: Sales Order Creation The sales order is the formal commitment from the customer to purchase goods or services. It’s the starting point of the core OTC process. Step 3: Availability Check and Delivery Scheduling SAP checks whether the requested materials are available and schedules delivery. Step 4: Outbound Delivery Once the order is confirmed, the next step is to create a delivery document to initiate the physical movement of goods. Step 5: Picking and Packing This step involves physically preparing the goods for shipment. Step 6: Goods Issue Goods issue (GI) records the movement of goods from the warehouse to the customer, updating inventory and financial records. Step 7: Billing Billing generates an invoice for the customer based on the delivered goods. Step 8: Payment Receipt The final step is recording the customer’s payment to close the OTC cycle. Additional Notes End-to-End Example
Order-to-Cash (OTC) Cycle (End User) Read More »
SAP MDG: How to Make UI Fields – Checked Default in CR
Requirement: Once choosing of PO The Following below fields has to be automatically checked Implementation: The BADI has to be used Create Implementation: Once Created Implementation Class: Filter Values Implementing Class Code:
SAP MDG: How to Make UI Fields – Checked Default in CR Read More »
SAP Master Data Governance (Introduction)
Contents SAP Master Data Governance Capabilities: Establish best quality master data to optimize business solutions Deliver Out-of-the box Full Integration to SAP systems as a client Offer integration services for non-SAP client systems. Workflow flexibility closely integrated to a framework for defining business rules. Deliver a data model proven by several applications & industries. Reuse of existing processing logic. Out-of-the-box data replication mechanisms, using stable mechanisms. Provide a directory of Business Partners (organizations, persons, groups of persons). This directory contains data primarily used for identification (e.g. name, address, ID numbers, etc.). The MDG objects like Customer and Supplier will be based on this directory and offer seamless integration with customer-specific data and supplier- specific data). Possibility to extend the process by adding business logic and thereby bringing in data quality. Has roles and responsibilities and also task authority (e.g. create, change, approve). Data in process stored in a separate repository, will be transferred to operational database after final approval. Flexible enough to respect the distributed responsibilities existing in a company across various business units. Can be adapted and tailored based on customer needs. Linear or distributed and workflow based. Prevent creation of duplicates for increased effectiveness and efficiency. Custom validations can be modelled and programmed (For example, code lists, simple checks, or rules using BRFplus). Integration of rules from MDG, Data Quality Management. Address Enrichment: Automatically adding Tax Jurisdiction Code reusing interfaces/providers Direct, pooled or manual replication to SAP and non-SAP systems. Flexibility to replicate selected data only to a specific client system by defining filters (controlled by DRF) Support of different object IDs or customizing keys between hub and client systems (via. mapping in MDG or PI). Monitoring and error handling DRF controlling replication mechanisms like: – > ALE for SAP S/HANA OP, SAP ERP 6.0, R/3 and non-SAP systems. – > SOA service for SAP and non-SAP systems. – > RFC and File for SAP and non-SAP systems. Reuse existing data structures and functionality of SAP S/4HANA. Be able to enhance MDG functionality based on predefined content or customer-specific extensions. Provide easy-to-use extensibility capabilities for enhancing nodes and fields. Data models.User interfaces.Processes. Data replication. Governing the master data of various legacy system centrally in MDG and replicating back to the respective legacy systems. The consolidation functionalities of merging and best record creation can be used for existing data preparation activities for the central governance scenario. This is one time activity where an enterprise decides to govern the master data centrally & then replicate the data to multiple systems. As part of initial load, data is extracted, profiled/cleansed, and then consolidated through the consolidation process. When new system are introduced into the landscape, consolidation can used to harmonize and deduplicate the new master data with existing data. Master data is created in separate systems/operational systems, as needed. The data is then consolidated into a central system by merging and mapping the data to a common data standard, so it can be used for analytical purpose. SAP Master Data Governance is fully integrated with SAP S/4HANA (SAP Master Data Governance on SAP S/4HANA). It can also be installed as an add-on component to SAP ERP 6.0. There are two versions: It leverages the inherent functionalities of the SAP ERP/ABAP application layer, including workflows, Business Rules Framework plus (BRFplus), replication, value mapping, key mapping, UI frameworks such as Floorplan Manager. SAP HANA capabilities such as SAP HANA smart data quality. Some of the functionalities of SAP MDG are exist only as part of SAP MDG on S4 HANA: Product master data quality control and remediation. Consolidation functionality involving multiple customer and vendor assignments of business partners. Central governance functionality to use newly added customers and vendors as references for partner functions within the same change request. Service-oriented architecture (SOA) replication (inbound and outbound) of FI-CA data. UI enhancements for material search Thank You, sapsolutionlab Team. ________________ Comment Your Opinions & Feedback. Looking for SAP MDG Training, please drop (Training) in comment Section, Team will reach you.
SAP Master Data Governance (Introduction) Read More »
P2P cycle in SAP (End user)
The Procure-to-Pay (P2P) cycle in SAP is a comprehensive process that integrates procurement and accounting functions. Below is a detailed explanation of each step in the P2P cycle, including the accounting entries at each stage. 1. Identify Requirement Process: A department identifies the need for goods or services. SAP Transaction: Create a Purchase Requisition (PR). Manual creation: ME51N Automatic creation: Through MRP (Material Requirements Planning). Key Document: Purchase Requisition (PR). Details: The PR specifies the material/service, quantity, and delivery date. Accounting Entry: No accounting entry is posted at this stage. 2. Create Purchase Order (PO) Process: The procurement team converts the PR into a Purchase Order (PO). SAP Transaction: ME21N (Create Purchase Order). Key Document: Purchase Order (PO). Details: The PO includes vendor details, material/service, quantity, price, delivery date, and payment terms. Accounting Entry: No accounting entry is posted at this stage. 3. Goods Receipt (GR) Process: When the goods or services are delivered, the receiving department confirms the receipt. SAP Transaction: MIGO (Goods Receipt). Key Document: Goods Receipt Document. Details: The system updates the inventory stock. A Material Document and an Accounting Document are created. Accounting Entry: Debit: Inventory Account (if goods are received) or Expense Account (if services are received). Credit: Goods Receipt/Invoice Receipt (GR/IR) Clearing Account. Example: Debit: Inventory Account (Material Stock) $1,000 Credit: GR/IR Clearing Account $1,000 4. Invoice Verification Process: The vendor sends an invoice, which is matched with the PO and Goods Receipt. SAP Transaction: MIRO (Enter Invoice). Key Document: Invoice Document. Details: The system performs a 3-way match (PO, Goods Receipt, and Invoice). If the match is successful, the invoice is posted. Accounting Entry: Debit: GR/IR Clearing Account. Credit: Vendor Account. Example: Debit: GR/IR Clearing Account $1,000 Credit: Vendor Account $1,000 5. Payment Processing Process: The payment is processed based on the payment terms specified in the PO. SAP Transaction: Automatic Payment: F110 (Automatic Payment Program). Manual Payment: F-53 (Post Outgoing Payment). Key Document: Payment Document. Details: The system generates payment proposals, which are approved and executed. Payments can be made via checks, wire transfers, or other methods. Accounting Entry: Debit: Vendor Account. Credit: Bank Account. Example: Debit: Vendor Account $1,000 Credit: Bank Account $1,000 6. Vendor Reconciliation Process: The vendor account is reconciled to ensure all transactions are accurately recorded. SAP Transaction: FBL1N (Vendor Line Item Display). Details: The accounts payable team reviews vendor statements and resolves any discrepancies. Accounting Entry: No new accounting entry is posted at this stage. 7. Reporting and Analysis Process: Reports are generated to analyze procurement performance, vendor performance, and spending. SAP Transactions: ME2N (Purchase Orders by PO Number). ME23N (Display Purchase Order). Other reporting tools. Details: Key metrics include lead time, vendor performance, and cost savings. Accounting Entry: No accounting entry is posted at this stage. Summary of Accounting Entries in P2P Cycle Goods Receipt (GR): Debit: Inventory Account (or Expense Account) $1,000 Credit: GR/IR Clearing Account $1,000 Invoice Verification: Debit: GR/IR Clearing Account $1,000 Credit: Vendor Account $1,000 Payment Processing: Debit: Vendor Account $1,000 Credit: Bank Account $1,000 Key Integration Points in SAP Material Management (MM): Handles procurement, inventory management, and goods receipt. Financial Accounting (FI): Manages invoice posting and payment processing. Controlling (CO): Tracks costs associated with procurement. Sales and Distribution (SD): For services or goods related to sales orders. Benefits of the P2P Cycle in SAP Streamlines procurement processes. Ensures accurate financial records. Improves vendor relationships through timely payments. Provides visibility into spending and procurement performance.
P2P cycle in SAP (End user) Read More »