Process Orchestration - A Round-Trip For B2B Integration Scenarios

Process Orchestration –
A Round-Trip for B2B Integration Scenarios
POP361
Exercise b)
Piyush Gakhar
Vikas Singh Rajpurohit
Gunther Stuhec
Ilya Stepanov
Appala Naidu
Vishnu Prasad K
2
Exercise b: Pick an INVOIC IDoc xml file, convert it to ANSI X12 format and
send it to trading partner (customer) using AS2 protocol and receive technical
(MDN) and functional (997) acknowledgements.
In this exercise, the Integration flows are already created for you. There are 4 Integration flows that will be used in this
th
exercise. You have to update 3 of them and reuse 4 IFlow (EXC_POP361_1_ReceiveBulk850OrdersFromCustomer)
as created in exercise a) without any change
Follow the steps as mentioned below:
Step Screenshots
1. Launch the internet explorer.

Open the
B2BIntegrationCockpit
form favourites > POP361 >
B2BIntegrationCockpit
2. Enter the credentials:

User : demo
Password: welcome
3
3. Click on the link NRO

Maintenance
4. Click on the button Create

new number range object.
Enter the following:
Number range object name:
/B2B/EXC361_X12Invoice
Out
Minimum Value:
6000000000
Maximum Value:
6999999999
Then click on button Save
and create.
4
5. It will create an entry.
6. Go to the SAP NetWeaver

Developer Studio. In the PI
Explorer tab view open the
folder EXC_POP361->
double click and open the
Integration Flow
EXC_POP361_4_SendX12
InvoiceToCustomer
Note: this integration flow

will pull the invoice IDoc
xml file and send it to the
Trading Partner.
7. Click on the “SFTP” arrow

at sender’s side.
Click on right mouse button

for getting the context menu
and select “Configure
Channel”.
5
8. Click on “Adapter-Specific”
tab. Enter the following
values:
a. Username: techedXX
(Replace ‘XX’ with your
participant no. during the
workshop. Example:
teched00)
b. Password :techedXX
9. Go back to integration flow

diagram view by clicking on
tab “Model Configurator”.
6
10. Click on the “AS2” arrow at

receiver’s side.

Channel”.

tab. Enter the Filename as
X12Invoice
12. Click on “MDN” sub-tab.

Enter the following values:
a. Communication Channel :
EXC_POP361_5_Receiv
eMDNFro_EXC_AS2_M
DN_SND
b. Communication
Component:
EXC_POP361_BC_PI
Note: Here the

Communication Component
and the Channel name
mentioned are of the already
provided Integration flow -
EXC_POP361_5_Receive
MDNFroCustomer
7
13. Click on “Modules” tab.

Ensure as per snapshot.

8
15. Select the Operation

Mapping element
OM_INVOI.. and go to the
Properties tab view.
Enter the value for Name
NROName as
$B2B_UEBNREXC361_X
12InvoiceOut$B2B_END_
UEBNR
Note: here we are

consuming the NRO created
above.
16. Open to the Properties tab of

the Integration flow by
clicking on the graphical
vacant area and selecting the
property sheet.
Ensure that the Adapter
Engine value is populated as
Central Adapter Engine. If
not then select it from the
dropdown.
17. Click on “Save” button to

save the configurations.
9
18. Activate the integration

flow, by select the
“Integration Flow”:
InvoiceToCustomer
Open the context menu by

clicking on right mouse
button and click on
“Activate”
19. Commit the activation by

clicking on “Yes” button.
Wait until the activation is

finished, successfully. Click
on Ok button on the
confirmation popup.
20. Deploy the activated

integration flow, by select
the “Integration Flow”:
InvoiceToCustomer

button and click on
“Deploy”
10
21. Commit the deployment by

22. Wait until the deployment is

finished successfully.
23. Now open the Integration

Flow
MDNFromCustomer
Note: this integration flow

will receive the MDN sent
from the Trading Partner
and put it to the SFTP
server.

at receiver’s side.

Channel”.
11

values:
workshop. Example:
teched00)


property sheet.
dropdown.
12


flow, by select the
MDNFromCustomer

button and click on
“Activate”


on Ok button on the
confirmation popup.

MDNFromCustomer

button and click on
“Deploy”
13


34. Now open the Integration

Flow
EXC_POP361_6_Receive9
97FromCustomer
Note: Here the integration

flow
EXC_POP361_1_ReceiveB
ulk850OrdersFromCusto
mer created in exercise a
will be used as it is. It will
hand over the 997 functional
ack to this integration flow
and it will put the 997
functional ack to the SFTP
server.
35. Click on the “EDISeparator”

arrow at sender’s side.

Channel”.
14

values:
a. Transaction Set identifier
Code: 997
b. Interchange Sender ID
:EXCMSA
c. Interchange Receiver ID
:EXCPIA
37. Go back to the integration

flow diagram view by
clicking on tab “Model
Configurator”.

at receiver’s side.

Channel”.
15

values:
workshop. Example:
teched00)
40. Go back to the integration

flow diagram view by
clicking on tab “Model
Configurator”.

property sheet.
dropdown.
16


flow, by select the
97FromCustomer

button and click on
“Activate”


on Ok button on the
confirmation popup.

97FromCustomer

button and click on
“Deploy”
17


48. Now you have configured

and activated all the
integration flows. Next step
is to run the scenario.
49. To run the scenario go to the

Filezilla client and drag and
drop the file
X12Invoice.xml from left
pain
(D:\Files\Session\POP361\T
est Files\Exercises\) to right
pain (/home/techedxx/input)
50. SFTP sender channel of the

integration flow
InvoiceToCustomer
automatically polls the file
according to the polling
interval defined in
communication channel and
would delete the file after
processing from input
folder.
18
51. Message should reach the

AS2 simulator software.
Read the logs for successful
message received and MDN
sent by AS2 simulator
software back to PI.
52. Open the message by double

clicking on it. Go to the
Transfer Payload tab and
copy the value highlighted
in the snapshot. You will use
it while sending the 997 ack.
19
53. Open the screen for

monitoring “Integration
Flow
a) Right Click on Iflow
and click “Monitor
Integration Flow” (If
required, enter
username as demo and
password as welcome)
54. Select the SFTP

communication channel and
scroll below to see the
channel logs. Check that the
SFTP Adapter
Communication Channel
Logs are successful.
55. Select AS2 adapter from

communication channel
monitor screen and scroll
down
56. Check AS2 Adapter

Logs. It should display
“MDN with action-mode
automatic-action, sending-
mode MDN-sent-
automatically and
disposition-type processed
received”
20
57. Now open the message

monitoring by clicking on
the Message id link.
Ensure:
a) The Message status is
Delivered.
b) In the B2B
Acknowledgements tab
The status indicator for
Type MDN should be
Success with a green
led.
The status indicator for

Type 997 should be In
Process with a yellow
led.
Note:
Keep this window open
(minimize it). You will refer
it to ensure the 997
functional acknowledgement
is received successfully.
58. Now open the monitoring

screen for integration flow:
MDNFromCustomer as
done in step 52 above.
59. Select AS2 adapter from

communication channel
monitor screen and scroll
down.
60. Check AS2 Adapter

Logs. It should display
“MDN received for
message”.
21
61. The MDN was received

successfully by the sender
AS2 channel of the
integration flow
MDNFromCustomer and
finally written to the SFTP
server by the receiver SFTP
channel.
Ensure the file
mdn_timestamp.xml is
present in the output folder.
Note: Refresh the folder via

context menu to get the file
if not seen already.
62. Now you will send the 997

functional acknowledgement
using the AS2 simulator
software.
Before that open the file 997
for invoice-A.txt and
replace the highlighted
fields with 6000000000 (the
value copied by you in step
52 above )
Save the file. Click on yes if
any confirmation is asked
for the update.
63. Now go to the AS2

simulator software.
File menu > Send file to
partner.
64. Click on the button browse.

22
65. In the popup enter the value

D:\Files\Session\POP361\T
est Files\Exercises then hit
Select button.
The files will appear. Select
the file 997 for invoice-
A.txt you updated latest.
66. Now hit the Ok button. As a

result the 997 ack will be
sent successfully.
67. Now open the window you

minimized in the step 57
above. Ensure the status
indicator for Type 997
should be Success with a
green led.
68. Now monitor the integration

flow
97FromCustomer.
Ensure that the EDI
Separator and the SFTP
channel logs are successful.
Now go to the filezilla client
and ensure that a file
997_timestamp.txt is
present in the output folder.
23
69. Now you can try Partially

accepted scenario. Where
the AS2 simulation software
partially accepts the
message.
To achieve this repeat the
steps from 49 to 61 as it is
(from sending invoice
again).
Follow the step 62 and
update the file 997 for
invoice-PA.txt in place of
997 for invoice-A.txt.
Then send the same file
using steps 63 to 66.
70. Now the step 67 will have

the status of the 997 ack will
be Error.
Status code will be
PARTIALLY_ACCEPTE
D_RECV
71. Similarly you can test the

Rejected scenario.
In this case:
a) The file to be sent as
997 ack will be 997 for
invoice-R.txt
b) Status code will be
REJECTED_RECV
24
© 2013 by SAP AG or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications
may vary.
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.
SAP 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.
Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.

Process Orchestration - A Round-Trip For B2B Integration Scenarios

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Process Orchestration - A Round-Trip For B2B Integration Scenarios

Uploaded by

Copyright:

Available Formats

Process Orchestration –

A Round-Trip for B2B Integration Scenarios

Follow the steps as mentioned below:

1. Launch the internet explorer.

2. Enter the credentials:

3. Click on the link NRO

4. Click on the button Create

5. It will create an entry.

6. Go to the SAP NetWeaver

Note: this integration flow

7. Click on the “SFTP” arrow

Click on right mouse button

9. Go back to integration flow

10. Click on the “AS2” arrow at

Click on right mouse button

11. Click on “Adapter-Specific”

12. Click on “MDN” sub-tab.

Note: Here the

13. Click on “Modules” tab.

14. Go back to integration flow

15. Select the Operation

Note: here we are

16. Open to the Properties tab of

17. Click on “Save” button to

18. Activate the integration

Open the context menu by

19. Commit the activation by

Wait until the activation is

20. Deploy the activated

Open the context menu by

21. Commit the deployment by

22. Wait until the deployment is

23. Now open the Integration

Note: this integration flow

24. Click on the “SFTP” arrow

Click on right mouse button

25. Click on “Adapter-Specific”

26. Go back to integration flow

27. Open to the Properties tab of

28. Click on “Save” button to

29. Activate the integration

Open the context menu by

30. Commit the activation by

Wait until the activation is

31. Deploy the activated

Open the context menu by

32. Commit the deployment by

33. Wait until the deployment is

34. Now open the Integration

Note: Here the integration

35. Click on the “EDISeparator”

Click on right mouse button

36. Click on “Adapter-Specific”

37. Go back to the integration

38. Click on the “SFTP” arrow

Click on right mouse button

39. Click on “Adapter-Specific”

40. Go back to the integration

41. Open to the Properties tab of

42. Click on “Save” button to

43. Activate the integration

Open the context menu by

44. Commit the activation by