Last updated on JULY 14, 2017
Applies to:Oracle Retail Allocation - Version 14.1.2 and later
Information in this document applies to any platform.
Allocation is not parsing certain error messages returned from ALLOC_WRAPPER_SQL correctly. When creating a purchase order in Allocation and the order does not meet vendor minimums, the message displayed to the user is cryptic and not parsed. For example, an error of ‘@0VEND_MIN_ORDER@1123456@2Amount@3250’ will be displayed. If correctly parsed, this error message would read ‘Order 123456 did not meet Amount minimum of 250.’
To create purchase orders the Allocation code will call the ALLOC_WRAPPER_SQL.CREATE_MOD_LOCPO function, which in turn will call the CORESVC_STOREORDER.CREATE_MOD_LOCPO function. Within CORESVC_STOREORDER.CREATE_MOD_LOCPO the code will create the XML to be used by the standard XORDER API. Now although CHECK_VEND_MIN is called in RMSSUB_XORDER.CONSUME, it will only be called for ‘Approved' orders, which is not the case for Allocation orders. Thus, an additional call to CHECK_VEND_MIN after the return from RMSSUB_XORDER.CONSUME. However, if you look at RMSSUB_XORDER you will see that before returning control it will call API_LIBRARY.HANDLE_ERRORS to parse any error messages before returning. This is not the case when calling CHECK_VEND_MIN directly. CHECK_VEND_MIN will return an unparsed error message in the IO_error_message parameter. Thus, there needs to be code in CORESVC_STOREORDER.CREATE_MOD_LOCPO to parse any error message returning from the direct call to CHECK_VEND_MIN.
Steps to recreate:
1. Start creating a What If allocation
2. Allocate to a store
3. Enter Quantity Limits Min Gross Need
4. Calculate the allocation
5. Click on What If Summary
6. Try creating the PO
7. User will be presented with a cryptic message which is not properly parsed
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms