SAP PO for Beginners Part 8 – Configure User Defined Search Criteria
This is the eighth post in blog series on “SAP PO – Cycle Organization for novices”. In this post we will see the how to design bit by bit on looking for Payload esteem by making client characterized search. Presenting SAP PO for Beginners Part 8 – Configure User Defined Search Criteria.
So, underneath is the substance we will be intricate in this instructional exercise:
- Overview
- User Defined Message Search Configuration
1. Overview:
Before going for SAP PO for Beginners Part 8 – Configure User Defined Search Criteria. You would have most certainly got this solicitation from functionals like, to check assuming this PO number is communicated or this client reference number is shipped off SFTP, where merchant asserts that the document was not gotten. We would explore the Message screen, go to that particular connection point transmission date and explore to the particular message. This is conceivable on the off chance that you have fewer messages. In any case, imagine a scenario where you received 1000s of messages communicated on that specific day ? You would say like, then I will channel by time. Imagine a scenario where functionals didn’t have a clue about the transmission time, the majority of the case.
At these sorts of situations, having a custom quest rules arrangement for that interface is better. That custom pursuit models is known as “Client Characterized Message Search”. Client Characterized search is only looking for an expected message in a connection point in light of the substance of the payload.
2. User Defined Message Search Configuration:
Navigate to PO Home page -> NetWeaver Administrator -> SOA -> Monitoring -> User Defined Message Search Configuration, where you will be taken to Overview page.
Client Characterized Message Search config outline screen show up, where you can see the rundown of custom message search assembled and void if not.
There are 2 segments where you will give data:
- Interface Name and Component Information
- XPath of the Payload Content
Under the rundown of channels, click on NEW to make a custom inquiry measure and tap on Make button.
The test interface which I took was an inbound EDI interface (EDI document to ABAP Intermediary), where I need to look for Receipt number. I won’t give shipper and beneficiary part/party. Straightforwardly interface name and namespace.
Click on SAVE once finished. In this way, the main area is finished on choosing the connection point. Second is that we want to give the XPath of the chronic number.
By choosing the recently made interface, look down and snap on NEW under Search Models tab.
Give name and depiction.
XPath is the design of the field in the payload. The XPath contains the root namespace followed by the hub and field name.
When the XPath structure is characterized, next is to give the namespace prefix.
Explore to the Prefixes tab and snap on NEW. Give the connection point namespace and the prefix, which you can find in the payload ns0/ns1/ns2.
When all finished. Click on Enact for changes to become effective. Presently you will actually want to look for the message receipt numbers for that point of interaction. This search will work for messages which came after you actuated. In this way, for the old ventures to work, there is a choice called “Ordering Choices”.
Click on Ordering Choices and select the date range for which the hunt standards ought to work in the past dates.
Whenever date is picked, click on the Starting Requesting button to start the establishment control of considering the old payload as well. To be know all about the Requesting Status, click on the Requesting status button, which would enlighten whether the establishment work is running or wrapped up.
Once got done, investigate to the Message Actually looking at Presentation page – > PI Messages tab – > Snap on State of the art in right side corner. Also select the stretch of time of the payload, like this week, month or year.
On clicking Advanced, select the Client described Search Rules checkbox and click on Add predefined button which would jump up a trade box to pick and enter the pursuit regard.
Enter the receipt number in the value data field and snap on okay and GO to channel the receipt archive.
Click on the OPEN MESSAGE to affirm that the separated payload is a right receipt document.
That is all there is to it. This is the way the receipt document can be sifted through Client Characterized Search Rules. This is only a model. We can make any client characterized search.
It might be helpful:
