Import Sales Orders – Part3: Text fields and pricing elements support
Hi Guys, I am glad to tell you a wonderful news that our Import Sales Orders app is able to support text fields and pricing elements now. In this blog, I will briefly introduce how to use them.
If you are not familiar with this app, please refer to this Blog.
In the excel template, the ‘Field List’ sheet lists all available fields. You can find the field names for text as well.
|Data for Import||Field Name||Field Description|
|Header Text||HEADER_TEXT.<TEXTID>.LONGTEXT||Header text. Logon language will be used by default.|
|HEADER_TEXT.<TEXTID>.LONGTEXT.<LANG>||Language-specific header text|
|Item Text||ITEM_TEXT.<TEXTID>.LONGTEXT||Item text. Logon language will be used by default.|
|ITEM_TEXT.<TEXTID>.LONGTEXT.<LANG>||Language-specific item text|
Generally, you can upload different texts based on text type (text ID). Language-specific texts are also supported. Here,
- <TEXTID> represents Text ID
- <LANG> represents language
When adding these fields to the order data sheet, please remember to replace the <TEXTID> and <LANG> with text ID and language ID defined in your system. For example, if system language is English, and you want to upload ‘Shipping instructions’ in English and German, the column name could be:
HEADER_TEXT.0012.LONGTEXT and HEADER_TEXT.0012.LONGTEXT_DE
Quick tips: To query a text ID as Cloud customers, please open ‘Process Sales Orders’ app, open the value help for text type on the ‘Texts’ tab, and you can find available text names and text IDs. For Op customers, please open the ‘Create Sales Orders – VA01’ app. You can find text IDs and language keys as indicated below.
To import pricing element data, we provide four fields in the template. The import may change an existing pricing element (for which a condition record already exists) or add a new one (for which no condition record exists, but with condition type already defined in the related pricing procedure) when the sales order is created.
|Data for Import||Field Name||Field Description|
|Header pricing element||HEADER_PRICE.<CONDTYPE>.CONDITIONRATEVALUE||Condition Amount or Ratio|
|HEADER_PRICE.<CONDTYPE>.CONDITIONQUANTITYUNIT||Unit of Measure|
|Item pricing element||ITEM_PRICE.<CONDTYPE>.CONDITIONRATEVALUE||Condition Amount or Ratio|
|ITEM_PRICE.<CONDTYPE>.CONDITIONQUANTITYUNIT||Unit of Measure|
Here, <CONDTYPE> is used to distinguish condition types. Please be aware that not all four fields are not required for each condition type. Here are some examples.
Condition type SKTO (cash discount) is used for percentage-based price calculation. You only need to specify the ‘Condition Amount or Ratio’ field. Meanwhile, the app supports value with % or without %.
Condition type PR00 is used for amount-based price calculation. You can choose to fill in all four fields or only specify the ‘Condition Amount or Ratio’ field. If you only specify the ‘Condition Amount or Ratio’ field, the system will default the other three fields as follows:
- If no condition record has been maintained (indicating that you’re adding a new pricing element), the system will default the currency to transaction currency of the sales order, pricing unit to 1, and unit of measure to the sales unit of the product.
- If a condition record has been maintained (indicating that you’re changing an existing pricing element), the system will default the three fields to the values already maintained in the condition record.
If you add pricing element columns to the ‘Order Data’ sheet but leave all fields empty, the system will not transfer empty values to the sales order.
Quick Tips: If want to import a couple of condition types at one time, you can add more columns in the data sheet and replace <CONDTYPE>.
Hope this blog can bring you something new. If you have any questions or ideas, feel free to contact us.
Blogs Series for Import Sales Orders
Hi - Thank you for the writeup - very useful! I was wondering if it's possible to use the Import Sales Order app to create Sales Orders with reference to a Contract number or other Sales Orders? If not, is it in the roadmap for this app?
Hi Yiin, thanks a lot for your feedback! Right now create sales order with reference is not supported in the import apps, and it's also not on our roadmap yet. If you could provide customer requirement to us then it would be very helpful.
Thanks, Miles! Is there a link to provide that requirement?
Hi Yiin, sorry for the late reply due to the holiday season in China. You can create a new CIP(customer influence portal) request via this link:
Once it's created our product management colleagues will pick up the requirement according to the votes. You can also share the link here with us and I can try to put the requirement on our internal roadmap first. Thanks a lot!
Thank you Miles, and Happy New Year to you. I have created the Customer Influence Item below - Hopefully others have the same requirement too!