× 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.



Depending who is the authority. In our case, the goal is to fix our
screw-ups without advertising to the customer that we have mistakes.

Ideally you want a system which is easy for everyone to use, and easy to
audit. We sometimes use item classes to associate activity which follows
some standard non-standard rule. Everyone knows the special handling rules
for special item classes.

We on earlier version of BPCS. We have shipping dept errors.
* Oops we shipped X but we keyed in wrong order as being shipped, or
wrong order line, or wrong item, or wrong quantity, or whatever.
* Oops, there was a price change but it did not get keyed in, in time,
we need the invoice correct.
* To solve this, after the B transaction, we go into BBL record with
DFU and tinker with it.
* There is a sequence line # in the BBL which tells us which sequence
line # in the ECL customer order line is the corresponding record to need a
DFU adjustment.
* There has to be an inventory adjustment to reverse the B
transaction, so inventory correct. There's an opposite cost-of-sales GL
transaction to the B to make sure GL is corrected.
* If someone was to match shipping records with billing records, they
would find evidence of stuff shipped but not billed. We inform auditors,
stick a note in the accounting, how come this done.

In your case, you can have multiple ship-to attached to each bill-to, where
in some cases customer-A ship-to just happens to be attached to customer-B
bill-to. It could be a drop-ship arrangement, where some customer-A is both
your customer and customer of B. Sometimes customer-A orders direct from
you, and sometimes thru customer-B.

Since customer-A ship to is probably also attached to customer-A bill-to,
there's occasional risk of getting them mixed up. BPCS also supports a
third level . corporate customer, where the bill-to ship-to might be a
division of a conglomerate, but all bills go to corporate HQ.

-
Al Mac
-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of Rajesh.Kamath
Sent: Monday, June 27, 2011 1:28 AM
To: 'BPCS ERP System'
Subject: Re: [BPCS-L] BPCS-L Digest, Vol 9, Issue 89

Hi..

This can be business requirement to facilitate the customer requirement...

Scenario is customer order is created for customer A and for some reason
management wants to ship the material customer B
And at the same time they does not want to bill the customer order of A and
do RMA and then create a new order on customer B because cancellation of
invoice need to be informed the statutory authority.

In this can I do the -B transaction and may have to delete the BBH/BBL
records. But the customer order of A will show the status ready for billing.

Regards
Rajesh


-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of debasish chakraborty
Sent: Monday, June 27, 2011 11:20 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: Re: [BPCS-L] BPCS-L Digest, Vol 9, Issue 89


No you cannot do it , you can de allocate the order if it is only pick
released , cancel the order and raise a new order for the new customer.
The exsisting order cannot be changed. But if you have pick confirmed then
you have essentially shipped a order physically so it is not possible to
revert back as you have already done the hard allocation.

My question is what is your purpose , is it a one of mistake that the
customer has done or it is going to be a regular phenomenon.

If it is regular then you need some customization to check and stop people
from Pick confirming if the customer is not right. Thats my view the experts
in the forum might shed some more light as I am not too familiar with LX
what I have said is my experience from version 6.xx.xx.




Thanks & Regards
Debasish
The past, it's a story. The future, it's a mystery. The present, it is a
gift.
IBM System i - For when you can't afford to be out of business.


From: bpcs-l-request@xxxxxxxxxxxx
Subject: BPCS-L Digest, Vol 9, Issue 89
To: bpcs-l@xxxxxxxxxxxx
Date: Thu, 23 Jun 2011 12:00:10 -0500

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. Pick Confirm Activity (Rajesh.Kamath)


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

message: 1
date: Thu, 23 Jun 2011 13:08:08 +0530
from: "Rajesh.Kamath" <rajesh.kamath@xxxxxxxx>
subject: [BPCS-L] Pick Confirm Activity

Hi,



If have carried out Pick release and pick release and prick confirm
activity
but not billed. If this is case can I cancel the order and bill it to
other
customer. If so how do we do it ERP Lx.







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

--
This is the BPCS ERP System (BPCS-L) digest list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.



End of BPCS-L Digest, Vol 9, Issue 89
*************************************


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.