×
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.
BPCS V8.0 and BPCS V8.1 won't automatically convert due to the way it was shipped. Prior to BPCS V8.0 and beyond BPCS 8.1, the majority of programs will convert automatically.
I raised this issue with Infor for our BPCS V8.0 environments, after which the BMR was created.
________________________________________
From: bpcs-l-bounces@xxxxxxxxxxxx [bpcs-l-bounces@xxxxxxxxxxxx] on behalf of SRohatgi@xxxxxxxxxxxxxxxxxx [SRohatgi@xxxxxxxxxxxxxxxxxx]
Sent: 12 October 2012 18:14
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] V6R1 migration with modified BPCS V8.1
Hi All,
We are V5R4 OS level and want to move to V6R1 and have modified version of
BPCS 8.1. We are on maintenance with infor but according to them we need
to convert most of the BPCS program objects to V6R1 by applying a BMR
bundle. We've extensively modified environment and it would be huge task
for us to retrofit our codes at this time to apply that BMR bundle.
Just wondering if anyone has encounter such an issue and what you have
done to move to V6R1 with modified BPCS environment?
Thanks in advance for your responses.
Sumit
Sumit Rohatgi
Enterprise Applications Team Lead - Supply
Please consider the environment before printing this email
This e-mail message is intended for the use of the addressee and may contain
privileged, confidential or personal information. If you are not the intended
recipient, please be advised that you are strictly prohibited from using,
disclosing, distributing or reproducing this email or the information contained
within. If you have received this email in error, please notify the sender
immediately by return e-mail and destroy the original message and any copies.
Ce message électronique est destiné uniquement à la personne à laquelle il a
été adressé et pourrait contenir des renseignements à caractère confidentiel et
personnel. Si vous n’êtes pas le destinataire, veuillez prendre note qu’il vous
est strictement défendu d’utiliser, de divulguer, de diffuser ou de reproduire
ce courriel ou les renseignements qu’il contient. Si vous avez reçu ce message
par erreur, veuillez le signaler à l’expéditeur immédiatement en répondant au
courriel et détruire le message original et toute copie.
As an Amazon Associate we earn from qualifying purchases.
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.