JDEdwards World (MOSC)

MOSC Banner

Bypassing the ASN while advancing the status for line type F (Freight) line items

edited Oct 13, 2016 10:32AM in JDEdwards World (MOSC) 2 commentsAnswered

We are in the process of bringing a new customer live for EDI ASNs and invoices (outbound 856s and 810s), and this customer's orders include line type F (Freight) line items that should invoice EDI but should not generate an ASN, which is a new scenario for us.

In our current configuration, when a customer is to receive both EDI ASNs and EDI invoices, the sales order detail line flows from status 560 to status 580 at shipment confirmation; we don't use status 571 (Send EDI Advance Ship Notice) because doing so requires the users to correctly select a version of P4205 based on whether the confirmed line items are to generate ASNs or invoices next, and we found this introduced too much confusion in practice, so instead, all orders are ship-confirmed in exactly the same manner, P47032 looks for orders at status 580 instead of 571 and

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center