cancel
Showing results for 
Search instead for 
Did you mean: 

SC follow on document create from external system

Former Member
0 Kudos

Hi,

I am using SRM 5.0 and having requirement where

I want my shopping cart will not go to create any backend document after approval .

I will create the PO in SRM seprately through legacy system and update it

in Shopping cart follow on document l.

After that it will show the follow on document .

Is there any idea for this ..

Thanks in advance .

Accepted Solutions (0)

Answers (2)

Answers (2)

yann_bouillut
Active Contributor
0 Kudos

Hi,

I don't understand your business requirement ...

However some hints :

Add a step at the very end of your workflow, before PO creation.

Add a new status "PO not created yet" for example.

Release the status when you want to create the PO

Kind regards,

Yann

Former Member
0 Kudos

Hi,

Our requirement is only create the shopping cart (SC) with approval in SRM .

And after approval the process will stop in SRM Purchase Order will be created in SRM but the FM : BBP_PD_PO_CREATE will be trigger from external system .now I want once the PO will create in SRM PO number will stamp in follow on document of SC .So i can get in action details link between PO and SC .

Creation of SC and PO are independent process just to establish link I want to put PO number in SC .

Thanks ..

Former Member
0 Kudos

Hi,

still, it looks like an inefficient process. How do you create the PO in the external

system without the information of the requisition? The process does not make

sense to me. Reqs (SCs) and POs are not independed documents.

In which landscape are you in - which system is the external system?

Maybe that helps to get you some ideas.

Cheers,

Claudia

Former Member
0 Kudos

Hi,

Definately PO will be created in SRM but from external system and when calling to create PO in SRM the interface also have refrence of SC .

Thanks ...

yeushengteo
Advisor
Advisor
0 Kudos

Hi,

I do not understand your requirement completely on why you need to do it this way.

Nevertheless, the closest method i can think of is to deploy your requirment in a local scenario. In other words, your SC and PO will be creating in SRM only. However, instead of creating PO from your legacy system, you will update the SRM PO instead. Not sure if this will help you...

Good luck..

Regards.