Customer PO creation using SXAPI Full Order Maintenance
This table show the logic that determines the Customer PO for orders generated by the SX API Full Order Maintenance process.
PO required per customer or ship to record? | Duplicate customer POs allowed per SA Administrator Options | Value sent | Action |
---|---|---|---|
yes | yes | non blank | The value that was sent is used by the system. |
yes | yes | blank | The default PO on the Customer Setup or Customer Ship To Setup record is used, or auto generates a PO number. |
yes | no | non blank | If the purchase order is a duplicate, no order is created. |
yes | no | blank | The default PO on the Customer Setup or Customer Ship To Setup record is used, or auto generates a PO number. |
no | yes | non blank | The value that was sent is used by the system. |
no | yes | blank | The Customer PO # field is blank. |
no | no | blank | The Customer PO # field is blank. |
no | no | non blank | If the purchase order is a duplicate, no order is created. |
Note: The format for an automatically generated PO number is
SXcustno_nnn, where
nnnis a sequential counter.