PipeChain Release Notes 4.9.2

PipeChain Release Notes 4.9.2
PipeChain Release Notes 4.9.2
PipeChain Release Notes 4.9.2
1
PipeChain Release Notes 4.9.2
1
2
WELCOME .......................................................................................................... 4
UPGRADE TO VERSION 4.9.2 .............................................................................. 5
2.1
3
Actions before upgrading to PipeChain 4.9.2................................................... 5
RELEASE NOTES PIPECHAIN 4.9.2 ...................................................................... 6
3.1
New functions and improvments in 4.9.2 ........................................................ 6
3.1.1. POC: Four new fields in Blanket OrderLine ........................................................ 6
3.1.2. Possible to retrive received order lines for a delivery note by a new web service ..... 6
3.1.3. POC: New screen in POC for goods reception..................................................... 6
3.1.4. Platform: Event Scanning BGJob stability.......................................................... 6
3.1.5. POC: Add new row to Invoice ......................................................................... 6
3.1.6. POC, Supply: Improved Recipient Info in Delivery Agreement Detail screens .......... 7
3.1.7. Platform: AutoConfirm via Event transactions .................................................... 7
3.1.8. Supply: Possible to delete finished inbound orders and finished inbound deliveries .. 7
3.1.9. Platform: UNB support in outbound transactions ................................................ 8
3.1.10. Platform: Background job recovery after distubancies ..................................... 8
3.1.11. SOC: Shipment and reception time is corrected for inbound order head in
Commission Call-off .............................................................................................. 8
3.1.12. SOC: The reception time in basket line is not automatically changed to same value
as on order head .................................................................................................. 8
3.1.13. POC: Restriction on number of suppliers to show Despatch Order Lines with "All
Suppliers"............................................................................................................ 8
3.1.14. Supply: Profile setting för Net Demand and Gross Demand POC screens ............. 8
3.1.15. Supply: Ship Order screens is now shown after shipping a despatch .................. 9
3.1.16. Supply: Weekly transport dates can be modified in the Outbound Reception
Schedule Detail screen by supplier ........................................................................... 9
3.1.17. SOC: New order in web shop price range ..................................................... 9
3.1.18. POC: Supplier's Calendar screen .................................................................. 9
3.1.19. Supply: The Flow model functionality is extended with
DisregardFMDmdAfter and
DisregardFMDmdBefore,
DeliverToCustomer ........................................................ 9
3.1.20. POC: Added Print Buttons in Web interface Despatch Detail screen .................... 9
3.1.21. Link from DelivNoteId attribute to OrderLine, Delivery and Finished Delivery Detail
to Despatch Detail screen ..................................................................................... 10
3.1.22. Supply: Own balance was updated twice in In & Out Deliveries in Inventory Chart10
3.1.23. Supply: The invoce printout is generated if the invoice is created from a
transaction (CS80) as well, not only from POC web................................................... 10
3.1.24. Supply: Performance improvement in the PipeChain Supply Overview screen .... 10
3.1.25. Supply: The despatch advice ( CS48) generated from supplier integration (PW03)
is corrected........................................................................................................ 10
3.1.26. Supply: CS02 Orderresponse does not add/subtract leadtime to reception-/and
shipment time .................................................................................................... 10
2
3.2
New functions in 4.9.1 service packs ............................................................ 11
3.2.1. POC: Add new row to Invoice (SP03) ............................................................. 11
3.2.2. New fields added to Claim Mail (SP03) ........................................................... 11
3.3
Corrections in 4.9.1 service packs ................................................................ 11
3.3.1. CS80 Invoice transaction corrections (SP01) .......................................................... 11
3.3.2. SOC: New order in web shop price range (SP01) If the price list is to be shown for user, it is
placed first instead of last. ........................................................................................ 11
3.3.3. CS80 should be processed error if expecting DESADV and no despatch object found in ....... 11
3.3.4. POC: CS38 DeliverySchedule nullexception correction .............................................. 12
3.3.5. SOC: Shipment and reception time is corrected for inbound order head in Commission Call-off 12
3.3.6. POC: CS38 DeliverySchedule transation; Improved handling of orderlines with status 2 ........ 12
3.3.7. POC: Conditional display of link to order in Web Forecast Overview screen ...................... 12
3.3.8. POC: Optimized POC webinterface screen Despatch Order Lines for faster display. ............ 12
3.3.9. POC: Profile setting för Net Demand and Gross Demand POC screens ........................... 12
3.3.10. POC: Restriction on number of suppliers to show Despatch Order Lines with "All Suppliers" ... 12
3.3.11. POC: Invoice printout including PR80 VAT in account currency ..................................... 12
3.3.12. Plattform: Handled background job Update Order Statuses unnecessary error in message log 13
3.3.13. POC: Invoice CS80 TotalAmountExclTax/GrossNet uses value of.................................. 13
3.3.14. CS02 OrderResponse transaction now handles cancellation of already cancelled orderlines ... 13
3.3.15. Corrected label on Order and Orderline General Information text ................................... 13
3.3.16. Change of Forecast row in CS38 DeliverySchedule turns up wrong delivstatus .................. 13
3.3.17. Web supplier's Outbound Order Overview screen does not count finished order lines ........... 13
3.3.18. Supply: Sales Order Id in Web Confirm Replenishment Order Lines ............................... 13
3.3.19. Web Shop: Checking out basket when price range expired .......................................... 13
3.3.20. Suppliers Web Forecast Delivery Period Overview shows DelivQty instead of DmdQty ......... 14
3.3.21. Search in Web Forecast Delivery Period Overview does not include all results ................... 14
3.3.22. Platform: Background job recovery after distubancies ................................................ 14
3.3.23. Web Confirm via Order and Forecast screens yield different dates, CS05 OrderResponse ..... 14
3.3.23.1 Forecast transaction CS38, non-firm, non-forecast orderline with missing orders should have
the order created by pipechain. .................................................................................. 14
3.3.24. Platform: AutoConfirm via Event transactions ......................................................... 14
3.3.25. OrderId is missing in Invoice Printout and in PR80 transaction from invoice created by CS80. . 15
3.3.26. Illegal filename charcters in invoice file, PR80 ......................................................... 15
3.3.27. The reception time in basket line is not automatically changed to same value as on order head 15
3.3.28. Invoice transaction CS80 crashes ....................................................................... 15
3
PipeChain Release Notes 4.9.2
1
WELCOME
PipeChain is a software system that automates the flow of goods between companies, in production,
between production and sales within a company.
Website: www.pipechain.com
Copyright protects all information in this document. You must have prior written permission from
PipeChain AB, Lund, Sweden to electronically or mechanically copy, duplicate, reproduce,
photocopy, print, record, transmit, or translate any part of this document to persons not using
PipeChain.
PipeChain, Duration Meter (name and layout), and Market Meter (name and layout) are trademarks
of PipeChain AB. Microsoft, Windows, SQL Server, and Excel are trademarks of the Microsoft
Corporation. Oracle is a trademark of the Oracle Corporation. All other trademarks mentioned in this
publication are the property of their respective owners in their respective countries.
NOTICE
Information in this document is subject to change without notice.
4
2
UPGRADE TO VERSION 4.9.2
Here are actions for what to do before installation of PipeChain 4.9.2. Document describing how to
install PipeChain 4.9.2 can be found at Customer login at www.pipechain.com - Flow on demand
2.1
Actions before upgrading to PipeChain 4.9.2
Before upgrading to PipeChain 4.9.2 from a previous version than 4.9.1, please follow the
instructions in release notes for all previous releases of PipeChain that you need to check. See
www.pipechain.com at Customer login for earlier release notes.
PipeChain Analyzer 4.9.2 does NOT support SQL Server 2000. SQL Server 2005 or SQL Server
2008 is required.
5
PipeChain Release Notes 4.9.2
3
RELEASE NOTES PIPECHAIN 4.9.2
Release notes is a list of all new functions made in PipeChain 4.9.2. The list also includes all new
functions and corrections delivered in service packs in PipeChain 4.9.1.
Please notice that this list is not updated after the release date of 4.9.2. Any new service pack in
PipeChain 4.9.1 created after the release date of 4.9.1 is not included but can be found at
www.pipechain.com, Customer login/Documentation/4.9.1/Service Pack Notes
3.1
New functions and improvments in 4.9.2
3.1.1. POC: Four new fields in Blanket OrderLine
Four new fields are added to blanket order. These new four field are shown in blanket order tab in
Delivery Agreement screen and are used in goods reception screen for POC.
1. Blanket Quantity - shows the maximum quantity that should be received for this blanket order line
2. Recived Quantity - shows the quantity that is received until now for this blanket order line
3. Blanket Amount - shows the maximum amount (cost) that should be received for this blanket
order line
4. Recived Amount - shows the amount (cost) that is received until now for this blanket order line
3.1.2. Possible to retrive received order lines for a delivery note by a
new web service
There is a new web service that can be used to get information about received order lines belloing to
a delivery note. The Web service return following data for each order line
SiteId, Supplier Id, Supplier Delivery Address Id, Delivery Note Id, OrderId, Order Line Id, Product
Id, Product Variant, Quantity, Unit Price, Price Code, Account
3.1.3. POC: New screen in POC for goods reception
New screen in POC for goods reception is introduced. Note this screen should be used by customer
when using POC. The screen supports reception of a whole order and shows data from blanket order
about max and actual values for quantity and amount (cost) for each blanket order line (product).
3.1.4. Platform: Event Scanning BGJob stability
The 'Event Scanning' background job no longer crasches when Event owning User is missing.
3.1.5. POC: Add new row to Invoice
The functionality of the Add new invoice row-button in Create Invoice-screen in the Web Interface
has been extended to incorporate new columns, and bugs has been weeded out.
6
This button is goverend by Selected Property 34, AllowExtraInvoiceRows
3.1.6. POC, Supply: Improved Recipient Info in Delivery Agreement
Detail screens
Delivery Recipient and Goods Recipient was added to Outbound Delivery Agreement Detail screen
(already present on Inbound ditto).
Link jumps to the Address screen were corrected, since focus was always on the first Address line.
Since both "Advanced" tabs have become very large, attributes for
Generation of Suggestions
Sending of Suggestions
Confirmation Margin
Backlog
were moved to the new tab "Delivery Suggestion Parameters".
3.1.7. Platform: AutoConfirm via Event transactions
Event transactions can be used to automatically confirm Messages and MACom Transactions. This
is intended as a help for System Administrators.
The function requires that
- Events are configured and activated
- the Event Scanning background job is enabled
- the event User has enabled Event Export
- the event User has enabled AutoConfirm by adding the string "AutoConfirm" somewhere in the
Description field (this is changed to a checkbox in version 4.9.3)
The function is executed by the Event Scanning background job. Before creating new event
transactions, the available event transactions are used for AutoConfirm if
- the Event transaction is not already handled
- the Event transaction was successfully transmitted
- the corresponding User conforms to the above conditions
All Messages and MACom Transactions identified by such Event transactions are automatically
confirmed.
3.1.8. Supply: Possible to delete finished inbound orders and finished
inbound deliveries
Previously, delete of finished inbound orders and deliveries where not allowed. Only the background
cleanup job was allowed to delete old items.
7
PipeChain Release Notes 4.9.2
Delete of finished inbound orders is now possible and require the privilige Configuring. Delete of an
finished inbound delivery (as opposed to deleting the entire order) requires the privilige Siteadmin.
Outbound uses the same rules.
3.1.9. Platform: UNB support in outbound transactions
For every bussiness node (supplier, customer and own bussiness) you can now enter the Edifact
UNB-address under the tab connection. If these values are not blank, this data will be in put in the
the Receiver and Sender elements in all outbound transactions from PipeChain. This superceeds the
values that are possible to put in the Channel-Transaction mapping.
3.1.10. Platform: Background job recovery after distubancies
The running of background jobs could stop after periods of network distubancies. These problems
are now fixed.
3.1.11. SOC: Shipment and reception time is corrected for inbound
order head in Commission Call-off
Previous, the shipment and reception time for inbound order head was fetched from first outbound
orderline.
Now - it is fetched from the outbound order head.
3.1.12. SOC: The reception time in basket line is not automatically
changed to same value as on order head
Previous, the recption time on line was changed to the one in head - if it was changed.
3.1.13. POC: Restriction on number of suppliers to show Despatch
Order Lines with "All Suppliers"
When a user has access to more than a certain number of suppliers, he can no longer show the
'Despatch Order Lines' screen with the supplier selector set to "All Suppliers". Instead, he will see an
instruction to select a single Supplier.
The reason behind this change is performance and stability.
3.1.14. Supply: Profile setting för Net Demand and Gross Demand POC
screens
There was an error in the Profile Definitions for the POC screens Net Demand and Gross Demand,
causing strange effects when trying to set their privileges. That error is now fixed.
8
3.1.15. Supply: Ship Order screens is now shown after shipping a
despatch
Ship Order screens is now shown after shipping a despatch. Before was the Destatch Overview
screen shown with possiblillity to invoice the despatch, but this was no good solution as user
normaly don't want to invoice directly after creating the despatch. From now on is Ship Order or
Ship Order Line screen shown after shipping.
3.1.16. Supply: Weekly transport dates can be modified in the
Outbound Reception Schedule Detail screen by supplier
The weekly transport dates can be modified in the Outbound Reception Schedule Detail screen by
supplier. Following is required;
The supplier has privileges to configure.
The timezones för supplier has to be equal to customer.
3.1.17. SOC: New order in web shop price range
If the price list is to be shown for user, it is placed first instead of last.
3.1.18. POC: Supplier's Calendar screen
A new screen lets the supplier edit a calendar. Weekdays and speciffic days that are closed can be
entered.
3.1.19. Supply: The Flow model functionality is extended with
DisregardFMDmdBefore, DisregardFMDmdAfter and
DeliverToCustomer
The values DisregardFMDmdBefore and DisregardFMDmdAfter can be set either by Product
Definition message (CS08), Delivery Agreement Definition message (CS10) or interactively in the
Advanced folder in the Delivery Agreement Detail screen.
These values are used when the Flow model from customer (CS21) is read into PipeChain. Flow
periods before DisregardFMDmdBefore and after DisregardFMDmdAfter are removed.
The FlowModel transaction (CS21) now also supports a "DeliverToCustomer" element in the
"FlowModelDeliveryAgreementData" section.
3.1.20. POC: Added Print Buttons in Web interface Despatch Detail
screen
9
PipeChain Release Notes 4.9.2
Print buttons has been added to the Despatch Detail screen. Previously, you could only print from
Despatch Overview. Print buttons are only visible when for a despatch that is sent.
3.1.21. Link from DelivNoteId attribute to OrderLine, Delivery and
Finished Delivery Detail to Despatch Detail screen
To provide a fast way to see the orderlines despatch, a link from the Detail screen's DelivNoteId
attribute to the Despatch Detail has been implemented.
Please note that even though na orderline could have been shipped mulitiple times, only one
DeliveryNoteId is shown.
3.1.22. Supply: Own balance was updated twice in In & Out Deliveries
in Inventory Chart
Own balance was updated tvice in In & Out Deliveries in Inventory Chart. This error is now
corrected.
3.1.23. Supply: The invoce printout is generated if the invoice is
created from a transaction (CS80) as well, not only from POC
web
The PR80 Transaction has to be assigned to a channel.
3.1.24. Supply: Performance improvement in the PipeChain Supply
Overview screen
The PipeChain Supply Overview screen, which is the the first screen you come to after login,
sometimes suffer from poor performance. Depending on the number and state of Inbound Deliveries,
the screen could sometimes take several minutes to load. That problem is now fixed.
3.1.25. Supply: The despatch advice ( CS48) generated from supplier
integration (PW03) is corrected
The supplier Id in CS48 is corrected to the value known by customer.
3.1.26. Supply: CS02 Orderresponse does not add/subtract leadtime
to reception-/and shipment time
If the products Delivery Agreement is set up to use a transport Schedule, the leadtime specified in
the Agreement is disregarded when calculating the shipmenttime from receptiontime and vice versa.
10
Also affects PW02 and updates via the CS38, CS40, and PW40. This error is not present in 4.8.0 and
onwards.
3.2
New functions in 4.9.1 service packs
3.2.1. POC: Add new row to Invoice (SP03)
The functionality of the Add new invoice row-button in Create Invoice-screen in the Web Interface
has been extended to incorporate new columns, and bugs has been weeded out.
This button is goverend by Selected Property 34, AllowExtraInvoiceRows
3.2.2. New fields added to Claim Mail (SP03)
Following new fields are added to Claim Mail:
1. Supplier (SiteId and Site Name)
2. Customer Name (Schema change)
3. Sales Order Id and line
4. Supplier Product Id
5. Supplier Product Name
Purchase Order Id and Line is moved to "Head" of Claim Mail.
The xml schema is updated with customer name
3.3
3.3.1.
Corrections in 4.9.1 service packs
CS80 Invoice transaction corrections (SP01)
Corrected handling of the roundingAdjustment in incomming CS80 so that it is used when
calculating
Gross And Tax.
Also corrected a programming error where rateofexchange and rateofexchange values where
erroneous
3.3.2.
SOC: New order in web shop price range (SP01)
If the price list is to be shown for user, it is placed first instead of last.
3.3.3.
CS80 should be processed error if expecting DESADV and no despatch object found in
PipeChain (SP01)
CS80 should be processed error if expecting DESADV and no despatch object found in PipeChain.
This error is now corrected.
11
PipeChain Release Notes 4.9.2
3.3.4.
POC: CS38 DeliverySchedule nullexception correction
If you hade a orderrow (as opposed to forecastrow) which hade an orderreference, and that order
was missing in pipechain, you would get a nullexception in the transaction reader, as this should not
happen.This eventuality is now handled - A warning is logged if the order is missing.
3.3.5.
SOC: Shipment and reception time is corrected for inbound order head in Commission Calloff
Previous, the shipment and reception time for inbound order head was fetched from first outbound
orderline.Now - it is fetched from the outbound order head.
3.3.6.
POC: CS38 DeliverySchedule transation; Improved handling of orderlines with status 2
Lines that are of status 2 ("Commitment for manufacturing") are in a state between forecast and firm
(=order). A orderline reference might exist, and even if such a referece exists, the order itself might
not exist.PipeChain use to handle the latter case as an error. This is now seen as normal. A warning
is logged if the order does not exist when it should. Please not that this behaviour has been changed
in later service packs, where no warning for a missingorder is logged if the line is in forecast status 2,
but an error is if the forecast status is 1 and the order ismissing.
3.3.7.
POC: Conditional display of link to order in Web Forecast Overview screen
Lines that are of status 2 ("Commitment for manufacturing") are in a state between forecast and firm
(=order). A orderline reference might exist, and even if such a referece exists, the order itself might
not exist. The forecast overview screen now only displays the ordernumber as a link for a line of
status 2 if an order actually exists.
3.3.8.
POC: Optimized POC webinterface screen Despatch Order Lines for faster display.
Optimized Despatch Order Lines so it would run faster by eliminating datasources not used. Also
other (Order) overview screens should notice a performance gain.
Should considerably lessen the strain on the server.
3.3.9.
POC: Profile setting för Net Demand and Gross Demand POC screens
There was an error in the Profile Definitions for the POC screens Net Demand and Gross Demand,
causing strange effects when trying to set their privileges. That error is now fixed.
Review your Profile settings for the mentioned screens.
3.3.10.
POC: Restriction on number of suppliers to show Despatch Order Lines with "All Suppliers"
When a user has access to more than a certain number of suppliers, he can no longer show the
'Despatch Order Lines' screen with the supplier selector set to "All Suppliers". Instead, he will see an
instruction to select a single Supplier.
The reason behind this change is performance and stbility.
Max number of suppliers is set as the se.masystem.Websuppl.DespatchOrderLines.MaxSuppliers
property in Servlet.properties. Please note that missing property sets the restriction to 5.
3.3.11.
POC: Invoice printout including PR80 VAT in account currency
Some issues where the formating and fetching of the report have been solved. An upgraded invoice
report file (StdInvoice.xsl) must be used for this Service Pack and onward.
If no account currency is found in the invoice, the data is fetched from Selected Property 104. If no
invoice currency is found, the currency used is from the order, if avalible.
12
3.3.12.
Plattform: Handled background job Update Order Statuses unnecessary error in message
log
The background job Update Order Statuses mission is to ensure the correct status of orders. It is
triggered via several events. If the order had been deleted or moved to finished during the run of the
background job, the job failes and logs an error. This this circumstance is not exceptional, only rare.
The background job now continues to process any remaing orders, and does not log any errors.
3.3.13.
POC: Invoice CS80 TotalAmountExclTax/GrossNet uses value of
TotalAmountRowsExclTax/GrossRows
SP01 introduced an error where TotalAmountRowsExclTax is used for the value of
TotalAmountExclTax. Theese will differ if you are using invoicefees other than taxes on the
invoicehead. The CS80 Invoice transaction will be processed error if you have invoicecheck enabled.
Does not affect invoices created by the supplier on the PipeChain Web.
3.3.14.
CS02 OrderResponse transaction now handles cancellation of already cancelled orderlines
A cancellation by CS02 OrderResponse transaction on an orderline that is already cancelled is no
longer handled as a fault. Previously, that line caused the transaction to be processed with error, and
processing continued. Now this line will not cause error, but an information-only message will be
logged.
3.3.15.
Corrected label on Order and Orderline General Information text
The label for "General Information" on both Order and Orderline showed "Line Information" or
"Deviation Information". Changed to show "General Information" in all instances.
Note that Order General Information in SOC is Called "Head Information".
3.3.16.
Change of Forecast row in CS38 DeliverySchedule turns up wrong delivstatus
A Forecast row in CS38 DeliverySchedule that is changed from previous forecast, errounusly got
their delivstatus from "Forecast" to "Change Requested". Only Firm rows (ie an actual order) should
change their status. Forecast rows should always use the delivstatus "Forecast". This issue has now
been remedied.
3.3.17.
Web supplier's Outbound Order Overview screen does not count finished order lines
The orderlines column in the Web supplier's Outbound Order Overview screen does not count the
orderlines that are finished. Changed this behaviour. Also added the respective orderlines count
(order lines/finished order lines) on the respective tab header in Outbound Order Detail screen in the
web.
3.3.18.
Supply: Sales Order Id in Web Confirm Replenishment Order Lines
Previously the SalesOrderId was only fetched from the Head. You could thus not have different
Sales Order Id's on an Replenisment order, even thought the actual field is open for input. Also,
SalesSubOrderId was not handled. Rectefied these issues.
3.3.19.
Web Shop: Checking out basket when price range expired
It's been possible to check out a basket line where the price range has expired when the selected
property 10003 was set to "order date". That is no longer the case.
13
PipeChain Release Notes 4.9.2
3.3.20.
Suppliers Web Forecast Delivery Period Overview shows DelivQty instead of DmdQty
The forecast screen is supposed to display Demanded Quantity, instead of Delivery Quantity - which
for a forecast has little mening, and is just set to original Demanded Qty.
This issue has now been adressed.
3.3.21.
Search in Web Forecast Delivery Period Overview does not include all results
The results you get when searching in this screen by date does not include the from and to-dates,
which becomes obvious when you search for a single date, but also a search for a one date intervall
could return zero hits even though there is data.
3.3.22.
Platform: Background job recovery after distubancies
The running of background jobs could stop after periods of network distubancies. These problems
are now fixed. 5 / 7 2012-07-27 16:36:57
3.3.23.
Web Confirm via Order and Forecast screens yield different dates, CS05 OrderResponse
transaction
There is a buisiness logic in the order screen that does not allow you to confirm an order with data
that results in a reception date later than today. This could result in different dates beeing sent in
CS05 when confirming the same order in forecast and in the order screen. This is not the desired
behavior. Enforced the same business logic when confirming orders in the forecast screen as in the
order screen, where an shipment- or receptiondate that is before the current date, the current date
will be used.
3.3.23.1 Forecast transaction CS38, non-firm, non-forecast orderline with missing orders
should have the order created by pipechain.
A non-firm, non-forecast orderline (ie "Commitment for manufacturing", 2 or "Commitment for
material", 3) that are sent into PipeChain might or might not have an order reference. If the
orderreference exist, but the order does not, the order should be created by PipeChain when an
CS38 is received with the orderline in Firm Status. This is now implemented. An already firm
orderline without an existing will not be processed, instead the transaction will be processed with
errors. (Previous behaviour was that only a warning would be logged for any non-forecast line where
the order was missing.)
3.3.24.
Platform: AutoConfirm via Event transactions
Event transactions can be used to automatically confirm Messages and MACom Transactions. This
is intended as a help for System Administrators.
The function requires that
- Events are configured and activated
- the Event Scanning background job is enabled
- the event User has enabled Event Export
- the event User has enabled AutoConfirm by adding the string "AutoConfirm" somewhere in the
Description field (this is changed to a checkbox in version 4.9.3)
The function is executed by the Event Scanning background job. Before creating new event
transactions, the available event transactions are used for AutoConfirm if
- the Event transaction is not already handled
- the Event transaction was successfully transmitted
- the corresponding User conforms to the above conditions
All Messages and MACom Transactions identified by such Event transactions are automatically
confirmed. 6 / 7 2012-07-27 16:36:57
14
3.3.25.
OrderId is missing in Invoice Printout and in PR80 transaction from invoice created by
CS80.
A gap in the functionality has been bridged; The gap is that; for a CS80 supplier invoice, if the
supplier is not shipping in PipeChain and he do not
supply a PurchaseOrderLineId (PurchaseOrderLineId missing or blank), PipeChain cannot perform a
look-up on the OrderLine. This leaves the invoice row without an (PipeChain/Replen) Order Id, for
example. That OrderId will then be missing from PR80 and from the invoice printout.
The look-up functionality has been exteended so that the (PipeChain)OrderId and SalesOrderId are
fetched from the order, even if the orderline could not be found with the data supplied in the
transaction.
But OrderLine-specific attributes as Delivery Id, for example, is still not fetched if
PurchaseOrderLineId is blank or missing.
3.3.26.
3.3.27.
Illegal filename charcters in invoice file, PR80
The filename constructed in PR80 and CS80 transactions are made part from the invoice number.
Sometimes the invoice number contains characters that are illegal to use in a operating system
filename. A windows filename cannot contain any of the following characters: \ / : * ? " < > |
If the characters above are found in the invoice no, these character are replaces in the filename by a
valid character. Fore excample, "/" becomes "-" in the filename. Please note that the actual invoice
number is not changed in any way.
The reception time in basket line is not automatically changed to same value as on order
head
Previous, the recption time on line was changed to the one in head - if it was changed.
Prevent multiple login-attempts on the web
The login page now has scripting functionality to prevent mulitiple log-on attempts. Consecutive
attempts before the original attempts is processed (which could take several seconds during intense
server load). All customized versions are also upgraded.
3.3.28.
Invoice transaction CS80 crashes
There is a problem that makes outbound (customer) invoice transaction crash when matching
invoice and despatch. This issue has now been remedied.
15
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising