Adapotors

SAP NetWeaver Process Integration 7.
31
Simple Use Cases for B2B AS2 & EDI Separator Using
Integration Flow Configuration
Simple Use Cases for B2B AS2 & EDI Separator using Integration Flow Configuration
TABLE OF CONTENTS
1 Preface .............................................................................................................................................. 6
1.1 Constraints ....................................................................................................................................... 6
1.2 Definition .......................................................................................................................................... 6
1.3 Intended Audience........................................................................................................................... 6
1.4 Structure ........................................................................................................................................... 6
2 Introduction and Prerequisites ...................................................................................................... 6
2.1 Introduction ...................................................................................................................................... 6
2.1.1 AS2 Adapter ...................................................................................................................................... 8
2.1.2 EDI Separator .................................................................................................................................... 8
2.1.3 EDI-XML Converters.......................................................................................................................... 8
2.1.4 SCN Articles ...................................................................................................................................... 8
2.2 Prerequisites .................................................................................................................................... 9
2.2.1 General Prerequisites ........................................................................................................................ 9
2.2.2 Providing the necessary User and Authorizations ........................................................................... 10
2.2.3 Setting up the Third party Tool Infrastructure (AS2 Connector) ...................................................... 10
2.2.4 Configuring the Certificates for authorization and authentication .................................................... 10
2.2.5 Setting Up the File Directories ......................................................................................................... 10
2.2.6 Adding Software Components to PI B2B ADDON product ............................................................. 11
2.3 Design Objects Used ..................................................................................................................... 12
2.3.1 Interface Objects .............................................................................................................................. 12
2.3.2 Mapping Objects .............................................................................................................................. 12
2.4 Working with NWDS ...................................................................................................................... 12
2.4.1 Setting Connection Parameters ....................................................................................................... 12
2.4.2 Opening Perspectives and Views .................................................................................................... 12
2.4.3 Connecting to the Systems .............................................................................................................. 13
2.4.4 Maintenance tool and B2B Seed File .............................................................................................. 13
2.5 Variant 1a: One Sender and one Receiver using the Advanced Adapter Engine Extended –
Encryption and Signature with synchronous MDN .................................................................................... 14
2.6.1 Summary of Design Objects Used .................................................................................................. 15
2.7 Configuring the Process Integration Scenario ........................................................................... 15
2.8 Calling the Process Integration Designer ................................................................................... 15
2.9 Creating the Integration Flow ....................................................................................................... 15
2.10 Creating Channels ......................................................................................................................... 16
2.11 Saving and Activating the Configuration Objects ...................................................................... 19
2.12 Configuring the trading partner ................................................................................................... 19
2.12.1 Creating the trading partner ............................................................................................................. 19
2.13 Executing the Use Case ................................................................................................................ 19
3 Variant 1b : AS2 Adapter with EDI Converter (Plain XML and XML to Plain) .......................... 20
3.6 Saving and Activating the Configuration Object ........................................................................ 22
4 Variant 2a: AS2 Adapter – Encryption, Signature and Compression of the message with
Asynchronous MDN ...................................................................................................................................... 23
2

4.1.1 Creating the trading partner on AS2 connector ............................................................................... 25
5 Variant 2b: AS2 Adapter – Encryption, Signature and Compression of the message with
Asynchronous MDN and Creation of New XI Message.............................................................................. 27
5.4 Creating the Integration Flow1 ..................................................................................................... 27
5.8 Creation of Integration Flow2 ....................................................................................................... 30
6 Variant 3: AS2 Adapter – Decryption and Signature of the message without MDN Signature
32
6.7.2 Adding test data to the configured trading partner .......................................................................... 36
7 Variant 4a: AS2 Adapter – No Decryption and No Signature of the message with Signed
Async MDN ..................................................................................................................................................... 37
8 Variant 4b: AS2 Adapter – Duplicate message handling Feature in AS2 ................................ 42
8.8 Execution and Verification............................................................................................................ 48
3
9 Variant 5: AS2, EDI Separator (ANSI X12 transaction sets 830, 856, 997) and EDI-XML
Converter ........................................................................................................................................................ 49
9.1 Configuring the Integration Flows ............................................................................................... 50
9.1.1 Calling the Process Integration Designer ........................................................................................ 50
9.1.2 Creating the integration Flows ......................................................................................................... 50
9.1.2.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. .............................................. 50
9.1.2.2 Integration Flow 2: Sender: EDI Separator & EDI-XML Converter module, Receiver: File adapter 51
9.1.2.4 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter ............................................... 52
9.1.3 Configuring the integration Flows .................................................................................................... 52
9.1.3.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. .............................................. 52
9.1.3.4 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter ............................................... 58
10 Variant 6: AS2, EDI Separator (ANSI X12 transaction sets 830, 856, 997), EDI-XML Converter
& Conversion Using the Maintenance Tool ................................................................................................ 70
10.1.1 Integration Flow 3: Sender: EDI Separator & EDI-XML Converter module, Receiver: File adapter 70
11 Variant 7: AS2, EDI Separator (EDIFACT: DELFOR and DESADV) and EDI-XML Converter . 71
11.1.2.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. .......................................... 73
11.1.2.2 Integration Flow 2: Sender: EDI Separator & EDI-XML Converter module, Receiver: File adapter
74
74
11.1.2.4 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter ........................................... 74
77
79
11.1.3.4 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter ........................................... 81
12 Variant 8: AS2, EDI Separator (Odette: AVIEXP and DELINS) and EDI-XML Converter ......... 92
4

93
93
96
97
12.2.2 Adding test data to the configured trading partner ........................................................................ 100
12.3 Saving and Activating the Configuration Objects .................................................................... 100
12.4 Executing the Use Case .............................................................................................................. 100
13 Variant 9: AS2, EDI Separator (VDA: 4905 and 4913) and EDI-XML Converter ..................... 101
13.1 Configuring the Integration Flows ............................................................................................. 101
13.1.1 Calling the Process Integration Designer ...................................................................................... 101
13.1.2 Creating the integration Flows ....................................................................................................... 101
13.1.2.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. ........................................ 101
102
102
13.1.3 Configuring the integration Flows .................................................................................................. 102
13.1.3.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator. ........................................ 102
105
106
13.2 Configuring the trading partner ................................................................................................. 107
13.2.1 Creating the trading partner on AS2 connector ............................................................................. 107
13.2.2 Adding test data to the configured trading partner ........................................................................ 108
13.3 Saving and Activating the Configuration Objects .................................................................... 109
13.4 Executing the Use Case .............................................................................................................. 109
5
1 Preface
1.1 Constraints
The texts, references, and graphics contained in this manual have been compiled with utmost care;
nevertheless, it is impossible to guarantee that they are fully without error. SAP cannot assume any
responsibility for the correctness or completeness of the following documentation; the user alone is
responsible for verifying the information contained therein.
SAP will only assume liability for damage arising from the use of this documentation – irrespective of the
pertinent legal basis – in the case of intentional or active negligence; under no other circumstances will a
warranty be made.
1.2 Definition
This manual describes simple application cases using Integration Flow configuration for B2B and all the
configuration steps that are necessary to execute the application cases on the basis of SAP NetWeaver
7.31.
1.3 Intended Audience

This manual is intended to be used by both technology and application consultants.
1.4 Structure
The structure of this document follows the sequence of steps required to configure and run the use cases.
2 Introduction and Prerequisites

2.1 Introduction
Use cases are based on simple examples that enable you to learn the main features of the B2B AS2 Adapter
Configuration and EDI Separator Configuration for the Advanced Adapter Engine Extended. These
instructions will enable you to understand, configure, and execute simple scenarios (that are based on
fundamental communication patterns), as well as check that the scenarios are executed correctly. The
prerequisite for this document is that you have a general understanding of SAP NetWeaver Process
Integration.
The scope of this test case is to test the following features of the AS2 adapter and EDI-Separator.
AS2 Adapter
 Verification of signature for ensuring non-repudiation
 Signed MDN
 Compression of message payload
 Encryption of message payload for message integrity
 Signing of message for non-repudiation
 Encryption of message payload for message integrity
 Synchronous signed MDN with request and verification of MIC (Message Integrity Check) and signing
 Decryption of message payload for verifying message integrity
 Separating the combined message by the use of EDI Separator adapter
EDI Separator
 ANSI X.12 message with Transaction Set Identifier Codes and Interchange Sender/Receiver Id
specified
 Edifact with message type, version, release number, interchange sender and receiver identification
and code qualifier specified
 Odette with message type, version number, Interchange sender and recipient identification and code
qualifier specified.
 VDA with message type, customer and vendor number specified
 Acknowledgement (positive) message generation for ANSI X.12 message type
The following use case variants for the Advanced Adapter Engine Extended are available at present:
6
Variant Description
Variant 1: Represents message exchange between one sender and one receiver on
One sender and one receiver-with the Advanced Adapter Engine Extended (AEX) with encryption and
synchronous MDN signature of the message followed by sending the synchronous MDN.
The message processing is done locally on the Advanced Adapter
Engine Extended.
One sender and one receiver-with the Advanced Adapter Engine Extended (AEX) with encryption, signature
Asynchronous MDN and compression of the message followed by sending the Asynchronous
MDN. The message processing is done locally on the Advanced Adapter
Engine Extended.
One sender and one receiver- with the Advanced Adapter Engine Extended (AEX) with decryption and
unsigned synchronous MDN signature of the message followed by sending unsigned the synchronous
MDN. The message processing is done locally on the Advanced Adapter
Engine Extended.
One sender and two receivers – with the Advanced Adapter Engine Extended (AEX) without decryption and
signed synchronous MDN signature of the message followed by sending the synchronous MDN.
The message processing is done locally on the Advanced Adapter
Engine Extended.
Variant 5: Represents message exchange parting from a trading partner as ASC

AS2, EDI Separator (transaction set 830, X12 message containing two message types (transaction sets), being
856, 997) and EDI-XML Converter (X.12 converted into XML and split by the EDI separator. Additionally an
to XML) acknowledgment message (transaction code 997) is generated and sent
back to the trading partner via AS2 adapter
Variant 6: Based on the scenario in variant 5 by adding the module converter to one
AS2, EDI Separator (transaction set 830, of the file receivers and using the maintenance tool to convert one of the
856, 997), EDI-XML Converter (XML to received messages to xml and back to X.12.
X.12) & Conversion Using the
Maintenance Tool
Variant 7: AS2, EDI Separator On this variant, an EDIFACT multi-message containing two message
(EDIFACT: DELFOR and DESADV) and types (DELFOR and DESADV) is sent by a trading partner. The message
EDI-XML Converter is split by the EDI Separator, converted into XML and sent to a file
receiver.
Variant 8: AS2, EDI Separator (Odette: On this variant, an Odette multi-message containing two message types
AVIEXP and DELINS) and EDI-XML (AVIEXP and DELINS) is sent by a trading partner. The message is split
Converter by the EDI Separator, converted into XML and sent to a file receiver.
Variant 9: AS2, EDI Separator (VDA: On this variant, a VDA multi-message containing two message types
4905 and 4913) and EDI-XML Converter (4905 and 4913) is sent by a trading partner. The message is split by the
EDI Separator, converted into XML and sent to a file receiver.
You can aim to learn about the following with the use cases:
 Working with the AS2 protocol and AS2 adapter
 Configuring The EDI Separator adapter and splitting different types of messages
 Using the EDI-XML Convertor module and maintaining control data on the maintenance tool
7
 Working with the Process Integration Designer in NWDS: Configuring simple scenarios and
understanding created configuration objects
 Working with the runtime: Executing the use cases and checking the results by using the monitoring
tools
SAP provides the required design objects and files for these learning targets. This document contains a
complete set of instructions that enable you to configure and execute the use cases without any additional
special prerequisites.
SAP NetWeaver Process Integration (Advanced Adapter Engine Extended) must be installed
and configured, and be error free.
2.1.1 AS2 Adapter
The AS2 Adapter enables data transfer using the AS2 protocol.
AS2 (stands for Applicability Statement 2) is a protocol is used to transport data securely and reliably over
the Internet, based on HTTP and S/MIME. The partners are always connected via the tried and tested
HTTP(s) protocol. The AS2 process is a clear choice thanks to its effective firewall administration capability,
signature, encryption, return receipt/acknowledgement (MDN) and rapid response times.
Detailed information on the AS2 protocol can be found in RFC 4130.
2.1.2 EDI Separator
The EDI Separator is a component providing the feature of splitting incoming mass EDI messages into single
messages. It is implemented as a PI Adapter and therefore can be used on sender and receiver adapter
channels that are configured to perform the splitting function. Furthermore, the adapter controls the “content
based receiver determination”. This feature of the adapter offers the possibility to use content-based routing
(message identification) and split mass messages according to interfaces based on message type and
partner.
The SAP NW PI EDI Separator adapter supports 4 EDI formats which are:
 ANSI ASC X12
 EDIFACT
 ODETTE
 VDA
For at least one of the variants described in this document, the format ANSI ASC X12 will be used.
Configuration details will be explained on the corresponding variant.
2.1.3 EDI-XML Converters

EDI-XML converters are set of modules which convert from EDI formats to XML and vice-versa. All format-
specific conversions are called via own modules.
On this simple use case, The ASC X12 message is converted using the module called
“localejbs/X12ConverterModule”. This Java-Bean is able to recognize automatically whether it is an X12 or
an XML message and can process them correspondingly. A maintenance tool is available via web, where
the control data for the conversions can be maintained and conversions can be made. More information on
‎2.4.4
2.1.4 SCN Articles

Additional information can be found on the respective articles published on SAP Community Network:
Link Title
AS2 Adapter Learning Series SAP NetWeaver Process Orchestration, business to business add-on 2c
AS2 Adapter
8
EDI Separator Learning Series SAP NetWeaver Process Orchestration, business to business add-on 2f EDI
Adapter Separator Adapter
All in one guide All in one Guide ADD-On Solutions for SAP NetWeaver Process Orchestration
for Add-on
Solutions
2.2 Prerequisites
2.2.1 General Prerequisites

To configure and execute the use cases, SAP NetWeaver with usage type Advanced Adapter Engine
Extended must be correctly installed and configured. The following table lists the prerequisites and the
relevant guides:
List of required steps:
Step Documentation
1. You have installed SAP You can find the corresponding guides on SAP Service Marketplace in
NetWeaver 7.31. the Implementation Documentation Center for SAP NetWeaver 7.3 and
SAP NetWeaver 7.3 including Enhancement Package 1
2. You have imported the content SAP Note 836200

for the Enterprise Services
Repository corresponding to the
latest support package/patch.
The simple use cases are located in the Enterprise
Services Repository in the software component SAP
BASIS, software component version SAP BASIS 7.31, in
the namespaces http://sap.com/xi/XI/System/Patterns.
3. You have configured SAP Configuration of SAP NetWeaver Process Integration

NetWeaver Process Integration.
4. You have configured the System Configuring, Working with and Administering System Landscape
Landscape Directory (SLD). Directory
5. You have installed the You can find the corresponding guides on SAP Service
NetWeaver Developer Studio. Marketplace at https://service.sap.com/installnw73  Under
Installation - Standalone Engines and Clients  Installation –
Clients  Inst. and Update - SAP NetWeaver Developer Studio
7.3 EHP1 (SP04).
6. You have installed the SFTP &  You can download the B2B add-on from the following location:
PGP Add-on. http://service.sap.com/swdc -> Browse our Download Catalog - > ->
Installation and Upgrades -> SAP NetWeaver and complementary
products -> PI SFTP PGP ADDON.
7. You have installed the PI B2B  You can download the B2B add-on from the following location:
Add-on. http://service.sap.com/swdc -> Browse our Download Catalog - > ->
Installation and Upgrades -> SAP NetWeaver and complementary
products -> PI B2B ADDON
9
2.2.2 Providing the necessary User and Authorizations

To log on to the AEX system to configure the simple use cases, you have to create a user XIDEMO with the
following roles in the Advanced Adapter Engine Extended:
 SAP_XI_CONFIGURATOR _J2EE
 SAP_XI_MONITOR_J2EE
2.2.3 Setting up the Third party Tool Infrastructure (AS2 Connector)
In this document all the scenarios described are based on the third party tool called AS2 Connector by /n
Software. This third party software has been used just as an example for configuration of trading partners
for the purpose of sending and receiving the AS2 message payloads. You are free to use any third party
software and configure your scenario based on AS2 adapter. The third party software can change in your
case. The scenarios described in this document are based on /n Software AS2 connector, therefore you
need to configure the trading partners which will be used for the communication with the PI system on the
variants described in this document.
Please note that the PIs public Key certificate is used by the AS2 connector in some variants and therefore
should be present on the system hosting the AS2 connector and when configuring a trading partner the path
to the PI public key certificate will be needed. E.g. “<selected-path>/PI_Test-cert.crt”
2.2.4 Configuring the Certificates for authorization and authentication
Some of the AS2 scenarios need encryption, decryption and signing of the payload, for this
2 pairs of keys (public & private key pair) and 2 public key certificates one each for each partner are needed.
The public-private key pair and public key certificates can be generated in NWA.
The scenarios described on this document will use (if any) the public/private key pairs listed on the following
table.
For more information you can read the relevant articles as listed on ‎2.1.4
NW Key Storage View Entry Description
AS2_CERTIFICATE Partner_Test-cert Partners Public Key Certificate
AS2_CERTIFICATE PI_Test-cert Own Public Key Certificate
AS2_KEYSTORE PI_Test Own Private Key
2.2.5 Setting Up the File Directories
The variants are based on a simple system landscape that comprises various different file systems (on the
host of the SAP system on which the Advanced Adapter Engine Extended is installed). When the use cases
are executed, files are moved between file directories and/or the third party software. Therefore, to be able to
configure the use cases, the file directories must have been created and described in the System Landscape
Directory. Only then can you access the directories during configuration in the PI Designer.
Perform the steps below to create the required directories on the host of the SAP system on which the
Advanced Adapter Engine Extended is installed.
1. Open the file directory of the SAP system, on which the Advanced Adapter Engine Extended is
installed. For Example using Windows Explorer on Windows Systems.
2. Create a directory in which you can save files temporarily and create the sub directories
Inputfiles and Receiver
A work directory already exists on many computers that can be used for this purpose and under
which you can create the required directories.
3. Create further sub directories in the sub directory Inputfiles. Suggested names: Tradacoms,
ANSI, Odette, Edifact.
10
You must have authorization to access this directory to be able to test the process integration
scenario. Bear this in mind when you define the directory, and, if applicable, contact your system
administrator.
4. Copy the files to their respective directory under Inputfiles:
 ZB2B_ANSI.xml
 ZB2B_Tradacoms.xml
 ZB2B_Odette.xml
 ZB2B_Edifact.xml
 ZB2B_input.txt
These files are provided by SAP in a ZIP file. The ZIP file for 7.31 containing also the EOIO test
files is available in SAP Developer Network (SDN) and can be found using the direct link EHP 1
for SAP NetWeaver Process Integration 7.3 – Test Files for Simple Use Cases.
5. Create one more directory: AS2-EDISEP
6. Under AS2-EDISEP create the following sub-directories: 830, 856, output-edifact, output-
odette and output-vda
7. Additionally, the following files will be needed for sending messages from the trading partner:
 B2B_ansix12SenderMessage_830_856.txt
 B2B_ansix12SenderMessage_830_856_error.txt
 B2B_edifactSenderMessage_DELFOR_DESADV.txt
 B2B_edifactSenderMessage_DELFOR_DESADV_error.txt
 B2B_odetteSenderMessage_AVIEXP3_DELINS3.txt
 B2B_vdaSenderMessage_4905_4913.txt
2.2.6 Adding Software Components to PI B2B ADDON product
Perform the following steps to create the required technical and business systems in the System Landscape
Directory (SLD) for the Advanced Adapter Engine Extended:
1. To call the System Landscape Directory for the Advanced Adapter Engine Extended System, open the
Advanced Adapter Engine Extended Start Page using the URL: http(s)://<AEX-Host>:<AEX-Port>/dir.
2. Start the SLD. To do so, on the Advanced Adapter Engine Extended start page, choose System
Landscape Directory.
3. Log on using your user you created.
4. On the initial screen of the SLD, choose Products.
5. Filter for PI B2B ADDON product and check for B2B MAPPING KIT 1.0 software component version is
available in Software Components tab. If not proceed with below associations steps.
6. On the initial screen of the SLD, choose CIM Instances.
7. Filter for B2B MAPPING KIT 1.0 for class Software Component Version.
8. Click on New Association.
9. Filter for *B2B* with Association Type Software Features Software Component and Associated Class as
Product Instance.
10. Select PI B2B ADDON 1.0: JAVA COMPONENTS and click on Associate. A message for successful
association is displayed.
11. Now software component version B2B MAPPING KIT 1.0 will be available in list of Software
Components for PI B2B ADDON product.
Business Components used in the scenarios :
11
 <SID>_<User-ID>_B2B_BC_AS2_V1
 <SID>_<User-ID>_B2B_BC_AS2_V2b
 <SID>_<User-ID>_B2B_BC_AS2_EDISEP_V5_01
2.3 Design Objects Used

2.3.1 Interface Objects
Interface objects describe the communication mode and the data structure for exchanging messages.
Interface objects comprise service interfaces, message types, and data types, which you can open by means
of forward navigation, starting with the Service Interfaces.
2.3.2 Mapping Objects
If the interfaces at the sender and receiver are different, a mapping is required.
The specific design objects will be listed in the specific variants below
2.4 Working with NWDS

2.4.1 Setting Connection Parameters
If not done yet, open the SAP NetWeaver Developer Studio.
Set the connection data for accessing the Integration Directory under the menu Process Integration →
Change Preferences. The connection details to the Advanced Adapter Engine Extended System have to be
maintained using URL or AEX-Host and AEX-Port, click on “test connection” to verify if the connection is
successful. Click on Apply for saving changes.
On the same menu (Process Integration → Change Preferences), under the following path: Web Services →
Enterprise Services Browser, set the connection details for the ESR System using ESR-Host and ESR-Port.
Once done, click on Apply and exit the menu by clicking on OK.
2.4.2 Opening Perspectives and Views

For creating Integration Flows, the Process Integration Designer perspective is needed.
To call the SAP Process Integration Designer perspective, follow the menu path:
Window → Open Perspective → Other → SAP Process Integration Designer.
Please note that not all views of this perspective (shown as tabs on the left side of the NWDS) will be
opened by default. If missing you can manually open them by using the Show view icon located on the
bottom-left corner of the NWDS. After selecting one view you can change its tab position using drag & drop
with the mouse. You will need at least the following views: PI Explorer, Enterprise Services Browser, PI
Runtime Explorer and Change Lists.
12
Optionally, you can also call the “Enterprise Services Repository” Perspective:
To call the Enterprise Service Browser in the SAP NetWeaver Developer Studio follow the menu path
Window → Open Perspective → Other → Enterprise Services Repository.
Once done, you can quickly switch between perspectives by selecting the desired one on the top-right corner
of the NWDS.
2.4.3 Connecting to the Systems

Before proceeding to connection ensure that you have set the connection parameters as described
previously.
On the SAP Process Integration Designer perspective connect to the systems using the common logon
option by clicking the connect icon located on the top toolbar ( ).
Provide your credentials on the pop-up window. This will connect automatically to both, the AEX and the
ESR systems.
On the connection pop-up window, you can select the check-box “Use common credentials for directory and
repository” if your credentials are the same for both systems.
Alternatively, you can also use the common logon using the Menu Process Integration → Connect
There is also the possibility of connecting to the ESR only. If you would like to connect only to the ESR, use
the connect icon located on the Enterprise Service Browser view.
2.4.4 Maintenance tool and B2B Seed File

SAP PI B2B, specifically the XML converter uses two different types of tables B2B_X12_CTRL_* (contain
rules for creating the nesting structure for the conversion of the messages) and B2B_X12_DEF_* manage
information for generating the XML Definition Schemes (XSD‟s). For the variant described in this document,
we only have to ensure that the tables are populated. This is done using the maintenance tool for EDI
Content Manager available at B2B Integration Cockpit. Follow the next steps:
 Open B2B Integration Cockpit (proceed with user credentials if prompted):
https://host:port/webdynpro/resources/sap.com/b2b~home/B2BHome
 Then click on EDI Content Manager.
 Please check if the data is already available: Go to tab “Ansi X.12” – Tables - B2B_X12_CTRL_IF.
If the table is empty you need to import the B2B seed file. If not, you can skip the next steps.
 Copy the B2B seed file locally
 Import the “B2B seed file”: On the maintenance tool, go to tab “Ansi X.12” – Tables – Import,
browse for your local copy of the B2B seed file and click on „Import“
Since the file is larger than 20 MB, you will get the following warning message:
13
After a couple of minutes the import will be complete. Please note that no confirmation will be
displayed. If you want to see the import result, you can have a look at the import log file. The
location for the log file is displayed on the previous warning message.
After the import, the control data is available on the tables:
Repeat the same steps for Plain, VDA, Odette, Tradacoms and EDIFACT.
2.5 Variant 1a: One Sender and one Receiver using the Advanced Adapter Engine Extended –
Encryption and Signature with synchronous MDN
This variant enables you to configure and execute the simplest kind of message exchange:
One sender (file directory Inputfiles) sends a message to one receiver. Hereby, the message is
exchanged between sender and receiver adapter by using one Advanced Adapter Engine Extended.
Mapping is executed between the outbound and inbound interface and the message is being converted into
the Tradacoms type in this variant.
This section explains all the design objects that are used for describing this variant.
The subsequent description of each variant will refer to the detailed step-by-step description in this section;
the relevant design objects will only be listed briefly in each case.
The following describes all the objects that describe the message exchange in this variant in turn. There are
two possibilities to learn more about the design objects, the Enterprise Services Builder and the Enterprise
Service Browser.
To call the Enterprise Service Browser in the SAP NetWeaver Developer Studio first set the connection data
for accessing the Enterprise Services Builder under the menu Window → Preferences. Under Web Services
14
→ Enterprise Services Browser the connection details to the ESR System have to be maintained using ESR-
Host and ESR-Port.
1. To call the Enterprise Services Browser follow the menu path Window → Open Perspective → Other
→ Enterprise Services Repository.
2. Use the Connect Button to connect to the Enterprise Services Builder.
3. In the navigation area, open the software component B2B TOOLKIT software component version
B2B TOOLKIT 1.0, and namespace http://sap.com/xi/XI/AS2
4. Open the node and ensure that the adapter metadata for AS2 is present under the namespace.
5. Again ensure that the software component B2B MAPPING KIT 1.0 is available, as this contains the
mapping objects which will be consumed in the variants described
All the design objects can also be checked directly in the Enterprise Services Builder. To call it call the
Process Integration Tools Page http://<AEX-Host>:<AEX-Port>/dir and from there open the Enterprise
Services Builder.
2.6.1 Summary of Design Objects Used

The design objects used are summarized once more in the following table
Object Type (Name) Description
Specifies the communication mode (asynchronous) and references the

Service Interfaces (INVOIC.INVOIC02 message type used.
SI_INBOUND_EDI_TRADACOMS_INVOIC)
Message Type (INVFILTO9) Message Type (INVFILTO9)
Data Type (INVFILTO9) Describes the data structure of the message
2.7 Configuring the Process Integration Scenario

In configuration, you use the design objects in the process integration scenario for the actual system
landscape. You have already described the system landscape in the SLD. The communication components
you defined earlier enable you to address the involved business systems as senders/receivers of messages
from the Process Integration Designer. You perform the following configuration steps in the SAP Process
Integration Designer for the Advanced Adapter Engine Extended.
2.8 Calling the Process Integration Designer

Open the SAP NetWeaver Developer Studio, connect and open the Process Integration Designer view as
described in ‎2.4
2.9 Creating the Integration Flow
Perform the following steps to create a new integration flow.

1. In the Process Integration Designer choose New → Integration Flow ( ).
2. In category Enterprise Integration Patterns select the Point-to-Point Pattern and set the name and ID
of the Integration Flow as AS2_Variant1_IntFlowScenario_<User-ID>.
3. Choose Next.
4. To assign Business component to sender, right click on the sender -> New Business component ->
name as <SID>_<User-ID>_B2B_BC_AS2_V1-> Click Finish.
5. As Interface select INVOIC.INVOIC02.
6. In Tab Receiver Systems as Receiver component select the Business component <SID>_<User-
ID>_B2B_BC_AS2_V1 using the input help for the Receiver Name.
7. As Receiver Interface select SI_INBOUND_EDI_TRADACOMS_INVOIC.
8. Choose Finish.
15
9. The integration Flow will be displayed in a graphical overview.

10. On the line representing the message flow to receiver <SID>_<User-ID>_B2B_BC_AS2_V1 in the
context menu select Add Mapping.
11. Select the mapping object in the graphical view. The properties tab will open.
12. Using the Browse functionality select the operation mapping OM_INVOIC02_TO_INVOICTO9.
2.10 Creating Channels

You perform the following steps to configure the connection of the process integration scenario. You activate
the relevant sender-receiver relation (between the sender and receiver component) and assign both the
sender and receiver a (sender or receiver) communication channel.
1. In the graphical editor, right-click on channel for the sender component. Select Apply Channel
Template. The Choose Channel Template screen will open.
2. Select the template B2B_AS2_FileSender of software component version B2BTOOLKIT 1.0 and
press OK. Change to the channel view.
3. In tab Adapter Specific under File Access Parameter in the Source Directory field, enter the path in
the file directory that you defined previously (see 2.2.3). In the case of the sender communication
channel, enter the whole path for the file directory Inputfiles.
Example: \\host\<selected_path>\AS2\Inputfiles\Tradacoms.
4. As File Name Tradacoms.xml should be set automatically.
5. In the graphical editor, right-click on channel for the receiver component. The channel view will open
and then name the channel, as in this case named it as B2B_AS2_ReceiverAS2_Variant1.
6. In adapter type field browse and select AS2 adapter.
7. Go to Adapter-Specific tab and under General tab fill the details as given below in the table
Header Field Field Name Value
Recipient Recipient URL <Enter The URL path of the partner

(initiator) where the incoming AS2 messages
shall be received>
e.g. http://host:port/Receiver.aspx
Basic Authentication Checked
 Username <User ID for login the system where

message will be received>
 Password <Password for login the system where

message will be received>
Use your credentials
Message Filename <Enter the file name>

File_var1.txt
MessageID left .*
MessageID right .*
<Enter the AS2 identifier >

Own AS2Name
AS2 name which is transmitted in
the AS2 message as AS2-From-
Parameter
e.g. AS2_<SID>_<User-ID>_var01
16
<Enter the AS2 Name of the Recipient >

Recipient AS2 Name
AS2 name which is transmitted in
the AS2 as AS2-To-Parameter
e.g. testas2
Own email- address <Enter the email address >

The email address which is
transmitted in the AS2 message as
sender.
e.g. <user-id>@sap.com
Message subject <Enter the subject of the message>

The message subject which is
transmitted in the AS2 message as
sender.
e.g. AS2_Scenario_sign_enc
Content-Type <Enter the type of the content>
Content type with which the message is

marked.
application/edi-x12
Charset conversion Checked

Charset
 Source encoding UTF-8
 Destination encoding UTF-8
8. Navigate to the tab Signature and Encryption and fill the details as given below in the table:
Header Field Field Name Value
Signature Sign message Check the sign message
View to own public key certificate <Enter storage name of public key
certificate >
The NWA key-storage view in the

sending partner (SAP PI -initiator),
which contains the self (own) public key
certificate
e.g. AS2_CERTIFICATE / PI_Test-cert

for both (view and alias)
Alias of own public key certificate <Enter the name of the public key>
The alias (or name) under which the self

(own) public key certificate is stored
See above
View to own private key <Enter the key storage name of private
key>
sending partner (SAP PI - initiator),
17
which contains the self (own) private key

e.g. AS2_KEYSTORE / PI_Test for
both (view and alias)
Alias of own private key <Enter the name of the private key>
(own) private key is stored see above
Encryption Encrypt message Check the encrypt message box

Checked
Algorithm <Select the encryption algorithm >
The encryption algorithm to be used

(default is AES 128. The other available
values are AES 192, AES 256, 3DES and
RC2
3DES
View to recipient‟s public key <Enter the storage name of the public key>
certificate
sending partner (SAP PI- initiator),
which contains the receiving partner‟s
(responder) public key certificate
AS2_CERTIFICATE / Partner_Test-cert
<Enter the storage name of the public key>

View to recipient‟s public key
certificate The alias (or name) under which the
receiving partner‟s (responder) public
key certificate is stored
9. Now go to MDN tab and give the details as below:
HEADER FIELD FIELD NAME VALUE
MDN
Message Delivery Notification Select Synchronous
Verify MIC Checked

Request Signing Checked
Verify Signature Checked
View to signer‟s public key <Enter the key storage name>

certificate
The NWA key-storage view in the sending partner
(SAP PI- initiator), which contains the receiving
partner‟s (responder) public key certificate
18
Alias of signer‟s public key <Enter the key name>

certificate The alias (or name) under which the receiving
partner‟s (responder) public key certificate is stored
1. Go to Module Tab and Add Converter module Tradacoms converter

“localejbs/GenericConverterModule”. For adding the converter module bean click on the
Add button. Move the GenericConverterModule module bean to the first position by clicking on
the Move Up button which is present at the right hand side. The final screen should look like as
given below:
2.11 Saving and Activating the Configuration Objects

In the following steps, you save the integration flow with all its objects and activate it for the runtime.
1. Save the Integration Flow by pressing the save button ( ).

2. Use the Activate entry in the context menu of the integration flow
AS2_Variant1_IntFlowScenario_<User-ID> to activate the configuration.
3. Use the Deploy entry in the context menu of the integration flow
AS2_Variant1_IntFlowScenario_<User-ID> to deploy it in the runtime.
2.12 Configuring the trading partner
2.12.1 Creating the trading partner

2.13 Executing the Use Case
You perform the following steps to check that the use case is executed without errors.
Here the whole execution is described on the basis of third party /n software . In this variant the third party
has been used for receiving the message . Third party can vary in your case . For the configuration of third
party in /n software please refer the section ‎2.2.3.
1. On the host of the Advanced Adapter Engine Extended, open the file directory Tradacoms.
2. Rename the file ZB2B_Tradcoms.xml as B2B_Tradcoms.xml.
3. The File adapter is designed in a way that a file with exactly this name is recognized and moved
from the source directory to the AS2 Recipient every 60 seconds. If the configuration was executed
without errors, the file will be moved from the source directory within 60 seconds after it is renamed.
4. Open the third party software (In this case /n software) http://host:port/Default.aspx
5. Go to Incoming Tab select the trading partner “SAPPI_<SID>_<User-ID>_01”. The tab content
shows the successfully received messages.
6. Also the “Logs” tab shows the logs of the incoming messages (successful transmissions and errors if
any) and the MDN requested by the sender will be available in the “Logs”.
OR
19
7. As the third party software will be installed in a server. You can also go to the file structure of the
server where the third party is installed and can also check the Incoming file on the basis of the
party.
8. Open the received file and compare with the original file ZB2B_Tradcoms.xml and verify the content
of the received file. Received File can be found on: \\host\as2data\AS2_<SID>_<User-
ID>_var01\Incoming
The file must have been changed to tradacoms format when this variant is executed.
Furthermore, you can check the processing of the message in monitoring. You can do this in channel and
message monitoring. To do this, proceed as follows:
Channel Monitoring:
1. Start the Monitoring by choosing Configuration and Monitoring Home on the Advanced Adapter
Engine Extended start page.
2. Choose Adapter Engine → Communication Channel Monitor
3. Use appropriate filter criteria to restrict the number of channels displayed. On the very right hand
side select Advanced to get all possible filter criteria displayed. To select your channels, put in the
channel ID (you can find it in the channel editor screen) into the communication channel field, press
Go and select your sender channel from the list.
4. Check that the channel is running without error.
5. In the Processing Details section you can find the processing logs and the links to the processed
messages. The link can be followed to get the message details.
6. In the processing log you can see the encryption and signing of the message has been done as you
have chosen these features in the scenario.
Message Monitoring:
1. Start the Monitoring by choosing Configuration and Monitoring Home on the Advanced Adapter
Engine Extended start page.
2. Choose Adapter Engine → Message Monitor.
3. Select Database.
4. Use appropriate filter criteria to restrict the number of XML messages displayed (for example, the
processing period). On the very right hand side select Advanced to get all possible filter criteria
displayed and open the Message Header Data section. To select using your Integration Flow name
put in the Integration Flow name into the field Integration Flow.
5. Choose Go.
6. The system displays the selected messages in a table. You want to locate the messages that were
sent during execution.
7. Select the message to be displayed by selecting the appropriate radio button and then choose Open
Message.
8. The tab Payloads displays the message contents for the various versions of the message during
processing.
Note: This scenario described in this variant contains encryption and signing of message. You can also try
with different combination like without signing and with encryption or with signing and with encryption option
and test the scenario.
3 Variant 1b : AS2 Adapter with EDI Converter (Plain XML and XML to Plain)
This variant enables you to configure and execute: One sender (file directory Inputfiles) sends a message to
one receiver. Hereby, the message is exchanged between sender and receiver adapter by using one
Advanced Adapter Engine Extended and the EDI Converter has been used in the scenario which will convert
the message into Plain Message.

To call the ESR proceed as outlined in variant 1.
20

from the in the Process Integration Designer.
You perform the following configuration steps in the SAP Process Integration Designer for the Advanced
Adapter Engine Extended.
Follow the procedure mentioned in variant1.

of the Integration Flow as AS2_Variant1b_Integration_FlowScenario.
3. Choose Next.
4. As Sender Business componet select the Business component
<SID>_<UserID>_B2B_BC_AS2_V1 you imported from SLD using the Browse… button.
5. As Interface select XiPatternInterface1.
6. In Tab Receiver Systems as Receiver componet select the Business component
<SID>_<UserID>_B2B_BC_AS2_V1 using the input help for the Receiver Name.
7. As Receiver Interface select XiPatternInterface1.
8. Choose Finish.
2. Select the template XiPatternChannel_FileSender of software component version SAP BASIS
7.31 and press OK. Change to the channel view.
Example: ../../../../SYS/global/Connectivity_Test/B2B/AS2/Inputfiles.
4. As File Name AS2_Converter.txt should be set.
5. Go to the Module tab and Add Odette converter “localejbs/PlainConverterModule”.
For adding the converter module bean, click on the Add button. Move the converter module bean to
the first step by clicking on the Move Up button which is present at the right hand side. The final
screen should look like as given below:
21
and then name the channel, as in this case named it as B2B_AS2_ReceiverAS2_Var1.
8. Go to Adapter-Specific tab and under General tab fill the details as given in the variant1 table.
Uncheck the characterset conversion check box.
9. Navigate to the tab Signature and Encryption and fill the details as given in the variant1 table.
10. Now go to MDN tab and give the details as given in variant1.
Note: An MDN (Message Delivery Notification) is a functional acknowledgement of receipt generated by the
receiving party to positively or negatively acknowledge the success/failure/error in receipt of the original AS2
message.
11. Now go to Module tab and similarly add converter module “localejbs/PlainConverterModule” as given
below
3.6 Saving and Activating the Configuration Object
Proceed as described in variant1.

You can reuse the trading partner that was created and configured in variant 1.
1. On the host of the Advanced Adapter Engine Extended, open the file directory Inputfiles.
2. Rename the file ZAS2_Converter.txt as AS2_Converter.txt
The File adapter is designed in a way that a file with exactly this name is recognized and moved
3. Open the third party software (In this case /n software) http://host:port/Default.aspx
4. Go to Incoming Tab select the trading partner “SAPPI_<SID>_<User-ID>_01” (created in variant 1).
The tab content shows the successfully received messages.
OR
party.(Please refer the section 2.2.6 for checking the file).
22
7. Open the received file and compare with the original file ZAS2_Converter.txt and verify the
content of the received message should be same and the format of the received message will be
Plain . The size of the file should be compressed (size of the format should be lesser than the
original file) when this variant is executed.
Furthermore, you can check the processing of the message in monitoring. You can do this in channel
and message monitoring. To do this, proceed as given in variant1.
4 Variant 2a: AS2 Adapter – Encryption, Signature and Compression of the

message with Asynchronous MDN
This variant enables you to configure and execute: One sender (file directory Inputfiles) sends a message to
one receiver. Hereby, the message is exchanged between sender and receiver adapter by using one
Advanced Adapter Engine Extended and the mapping used in the scenario will convert the message into the
ANSI type.


The design objects used are summarized once more in the following table.

SI_INBOUND_EDI_ANSIX12_INVOICE)
Message Type (ASC810_004010) Describes the message sent at runtime and references the data type
used.
Data Type (ASC810_004010) Describes the data structure of the message


of the Integration Flow as AS2_Variant2_IntFlowScenario_<User-ID>
3. Choose Next.
4. To assign Business component to sender right click on the sender -> New Business component ->
23

7. As Receiver Interface select SI_INBOUND_EDI_ANSIX12_INVOICE.
8. Choose Finish.
12. Using the Browse functionality select the operation mapping OM_INVOIC02_TO_ASC810_4010.
channel, enter the whole path for the file directory Inputfiles\ANSI.
Example: \\host\<selected_path>\AS2\Inputfiles\ANSI
4. As File Name ANSI.XML should be set .
AS2_<SID>_<User-ID>_var02 as Own AS2Name
8. Navigate to the tab Signature and Encryption and fill the details as given in the variant1 table
and check the Compress message check box.
MDN
Message Delivery Notification Select Asynchronous
MDN target-URL <Enter the URL where the MDN will be received>
http:/<host>:port/AS2/mdn
Request signing Check the request signing

Checked
Algorithm SHA1
24
certificate

certificate
Create new XI message for None

received MDN
message.
4.1.1 Creating the trading partner on AS2 connector
Proceed as Variant 1
1. On “Organization Name”, type: SAPPI_<SID>_<User-ID>_02

2. On “AS2 Identifier”, type: AS2_<SID>_<User-ID>_var02
3. On “Partner URL”, type: http://<host>:<port>/AS2/<ExpectedURLPath>
http://host:port/AS2/AS2DispatcherServlet_<User-ID>_V2
4. On “Connection Info” select the following options:
Category Field Name Value
Outgoing Message Sign Outgoing Data Unchecked

Security Encrypt Outgoing Data Unchecked
Incoming Message Require Signature Checked

Security Require encryption checked
Compression Compress Outgoing Data Checked
Connection timeout (sec) 600
Restrict the use of signing and Unchecked

encryption algorithms…
5. On “MDN Receipts” select the following options:

Request MDN Receipt Checked
Security Signed / Unsigned Signed
Delivery Synchronous / Asynchronous Asynchronous
25
6. On “Trading Partner Certificates” provide the following data:

Trading Partner Certificate - <selected-path>\PI_Test-cert.crt

Encryption
Security Trading Partner Certificate - <selected-path>\PI_Test-cert.crt

Signature
Delivery Trading Partner Certificate - SSL Can be left empty

Server Authentication
7. Click on “Save Changes”
2. Rename the file ZB2B_ANSI.xml as B2B_ANSI.xml.
3. Open the third part software http://host:port/Default.aspx?a=Incoming go to Incoming Tab select the
trading partner “SAPPI_<SID>_<User-ID>_02”. The tab content shows the successfully received
messages.
Received File can be found on: \\host\as2data\ AS2_<SID>_<User-ID>_var02\Incoming
5. Check in the “Received Transmissions” if a file was received and an MDN was generated.
OR
party.
7. Open the received file and compare with the original file ZB2B_ANSI.xml and verify the content of
the received file and size of the file as the file must be changed to ANSI format and the size of the
format should be lesser than the original file when this variant is executed.
26
5 Variant 2b: AS2 Adapter – Encryption, Signature and Compression of the

message with Asynchronous MDN and Creation of New XI Message.
The feature tested here for AS2 adapter is, creation of new XI message specifically for MDN tracking .
 Integration Flow 1: Sender: File Adapter, Receiver: AS2 Adapter.

The message is sent from the file adapter and AS2 adapter receives the message.
 Integration Flow 2: Sender: AS2 Adapter , Receiver: File adapter
The MDN will be received at the AS2 sender, new XI message will be generated in the
communication channel monitoring and then the MDN will be sent to the file adapter (receiver).



SI_INBOUND_EDI_ANSIX12_INVOICE)
Message Type (ASC810_004010) Describes the message sent at runtime and references the data type
used.
Data Type (ASC810_004010) Describes the data structure of the message

5.4 Creating the Integration Flow1

of the Integration Flow as AS2_Variant2b_IntFlowScenario_<User-ID>
3. Choose Next.
4. To assign Business Component to sender, right click on the sender -> New Business component ->
name as <SID>_<User-ID>_B2B_BC_AS2_V2b-> Click Finish.
27
7. As Receiver Interface select SI_INBOUND_EDI_ANSIX12_INVOICE.
8. Choose Finish.
10. On the line representing the message flow to receiver <SID>_<User-ID>_B2B_BC_AS2_V2b in
the context menu select Add Mapping.
12. Using the Browse functionality select the operation mapping OM_INVOIC02_TO_ASC810_4010.
channel, enter the whole path for the file directory Inputfiles\ANSI.
Example: \\host\<selected_path>\AS2\Inputfiles\ANSI
4. As File Name ANSI.XML should be set .
AS2_<SID>_<User-ID>_var02 as Own AS2Name
8. Navigate to the tab Signature and Encryption and fill the details as given in the variant1 table
and check the Compress message check box.
MDN
Message Delivery Notification Select Asynchronous
MDN target-URL <Enter the URL where the MDN will be received>
http:/<host>:port/AS2/mdn
Request signing Check the request signing

Checked
Algorithm SHA1

certificate
28

certificate
Create new XI message for Both positive and negative MDN

received MDN
Referenced MDN Channel Name AS2 Sender channel name (from Integration Flow2)
Channel
Communication Component AS2 Sender Communication Component (from
Integration Flow2)
1. On “Organization Name”, type: SAPPI_<SID>_<User-ID>_02b

2. On “AS2 Identifier”, type: AS2_<SID>_<User-ID>_var02b
http://host:port/AS2/AS2DispatcherServlet_<User-ID>_V2b




Security Signed / Unsigned Signed
29


Encryption

Signature

7. Click on “Save Changes”.
5.8 Creation of Integration Flow2

of the Integration Flow as AS2_Variant2b_IntFlowScenario_<User-ID>_MDN.
3. Choose Next.
4. To assign Business component to sender right click on the sender -> New Business Component,
name as <SID>_<User-ID>_B2B_BC_AS2_V2b_MDN-> Click Finish.
6. In Tab Receiver Systems as Receiver component select the Business
component<SID>_<UserID>_B2B_BC_AS2_V2b_MDN using the input help for the Receiver Name.
7. As Receiver Interface XiPatternInterface2 .
8. Choose Finish.
1. In the graphical editor, right-click on channel for the sender component. Select Configure channel.
The channel view screen will open. Name the sender channel as B2B_AS2Sender_MDN.
3. Select Transport protocol as AS2MDN.
4. In the graphical editor, right-click on channel for the receiver component. Select Apply Channel
5. Select the template XiPatternChannel_FileReceiver of software component version SAP
BASIS 7.31 and press OK. Change to the channel view.
6. In tab Adapter Specific under File Access Parameter in the Target Directory field, enter the path in
the file directory that you defined previously (see 2.2.3). In the case of the receiver communication
channel, enter the whole path for the file directory AS2.
Example: \\host\<selected-path>\AS2\Receiver.
7. As File Name mdn.txt should be set.
30
You perform the following steps to check the use case is executed without errors.
2. Rename the file ZB2B_ANSI.xml as B2B_ANSI.xml.
3. Open the third part software http://host:port/Default.aspx?a=Incoming go to Incoming Tab select the
trading partner “SAPPI_<SID>_<User-ID>_02b”. The tab content shows the successfully received
messages.
Received File can be found on: \\host\as2data\ AS2_<SID>_<User-ID>_var02b\Incoming
5. Check in the “Received Transmissions” if a file was received and an MDN was generated.
OR
party.
7. Open the received file and compare with the original file ZB2B_ANSI.xml and verify the content of
the received file and size of the file as the file must be changed to ANSI format and the size of the
format should be lesser than the original file when this variant is executed.
In the channel monitoring you can see the message ID for the Integration Flow2 communication
channels is newly created and it‟s different from the message ID generated for the Integration Flow1
communication channels.
You can open the newly created XI message ID(for the Integration flow2 channels) and check the
content of the payload. The payload will have MDN details. For doing so:
1. Click on the newly created XI message ID.

2. Click on Open Message.
3. Go to payload Tab.
4. Check for the MDN content.
Also check the mdn.txt file at the receiver location given in the configuration. MDN should be received at
the receiver location.
31
6 Variant 3: AS2 Adapter – Decryption and Signature of the message without MDN
Signature
This variant enables you to configure one sender (AS2) sends a message to one receiver (File). Hereby, the
message is exchanged between sender and receiver adapter by using one Advanced Adapter Engine
Extended. The mapping used in the scenario will change the message format to Edifact type.
To call the ESR proceed as in variant1
Design Objects Used

Service Interfaces message type used.
(ORDERS.ORDERS05
SI_INBOUND_EDI_EDIFACT_ORDERS)
Message Type (ORDERS96A) Describes the message sent at runtime and references the data type
used.
Data Type (ORDERS96A) Describes the data structure of the message

of the Integration Flow as AS2_Variant3_IntFlowScenario_<User-ID>
3. Choose Next.
4. To assign Business component to sender right click on the sender -> New Business component ->
5. As Interface select ORDERS.ORDERS05.
32
7. As Receiver Interface select SI_INBOUND_EDI_EDIFACT_ORDERS.
8. Choose Finish.

12. Using the Browse functionality select the operation mapping OM_INVOIC02_TO_INVOICTO9.The
integration Flow will be displayed in a graphical overview OM_ORDERS05_TO_ORDERS96A.
1. In the graphical editor, right-click on channel for the sender component. Select Configure
channel. The channel view screen will open. Name the sender channel as
B2B_AS2_SenderAS2_Variant3.
3. Go to Adapter-Specific tab and under General tab fill the details as given in the table below.
Server Expected URL-Path <Enter The URL path of the partner

(initiator) where the incoming AS2 messages
shall be received>
AS2DispatcherServlet_<User-ID>_V3
Message Expected Message ID left Specifies the left part of the incoming AS2
MessageID.
“.*” (type without quotes)
Specifies the right part of the incoming AS2

Expected Message ID right MessageID.
”.*”

Expected sender‟s AS2Name AS2 name which is transmitted in the AS2
message as AS2-From-Parameter
e.g. testas2
<Enter the AS2 Identifier>

Expected own AS2 name The email address which is transmitted in the
AS2 message as sender.
AS2_<SID>_<User-ID>_var03
Expected subject <Enter the subject of the message>

The message subject which is transmitted in
the AS2 message as sender.
.*
33

Charset
UTF-8
 Destination encoding
Message configuration set dynamic parameter Checked

QoS Exactly once
4. Navigate to the tab Signature and Encryption and fill the details as given in the table below:
Signature Verify Signature Checked
View to sender‟s public key <Enter storage name of public key certificate >
certificate
The NWA key-storage view in the sending
partner (SAP PI -initiator), which contains the
self (own) public key certificate
Alias of sender‟s public key <Enter the name of the public key>
certificate
(own) public key certificate is stored
Decryption Decrypt message Check the decrypt message box
View to own private key significance same as receiver channel

configuration
AS2_KEYSTORE / PI_Test
Alias of own private significance same as receiver channel

configuration
MDN
Message Delivery Notification Uncheck the sign MDN
Override URL for MDN Unchecked
34
Basic HTTP Authentication Unchecked
Proxy server Unchecked
message.
7. Select the template B2B_AS2_FileReceiver of software component version B2BTOOLKIT
8. In tab Adapter Specific under File Access Parameter in the Target Directory field, enter the path
in the file directory that you defined previously (see 2.2.3). In the case of the receiver
communication channel, enter the whole path for the file directory Receiver.
\\host\<selected-path>\AS2\Receiver
9. As File Name output.txt should be set automatically.

2. On “AS2 Identifier”, type: AS2_<SID>_<User-ID>_var03
http:// host:port/AS2/AS2DispatcherServlet_<User-ID>_V3
The last part is the parameter you configured on the AS2 Sender Communication Channel (Expected
URL-Path)
Outgoing Message Sign Outgoing Data Checked

Security Encrypt Outgoing Data Checked
Incoming Message Require Signature Unchecked

Security Require encryption Unchecked
35

Security Signed / Unsigned Unsigned
Delivery Synchronous / Asynchronous Synchronous


Encryption

Signature

7. Click on “Save Changes”.
6.7.2 Adding test data to the configured trading partner
On the system hosting the AS2 connector, a new folder with the name of the AS2 Identifier has been
automatically created. Under that folder, the folder “Outgoing” was created, where the test files have to be
present in order to be sent.
1. Go to the corresponding folder of the trading partner you just created.

\\host\as2data\ AS2_<SID>_<User-ID>_var03\Outgoing
2. Copy the file “B2B_Edifact.xml” into the “Outgoing” folder.
has been used for sending the message . Third party can vary in your case . For the configuration of third
1. Start the sender and receiver channels before sending the message.
2. Go to http://<host>:<port>/Default.aspx and navigate to the Outcoming tab.
3. Select the trading partner “SAPPI_<SID>_<User-ID>_03”. The tab content shows the messages
present at the trading partner location.
4. Click on the send button.(Input file you can get from the directory Inputfiles)
5. On the host of the Advanced Adapter Engine Extended, open the file directory AS2.
6. Example: \\host\<selected-path>\AS2\Receiver
7. Verify the contents of the file –“output.txt” at the file target directory.
36
8. Go to file structure of the server where the third party is installed

http://host:port/Default.aspx?a=Outgoing and select the trading partner “SAPPI_<SID>_03. The tab
content shows the successfully sent messages in the “Sent Files” tab. Also the “Logs” tab shows the
logs of the outgoing messages (successful transmissions and errors if any) and the MDN.
9. Open the received file and compare with the file sent. The received message should be in Edifact
format and the content of the file should be same.
message monitoring. To do this, proceed as given in variant1
In the processing log you can see the decryption and signing of the message has been done as you
have chosen these features in the scenario.
Note: This scenario described in this variant contains decryption and signing of message. You can also try
with different combination like without signing and with decryption or with signing and with decryption option
and test the scenario.
7 Variant 4a: AS2 Adapter – No Decryption and No Signature of the message with
Signed Async MDN
This variant enables you to configure one sender (AS2) sends a message to one receiver(File). Hereby, the
message is exchanged between sender and receiver adapter by using one Advanced Adapter Engine
Extended. The mapping used in the scenario will change the message format to Odette type.
To call the ESR proceed as in variant1
Design Objects Used

SI_INBOUND_EDI_ODETTE_INVOIC)
Message Type (INVOIC3) Describes the message sent at runtime and references the data type
used.
Data Type (INVOIC3) Describes the data structure of the message
37

of the Integration Flow as AS2_Variant4_IntFlowScenario_<UserID>
3. Choose Next.
4. To assign Business component to sender right click on the sender -> New Business component->
name as <SID>_<User-ID>_B2B_BC_AS2_V4-> Click Finish
6. In Tab Receiver Systems as Receiver Component select the Business Component
7. As Receiver Interface SI_INBOUND_EDI_ODETTE_INVOIC.
8. Choose Finish.
10. On the line representing the message flow to receiver <SID>_<UserID>_B2B_BC_AS2_V4 in the
12. Using the Browse functionality select the operation mapping OM_INVOIC02_TO_INVOIC3 .
The integration Flow will be displayed in a graphical overview OM_INVOIC02_TO_INVOIC3.
The channel view screen will open. Name the sender channel as
B2B_AS2_SenderAS2_Variant4.
Server Expected URL-Path <Enter The URL path of the partner

(initiator) where the incoming AS2
messages shall be received>
AS2DispatcherServlet_<User-ID>_V4
Message Expected Message ID left Specifies the left part of the incoming AS2
MessageID. Recommended : ”.*”
Expected Message ID right Specifies the right part of the incoming AS2
Message ID.
Recommended : ”.*”
Expected sender‟s AS2Name <Enter the AS2 identifier >
testas2
38

Expected own AS2 name The email address which is transmitted in
the AS2 message as sender.
AS2_<SID>_<User-ID>_Var04

The message subject which is transmitted
in the AS2 message as sender.
.*

Charset
 Source encoding <Enter the type of incoming message
encoding> UTF-8
<Enter the type of outgoing message
 Destination encoding encoding > UTF-8
QoS Exactly once
Signature Verify Signature Unchecked
Decryption Decrypt message Uncheck the decrypt message box
MDN
Message Delivery Notification Check the sign MDN
View to own public key certificate <Enter storage name of public key certificate >
The NWA key-storage view in the sending

partner (SAP PI –initiator), which contains the
AS2_CERTIFICATE / PI_Test-cert
The alias (or name) under which the self (own)

public key certificate is stored
AS2_CERTIFICATE / PI_Test-cert
View to own private key significance same as receiver channel
39
configuration
Alias of own private significance same as receiver channel

configuration
Send options Immediate
Override URL for MDN Checked
Async MDN URL http://host:port/AsyncMDN.aspx
Basic HTTP Authentication Checked

Username <User ID for login the system where message will
be received>
Password
<Password for login the system where message will
be received>
Proxy server Unchecked
7. Select the template XiPatternChannel_FileReceiver of software component version
B2BTOOLKIT 1.0 and press OK. Change to the channel view.
9. As File Name output.txt should be set.
10. Go to the Module tab and Add Odette converter “localejbs/OdetteConverterModule”.
For adding the converter module bean, click on the Add button. Move the converter module bean to
the first step by clicking on the Move Up button which is present at the right hand side. The final
screen should look like as given below:
40

2. On “AS2 Identifier”, type: AS2_<SID>_<User-ID>_Var04
http://host:port/AS2/AS2DispatcherServlet_<User-ID>_V4
URL-Path)

Incoming Message Require Signature Unchecked

Security Require encryption Unchecked
Compression Compress Outgoing Data checked


Request MDN Receipt checked
Security Signed / Unsigned signed


Encryption

Signature
41
1 Go to the corresponding folder of the trading partner you just created.

e.g. \\host\as2data\AS2_<SID>_<User-ID>_Var04\Outgoing
2 Copy the file “B2B_Odette.xml” into the “Outgoing” folder.
has been used for sending the message . Third party can vary in your case . For the configuration of third
1. Start the sender and receiver channels before sending the message from third party software.
2. Go to http://host:port/Default.aspx and navigate to the Outcoming tab.
3. Select the trading partner “SAPPI_<SID>_<User-ID>_04”. The tab content shows the messages
present at the trading partner location.
4. Click on the send button.(Input file you can get from the directory Inputfiles)
5. On the host of the Advanced Adapter Engine Extended, open the file directory Receiver.
6. Example: \\host\<selected-path>\AS2\Receiver.
7. Verify the contents of the file –“output.txt” at the file target directory.
8. Go to file structure of the server where the third party is installed
http://host:port/Default.aspx?a=Outgoing and select the trading partner “SAPPI_<SID>_<User-
ID>_04”. The tab content shows the successfully sent messages in the “Sent Files” tab. Also the
“Logs” tab shows the logs of the outgoing messages (successful transmissions and errors if any) and
the MDN.
9. In the “Logs” tab open the “Request” link for the recently executed message. The Receipt-delivery-
option should be the same URL as given in the configuration (Async MDN URL).
10. Open the received file and compare with the file sent. The received message should be in Odette
format and the content of the file should be same.
message monitoring. To do this, proceed as given in variant1.
In the processing log you can see there will not be any kind of decryption and signing of the message as you
have not chosen these features in the scenario.
8 Variant 4b: AS2 Adapter – Duplicate message handling Feature in AS2
The feature tested here for AS2 adapter is the duplicate message handling feature in the sender channel.
The variant involves the feature to avoid/control the processing of duplicate messages using AS2 Sender
Channel. It also provides flexible threshold configuration and channel stops (if threshold exceeds) options.
The message flow will start from the file adapter.
 Integration Flow 1: Sender: File Adapter, Receiver: AS2 Adapter.
42
The message is sent from the file adapter and AS2 adapter receives the message and sends it to a
receiver communication channel .
 Integration Flow 2: Sender: AS2 Adapter , Receiver: File adapter
The message received at the AS2 sender will be sent again to the file adapter (receiver).



2. In category Enterprise Integration Patterns select the Point-to-Point Pattern and set the name
and ID of the Integration Flow as AS2_DuplicateCheck1_Integration_FlowScenario.
3. Choose Next.
4. As Sender Business component select the Business component
6. In Tab Receiver Systems as Receiver Component select the Business Component.
7. As Receiver Interface select XiPatternInterface1.
8. Choose Finish.
Template. The Channel Template screen will open.
Example: ../../../../SYS/global/Connectivity_Test/B2B/AS2/Inputfiles.
4. As File Name input.txt should be set.
and then name the channel, as in this case named it as B2B_DuplicateCheck_AS2_Rec
7. Go to Adapter-Specific tab and under General tab fill the details as given below in the table
43
Header
Field Name Value
Field
Recipient Recipient URL https://<host:port>/AS2/AS2DispatcherServlet/DuplicateCheck/
Basic Authentication Checked
 Username <User ID for login the system where message will be

received>
 Password <Password for login the system where message will be

received>
Message Filename <Enter the file name>

Duplicate
MessageID left 12345

MessageID right 54321

Own AS2Name
e.g. duplicateSender
<Enter the AS2 Name of the Recipient >

Recipient AS2 Name
AS2 name which is transmitted in the AS2 as AS2-
To-Parameter
e.g. duplicateReceiver
Own email- address <Enter the email address >

The email address which is transmitted in the AS2
message as sender.
e.g. duplicate@as2.com
Message subject <Enter the subject of the message>

The message subject which is transmitted in the AS2
message as sender.
e.g. duplicateTest
Content-Type <Enter the type of the content>
Content type with which the message is marked.

e.g application/edi-x12
44
Algorithm SHA 224 (Algorithm used to sign

the message)
View to own public key certificate <Enter storage name of public

key certificate >
The NWA key-storage view in

the sending partner (SAP PI -
initiator), which contains the
e.g. AS2_CERTIFICATE /
PI_Test-cert for both (view and
alias)
The alias (or name) under

which the self (own) public key
certificate is stored
See above
View to own private key <Enter the key storage name of

private key>
The NWA key-storage view in
the sending partner (SAP PI -
initiator), which contains the
self (own) private key
e.g. AS2_KEYSTORE / PI_Test
for both (view and alias)
Alias of own private key <Enter the name of the private

key>
The alias (or name) under which
the self (own) private key is stored
see above
9. Navigate to the tab MDN Tab and fill the details as given in the table below
45
MDN
Message Delivery Notification Select Synchronous
Verify MIC Checked
Request Signing Checked
Algorithm SHA 224
Verify Signature Checked

certificate
The NWA key-storage view in the sending partner
(SAP PI- initiator), which contains the receiving
partner‟s (responder) public key certificate

certificate The alias (or name) under which the receiving
partner‟s (responder) public key certificate is stored

of the Integration Flow as AS2_DuplicateCheck2_Integration_FlowScenario.
12. Choose Next.
13. As Sender Business component select the Business component
15. In Tab Receiver Systems as Receiver component select the Business
component<SID>_<UserID>_B2B_BC_AS2_V4 using the input help for the Receiver Name.
16. As Receiver Interface XiPatternInterface2 .
17. Choose Finish.
46
The channel view screen will open. Name the sender channel as
B2B_DuplicateCheck2_AS2Sender.
Server Expected URL-Path AS2DispatcherServlet/DuplicateCheck/
Message Expected Message ID left 12345
Expected Message ID right 54321
Expected sender‟s AS2Name <Enter the AS2 identifier >
duplicateSender

Expected own AS2 name duplicateReceiver

duplicateTest
UnChecked
Charset Charset conversion
Duplicate Handling Enable Duplicate Handling Checked
Duplicate Message Threshold 1
Disable channel if threshold Checked

exceeded
Time period for Duplicate 1

check
Time period for duplicate Day

Check
QoS Exactly once
47
Signature Verify Signature Unchecked
12. Navigate to the tab MDN and fill the details as given below:
HEADER FIELD VALUE
Signature Unchecked
Override URL for MDN Unchecked

Basic HTTP Unchecked
Authentication
Proxyserver Unchecked
14. Select the template XiPatternChannel_FileReceiver of software component version SAP
BASIS 7.31 and press OK. Change to the channel view.
16. As File Name output.txt should be set.
8.8 Execution and Verification
1. Start all the four channels consumed in the above created integration flows.
2. As in AS2 sender channel you have enabled duplicate handling with threshold level 1. Only one
message will be processed and flowing sucessfully in all four different channels. When the
second message comes, the AS2 sender channel should throw an error and AS2 sender channel
should go to stop status as you have also checked the box Disable channel if threshold exceeds.
3. For running the scenario again, start the AS2 sender channel manually in the channel monitoring
and execute the scenario.
4. In the configuration we have set Time period for duplicate check as 1 Hour. The duplicacy of the
message should be checked for 1 hour and after that the duplicacy will not be identified and
channels will allow processing the duplicate message as well.
5. In the channel monitoring you should be able to see the message and MDN is signed by the
algorithm SHA 224.
48
9 Variant 5: AS2, EDI Separator (ANSI X12 transaction sets 830, 856, 997) and EDI-
XML Converter
On this variant, the AS2 adapter is used in combination with the EDI Separator (adapter) and the EDI_XML
Converter (module).
The message flow starts as an ASC X12 message containing two message types (transaction sets):
 Material Planning Schedule – 830
 Shipment Notice – 856
The EDI separator splits the message into each transaction set, which are converted into XML by the
X12Converter Module at each of the EDI Separator sender channels and sent to a receiver file adapter,
respectively.
Additionally an acknowledgment message (transaction code 997) is generated by the EDI Separator after
splitting, validating (optional) and dispatching the individual messages and sent back to the trading partner
(AS2 connector) via AS2 adapter. The 997 message generation by the EDI Separator channel can be tested
using the various configurable parameters available and the validation feature provided by the
X12ConverterModule of the EDI-XML Converter Module.
The configurable options for 997 message generation are:

 Acknowledgment required or not
 997 message in the transaction mode-"All”(global at parent message level) or transaction mode
“Individual”(local per message)
 Positive Acknowledgment not required option for “All” transaction mode
 Negative Acknowledgment not required option for “All” transaction mode
 Partially accepted (P) acknowledgement code for “Individual” transaction mode
 Execution modes:
 997 message for receipt and dispatch of messages only
 997 message for receipt and validation of individual messages
Note:
 Executing in Transaction Mode “All” means that even if a single message in the bulk parent message
fails (due to errors in configuration, dispatch, validation, etc), the entire transaction will be rolled back
with all the individual messages rejected (R).
 Executing in Transaction mode “Individual” means that, if one or more messages in the bulk parent
message fails (due to errors in configuration, dispatch, validation, etc), only those failed messages
will be rejected (R) while the successful messages will be accepted (A).
The General structure of the 997 Acknowledgment message is
ISA (Interchange Control header)

GS (Group segment header)
ST (Transaction set header)
AK1 -> Functional Group Response Header
AK2-> Transaction Set Response Header
AK3 -> Data Segment Note
AK4 -> Data Element Note
AK5 -> Transaction Set Response Trailer
AK9 -> Functional Group Response Trailer
SE (Transaction set trailer)
49
GE (Group trailer)
IEA (Interchange control trailer)
Four Integration Flows are configured in this variant:
 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator.

The message is sent with AS2 protocol from a partner to the PI. A sender Communication Channel
with AS2 adapter receives the message and sends it to a receiver communication channel with
Adapter type EDI Separator.
 Integration Flow 2: Sender: EDI Separator & EDI-XML Converter module, Receiver: File adapter
Transaction Set Identifier code: 830
The transaction set 830 is converted into XML on the sender side and sent to the file adapter
(receiver).
Transaction Set Identifier code: 856
The transaction set 856 is converted into XML on the sender side and sent to the file adapter
(receiver).
 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter
Transaction Set Identifier Code: 997 and sent back to the third party software (AS2 connector).
9.1 Configuring the Integration Flows
9.1.1 Calling the Process Integration Designer

If not done yet, open the SAP NetWeaver Developer Studio, connect to the systems and open the SAP
Process Integration Designer perspective as described on the Prerequisites section.
9.1.2 Creating the integration Flows
9.1.2.1 Integration Flow 1: Sender: AS2 Adapter, Receiver: EDI Separator.
1. On the PI Explorer View, select “New Integration Flow” form the context menu (right click) or from
the toolbar menu (top-left) as shown in the screenshot below
50
2. On the Name field type “AS2_EDISep_R1_<User-ID>”, select “Point-to-Point Channel” and click on
“Next”
3. To Assign the business component to sender, right click on the sender -> Click on the New Business
component and give the name as Business Component <SID>_<User-
ID>_B2B_BC_AS2_EDISEP_V5_01 -> Click Finish.
4. Click on the Browse button for the field Interface and select the service interface
“XiPatternInterface1”, software component SAP BASIS 7.31
5. Select the “Receiver Systems” tab
6. Click on the field located on the column “Communication Components”, a browse button will appear
on the right side of the field, click on it and select the Business Component <SID>_<User-
ID>_B2B_BC_AS2_EDISEP_V5_01
7. Following the same procedure, select the service interface “XiPatternInterface1”, software
component SAP BASIS 7.31 on the field located under column “Interface”
8. Click on button “Finish”
Following the same steps for Integration Flow1, create the second Integration Flow with the following data:
Integration Flow Name AS2_EDISep_S1_<User-ID>
Sender Communication Component <SID>_<User-ID>_B2B_BC_AS2_EDISEP_V5_02
Sender Service Interface “XiPatternInterface1”, software component SAP BASIS 7.31
Receiver Communication Component <SID>_<User-ID>_B2B_BC_AS2_EDISEP_V5_02
Following the same steps for Integration Flow 1, create the third Integration Flow with the following data:
51
9.1.2.4 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter
Following the same steps for Integration Flow 1, create the fourth Integration Flow with the following data:
9.1.3 Configuring the integration Flows
In the following steps, you configure the first Integration Flow using AS2 adapter as sender and EDI
separator as receiver.
Configuring the AS2 adapter on the sender communication channel
1. Open the Integration Flow “AS2_EDISep_R1_<User-ID>”

2. In the graphical editor, right click on the channel for the sender component and select configure
channel (please see screenshot below)
3. As adapter type, select AS2 (Software Component B2B Toolkit 1.0)

4. On the field Channel Name type: AS2_sender
5. Select tab “Adapter-Specific”. Under sub-tab “General” provide the following configuration values:
52
Server Expected URL-Path AS2DispatcherServlet_<User-ID>_R1
Message Expected Message ID left <Specifies the left part of the incoming AS2
MessageID>
This is a regular expression. For more

information on regular expressions you can refer
to the following link: Regular expression
Patterns>
Type without the quotes:

”.*”
<Specifies the right part of the incoming AS2

Expected Message ID right Message ID>
”.*“
<aka Organization name on AS2 connector>

Expected sender‟s AS2Name
testas2
Expected own AS2 name <AS2 Identifier>
AS2_<SID>_<User-ID>_Var05_Outbound_PO_SE
Expected subject “.*”
Charset Charset conversion Checked

 Source encoding ISO-8859-1
Message Set dynamic parameter Checked

configuration Quality of Service Exactly Once (asynchronous)
Archiving Archive Messages Unchecked
Adapter Adapter Status Active

Status
53
6. Select sub-tab “Signature and Encryption” and provide the following configuration values:
View to sender‟s public key <The NWA key-storage view containing the
certificate sending partner‟s public key certificate and alias
(or name) under which the sending partner‟s
Alias of sender‟s public key public key certificate is stored.>
certificate
Use the browse button to select both, View and
Alias, and click OK
Select Keystore: AS2_CERTIFICATE /

Keystore Entry: Partner_Test-cert for both (view
and alias)
Decryption Decrypt Checked
View to own private key <, the NWA key-storage view containing self (own)
Alias of own private key private key and alias (or name) under which the self-
private key is stored >
Alias, and click OK
Select AS2_KEYSTORE / PI_Test for both (view and

alias)
7. Select sub-tab “MDN” and provide the following configuration values:
Message Sign MDN Unchecked

Disposition
Notification
Configuring the EDI Separator on the receiver communication channel
1. In the graphical editor, right click on the channel for the receiver component and select “configure
channel”
2. As adapter type, select EDI Separator (Software Component B2B Toolkit 1.0)
3. On the field Channel Name type: EDISep_rec
4. Select tab “Adapter-Specific”. Under tab “General” provide the following configuration values
Formatting Indent messages Checked

Status
54
5. Under tab “ANSI X12”, enter the following configuration values
997 Acknowledgement Required Required (by Default ”Not Required”)

Acknowledgements
Transaction Mode All
Negative Acknowledgement Unchecked

not Required
Positive Acknowledgement Unchecked

not Required
Execution Mode Receipt Only
6. Save the integration Flow
Configuring the EDI Separator adapter on the sender communication channel
1. Open the Integration Flow “AS2_EDISep_S1_<User-ID>”

channel
3. As adapter type, select EDI Separator (Software Component B2B Toolkit 1.0), for transport protocol,
select “PI” and for Message protocol, select “ANSI X.12”
4. On the field Channel Name type: EDISep_send1
Filter Version /Release/Industry All versions

Identifier Code
Transaction Set Identifier 830

Code
<The value in the ISA segment of the incoming

Interchange Sender ID: message in the sender ID field (ISA06) identifying the
sender (Partner 1)>
87654321
Interchange Receiver ID: <The value in the ISA segment of the outgoing
message in the receiver ID field (ISA08)identifying the
receiver (Partner 2)>
12345678
55
Encoding Charset encoding UTF-8
QoS Quality of Service Exactly Once (asynchronous)

Status
6. Select tab “Modules”

7. Add the Converter module to convert from X12 to XML, to do this, please click on “Add” on the first
table (Processing sequence) and type the following values:
Category Parameter name Value
Processing Module Name Localejbs/GenericConverterModule

sequence
Type Local Enterprise Bean
Module Key 1
8. Move to the position number 1 the module you just added by selecting the row and using the “Move
Up” button
Configuring the File Adapter on the receiver communication channel
1. In the graphical editor, right click on the channel for the receiver component and select “Apply
Channel Template”
2. Select “XiPatternChannel_FileReceiver”, software component “SAP BASIS 7.31” and click “OK”
3. In the graphical editor, right click on the channel and select “configure channel”
4. On the field Channel Name type: File_rec1
5. Go to the tab “Adapter-Specific” and adjust the following values:
File Access Target Directory: <the path to the output folder on the server>
Parameters
e.g. \\host\<selected-path>\AS2-EDISEP\830
Create Target Directory: Checked
File Name Scheme Output-830.xml
Configuring the EDISeparator adapter on the sender communication channel
56
channel
3. As adapter type, select EDISeparator (Software Component B2B Toolkit 1.0), for transport protocol,
Filter Version /Release/Industry Select :

Identifier Code « 003060 Draft Standards Approved for
Publication by ASC X12 Procedures »

Code

sender (Partner 1)>
87654321
12345678

Status

7. Add the Converter module, to do this, please click on “Add” on the first table (Processing sequence)
and type the following values:

sequence
Module Key 1
57
Up” button
Channel Template”
Parameters
e.g. \\host\<selected-path>\AS2-EDISEP\856

2. In the graphical editor, right click on the channel for the sender component and select “Configure
Channel”
Filter Version /Release/Industry All versions

Identifier Code

Code

sender (Partner 1)>
12345678
58
87654321

Status
6. No conversion module is configured
Configuring the AS2 Adapter on the receiver communication channel
1. In the graphical editor, right click on the channel for the receiver component and select “Configure
Channel”
2. As adapter type, select AS2 (Software Component B2B Toolkit 1.0), for transport protocol, select
“Hypertext Transfer Protocol” and for Message protocol, select “AS2”
3. On the field Channel Name type: as2_rec
4. Select tab “Adapter-Specific”. Under tab “General” provide the following configuration values:
Recipient Recipient URL <Enter The URL path of the partner (initiator)
where the AS2 messages shall be received>
http://host:port/Receiver.aspx

Username <User ID for login the system where message will be
Password received>
<Password for login the system where message

will be received>
Message Filename AS2-EDISEP-997.txt
Message ID left Type the following regular expression for both:

Message ID right .*
Use compatible MessageId Unchecked
Own AS2 Name <AS2 Identifier>
59
Recipient‟s AS2Name <aka Organization name on AS2 connector>
testas2
Own email-address < Specifies the email address which is

transmitted in the AS2 message as sender >
<User-ID>@mailhost.com
Message subject < Specifies the subject included in the

message>
AS2-EDISEP-997
Content type application/edi-x12

 Destination encoding ISO-8859-1
Dynamic Respect parameter Checked

configuration

Status
Compression Compress message Unchecked
Signature Sign message Checked
View to own public key < The NWA key-storage view in the sending
certificate partner, which contains the self (own) public key
Alias of own public key certificate and the alias (or name) under which
certificate the self (own) public key certificate is stored.
Use browse button to select it>
Select: AS2_CERTIFICATE / PI_Test-cert for

View to own private key < The NWA key-storage view in the sending partner,
Alias of own private key which contains the self (own) private key >
Select AS2_KEYSTORE / PI_Test for both

(view and alias)
60
Encrypt Encrypt message Checked
Algorithm 3DES
View to recipients public key AS2_CERTIFICATE / Partner_Test-cert

Alias of recipients certificate
MDN MessageDeliveryNotification Synchronous
Verify MIC checked

Request signing checked
Verify signature checked
View to signer‟s public key <The NWA key-storage view in the sending partner
certificate (SAP PI- initiator), which contains the receiving
partner‟s (responder) public key certificate and the
Alias of signer‟s public key alias (or name) under which the receiving partner‟s
certificate (responder) public key certificate is stored >
1. Open the URL of the AS2 connector http://host:port/Default.aspx

2. Navigate to the tab “Trading Partner”
3. Click on “Add New”
4. On “Select partner type” select “AS2”
6. On “AS2 Identifier”, type: AS2_<SID>_<User-ID>_Var05_Outbound_PO_SE
http://host:port/AS2/AS2DispatcherServlet_<User-ID>_R1
URL-Path)
Outgoing Message Sign Outgoing Data checked

Security Encrypt Outgoing Data checked
Incoming Message Require Signature checked

Compression Compress Outgoing Data checked
61

Request MDN Receipt checked


Encryption

Signature


\\host\as2data\AS2_<SID>_<User-ID>_Var05_Outbound_PO_SE\Outgoing
2. Copy the file “B2B_ansix12SenderMessage_830_856.txt” into the “Outgoing” folder and create two
or more copies of it.
3. Also, Copy the file “B2B_ansix12SenderMessage_830_856_error.txt” with validation errors in the

856 transaction set into the “Outgoing” folder and create two or more copies of it.
In this variant the third party AS2 Connector from /n software has been used for sending the message. Third
party can vary in your case. For the configuration of this third party software please refer the section ‎2.2.3.
1. Check that all sender and receiver channels are started before sending the message from third party
software.
2. Go to AS2 Connector (AS2 connector http://host:port/Default.aspx )and navigate to the “Outcoming”
tab.
62
3. Select the trading partner‟s organization name (SAPPI_<SID>_<User-ID>_05). The table “Outgoing
files” shows the available test files present at the trading partner location. If there isn‟t any, place the
test files.
4. Click on the send button for the test file “B2B_ansix12SenderMessage_830_856.txt”.

5. After some seconds the message “transmission successful” should be displayed.
6. On the host of the Advanced Adapter Engine Extended, open the file directories 830 and 856 (e.g.
\\host\<Selected-path>\AS2-EDISEP\856 ) respectively. There should be an XML version of the input
file for each transaction set 830 and 856, respectively.
7. On the AS2 connector, go to the “Incoming” tab
8. Select the trading partner identifier (e.g. “SAPPI_<SID>_06”).
9. A table with all incoming files for this identifier is displayed. There should be a recent message called
“AS2-EDISEP-997” which is the MDN (acknowledgement)
10. Click on “View” to see the file contents. The file contains an ANSI X.12 acknowledgment.
63
Verification for the 997 Acknowledgement generated:
1. Open the ANSI X12 997 file “AS2-EDISEP-997”.
2. Check the ISA segment to identify the Sender Interchange ID and Receiver Interchange ID (ISA06
and ISA08) to be the same as 87654321 and 12345678 respectively.
3. There should be two functional group GS segment loops one for each 830 and 856 transaction sets.
The Functional Group Header Segment (GS) is used to start the envelope for the Functional
Acknowledgment Transaction Sets.
4. The AK2 segment should identify the transaction set code (830 and 856) for each transaction set at
AK201.
The AK2 segments appear in the same order as the transaction sets in the functional group that has
been received and is acknowledged. In this case the AK2 segment for 830 appears first.
5. The AK5 and AK9 segment for both 830 and 856 should indicate “A” as the transaction set and the
functional group has been accepted.
Note:
The ANSI X.12 message used for testing has the code 00360, If a different code is used on the filter
parameter “Version/Release/Industry Identifier Code” (on Adapter-Specific tab of the Sender
Communication Channel using the EDISeparator) the filtering will not be successful and no
message will be processed.
Now repeat the steps 1-10 of the Execution section 9.4 with the test file
“B2B_ansix12SenderMessage_830_856_error.txt” and verify the 997 generated as follows:
Verification for the 997 Acknowledgement generated:
1. Open the ANSI X12 997 file “AS2-EDISEP-997”.
2. Check the ISA segment to identify the Sender Interchange ID and Receiver Interchange ID
(ISA06 and ISA08) to be the same as 87654321 and 12345678 respectively.
3. There should be two functional group GS segment loops one for each 830 and 856 transaction
sets.
The Functional Group Header Segment (GS) is used to start the envelope for the Functional
Acknowledgment Transaction Sets.
4. The AK2 segment should identify the transaction set code (830 and 856) for each transaction set
at AK201.
The AK2 segments appear in the same order as the transaction sets in the functional group that
has been received and is acknowledged. In this case the AK2 segment for 830 appears first.
5. The AK5 and AK9 segment for both 830 and 856 should indicate “A” as the transaction sets and
the functional groups has been accepted.
On the Receiver EDI Separator, the generation of acknowledgement was configured according to
section 9.1.3.1.
Additionally you have various configuration options to test the feature of the generation of 997
Acknowledgement:
64
Case Positive Exclude Execution Exclude

Negative
Acknowled Partially Mode AK3 and
Acknowled Acknowled
Transaction gement not Accepted AK4
gement gement
Mode Required Acknowled
Required not
gement
Required
code
1 Not NA NA NA NA NA NA
Required
2 Required All Checked Unchecked NA Receipt Only NA
3 Required All Unchecked Checked NA Receipt Only NA
4 Required All Checked Checked NA Receipt Only NA
5 Required All Unchecked Checked NA Receipt & Unchecked

Validation
6 Required All Unchecked Checked NA Receipt & Checked

Validation
7 Required All Checked Checked NA Receipt & Checked

Validation
8 Required Individual NA NA Unchecked Receipt only NA
9 Required Individual NA NA Checked Receipt only NA
10 Required Individual NA NA Unchecked Receipt & Unchecked

Validation
11 Required Individual NA NA Checked Receipt & Checked

Validation
 Case 1:
Execution:
1. Execute the steps 1-5 of section 9.4 with the test file
“B2B_ansix12SenderMessage_830_856_error.txt”
Verification of the 997 Acknowledgement generated:

1. No 997 Acknowledgement should be generated.
 Case 2:
Execution:
1. In the Integration flow “AS2_EDISep_S1_<User-ID>” change the configurable parameter value for
eg, for the Sender Interchange ID to 765432.
65
3. There should be no messages generated for 830 or 856 transaction sets as the entire transaction is
rolled back due to error in configuration.

 Case 3:
Execution:
1. Revert the changes done to the Integration flow “AS2_EDISep_S1_<User-ID>” in Case 2.

 Case 4:
Execution:

 Case 5:
Execution:
rolled back due to validation error in the 856 transaction set.

1. 997 Acknowledgement should be generated.
AK201. In this case the AK2 segment for 830 appears first.
5. The AK5 and AK9 segment for both 830 and 856 should indicate “R” as the transaction sets and the
functional groups has been Rejected due to validation error in the transaction set 856.
6. The AK3 and AK4 segments should be displayed for the 856 transaction set reporting errors in the
data segment and data element and indicating the location of the error. In this case for the
66
transaction set 856 AK3 identifies “BSN” as the segment with error code “8”, AK4 identifies the
numerical count of the data element in error “2”.
 Case 6:
Execution:

5. The AK5 and AK9 segment for both 830 and 856 should indicate “R” as the transaction sets and the
functional groups has been Rejected due to validation error in the transaction set 856.
6. There should not be any AK3 and AK4 segments.
 Case 7:
Execution:
3. The EDI Separator Receiver channel EDISep_rec in the Integration flow “AS2_EDISep_R1_<User-
ID>” should be in error state indicating that the messages are not dispatched due to validation errors
in transaction set 856.

 Case 8:
Execution:

67
5. The AK5 and AK9 segment for both 830 and 856 should indicate “A” as the transaction sets and the
functional groups have been Accepted.
 Case 9:
Execution:

5. The AK5 and AK9 segment for both 830 and 856 should indicate “A” as the transaction sets and the
functional groups have been Accepted.
 Case 10:
Execution:
file for transaction set 830 but no file for transaction set 856 indicating it has not been dispatched.

5. The AK5 and AK9 segment for transaction set 830 should indicate “A” as the transaction set and the
functional group have been Accepted.
68
6. For the transaction set 856, the AK5 segment should indicate “R” as the transaction set has been
Rejected and the AK9 segment should indicate “P” (Partially accepted) as there is at least one
transaction set in the functional group which is rejected.
7. The AK3 and AK4 segments should be displayed for the 856 transaction set reporting errors in the
data segment and data element and indicating the location of the error. In this case for the
transaction set 856 AK3 identifies “BSN” as the segment with error code “8”, AK4 identifies the
numerical count of the data element in error “2”.
 Case 11:
Execution:
file for transaction set 830 but no file for transaction set 856 indicating it has not been dispatched.

5. The AK5 and AK9 segment for transaction set 830 should indicate “A” as the transaction set and the
functional group have been Accepted.
6. For the transaction set 856, the AK5 and AK9 segment should indicate “R” as the transaction sets
and the functional group have been Rejected.
7. There should be no AK3 and AK4 segments.

.
With a Negative 997 Acknowledgement, the user is able to edit the message (transaction set) with error and
Resend the message.
You can also monitor the relation between the EDI parent message and child messages (of type 830 and
856) after their split.
1. To do so, in Message Monitoring, search for the child message (of type 830 and 856) by selecting
the appropriate radio button and then go to Message log tab.
2. The tab Message log and Message Details for the child messages (of type 830 and 856) displays the
correlation between the child messages and the parent message.
3. In the Message Details tab check for the Reference ID label which refers to the Message ID of the
Parent EDI message.
69
4. Also check for the message “Message was split from an Ansi X. 12 message with ID <Message ID of
the parent EDI message>” in the Message log.
10 Variant 6: AS2, EDI Separator (ANSI X12 transaction sets 830, 856, 997), EDI-XML
Converter & Conversion Using the Maintenance Tool
On this variant we modify the scenario in variant 5 by adding the module converter to one of the file receivers
and afterwards we use the maintenance tool to convert one of the received messages to xml and back to
X.12.
One of the Integration Flows from variant 5 will be modified:
Transaction Set Identifier code: 856. The transaction set 856 is converted into XML on the sender
side and sent to the file adapter. The receiver file adapter uses the converter module once again and
the message is converted back to ANSI X.12 and saved on the output folder.
10.1.1 Integration Flow 3: Sender: EDI Separator & EDI-XML Converter module, Receiver: File
adapter

Channel”

sequence
Module Key 1
Up” button
6. Save the integration Flow. The rest of the configuration remains intact.
70
1. Proceed as in variant 5.
2. On the host of the Advanced Adapter Engine Extended, open the file directory 856 (e.g.
\\host\<selected-path>\AS2-EDISEP\856 ). There should be the transaction set 856 in ANSI X.12
form. Please keep this file since we will use it for conversion on the EDI Content Manager
maintenance tool
3. Open the EDI Content Manager Maintenance tool via URL for B2B Integration Cockpit:
https://host:port/webdynpro/resources/sap.com/b2b~home/B2BHome -> EDI Content Manager.
4. Go to the Ansi X.12 tab and select “Ansi X.12-XML Converter” → “Ansi X.12 to XML”
5. On the text input box “Convert Ansi.X12 to XML”, insert the content of the file received on step 2,
overwriting the text “Insert Ansi X.12” Alternatively you can perform a file import using the Browse
button, selecting the file and clicking on “import”
6. Click on “Convert”
7. The conversion is performed and a confirmation message is shown (e.g. Converted in 400
milliseconds), the converted message is displayed (in XML).
8. Copy the converted message to the clipboard
9. On the same Ansi X.12 tab, select “Ansi X.12-XML Converter” → “XML to Ansi X.12”
10. Paste the XML message from your clipboard on the text input box and proceed with the conversion
to Ansi X.12
11. Compare the converted message to the original one on the 856 folder, they should be similar.
2. The tab Message log and Message Details for the child messages (of type 830 and 856) displays the
correlation between the child messages and the parent message.
Parent EDI message.
4. Also check for the message “Message was split from an Ansi X. 12 message with ID <Message ID of
11 Variant 7: AS2, EDI Separator (EDIFACT: DELFOR and DESADV) and EDI-XML
Converter
On this variant, an EDIFACT multi-message containing two message types (DELFOR and DESADV) is sent
by a trading partner. The message is split by the EDI Separator, converted into XML and sent to a file
receiver.
Additionally an acknowledgment message (Message Type CONTRL) is generated by the EDI Separator
(after splitting, validating (optional) and dispatching the individual messages) and sent back to the trading
partner (AS2 connector) via AS2 adapter. The CONTRL message generation by the EDI Separator receiver
channel can be tested using the various configurable parameters available.
The configurable options for CONTRL message generation are:

 Acknowledgment required or not
 EDIFACT CONTRL Message Version and Release
 CONTRL message in the transaction mode-"All”(global at parent message level) or transaction
mode “Individual”(local per message)
 Positive Acknowledgment not required option for “All” transaction mode
 Negative Acknowledgment not required option for “All” transaction mode
 Execution modes:
71
 CONTRL Acknowledgement for receipt and dispatch of messages only

 CONTRL Acknowledgement for receipt and validation of individual messages
Note:
Executing in Transaction Mode “All” means that even if a single message in the bulk parent
message fails (due to errors in configuration, dispatch, validation, etc), the entire transaction
will be rolled back with all the individual messages rejected (4).
Executing in Transaction mode “Individual” means that, if one or more messages in the bulk
parent message fails (due to errors in configuration, dispatch, validation, etc), only those failed
messages will be rejected (4) while the successful messages will be accepted/acknowledged
(7). In case all the messages in a group fail, the UCI and UCF segment will be
accepted/acknowledged (7).
The General structure of the CONTRL Acknowledgment message is
UNA (Service String Advice)

UNB (Interchange Header)
UNG (Functional Group Header)
UNH -> Message Header
UCI -> Interchange Response
UCF -> Functional Group Response
UCM -> Message Response
UCS -> Segment Error Indication
UCD -> Data Element Error Indication
UNT -> Message Trailer
UNE (Functional Group Trailer)
UNZ (Interchange trailer)
Four Integration Flows are configured in this variant:

Message Type: DESADV, Message Version Number: D, Message Release Number: 96A
Message Type: DELFOR, Message Version Number: D, Message Release Number: 96A
 Integration Flow 4: Sender: EDI Separator, Receiver: AS2 adapter
Message Type: CONTRL, Message Version Number: D, Message Release Number: 3
72

2. On the Name field type “AS2_EDISep_var7_R1_<User-ID>”, select “Point-to-Point Channel” and

click on “Next”
3. To Assign the business component to sender, right click on the sender-> click on New Business
component select the Business Component name as <SID>_<User-
73
Integration Flow Name AS2_EDISep_var7_S1_<User-ID>
74
1. Open the Integration Flow “AS2_EDISep_var7_R1_<User-ID>”


Server Expected URL-Path AS2DispatcherServlet_<User-ID>_var7
MessageID. This is a regular expression. For
more information on regular expressions you
can refer to the following link: Regular
expression Patterns>
”.*”

”.*“

75
testas2



Status
certificate
Alias, and click OK

and alias)
Alias, and click OK

alias)
7.
76

Disposition
Notification
channel”
Formatting Indent messages Checked

Status
5. Under tab “EDIFACT”, enter the following configuration values
Syntax and Service Acknowledgement Required Required (by Default ”Not Required”)
report message
(CONTRL)
EDIFACT CONTRL Message Version D, Release 3
Version and Release
Transaction Mode All
Negative Acknowledgement Unchecked

not Required
Positive Acknowledgement Unchecked

not Required
Execution Mode Receipt Only
UNA Segment Required Unchecked
77
1. Open the Integration Flow “AS2_EDISep_var7_S1_<User-ID>”

channel
select “PI” and for Message protocol, select “EDIFACT”
Filter Message Type Select „DESADV’
Message Version Number Select „D‟
Message Release Number: Select „96A’
Interchange Sender 1234567

Identification
Interchange Sender Select „ZZZ‟

Identification Code Qualifier
Interchange Recipient 7654321

Identification
Interchange Recipient Select „ZZZ‟

Encoding Character encoding Select „ISO-8859-15‟

Status

Processing Module Name localejbs/GenericConverterModule

sequence
Module Key 1
78
Up” button
Channel Template”
Parameters
e.g. \\host\<selected-path>\AS2-EDISEP\output-
edifact
File Name Scheme Output-DESADV.xml

channel
select “PI” and for Message protocol, select “EDIFACT”
Filter Message Type Select „DELFOR’
Message Release Number Select „96A‟
Interchange Sender 1234567

Identification
79
Interchange Sender Select „ZZZ’

Interchange Recipient 7654321

Identification
Interchange Recipient Select „ZZZ’

Encoding Character encoding Select „ISO-8859-15’

Status
Channel Template”
Parameters
edifact
File Name Scheme Output-DELFOR.xml


sequence
Module Key 1
80
Up” button

2. In the graphical editor, right click on the channel for the sender component and select “Configure
Channel”
select “PI” and for Message protocol, select “Edifact”
Filter Message Type Select 'CONTRL‟
Message Release number Select „3‟
7654321
Interchange Sender ID:
Interchange Sender Select „ZZZ’

Interchange Receiver ID: 1234567
Interchange Reciever Select „ZZZ’

Encoding Charset encoding Select „ISO-8859-15’

Status
6. No conversion module is configured
81
Configuring the AS2 Adapter on the receiver communication channel
Channel”
2. As adapter type, select AS2 (Software Component B2B Toolkit 1.0), for transport protocol, select
“Hypertext Transfer Protocol” and for Message protocol, select “AS2”
3. On the field Channel Name type: as2_rec
4. Select tab “Adapter-Specific”. Under tab “General” provide the following configuration values:
Recipient Recipient URL <Enter The URL path of the partner (initiator)
where the AS2 messages shall be received>
http://host:port/Receiver.aspx

Username <User ID for login the system where message will be
Password received>
<Password for login the system where message

will be received>
Message Filename Edifact_CONTRL_Ack.txt
Message ID left Type the following regular expression for both:

Message ID right .*
Use compatible MessageId Unchecked
Own AS2 Name <AS2 Identifier>
Recipient‟s AS2Name <aka Organization name on AS2 connector>
testas2
Own email-address < Specifies the email address which is

transmitted in the AS2 message as sender >
<User-ID>@mailhost.com
Message subject < Specifies the subject included in the

message>
Edifact-CONTRL-Ack
Content type application/edi-x12
82

 Destination encoding ISO-8859-1
Dynamic Respect parameter Checked

configuration

Status
Compression Compress message Unchecked
Signature Sign message Checked
View to own public key < The NWA key-storage view in the sending
certificate partner, which contains the self (own) public key
Alias of own public key certificate and the alias (or name) under which
certificate the self (own) public key certificate is stored.
Use browse button to select it>
Select: AS2_CERTIFICATE / PI_Test-cert for

View to own private key < The NWA key-storage view in the sending partner,
Alias of own private key which contains the self (own) private key >
Select AS2_KEYSTORE / PI_Test for both

(view and alias)
Encrypt Encrypt message Checked
Algorithm 3DES
View to recipients public key AS2_CERTIFICATE / Partner_Test-cert

Alias of recipients certificate
83
MDN MessageDeliveryNotification Synchronous
Verify MIC checked

Request signing checked
Verify signature checked
View to signer‟s public key <The NWA key-storage view in the sending partner
certificate (SAP PI- initiator), which contains the receiving
partner‟s (responder) public key certificate and the
Alias of signer‟s public key alias (or name) under which the receiving partner‟s
certificate (responder) public key certificate is stored >

http://host:port/AS2/AS2DispatcherServlet_<User-ID>_var7
URL-Path)


Security Require encryption Checked


Request MDN Receipt Unchecked
84

Trading Partner Certificate – <selected-path>\PI_Test-cert.crt

Encryption
Security Trading Partner Certificate – <selected-path>\PI_Test-cert.crt

Signature


2. Copy the file “B2B_edifactSenderMessage_DELFOR_DESADV.txt” into the “Outgoing” folder and

create two or more copies of it.
3. Also, Copy the file “B2B_edifactSenderMessage_ DELFOR_DESADV_error.txt” with validation

errors in the DESADV Message Type into the “Outgoing” folder and create two or more copies of it.
software.
tab.
files” shows the available test files present at the trading partner location. If there isn‟t any, proceed
as described in ‎11.2.2
4. Click on the send button for the input file “B2B_edifactSenderMessage_DELFOR_DESADV.txt”.
6. On the host of the Advanced Adapter Engine Extended, open the file directory output-edifact (e.g.
\\host\<Selected-path>\AS2-EDISEP\output-edifact ). There should be an XML version of the input file
for each message type DELFOR and DESADV, respectively.
Verification for the CONTRL Acknowledgement generated:

1. Open the CONTRL Ack file “Edifact_CONTRL_Ack.txt”.
85
2. Check the UNB segment to identify the Interchange Sender ID and Interchange Receiver ID
(UNB020 and UNB030) to be the same as 7654321 and 1234567 respectively.
3. Check the Message Header UNH. A service segment starting and uniquely identifying a message.
Check for the Message Reference number at UNH010 which is also referenced in UNB, UNT, UNZ.
And for the Message Identifier at UNH020 for the Message type, Message Version number,
Message Release number and Controlling agency (in this case CONTRL, D, 3, UN respectively).
4. The UCI segment is the Interchange Response indicating the acknowledgment of the Interchange at
UCI040 to be “7”.
5. The UCF and UCM segment for both DESADV and DELFOR should indicate “7” as the Group
segment and the Message segment has been accepted.
6. The UNT and UNZ segment should indicate the count of the number of segments and the number of
Functional groups in the message at UNT010 and UNZ010.
Now repeat the steps 1-10 of the Execution section 10.4 with the test file “B2B_edifactSenderMessage_
DELFOR_DESADV_error.txt” and verify the CONTRL message generated as follows:
On the host of the Advanced Adapter Engine Extended, open the file directory output-edifact (e.g.
\\host\<Selected-path>\AS2-EDISEP\output-edifact ). There should be an XML version of the input file for
each message type DELFOR and DESADV.
Verification for the CONTRL Acknowledgement generated:
3. Check the Message Header UNH. A service segment starting and uniquely identifying a message.
Check for the Message Reference number at UNH010 which is also referenced in UNB, UNT, UNZ.
And for the Message Identifier at UNH020 for the Message type, Message Version number,
Message Release number and Controlling agency (in this case CONTRL, D, 3, UN respectively).
86
On the Receiver EDI Separator, the generation of acknowledgement was configured according to section
10.1.3.1
Additionally you have various configuration options to test the feature of the generation of CONTRL
Acknowledgement:
Case EDIFACT Negative Positive Execution UNA
Acknowled CONTRL Acknowled Acknowledg Mode segment
Transaction
gement Message gement not ement not required
Mode
Required Version and Required Required
Release
1 Not Version D, NA NA NA NA NA
Required Release 3
2 Required Version D, All Unchecked Checked Receipt Only Checked

Release 3
3 Required Version D, All Checked Unchecked Receipt Only Unchecked

Release 3
4 Required Version D, All Checked Checked Receipt Only Unchecked

Release 3
5 Required Version D, All Unchecked Checked Receipt & Unchecked

Release 3 Validation
6 Required Version D, All Unchecked Checked Receipt & Checked

7 Required Version D, All Checked Checked Receipt & Unchecked

8 Required Version D, Individual NA NA Receipt only Unchecked

Release 3
9 Required Version D, Individual NA NA Receipt & Checked

 Case 1:
Execution:
1. Execute the steps 1-5 of section 10.4 with the test file “B2B_edifactSenderMessage_
DELFOR_DESADV.txt”
\\host\<Selected-path>\AS2-EDISEP\output-edifact ). There should be an XML version of the input file
for each message type DELFOR and DESADV, respectively.
Verification of the CONTRL Acknowledgement generated:

1. No CONTRL Acknowledgement should be generated.
 Case 2:
Execution:
1. In the Integration flow “AS2_EDISep_var7_S1_<User-ID>” change the configurable parameter value
for eg, for the Sender Interchange ID to 765432.
87
2. There should be no messages generated for DESADV or DELFOR Message types as the entire
transaction is rolled back due to error in configuration.

2. Check for the UNA segment. The specifications in the UNA segment define the characters used as
separators and indicators for the interchange.
4. Check the Message Header UNH for the Message Reference number at UNH010 which is also
referenced in UNB, UNT, UNZ and for the Message Identifier at UNH020 (in this case CONTRL, D,
3, UN respectively).
5. The UCI segment is the Interchange Response indicating the Interchange is rejected at UCI040 to
be “4”.
segment and the Message segment has been rejected. The UCM segment should also indicate the
error code “17” (No Agreement) and “18” (Unspecified error) respectively at UCM0030.
 Case 3:
Execution:
1. Revert the changes done to the Integration flow “AS2_EDISep_S1_<User-ID>” in Case 2.
\\host\<Selected-path>\AS2-EDISEP\output-edifact ) respectively. There should be an XML version of
the input file for message type DELFOR and DESADV.

88
 Case 4:
Execution:
the input file for message type DELFOR and DESADV.

 Case 5:
Execution:
DELFOR_DESADV_error.txt”
transaction is rolled back due to validation error in DESADV Message type.

be “4”.
segment and the Message segment has been rejected. The UCS segment for DESADV should
indicate the error code “13” (Missing mandatory segment) at UCS020 and the UCM segment should
indicate “18” (Unspecified error) for DELFOR at UCM0030.
 Case 6:
Execution:

89
be “4”.
segment and the Message segment has been rejected. The UCS segment for DESADV should
indicate the error code “13” (Missing mandatory segment) at UCS020 and the UCM segment should
indicate “18” (Unspecified error) for DELFOR at UCM0030.
 Case 7:
Execution:
3. The EDI Separator Receiver channel EDISep_rec in the Integration flow
“AS2_EDISep_var7_R1_<User-ID>” should be in error state indicating that the messages are not
dispatched due to validation errors in Message type DESADV.

 Case 8:
Execution:
file for message type DELFOR but not for DESADV.

90
 Case 9:
Execution:
the input file for each message type DELFOR but not for DESADV due to validation error in
DESADV Message type.

6. The UCF and UCM segment for both DESADV and DELFOR should indicate “4” and “7” as the
Group segment and the Message segment has been rejected for DESADV and accepted for
DELFOR. The UCS segment for DESADV should indicate error code “13” (Missing mandatory
segment) at UCS020.
You can also monitor the relation between the EDI parent message and child messages (of type DELFOR
and DESADV) after their split.
1. To do so, in Message Monitoring, search for the child message (of type DELFOR and DESADV) by
selecting the appropriate radio button and then go to Message log tab.
2. The tab Message log and Message Details for the child messages (of type DELFOR and DESADV)
displays the correlation between the child messages and the parent message.
Parent EDI message.
91
4. Also check for the message “Message was split from an EDIFACT message with ID <Message ID of
12 Variant 8: AS2, EDI Separator (Odette: AVIEXP and DELINS) and EDI-XML Converter
On this variant, an Odette multi-message containing two message types (AVIEXP and DELINS) is sent by a
trading partner. The message is split by the EDI Separator, converted into XML and sent to a file receiver.
Three Integration Flows are configured in this variant:

Message Type: AVIEXP, Message Version Number: 3
Message Type: DELINS, Message Version Number: 3


click on “Next”
3. To assign the Communication Component to sender, right click on the sender -> Click on New
Business component -> select the Business Component name as <SID>_<User-
92
93

MessageID>
”.*”

”.*“

testas2

94

Status
certificate
Alias, and click OK

and alias)
Alias, and click OK

alias)

Disposition
Notification
channel”
95
Formatting Indent messages Unchecked

Status

channel
select “PI” and for Message protocol, select “Odette”
Filter Message Type Select „AVIEXP‟
Message Version Number Select „3‟
Interchange Sender SENDERXYZ

Identification

Interchange Recipient PARTNERZYX

Identification

Encoding Character encoding Select „US-ASCII‟
QoS Quality of Service Select „Exactly Once (asynchronous)‟

Status

96

sequence
Module Key 1
Up” button
Channel Template”
Parameters
odette
File Name Scheme Output-AVIEXP.xml

channel
select “PI” and for Message protocol, select “Odette”
Filter Message Type Select „DELINS‟
97
Message Version Number Select „3‟
Interchange Sender SENDERXYZ

Identification

Interchange Recipient PARTNERZYX

Identification

Encoding Character encoding Select „US-ASCII‟

Status


sequence
Module Key 1
Up” button
Channel Template”
Parameters
98
odette
File Name Scheme Output-DELINS.xml

URL-Path)




Request MDN Receipt Unchecked
99


Encryption

Signature


2. Copy the file “B2B_odetteSenderMessage_AVIEXP3_DELINS3.txt” into the “Outgoing” folder and

create two or more copies of it.
software.
tab.
4. Click on the send button.
6. On the host of the Advanced Adapter Engine Extended, open the file directory output-odette (e.g.
\\host\<Selected-path>\AS2-EDISEP\output-odette ). There should be an XML version of the input file
for each message type AVIEXP and DELINS, respectively.
You can also monitor the relation between the EDI parent message and child messages (of type AVIEXP
and DELINS) after their split.
1. To do so, in Message Monitoring, search for the child message (of type AVIEXP and DELINS) by
selecting the appropriate radio button and then go to Message log tab.
100
2. The tab Message log and Message Details for the child messages (of type AVIEXP and DELINS)
displays the correlation between the child messages and the parent message.
Parent EDI message.
4. Also check for the message “Message was split from an Odette message with ID <Message ID of
13 Variant 9: AS2, EDI Separator (VDA: 4905 and 4913) and EDI-XML Converter
On this variant, a VDA multi-message containing two message types (4905 and 4913) is sent by a trading
partner. The message is split by the EDI Separator, converted into XML and sent to a file receiver.
Three Integration Flows are configured in this variant:

Message Type: 4905
Message Type: 4913


click on “Next”
3. To assign the Communication Component to sender, right click on the sender -> give the Business
Component name as <SID>_<User-ID>_B2B_BC_AS2_EDISEP_V9_01 -> Click finish.
101
102

MessageID>
”.*”

”.*“

testas2

103

Status
certificate
Alias, and click OK

and alias)
Alias, and click OK

alias)

Disposition
Notification
channel”
104
Formatting Indent messages Unchecked

Status

channel
select “PI” and for Message protocol, select “VDA”
Filter Message Type Select „4913‟
Customer Number 12345678
Vendor Number 87654321
Encoding Character encoding Select „UTF-8‟
QoS Quality of Service Select „EO‟

Status


sequence
Module Key 1
105
Up” button
Channel Template”
Parameters
e.g. \\host\<selected-path>\AS2-EDISEP\output-vda

channel
select “PI” and for Message protocol, select “VDA”
Filter Message Type Select „4905‟
Customer Number 12345678
Vendor Number 87654321
Encoding Character encoding Select „UTF-8’
106

Status

and type the following values (please note that the module name is case sensitive):

sequence
Module Key 1
Up” button
Channel Template”
Parameters
e.g. \\host\<selected-path>\AS2-EDISEP\output-vda

107

URL-Path)




Request MDN Receipt unchecked


Encryption

Signature


2. Copy the file “B2B_vdaSenderMessage_4905_4913.txt” into the “Outgoing” folder and create two or
more copies of it.
108
software.
tab.
4. Click on the send button.
6. On the host of the Advanced Adapter Engine Extended, open the file directory output-vda (e.g.
\\host\<Selected-path>\AS2-EDISEP\output-vda ). There should be an XML version of the input file for
each message type 4913 and 4905, respectively.
2. The tab Message log and Message Details for the child messages (of type 4913 and 4905) displays
the correlation between the child messages and the parent message.
Parent EDI message.
4. Also check for the message “Message was split from a VDA message with ID <Message ID of the
parent EDI message>” in the Message log.
109
www.sap.com
© 2013 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP
products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany
and other countries.
Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty.

Adapotors

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Adapotors

Caricato da

Copyright:

Formati disponibili

SAP NetWeaver Process Integration 7.

4.4 Creating the Integration Flow ....................................................................................................... 23

12.1.1 Calling the Process Integration Designer ........................................................................................ 92

1.3 Intended Audience

2 Introduction and Prerequisites

Variant 5: Represents message exchange parting from a trading partner as ASC

2.1.1 AS2 Adapter

2.1.2 EDI Separator

2.1.3 EDI-XML Converters

2.1.4 SCN Articles

2.2.1 General Prerequisites

List of required steps:

2. You have imported the content SAP Note 836200

3. You have configured SAP Configuration of SAP NetWeaver Process Integration

2.2.2 Providing the necessary User and Authorizations

2.2.3 Setting up the Third party Tool Infrastructure (AS2 Connector)

2.2.4 Configuring the Certificates for authorization and authentication

NW Key Storage View Entry Description

AS2_CERTIFICATE Partner_Test-cert Partners Public Key Certificate

AS2_CERTIFICATE PI_Test-cert Own Public Key Certificate

AS2_KEYSTORE PI_Test Own Private Key

2.2.5 Setting Up the File Directories

2.2.6 Adding Software Components to PI B2B ADDON product

Business Components used in the scenarios :

2.3 Design Objects Used

2.4 Working with NWDS

2.4.2 Opening Perspectives and Views

2.4.3 Connecting to the Systems

2.4.4 Maintenance tool and B2B Seed File

After the import, the control data is available on the tables:

2.6 Design Objects Used

2.6.1 Summary of Design Objects Used

Object Type (Name) Description

Specifies the communication mode (asynchronous) and references the

Message Type (INVFILTO9) Message Type (INVFILTO9)

Data Type (INVFILTO9) Describes the data structure of the message

2.7 Configuring the Process Integration Scenario

2.8 Calling the Process Integration Designer

2.9 Creating the Integration Flow

Perform the following steps to create a new integration flow.

9. The integration Flow will be displayed in a graphical overview.

2.10 Creating Channels

Header Field Field Name Value

Recipient Recipient URL <Enter The URL path of the partner

Basic Authentication Checked

 Username <User ID for login the system where

 Password <Password for login the system where

Message Filename <Enter the file name>

<Enter the AS2 identifier >

<Enter the AS2 Name of the Recipient >

Own email- address <Enter the email address >

Message subject <Enter the subject of the message>

Content-Type <Enter the type of the content>

Content type with which the message is

Charset conversion Checked

 Destination encoding UTF-8

Header Field Field Name Value

Signature Sign message Check the sign message

The NWA key-storage view in the

e.g. AS2_CERTIFICATE / PI_Test-cert

The alias (or name) under which the self

which contains the self (own) private key

Encryption Encrypt message Check the encrypt message box

Algorithm <Select the encryption algorithm >