This post will focus on introducing the application named Postman as a tool to help SAP Functional Consultants in their SAP testing. This is not going to be a full blown technical how-to guide for developers (I might touch base on that in the future with a separate post). Instead, the goal of this post is to simply help functional consultants get acquainted with Postman and provide some high-level use cases.
In this post we will discuss the purpose of CDHDR and CDPOS SAP Tables and how to utilize them. Standard SAP and a Custom SAP Program will be provided as examples. We will additionally discuss some information that deals with the overall usage of the 2 tables.
In this post we will go through the steps needed to create, export / import, and finally run the LSMW. This will additionally cover how to create your own Batch Input Recording and how to reuse the created LSMW. Towards the end we will discuss some frequently asked questions.
This post will help you determine the Table-Field or Table-Technical Name equivalent in SAP. This information is particularly useful when writing functional specifications and doing further analysis. This post will also include quick tips that answer related questions.
In this post we will quickly discuss how to troubleshoot and resolve SAP IDoc Error “Error Passing Data to port” or Error Text “Could not find code page for receiving system”. We will additionally cover how to reprocess the erroneous IDoc for it to successfully post and the key difference between transaction code WE20 vs WE21.
In this post, we will quickly go through the detailed steps needed to create and release your SAP Transport of Copies or TOC. We will additionally cover the purpose of Transport of Copies.
Here are some of the most used SAP Financial Accounting (FI) Transaction Codes per sub module. This post will be continuously updated.
Think of yourself as an SAP Fresher being given a blank functional specification template. Sure, you may find a few keywords and/or sentences in the template. That should be enough right? My response to that is “no, it is not enough”. In this post, we will cover the 10 must-know tips in writing your SAP Functional Specification documents. Extras included.
Business Transaction Events are also known as BTEs and they are accessible through transaction code FIBF. This post will give you an overview on BTEs, their purpose, how and why to utilize them.
Learn how to change a Company Code name in SAP through this detailed guide and checklist. Additionally learn the impacts, testing, and documentation involved in this type of change.
Understand the definition, overview, and modules of SAP ERP. Additionally get a quick insight on the functionalities advantages, and innovations.
Learn how to differentiate between the available SAP interfaces. This post focuses on the key differences between RFC, BAPI, IDOC, EDI, ALE, UDDI, SOAP, WSDL, REST, API, FTP, and SFTP.