This is the 6th post in my blog series on “SAP PO for Beginners Part 6 – Complete Overview on Integration Directory (ID)”. In this post we will see the outline on Combination Catalog and furthermore be covering on building IDoc to Record interface.
To put it plainly, underneath is the substance we will be intricate in this instructional exercise: SAP PO for Beginners Part 6 – Complete Overview on Integration Directory (ID)
- Accessing ID
- Common terms used in ID
- Communication Channel Creation
- Integrated Configuration (ICO) Creation
- Message Monitoring
1. Accessing ID: SAP PO for Beginners Part 6 – Complete Overview on Integration Directory (ID)
To access ID, navigate to home page http://<host>:<port>/dir/start/index.jsp and click on Integration Builder link which would open using Java web start by downloading a temporary JNLP file and clicking on it would open ID.
Assuming you investigate the dropdowns accessible in ID contrasted and ESR, where in ESR all are custom, and that implies you will make programming part and renditions in SLD and will import it, yet in ID, its steady. There are 2 fundamental dropdowns which we will utilize most.
1 – Communication component without Party
2 – Integrated Configuration
2. Common terms used in ID:
Prior to bouncing into the connection point advancement, we should see based on conditions that we utilize regularly in ID.
Correspondence Part:
Correspondence part is a typical term that alludes both source and collector frameworks. It is where we pronounce the source and beneficiary framework subtleties.
Correspondence channel:
Correspondence channel holds the design subtleties or the association subtleties of the source or beneficiary framework.
Business Framework:
Business Framework relates to the ECC/S4H framework. Here we will make the ECC framework channels.
Business Part:
Business part holds the outsider association subtleties.
Incorporated Arrangement:
Incorporated arrangement is otherwise called ICO. In ICO, we will gather the source and beneficiary channels and make up a connection point. Likewise, we will connect the ESR content in here, if material.
Connectors:
Connectors empower the runtime motors of SAP NetWeaver PI to speak with various applications. You just require a connector to speak with SAP frameworks and with outside frameworks. For eg: To speak with webservice, we have connectors like Cleanser and for interfacing with FTP, we have SFTP, FTP connectors.
- Correspondence Channel Creation:
Making a correspondence channel is a typical term, on the grounds that the main part in correspondence channel is the connector and it fluctuates in light of the necessity. For e.g.: Say I’m getting IDOC messages from SAP ECC and I’m changing over it into XML and putting away the items in the IDOC into Document and setting it in SFTP.
Here, in source we use IDOC connector as we get IDOC messages and in getting side we use SFTP connector. Thus, the arrangement for IDOC connector will be unique and of SFTP will be unique. It’s impractical to go through every single connector design subtleties.
We will fabricate a connection point for the situation we worked in ESR in past post.
Situation:
Shipper – ECC (moving IDOC)
Middleware – PO
Recipient – Outsider (Record sent in type of XML)
Mode – Nonconcurrent
In the first place, we will make source and beneficiary correspondence channel .
Source Channel:
There is no need of building a different association for IDOC, as we have previously designed the IDOC outbound and inbound association among ECC and PO framework in POST #4. Thus, an example IDOC point of interaction is enough only for building the coordinated setup as shipper channel is compulsory to be given.
Prior to continuing into source channel, we want to import the business framework we made in SLD. For bringing in, follow the underneath steps:
The business frameworks will get naturally enlisted in SLD. It will be finished by Premise group.
In ID, explore to Correspondence Part Without Party – > Business Framework. Right snap on Business Situation and pick Appoint Business Frameworks, which will drill down all business frameworks enlisted in SLD. Select the required and click on FINISH.
When the business situation shows up, right snap on it, and pick NEW. Make Article discourse box shows up, where pick correspondence channel under Coordinated effort Profiles.
Provide communication channel name and click on Create.
Click on the button at the end of the Adapter type field to get the list of available ADAPTERS in PO system like REST, IDOC_AAE, HTTP_AAE, File, SFTP, FTP, JDBC etc.. For our requirement, choose IDOC_AAE adapter.
Select the Source radio button, as it is a shipper channel.
TRANSPORT Convention – Transport convention implies how the messages are moved so they can be handled by the Mix Motor. Like FTP/NFS.
MESSAGE Convention – Message convention implies how the messages are being handled. like Record.
Leave the other boundaries for what it’s worth. Click on SAVE and Actuate.
Recipient Channel:
Make another business part by exploring to Correspondence Part Without Party – > Business Part. Right snap on Business Part and snap on NEW.
Naming show:
For Business framework – BS__
For Business Part – BC__
Give the business part a reasonable name and tap on Make. When made, right snap on it and snap on NEW – > Correspondence channel.
The connector type in beneficiary channel is SFTP.
Select the Receiver Radio button.
The vehicle convention is SFTP.
Message convention – Record and Document Content Change.
In this situation, we will utilize Record. Record content change will be utilized when you need to switch a level document over completely to XML. For this situation, we are getting IDOC and in planning, we are switching over completely to XML. Thus, no need of Record CONTENT Transformation.
We have three tabs in here: Objective, Handling, Progressed.
Objective:
For associating with the collector SFTP, we want IP subtleties: IP, Port, Server Unique mark, Validation System which should be filled in Objective tab.
We have three kinds of Validation System for SFTP: Secret key, SSH Key matches, Secret key + SSH key.
For SSH key matches, either get the public key from merchant or produce another sets of keys from Clay programming and introduce the confidential key in NWA and share the public key to seller.
For producing SSH key pair and transferring keys to NWA SAP PO, really look at the this connection : Create and Involve Client Endorsement Validation in SAP PI/PO – A Fast Aide
Once transferred, you will have PRIVATE KEY VIEW and Confidential KEY Passage. Enter those qualifications in the SFTP beneficiary channel.
Once done, next is the filename and file path that we need to provide.
Handling:
In Handling tab, we have two areas: Handling Boundary and operating system order
In Handling Boundary, you can determine whether the document you send ought to contain the timestamp or the message ID, in the event that Indeed, empower the checkbox.
Break and time unit boundaries will be referenced as a matter of course as 30sec. Leave all things considered.
Void document dealing with – On the off chance that any unfilled record is passed from Source, this setting will become an integral factor. You can either disregard it or toss a mistake in PO observing screen that the record is unfilled or doesn’t contain information.
Progressed:
In Cutting edge tab, we have the variable replacement and connector explicit message credits which are the central thing one need to be aware.
Variable Replacement:
Variable Replacement permits you to powerfully set the objective record name plan or target catalog area by subbing a variable placeholder with a worth from the XI message payload or XI message header.
Connector Explicit Message Credits:
ASMA or connector explicit message ascribes are extra data about the message. Every connector has set of ASMA and these are accessible in message header. This data isn’t situated in that frame of mind of the message, however in extra message header fields. You can set the qualities in the source connector and utilize the characteristics in the beneficiary connector.
Once finished, click on SAVE and Enact. Both source and collector correspondence channels are prepared at this point.
We should begin the ICO (Incorporated Setup) settings.
4. Integrated Configuration (ICO) Creation:
Explore to Incorporated Arrangement dropdown and right snap on it and pick NEW.
Select the source correspondence part name.
Note: For Connection point name and namespace, give the specific name and namespace of the source administration interface (for our situation it is IDOC name, as we didn’t make SI-Outbound), then, at that point, just the activity planning will be picked naturally. If not, it won’t show.
When name and namespace gave, click on Make.
Determine the source correspondence direct in Inbound Handling tab.
In the beneficiary tab, incorporate on the off chance that any condition is there or not. Like, on the off chance that a field is accessible or filled, just the document should be communicated, else no information ought to be sent. The message ought to be tossed as a mistake or cautioning or disregarded.
The above given XPATH articulation is:
/YLFINV/IDOC/E1EDK01/YLSINVH/OPPORTUNITY_ID ≠
On the off chance that Open door ID doesn’t equivalent to purge esteem, then continue with transmission, else don’t continue with transmission and overlook (radio button chose).
In beneficiary connection point tab, select the correspondence part and snap on the activity planning button and select the recommended OMs.
Select the receiver communication channel.
In cutting edge settings tab, empower the logs so that logs and payload will be accessible in PO Message checking screen.
5. Message Monitoring:
Explore to URL: http://:/dir/begin/index.jsp and click on Design AND Checking HOME – > Under Observing tab, Connector motor sub-tab – > click on Message Observing connection.
Click on Open Message to view the payload.
Case where OPPORTUNITY ID is not available :
As no OPPORTUNITY ID is not available, no mapping done.
Trust, you found out about Idoc to Record Point of interaction design and cycle. We attempted to cover it without any preparation and fabricated the IDoc to Record interface Start to finish. Assuming that you feel somewhat wary, go ahead and put them in the remark segment underneath.
YOU MAY LIKT THIS
ALE – Error Handling Through Workflow
IDoc in SAP MM (Material Management)
WhatsApp us