Update contract request internal ID to "CRW" parameter. How?

Why Contract Request have ID prefix as CW instead of CRW?

Previously, Ariba prefixed newly created Contract Request IDs with CW.
For example: CW2757. When the Contract Request was converted to a Contract Workspace (CW), Ariba assigned the Contract Workspace a new CW ID. Even though the Contract Request and Contract Workspace were linked, they had different CW IDs, which caused some confusion.

Now, Ariba prefixes newly created contract request IDs with CRW (for example, CRW5555). Ariba will continue to prefix Contract Workspaces with CW. Previously created Contract Requests will keep their current internal CW ID (contract workspace ID).

This feature only affects newly created contract requests once the parameter is enabled.

The following parameter controls this feature: Application.ACM.EnableContractRequestNewInternalIdPrefix

Backward Compatibility : Ariba will not migrate existing contract request ID prefixes from the CW to CRW prefix. After this parameter is enabled, all new contract request IDs will use the CRW prefix. Customers can continue to search for the contract request by number only, and Ariba will return search results regardless of whether the contract request starts with CW or CRW. For example, if you want to search for contract request IDs CW2757 and CRW55555, you can enter 2757 only (not using exact match) and the CW2757 contract request displays in the search results. Similarly, if you enter 5555, the CRW5555 contract request displays in the search results. If there are two contract requests with the same ID but different prefixes, Ariba returns both the CW and CRW contract requests.

Strategic Contracts