Search

Home Trainings Quiz Tips Tutorials Functional Cert Q's Interview Q's Jobs Testimonials Advertise Contact Us

SAP Virtual/Onsite
Trainings

Palazzo delle Stelline

103

Miglior Prezzo
Garantito
Booking.com

Document Categories:
ABAPTM
Adobe Forms
ABAP-HR
ALE & IDocs
ALV
BAPI
BASIS
BSP
Business Objects
Business Workflow
CRM NEW
LSMW
SAP Script/Smart Forms
BI/BW
eXchange Infrastructure (XI)
Enterprise Portals (EP)
eCATT
Object Oriented Programming
SAP Query
Userexits/BADIs
WebDynpro for Java/ABAPTM
Others

XI - Inter Company Stock Transfer Order between 2 SAP systems

achieved by designing a BPM
By Venkata Narayana Marella, YASH PI Competency Core Team, Yash Technologies

Business Scenario:

Inter Company Stock Transfer Order between 2 SAP systems achieved by designing a BPM

Qual
l'hotel n.
1 in
Milano?

14

Prenota ora
TripAdvisor

What's New?
ABAP Test Cockpit HOT
SAP ABAP Pragmas
Understanding SE32 (ABAP
Text Element Maintenance)
Creating an IDoc File on SAP
Application Server
Understanding Advance with
dialog option of SAP Workflow
SAP Workflow Scenario:
Maintenance Notification
Approval
Enhancements to a standard
class
Working with Floating Field in
Adobe Forms
Inserting data from Internal
Table into the step Send Mail
Display GL Account long text
using enhancement framework
Differences between
polymorphism in JAVA and
ABAP
Passing multiline parameters
from an ABAP Class event to a
Workflow container
Concept of Re-evaluate agents
for active work items in SAP
Workflow
Dynamic creation of component
usage in ABAP WebDynpro
Adobe Forms: Display symbols
like copyright and others
Deactivate Hold functionality in
Purchase order (ME21N)
Quiz on OOABAP
Add fields in FBL5N using
BADIs
Tutorial on Wide casting
Defining a Range in Module
Pool Program
Copy fields from one
structure/table into another
structure/table
Side Panel Usage in NWBC

Contribute?

When a Purchase Order in the System A is created, then the output type NEU is triggered to generate the
IDOC and Post it to System B.
In System B, Sales Order is created for Corresponding Purchase Order in System B. As this Sales Order is rush
order, it would create delivery automatically and would then generate another IDOC and send back to System A.

Some settings would be required in R/3 (Business system) before sending to other system.
Mappings:

Purchase Order to Sales Order:

Map the customer number, Customer material, Sales organization, Distribution channel and division in the
enhancement EXIT_SAPLVEDA_001 in source system and to pass the PO number in delivery note IDOC the
exit EXIT_SAPLV56K_002 in target system are used, below are the segments used to map the required data.
E1EDK14 Sale area
E1EDP01 Item data

E1EDK02 Purchase order and date

E1EDP19 Material identification

This is achieved by designing BPM in XI and following steps illustrate how to achieve it.
BPM

Sample Specs

A business process is an aggregation of operations performed by people and software systems containing the
information used in the process, along with the applicable business rules.

What's Hot?

BPM Sync/Async

Web Dynpro for ABAP Tutorials

Join the Mailing List

Palazzo
delle
Stelline

With this exercise we will be able to model a 'Sync/Asyn' pattern using BPM and apply it to IDOC
communication.

103

Miglior Prezzo
Garantito
Booking.com

Enter name and email address below:

Name:
Email:
Subscribe

GO

The requirement is to receive the PO from system A and send it to System B in synchronous mode. And
receive the Delivery notification from System B and send it back to the System A as response using the BPM
Sync/Async.
Communication between a synchronous and an asynchronous business system:

Unsubscribe

Create business process management IP_STO_PO_OR_Sync_Async

DELIDOC (Abstract interface, MI_DEL_ABS)

Create container variables

POIDOC (Abstract interface, MI_PO_ABS

Create correlation object ID with the messages MI_DEL_ABS, MI_PO_ABS with the
/ORDERS05/IDOC/E1EDK01/BELNR from PO and /DELVRY03/IDOC/E1EDL20/XABLN from Delivery.

fields

Switch to the Graphical design editor and design the BPM by dragging the required steps and filling the
properties.

You can only define one sync/async bridge per integration process.

Synchronous receive (Opening Receive): Receives the Request message from the synchronous
business system and opens the sync/async bridge. The receive step must be the first in the IP. In the
receive step you specify the synchronous interface receiving the message from the synchronous
business system. The IP is started when the message is received. The message type of the message
to be received and the request message from the synchronous interface must be identical.

This step receives the PO IDOC and opens the bridge. Give the properties as shown below:

Asynchronous Send: Sends the received request message asynchronously to the asynchronous
business system.

Send step: This step sends the received PO IDOC asynchronously and uses the correlation

Asynchronous Receive: Receives the response message from the synchronous business system.

Synchronous Send: Sends the response message from the asynchronous business system
synchronously to the synchronous business system and closed the Sync/asynch Bridge.

Receive step: This step receives the Delivery IDOC asynchronously by using the

correlation.

This

step

sends

the

Delivery

IDOC

and

closes

the

sync

bridge

Block Step: This is required to define the exception and handle the exception. Here exception is
required as Synchronous Receive message (PO) is different from the Synchronous Send Message
(delivery).

Exception

Handler:

This

is

required

to

catch

the

exceptions

Send Delivery IDOC in the Exception block

Click here to continue...

Qual l'hotel n. 1 in
Milano?
14

Prenota ora
TripAdvisor

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM

Home Contribute About Us Privacy Terms Of Use Disclaimer Safe Companies: Advertise on SAPTechnical.COM | Post Job Contact Us
2006-2007 SAPTechnical.COM. All rights reserved.
All product names are trademarks of their respective companies. SAPTechnical.COM is in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver, and and any other SAP trademarks are registered trademarks of SAP AG in Germany and in several other countries.
Every effort is made to ensure content integrity. Use information on this site at your own risk.

Graphic Design by Round the Bend Wizards