Enjoy the Answers to Frequently Asked Questions About:

source: sdn.sap.com

Central User Administration Overview : ABAP Query Primer :Getting Started in BSP

Getting Started in BSP

The document describes the step by step activities to be performed while creating and executing a simple BSP. It is suitable for budding BSP developers who needs a start up.

Click here for the full version of the document..... BSP

ABAP Query Primer

This document describes various options for using query tools in the ABAP context and differentiates the prototypical ABAP/4 Query tool and the query tools such as SAP Query, QuickViewer, and InfoSet Query. These tools are described from two perspectives: that of the end user who has little programming knowledge, and the ABAP developer, who must handle certain administrative tasks in the query environment.

Click here for the full version of the document.....ABAP Query Primer

Central User Administration Overview

Using Central User Administration, you can maintain user master records centrally in one system.

Click here for the full version of the document.....User Administration Overview

source: sdn.sap .com

Implementing a Business Add In (BAdI) in an Enhancement

This tutorial shows how to implement a custom BAdI, into an SAP Enhancement Project - CMOD. This eliminiates the inherent problems associated with Enhancements/Projects caused when multiple developments are sharing the same Enhancement. e.g. Transports Organizing, Syntax Errors, Release strategies, Bundled non releated functionality.

Click on BADI for the full version of the document....BADI

source: sdn.sap.com

How to Implement Events in Table Maintenance

How to implement the table maintenance events which is very helpful while creating new entries in a table. Many validations and checks can be performed while creating or saving entries in a table using transactions or via SM30.

Click here for the full version of the document...Events in Table

Business Transaction Events (BTE) Guide : FI Enhancement Technique

This article provides a step-by-step guide on the usage of Business Transaction Events, as an Enhancement technique in the Financial Accounting Module of the SAP R/3 system. The Open FI enhancement technique was developed in the Financial Accounting component.

It can be used as Validation, Substitution, Processing point, etc. It works based on the event like FI document simulation, before saving the FI document, after saving the FI document,

Click here for the full version of the document....BTE

SAP Tables for Technical Consultants & also for Function Consultants !!!

Tables on below topics :

Authorisation, objects, Batch input map's, Batch jobs,Correction & transport, Countries, Currency, Data elements, Development classes, Domains, Dynpro areas, Filenames, Function modules, Function groups, Icons, Logical databases, Matchcodes, Messages, Programs, Repository objects, Purchase Requisition, SAPscript, Spool, Status (menu), Switch objects, Tables and views, Texts, Transactions, User parameters, Variants, Accounting, Accounting documents, Bill Of Material, Classification, Classification characteristics, Configurator, Cost elements, centers, activities, Customer,Equipment, Equipment status, Function location, Customising tables, General ledger accounts, Goods movement, Customising, Inventory document, Maintenance Order, Material, Material document, Notifications, Orders,Personel, Production resource tools, Customising tables, Project, Purchase Requisition, Purchasing document, Purchasing info record, Reservation, Sales Document, Sales requirements, Storage locations and stocks, Tasklist, Transfer requirement, User data, Vendor master, WM transfer, Other tables, Useful Transactions, Function modules, Standard data transfer, Helpful reports.

Click on SAP Tables for the document.

SAP ABAP Query....CATT Scripts....Excel Sheet > 1

ABAP Query - A Quick Glance

This article discusses SAP Query. It begins with an introduction to SAP Query and its uses, then shows how to create a program using Basic List and generate program code from query.

Click here for the full version...ABAP Query

Testing Function Modules Using CATT Scripts

This article describes how to test function modules and check the logs using CATT scripts.

Click here for the full version... CATT Scripts

Creating Excel Spreadsheet with More Than One Page

Normally, we use the Function module WS_EXCEL to download the data into an excel sheet, but sometimes we may require to download the different data in to an Excel spreadsheet with more than one sheet, in that case we can make use of the OLE concept to achieve this one. Use the Class cl_gui_frontend_services,In this class use the method clipboard_export.

Click here for the full version...WS_EXCEL

SAP Interface Strategy...BSP Applications...BAPI Step by Step

Interface Strategy for Custom Development

The Client application portfolio will consist of a set of system components configured to operate together in support of standard business processes. Wherever possible, these components will be elements of the mySAP.com product suite. In specific cases, we will incorporate non-SAP applications, either commercial software products or Client custom applications, to provide different or additional functionality. These application components must be integrated at the data or transaction level. The heterogeneous, distributed application landscape necessitates the configuration or construction of interfaces to allow the required exchange of data.

Click here for the full version....Interface

How to Use Interactive Forms in BSP Applications

Using Adobe Interactive Forms in BSP applications isn't much different from doing just standard print forms from BSP. It just takes an understanding of a few details as well as the iXML library to parse the result that is passed back from the Interactive Form. The following tutorial will guide you through creating the Interactive Form, creating a BSP application that uses the Form, and parsing the data returned by the form with the iXML API.

Click here for the full version....BSP

BAPI Step-by-Step

This document describes step by step procedure to use BAPI function modules in Reporting .

Click here for the full version....BAPI

SAP Workflow : ECC 6.0 : Tasks, Rules, Troubleshooting

How to Create Your Own Rule in Workflow

This article highlights rule creation in workflow. The rule is used to pick the right agent at runtime. From this document the reader can learn how to create a rule in workflow for processing the work item.

Click here for the full version....Workflow

Complete Guide for Tasks in Workflows in SAP ECC 6.0

This is a complete guide for tasks in workflow; it is helpful for the beginners to understand the relevance of task in workflow, it contains the different types of tasks, features in task, important transaction codes involved.

Click here for the full version....Guide for Tasks

Complete Guide to Learn ALE Error-Handling through Workflow and Implementation in SAP ECC 6.0

Through this document the reader will be able to get a detailed idea about the working of the Workflow whenever an error occurred in the ALE Idoc. The idoc at the receiving system will be validated and correspondingly a workflow will be triggered whenever there is an error occurred in the idoc.

Click here for the full version....ALE Error Handling

Rules in Workflow in SAP ECC 6.0

This document is prepared to give the beginners a brief idea about Rules in SAP Business Workflow. The document contains basics of Rules and also shows how and where rules can be applied in Workflow with necessary screenshots.

Click here for the full version....Rules

Workflow Troubleshooting and Monitoring in SAP ECC 6.0

A major advantage of workflow is the ability to monitor the workflow steps according to a predefined schedule. Deadline monitoring defines the time span with in which a job is scheduled to start 'or' terminate.

Click here for the full version....Troubleshooting and Monitoring

source: sdn.sap.com

SAP Technical Upgrade – Tips and Tricks

Overview

This article describes SAP upgrade projects: What steps to follow in an upgrade, what points to be taken care of, what are various prerequisites, etc. The SAP technical upgrade scores for a short duration project ? 20 days to around 3 months duration. In technical upgrades, we aim to get the same or better SAP functionalities in the new system (SAP ECC 6.0) as in the old system (SAP 4.6).

Click here for the full version.....Technical Upgrade

SAP Upgrade Project...Simple Rule...Tax Calculation Application

SAP Technical Upgrade Project

This article is about the Upgrade Project and what are the phases involved in it and what happens in technical upgrade time.

Click here for full version....Upgrade Project

How to Create and Process a Simple Rule

Explains the creation of a simple rule and how to process it.

Click here for full version....Simple Rule

Building a Tax Calculation Application

In this tutorial, you learn to model an application for calculating the final tax amount to be paid by an employee.

Click here for full version....Tax Calculation

source: sdn.sap.com

CATT Tool..Roll-out Projects..One Transport System..System Landscape Directory

Master Data Uploads Using CATT Tool

The steps involved for uploading of master data & cutover open items by using CATT tool, which will be useful for the functional consultants with out the help of writing BDC program by the ABAP consultant.

Click here for full version.....CATT Tool

Organizing Translations in SAP Implementation Roll-out Projects

This document describes the diferrent appraches of translation and which approach is best suited for roll-out projects.

Click here for full version.....Roll-out Projects

CTS+: One Transport System Fits All - Slides

The enhancements of the Change and Transport System allow using it also for transporting Java objects. Visit this session if you like to know about Best Practices and Examples for using the enhanced Change and Transport system (CTS+). In addition, you'll get answers to questions like 'What is new in the area of CTS+?' and 'What is planned for the future?'.

Click here for full version.....One Transport System

System Landscape Directory: Planning Guide

This documentation provides you with a central starting point for the planning of your landscape strategy for the system landscape directory of SAP NetWeaver. It helps you to decide how many system landscape directories you require + how and where to run them in your landscape.

Click here for full version.....Planning Guide

Some important SAP ABAP Articles

Creating Email Content Using SO10 Objects and Text Symbols

The article describes the benefits of SO10 objects as compared to text symbols...Click here

Guidelines for Effective Data Migration

This article provides a set of guidelines for data migration using LSMW and/or customer developer programs...Click here

How to Extend an Outbound IDoc

This document provides details on why we need an extended IDoc and how to create it. We will also see a step-by-step procedure for creating an extended IDoc. The steps involve creating a segment of required structure, extend basic IDoc, and assign new segment to extended IDoc. Also involves Maintaining message type, partner profile and implementing the User exit. Further the IDoc is transferred to the destination. A whole overview of Extended Outbound IDoc can be learned with this article....Click here

Sending Outlook Appointments and Meeting Requests Directly from ABAP Applications

Sample code to demonstrate how to send Appointments or Meetings Requests to e.g. Microsoft Outlook directly from a Netweaver (6.20 or higher) based system. There are many possible ways to use this, one very logical and helpful use is to automatically send "vacation"/Leave of absence appointments back to a respective employee and his manager after vacation/leave request approval in SAP HCM....Click here

Limitation in BAPI Scheduling Agreement (SA) Create or Change

The article describes the limitations in standard SAP BAPIs to create or change Scheduling Agreements with multiple line items, each of which having multiple conditions....Click here

Version Management of ABAP Programs

In some companies we may have different systems for Development, Quality Control and Production. Writing a new program from scratch in Development will never be a problem for developers. However, sometimes someone else writes a code and the program is maintained, changed, or enhanced by some other developers. In those cases, there is a great possibility that we start changing or updating wrong versions of the program. In addition, manual comparison of the ABAP programs can lead to a waste of time, which can be avoided....Click here

Implementing Menu Exits and Screen Exits in CJ92 Transaction (PS Module)

This tutorial shows how to implement Menu Exits and Screen Exits for transaction CJ92 in PS Module. It shows how to add new Menu item to the existing Menu and a new Screen with Custom Fields....Click here

Workflow: Cross System and Cross Client

The article describes the concept and approach for cross system and cross client workflows...Click here

source: www.sdn.sap.com

Create or Change Scheduling Agreement Using Standard SAP BAPI

The article describes the procedure to create or change scheduling agreements using BAPI – 'BAPI_SAG_CREATE' or 'BAPI_SAG_CHANGE' respectively.

Click on below for the full article....

Create or Change Scheduling Agreement

Missing Authorization Assistance - ZSU53

This tool was developed to simplify the process of finding the appropriate profiles/roles for users to get the job done! Just execute this program and it will list all the profiles/roles which contain the missing (last failed) authorization!

Assign any identified profile/role found to the user to get going with the work...

Click on below for full article....

Missing Authorization Assistance - ZSU53

ABAP Runtime Analysis (SE30) - How to analyze ABAP program flow

The ABAP Runtime Analysis (transaction SE30) is the best starting point if you want to execute performance or flow analysis of your ABAP program. Unfortunately many people use ABAP Runtime Analysis only to look for performance bottlenecks and don't know that ABAP Trace is the only tool with which you can trace the execution flow of an ABAP program at the statement level.

This blog will show you how to use ABAP Trace of ABAP Runtime Analysis (SE30) to follow the flow logic of your ABAP program.

Click on below for full article.....

ABAP Runtime Analysis (SE30)

Workflow Configuration of Inbound IDOC processing:

Standard SAP IDoc interface uses ALE as the transfer mechanism and workflow functionality is used to route a failed IDOC to a specific individual or workgroup.

Application Link Enabling (ALE) is a component-based architecture enabling software component from SAP and from other software vendors to communicate and be integrated with each other. ALE can integrate business processes between R/3 Systems and non-R/3 systems as well as between R/3 Systems.

Business data is exchanged with an external system using the IDoc Interface. The IDoc Interface consists of the definition of a data structure and a processing logic for this. The data structure is the IDoc. It is the exchange format that unites the communicating systems. Using IDocs you can define an exception handling within the SAP System using SAP Business Workflow, without the need for the data to already be an SAP application document.

To implement the distribution of business application processes and functions using ALE you need to construct a logical Distribution Model of the whole system. Within the framework of this configuration, customers can specify which applications are to run on which systems and which messages are to be exchanged between the applications.

Follow the below 3 Steps for the configuration :

Workflow Configuration of Inbound data processing
Workflow Configuration ALE / Organization Unit
Workflow Processing Inbox fallout
Workflow Processing IDOC programming / Testing

IDoc : Transaction Codes

Workflow Configuration of Inbound data processing

Main Path: Tools->Business Communication

First step in the workflow configuration is to identify the IDOC type to be used for the inbound processing

The main menu path to configure the IDOC can be found under Tools in SAP Easy Access Screen:

ALE > Inbound data processing

Business Communication > IDOC setup

Business Workflow > Org setup

WE30 - Identify the IDOC type

Identify the IDOC types for the inbound transaction, e.g.: ORDERS05 for orders, DELVRY03 for shipments, etc

Make sure to use the latest available version, e.g.: for shipment, the latest would be DELVRY03

Make sure the IDOC has been released

WE81 - Identify the Message type

Identify the message type for the transaction, e.g.: ORDERS for orders, SHPCON for shipments, etc

WE82 - Link IDOC to Message type

In this screen, link the Message type with the Basic type

WE57 – Link IDOC to Function Module

For a custom function module that will be used to process the inbound IDOC:

Use SE37 to create the FM

Find one that is related and copy

Create a new entry with the new custom FM

BD51 – Define FM attribute

If your custom FM would be using a 'Call Transaction', enter '2' in 'Input'

Check the 'Dialog allow', this will allow to run foreground and background if checked

WE42 – Define Process Code

For custom FM, create a new process code

Click on Logical message

Enter the Message Code if your setup required it, eg, you can setup different message code that will be use in the FM to identify logic specific for Beaconlite vs MBP

Message Code can also be used to assign different org. unit for fallout notifications

Double click on the process code to get to this screen

Click on the ==> to go to next screen

This setup will be use to configure the fallout event triggering

SWE2 – Event linkage

Take note of the Receiver type, this will be use in subsequent fallout configuration

Workflow Configuration ALE / Organization Unit:

ALE configuration

Transaction Code: SALE

Steps:

Maintain Logical system

Maintain Partner profiles

Maintain inbox workflow recipient

Maintain recipient by responsibility (as needed)

Maintain Logical System

The logical system is used to uniquely identify a system in the network

Use this if the partner is neither a customer or a vendor

Organization Management

Organizational structure is created by assigning objects of the following types to each other:

Organizational Unit

Position

Job

Person

User

Task

PPOCW - Maintain inbox workflow recipient:

Create New Org unit

This step is to setup the business user getting the error notification for any failed IDoc

Create New Position

Put the cursor on the org unit and click on 'Create'

Click on 'Position', and press the enter button

Create the new Position

Assign Position to User

Right click on the position, click on 'Assign'

Place the cursor on the 'User'

and press the enter button

Find the user to be assign

Press Enter

Click on 'Yes'

Assign Task to Position

Place the cursor on Position again (Delivery fallout)

Right click, and select 'Assign'

Place the cursor on Standard task, and press the enter button

Click on the 'Column Configuration'button

Put a check on all

Take the ID (XXXXXXXX) for the Org. Unit

Make sure to save the setup (will create a transport)

WE20 – Partner Profile

3 types of Partner types

KU – customer

LI – vendor

LS – logical system

Create a new partner profile under Partner type LS

For AP, I think we would need to create the partner under LS

Enter the Partner number, Type and Agent.

You should not use a user for this, user can come in and out, not stable

This is the default Agent that will get notified if the agent in the inbound Post processing agent does not get resolved

Click on the "+" create the inbound parameter

Enter the Message type and Process code

- Select Processing to be 'Trigger by background program'

Click on the 'Post processing permitted agent'

Enter Type, Agent and Lang

This is the setup for the error notification

Workflow Processing Inbox fallout:

SBWP – SAP Business Work Place

Any outstanding fallout items would be available here

A user can be assigned to multiple tasks

Reserving a work item

You can execute workflow items by either "double clicking the item" or selecting the item and clicking "Execute" button on the menu bar

This prohibits anyone else from taking the same work item

There are 2 kind of status buttons, one is white (square shape) and the other is blue (square shape). Items in white has not been reserved by anyone.

Releasing a work item

If you determine that the item does not belongs to your business unit or for any other reason you are not going to trouble shoot this item you MUST release the item

This will allow the work item to be place back in the queue

Place the cursor on the item, right click and select 'Replace' or use the (dotted square shape)button on top of the menu bar.

Forwarding a work item

To forward a workflow items beyond your team, place the cursor on the item, right click and select 'Forward'. A new popup screen will come up, you can enter the User in this box.

Fallout processing - Process

Double click on the work item to get more info for the fallout.

Use the 'Process' button to fix the fallout.

Fallout processing - Deletion

If there is a need to resend the IDOC, you must delete the existing fallout work item to delete it from the queue

Click on the 'Delete flag' and the 'Yes' button to confirm the deletion.

Fallout processing - IDOC Status

Expand the 'Status records' to view error messages

Workflow Processing IDOC programming / Testing :

SE37 – Function Module builder

FM usually starts with IDOC_INPUT_XXXXXX

XXXXXX usually is the message type, eg DESADV for delivery, ORDERS for order, etc

The FILL_DATA_XXXXXX is where you do data validation and build internal tables and variables needed for subsequent process

The MAINTAIN_DATA_XXXXXX is usually where you see the main logic of the program, eg: to update orders, delivery, purchase order, etc

FILL_DATA_XXXXXX

This section contains editing logic and data validation

IDOC_STATUS_FILL

This is where you fill up the error messages you want display in the IDOC. You will need the status, document number, message ID, message number, and detail messages (msgv1-4).

Status value:

50 - erster_statuswert_eingang

51 - fehler_bei_uebergabe

52 - beleg_unvollstaendig

53 - alles_ok

54 - fehler_in_der_bearbeitung

WE19 – IDOC test tool

Find an IDOC to be copied and change the data

Use the Inbound function module to test the IDOC

IDoc : Transaction Codes

WE31 – IDoc segments

WE60 – IDoc types documentation
WE30 – IDoc types
WE81 – Message types
WE82 – IDoc Type / Message
WE60 – Process codes
WE41 – Outbound process code
WE42 – Inbound process code
WE57 – Message / application object
WE09 – Find IDoc in database
WE19 – test tool
WE20 – Partner profiles
WE21 – Ports in IDoc processing
SBWP – SAP Business Work Place
SALE – ALE IMG
BD67 – Function modules for inbound ALE-EDI: details
BD64 – Maintain Distribution Model and Distribute Views
SM59 – Display and maintain RFC destinations
PFTC_DIS – Maintain Task
PFAC_DIS – Maintain Rule
PPOSW– Maintain Organization Structure
WE47 – IDOC status maintenance
SWO1 – business object builder
SE37 – function module builder
SE91 – messages

Workflow Configuration of Inbound IDOC processing:

Standard SAP IDoc interface uses ALE as the transfer mechanism and workflow functionality is used to route a failed IDOC to a specific individual or workgroup.

Main Path: Tools->Business Communication

First step in the workflow configuration is to identify the IDOC type to be used for the inbound processing

The main menu path to configure the IDOC can be found under Tools in SAP Easy Access Screen:

ALE > Inbound data processing

Business Communication > IDOC setup

Business Workflow > Org setup

WE30 - Identify the IDOC type

Identify the IDOC types for the inbound transaction, e.g.: ORDERS05 for orders, DELVRY03 for shipments, etc

Make sure to use the latest available version, e.g.: for shipment, the latest would be DELVRY03

Make sure the IDOC has been released

WE81 - Identify the Message type

Identify the message type for the transaction, e.g.: ORDERS for orders, SHPCON for shipments, etc

WE82 - Link IDOC to Message type

In this screen, link the Message type with the Basic type

WE57 – Link IDOC to Function Module

For a custom function module that will be used to process the inbound IDOC:

Use SE37 to create the FM

Find one that is related and copy

Create a new entry with the new custom FM

BD51 – Define FM attribute

If your custom FM would be using a 'Call Transaction', enter '2' in 'Input'

Check the 'Dialog allow', this will allow to run foreground and background if checked

WE42 – Define Process Code

For custom FM, create a new process code

Click on Logical message

Enter the Message Code if your setup required it, eg, you can setup different message code that will be use in the FM to identify logic specific for Beaconlite vs MBP

Message Code can also be used to assign different org. unit for fallout notifications

Double click on the process code to get to this screen

Click on the ==> to go to next screen

This setup will be use to configure the fallout event triggering

SWE2 – Event linkage

Take note of the Receiver type, this will be use in subsequent fallout configuration

Workflow Configuration ALE / Organization Unit:

ALE configuration

Transaction Code: SALE

Steps:

Maintain Logical system

Maintain Partner profiles

Maintain inbox workflow recipient

Maintain recipient by responsibility (as needed)

Maintain Logical System

The logical system is used to uniquely identify a system in the network

Use this if the partner is neither a customer or a vendor

Organization Management

Organizational structure is created by assigning objects of the following types to each other:

Organizational Unit

Position

Job

Person

User

Task

PPOCW - Maintain inbox workflow recipient:

Create New Org unit

This step is to setup the business user getting the error notification for any failed IDoc

Create New Position

Put the cursor on the org unit and click on 'Create'

Click on 'Position', and press the enter button

Create the new Position

Assign Position to User

Right click on the position, click on 'Assign'

Place the cursor on the 'User'

and press the enter button

Find the user to be assign

Press Enter

Click on 'Yes'

Assign Task to Position

Place the cursor on Position again (Delivery fallout)

Right click, and select 'Assign'

Place the cursor on Standard task, and press the enter button

Click on the 'Column Configuration'button

Put a check on all

Take the ID (XXXXXXXX) for the Org. Unit

Make sure to save the setup (will create a transport)

WE20 – Partner Profile

3 types of Partner type

KU – customer

LI – vendor

LS – logical system

Create a new partner profile under Partner type LS

For AP, I think we would need to create the partner under LS

Enter the Partner number, Type and Agent.

You should not use a user for this, user can come in and out, not stable

This is the default Agent that will get notified if the agent in the inbound Post processing agent does not get resolved

Click on the "+" create the inbound parameter

Enter the Message type and Process code

- Select Processing to be 'Trigger by background program'

Click on the 'Post processing permitted agent'

Enter Type, Agent and Lang

This is the setup for the error notification

Workflow Processing Inbox fallout:

SBWP – SAP Business Work Place

Any outstanding fallout items would be available here

A user can be assigned to multiple tasks

Reserving a work item

You can execute workflow items by either "double clicking the item" or selecting the item and clicking "Execute" button on the menu bar

This prohibits anyone else from taking the same work item

There are 2 kind of status buttons, one is white (square shape) and the other is blue (square shape). Items in white has not been reserved by anyone.

Releasing a work item

If you determine that the item does not belongs to your business unit or for any other reason you are not going to trouble shoot this item you MUST release the item

This will allow the work item to be place back in the queue

Place the cursor on the item, right click and select 'Replace' or use the (dotted square shape)button on top of the menu bar.

Forwarding a work item

To forward a workflow items beyond your team, place the cursor on the item, right click and select 'Forward'. A new popup screen will come up, you can enter the User in this box.

Fallout processing - Process

Double click on the work item to get more info for the fallout.

Use the 'Process' button to fix the fallout.

Fallout processing - Deletion

If there is a need to resend the IDOC, you must delete the existing fallout work item to delete it from the queue

Click on the 'Delete flag' and the 'Yes' button to confirm the deletion.

Fallout processing - IDOC Status

Expand the 'Status records' to view error messages

Workflow Processing IDOC programming / Testing :

SE37 – Function Module builder

FM usually starts with IDOC_INPUT_XXXXXX

XXXXXX usually is the message type, eg DESADV for delivery, ORDERS for order, etc

The FILL_DATA_XXXXXX is where you do data validation and build internal tables and variables needed for subsequent process

The MAINTAIN_DATA_XXXXXX is usually where you see the main logic of the program, eg: to update orders, delivery, purchase order, etc

FILL_DATA_XXXXXX

This section contains editing logic and data validation

IDOC_STATUS_FILL

This is where you fill up the error messages you want display in the IDOC. You will need the status, document number, message ID, message number, and detail messages (msgv1-4).

Status value:

50 - erster_statuswert_eingang

51 - fehler_bei_uebergabe

52 - beleg_unvollstaendig

53 - alles_ok

54 - fehler_in_der_bearbeitung

WE19 – IDOC test tool

Find an IDOC to be copied and change the data

Use the Inbound function module to test the IDOC