1. Home
  2. /
  3. Panel Help
  4. /
  5. Australian Functionality
  6. /
  7. Validating a CPO

Validating a CPO

Note:

Related topics

When DC1 receives the EANway order, the system starts validating it for any errors or issues before converting the customer purchase order to a sales order. You can also configure optional validations required for each trading partner, for example the Pack size validation routine. Should the validations fail, the customer purchase order will be held and an entry in the CPO flow log will be recorded. The next validation test will then be performed.

The validations occur in a series of steps which are described below:

Step Additional info
Validate the business partner (BP) ID of the trading partner.  
Validate header dates The Not before and Not after dates in the CPO files are validated to ensure that they are valid dates in the DC1 calendar and that the Not before date is within the number of days forward configured for sales orders.
Validate the To-store BP code The business partner code, which represents the To-store, is used to depict the address of the customer where the order is to be delivered. In the validation process, the validity of the BP code for the To-store is checked in the DC1 Business partner file and whether it is set up as type 1 or type 3 BP.
Validate the For-store BP code The business partner code, which represents the For-store, is used to set the customer code for the order. In the validation process, the validity of the BP code for the For-store is checked in the DC1 Business partner file and whether it is set up as type 1 or type 3 BP.
Validate the EAN code of each item/sales unit combination included in the CPO The EAN code is validated to ensure that it exists in the DC1 Item file details. For situations where an inbound item does not have a valid GTIN and valid item number, an additional check is performed by the trading partner and key code to determine the item number. For this purpose, the DC1 Item cross-reference file is used.
Price and price variance check The price variance check is an optional validation. In this validation stage, the DC1 price of the item is retrieved. If no price is found, then you can set the price as zero. This DC1 price is then compared with the price from the CPO which is retrieved from the Trading partner control file. After comparing, the variance is calculated. If the price variance exceeds the tolerance level for the trading partner, then the CPO is held and an entry will be recorded in the CPO flow log. If NO, the process enters the next stage.
Item availability check In this validation process the availability of all the items in the CPO is checked. If any item is not available in the required time frame as requested by the customer, the CPO is held. The step-wise elaboration of the process is stated below:

  • The CPO contains the details of goods that are to be delivered between the Not before and Not after dates. These dates are used to determine the required time frame in which the goods should be dispatched to meet the delivery requirements.
  • The standard DC1 availability check is then used to determine if stock is available in the dispatch date time frame. Order structure availability checking will follow standard DC1 rules.
  • If the stock for an item is available within the time frame, the earliest date for its dispatch is updated in the CPO line. The next item is then checked for availability.
  • If the stock for an item is not available within the time frame, the earliest date for its dispatch is updated in the CPO line. The CPO is then held and the availability for the next item is checked.
  • When the availability for all the items in the CPO is checked, the system checks if there is an item that is not available in the time frame. As a result, the order is held for stock availability reasons. In this case, the availability check process ends and the system moves to the next validation.
  • If all the items in the CPO are available in the required time frame, the process determines the latest date (within the dispatch time frame) defined as the available date for the item in the CPO. This date is then used as the required dispatch date for all the items in the CPO, and the dispatch date in the CPO lines is updated accordingly. The dispatch date from the CPO lines is used in the creation of the sales order lines.
Floor readiness/retail pricing check In this validation process, the Trading partner file is checked and the retail price list is determined. For each item number, the program attempts to retrieve the retail price from the CPO. If the price is found, no further check occurs for the respective item. If no price is found on the CPO, the retail price is retrieved from the EANway Retail price file. If a retail price record is not found, the Trading partner/item group file is checked to determine if the item requires a label. If any lines in a CPO are unable to retrieve retail price data via the above process, then the CPO will be held.
Validate whether the CPO for the trading partners should always be held for review The final validation is to check if a CPO from a trading partner should always be held for review prior to the creation of sales order pick lists. This is determined by the CPO hld for W/H proc field in the trading partner details. If this field is NO and all other validations have been performed, then the process allows the creation of the sales order pick lists. If YES, then the CPO is held from warehouse pick list generation.