SAP Knowledge Base Article - Public

3015718 - Sold-to party, ship-to party or product is not determined or "wrongly" determined in the “Create Sales Orders - Automatic Extraction” app

Symptom

In the "Create Sales Orders - Automatic Extraction" app, after uploading a purchase order pdf file:

  • The sold-to party, ship-to party or product is not determined.
  • The auto-determined sold-to party, ship-to party or product is different from what is extracted from the pdf file.

Environment

SAP S/4HANA CLOUD

Reproducing the Issue

  1. Open the "Create Sales Orders - Automatic Extraction" app and click the "Upload File" button.
  2. Enter the company code and upload a purchase order pdf file.
  3. Find in the Sales Order Request that the sold-to party, ship-to party or product is not determined or the auto-determined sold-to party, ship-to party or product is different from what is extracted from the pdf file.

Cause

According to the master data determination logic, the sold-to party, ship-to party and product are firstly determined on the basis of historical records.

(1) For sold-to party and ship-to party, if three or more sales orders have been successfully created with the same sold-to party/ship-to party, the next time when the user inputs the same company code and uploads a pdf file from which the same address data can be extracted, the same sold-to party/ship-to party will be determined. If another three or more sales orders are successfully created with a new sold-to party/ship-to party, the next time when the user inputs the same company code and uploads a pdf file from which the same address data can be extracted, the new sold-to party/ship-to party will be determined.

Please pay attention that: the extracted address data (extracted sold-to party/ship to party address data) is returned by the dox service according to the address data in the pdf file and cannot be changed by the users. It is the same with product.

(2) For product, the determination logic is similar with that of sold-to party and ship-to party. The difference is that, instead of the extracted address data, it is the extracted product, extracted customer material or extracted description returned by the dox service that helps with the determination.

There are also other reasons for sold-to party, ship-to party or product not being determined or "wrongly" determined. For example, the information in the pdf file is not extracted accurately by the dox service, or the master data is not well maintained by the customer. Also, when the auto-determined sold-to party, ship-to party or product is different from what is extracted from the pdf file, it is one possible reason that three or more sales orders have been successfully created with the same company code and extracted sold-to party, ship-to party or product data. In other words, this article provides a way to help determine the right information from the perspective of historical records.

Resolution

According to the above explanation of master data determination logic, this symptom is standard behaviour instead of an error. If the sold-to party, ship-to party or product is not determined or the auto-determined sold-to party, ship-to party or product is different from what is extracted from the pdf file, please manually enter or change it (them) in the sales order request and follow the above explanation to help with the future determination.

Keywords

Sold-to Party, Ship-to Party, Product, Determine, Create Sales Orders - Automatic Extraction, F4920, Purchase Order, PDF File, Sales Order Request, Sales Order, Master Data, Determination Logic, Company Code, Upload File, Historical Record, Extracted Address Data, Extracted Sold-to Party Address Data, Extracted Ship-to Party Address Data, Extracted Product, Extracted Customer Material, Extracted Description , KBA , SD-FIO-SLS , Sales Apps , Problem

Product

SAP S/4HANA Cloud all versions