• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Integration of SSRS reporting with JDedwards 9.1 version using BSSV

BhushanC

Active Member
Dear JDElist,

Our client has implemented E1 9.1 version and they would like use JDE BSSV through SSRS (SQL Server Reporting Services).

Please tell us, how we should call JDE web services from SSRS.

We are using following query function to call simple address book JDE BSSV from SSRS; however we are not getting correct data/output from below query function.


********************SSRS Query to JDE address book BSSV ******************
<query>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:eek:rac="http://oracle.e1.bssv.JPR01000/" xmlns:java="java:eek:racle.e1.bssv.JPR01000.valueobject" xmlns:java1="java:eek:racle.e1.bssv.JR010020.valueobject">
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
soapenv:mustUnderstand="1">
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<orac:getAddressBookElement>
<java:Entity>
<java1:EntityId>5562256</java1:EntityId>
</java:Entity>
</orac:getAddressBookElement>
</soapenv:Body>
</soapenv:Envelope>

</query>

********************SSRS Query to JDE address book BSSV ******************

Thanks in advance for your help.

Best regards,

Bhushan
 

nkuebelbeck

VIP Member
It appears as though you are missing the security header username/password. was that left out from the post intentionally?

PROTIP: Use SoapUI to test your bssv before integration. http://www.soapui.org/

here is a copy of a valid header with valid WS-SECURITY

<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" soapenv:mustUnderstand="1">
<wsse:UsernameToken>
<wsse:Username>[USERNAME]</wsse:Username>
<wsse:password>[PASSWORD]</wsse:password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
 

BhushanC

Active Member
It appears as though you are missing the security header username/password. was that left out from the post intentionally?

PROTIP: Use SoapUI to test your bssv before integration. http://www.soapui.org/

here is a copy of a valid header with valid WS-SECURITY

<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" soapenv:mustUnderstand="1">
<wsse:UsernameToken>
<wsse:Username>[USERNAME]</wsse:Username>
<wsse:password>[PASSWORD]</wsse:password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>


Should we JDEdwards user name and password WS-SECURITY
 

BhushanC

Active Member
I am getting attached output.

Hi,

After adding user name and pwd I am getting attached output from SSRS reporting.

Please can you advice on this.

Thanks ,

Bhushan
 

Attachments

nkuebelbeck

VIP Member
Hi,

After adding user name and pwd I am getting attached output from SSRS reporting.

Please can you advice on this.

Thanks ,

Bhushan
I don't know anything about SSRS reporting. The calling function (in this case your SSRS?, needs to be able to process the returned xml soap document from BSSV)

Turn on debug on the BSSV and you will see the request come in, and the request leave.
 

Larry_Jones

Legendary Poster
I guess I'm not very educated and you have a amazing client that understands these architecture thingies but ...

Why do they want to do reporting through business services? Is the database not accessible to SSRS?
 

BhushanC

Active Member
Hi,
They are looking BSSV because; SSRS developers have to write very large SQL store procedure in SSRS for our JDE business functions to display data for reporting.
We are using existing business function in JDE, but they don't have any option in SSRS to fetch processed JDE data.
Do you have any other option on this?

Thanks and best regards,
Bhushan
 

ONYX

Well Known Member
Hi,
They are looking BSSV because; SSRS developers have to write very large SQL store procedure in SSRS for our JDE business functions to display data for reporting.
We are using existing business function in JDE, but they don't have any option in SSRS to fetch processed JDE data.
Do you have any other option on this?

Thanks and best regards,
Bhushan
Hello Bhushan,
It might be a convoluted and ugly but what about old good JDE temporary/work tables.
JDE UBE pushes data to work table(s), SSRS picks up data and creates nice looking reports.
 

Larry_Jones

Legendary Poster
You know, I still don't get it.
Why write reports that call web services -> business functions?

#1` it will be very slow
#2 Its not less complicated than joining tables together and writing where clauses in the report writer
#3 BSFNs / web services are not well documented. Either way you're going to have do research and trial and error.
#4 JDE's BSFNs tend to be specialized and oriented toward use in transactional UBEs and applications. Those that aren't are basically pretty simple to duplicate the logic in Crystal / SSRS.

I guess the only justification I can think of is that Database Access isn't available - thanks to the King's New Suit (AKA the "Cloud").

Just had to get that off my chest ;-)
 

BOster

Legendary Poster
You know, I still don't get it.
Why write reports that call web services -> business functions?

#1` it will be very slow
#2 Its not less complicated than joining tables together and writing where clauses in the report writer
#3 BSFNs / web services are not well documented. Either way you're going to have do research and trial and error.
#4 JDE's BSFNs tend to be specialized and oriented toward use in transactional UBEs and applications. Those that aren't are basically pretty simple to duplicate the logic in Crystal / SSRS.

I guess the only justification I can think of is that Database Access isn't available - thanks to the King's New Suit (AKA the "Cloud").
I tend to agree. But I can think of some situations where you may want to call E1 Business Logic even for reporting purposes. For example if you had some kind of customer pricing report you may want to call the BSFN that calculates price instead of trying to reverse engineer all the advanced pricing tables and re-create all that logic in T-SQL.
 
Top