P4310/P43081 messaging

Edward_Luke

Active Member
The link in the approvers work center that brings up an order to approve calls the JDE standard interactive version ZJDE0001 of P43081. How can I make this call a different version? I have listed our version CFS001 in the P4310 processing options versions tab, but that only seems to work related to the row exit 'approval review' on the P4310 app. Is this controlled through some workflow process or some other way. I have looked through the workflow and made a couple of changes to no avail.

Thanks for your help.

B733.2 SP15.1 HP9000 Oracle 8.1.7
 
Hi Edward,

My knowledge of Workflow is limited and maybe you already tried this solution, but nevertheless here it comes:

In your Process Relationships, go to Advanced Set up and select the activity which calls the application (I believe it is called "Review").
Take the row exit "Edit Definition" to edit your "send message" action message. In its parameter listing, select "Active" and note the parameters passed into the application.
Now change the value selection to <none> and change it again to <Define Active Message>. You now should have the opportunity to select the application (P43081), the form and the version and to pass the parameters back in again.

Good luck,


Sef van den Nieuwelaar
Australia
B732 on NT, XE on NT, B732/A73 on AS400, B733 on NT
 
Well, I did a little more investigation and found a knowledge garden document that explains that this can't be done because the version is hard coded in a table event rule in F4209.

However, I wonder if it is possible to modify that event rule in the the Table ER to use a different version. I realize you have to rebuild the triggers, but is this ok to do? I tested it on a custom table and it seems to work ok. Any problems with making this change to triggers on F4209?

Thanks.

B733.2 SP15.1 HP9000 Oracle 8.1.7
 
Will what Edward is suggesting work? Can I put logic into the F4209 event rules to determine what version to run?

After the change he says to rebuild triggers. I've never done this before. Is this similar to busbuild? When I build a package do I just include F4209?

Patty
 
Edward,

I've done this & it works, however, you may need to call different versions dependant on the order type.

// Call correct approval version depending on the order type
//
If TK OrderType is equal to "OR"
Send Message(TK PersonResponsible, <Electronic Workbench>, <Blank>, <Blank>, Call( App:p43081 , Form: W43081B ), LM0016, VA evt_EMailSerialNumber)
End If
//
If TK OrderType is equal to "OP"
Send Message(TK PersonResponsible, <Electronic Workbench>, <Blank>, <Blank>, Call( App:p43081 , Form: W43081B ), LM0016, VA evt_EMailSerialNumber)
End If
//
If TK OrderType is equal to "OB"
Send Message(TK PersonResponsible, <Electronic Workbench>, <Blank>, <Blank>, Call( App:p43081 , Form: W43081B ), LM0016, VA evt_EMailSerialNumber)
End If
//
If TK OrderType is equal to "O4"
Send Message(TK PersonResponsible, <Electronic Workbench>, <Blank>, <Blank>, Call( App:p43081 , Form: W43081B ), LM0016, VA evt_EMailSerialNumber)
End If
 
Ian

Thanks for the response. What about re-building table triggers? Would the steps be:

1. Make change to Table ER in F4209.
2. Rebuild triggers.
3. Include F4209 in a package.

Patty
 
Patty,

Yep. That's is. It should update one of the JDBTRG* DLLs

/ Ian



Xe, Oracle 8, NT
 
Back
Top