UJR_WRITE_BACK and script logic

[Former Member]

Hi Guys,

We implement a UJR_WRITE_BACK that performs correctly the evenly top-down approach on two dimensions (product and time). Then, we have to convert records created by the UJR_WRITE_BACK in others measures of unit using script logics.

How can we call these script logics?

How can we do it avoiding to write records two time (by the BADI and the by the script logic)?

Thanks for your answers.

Edited by: D-Mark on Aug 4, 2010 11:01 AM

[Former Member]

Hi Mark

This BADI will be called whenever you post data into BPC, could be from Input Schedule and *REC() in script logic.

You don't have to call it as it is a trigger.

It is on you control in the BADI code when Script logic will trigger the BADI to run on what data to be generated and what should not be generated.

Halomoan

[Former Member]

Hi Halomoan,

We need to trigger the UJR_WRITE_BACK BAdI to disaggregate data by evenly top-down approach. Then, trigger some script logics to convert data (created by the BAdI) and run some other calculations.

We know that inside the How-To u201CHow To... Use the Write Back Pre-Process BAdIu201D there are some triggering mode available (MAN, DM, JRN, COMM and DOCS), but they are not executable in our cases.

Do you know how we can avoid trigger the BAdI for each data entry?

By this way could we trigger the BAdI directly by a script logic (START_BADIu2026END_BADI)?

Thanks for your answers.

[Former Member]

Hi Guys,

We have to run the UJR_WRITE_BACK BAdI. When the BAdI finish, we have to run others script logics to do calculations on the records created by the BAdI.

How can we syncronize the BAdI event with the script logic event (i.e. avoiding that the script logic runs when the BAdI is still running)?

Thanks for your answers.

[Former Member]

To trigger the BADI to run or not to run is based on the BADI filter: MAN, DM, JRN, COMM and DOCS.

And I don't think WRITE BACK Badi is designed to do a call back to run other script logic or Badi as it will be end to an endless recursion.

If you have that need to run other logic after the top-down process, could you code the logic in the Writeback Badi itself ?

Halomoan

[former_member200327]

I agree with Halomoan that WRITE_BACK BADI is not a right tool for what you are trying to achieve.

May be better approach would be to put your logic in a Custom BPC BADI that would be called from the DEFAULT script. Than After you call that BADI you can call your other script from same DEFAULT. This way you synchronize BADI execution with script execution and have your logic run every time user hits Save.

If this is not exactly what you are trying to achieve, please provide more details.

And 'yes', you can call your BADI with START_BADI ... END_BADI, just not the BADI you've developed for WRITE_BACK. It should be CUSTOM LOGIC BADI which have a different interface.

Cheers,

Gersh

Edited by: Gersh Voldman on Aug 10, 2010 3:19 PM