In this post, “SAP PO for Beginners Part – 12 – Interface Development – B2B EDI Inbound to XML Proxy to ECC,” we will discuss and convert EDI format inbound documents to XML and pass them to an ABAP proxy by developing an interface from scratch.

In short, below is the content we will be elaborate in this tutorial: Interface Development – B2B EDI Inbound to XML Proxy to ECC

• Overview
• Scenario
• Objects involved in Interface Development
• Build Enterprise Service Repository Objects
• Build Communication Channels
• Build Integrated Configuration (ICO)
• Testing the Interface

1. Overview:

Assume there is a business requirement where the vendor will place invoice records in SFTP in EDI format, which SAP PO needs to pick up and process. The EDI messages are then communicated to the EDI separator connector to split bulk EDI messages into single transaction sets, as one EDI document can contain multiple sales orders, invoices, delivery notifications, etc., which completes one ICO. Subsequently, it will be passed to another ICO of the sender EDI separator channel, which will convert individual EDI messages to XML. This process is detailed in SAP PO for Beginners Part – 12 – Interface Development – B2B EDI Inbound to XML Proxy to ECC.

2. Scenario:

3. Objects involved in Interface Development:

As said, there are 2 ICOs to be created. For first ICO, we will pick the document from SFTP, so the shipper correspondence channel is of connector type SFTP (not going to cover the SFTP channel config, as I take care of it in past areas) and the recipient correspondence channel will be of connector type EDI Separator.

For second ICO, the shipper correspondence channel would be of connector type EDI Separator and the collector correspondence channel will be of connector type Cleanser with message convention as XI 3.0.

In second ICO, we will import message planning, in light of the fact that through shipper EDI connector, the EDI record will be changed over completely to XML and passed to message planning for getting the ideal construction to pass the information to ECC through ABAP Intermediary.

We should make information objects for the inbound XML information. In this model we won’t make information type and message type, rather we are utilizing the Outer Definitions given by the merchant. Outside Definitions are like pre-characterized field structures which you can simply import and use it in Message planning.

4. Build ESR Objects:

Prior to continuing with the formation of Correspondence channels, we should begin with the result structure creation.

External Definitions:

Click on Make NEW – > Outside Definitions

Select the class as XSD from the dropdown and import the XSD document.

For getting the import XSD document, explore to the underneath way:

http://:/b2bic (For this to be accessible, B2B add on should be introduced by Premise group)

Select the choice, EDI Content Administrator and select the dropdown in the arrangement ANSI X12 and pick XSD Generator.

For producing XSD record, pick the suitable exchange set as 810 and adaptation to 5040 (for our situation). Once finished, click on START.

Framework will produce the xsd record, save it and import it in outer definition as displayed beneath.

External Definition:

Click on SAVE & ACTIVATE.

Service Interface:

Create two service interfaces.

The file is passed from SFTP to P – Outbound Service Interface – 1

PI to ECC – Inbound Service Interface – 2

Choose the Mode as ASYNCHRONOUS

Outbound Service Interface:

Inbound Service Interface:

Message Mapping:

Import a similar outside definition into source and target area, as we will be passing the information for all intents and purposes to ECC.

Operation Mapping:

Import both the outbound and inbound assistance interfaces. Once imported, click on READ Tasks button which would peruse the outside definitions put away in assistance interfaces.

When done, select the sort of planning and import the message planning made.

Click on SAVE & ACTIVATE.

ESR Items creation done. We should begin with the Joining Items advancement.

5. Build Communication Channels:

FIRST ICO:

Sender Communication Channel:

Open the Reconciliation Catalog – > Snap on Make New symbol and pick Correspondence Channel.

Give the channel a reasonable channel name and tap on Make. Pick Connector type as SFTP and pick Shipper Radio button.

Click on SAVE and Actuate.

Receiver Communication Channel:

Click and Make New – > Correspondence Channel – > Pick Collector radio button and connector type as EDI Separator with Message Convention as Electronic Report Exchange.

Note: For getting the EDI Separator connector which wouldn’t be in standard PO 7.5 establishment, B2B add on establishment should be finished.

• BASIS team installs B2B cockpit
  • Make sure NWA-> Components Info, b2b components are installed
  • Download and extract ZIP files of B2B Cockpit/toolkit/EDI mapping runtime
  • Import toolkit/mapping kit extracted files in ID
  • For installing EDI runtime content, there will be many .b2b seed file, import the required file. For e.g.: for EDI ANSI X12 format, required runtime is *X12.b2b file
  • http://<host>:<port>/b2bic -> EDI content Manager. Select required format and choose to import in dropdown
  • Verify imported components by selecting format -> Editor > Message Editor
  • Verify in ID whether EDI adapter is visible
  • If these B2B adapters are still not available, request BASIS team to register the adapters using JSPM

Click on SAVE & ACTIVATE.

SECOND ICO:

Sender Communication Channel:

Open the Combination Catalog – > Snap on Make New symbol and pick Correspondence Channel.

Give the channel a reasonable channel name and tap on Make. Pick Connector type as EDI Separator and pick Shipper Radio button.

Source EDI separator will change over individual EDI messages to XML. For changing over the EDI design payload to XML, add the underneath module in the source channel.

Under module tab,

localejbs/X12ConverterModule – Nearby Venture Bean – 1

This ought to be the first and afterward the SAP call connector ought to come. Request is significant.

Since it is a receipt record of EDI 810, we want to determine the exchange set identifier code as 810 and rest all as *.

Click on SAVE & ACTIVATE.

Receiver Communication Channel:

Open the Coordination Catalog – > Snap on Make New symbol and pick Correspondence Channel.

Give the channel a reasonable channel name and tap on Make. Pick Connector type as Cleanser with message convention as XI 3.0 and pick Collector Radio button.

Click on SAVE and Initiate.

6. Build Integrated Configuration (ICO):

Click on NEW – > Coordinated Setup (make ICOs).

Give the Coordinated setup name and namespace. It ought to be indistinguishable from the ESR Outbound Help Point of interaction name and namespace.

Import the shipper divert and in next tab, select the business part under which the collector correspondence channel is made.

Import the Activity planning (for first ICO, no activity planning exists) from ESR. Activity planning will consequently show in the event that you have offered right Support Connection point name and namespace while characterizing Coordinated design name and namespace.

Import the recipient correspondence channel.

Click on SAVE and Initiate.

That is finished. We have made EDI to intermediary interface without any preparation. We should test it.

7. Testing the Interface:

SFTP, I have transferred an example EDI 810 document.

first ICO, no planning happens. In the event that EDI document contains various receipt sets, it will be parted separately.

second ICO source channel, the module we added for change to XML.

Also, planned to the ECC structure through message planning and went to ECC through intermediary.

SXI_MONITOR:

We have successfully developed and tested the Interface Development – B2B EDI Inbound to XML Proxy to ECC interface. Hope you found it helpful. If you have any doubts, questions, or suggestions for us, please feel free to leave your comments below.

YOU MAY BE INTERESTED IN:

Do all ABAPers know Fixed Point Arithmetic?

Understanding IDoc Status in SAP SD: A Comprehensive Guide

SAP ABAP CRM Tips

In this post, “SAP PO for Beginners Part – 11 – Synchronous Interface Development – SOAP Proxy to SOAP Webservice,” we will guide you through creating a mediator to SOAP web service interface without any initial setup. This will be an ad hoc interface, triggered as needed from ECC, where configuration will take place and be sent to the target web service.

Thus, under is the substance we will be mind boggling in this educational activity:

Outline
Situation
Objects associated with Connection point Advancement
Fabricate Undertaking Administration Store Items
Assemble Correspondence Channels
Assemble Coordinated Setup (ICO)
Testing the Point of interaction

1. Overview:

Imagine a scenario where there is a business requirement to send the XML payload through ABAP Proxy and communicate the same to the recipient web service. You would also need to handle the response from the web service, as it is a synchronous interface. In “SAP PO for Beginners Part – 11 – Synchronous Interface Development – SOAP Proxy to SOAP Webservice,“ we will cover how to effectively manage this process, ensuring smooth communication between the systems.

2. Scenario:

3. Objects involved in Interface Development:

In the first place, we should make information objects for the solicitation and for the reaction. In this model we won’t make information type and message type, rather we are utilizing the Outside Definitions given by the merchant. Outside Definitions are like pre-characterized field structures which you can simply import and use it in Message planning.

There will be 2 Message mappings that must be made. Solicitation to reaction and reaction to ECC yield structure.

Second, we will make a source correspondence channel of connector type Cleanser with Message Convention as XI 3.0, for ECC association. For Cleanser Intermediary association from ECC to PI, I have proactively posted a blog on it To some extent 4 of my “SAP PO for novices” series.

Third, a recipient correspondence channel of connector type Cleanser with Message Convention as Cleanser 1.1.

At last, we will make an ICO and import the shipper, recipient, and activity planning.

4. Build ESR Objects:

Prior to continuing with the making of Correspondence channels, how about we start with the result structure creation.

External Definitions:

Click on Make NEW – > Outer Definitions

Select the classification as WSDL from the dropdown and import the WSDL document. Click on SAVE and Initiate.

Service Interface:

Make two assistance interfaces. The justification behind two help connection points is:

The document is passed from ECC to PI and the reaction from PI to ECC – Outbound Assistance Point of interaction – 1

PI to Web administration and webservice to PI – Inbound Assistance Connection point – 2

Pick the Mode as Simultaneous

Outbound Assistance Connection point:

Inbound Service Interface:

Message Mapping:

Import same message types in source and target region and perform adjusted arranging. If the objective webservice contains username token (username and secret expression for security), add those fields in the objective XSD and import it in message arranging.

The username and secret key the recipient webservice can be different for every client. Like, the outsider would have arrangement different username and secret phrase for dev, QA and Push. What’s more, in the event that you offer a consistent benefit to username and secret word in DEV and on moving ESR objects to QA, you will not have the option to change the certifications in QA as it is unmodifiable.

At these kinds of cases, esteem planning comes into picture.

You should make esteem planning in Joining catalog, yet before that you want to import the standard worth planning capability in the graphical planning region and give source and target outline (simply an irregular worth to relate with diagram you make in Mix registry. Against the construction just, you will appoint username and secret phrase).

On double tapping the worth planning capability, you will be provoked to enter source office, pattern, and target organization construction. Enter an important string, so in future it will be engaging. Up until this point, you haven’t entered any accreditations. With this office pattern, you will dole out this in esteem planning bunch made in ID and referencing the certifications.

Click on SAVE & ACTIVATE.

Value Mapping:

Map the objective office and construction and guide the accreditations in the worth region. At planning runtime, framework will pick the planned certifications. By this way you can have the certifications put away in one spot and can change it in every client.

Solicitation to Reaction planning is finished, next is the webservice reaction to ECC yield structure planning.

In this way, make another message planning and import the necessary WSDL documents at the source and target.

Operation Mapping:

Import both the outbound and inbound help interfaces. Once imported, click on READ Tasks button which would peruse the message types put away in help interfaces.

When done, select the kind of planning and import the message planning made.

Moreover, in the solicitation and reaction we have imported XSL planning record in light of the fact that while sending the solicitation payload to webservice, it just acknowledges Cleanser Envelope payload body, thus while outbound we add Cleanser design to payload and keeping in mind that reaction, we eliminate it, since ECC doesn’t comprehend Cleanser structure.

In the reaction tab, import first the XSL eliminating document and afterward the message planning.

Click on SAVE & ACTIVATE.

ESR Items creation done. We should begin with the Incorporation Items advancement.

5. Build Communication Channels:

Sender Communication Channel:

Open the Joining Catalog – > Snap on Make New symbol and pick Correspondence Channel.

Give the channel a reasonable channel name and namespace and tap on Make. Pick Connector type as Cleanser and Source Radio button.

Message Convention – XI 3.0

That is all there is to it. No extra configs in channel. Click on SAVE and ACTIVATE.

Receiver Communication Channel:

Click and Make New – > Correspondence Channel – > Pick Recipient radio button and connector type as Cleanser with Message Convention as Cleanser 1.1.

Under the Association Boundaries, enter the Objective Webservice URL. As we are adding Cleanser envelope through planning, actually take a look at the choice – Don’t utilize Cleanser Envelope.

Click on SAVE & ACTIVATE.

6. Build Integrated Configuration (ICO):

Click on NEW – > Incorporated Design.

Give the Incorporated design name and namespace. It ought to be indistinguishable from the ESR Outbound Assistance Connection point name and namespace.

Import the source direct and in next tab, select the business part under which the beneficiary correspondence channel is made.

Determine beneficiary condition if any.

Import the Activity planning from ESR. Activity planning will naturally show assuming that you have offered right Support Connection point name and namespace while characterizing Coordinated arrangement name and namespace.

Import the recipient correspondence channel.

Click on SAVE and Enact.

That is finished. We have made Cleanser Intermediary to Cleanser Webservice interface without any preparation. How about we test it.

7. Testing the Interface:

For testing a simultaneous connection point, you can either do it in Cleanser UI or from PI Send Test message wizard or illuminating functionals to set off the exchange.

I will do it from PI Send Test Message Wizard.

I have the XML payload. Explore to the Send Test Message wizard, PI Landing page – > Arrangement and Checking – > Testing tab – > Send Test Message.

Select the Incorporated arrangement you made. Pick the Nature of Administration as Best Exertion. Glue the payload. Click on SEND once finished.

Note: For Simultaneous connection point, you ought to set off from the shipper framework, for this situation ECC. For testing reason, I’m setting off from PI.

1 – PI to Webservice

2 – Webservice to PI to ECC

Both are effective.

To see the effective planning, explore to the message and snap on OPEN MESSAGE button. Under the payload choice you can see the various variants of the payload.

0 – addresses the before-planning variant

2 – addresses the subsequent to planning rendition

That concludes SAP PO for Beginners Part – 11 – Synchronous Interface Development – SOAP Proxy to SOAP Webservice. I hope you found it informative and engaging. If you have any doubts, questions, or suggestions, please feel free to leave your comments below.

YOU MAY BE INTERESTED IN

ABAP for SAP HANA. ALV Report On SAP HANA – Opportunities And Challenges

OData in SAP ABAP: Streamlining Data Exchange and Integration

ABAP on SAP HANA: ATC – ABAP Test Cockpit Setup & Exemption Process

In this post, “SAP PO for Beginners Part – 10 – Interface Development – File (with File Content Conversion) to SFTP,“ we will develop a file-to-SFTP interface from scratch. We will convert the flat file to XML format using File Content Conversion (FCC) and place it in the SFTP server location with SSH key authentication.

In short, below is the content we will be elaborate in this tutorial:

• Overview
• Scenario
• Objects involved in Interface Development
• Build Enterprise Service Repository Objects
• Build Communication Channels
• Build Integrated Configuration (ICO)
• Testing the Interface

---

1. Overview:

Expect there is a prerequisite from business on sending the level document from ECC Application server to a SFTP area with SSH key verification. We won’t send the level record for all intents and purposes, rather convert it to XML by Document Content Change. Additionally, for getting to SFTP, we won’t go with Fundamental auth (Username and secret phrase), rather we will go with SSH key confirmation where we create private and public SSH key matches through Clay programming and give the public key to the outsider who possesses the SFTP server. We should introduce the confidential key in the NWA-> Keys and Endorsements area and notice the keystore name and view in the collector correspondence channel for fruitful validation.

2.Scenario:

3. Objects Involved in Interface Development:

To begin with, we should make ESR objects like Information type, Message type, Administration Connection point, Message Planning, Activity Planning.

Second, we will make a shipper correspondence channel of connector type Document with Message Convention as Record Content Transformation.

Third, a beneficiary correspondence channel of connector type SFTP.

Fourth, SSH KEY matches through Clay programming and introduce it in PI NWA.

At long last, we will make an ICO and import the source, collector, and activity planning.

4. Build ESR Objects:

Prior to continuing with the formation of Correspondence channels, how about we start with the result structure creation.

Data Type:

Characterize the fields and events.

Message Type:

Wrap the information type with message type. Also, this message type and namespace, you need to give it in Record CONTENT Transformation which will come while making source correspondence channel.

Service Interface:

Make two help interfaces. The justification for two help connection points is:

The record is passed from ECC to PI – Outbound Help Connection point – 1

PI to SFTP – Inbound Help Point of interaction – 2

In both help interfaces, the solicitation message type will be same, as we are passing one steady result structure.

Outbound Assistance Connection point:

Inbound Service Interface:

Message Mapping:

Import same message types in source and target area and perform balanced planning.

Click on SAVE and ACTIVATE.

Operation Mapping:

Import both the outbound and inbound assistance interfaces. Once imported, click on READ Tasks button which would peruse the message types put away in assistance interfaces.

When done, select the sort of planning and import the message planning made.

Click on SAVE and Enact.

ESR Items creation done. We should begin with the Reconciliation Items improvement.

5. Build Communication Channels:

Sender Communication Channel:

Open the Combination Registry – > Snap on Make New symbol and pick Correspondence Channel.

Give the channel a reasonable channel name and namespace and tap on Make. Pick Connector type as Record and Source Radio button.

Message Convention – Document Content Transformation

Under the Source tab, give the document way and the record name design.

Under the Handling tab, give the nature of administration (for async interfaces, it should be Precisely Once all together/Precisely Once). In the event that Precisely Once all together is picked, you should give a line name in which the connection point will be handled.

Survey Stretch – 3600 (in secs)

Handling Mode – File and notice the Chronicle Index.

Void Document Dealing with – In the event that vacant record is set in AL11, this boundary can be kept up with for the expected move to be made in such cases. Default – Don’t make message

In the event that Message Convention is picked as Document Content Transformation, an extra tab will be empowered as Record CONTENT Change.

Content Conversion Tab:

Document Name  – <Message Type Name>

Document Namespace – <Message Type Namespace>

Document Offset – <No. of lines to be skipped in the file – from top>

Recordset Name – <Root node name>

Recordset Structure – <Node name and its occurrence – 1 means node will appear 1 time and * means multiple>

Keyfield Name – <Field which must be there in file to start content conversion>

In the above picture, we can see that the primary hub is header, and it happens 1 time. There are 4 significant properties to be characterized to change it over completely to XML values.

<Node_Name>.fieldFixedLengths

<Node_Name>.endSeparator

<Node_Name>.fieldNames

<Node_Name>.keyFieldValue

Push on the Add column symbol and supplement the underneath shown lines.

The following is the Level record.

As we have referenced the Record Counterbalanced to 1, the primary line will be skirted in the change.

Next line is the header line. As we have referenced as RECORDTYPE as the key field name, framework will check for keyfield esteem present in document or not. On the off chance that present continue with the change or, in all likelihood skirt the line.

For this situation, keyfield esteem we referenced is H, and its additionally present in the level record at line 2. Subsequently continue for change.

First field name is record type and its length is 1, so record type XML label will contain esteem as H.

Next field name is CurrencyCode, and its length is 3, so in level document after H, 3 scorches will be managed and put away in CurrencyCode XML tag.

Next field in header is filler and its length is 76 which implies in level document there perhaps spaces in that first line end, and that is put away filler XML tag.

Also, after that no field name is accessible, framework will check for “endSeparator” property. As we have given “nl” (new line) as the separator, after that first line closes, framework will close the header tag and continue with the following XML tag referenced in the recordSetStructure.

1 – Record name and namespace

2 – RecordSet Name

3-According to the properties we gave, XML structure is framed. Filler is in void tag in light of the fact that XML wont store clear qualities.

Same way the other XML labels are filled. Next is replacementPartsPrices and its event is * and that implies until the condition (keyFieldValue not in level record line) comes up short, this label will continue to populate.

The following is the properties for replacementPartsPrices:

The keyFieldValue is 7. Framework will check for 7 toward the beginning of each line and continues with the transformation.

In the level record you can see, there are numerous 7 toward the beginning of the line and that many labels will show up for replacementPartsPrices.

Furthermore, that is all there is to it for Record Content Change. We will continue with the beneficiary correspondence channel.

Click and Make New – > Correspondence Channel – > Pick Collector radio button and connector type as SFTP.

Give the SFTP server subtleties:

Server, Port, Break, Server Unique mark.

Validation mode as Secret key OR Confidential KEY OR BOTH.

We pick PRIVATE KEY.

Prior to making the key coordinates, how about we fill the other fields.

Filename and record way.

If timestamp required toward the finish of the filename, actually take a look at the choice “Add timestamp to filename”.

For making the SSH Key coordinates, how about we download the Clay programming.

Follow this connect to create the SSH key matches and they take care of the import cycle in SAP PI/PO.

Enter the keystore view and name in recipient correspondence channel and snap on SAVE and Order.

6. Build Integrated Configuration (ICO):

Click on NEW – > Coordinated Design.

Give the Coordinated design name and namespace. It ought to be indistinguishable from the ESR Administration Connection point name and namespace.

Import the shipper divert and in next tab, select the business part under which the recipient correspondence channel is made.

Determine recipient condition if any.

Import the Activity planning from ESR. Activity planning will naturally show assuming you have offered right Assistance Connection point name and namespace while characterizing Incorporated arrangement name and namespace.

Import the recipient correspondence channel.

Click on SAVE & ACTIVATE.

That is finished. We have made Document to SFTP interface without any preparation. We should test it.

7. Testing the Interface:

Place a level record in AL11 area and notice the registry way in shipper correspondence channel for the channel to get it and furthermore the document way, with the goal that a similar document isn’t surveyed sometime later.

Begin the source correspondence channel and check whether the document gets gotten.

To see the document content change and effective planning, explore to the message and snap on OPEN MESSAGE button. Under the payload choice you can see the various variants of the payload.

0 – represents the before-mapping version

2 – represents the after-mapping version

I trust you were able to learn about this intriguing topic in “SAP PO for Beginners Part – 10 – Interface Development – File (with File Content Conversion) to SFTP.“ I hope the insights provided have been valuable in understanding how to develop and manage file interfaces with content conversion to SFTP.

YOU MAY BE INTERESTED IN

ABAP Test Cockpit(ATC) – Introduction and Steps

SAP ABAP future in next coming years

Power of Parallel Cursor in SAP ABAP

SAP BTP: Handling the Business Logic in RAP – Part 1