Hi Mike,
Â
I guess then I am misunderstanding what you are looking for. When a new PO line is created, the release for that line is not generated until the PO is saved. So if the BPM is attached to the POupdate method, it will populate the promise date when the PO is saved.
Â
Maurice
________________________________
From: Mike Tonoyan <mtonoyan@...>
To: vantage@yahoogroups.com
Sent: Thursday, February 2, 2012 4:28 PM
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Â
Maurice,
This approached worked better, but still we have to open the release tab and refresh in order to populate the promise date. I was hoping for it to be populated as soon as we enter a PO Line Due Date, which in it’s turn populates the PO Release Due Date, and we don’t have to refresh.
Mike Tonoyan / Natel EMS
mtonoyan@...
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Maurice Swede
Sent: Thursday, February 02, 2012 12:31 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] RE: BPM to populate PORel Promise Date
Mike,
You can also accomplish this by using a post process method directive. Under the "Conditions" check the promise date field to determine if it is empty. Then under the "Actions" select the "synchronously execute ABL code...record nothing" option, click on the word "code" and enter the following ABL code:
for each ttPORel where ttPORel.PromiseDt = ?,
each PORel where PORel.PONum = ttPORel.PONum and PORel.POLine = ttPORel.POLine and PORel.PORelNum = ttPORel.PORelNum:
Assign PORel.PromiseDt = ttPORel.DueDate.
Assign ttPORel.PromiseDt = ttPORel.DueDate.
end.
To explain the code:
The "for each ttPORel..." line is doing the same check as the condition you set up so could be eliminated. If you do eliminate it, you need to put a "for" before the "each PORel..." line.
The "each PORel where...." line is going out and finding the just created record in the database.
The "Assign..." lines are setting the promise date fields to the due date. For the screen to display the promise date the temp table field needs to be populated as well.
The "end." obviously ends the program.
We are currently running 9.04.507A and the above process worked, so I hape this helps.
Maurice
________________________________
From: Mike Tonoyan <mtonoyan@... <mailto:mtonoyan%40natelems.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Thursday, February 2, 2012 2:02 PM
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Greg,
Thanks, we are on 9.04.507, most likely that's the reason. I added a
method directive also, still the same, it populates when the due date is
changed.
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com>
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf
Of Greg Payne
Sent: Thursday, February 02, 2012 10:42 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Mine is in transaction and works on 905.605.
based on the documentation that is the data directive to use. The table
name should be colored and not black if the editor recognizes it. I have
seen where the table is not recognized, but when I typed it again it
was.
Greg
from business.process.management.pdf
There are two types of data directives:
* In-Transaction: Affects data while it is being saved to the database.
This directive type can only process one
row at a time; it cannot process multiple dirty rows.
* Standard: Does not affect data in the database. This directive type
executes after a data transaction saves
to the database. It can process multiple dirty rows modified in the
database. This directive type runs after base
methods and method directives.
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Mike Tonoyan
Sent: Thursday, February 02, 2012 12:20 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
As I mentioned before it didn't work on "In-Transactions" tab. No, I
didn't create a Method Directive. Should it be a Post-Processing method
directive?
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com>
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>]
On Behalf
Of Greg Payne
Sent: Thursday, February 02, 2012 5:22 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
In transaction is where it goes. Yes, it should set the value whenever
due date has a date and promise is not set.
Should happen on po entry and on generate po. Did you put on a method
directive of Update?
Greg
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
On
Behalf Of Mike Tonoyan
Sent: Wednesday, February 01, 2012 6:58 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Never mind the previous e-mail, I shouldn't have selected the
"In-Transaction" Data Directive.
After that everything went fine, the directive is enabled but the only
time it populates the "Promise Date" when the "Due Date" is changed. Was
it supposed to populate when a new record was added too?
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com>
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>]
On Behalf
Of Mike Tonoyan
Sent: Wednesday, February 01, 2012 3:27 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Greg,
I am new at this, so please bear with me.
1. Created a "In-Transaction" Data Directive for PORel table
2. Clicked on "Conditions... " and selected "number of rows in the
designed query is not less than 1" user text.
3. Clicked on "designed" and entered the query name "Empty promise
date Query"
4. Copied and pasted "for each ttPORel where ttPORel.PromiseDt = ?
and ttPORel.DueDate <> ?"
5. When tried to save I received the following message "Unable to
find any table in the query"
What am I doing wrong?
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
On
Behalf
Of Greg Payne
Sent: Friday, January 27, 2012 10:44 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] RE: BPM to populate PORel Promise Date
I actually wrote that same routine today for our purchasing dept.
This is how I approached it.
Greg
Data Directive:
Condition
number of rows in the 'Empty Promise date' query is not less than 1
Empty promise date Query
for each ttPORel where ttPORel.PromiseDt = ? and ttPORel.DueDate <> ?
Action:
synchronously execute ABL for each ttPORel where ttPORel.PromiseDt ...
record nothing
ABL Code:
for each ttPORel where ttPORel.PromiseDt = ? and ttPORel.DueDate <> ?
no-lock.
If available ttPORel then do:
Assign ttPOrel.PromiseDt = ttPORel.DueDate.
End.
End.
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ] On
Behalf Of Mike Tonoyan
Sent: Friday, January 27, 2012 12:40 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] BPM to populate PORel Promise Date
I am wondering if anyone knows how to create a BPM for populating the PO
Release Promise Date when the PO Release Due Date is populated for the
first time. The promise date then should not change automatically when
the due date is changed.
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com>
_,___
__________________________________________________________
Notice: This email transmission may contain confidential information and
is intended only for the person(s) named. Any use, copying or disclosure
to/by any other person(s) is strictly prohibited. By accepting this
information, recipients confirm that they understand and will comply
with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
________________________________
CONFIDENTIALITY NOTICE
The information contained in this communication, including attachments,
is privileged and confidential. It is intended only for the exclusive
use of the addressee. If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering it to the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us at (727)
578-6258 and immediately delete the communication.
"This (document/presentation) may contain technical data as defined in
the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
Export of this material is restricted by the Arms Export Control Act (22
U.S.C. 2751 et seq.) and may not be exported to foreign persons without
prior approval form the U.S. Department of State."
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and
is intended only for the person(s) named. Any use, copying or disclosure
to/by any other person(s) is strictly prohibited. By accepting this
information, recipients confirm that they understand and will comply
with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and
is intended only for the person(s) named. Any use, copying or disclosure
to/by any other person(s) is strictly prohibited. By accepting this
information, recipients confirm that they understand and will comply
with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
________________________________
CONFIDENTIALITY NOTICE
The information contained in this communication, including attachments,
is privileged and confidential. It is intended only for the exclusive
use of the addressee. If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering it to the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us at (727)
578-6258 and immediately delete the communication.
"This (document/presentation) may contain technical data as defined in
the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
Export of this material is restricted by the Arms Export Control Act (22
U.S.C. 2751 et seq.) and may not be exported to foreign persons without
prior approval form the U.S. Department of State."
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and
is intended only for the person(s) named. Any use, copying or disclosure
to/by any other person(s) is strictly prohibited. By accepting this
information, recipients confirm that they understand and will comply
with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
________________________________
CONFIDENTIALITY NOTICE
The information contained in this communication, including attachments,
is privileged and confidential. It is intended only for the exclusive
use of the addressee. If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering it to the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us at (727)
578-6258 and immediately delete the communication.
"This (document/presentation) may contain technical data as defined in
the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
Export of this material is restricted by the Arms Export Control Act (22
U.S.C. 2751 et seq.) and may not be exported to foreign persons without
prior approval form the U.S. Department of State."
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure to/by any other person(s) is strictly prohibited. By accepting this information, recipients confirm that they understand and will comply with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure to/by any other person(s) is strictly prohibited. By accepting this information, recipients confirm that they understand and will comply with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
Â
I guess then I am misunderstanding what you are looking for. When a new PO line is created, the release for that line is not generated until the PO is saved. So if the BPM is attached to the POupdate method, it will populate the promise date when the PO is saved.
Â
Maurice
________________________________
From: Mike Tonoyan <mtonoyan@...>
To: vantage@yahoogroups.com
Sent: Thursday, February 2, 2012 4:28 PM
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Â
Maurice,
This approached worked better, but still we have to open the release tab and refresh in order to populate the promise date. I was hoping for it to be populated as soon as we enter a PO Line Due Date, which in it’s turn populates the PO Release Due Date, and we don’t have to refresh.
Mike Tonoyan / Natel EMS
mtonoyan@...
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Maurice Swede
Sent: Thursday, February 02, 2012 12:31 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] RE: BPM to populate PORel Promise Date
Mike,
You can also accomplish this by using a post process method directive. Under the "Conditions" check the promise date field to determine if it is empty. Then under the "Actions" select the "synchronously execute ABL code...record nothing" option, click on the word "code" and enter the following ABL code:
for each ttPORel where ttPORel.PromiseDt = ?,
each PORel where PORel.PONum = ttPORel.PONum and PORel.POLine = ttPORel.POLine and PORel.PORelNum = ttPORel.PORelNum:
Assign PORel.PromiseDt = ttPORel.DueDate.
Assign ttPORel.PromiseDt = ttPORel.DueDate.
end.
To explain the code:
The "for each ttPORel..." line is doing the same check as the condition you set up so could be eliminated. If you do eliminate it, you need to put a "for" before the "each PORel..." line.
The "each PORel where...." line is going out and finding the just created record in the database.
The "Assign..." lines are setting the promise date fields to the due date. For the screen to display the promise date the temp table field needs to be populated as well.
The "end." obviously ends the program.
We are currently running 9.04.507A and the above process worked, so I hape this helps.
Maurice
________________________________
From: Mike Tonoyan <mtonoyan@... <mailto:mtonoyan%40natelems.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Thursday, February 2, 2012 2:02 PM
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Greg,
Thanks, we are on 9.04.507, most likely that's the reason. I added a
method directive also, still the same, it populates when the due date is
changed.
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com>
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf
Of Greg Payne
Sent: Thursday, February 02, 2012 10:42 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Mine is in transaction and works on 905.605.
based on the documentation that is the data directive to use. The table
name should be colored and not black if the editor recognizes it. I have
seen where the table is not recognized, but when I typed it again it
was.
Greg
from business.process.management.pdf
There are two types of data directives:
* In-Transaction: Affects data while it is being saved to the database.
This directive type can only process one
row at a time; it cannot process multiple dirty rows.
* Standard: Does not affect data in the database. This directive type
executes after a data transaction saves
to the database. It can process multiple dirty rows modified in the
database. This directive type runs after base
methods and method directives.
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Mike Tonoyan
Sent: Thursday, February 02, 2012 12:20 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
As I mentioned before it didn't work on "In-Transactions" tab. No, I
didn't create a Method Directive. Should it be a Post-Processing method
directive?
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com>
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>]
On Behalf
Of Greg Payne
Sent: Thursday, February 02, 2012 5:22 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
In transaction is where it goes. Yes, it should set the value whenever
due date has a date and promise is not set.
Should happen on po entry and on generate po. Did you put on a method
directive of Update?
Greg
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
On
Behalf Of Mike Tonoyan
Sent: Wednesday, February 01, 2012 6:58 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Never mind the previous e-mail, I shouldn't have selected the
"In-Transaction" Data Directive.
After that everything went fine, the directive is enabled but the only
time it populates the "Promise Date" when the "Due Date" is changed. Was
it supposed to populate when a new record was added too?
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com>
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>]
On Behalf
Of Mike Tonoyan
Sent: Wednesday, February 01, 2012 3:27 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] RE: BPM to populate PORel Promise Date
Greg,
I am new at this, so please bear with me.
1. Created a "In-Transaction" Data Directive for PORel table
2. Clicked on "Conditions... " and selected "number of rows in the
designed query is not less than 1" user text.
3. Clicked on "designed" and entered the query name "Empty promise
date Query"
4. Copied and pasted "for each ttPORel where ttPORel.PromiseDt = ?
and ttPORel.DueDate <> ?"
5. When tried to save I received the following message "Unable to
find any table in the query"
What am I doing wrong?
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
On
Behalf
Of Greg Payne
Sent: Friday, January 27, 2012 10:44 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] RE: BPM to populate PORel Promise Date
I actually wrote that same routine today for our purchasing dept.
This is how I approached it.
Greg
Data Directive:
Condition
number of rows in the 'Empty Promise date' query is not less than 1
Empty promise date Query
for each ttPORel where ttPORel.PromiseDt = ? and ttPORel.DueDate <> ?
Action:
synchronously execute ABL for each ttPORel where ttPORel.PromiseDt ...
record nothing
ABL Code:
for each ttPORel where ttPORel.PromiseDt = ? and ttPORel.DueDate <> ?
no-lock.
If available ttPORel then do:
Assign ttPOrel.PromiseDt = ttPORel.DueDate.
End.
End.
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ] On
Behalf Of Mike Tonoyan
Sent: Friday, January 27, 2012 12:40 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] BPM to populate PORel Promise Date
I am wondering if anyone knows how to create a BPM for populating the PO
Release Promise Date when the PO Release Due Date is populated for the
first time. The promise date then should not change automatically when
the due date is changed.
Mike Tonoyan / Natel EMS
mtonoyan@... <mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com> <mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com>
<mailto:mtonoyan%40natelems.com>
_,___
__________________________________________________________
Notice: This email transmission may contain confidential information and
is intended only for the person(s) named. Any use, copying or disclosure
to/by any other person(s) is strictly prohibited. By accepting this
information, recipients confirm that they understand and will comply
with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
________________________________
CONFIDENTIALITY NOTICE
The information contained in this communication, including attachments,
is privileged and confidential. It is intended only for the exclusive
use of the addressee. If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering it to the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us at (727)
578-6258 and immediately delete the communication.
"This (document/presentation) may contain technical data as defined in
the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
Export of this material is restricted by the Arms Export Control Act (22
U.S.C. 2751 et seq.) and may not be exported to foreign persons without
prior approval form the U.S. Department of State."
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and
is intended only for the person(s) named. Any use, copying or disclosure
to/by any other person(s) is strictly prohibited. By accepting this
information, recipients confirm that they understand and will comply
with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and
is intended only for the person(s) named. Any use, copying or disclosure
to/by any other person(s) is strictly prohibited. By accepting this
information, recipients confirm that they understand and will comply
with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
________________________________
CONFIDENTIALITY NOTICE
The information contained in this communication, including attachments,
is privileged and confidential. It is intended only for the exclusive
use of the addressee. If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering it to the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us at (727)
578-6258 and immediately delete the communication.
"This (document/presentation) may contain technical data as defined in
the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
Export of this material is restricted by the Arms Export Control Act (22
U.S.C. 2751 et seq.) and may not be exported to foreign persons without
prior approval form the U.S. Department of State."
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and
is intended only for the person(s) named. Any use, copying or disclosure
to/by any other person(s) is strictly prohibited. By accepting this
information, recipients confirm that they understand and will comply
with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
________________________________
CONFIDENTIALITY NOTICE
The information contained in this communication, including attachments,
is privileged and confidential. It is intended only for the exclusive
use of the addressee. If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering it to the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us at (727)
578-6258 and immediately delete the communication.
"This (document/presentation) may contain technical data as defined in
the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
Export of this material is restricted by the Arms Export Control Act (22
U.S.C. 2751 et seq.) and may not be exported to foreign persons without
prior approval form the U.S. Department of State."
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure to/by any other person(s) is strictly prohibited. By accepting this information, recipients confirm that they understand and will comply with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
__________________________________________________________
Notice: This email transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure to/by any other person(s) is strictly prohibited. By accepting this information, recipients confirm that they understand and will comply with all applicable ITAR and EAR requirements.
__________________________________________________________
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]