Documentos de Académico
Documentos de Profesional
Documentos de Cultura
As per defaulting rules we are defaulting customer PO from the sales order
header.
1. After entering the order, the user must verify if the correct Customer PO is
cascaded from the SO header by following the following navigation as shown
below. He can correct it here during its entry.
The issue here is the Customer PO from the SO header is not cascaded to the
line level which in turn is not shown at the AR invoice . The issue occurs only
when the order lines are copied from an existing order.The issue is
demonstated below with sample orders 865258991 & 865258992 from
support.
Below is the order 865258991 whose lines are being copied to 865258992. In
our case we take line 6.1
Whose customer PO is N/A.
Copy Successful
The line is copied to the new order 865258992 as 11.1. If we look at the
customer PO field the PO from the order 865258991 is copied.
Now we copy the same line from order 865258991 to 865258992 with
Default Missing attribute unchecked.
Now we clear the Customer PO from line 6.1 in 865258991 and then copy
to 865258992 with Default Missing Attributes checked as shown
below.
After copy you see that the Customer PO from SO 865258992 header is
cascaded to the line as well because Defaulting rules work only
when you are creating a new line and not when you are updating it
hence cascading did take place here. i.e. you have PO = Null from
the source which will be updated during copy as per defaulting rule
as shown below.
Hence to prevent this issue from occurring follow any of the below: