SAP MM WM ABAP Workflow ALE/IDOC EDI Dominik Tylczyński July 30, 2012

Benefit from breaking SAP rules of thumb

October 24, 2011

5

SAP MM WM ABAP Workflow ALE/IDOC EDI Dominik Tylczyński

Rules are good - as long as you know when to break them. The same goes for SAP world. Let's see a couple of SAP rules of thumb and examine benefits of not following them.

Tagged: , ,

Quickly fill your batch input data table

September 16, 2011

0

SAP MM WM ABAP Workflow ALE/IDOC EDI Dominik Tylczyński

Even in the days of direct inputs and BAPIs the old fashioned batch inputs are still widely used. Here I present a simple yet efficient method to quickly populate BDCDATA table that is required when calling an SAP transaction in background.

Free of charge SAP IDES access

July 25, 2011

5

SAP MM WM ABAP Workflow ALE/IDOC EDI Dominik Tylczyński

SAP IDES stands for Internet Demonstration and Evaluation System. It is great demonstration and education platform providing real-life business processes and their integration. Now it is available free of charge.

Tagged: ,

Import a single object from a transport request

July 22, 2011

0

SAP MM WM ABAP Workflow ALE/IDOC EDI Dominik Tylczyński

Sometimes there is a transport request exported into data and co-files out which only a single object needs to be imported into destination SAP system. Standard option is to import entire transport request only with all the objects included in it. Here is a simple method to import a single object.

Posted in: SAP Basis

Generic change documents display

July 8, 2011

1

SAP MM WM ABAP Workflow ALE/IDOC EDI Dominik Tylczyński

Change documents are one of the nicest cross-application functions in SAP ERP. They allow for close monitoring of who, when and what changed in system data - down to a single field. Better yet, they can be easily incorporated into custom applications. See how to use SAP report to analyze both standard and custom change documents.

Easy BAPI testing in SE37

July 6, 2011

1

SAP MM WM ABAP Workflow ALE/IDOC EDI Dominik Tylczyński

As a general implementation rule, BAPI functions don't perform COMMIT WORK. Saving changes performed by a BAPI requires subsequent call to BAPI_TRANSACTION_COMMIT function. Such a transaction model makes it difficult to test BAPIs in SE37 transaction, as the results of BAPI call can not be checked in standard SAP transactions immediately. Here is an easy way to solve this problem.

Follow

Get every new post delivered to your Inbox.