LBI Back Office Reports, publish more than 1 rpt from same job

I agree to Lawson support. Only if a back office report has burstable tags in the program can it be burstable. Not all programs can be burst. At the back of the reporting services manual there is a list of programs that defines which back office reports can be bursted.

To clarify:

This is a custom COBOL report that generates 2 print files NOT a canned Lawson program.

All the necessary workflow coding is including so that it will create the final output files with the necessary tags.

I am attempting to find out from all the great reporting services experts if it is possible to publish the 2nd report. If it is possible, how would I specify the 'listing' report?

Thanks in advance for your assistance.

Elizabeth Ardito
Systems Analyst
Middlesex Health System

I encountered this challenge a few years back, and I'm pretty sure there is a feasible solution. I need to go through old emails/notes and see what I can find.

Your custom program shouldn't behave any differently from a standard Lawson program, and as long as you have the tags in the output, it should be burstable.
Have you tried publishing it via LBI yet?

Depending on your versions of LSF9 and LBI, you might have to fiddle with creating a .cfg file for the custom program to make sure the requisite .xml files are created in the print directory. That is what LBI reads to determine the print file structure. Have you tried publishing it via LBI yet?

Bursting and publishing are two different things. Presuming for a moment that you don't have to burst (i.e. "filter") the data in the report, one option would be to simply publish the webrpt urll to the print file.

Have you tried creating a URL in LBI directly to the print file?

Have you looked to see whether the custom program has a .cfg associated with it? If the second report generates a .prt and it has the associated tags it can be published on LBI. There is a bldfxfiles utility that is used to publish a back office report. You may need to look at that as well as the FTP utility that picks up the files from the print directory to move it to the LBI server.

First off, I thanks for all the responses.

We are on lbi version 9.0.4.2.93.

I have completed setup the best that I can within lbi. When I published the new report and get to the report field, I clicked on the yellow box with the ... and entered the report name of listing to match what is in the print manager and workdef (not sure if this is correct or not but my best guess).

I checked the $LAWDIR/system/ers/backoffice/<pl>/publish.csv and it did update with the new job name; checked the server where reporting services is and it did create a new folder.

Next, I ran the program again, checked $LAWDIR/system/ers/backoffice/<pl>/ and there was NO broadcast.csv file created; checked the print manager and both reports have the necessary tags in the output; I checked the print directory and there is a listing.xml file.

I do not create separate .cfg files as we have $LAWDIR/system/rpt.cfg setup for all reports.

Thanks!

If the broadcast.csv file is not generated then there may be 2 issues. Can you check the bldxffiles utility and then check the ftp utility too.

Sometimes the broadcast.csv file is generated so fast and picked up and moved that you may not see it.

In the past when we have done this for customized programs we have tried to troubleshoot on our own. Have you tried the whole process with a CU201 program to make sure that a recommended lawson program and outout works before trying it on a custom cobol program.

We have over 300+ reports setup currently in reporting services, some of them canned reports which have been cloned and the necessary workflow code added others are custom programs.

This is our development environment and have the retrieval of files set to 5 minutes so I know in fact that the broadcast file is not being created at all. Also, there are no files on the lbi server being updated.

Thanks! for your suggestions.

So there are no canned unmodified Lawson reports (e.g. CU201) which are
currently broadcasting from your development environment to your LBI
server? Is this correct?

If so, have you verified the ftp settings between the RS "Lawson Data
Connection" and what is actually configured on the LSF development server?

On Wed, May 23, 2012 at 11:45 AM, <forums-epm-lbi@lawsonguru.com> wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> Lawson
> Business Intelligence/Reporting/Crystal Forum Notification A message was
> posted to a thread you are tracking. *RE: LBI Back Office Reports,
> publish more than 1 rpt from same job* Posted by: *Elizabeth Ardito*
> 05/23/2012 10:45 AM We have over 300+ reports setup currently in
> reporting services, some of them canned reports which have been cloned and
> the necessary workflow code added others are custom programs.
>
> This is our development environment and have the retrieval of files set to
> 5 minutes so I know in fact that the broadcast file is not being created at
> all. Also, there are no files on the lbi server being updated.
>
> Thanks! for your suggestions.
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...1-rpt-from-same-job/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

Yes I stated that we have 300+ reports setup some of them canned some of them custom.

I have setup cu201 and it burst correctly.

All the other reports I have setup are bursting correctly. The only issue I am having is with the special second report that I want to setup.

thanks!

You mentioned in a couple of steps back about clicking on the "..." when publishing. I think you need to use the drop down to the left of that to select the different output file. =

When I do that, only the main report with the .prt displays.

That is the part that I am stuck on as I am not sure what to do there on the second report.

Thanks!

Does your custom report produce a file with an extension on it? I've found in some cases Lawson expects to see an extension of some sort... *Just an idea, not sure if it is applicable here or not.

Ok, that helps. Hang in there.

My apologies in advance. You may have already answered this, but does the
main rpt file broadcast as expected?

If so, have you tried generating a second *.prt file? I have some
high-level instructions on how if you need them.

On Wed, May 23, 2012 at 2:31 PM, <forums-epm-lbi@lawsonguru.com> wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> Lawson
> Business Intelligence/Reporting/Crystal Forum Notification A message was
> posted to a thread you are tracking. *RE: LBI Back Office Reports,
> publish more than 1 rpt from same job* Posted by: *Elizabeth Ardito*
> 05/23/2012 01:24 PM When I do that, only the main report with the .prt
> displays.
>
> That is the part that I am stuck on as I am not sure what to do there on
> the second report.
>
> Thanks!
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...1-rpt-from-same-job/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

Can you post a screenshot of the contents in the print folder for that job?

Yes I setup the main .prt report and it bursts normally.

I do not know how to make the second report appear in the print manager with a .prt extension. Any assistance with this would be great

Hopefully the screen shot of the directory will upload properly.

You will need to set the workdef for this "listing" file to use the WsFld, match it to a working-storage field, and include code in your MH672PD to override the default "listing" filename.

Elizabeth,

Here are the high level steps get a 4GL program to produce a second rpt
file in the print manager:
1. Define the additional report(s) in workdef, file type = Printer
2. In the .rpt file, clone the lines from $REPORT thru $ENDRPT
3. In the clone, under the $REPORT put a line: $PRINTFILE xxxx where
xxxx = the workdef file name
4. In the PD do this: OPEN OUTPUT xxxxx-FILE.




On Thu, May 24, 2012 at 5:51 AM, <forums-epm-lbi@lawsonguru.com> wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> Lawson
> Business Intelligence/Reporting/Crystal Forum Notification A message was
> posted to a thread you are tracking. *RE: LBI Back Office Reports,
> publish more than 1 rpt from same job* Posted by: *Elizabeth Ardito*
> 05/24/2012 04:42 AM Yes I setup the main .prt report and it bursts
> normally.
>
> I do not know how to make the second report appear in the print manager
> with a .prt extension. Any assistance with this would be great
>
> Hopefully the screen shot of the directory will upload properly.
>
>
>
>
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...rpt-from-same-job/2/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

Thanks John for the instructions. I am in the midst of an environment upgrade and I am hoping in the next few days to get a chance to make the necessary coding changes and see if this will make the report display in reporting services as a report selection.

Thanks everyone for all the assistance.

I am unable to get the program code correct to 'match it to a working-storage field, and include code in your MH672PD to override the default "listing" filename.

I have spent enough time attempting to figure this out without success so I am going to split the program into 2 separate ones to get both reports burst.

Thanks again for all the assistance in helping to get this to work.

Elizabeth Ardito