Problem. PO isn't created.

[Former Member]

Hi all,

I have an issue with PO's.

When I create the SC, PO isn't created in background, it previously be created without problems.

What can be the problem?

Many Thanks.

Regards,

David

[former_member183819]

Hi

What is the status of your sc ? You check via CHECK STATUS.

is it awaiting for approval. check it up ? or wento to sourcing cockpit?

Any error in Application monitor or RZ20.

Update your scenario ?

regards

muthu

[Former Member]

Hi,

The status of SC is Approved. I have put a BP into the FM BBP_PD_PO_CREATE, but it isn't launched.

Thanks!

BR,

David.

[former_member183819]

Hi

Is it via zprogram?

as per standard the crmd_partner table helps to create a PO depends upon the partner function of vendor.( all required BP s are stored int hat table). no idea much via program.

regards

muthu

[Former Member]

Hi,

It isn't via zprogram. It is via standard.

Regards,

David.

[Former Member]

Hello David,

Did you get a solution for your problem.

Even i'm facing the same problem.After the Shopping Cart is approved,PO is not created.

Status of Shopping Cart is Approved.

Please let me know how you tackled this issue.

Thanks in Advance,

Navin

[former_member183819]

Hi Naveen

create a new thread .. for your new request.

BBP_PDIGP -Table SOURCE_REL_IND - field value = ?

are you in extended classi or classic?

Are you grouping sc and run some jobs for creating PO ?

update here bbp_pd status of your sc.

br

muthu

[Former Member]

Hi Muthu,

Table - BBP_PDIGP

Field - SOURCE_REL_IND has no value,this field is blank.

We are using extended classis scenario.

We are not using any jobs to create PO from SC.

As soon as the SC is Approved by the approver,a corresponding PO gets created..

Only for a few SC we are facing such a problem.For all others its working fine..

br,

Navin

[former_member183819]

Hi naveen

it is a hide and seek game for you

plz check process Purchase order ? or PO created with held status.

regards

muthu

[Former Member]

Hi Naveen,

Execute transaction SLG1 and check if you have any error.

Our issue was due to an one determination pricing error.

Regards,

David.