Hi Rob,

We have not yet announced support for ANY release of BPCS or LX on
V6R1M0. When we finish our testing and do announce support, there will
be a new Info APAR for that. IBM support maintains the Info APARs that
are already released so you can ask them any further questions about
dates etc. inside the Info APAR itself.

Thanks,

Genyphyr Novak | Senior Architect, ERP LX Architecture | Infor |
genyphyr.novak@xxxxxxxxx




-----Original Message-----
From: bpcs-l-bounces+genyphyr.novak=infor.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+genyphyr.novak=infor.com@xxxxxxxxxxxx] On Behalf
Of bpcs-l-request@xxxxxxxxxxxx
Sent: 05 February 2008 16:04
To: bpcs-l@xxxxxxxxxxxx
Subject: BPCS-L Digest, Vol 6, Issue 21

Send BPCS-L mailing list submissions to
bpcs-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/bpcs-l
or, via email, send a message with subject or body 'help' to
bpcs-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
bpcs-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of BPCS-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

1. Re: Older versions of BPCS (rob@xxxxxxxxx)
2. Question on Price Book Date (Papada, Andrew Joseph CAR)
3. Re: Question on Price Book Date (Dan Sweeney)
4. Re: Question on Price Book Date (Molyneux, Tom)
5. Excel BOM vs BPCS BOM & Requirement Checking (Larenzo Alexander)
6. Re: Excel BOM vs BPCS BOM & Requirement Checking (DANIEL WARTHOLD)
7. Re: Excel BOM vs BPCS BOM & Requirement Checking (Dan Sweeney)
8. Re: Question on Price Book Date (Papada, Andrew Joseph CAR)


----------------------------------------------------------------------

message: 1
date: Mon, 4 Feb 2008 14:51:04 -0500
from: rob@xxxxxxxxx
subject: Re: [BPCS-L] Older versions of BPCS

A couple of concerns with the information apar:
II14189: OSP-DB INFOR's ERP LX AND BPCS ON I5 REQUIRED PTF LIST FOR
V5R4

1 - While somewhere near the top it mentions 2007, there are other spots
with lingo like:
"The most current R540 CUM is recommended. The latest CUM is C6297 for
R540, as of this posting's date 12/20/2006. DB Fix Pack for V5R4, order
SF99504. The DB fixpack, SF99504 is required. The current fix pack date
is 11/06/2006. Do a WRKPTFGRP SF99504 and this will show you the level
of the installed Group PTF SF99504. The current DB fix pack level is 6
as of this posting's date 12/20/2006 HIPER group (SF99539) is level 30
and is required for BPCS V6.x and V8.x and LX to avoid performance
issues."

2 - Do they have a like cover letter for V6R1? I can see stuff for V6R1
at:
http://www-912.ibm.com/s_dir/sline003.nsf/ALLPSPBYREL?OpenView&Start=1&C
ount=30&Expand=1#1
http://www-912.ibm.com/a_dir/as4ptf.nsf/wwwv6r1?OpenView&view=wwwV6R1

And, just to point out the competition:
II14362 CLOSED CAN SAP SUPPORT REQUIRED PTF LIST FOR V6R1M0 available at
http://www-912.ibm.com/n_dir/nas4apar.nsf/$$v6r1?OpenView&view=$$v6r1

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com



------------------------------

message: 2
date: Mon, 4 Feb 2008 17:06:00 -0500
from: "Papada, Andrew Joseph CAR" <Andrew.Papada@xxxxxxxxxx>
subject: [BPCS-L] Question on Price Book Date

Hello Everyone,



I'm trying to find out what how the Price Book dates are populated
during order entry (ECH.CHPRBD and ECL.CLPRBD). We developed a web
based ecommerce application that ties into BPCS 6.02 and uses ORD702B to
create the header and line items. I've recently had an issue in which
the order was said to have been entered on the current day but the price
book date is equal to the previous day; however I cannot recreate this
issue. I looked through the code to see how this value gets populated
and all I can tell is that it appears to be set to the current date if
not overridden on the calling param list to ORD702B. Can you tell me
what the standard procedure is for populating this value on entry?
Also, and forgive my ignorance, can you tell me what value this has on
the order (specifically the header ) itself?



Thanks,

Andy



------------------------------

message: 3
date: Tue, 5 Feb 2008 07:45:13 -0500
from: "Dan Sweeney" <dsweeney@xxxxxxxxxxxxxxxx>
subject: Re: [BPCS-L] Question on Price Book Date

Andy,

Normally the price book date defaults to the requested due date.

Why you had your specific scenario of the price book date being one day
prior to the entry date is confusing.

What is the requested due date?

-----Original Message-----
From: bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx] On Behalf
Of
Papada, Andrew Joseph CAR
Sent: Monday, February 04, 2008 5:06 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Question on Price Book Date

Hello Everyone,



I'm trying to find out what how the Price Book dates are populated
during order entry (ECH.CHPRBD and ECL.CLPRBD). We developed a web
based ecommerce application that ties into BPCS 6.02 and uses ORD702B to
create the header and line items. I've recently had an issue in which
the order was said to have been entered on the current day but the price
book date is equal to the previous day; however I cannot recreate this
issue. I looked through the code to see how this value gets populated
and all I can tell is that it appears to be set to the current date if
not overridden on the calling param list to ORD702B. Can you tell me
what the standard procedure is for populating this value on entry?
Also, and forgive my ignorance, can you tell me what value this has on
the order (specifically the header ) itself?



Thanks,

Andy


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 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.