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



Hello Carlos,

What version of BPCS/ERP LX are you running?

Thank you.

Franck Guillet | Principal Technical Consultant, Professional Services | Infor | cell: 773-610-7375 | e-mail: franck.guillet@xxxxxxxxx

-----Original Message-----
From: bpcs-l-bounces+franck.guillet=infor.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+franck.guillet=infor.com@xxxxxxxxxxxx] On Behalf Of Carlos Anazco
Sent: Tuesday, January 12, 2010 1:20 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Customer PO Line

Hi there,
This is my first posting; however I usually find what I need in this forum. Thanks.
Here it's my problem: I'm creating an outbound ASN (856) and the customer requires to include his PO line which was received in the inbound 862. When I receive the 862 I write the customer PO line in the file TDDB.DDPOLN. For the outbound message I found that TAIB contains the field AICPL which is unfortunately always empty. The ECM documentation describes AICPL as: "ECM retrieves the Customer Purchase Order Line Number from the Order Lines file in BPCS (ECL.CLCRLN)" which is also empty. I see everything in BPCS is ready to manage the Customer PO Line but, for some reason it is not "travelling" up to the end. Probably DDPOLN is not the right field to receive it, or there may be a switch in ECM that requires activation... I don't know.

Any ideas?. Thanks again.


Carlos Anazco
Schukra of North America
phone:: 519-727-7000 x 1003



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.