Tips about Error EA299 ‘Could not write IDoc to file’ for RFFOEDI1

There is one standard IDOC type DIRDEB with Basic type PEXR2003 used to generate EDI payment documents. It worked fine all the time until last week when one user complained one file was missing in the desired AL11 directory even with multiple re-runs.

Service Due Indicator for Managers

Background:

In Many Tables there might be a need to provide a quick high-level view of the Pending status of every record for a quick view by Managers.

For example, a Service Team Manager might want to see the list of Service Orders whose Service Due date is in the past (or) Service Due date which is today (or) Service Due date which is in future.

In these scenarios, we can provide an Indicator in the first column so that the Manager will be able to see the status immediately.

Consuming REST API with Basic Authentication- Step-by-Step Guide for the GET Method

In this blog post, I will show you how to consume an API step by step. The API contains various methods, with the most commonly used ones being “Get,” “Post,” and “Delete.”

For the sake of example, in this blog, I will use the “Get” method.

“GET” Method: The “GET” method is used to retrieve information from a web API or query resources (data). This method is used to request data from a specific resource and is typically called with parameters through a URL (web address). A “GET” request typically does not modify data, it only reads it.

RAP EML Dynamic Operations: Dynamic EML Requests

Introduction

In the world of ABAP development, the RAP framework has revolutionized the way we build robust and flexible applications. One of the key features of RAP is the ability to dynamically generate EML (Entity Manipulation Language) requests. In this blog post, we will explore the dynamic form of MODIFY ENTITIES OPERATIONS, which allows us to perform operations on multiple business objects within a single statement.

Customer Aging and Supplier Aging Reports at the Line Item Level using Analytical Query in S/4HANA Cloud, Public Edition

Introduction

Functional consultant or a business key user can effortlessly generate supplier and customer aging reports using the Custom Analytical Queries App for the scenarios outlined below.

Scenario – Accounts Payable Aging:

Your client requires a supplier aging report that displays the aging at different levels: Supplier level, Reconciliation G/L level, Supplier Region level, and Profit Center level. Additionally, they would like the option to access the aging information at the accounting document level in the same report.

How to add two or more fields in a range table with FOR Expression

Requirement: To form a range table consuming two or more fields from a table in ABAP.

Old or Traditional way of Coding:

*Define the structures of table

TYPES:

  BEGIN OF lty_comp,

    seqno  TYPE char4,

    wtype1 TYPE char4,

    wtype2 TYPE char4,

    wtype3 TYPE char4,

Traceability Text in VF03 T-code & also on reports FBL5N & FBL3N

Introduction

Requirement: To enhance the functionality of text which is maintained during sales order creation ( VA01 ) under item level. When we pass the sales order ID in ( VF01 ) Billing document is generated. Please check the below screen shot.

Create new CO-PA Margin Analysis characteristic with existing table as code list

Introduction

In S/4HANA OP2022 there are several ways to create customer specific characteristics for Margin Analysis. While using transaction KEA5 might seem like the most intuitive and classic way to create new characteristics it will make it very hard to use those with any Fiori applications.

The “new” Fiori enabled way to create characteristics would be by using the Fiori app F1481 “Custom Fields” with the “Market Segment” business context.