× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Task authorization by company
  • From: "OleBlighty" <oleblighty@xxxxxxxx>
  • Date: Thu, 9 Dec 1999 22:28:50 -0800

Dan,

Missed the explorer bit.  Ooops, sorry :)

FI.  The posting rules within FI are setup based on application code (AU,
IN, PM are the standard applications defined).  In each of these
applications you will find the FI processing program FI502.  I believe that
this programs checks the application you are signed by looking at the LDA.
It then goes to the rules based on the application code.  If, for instance,
you wanted to post Invoices from application 'PA', you would need to define
'PA' to FI as it wouldn't find any rules.

INP96 is the file Inventory movements get posted from.  As long as FI is NOT
submitted from 'PA' then any records in INP96 will be picked up when 'IN' FI
is run.

Clear as mud :)

Regards,

Mark.

----- Original Message -----
From: Dan Thomas <DThomas@lpw-mdi.com>
To: <JBAUSERS-L@midrange.com>
Sent: Thursday, December 09, 1999 9:41 PM
Subject: RE: Task authorization by company


> Mark, thanks for responding.  However, as I mentioned, we use System 21
> Explorer Roles, so server session menu authority is not an option.
Explorer
> is only affected by task authority.  The AFI part seems kind of odd to me,
> but I'll certainly check it out.  I think our G/L updates via AFI for
> inventory adjustments are done by a batch process that came out of some
> inventory movements file (INP96).  I don't understand why the module which
> has the task should be an issue.  Most of our AFI updates are generated by
> our invoicing process.  For us, almost all items are on consignment from
our
> supplier and we don't generally update G/L with inventory receipts or
> adjustments anyway.
>
> I realize that program modifications were an alternative.  The catch is
that
> we have many programs needing this capability.  I was simply mentioning
> physical inventory adjustments as an example.  I'll continue to check this
> out and let everyone know what I find out.
>
> -----Original Message-----
> From: OleBlighty [mailto:oleblighty@home.com]
> Sent: Thursday, December 09, 1999 6:54 PM
> To: JBAUSERS-L@midrange.com
> Subject: Re: Task authorization by company
>
> Dan,
>
> A predicament to be sure.  The task/menu authorization is
> not as flexible as
> I would like sometimes and your specific case highlights
> this.
>
> Personally, I would try to stay away from creating a new
> application (PA)
> because of the AFI ramifications.  Most companies I deal
> with update General
> Ledger through AFI for all/most Inventory movements.  AFI
> does not know
> about application 'PA' without modification and a new
> version of FI502.
>
> I would look at two options.  Firstly, instead of a new
> application, create
> new Inventory Movement tasks and a new Menu within the 'IN'
> application.
> You should then be able to take authorization away from the
> Menu Option
> itself .  I think this should work but haven't tried it
> (actually, you may
> not need to define new task codes).  Secondly you could use
> the
> pre-processing option on the task definition and write your
> own simple
> authority checking program.  You could use the Inventory
> parameter file
> INP15 to hold the user/company authority.  This
> pre-processing program could
> simply set a flag in the LDA to say if authorized or not.
> Then, of course,
> IN009 and IN079 would need a modification to check the flag
> and return a
> message if the user is not authorized.
>
> As I say, I am not on an AS/400 right now so I can't confirm
> that these
> options will work.  Good luck.
>
> Regards,
>
> Mark.
>
> ----- Original Message -----
> From: Dan Thomas <DThomas@lpw-mdi.com>
> To: <JBAUSERS-L@midrange.com>
> Sent: Thursday, December 09, 1999 2:17 PM
> Subject: Task authorization by company
>
>
> > We have a need for users to be authorized only in certain
> companies for
> some
> > tasks like inventory maintenance and inventory
> adjustments.  JBA allows
> > authorization by user/task and user/company/module.  The
> tasks we want
> > restricted in certain companies are part of module for
> which these same
> > users need to be able to do other tasks for all tasks.
> Our solution was
> to
> > create a new module ('PA' for physical adjustments) and
> make copies of
> those
> > tasks into this new module.  We'll then authorize users to
> module 'PA'
> only
> > for those companies where is needed.  We de-authorize all
> users for the
> > original tasks.  By the way, we use JBA System 21
> Explorer.  I would love
> to
> > hear from anyone that has had a better solution to this
> requirement: To
> > allow a given user to be authorized to physical inventory
> adjustments in
> > Company A and not in Company B, while being able to do
> other inventory
> > functions (reports and inquiries) in both companies.
> >
> > Dan Thomas
> > Sr. VP Information Systems
> > Medical Distribution, Inc.
> > 4500 Progress Blvd
> > Louisville, KY  40218-5058
> > Phone (502) 454-9013 ext 120
> > email  DThomas@lpw-mdi.com
> >
> > +---
> > | This is the JBA Software Users Mailing List!
> > | To submit a new message send your mail to
> JBAUSERS-L@midrange.com.
> > | To subscribe to this list send email to
> JBAUSERS-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> JBAUSERS-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner:
> doug333@aol.com.
> > +---
>
> +---
> | This is the JBA Software Users Mailing List!
> | To submit a new message send your mail to
> JBAUSERS-L@midrange.com.
> | To subscribe to this list send email to
> JBAUSERS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> JBAUSERS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner:
> doug333@aol.com.
> +---
> +---
> | This is the JBA Software Users Mailing List!
> | To submit a new message send your mail to JBAUSERS-L@midrange.com.
> | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
JBAUSERS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: doug333@aol.com.
> +---

+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.