3751454 - CMD_VALIDATE_BP lacks importing parameter for BP identification.

• CMD_VALIDATE_BP extension point does not have an importing parameter for BP Identification.
• There is a requirement to validate newly created business partners using entered BP Grouping, Tax Category/Number, and BP Identification Type/Number.
• Custom logic was implemented using CMD_VALIDATE_BP, but the required importing parameter for BP Identification is missing.
• A method is sought to extract BP Identification information from the extension point.

SAP S/4HANA Cloud Public Edition

1. Implement custom logic using the CMD_VALIDATE_BP extension point.
2. Attempt to validate newly created business partners using BP Grouping, Tax Category/Number, and BP Identification Type/Number.
3. Observe that the importing parameter for BP Identification is missing.

CMD_VALIDATE_BP does not provide importing parameters for BP Identification in the current version by design.

1. Do not use CMD_VALIDATE_BP for validations that require access to BP Identification data.
2. Implement the validation using the Unified BAdI MDBPCV_VALIDATE_BP, which replaces CMD_VALIDATE_BP.
3. Locate the custom logic entry point via: Object CVI_EI_ADAPTER → PROCESS_SINGLE_LUW → Line 45 → CL_MDBPCV_UFBD_UTIL=>PREP_CVIS_AND_CALL_BADI.
4. Perform all required validations (Customer, Supplier, and general Business Partner data) within MDBPCV_VALIDATE_BP.
5. Test the implementation to verify that BP Identification Type/Number can be read and validated as required.

• refer to: BAdIs for Custom Checks of Fields in the Business Partner Master Data Apps

CMD_VALIDATE_BP, MDBPCV_VALIDATE_BP, Business Partner, identification, ID type, ID number, validation, custom logic, BAdI, missing parameter, import parameter, CVI_EI_ADAPTER, PROCESS_SINGLE_LUW, CL_MDBPCV_UFBD_UTIL , KBA , LO-MD-BP-2CL , Business Partners for Public Cloud , Problem