Error: Status code: 657 Error: Invalid record_no When Creating BP Records Via Web Services
Last updated on NOVEMBER 14, 2016
Applies to:Primavera Unifier - Version 9.14 and later
Primavera Unifier Cloud Service - Version 9.14 and later
Information in this document applies to any platform.
Unifier allows for configuration of the Sequence Format for record numbers. For cost-type business processes of the Change Commit type, there is an option to use the corresponding Base Commit’s record number. This option allows selection of a separator and start number for the sequence. The default separator for this configuration is a dot (i.e. “.”). After accepting this configuration for Change Commit records, Unifier will generate record numbers with the specified format. For example, a valid record number could be “CO-00001.0001” and Unifier will proceed to number records accordingly.
However when a web services call is made using the "updateBPRecordV2" function to a Change Commit BP record that uses the dot separator in the record numbering scheme, the web services call fails due to the record number not being accepted by the web services. The web services should accept and process the valid record number, but it does not.
Status code: 657 Error: Invalid record_no
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms