Sh.Cart created from PR - but not visible in SOCO(MaterialsHas MRPview)

[Former Member]

Hi,

We are in SRM 7.0 Classic scenario - EhP4 - Using ECC-PI-SRM route to transfer docs.

When a PR is created with materials which has MRP1 view with MRP Type value 'ND - no mrp' .... transfered to central system - Shopping cart is getting created. Issue is : this Shopping cart is not displayed in Assign sources of Supply(SOCO) screen.

Shopping carts with PR's containing materials without MRP view are displayed in Assign Sources of supply(SOCO) screen.

We are creating RFx from Assign sources of supply screen by selecting the Shopping carts .

Pls suggest as how to make the "Shopping carts from PRs having materials with MRP view" available in SOCO.

Thanks,

Ashwin.

[Former Member · Accepted solution]

Hi

Check the following configuration:

1. SRM server->Sourcing->Define sourcing for product categories(is it "sourcing never carried out")

2. SRM server->Cross application basic settings->Define objects in backend system

3. Based on the config of point 2, check in the SC if it has a fixed vendor and PO is already created due to which the SC is not shown in the SOCO.

4. Check SXMB_MONI in both SRM and ECC side.

5. use transaction /n/sappo/ppo2 to see the issue.

6. Has PI configuration been done for the interface:

PurchaseRequestERPSourcingRequest_Out, PurchaseRequestERPSourcingRequest_In

PurchaseRequestERPSourcingConfirmation_Out, PurchaseRequestERPSourcingConfirmation_In

with regards

Manjunath

[Former Member · Accepted solution]

Hi Manjunath,

All the PI & ESOA configs are done, because Shopping carts are getting created and are visible in SOCO screen.

All settings are maitained as u mentioned.

As Mentioned in my initial post that we are NOT able to see the Shopping carts in SOCO screen which has materials which has MRP view.

Hope the issue is now clear?

-Ashwin.

[former_member183819 · Accepted solution]

Hi

Can you see those shopping cart in monitor shopping cart ? Indeed shopping carts are created but sourcing flags are not set for those items?.

How requistions are created from ERP or PM /PS ?

what is your technical scenario ?

[Former Member · Accepted solution]

Hi,

Shopping cart is displayed in powl and able to display the same.

Sourcing flags are not set for those items.(why is this happening)

Requisitions are transferred from ERP.

We are using classic scenario.

PR is created in ERP - In SRM using transfer to central system option - SC number is displayed against the related document for PR.

Example:

Material A1 - NOT having MRP view.

Material A2 - has MRP view with MRP Type value 'ND'.

PR-10001 (with A1 Material) created in ERP ---> transferred to SRM through PI ---> Result1: SC1 is created.

PR-10002 (with A2 Material) created in ERP ---> transferred to SRM through PI ---> Result2: SC2 is created.

Result 1: SC1 is displayed in sourcing cockpit, able to select this cart and further create RFx for the same. - This is the expected behaviour and no issue with this.

Result 2: SC2 is NOT displayed in sourcing cockpit.

Thanks,

-Ashwin.

[former_member183819 · Accepted solution]

Hi Aswin

As of Know , Define sourcing only controls the sourcing criteria

you might be checked - however double check - In define sourcing config the material group is menetioned or not .

or Do you use any src determine BADI not to venture the cockpit by any cutom logic.

[former_member183819 · Accepted solution]

what is the sc item status APPROVED or Purchaser worklist

[Former Member · Accepted solution]

Hi Muthu,

Checked config, the material group criteria maintained is ''* so shouldnt have problem with that. Becuz same material maintained in other plant without MRP view is visible in SOCO.

No sourcing BADIs are implemented.

However, observed that item detail(BBP_PD) has 'CHECK_IND' as 'E' . This is not the case with Scarts visible in soco.

Thanks for ur inputs - but issue stll exists.

-Ashwin.

[Former Member · Accepted solution]

Hi Ashwin,

Check SXMB_MONI or /n/sappo/ppo2 in SRM and ECC, are you seeing any issues here?

with regards

Manjunath

[Former Member · Accepted solution]

Hi Manju,

SXMB_MONI is getting cleared, becuz shopping cart is created in srm. but it is not visible in sourcing cockpit.

No messages are displayed in /n/sappo/ppo2 .

-Ashwin.

[former_member183819 · Accepted solution]

This is little work around FM BBP_PDH_DB_DIRECT_UPDATE By using this FM you can can forcely send them to cockpit. but SAP has to do automatically .

Create ONE oss message under SRM-EBP-EXR

It may not happen due to your master data as you expected. let us wait for SAP reply ..

Question:

Why has my shopping cart not come to the Sourcing Cockpit ?

Answer:

Whether or not a shopping cart/external requirement goes to the Sourcing cockpit depends on the customizing SPRO settings for Define Product Categories for Sourcing (see attachment).

Here there are the following options:

Sourcing Always carried out

Sourcing Never carried out

Sourcing carried out for items withour Assd Source of supply

Aut. creation of Bid Inv for items w/o source of supply

Aut. Grouping. Sourcing for items withour source

Aut. Grouping, sourcing is never carried out

Aut. Grouping, and creation of Bid Inv w/o source

The technical field to check is : BBP_PDIGP-SOURCE_REL_IND

[Former Member · Accepted solution]

Hi,

Yes, the same technical field is checked for sourcing relevant indicator.

Checked Muthu's earlier post where this FM was mentioned to directly update the DB, however running this FM is not changing the sourcing indicator.

Will open an OSS for the same.

Thanks for all the support.

Warm Regards,

Ashwin.

SRM Techno Functional.

[Former Member · Accepted solution]

Hi Ashwin,

Did you get any reply from SAP to this issue?

I am experiencing the same issue but when the purchaser edit the SC from SOCO. We have activated the modification of Delivery Date from SOCO.

Thanks in advance for your help.

Regards.

[Former Member · Accepted solution]

Hi Acosta,

This was a primitive version SRM7.0 where i was facing issue but was resolved by SAP with an OSS note i think. But i didnt see this issue in the later versions of SRM7.01 & SRM7.02.

Warm Regards,

Ashwin.