Skip to Content

This is a continuation of previous demo SAP PI/PO : –  POSDM INTEGRATION WITH ARTS POSLog POS SYSTEM – TUTORIAL 1 . In the previous demo I have shown how to integrated POS Sales with POSDM BAPI.


Before proceeding to this demo request to go through the above demo published in link:

SAP PI/PO  : –  POSDM INTEGRATION WITH ARTS POSLog POS SYSTEM – TUTORIAL 1



In this demo I would like to show  how to integrate an Inbound ARTS POSLog Sales with POSDM IDOC  through SAP PI/PO

In any IS Retail implementation , Sales from Point Of Sales(POS) system needs to be integrated with SAP ERP. Process flow is as below:

          POS(Sales) -> SAP PI/PO -> POSDM(SAP BW) -> SAP ECC.

Capture0.JPG

Step1 :  Import the IDOC “/POSDW/POSTR_CREATEMULTIPLE./POSDW/POSTR_CREATEMULTIPLE04” from BW  system.


Capture1.JPG



Step2 : Create a Source Data Type.


Capture2.JPG


Step3 : Create a Message Type:


Capture3.JPG



Step 4: Create  outbound service interface


Capture5.JPG


Step6 : Create Operation Mapping as shown below :

Capture6.JPG


In the operation map 3 steps are  involved:

1) First map is an xslt map to remove namespace.This is used as the input ARTS POSLog has the vendor namespaces embedded in it. If you see the below screen shot  POSLog has namespaces and these must be removed before  converting to target BAPI.If the input payload does not have namespaces then this step is  not necessary.

Capture6.1.JPG

Below is the code which is must be entered in “RemoveNamespaces.xsl”.


<xsl:stylesheet version=“1.0” xmlns:xsl=http://www.w3.org/1999/XSL/Transform>

<xsl:output method=“xml” indent=“no”/>

<xsl:template match=“/|comment()|processing-instruction()”>

    <xsl:copy>

<xsl:apply-templates/>

    </xsl:copy>

</xsl:template>

         

<xsl:template match=“*”>

    <xsl:element name=“{local-name()}”>

<xsl:apply-templates select=“@*|node()”/>

    </xsl:element>

</xsl:template>

<xsl:template match=“@*”>

    <xsl:attribute name=“{local-name()}”>

<xsl:value-of select=“.”/>

    </xsl:attribute>

</xsl:template>

</xsl:stylesheet>


1) Second mapping is the java map which converts  ARTS POSLog to IDOC.

Here I have handled ARTS POSLog different operations in separate Java map.The advantage of this approach is that it is easy to maintain and support.

First  “PoslogFileToIdocConversion.java”  will be called and this inturn will call the other the other programs.


Capture7.JPG

Note:

In this scenario   I will show how to  split handling of POSLog operations in multiple java maps.The advantage is that it is easy to support and maintain however takes time and is more complex.

Upto the individual to take the call which approach one can follow.



  1. 1) Third map is  a graphical map in which /POSDW/POSTR_CREATEMULTIPLE./POSDW/POSTR_CREATEMULTIPLE04 fields are one to one map except for one field called “FINANCIAL TYPE CODE”. Fix value standard function is used.


Capture8.JPG



With ESR  development done lets proceed to ID development:

Step 7: Create File Sender Channel as below:


Capture9.0.JPG



Step 8 : Create Sender agreement .

Capture9.JPG


Step 9 : Create Receiver Determination.

Capture10.JPG


Step 10 : Create Interface Determination.


Capture11.JPG



Step 11:  Create Receiver Agreement.

Capture12.JPG



Test the scenario :

Place the POSLog file in the source system.

Capture13.JPG



Login into BW system and enter the tcode “WE02”. One can find the inbound idocs submitted by PI.


Capture14.JPG
















To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply