External pricing updates supported through ION API
External systems can use SX.API calls to update pricing information in Distribution SX.e.
Updates to pricing records
Pricing information is sent to Distribution SX.e in the sxapiPDPricingAllMnt call. The Import Excel logic from PD Mass Maintenance Entry is used to create, maintain, and delete records in PD Pricing Setup. The price types for all price records are supported.
Data validation is performed, based on standards that are used when an Excel spreadsheet is imported into PD Mass Maintenance Entry. If the updates are performed successfully, the set is removed from PD Mass Maintenance Entry.
Error messages for updates that failed validation are sent to the external system so the updates can be corrected and resent to Distribution SX.e. Errors are also displayed in EDI Electronic Transaction Control Center Entry (ETCC). These types of errors can occur:
- Fatal: These errors can occur when data that is related to the API call is invalid or missing.
- PDEM: These errors can occur when data that is related to the pricing records is invalid or missing.
- Duplicate: These errors occur if duplicate records are not allowed, based on the Allow Multiple Prices business rule.
Infrequently, an update can be received and validated but fails to update because of an event, such as a record lock. If such a situation occurs, you can manually perform the update in PD Mass Maintenance Entry.
These business rules determine if duplicate price records are permitted and determine default start and end dates on pricing records:
-
Allow Multiple Prices
Create this business rule with the Rule Value set to Yes to allow the creation of pricing records that are identical to existing records, excluding the start date. If the business rule was not set up or the Rule Value is No, an duplicate record error occurs.
-
Default Pricing Start
Create this business rule with the Rule Value set to Yes to prevent a fatal error from occurring when a start date is not included in the SX.API call.
-
Default Pricing End
Create this business rule to determine the end date on pricing records for which an end date was not included in the SX.API call.
Specify the number of days that the pricing record is effective in the Rule Value field. You can specify a value from 0-999. The end date is the value that you specify plus the start date. For example, if the start date is August 1 and the Rule Value is 30, the end date is August 31.
If you specify 0, the end date is the same as the start date. If you specify a value other than 0-999, the end date is the same as the start date
If the business rule is not set up, the end date from the SX.API call is used. If an invalid end date is included in the SX.API call, an error occurs. If an end date is not included in the SX.API call, the end date is blank on the pricing record. Because the PD Administrator Remove/Inactivate Customer Price Report cannot remove pricing records without end dates, we recommend that you do not leave the end date blank.
Updates to pricing sheets
Pricing sheet information is sent to Distribution SX.e in the new sxapiPDPriceSheetMnt call. Validation logic from data conversion and pricing sheet functions is used to create, maintain, and delete records in PD Pricing Sheet Setup. Error messages for updates that failed validation are sent to the external system so the updates can be corrected and resent to Distribution SX.e. The errors are also displayed in EDI Electronic Transaction Control Center Entry (ETCC).
Create the Default Price Sheet End business rule to determine the end date on pricing sheets for which an end date was not included in the SX.API call. The Default Price Sheet End business rule applies end dates to pricing sheets as the Default Pricing End business rule applies end dates to pricing records. See the information above.