Gentran Suite

Sap Suite Adapter in S:I
ALE Mode
Prague, January 2004 Carsten Michel
SapSuite Adapter in S:I
Adapter using 3rd Party Libs from SAP ( JCO libs)

Libs need to be installed separately
Supports 4 different Modes
BAPI Inbound (Outbound in S:I 3.1)
Rfc/tRfc Inbound (Outbound in S:I 3.1)
Filebased Idoc Transfer In/Outbound
ALE based Idoc Transfer In/Outbound
Training covers Idoc Issues (FileSystem based and

ALE)
Functionality in GIS 3.0

File based IDoc exchange via RFC (Remote Function
Call)
ALE based IDCO exchange through Network
IDoc format 3 and 4
Packaged Inbound and Outbound BPs (templates)
Status message support for Outbound processing
Supports all SAP R/3 versions
Command line tool to generate IDoc Meta Data
Description
SAP Suite Adapter

Comparison with GENTRAN product line
Example business processes allow easy transition from
GENTRAN UNIX to GIS (X-Ref)
New tool to extract IDoc meta data directly from SAP system
(no SAP report required)
SAP Suite Adapter

Requirements
SAP JCo libraries from SAPs Website (account required)
Supported Platforms
HW
OS
Supported
PC
Windows
Yes
PC
Linux
Yes
SUN Sparc
Solaris
Yes
IBM RS/6000
AIX
Yes
HP HP9000
HP-UX
Yes
IBM zSeries
zOS
JCo Beta
IBM zSeries
zLinux
NO
IBM iSeries
OS400
NO
Filebased Rfc Configuration
Chose Filebased Rfc Mode
Configuration (2)
Enter Sap System
Information
Choose to Start Rfc Server
for SAP Outbound
Define number of Server
Instances
Define BP that should be
started once an Idoc is sent
by SAP
Define the Program ID for
Registration with the SAP
System
Configuration (2)
Enter the User Details

Language and Codepage
refer to the Settings of SAP
Language Examples:
EN English
DE German
FR French
Codepage Examples:
1100 European(ISO8859-1)
8000 Japan(SJIS)
Configuration(3)
Used to configure the Client

Connection Pool
Max. Connections defines
how many connections are
in the Connection Pool for
this Adapter Instance
Difference in ALE
Configure SAP System

details.
Sap Version relates to the
Idocs that are inbound into
SAP
ALE is transactional and we
can automatical resend a
failed Idoc without risk
Tid Management is used for
duplicate checking
Idoc Encoding defines the
Encoding for Outbound
IDoc/RFC Overview
Sterling Integrator
Port
RFC trigger call
RFC Client
2nd send Trigger
SAP Adapter
Suite
Inbound BP
1 put IDoc
st
SAP
Outbound BP
2nd get IDoc

IDoc and Status
messages
RFC
Dest.
RFC trigger call

Registration opens
A Tunnel to SAP
RFC Server
1st Start BP
IDoc/ALE Overview
Sterling Integrator
Port
RFC trigger call

Including IDoc
SAP Adapter
Suite
SAP
RFC
Dest.
RFC trigger call

Registration opens
A Tunnel to SAP
c 2003 Sterling Commerce, Inc.
RFC Client
Inbound BP
Outbound BP
RFC Server
Start
Status Message Support
EDI Sub-system Status Messages for

Outbound Processing
04 failure of EDI Subsystem (GIS) to accept IDoc

05 Translation failed
06 Translation successful
07 Compliance checking failed
08 Compliance checking successful
09 Enveloping failed
10 Enveloping successful
Status Message Support
Outbound Status Message Creation

IDoc not configured properly
Status message 4
Translation failed
Status message 5
Translation successful
Status message 6, 8 and 10
Outbound BP Overview
More Docs
SAP
SAP
Adapter
Suite
Document
Extraction
Translation
SAP
Adapter
Suite
File System
Adapter
Status
Message
File System
Adapter
SAP Outbound BP
SAP
IDoc(s)
Split
IDocs
04
For Each
Document
EDI
Encoder
05
EDI
Envelope
IDoc
Translation
Status
Translation
Release
Status
OK
Message
AccepterLookupAlias
ReceiverID
Return Status message

(SAPInbDelivery)
SenderID
Business Process
c 2003 Sterling Commerce, Inc.
Service
SAP Status Message (on Error)
Filebased Idoc Inbound BP
SI
SI
De-envelope
Translation
File
System
Adapter
SAP
Adapter
Suite
SAP
ALE Idoc Inbound BP
SI
SI
De-envelope
Translation
SAP
Adapter
Suite
SAP
Inside SAP for Idoc outbound

Employee enters
Purchase Order in SAP
ORDER
SAP Determines the

Vendor that we are
buying at
Vendor
SAP looks in Message

control (nace) to find out
what to to with for this
vendor
EDI
SAP looks in the Partner
Profile (we20) which Port
to use to deliver the
Purchase Order
Port
SAP find the right, already

connected external
software and sends the
Order (ALE or FbRFC)
Programm-ID
The RFC Destination

builds the link to the
external Software which
uses a Programm-ID to
registern in SAP
Rfc-Destination
The Port describes if the

session will be ALE or
FbRFC and knows which
RFC-Destination to use
RFC Destinations (sm59)
First configure the RFC Destination.

Go to sm59 and create a new RFC-Destination for
SI.
The Connection Type is T.
Choose Registration Mode. Press Enter.
Provide a Program ID.
You can now press Test connection and should be
able to see that you are connected to SI.
Ports in IDoc processing (we21)
Create a new Port of Type File.

Provide all the Directory and Filename information
Choose the RFC-Destination that you have created
before in the Trigger Tab
Check the flag Autom. Start Possible
in the label Outbound: Trigger.
In francese: Lancement automat
Message Control (nace)
Use the nace SAP-Transaction to configure the

message flow for a BusinessPartner, e.g. Vendor
Depends on the SAP Application and Workflow
Possible ways to transport Business Data are:
EDI
Print to Paper
Fax
Configure the Scheduling when data is send
Partner Profiles (we20)
Choose your Business Partner in we20. E.g. a

Supplier
Create a new Entry in the Outbound Parameters List
Define type and function ot the Partner and what
type of message you want to send.
Provide the PORT that you created earlier.
Sequence of Steps (in SAP)
Employee enters an Order for that Vendor.

SAP looks into the Partner profile and finds the
PORT.
The PORT describes how the data needs to be send
(ALE, File based RFC(FbRFC))
SAP creates the IDoc and finds the right RFCDestination in the PORT Configuration.
In mode FbRFC it writes the IDoc to the Filesystem
Sap finds the Program ID in the RFC-Destination and
sends the IDoc or the Trigger to the Application that
registered before with the Program ID.
Inbound
For Inbound only start a BP that sends the IDoc in its

Primary Document.
When the Sap Version is correct and the User that
you use to login to SAP has the right permissions the
Adapter will send the IDoc to SAP and you will be
able to see it in Transaction we02.
To setup the needed Workflows in SAP to process
the IDocs, it might be quite handy to have a SAP
Admin sitting next to you ;-)
SAP Suite Adapter
Thank you for your time

Questions?

Gentran Suite

Uploaded by

Copyright:

Available Formats

Gentran Suite

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Gentran Suite

Uploaded by

Copyright:

Available Formats

What are the different modes supported by the SAP Suite Adapter?

What are the different modes supported by the SAP Suite Adapter?

How does the adapter integrate with SAP?

How does the adapter integrate with SAP?

Sap Suite Adapter in S:I

SapSuite Adapter in S:I

Adapter using 3rd Party Libs from SAP ( JCO libs)

Training covers Idoc Issues (FileSystem based and

Functionality in GIS 3.0

SAP Suite Adapter

SAP Suite Adapter

SAP JCo libraries from SAPs Website (account required)

Filebased Rfc Configuration

Chose Filebased Rfc Mode

Enter the User Details

Used to configure the Client

Configure SAP System

2nd send Trigger

2nd get IDoc

RFC trigger call

RFC trigger call

RFC trigger call

c 2003 Sterling Commerce, Inc.

Status Message Support

EDI Sub-system Status Messages for

04 failure of EDI Subsystem (GIS) to accept IDoc

Status Message Support

Outbound Status Message Creation

Status message 6, 8 and 10

Return Status message

c 2003 Sterling Commerce, Inc.

SAP Status Message (on Error)

Filebased Idoc Inbound BP

ALE Idoc Inbound BP

Inside SAP for Idoc outbound

SAP Determines the

SAP looks in Message

SAP find the right, already

The RFC Destination

The Port describes if the

RFC Destinations (sm59)

First configure the RFC Destination.

Ports in IDoc processing (we21)

Create a new Port of Type File.

Message Control (nace)

Use the nace SAP-Transaction to configure the

Configure the Scheduling when data is send

Partner Profiles (we20)

Choose your Business Partner in we20. E.g. a

Sequence of Steps (in SAP)

Employee enters an Order for that Vendor.

For Inbound only start a BP that sends the IDoc in its

SAP Suite Adapter

Thank you for your time

You might also like