Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

multiple production objects in one project?

6 posts in General Discussion Last posting was on 2008-11-13 14:55:29.0Z
John Fritsch Posted on 2008-10-10 14:46:21.0Z
Sender: 1a66.48ef66be.1804289383@sybase.com
From: John Fritsch
Newsgroups: sybase.public.impact
Subject: multiple production objects in one project?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <48ef6abd.1acf.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 10 Oct 2008 07:46:21 -0700
X-Trace: forums-1-dub 1223649981 10.22.241.41 (10 Oct 2008 07:46:21 -0700)
X-Original-Trace: 10 Oct 2008 07:46:21 -0700, 10.22.241.41
Lines: 87
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2133
Article PK: 230211

Hi everyone. I've been presented with somewhat of a
challenge and before I get too deep into tackling it, I
wanted to throw it out to the user group to see if anyone
has a better idea for doing what I need to do.

I need to create one, two or possibly three output
transactions from one input transaction, based on certain
conditions which can easily be identified.

If I receive a P01 and ACCTC then I need to send an A13, a
P01 AND an A03. There will be no change in the data in the
output transactions - except I will change the P01 to the
respective new event type for each.

If I receive a P01 and OPACC then I need to send a P01 and
an A03.

Otherwise, I'll send the message on as whatever event type
in came in as.

The messages have to be sent in the order listed above.

I have MSH, EVN, PID, NK1, MRG and PV1 segments to build and
there are other qualifications that universally apply to all
output transactions.

My initial thought, keeping everything tucked nicely inside
the project, was to create a different prod obj for each
transaction that would ever need to be sent and add the
quals to each so that each would only run under the
condition specified.

So prod obj #1 would have as one of it's quals -

If P01 && ACCTC return 1;
In the output all the rules would run as normal except
I'd change P01 to A13.


Prod obj #2:

If P01 && ACCTE return 1;
In the output all the rules would run as normal and P01
would remain as P01.


Prod obj #3:

If P01 && ACCTE return 1;
In the output all the rules would run as normal except
I'd change P01 to A03.


Prod obj #4:

If P01 && OPACC return 1;
In the output all the rules would run as normal and P01
would remain as P01.


Prod obj #5:

If P01 && OPACC return 1;
In the output all the rules would run as normal except
I'd change P01 to A03.


Prod obj #6:

(assuming all other basic quals met)
In the output all the rules would run as normal.

So that seems like a lot of work and maintenance and
confusion down the road with code changes, log extraction,
etc.

My other thought was to try to handle it within the aim but
it's a lot more difficult to identify the fields I need to
interrogate.

If anyone understands what I'm trying to do and has any
ideas I'd really appreciate hearing from you.

Feel free to post the reply here and/or email me @
john.fritsch@lvh.com

Thanks!


Alex Bear Posted on 2008-10-13 11:32:56.0Z
Sender: 318d.48f3306e.1804289383@sybase.com
From: Alex Bear
Newsgroups: sybase.public.impact
Subject: Re: multiple production objects in one project?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <48f331e8.31d8.1681692777@sybase.com>
References: <48ef6abd.1acf.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 13 Oct 2008 04:32:56 -0700
X-Trace: forums-1-dub 1223897576 10.22.241.41 (13 Oct 2008 04:32:56 -0700)
X-Original-Trace: 13 Oct 2008 04:32:56 -0700, 10.22.241.41
Lines: 98
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2134
Article PK: 230210

John,

I would suggest a single production object to handle your
situation. Since all qualifications except the transaction
type and command combination are universal. I would then add
a filter to the MSH message type field that does the
appropriate comparison and conversion routines that you
need.

Alex Bear

> Hi everyone. I've been presented with somewhat of a
> challenge and before I get too deep into tackling it, I
> wanted to throw it out to the user group to see if anyone
> has a better idea for doing what I need to do.
>
> I need to create one, two or possibly three output
> transactions from one input transaction, based on certain
> conditions which can easily be identified.
>
> If I receive a P01 and ACCTC then I need to send an A13, a
> P01 AND an A03. There will be no change in the data in
> the output transactions - except I will change the P01 to
> the respective new event type for each.
>
> If I receive a P01 and OPACC then I need to send a P01 and
> an A03.
>
> Otherwise, I'll send the message on as whatever event type
> in came in as.
>
> The messages have to be sent in the order listed above.
>
> I have MSH, EVN, PID, NK1, MRG and PV1 segments to build
> and there are other qualifications that universally apply
> to all output transactions.
>
> My initial thought, keeping everything tucked nicely
> inside the project, was to create a different prod obj for
> each transaction that would ever need to be sent and add
> the quals to each so that each would only run under the
> condition specified.
>
> So prod obj #1 would have as one of it's quals -
>
> If P01 && ACCTC return 1;
> In the output all the rules would run as normal
> except I'd change P01 to A13.
>
>
> Prod obj #2:
>
> If P01 && ACCTE return 1;
> In the output all the rules would run as normal and
> P01 would remain as P01.
>
>
> Prod obj #3:
>
> If P01 && ACCTE return 1;
> In the output all the rules would run as normal
> except I'd change P01 to A03.
>
>
> Prod obj #4:
>
> If P01 && OPACC return 1;
> In the output all the rules would run as normal and
> P01 would remain as P01.
>
>
> Prod obj #5:
>
> If P01 && OPACC return 1;
> In the output all the rules would run as normal
> except I'd change P01 to A03.
>
>
> Prod obj #6:
>
> (assuming all other basic quals met)
> In the output all the rules would run as normal.
>
> So that seems like a lot of work and maintenance and
> confusion down the road with code changes, log extraction,
> etc.
>
> My other thought was to try to handle it within the aim
> but it's a lot more difficult to identify the fields I
> need to interrogate.
>
> If anyone understands what I'm trying to do and has any
> ideas I'd really appreciate hearing from you.
>
> Feel free to post the reply here and/or email me @
> john.fritsch@lvh.com
>
> Thanks!