SAP

SAP S/4 HANA FSCM: Cash and Liquidity Management Configuration

In SAP Financial Supply Chain Management, the Cash and Liquidity Management module provides functionality for managing cash positions and forecasting liquidity. The Cash Operations functionality is used for calculating the current cash position, while the Liquidity Forecast functionality is used for forecasting cash positions in the longer term.

To generate a liquidity forecast, the system uses information such as invoice payment terms, sales orders, vendor invoice payment terms, and purchase requests/orders to derive the forecasted incoming and outgoing payments. This helps organizations to plan their cash requirements in advance, and take necessary actions to ensure sufficient liquidity is available to meet their obligations.
This document provides a basic guide to maintaining related configuration settings for Cash Management in SAP FSCM:

  • Define Basic Settings
  • Define Planning Levels and Planning Groups
  • Define Flow Types for Cash Flow Statement Preparation
  • Data Setup to Activate Cash Management Reporting
  • Use Flow Builder
  • Derivation Rules for Assignment of Liquidity Items

Read more

End Users Guide to Service Entry Sheet Process in SAP MM

Service Entry Sheet (SES) is a document used in SAP Materials Management to confirm the receipt of services performed by a vendor. It is used to verify that the services performed are accurate and that they meet the requirements of the purchase order. The SES process involves creating a service entry sheet that references a purchase order with standard items or limit items to procure lean services. After entering the purchase order number in the service sheet all purchase order items for lean services are added to the service entry sheet by the system.
This document explains the steps required for creating Service Entry Sheet in detail with screenshots;

  • Create Service Entry Sheet: Check Output Message [ML81N]
  • Check Service Entry sheet number and Goods Receipt document in PO History [ML81N]
  • Create Service Entry Sheet: Print Out [ML83]
  • Cancel/Revoke Service Entry Sheet [ML81N]
  • Create print out put messages of Service entry sheet [MN13]

Read more

Mastering Bill of Materials Process in SAP PP: Users Guide

The production master data consists of work centers, routings, Bill of Material and production versions. The Bill of Material data specific to production and planning will be described in the bills of material process definition document. In this document the process of creating and changing a manufacturing Bill of Material in SAP ERP is described.
Bill of materials (BOM) is a hierarchical list of components needed to complete a saleable end-item. BOMs are hierarchical in nature with the top level representing the sub-assembly or end-item. The BOMs that describe the sub-assemblies are referred to as Modular BOMs. A bill of material can define products as they are designed (Engineering Bill of Material), as they are ordered (Sales BOM), as they are built (Manufacturing BOM), or as they are maintained (Service BOM).
After reading this document, you will learn how to:

  • Create/Change/Display Bill of material in SAP (CSO1)
  • Display Multi Level BOM (CS12)
  • Display Multiple BOM (CS14)
  • Display a particular component of BOM(CS15)
  • Mass Change BOM (CS20)

Read more

5 Steps Configuration Guide to Product Allocation in SAP S/4 HANA

SAP S4HANA has built a product allocation mechanism process for manufacturers to keep an accurate record of product availability and planning as per end customer requirements. Product allocation is a function provided for carrying out control options intended to help an extensive organization avoid critical requirement and procurement situations. In simple words, product allocations represent an ordered allocation of production for certain periods. Product allocations can be created according to various criteria such as customer-wise or region-wise. Product allocation allows you to set buying limits on customers or groups of customers, which is sometimes required by companies that have new releases in high demand in the market. The goal is usually to allow for proportional supply across different regions, thus enabling a broad but solid market presence and high customer satisfaction regardless of region.
Following configuration steps are covered in this guide with screenshots;

  • Step 1: Activate Product Allocation
  • Step 2: Configure Product Allocation Object
  • Step 3: Manage Product Allocation Planning Data
  • Step 4: Manage Product Allocation Sequence
  • Step 5: Assign Product to Product Allocation

Read more

SAP S/4HANA Third Party Sales Process Configuration Guide

In SAP, the third party process is a procurement process in which a company does not keep the products in stock but instead relies on a third-party supplier to deliver the products directly to the customer. The third-party vendor provides the goods and services to the customer, and the company acts as an intermediary, passing on the order and payment information to the vendor. The company then receives payment from the customer and pays the third-party supplier. In SAP, the third-party process can be managed using the standard purchasing and sales processes with some additional settings to accommodate the third-party vendor. The process includes creating a purchase order for the third-party vendor, creating a sales order for the customer, and creating a billing document to issue an invoice to the customer.
Following configuration and end user steps are covered in this guide with screenshots:

  • Definition and Determination of TAS item Category in SD
  • Maintain Account Assignment in Purchasing
  • Maintain Purchasing Info Record
  • Third Party Process step by step without Shipping Notification
  • Post Goods Receipt [MIGO]
  • Invoice Verification [MIRO]
  • Billing [VF01]

Read more

Configuration Guide to Payment Process in SAP MM

SAP provides an automatic option for the payment program that consists on the payment request and its handling towards the conversion to a payment document. This payment program allows the companies to create documents to vendors, customers, and even G/L accounts, as well as to generate other documents that may be used to exchange with other systems, such as a bank’s system.

This option consists on creating payments based on requests instead of open items. Payment requests are blocked so that users can filter and select which of them will go on through the payment process.

At the end of this procedure, users will be able to manage payment block indicators, define clearing accounts per bank and payment methods, establish differences in dates that may occur between payment requests, payment creation and value date in house banks all based on factory calendars.

  • Define global settings [F8BG]
  • Define number ranges for payment requests [F8BM]
  • Define payment blocking indicators for accounting documents [S_ALR_87001743]
  • Define clearing accounts for receiving bank for acct. transfer [S_ALR_87001755]
  • Define ALE compatible payment methods [S_ALR_87001834]
  • Define bank clearing account determination [S_ALR_87001860]
  • Define diff. in days between value date of house/partner bank [S_ALR_87001895]
  • Define factory calendar per currency [S_ALR_87001909]
  • Define number of days between payment run date and value date at house bank [S ALR 87099738]
  • Define clearing accounts for cross-count bank account transfers [S_PLO_09000090]

Read more

New Developer’s Guide to IDocs in SAP

The SAP IDoc Technology is used in ALE, EDI, and 3rd Party Systems Integration scenarios. An IDoc stands for intermediate document and is simply a data container used to exchange information between any two processes that can understand the semantics of the data. IDocs are independent of the direction of data exchange. An inbound and an outbound process can use an IDoc. IDocs in the SAP system are stored in database tables. We can use transactions to view, edit, and process them. When an IDoc is generated in the system, a unique number is assigned to it via a Number Range Object. This number is unique within a client. An IDoc is created as a result of executing an Outbound ALE or EDI process whereas with an inbound ALE or EDI process, an IDoc serves as input to create an application object in SAP, like a Sales Order or PO. Using this technique avoids creating redundant IDoc types.
In this book, you will explore the architecture of an IDoc, IDoc’s definition and runtime components.

  • Basic IDoc Type
  • IDoc RUN Time Components
  • Technical Description of the IDoc Format
  • IDoc extensionsand enhancements. Why do We Need an Extended IDoc?
  • Create a new IDoc Segment using transaction WE31
  • Create a new Custom IDoc Message Type using transaction WE81
  • Create a New IDoc Assignment using transaction WE82
  • IDoc Processing and Message Control
  • Finding and Updating an IDoc Customer Exit Using SMOD

Read more