Derivations on Data Import

[Former Member]

Hi Sdners,

I have a requirement where the bulk data will be created through data import framework.

Now customer wants some fields to be populated through derivation.

Now question is when this derivation is triggered:

During import process before CR is generated  or after the CR is generated,during finalize processing step.

Also want to know about BRF+ validations when it will be triggered and if the record fails how the user will correct it.

Regards,

Neethu Joy

[former_member209780 · Accepted solution]

Hi Neethu,

Validation and Derivations from BADI and BRF+ happen when you assign the data to your change request and also during the workflow approval process. You can put a breakpoint in your file import class and check this while data import.

Generally easiest approach is to convert the validations to warning messages or bypass the validation during data import in BADI and BRF+based on the Data import change request type - workflow step and enable them as errors during the workflow approval process. If this doesn't fit your requirement you can customize the data import class and build your own logic to handle the file.

Thanks

Goutham

[Former Member · Accepted solution]

Hi Gautham,

Thanks a lot for you reply.

So you mean to say when I click on Import button during that time BRF+ validation and derivations are triggered and we get a CR no. or

the flow is import happens CR gets generated and then we need to go to CR and run validations and derivation .

To make it more clear suppose my import file has 3 fields out of which 3rd field needs to be derived based on field 1.So there are 2 possibilitiy:

Possibility 1 :This process happens during import i.e. when we hit Import button following activities happen

Backend validation are exceuted->BRF+/BADI validation and derivations are excuted ->CR is generated

and if there is any BRF+ validation fails CR ,import process errors out and CR is not generated so here user can correct the file and load again.

Possibility 2 is import gets triggered (during this time only idoc relalted validations are checked)and CR is generated .

User need to go the CR and execute Run Validation to excute BRF+ validation and during this time derivations will also take place.

In the last option if something fails then how user will correct the data as CR is already generated,

Please enlighten which possibility does MDG follows.

Regards,

Neethu Joy

[former_member209780 · Accepted solution]

Hi Neethu,

In data import framework you have two options either you can import the file directly to active area or you can use the governance option and select the change request type to import the file into a change request.

If you go for the governance option the change request gets created but not submitted unless there are no errors in your data. Change request number is generated by the API and then the data from the file is assigned to the change request. If there are any errors like attribute value is not available in check table or validation errors from BADI/BRF+, the file won't be imported and the change request is cancelled. If there are no errors then the data is submitted and the workflow is triggered. Until the file is imported it remains in the logical path and will be archived once imported. Hope this answers your question.

Thanks

Goutham

[Former Member · Accepted solution]

Hi Gautham,

Thanks again for the reply.

1.In the standard SAP document for Check and Dervivations for Material it is mentioned BRF+ is triggered only during "Check","Run Validation","Submit" and "Save" so can I assume that Import is similar to Submit.

2. Also please let me know will derivations be excecuted during the same time?

Regards,

Neethu Joy

[former_member209780 · Accepted solution]

Hi Neethu,

In data import framework you have two options either you can import the file directly to active area or you can use the governance option and select the change request type to import the file into a change request.

If you go for the governance option the change request gets created but not submitted unless there are no errors in your data. Change request number is generated by the API and then the data from the file is assigned to the change request. If there are any errors like attribute value is not available in check table or validation errors from BADI/BRF+, the file won't be imported and the change request is cancelled. If there are no errors then the data is submitted and the workflow is triggered. Until the file is imported it remains in the logical path and will be archived once imported. Hope this answers your question.

Thanks

Goutham

[former_member209780 · Accepted solution]

Yes as I mentioned data is assigned to your change request type and the change request is submitted through the API. This submit via the API is same as the submit you do on the UI. All the validations and derivations in BADI/BRF+ will be triggered and executed.

Thanks

Goutham