This is the second part of a detailed comparison of the order creation process using APIs and IDocs. The first part focused on partner mappings. In this part, I will examine the mapping of external material numbers to internal ones. My objective is t...
In my previous post, I described how to select an API for creating orders based on EDI data and how to test a payload using SE80. This article focuses on a key aspect of EDI integration: mapping external partners to internal partners and determining ...
From IDOCs to APIs In my previous posts, I described various aspects of EDI inbound order processing using the classical IDOC-based approach. However, SAP considers IDOCs an outdated technology, and the use of APIs is recommended for S/4HANA impleme...
Sales area and Sales Order type determination for inbound orders are managed using t-code VOE2 and table EDSDC. This is a well-known standard setting step for EDI implementation. Therefore, it's an important and powerful tool that SAP provides, offer...
Partners are a mandatory part of any sales order and key data elements for EDI interchange. At first, this topic doesn't seem sophisticated. However, having worked as an EDI and SAP Logistics consultant since 2013, I have implemented a wide variety o...
Hi,As I promised, I have posted a new article regarding UoM determination. I hope you'll find something new. Feel free to add comments or ask questions.
Thank you!Several month ago I tried to find a convenient way to convert text EDIFACT to XML to prepare an example for MIG creation based on my productive examples. And I missed the idea to use the Integration Advisor functionality for this. Thank you...
Thank you!Several month ago I tried to find a convenient way to convert text EDIFACT to XML to prepare an example for MIG creation based on my productive examples. And I missed the idea to use the Integration Advisor functionality for this. Thank you...
