New API Parameters to Support JSON Format for Sales Orders

We have introduced the ability to process Sales Order Requests in JSON Format in release 24B. For Sales Orders  that honor shipsets, if the Sales Order comes in multiple batches, then WMS cannot guarantee allocation of the Sales Order all at once as waves could be running at different intervals. INIT_STAGE_INTERFACE_API already has parameters to support multiple batches.

We are adding similar parameters for Sales Orders so that WMS picks up Sales Order processing only after all the records are captured.

The following parameter updates have been added to the Sales Order API:

Section	Name	Type	Required	prevent_stage_hdr_record_creation_flg
parameters	prevent_stage_hdr_record_creation_flg	boolean (y/n)		Default value is "no" to retain backward compatibility. When the value is no, WMS will create a new header record for the entity key in the corresponding stage tables. If the value is passed as "yes" then the new header record will not be created in stage tables and the detail records will get appended to the stage header record with the same file group number.
parameters	file_group_num_without_timestamp_flg	boolean (y/n)		Default value is "no" to retain backward compatibility. If the value is set to "no", then the filegroup number is generated (message_id appended with timestamp (YYYYMMDDHHMMSS format) as the file group number. If the value is set to "yes", then file group number is the same as the message id passed in the XML payload.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.