cancel
Showing results for 
Search instead for 
Did you mean: 

How to update commitment in R/3 after SC being created

former_member186144
Participant
0 Kudos

Dear gurus,

In my project, there is a requirement that whenever SC is created, a commitment should be updated into Fund Management in R/3. This is to make sure that the Fund Management should get the up-to-date information of all objects that are planned to consume the budget (also to make sure that the behaviour will mimic PR creation in R/3).

However as we're using extended classic, we will not create PR in R/3, thus only PO will be replicated to R/3. Though this will update the commitment for sure, this is considered by the client to be very late already.

So we need to find a way, where once the SC is created, SRM should be able to update the commitment into FM in R/3. Thus when SC is approved and converted into PO, then the commitment will be updated (deleted) and the real commitment from PO should be created in normal way.

I know there is a badi that can be triggered during SC creation, and also during PO creation. But we still stuck on the question of what Function Module that we can use in R/3 to:

a. Create commitment during SC creation,

b. Delete commitment when PO is created.

Can anyone help me on this? Or if someone have other and better way to make this happen, I'm really grateful if you want to share with me.

Best regards,

Yosea

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Yosea,

I had to do something similar in a previous project.

I think, first you should try to avoid but if it is a requirement.

I don't know if with a different (customer) account assignment category would be possible. How the problem is the moment of the commitment, we used tha DOC_SAVE BADI. Take into account, that you should delete the commitment after approval, reject, update during the approval process,....

In my case the commitment was done via a manual CO document (exactly batch-input FMZ1). I remember that exist a FM that did something similar but finally we didn't use and I don't remember know.

If finally you decided to do it in other way, please let me know.

I hope this help you.

Regards

former_member186144
Participant
0 Kudos

Hi Jorge,

Thanks for your suggestion. I think we will going to follow your suggestion. However how can you ensure the integrity of the data in your place. I mean, when we click order, then BADI will trigger and it will all FMZ1 to create shopping cart, and it is successfully posted. However there would be a chance as well that when it return to SRM and continue processing the SC, that SC is failed to be updated (for any reason). So in this case there would be a commitment in R/3 without any related SC in SRM.

How you manage this in your place?

Best regards,

Yosea

Former Member
0 Kudos

Hi Yosea,

As I said you is a hard task, you should analyse all the places where the SC can be update or delete and to react to this. One important is the approval process, there, it depends on if the people in approval process will able to change the shopping cart data and of course the approval or rejection.

In other transactions where the shopping cart can be updated you could analyse the change BADI for doing the adjust in R3.

I hope this at least guide you. good luck

regards

Answers (0)