Scribd
Upload
36 views5 pages

PI-PO Usage in AEI

This document provides a quick overview of how to use Process Integration/Orchestration (PI/PO) tools to understand Argentina's Electronic Invoicing (AEI) solution. The Message Monitor and Enterprise Services Builder are the most useful PI tools for incident processing and understanding how fields are mapped between XML and internal systems. The Enterprise Services Builder allows viewing how operation mappings define entire message flows and how message mappings link XML fields to backend systems. It can also test message mappings by using real payloads from customer systems.

Uploaded by

fzank
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
36 views5 pages

PI-PO Usage in AEI

This document provides a quick overview of how to use Process Integration/Orchestration (PI/PO) tools to understand Argentina's Electronic Invoicing (AEI) solution. The Message Monitor and Enterprise Services Builder are the most useful PI tools for incident processing and understanding how fields are mapped between XML and internal systems. The Enterprise Services Builder allows viewing how operation mappings define entire message flows and how message mappings link XML fields to backend systems. It can also test message mappings by using real payloads from customer systems.

Uploaded by

fzank
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Usage of Process Integration/Orchestration (PI/PO) in Argentina Electronic Inovicing

Note: This is not meant to be a comprehensive document or training material for PI. As AEI's
messaging service is based on PI at some points issues there will have to be checked by the AEI
application team. This document is meant to provide a quick overview of topics that have
shown to be relevant for incident processing and understanding the solution. It may be freely
updated by the AEI team.

PI Access can be useful to check how fields are being mapped to the XML, how
communications to the webservice are set up and to get payloads of past messages.

The most useful tools for us are the Message Monitor and Enterprise Services Builder.

In the end you will find a relation of internal systems.

Message Monitor

PI systems -> Log via R/3 connection and run transaction SXI_MONITOR. Look up the messages
with the timestamp seen in the log on J1AMONITOR at the ECC. Filtering by sender and
receiver component can be useful, but customers can define these with the names they prefer

PO systems -> In PO systems the ABAP layer is no longer available. In these cases, the message
monitor must be accessed via the cockpit. The path to be taken in the cockpit is:

Configuration and Monitoring Home -> Adapter Engine -> Communication Channel Monitoring
-> Search for the right channel (CC*rfc*AR* might be helpful when you don't have this
information at hand).

Find the node with errors and open it. Select the relevant message, click 'Open Message' and
then 'Payload'

Enterprise Services Builder

This requires WTS access on customers systems, as it must be accessed on a web cockpit which
then downloads a java executable.

You can use transaction SXMB_IFR in the ABAP layer or acess it directly on the browser via
http://<server>:<port>/dir/start/index.jsp. For X3X, the URL is
http://vwgsapx3x.wdf.sap.corp:52300/dir/start/index.jsp

Select 'Enterprise Services Builder' and execute the downloaded file.


There, navigate to component CNT-LOC -> CNT-LOC 6.05. You will find a package for each
webservice used.

Inside the definitions will be grouped in Operation Mappings, Message Mappings and others.

Operation Mappings

As the name states, it maps the entire operation, starting at input from a BAPI call and ending
in a message definition. When selecting the 'Response' mapping, the flow will be the other way
around.
Message Mappings

Here each field of the output XML gets mapped to a BAPI field. Double clicking a field on the
right side of the screen will show the mapping at the bottom in a graphical layout.

Sometimes, functions can be used. The definition can be seen by double clicking the function
call or acessing the tab 'Functions' at the top:

The tab 'Test' can be used to test the message mapping alone. You can collect the BAPI XML
payload from a customer system and test it internally to quickly identify mapping problems,
for an example.

<images for testing>

External Definitions

External messages are the layouts for each XML expected by AFIP webservice. They are
imported in a package (such as ED_wsfev1_WSDL) which can be accessed through the External
Definitions tab or just double clicking the external message name in the message or operation
mapping.
This is delivered straight from AFIP and there is not much room for error. The xml tags and
types can be seen by expanding the tabs on the definitions:

Service Interfaces

Operation mappings are tied to Service Interfaces, which contain the information about which
webservice to contact with different messages. There we can see the URL to be reached and
which message definitions should be used for each occurrence.

Internal Systems

QW9 - X1T

Usuário: ESR1
Senha: Initial@1

O link para esse sistema é o seguinte:

http://pwdf6638.wdf.sap.corp:50016/dir/start/index.jsp

QV6 - X3X

You might also like